CN101248630A - Method for implementing automatic exchange optical network fast heavy route - Google Patents
Method for implementing automatic exchange optical network fast heavy route Download PDFInfo
- Publication number
- CN101248630A CN101248630A CNA2005800513798A CN200580051379A CN101248630A CN 101248630 A CN101248630 A CN 101248630A CN A2005800513798 A CNA2005800513798 A CN A2005800513798A CN 200580051379 A CN200580051379 A CN 200580051379A CN 101248630 A CN101248630 A CN 101248630A
- Authority
- CN
- China
- Prior art keywords
- network element
- link
- route
- node
- service
- 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
Links
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L45/00—Routing or path finding of packets in data switching networks
- H04L45/28—Routing or path finding of packets in data switching networks using route fault recovery
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L45/00—Routing or path finding of packets in data switching networks
- H04L45/02—Topology update or discovery
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04Q—SELECTING
- H04Q11/00—Selecting arrangements for multiplex systems
- H04Q11/0001—Selecting arrangements for multiplex systems using optical switching
- H04Q11/0062—Network aspects
- H04Q2011/0073—Provisions for forwarding or routing, e.g. lookup tables
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04Q—SELECTING
- H04Q11/00—Selecting arrangements for multiplex systems
- H04Q11/0001—Selecting arrangements for multiplex systems using optical switching
- H04Q11/0062—Network aspects
- H04Q2011/0079—Operation or maintenance aspects
- H04Q2011/0081—Fault tolerance; Redundancy; Recovery; Reconfigurability
Landscapes
- Engineering & Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Data Exchanges In Wide-Area Networks (AREA)
- Mobile Radio Communication Systems (AREA)
Abstract
A fast rerouting method for automatically exchanging optical network, each node detectes several alarm conditions in all links of the node in time. When a fault of link be detected, the node searches a traffic beared at the failed link with fault, if the traffic exists, the node sends a signaling information including failed link information to a source node of the traffic sequentially. After detecting the failed traffic and receiving the signaling information, according to the restoration policy, the current node acts as the resource, the service destination node acts as the destination, the source node caculates the restoration route newly, the resource node connected with service begins to restore the signaling course of routing establishment. According to the described method in the present invention, it reduces the need of the link resource of network topology, avoids the blindness of selecting the restoration route channel, improves the success rate of service restoration , and shortens the service restoration time.
Description
A kind of implementation method of the quick heavy-route of ASON
Technical field
The present invention relates to the implementation method in transmission net field, more particularly to a kind of quick heavy-route of ASON.Background technology
Optical-fiber network, such as OTN (Optical Transmission Network, optical transport network), WDM (Wavelength-Division Multiplexing, wavelength-division multiplex), SDH (Synchronous Digital Hierarchy, Synchronous Digital Hierarchy)Or SONET (Synchronous Optical Network, Synchronous Optical Network)Transmission net, extensive use is had been obtained in field of telecommunications.
ASON(Automatic Switched Optical Network, abbreviation ASON) be field of optical networks in recent years study hotspot.ITU-TG.8080 and G.771X series suggestion propose ASON concept, the special control plane by setting(Control Plane, abbreviation CP) the automatic foundation of finishing service connection, the function such as automatic recovery of connection.
Self-healing ability is an important feature of optical-fiber network.International Telecommunication Association's ITU-TG.841 suggestions《The classification of SDH network protection structures and characteristic》SDH/SONET optical transfer network self-healing functions are described in detail.Its guard method recommended includes being based on path(Path protection) and based on link(Link protection).Based on path(Path protection), it is most common to have path protection and SNCP;Based on link(Link protection), it is most common to have two fine or Four-fiber MS shared protection ring, 1+1/1:N Linear multiplex section links etc..Path protection, multiplex section protection have obtained application widely in conventional optical network, but for complex networks such as mesh networks, above-mentioned protected mode is no longer appropriate for because taking a large amount of standby resources.
It is general that self-healing function is realized using " reset mode " for mesh network.Current ASON mainly realizes the automatic recovery of business using dynamic heavy route method, and its general principle is:After service connection breaks down, network element in heavy-route domain is based on its control plane, uses the methods such as source routing, hop-by-hop route or hierarchical routing to find connection again for customer service, finishing service it is automatic
Recover.
Rerouting recovering flow as shown in Fig. 1, is characterized in routing database(RDB, Routing DataBase) update complete after start business recovery, although this restoration methods reliability based on newest RDB is high, but link failure information spreads and RDB renewals cause service recovery time to have larger delay, for catenet, postpone then more obvious.If starting business recovery when faulty link information is not also diffused into business source node, the selected restoration route of business source node may still pass through faulty link, cause business to be successfully recovered.
In order to solve this problem, G.7715 ITU-T proposes is constrained using route diversity, including node separation, link disjoint and sharing memory(SRLG, Shared Risk Link Group) the router-level topology constraints such as separation carries out the channel selecting of restoration route, its purpose is to it need not be updated in RDB on the premise of, in the case of need not faulty link being accurately positioned, shorten service recovery time and improve the possibility that business is successfully recovered, its handling process is as shown in Figure 2.But this mode has higher requirements to network topology resource, real network topology can not necessarily be supported to route diversity constraints, in this case, whether business can be recovered to be still the diffusion and RDB renewals dependent on faulty link information, business recovery needs are caused to take a long time, it is impossible to meet the requirement of the fast quick-recovery of business.In addition, even if real network topology can be supported to route diversity constraints, but the signaling procedure time longer rather than optimal restoration route that the network element node that may be passed through by the restoration route searched out excessively causes network resource utilization not high and connection is set up, as shown in Figure 3, there is a business between network element A and network element Z, initial Work route is A-F-H-Z, if F-H link failures, the route calculated according to route diversity constraint is A-B-C-D-E-Z, but there are in fact a more preferable restoration route A-F-G-Z.
It is therefore desirable to have a kind of implementation method of the quick heavy-route of ASON, after service connection breaks down, can fast and accurately recover business route.The content of the invention
The technical problems to be solved by the invention are the implementation method for providing a kind of quick heavy-route of ASON, to overcome current ASON rerouting recovering success rate not high,
Recovery time slow shortcoming, realizes that success rate is high, recovery time is fast and saves the quick heavy-route of Internet resources, fast and accurately recovers business route.
The present invention provides a kind of implementation method of the quick heavy-route of ASON, comprise the following steps-(1) network in each network element detect the alert situations of all links of this network element in real time, when certain network element detects relevant link failure, into step(2), otherwise, continue to detect;
(2) service connection carried on the failed link that network element search is broken down, if carrying service connection, into step(3), otherwise return to step(1 ) ;
(3) network element sends the signaling message for including failed link information to the source endpoint network element of service connection successively;
(4) the source endpoint network element of service connection detects service failure and received after the signaling message comprising failed link information, according to recovery policy, using this network element as source, using business purpose network element as place, a restoration route is recalculated, if success, into step(5), otherwise return to step(1 );
(5) the source endpoint network element of service connection starts the signaling procedure of restoration route foundation.
Each network element all includes Link resource manager, connection controller, path control deivce and protocol controller, wherein:
The Link resource manager for detecting the network element of link failure completes detection and the management function of chain circuit alarming, and is responsible for notifying link failure information by the protocol controller of this network element the connection controller of the source endpoint network element of service connection;
The connection controller of source endpoint network element inquires about restoration route according to recovery policy to the path control deivce of this network element, the path control deivce of source endpoint network element is received after the inquiry request of connection controller, calculate restoration route, and result of calculation is returned to connection controller, the router-level topology result that the connection controller of source endpoint network element is returned according to path control deivce starts the signaling procedure that restoration route is set up.
Step(4) recovery policy described in can repel failure route to repel the network element node at faulty link two ends or repel the relevant link for having identical sharing memory with faulty link.
Using the method for the invention, compared with existing Reroute techniques, reduce to network topology chain
The requirement of road resource, it is to avoid the blindness of restoration route channel selecting, improves the success rate of business recovery, shortens service recovery time.' Summary of drawings
Fig. 1 is the rerouting recovering method flow diagram that failure broadcast mechanism is used in background technology;Fig. 2 is the rerouting recovering flow chart using route diversity tied mechanism in background technology;Fig. 3 is the mesh network structure chart that can support to route the rerouting recovering of diversity tied mechanism in background technology;
Fig. 4 is the control plane assembly assumption diagram of ASON according to embodiments of the present invention;Fig. 5 is technical solution of the present invention flow chart according to embodiments of the present invention;
Fig. 6 is the mesh network structure chart for being used to illustrate specific embodiment according to embodiments of the present invention.The preferred forms of the present invention
Below in conjunction with the accompanying drawings and preferred embodiment is described in further detail to technical solution of the present invention.
As shown in figure 4, being technical solution of the present invention functional block diagram, G.8080 technical solution of the present invention advises described control plane standard package, including Link resource manager using ITU-T(Link Resource Manager, abbreviation LRM), connection controller (Connection Controller, abbreviation CC), path control deivce(Routing Controller, abbreviation RC), protocol controller(Protocol Controller, abbreviation PC).Relation between each component units is as shown in figure 4, LRM completes detection and the management function of chain circuit alarming, and is responsible for notifying link failure information by protocol controller PC the source endpoint CC of service connection.Source endpoint CC inquires about restoration route according to recovery policy to RC.The Check that RC receives CC askes request, calculates restoration route based on current RDB, and return to result of calculation.The router-level topology result that source endpoint CC is returned according to RC starts the signaling procedure that restoration route is set up.
Fig. 5 is the flow chart of technical solution of the present invention, is comprised the following steps:
Step 501:Each network element detects the alert situation of all links of this network element in real time in network;
Step 502:Judge whether each network element detects link failureIf detecting link failure, continue, otherwise return to step 501;
Step 503:The network element for detecting link failure searches for the service connection carried on this failed link;
Step 504:Judge whether carry service connection on failed linkIf it is, continue, otherwise, return to step 501;
Step 505:The source endpoint network element of the service connection to being carried on failed link sends the signaling message for including failed link information successively;
Step 506:The source endpoint network element of service connection receives the signaling message for including failed link information, according to recovery policy, using this network element as source, using business purpose network element as place, recalculates a restoration route;
Step 507:Judge whether restoration route calculates successIf it is, continue, otherwise, return to step 501;
Step 508:The source endpoint network element of service connection starts the signaling procedure of restoration route foundation, can continue return to step 501, continues to detect.
Fig. 6 is the mesh network structure chart for illustrating specific embodiment, its link F-G, F-E belong to SRLGl (sharing memory 1), link C-G, F-E belong to SRLG2 (sharing memory 2), and link E-Z, H-Z belong to SRLG3 (sharing memory 3).
Describe the specific embodiment that the present invention takes different recovery policies in detail in conjunction with Fig. 4, Fig. 5, Fig. 6.
Hypothesis below is done first:Network element A to network element Z has a business, initial Work route is shortest path A-F-E-Z, and the 1# passages of 1# passages, F-E links, the 1# passages of E-Z links through A-F links are transmitted.If the receipts fiber failure in F-E link F directions, the present invention will carry out quick rerouting recovering using specific embodiment described below to business.
Embodiment 1, is, when recovery policy is repels specific embodiment during faulty link, to comprise the following steps:
Step 1: network element A, B, C, D, E, F, G, H and Z LRM detect this in real time
The alert situation of each link of network element;Network element F LRM detects the receipts fiber failure in local F-E links F directions;
Step 2: the service connection carried on network element F LRM search F-E links;Search result is to carry A-F-E-Z service connections on F-E links;
Step 3: network element F LRM is sent to service connection A-F-E-Z source endpoint network element A
F-E link failure message; ·
Step 4: network element A CC receives F-E link failure message, and using A network elements as source, for the purpose of Z network elements, and the RC inquiry restoration routes using repulsion failed link F-E as router-level topology constraints to this network element.It is A-F-G-H-Z that RC, which returns to routing inquiry result,;
Step 5: the route Check that network element A is returned according to local RC askes the signaling procedure that result starts restoration route foundation.The final recovery connection for setting up a 1# passage for passing through A-F links, the 1# passages of F-G links, the 1# passages of G-H links, the 1# passages of H-Z links.Embodiment 2, is the specific embodiment when network element node of the recovery policy for repulsion faulty link two ends, comprises the following steps:
Step 1: network element A, B, C>D, E, F, G, H and Z LRM detect the alert situation of each link of this network element in real time;Network element F LRM detects the receipts fiber failure in local F-E links F directions;
Step 2: the service connection carried on network element F LRM search F-E links;Search result is to carry A-F-E-Z service connections on F-E links;
Step 3: network element F LRM sends F-E link failure message to service connection A- F-E-Z source endpoint network element A;
Step 4: network element A CC receives F-E link failure message, and using A network elements as source, for the purpose of Z network elements, and the RC inquiry restoration routes using repulsion network element F and network element E as router-level topology constraints to this network element.It is A-B-C-G-H-Z that RC, which returns to routing inquiry result,;
Step 5: the routing inquiry result that network element A is returned according to local RC starts the signaling procedure of restoration route foundation.One is finally set up by the 1# passages of A-B links, the 1# of B-C links to lead to
Road, the 1# passages of C-G links, the 1# passages of G-H links, the recovery connection of the 1# passages of ^ chains;Embodiment 3, is, when recovery policy is repels specific embodiment when having identical SRLG relevant link with faulty link, to comprise the following steps:
Step 1: network element A, B, C, D, E, F, G, H and Z LRM detect the alert situation of each link of this network element in real time;Network element F LRM detects the receipts fiber failure in local F-E links F directions;
Step 2: the service connection carried on network element F LRM search F-E links;Search result is to carry A-F-E-Z service connections on F-E links; .
Step 3: network element F LRM sends F-E link failure message to service connection A-F-E-Z source endpoint network element A;
Step 4: network element enter (receive F-E link failure message, using A network elements as source, restoration route ask for the purpose of Z network elements, and using RC Checks of repulsion link F-E, C-G, the F-G as router-level topology constraints to this network element.It is A-B-C-D-E-Z that RC, which returns to routing inquiry result,;
Step 5: the routing inquiry result that network element A is returned according to local RC starts the signaling procedure of restoration route foundation.The final recovery connection for setting up a 1# passage for passing through A-B links, the 1# passages of B-C links, the 1# passages of C-D links, the 1# passages of D-E links, the 1# passages of E-Z links.
Described from above-mentioned implementation process and contrast, technical solution of the present invention can be further to define have following excellent eight to account for, '
Source node is when carrying out restoration route calculating, it is not necessary to wait routing database to update, and the time efficiency of recovery is high;
Source node is able to know that faulty link information when carrying out restoration route channel selecting and avoids faulty link, and the success rate of recovery is high;
The inventive method is applied to any complex network, and the network bandwidth can be saved while fast quick-recovery requirement is met.
Industrial applicibility
Using the method for the invention, compared with existing Reroute techniques, reduce the requirement to network topology link circuit resource, it is to avoid the blindness of restoration route channel selecting, improve the short service recovery times of success rate , Shrink of business recovery.Its particular advantage is that the source node of faulty link is when carrying out restoration route calculating, it is not necessary to wait routing database to update, and the time efficiency of recovery is high;The source node of faulty link is able to know that faulty link information when carrying out restoration route channel selecting and avoids faulty link, and the success rate of recovery is high.Method of the present invention is applied to any complex network, meet it is quick it is extensive-require again while can save the network bandwidth.
Claims (1)
- Claims1st, the implementation method of the quick heavy-route of a kind of ASON, it is characterised in that comprise the following steps:(1) each network element detects the alert situation of all links of this network element in real time in network, when certain network element detects relevant link failure, into step(2) ;(2) service connection carried on the failed link that network element search is broken down, if carrying service connection, into step(3 ) ;(3) network element successively to service connection source endpoint network element send comprising failed link information-signaling message;(4) the source endpoint network element of service connection detects service failure and received after the signaling message comprising failed link information, according to recovery policy, using this network element as source, using business purpose network element as place, a restoration route is recalculated, if success, into step(5);(5) the source endpoint network element of service connection starts the signaling procedure of restoration route foundation.2nd, the method as described in claim 1, it is characterised in that the step(1) further wrap ' include:If each network element is not detected by this network element relevant link failure, continue to detect the alert situation of all links of this network element.3rd, the method as described in claim 1, it is characterised in that the step(2) further comprise:If service connection, return to step are not carried on the failed link(1 ) .4th, the method as described in claim 1, it is characterised in that the step(4) further comprise:If it is unsuccessful to recalculate a restoration route, return to step(1 ) .5th, the method as described in claim 1, it is characterised in that each network element all includes Link resource manager, connection controller, path control deivce and protocol controller, wherein:The Link resource manager for detecting the network element of link failure completes detection and the management function of chain circuit alarming, and is responsible for notifying link failure information by the protocol controller of this network element the connection controller of the source endpoint network element of service connection;The connection controller of source endpoint network element is inquired about according to recovery policy to the path control deivce of this network element Restoration route, the Check that the path control deivce of source endpoint network element receives connection controller is ask after request, calculate restoration route, and result of calculation is returned to connection controller, the router-level topology result that the connection controller of source endpoint network element is returned according to path control deivce starts the signaling procedure that restoration route is set up.6th, the method as described in claim 1, it is characterised in that step(4) recovery policy described in is to repel failure route.7th, the method as described in claim 1, it is characterised in that step(4) recovery policy described in is to repel the network element node at faulty link two ends.8th, the method as described in claim 1, it is characterised in that step(4) recovery policy described in is to repel the relevant link for having identical sharing memory with faulty link.
Applications Claiming Priority (1)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
PCT/CN2005/002134 WO2007065301A1 (en) | 2005-12-09 | 2005-12-09 | A fast rerouting method for automatically exchanging optical network |
Publications (1)
Publication Number | Publication Date |
---|---|
CN101248630A true CN101248630A (en) | 2008-08-20 |
Family
ID=38122459
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
CNA2005800513798A Pending CN101248630A (en) | 2005-12-09 | 2005-12-09 | Method for implementing automatic exchange optical network fast heavy route |
Country Status (2)
Country | Link |
---|---|
CN (1) | CN101248630A (en) |
WO (1) | WO2007065301A1 (en) |
Cited By (2)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
WO2010145497A1 (en) * | 2009-06-17 | 2010-12-23 | 中兴通讯股份有限公司 | Method and device for protecting service based on automatic switched optical network |
CN113365165A (en) * | 2021-06-22 | 2021-09-07 | 烽火通信科技股份有限公司 | Method and equipment for dynamically switching transport network rerouting service |
Families Citing this family (3)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN101645847A (en) | 2009-08-25 | 2010-02-10 | 中兴通讯股份有限公司 | Method and system for improving service resumption speed in transmission network |
CN107579868B (en) * | 2016-07-04 | 2023-05-23 | 中兴通讯股份有限公司 | Method and device for detecting service affected by network element failure |
CN113727221B (en) * | 2021-08-13 | 2023-06-23 | 烽火通信科技股份有限公司 | Intelligent control method, device and system for optical network |
Family Cites Families (4)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
JP3705222B2 (en) * | 2002-02-06 | 2005-10-12 | 日本電気株式会社 | Path setting method, communication network using the same, and node device |
US7525907B2 (en) * | 2002-07-05 | 2009-04-28 | Nortel Networks Limited | Method, device and software for establishing protection paths on demand and revertive protection switching in a communications network |
CN1331363C (en) * | 2002-11-27 | 2007-08-08 | 华为技术有限公司 | Rerouting method based on network entrance node |
KR100462408B1 (en) * | 2002-12-10 | 2004-12-17 | 한국전자통신연구원 | A Fast Re-route Method Using GMPLS in Optical Transport Networks |
-
2005
- 2005-12-09 WO PCT/CN2005/002134 patent/WO2007065301A1/en active Application Filing
- 2005-12-09 CN CNA2005800513798A patent/CN101248630A/en active Pending
Cited By (3)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
WO2010145497A1 (en) * | 2009-06-17 | 2010-12-23 | 中兴通讯股份有限公司 | Method and device for protecting service based on automatic switched optical network |
CN113365165A (en) * | 2021-06-22 | 2021-09-07 | 烽火通信科技股份有限公司 | Method and equipment for dynamically switching transport network rerouting service |
CN113365165B (en) * | 2021-06-22 | 2022-07-08 | 烽火通信科技股份有限公司 | Method and equipment for dynamically switching transport network rerouting service |
Also Published As
Publication number | Publication date |
---|---|
WO2007065301A1 (en) | 2007-06-14 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
CN1866806B (en) | Method for realizing shared grid network recovery | |
EP1845656B1 (en) | A method for implementing master and backup transmission path | |
JP5062058B2 (en) | Node device and route setting method | |
US7652983B1 (en) | Method for restoration and normalization in a mesh network | |
CN100555922C (en) | A kind of method that realizes the grid network business recovery | |
US20040109687A1 (en) | Fast rerouting method through generalized multi-protocol label switching | |
US8289843B2 (en) | Service failure recovery method and system | |
CN101286892B (en) | Device and method for service recovery | |
US7525907B2 (en) | Method, device and software for establishing protection paths on demand and revertive protection switching in a communications network | |
US20040107382A1 (en) | Method for network layer restoration using spare interfaces connected to a reconfigurable transport network | |
US20030095500A1 (en) | Methods for distributed shared mesh restoration for optical networks | |
CN101176303A (en) | Service rearranging method and network node | |
JP2003298633A (en) | Transmission equipment having data channel fault informing function in the case of control channel fault | |
US9007890B2 (en) | Restoring aggregated circuits with circuit integrity checks in a hierarchical network | |
US20100128611A1 (en) | Transmitting apparatus, alarm control method, and computer product | |
WO2008040253A1 (en) | A method for processing the resource information of the traffic engineering link | |
US20040073700A1 (en) | Method and apparatus for restoring a network | |
WO2008119294A1 (en) | Method and equipment for restoring network business | |
CN100531092C (en) | Intelligent optical network business re-routing trigging method | |
CN101248630A (en) | Method for implementing automatic exchange optical network fast heavy route | |
WO2012071909A1 (en) | Method and device for service recovery | |
CN100382534C (en) | Method for detecting exchange failure of intelligent optical network dual-direction multi-plexing section loop network protection | |
Asthana et al. | Protection and restoration in optical networks | |
CN101138197A (en) | Fast recovery method of automatic exchange optical network | |
CN101155133B (en) | Processing method for information of flux project periodic line |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
C06 | Publication | ||
PB01 | Publication | ||
C10 | Entry into substantive examination | ||
SE01 | Entry into force of request for substantive examination | ||
C12 | Rejection of a patent application after its publication | ||
RJ01 | Rejection of invention patent application after publication |
Open date: 20080820 |