CN101094049A - Smoothing restarting method and neighbor devices - Google Patents
Smoothing restarting method and neighbor devices Download PDFInfo
- Publication number
- CN101094049A CN101094049A CN 200710119219 CN200710119219A CN101094049A CN 101094049 A CN101094049 A CN 101094049A CN 200710119219 CN200710119219 CN 200710119219 CN 200710119219 A CN200710119219 A CN 200710119219A CN 101094049 A CN101094049 A CN 101094049A
- Authority
- CN
- China
- Prior art keywords
- timer
- neighbor device
- equipment
- recovery
- list item
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Granted
Links
Images
Landscapes
- Small-Scale Networks (AREA)
- Data Exchanges In Wide-Area Networks (AREA)
Abstract
When the neighbor device tests and finds that the conversation with restart device is broken, the reconnect timer (RT) is started. When the neighbor device tests and finds that it is under the Operational state and RT is not overtime, RT is shut and a recovery timer is started. The neighbor device and the restarting device begin to recover the transferring items, used for keeping the flux. This invention prevents the flux from interrupting in the GR process. It also avoids the concurrence of several Recovery timers. All this raises the GR effectivity.
Description
Technical field
The present invention relates to data communication technology field, be specifically related to smooth restarting method and neighbor device.
Background technology
Smooth restarting (GR, Graceful Restart) refers to when agreement is restarted and to guarantee that data forwarding normally carries out, and guarantees that key business do not interrupt.The GR technology belongs to a kind of of high reliability technology.GR is a kind of redundancy fault-tolerant technology, has been widely used in active and standby switching and system upgrade aspect at present, to guarantee the uninterrupted forwarding of key business.
At present, support the multiprotocol label switching (mpls) agreement of GR to comprise: tag distribution protocol (LDP) and resource reservation protocol (rsvp).This two agreement increases the parameter relevant with GR in the initial message of agreement when supporting GR, mutual when these parameters are set up session between router, the carrying out that is used to help GR.
With LDP is example, and existing LDP GR process is described, and as shown in Figure 1, its concrete steps are as follows:
Step 101: active and standby switching takes place promptly in device A: switch to standby plate from main board, with the LDP session disconnection of neighbor device B.
Step 102: neighbor device B detects with the LDP session of device A and disconnects, and determines that device A restarts, and neighbor device B enters the GR state, starts simultaneously to reconnect (Reconnect) timer.
Each equipment can send hello message and KeepAlive message by regularly peripherad neighbor device, if neighbor device B does not receive hello message or the KeepAlive message that device A is sent in scheduled duration, then can determine to disconnect with the LDP session of device A.
Before the timing length of Reconnect timer is device A generation masterslave switchover, when setting up the LDP session with neighbor device B, device A sends to the Reconnect Timeout that carries in the initial message of neighbor device B and the smaller among the local Neighbor Liveness Timeout.
Smaller from startup Reconnect timer to duration the initial message of receiving device A and local Neighbor Liveness Timeout.
Step 103: neighbor device B searches label forwarding equivalence class (FEC, the Forwarding Equivalence Class) binding relationship of device A at the control plane of self, and makes aging mark on this label F EC binding relationship.
Become mapping relations between the MPLS forwarding-table item on label F EC binding relationship on the control plane and the Forwarding plane.Neighbor device B can continue to use MPLS forwarding-table item converting flow corresponding with this label F EC binding relationship on the Forwarding plane after making aging mark on the label F EC of the device A binding relationship.
Before active and standby switching took place device A, neighbor device B and device A can interactive tag FEC binding relationships when setting up session.
Step 104: device A is finished active and standby switching promptly: switched to standby plate from main board, started MPLS Forwarding State Holding timer, and all be labeled as all the MPLS forwarding-table items on self Forwarding plane aging.
Step 105: device A is found neighbor device B by Hello message, set up transmission control protocol (TCP with neighbor device B, Transfer Control Protocol) connects, foundation finishes, send the initial message that has FT Session TLV to neighbor device B, this message is carried and is recovered duration (Recovery timeout).
Step 106: neighbor device B is before the Reconnect timer expiry, receive the initial message that device A is sent, determine to set up with the session of device A, stop the Reconnect timer, and starting recovery (Recovery) timer, the timing length of Recovery timer is Recovery Timeout.
If neighbor device B does not receive the initial message that device A is sent when the Reconnect timer expiry, then delete the label F EC binding relationship of having made aging mark on self control plane, delete simultaneously on the Forwarding plane and the corresponding MPLS forwarding-table item of described label F EC binding relationship, and withdrawing from the GR state, this flow process finishes.
Step 107: neighbor device B is carried at the described label F EC binding relationship of having made aging mark and sends to device A in the label mapping message; Simultaneously, device A according to done aging mark and from as outlet LSR (LSR, MPLS forwarding-table item Label Switch Router), corresponding with neighbor device B generates label F EC binding relationship, this label F EC binding relationship is carried at sends to neighbor device B in the label mapping message.
Step 108: device A is received the label mapping message that neighbor device B sends, the label F EC binding relationship that carries in this message is saved in control plane, generate the MPLS forwarding-table item according to this label F EC binding relationship simultaneously, in Forwarding plane, search the MPLS forwarding-table item of this generation, if find, then with the aging tag delete on this MPLS forwarding-table item on the Forwarding plane; If do not find, the MPLS forwarding-table item that then will generate is saved on the Forwarding plane.
Step 109: neighbor device B receives the label mapping message that device A is sent, and searches the label F EC binding relationship that this message is carried on control plane, if find, then with the aging tag delete on this label F EC binding relationship on the control plane; If do not find, then this label F EC binding relationship is saved on the control plane, and generates the MPLS forwarding-table item according to this label F EC binding relationship, the MPLS forwarding-table item of this generation is saved on the Forwarding plane.
When MPLS Forwarding State Holding timer expiry, device A can will still be labeled as aging MPLS forwarding-table item deletion.When the Recovery timer expiry, the label F EC binding relationship deletion that neighbor device B can be will still be labeled as aging is deleted on the Forwarding plane and the corresponding MPLS forwarding-table item of this label F EC binding relationship simultaneously.
From flow process shown in Figure 1 as can be seen, the LDP GR period concerning restarting device A, is the timing length of MPLSForwarding State Holding timer; Concerning neighbor device B, be Reconnect timer timing length+Recovery timer timing length.And, the end point of Reconnect timer and the start-up point of Recovery timer are arranged on first initial message place, when restarting equipment A sends initial message, Recovery timeout among the FT Session TLV is made as the residue time-out time of current MPLS Forwarding State Holding timer, like this, neighbor device B just knows when restarting equipment B can finish LDP GR process when receiving initial message, be convenient to keep the LDP GR process unanimity of two equipment.
Above-mentioned with the processing mode of initial message as the start-up point of the end point of Reconnect timer and Recovery timer, can guarantee that under desirable network state flow does not interrupt, after the ideal network state here referred to and receives first initial message, the LDP session can be according to RFC[3036] in the session state transfer figure that describes normally arrive the Operational state.
Fig. 2 has provided RFC[3036] the middle session state transfer figure that defines, from Fig. 2, can clearly see, the transition process from initialization (Initialized) state to operation (Operational) state, might return back to and do not have (Non Existent) state.If neighbor device B is after receiving first initial message, before session arrives the Operational state,, return back to the NonExistent state because of certain reason.Then this moment, the Recovery timer starts, and the Recovery timer has only and overtimely just can stop.In this case, if neighbor device B thinks that network does not keep the MPLS forwarding-table item unusually, then flow will interrupt, and so just reduces the validity of GR; And if neighbor device B continues to keep the MPLS forwarding-table item, so, in the session process of reconstruction, should enable the Reconnect timer, after receiving initial message, enable the Recovery timer again, and the Recovery timer that a preceding session is rebuild has also started, there are two Recovery timers simultaneously, can cause LDPGR process confusion, this moment is if determine the duration of GR process according to the Recovery timer of preceding session reconstruction, then can cause the GR process to finish in advance, may cause forwarding-table item to be deleted by mistake, thereby reduce the validity of GR.
Summary of the invention
The invention provides a kind of GR method and a kind of neighbor device, to improve the validity of GR.
Technical scheme of the present invention is achieved in that
A kind of GR method comprises:
Neighbor device detects the session disconnection with restarting equipment, starts the Reconnect timer; Neighbor device detects and self enters the Operational state and the Reconnect timer is not overtime, then closes the Reconnect timer, and starts the Recovery timer, and neighbor device and restarting equipment are used to keep the recovery of forwarding of flow list item.
Described neighbor device further comprises after starting the Reconnect timer: neighbor device is received the initial message that restarting equipment is sent, and picks up counting, and writes down the Recovery timeout that this message is carried;
And, neighbor device detects and self enters Operational state and Reconnect timer and further comprise not overtime the time: neighbor device calculates the difference of described Recovery timeout and present timing value, with the timing length of this difference as the Recovery timer.
Described neighbor device further comprises after starting the Reconnect timer: neighbor device detects the Reconnect timer expiry and self does not enter the Operational state, then deletes the forwarding-table item of self preserving corresponding with restarting equipment.
A kind of neighbor device comprises:
The session detection module detects with the session of restarting equipment and disconnects, and starts the Reconnect timer;
The list item maintenance module when this equipment of detecting enters the Operational state and the Reconnect timer is not overtime, is closed the Reconnect timer, and starts the Recovery timer, recovers module to list item and sends and recover indication;
List item recovers module, receives to recover indication, and beginning is carried out forwarding-table item recovery process with restarting equipment.
This neighbor device further comprises:
Module is set up in session, receives the initial message that restarting equipment is sent, and the Recoverytimeout that this message is carried sends to the list item maintenance module;
And, described list item recovers module when receiving described Recovery timeout, pick up counting, and enter the Operational state and the Reconnect timer is not overtime at this equipment of detecting, calculate the difference of described Recovery timeout and present timing value, with the timing length of this difference as the Recovery timer.
This neighbor device further comprises: the list item removing module, receive the deletion indication, and delete forwarding-table item corresponding on this equipment with restarting equipment, and,
Described list item maintenance module detects the Reconnect timer expiry and this equipment does not enter the Operational state, then sends described deletion indication to the list item removing module.
Compared with prior art, the present invention detects when disconnecting with the session of restarting equipment at neighbor device, starts the Reconnect timer; Detect at neighbor device and self to enter the Operational state and the Reconnect timer is not overtime, close the Reconnect timer, and start the Recovery timer.The present invention has taken into account the processing under network normal condition and the abnormality, eliminated the processing blind spot of prior art under the network abnormality, avoided the generation of flow interrupt situation in the GR process, also avoided existing simultaneously the situation of a plurality of Recovery timers, the situation of having avoided the chaotic caused forwarding-table item of GR process by mistake to be deleted has improved the validity of GR.
Description of drawings
Fig. 1 is the existing flow chart that carries out LDR GR;
Fig. 2 is RFC[3036] the middle session state transfer figure that defines;
The flow chart that carries out LDP GR that Fig. 3 provides for the embodiment of the invention;
The structural representation of the neighbor device that carries out LDP GR that Fig. 4 provides for the embodiment of the invention.
Embodiment
The present invention is further described in more detail below in conjunction with drawings and the specific embodiments.
Fig. 3 is the flow chart that carries out LDP GR that the embodiment of the invention provides, and as shown in Figure 3, its concrete steps are as follows:
Step 301: active and standby switching takes place promptly in device A: switch to standby plate from main board, with the LDP session disconnection of neighbor device B.
Step 302: neighbor device B detects with the LDP session of device A and disconnects, and determines that device A restarts, and neighbor device B enters the GR state, starts the Reconnect timer simultaneously.
Before the timing length of Reconnect timer is device A generation masterslave switchover, when setting up the LDP session with neighbor device B, device A sends to the Reconnect Timeout that carries in the initial message of neighbor device B and the smaller among the local Neighbor Liveness Timeout.
Step 303: neighbor device B searches the label F EC binding relationship of device A at the control plane of self, and makes aging mark on this label F EC binding relationship.
Step 304: device A is finished active and standby switching promptly: switched to standby plate from main board, started MPLS Forwarding State Holding timer, and all be labeled as all the MPLS forwarding-table items on self Forwarding plane aging.
Step 305: device A is found neighbor device B by Hello message, sets up TCP with neighbor device B and is connected, and foundation finishes, and sends initial message to neighbor device B, and this message is carried Recoverytimeout.
Set up in the process in session, masters can be to sending first initial message to method, apparatus, and in this step, set device A is a masters.If neighbor device B is a masters, then neighbor device B can send first initial message to device A, after device A is received this initial message, sends initial message to neighbor device B.
Step 306: neighbor device B receives the initial message that device A is sent, and preserves the Recovery timeout that this message is carried, and starts timer.
Step 307: neighbor device B detects and self enters the Operational state and the Reconnect timer is not overtime, then close the Reconnect timer, start the Recovery timer, the timing length of Recovery timer equals the difference of the clocking value of Recovery Timeout and timer.
For neighbor device, when the Reconnect timer is not overtime, if the unusual condition of Non Existent state has taken place to return back to from the Initialized state in neighbor device, then still allowing to carry out between restarting equipment and the neighbor device session rebuilds, simultaneously, neighbor device can not deleted MPLS forwarding-table item corresponding with device A on the Forwarding plane yet, thereby flow can not interrupt.
If neighbor device B does not enter the Operational state yet when the Reconnect timer expiry, the above has made the label F EC binding relationship of aging mark then to delete self control plane, and on the deletion Forwarding plane with the corresponding MPLS forwarding-table item of described label F EC binding relationship, and withdrawing from the GR state, this flow process finishes.
Step 308: neighbor device B is carried at the label F EC binding relationship of self having made aging mark and sends to device A in the label mapping message; Simultaneously, device A according to self done aging mark and from generate label F EC binding relationship as egress LSR and corresponding MPLS forwarding-table item with neighbor device B, this label F EC binding relationship is carried at sends to neighbor device B in the label mapping message.
Step 309: device A is received the label mapping message that neighbor device B sends, the label F EC binding relationship that carries in this message is saved in control plane, generate the MPLS forwarding-table item according to this label F EC binding relationship simultaneously, in Forwarding plane, search the MPLS forwarding-table item identical with the MPLS forwarding-table item of this generation, if find, then with the aging tag delete on this MPLS forwarding-table item on the Forwarding plane; If do not find, the MPLS forwarding-table item that then will generate is saved on the Forwarding plane.
Step 310: neighbor device B receives the label mapping message that device A is sent, and searches the label F EC binding relationship that this message is carried on control plane, if find, then with the aging tag delete on this label F EC binding relationship on the control plane; If do not find, then this label F EC binding relationship is saved on the control plane, and generates the MPLS forwarding-table item according to this label F EC binding relationship, the MPLS forwarding-table item of this generation is saved on the Forwarding plane.
When MPLS Forwarding State Holding timer expiry, device A can will still be labeled as aging MPLS forwarding-table item deletion.When the Recovery timer expiry, the label F EC binding relationship deletion that neighbor device B can be will still be labeled as aging is deleted on the Forwarding plane and the corresponding MPLS forwarding-table item of this label F EC binding relationship simultaneously.
From flow process shown in Figure 3 as can be seen, only when neighbor device B enters the Operational state, just close the Reconnect timer and start the Recovery timer, like this, if before the Reconnect timer expiry, the unusual condition of Non Existent state has taken place to return back to from the Initialized state in neighbor device B, then do not start owing to the Recovery timer, neighbor device just can not think that network is unusual, and the MPLS forwarding-table item can not deleted by mistake yet, and flow can not interrupt; Simultaneously, because neighbor device only can enter the Operational state once, therefore can not produce two situations that the Recovery timer is enabled simultaneously of existence, thereby the MPLS forwarding-table item can not deleted by mistake yet yet.
The structural representation of the neighbor device that carries out LDP GR that Fig. 4 provides for the embodiment of the invention, as shown in Figure 4, it mainly comprises: module 42, list item maintenance module 43, list item recovery module 44, list item removing module 45, Reconnect timer 46 and Recovery timer 47 are set up in session detection module 41, session, wherein:
Session detection module 41: the LDP session that detects this equipment and restarting equipment A disconnects, and makes aging mark on the label F EC binding relationship corresponding with restarting equipment A that this equipment is preserved, and startup Reconnect timer 46.
List item maintenance module 43: receive session and set up the Recovery Timeout that module 42 is sent, preserve this Recovery Timeout and pick up counting, this equipment enters the Operational state and Reconnect timer 46 is not overtime as if detecting, then calculate the difference of the clocking value of Recovery Timeout and timer, with the timing length of this difference as Recovery timer 47, start Recovery timer 47, and recover module 44 transmissions to list item and recover indication; Do not enter the Operational state if detect overtime and this equipment of Reconnect timer 46, then send the deletion indication to list item removing module 45.
List item recovers module 44: receive the recovery indication that list item maintenance module 43 is sent, the label F EC binding relationship of making aging mark that this equipment is preserved is carried at and sends to restarting equipment A in the label mapping message; Receive the label mapping message that restarting equipment A sends, on the control plane of this equipment, search the label F EC binding relationship that this message is carried, if find, the aging mark on this label F EC binding relationship on the deleting control plane then; Otherwise, this label F EC binding relationship is saved on the control plane of this equipment.
List item removing module 45: receive the deletion indication that list item maintenance module 43 is sent, will do on this Equipment Control plane all label F EC binding relationships deletions corresponding of aging mark with restarting equipment A, and delete on this device forwards plane and the corresponding MPLS forwarding-table item of described label F EC binding relationship.
The above only is process of the present invention and method embodiment, in order to restriction the present invention, all any modifications of being made within the spirit and principles in the present invention, is not equal to replacement, improvement etc., all should be included within protection scope of the present invention.
Claims (6)
1, a kind of smooth restarting GR method is characterized in that, comprising:
Neighbor device detects the session disconnection with restarting equipment, starts to reconnect timer; Neighbor device detects and self enters running status and reconnect timer not overtime, then closes and reconnects timer, and start and recover timer, and neighbor device and restarting equipment are used to keep the recovery of forwarding of flow list item.
2, the method for claim 1 is characterized in that, described neighbor device startup further comprises after reconnecting timer: neighbor device is received the initial message that restarting equipment is sent, and picks up counting, and writes down the recovery duration that this message is carried;
And neighbor device detects self to enter running status and reconnect timer and further comprises not overtime the time: neighbor device calculates the difference of described recovery duration and present timing value, with this difference as the timing length that recovers timer.
3, method as claimed in claim 1 or 2, it is characterized in that, described neighbor device starts and further comprises after reconnecting timer: neighbor device detects and reconnects timer expiry and self does not enter running status, then deletes the forwarding-table item of self preserving corresponding with restarting equipment.
4, a kind of neighbor device is characterized in that, comprising:
The session detection module detects with the session of restarting equipment and disconnects, and starts to reconnect timer;
The list item maintenance module when this equipment of detecting enters running status and reconnect timer not overtime, is closed and is reconnected timer, and starts and recover timer, recovers module to list item and sends and recover indication;
List item recovers module, receives to recover indication, and beginning is carried out forwarding-table item recovery process with restarting equipment.
5, neighbor device as claimed in claim 4 is characterized in that, this neighbor device further comprises:
Module is set up in session, receives the initial message that restarting equipment is sent, and the recovery duration that this message is carried sends to the list item maintenance module;
And, described list item recovers module when receiving described recovery duration, picks up counting, and enters running status and reconnect timer not overtime at this equipment of detecting, calculate the difference of described recovery duration and present timing value, with the timing length of this difference as the recovery timer.
6, as claim 4 or 5 described neighbor devices, it is characterized in that this neighbor device further comprises: the list item removing module, receive the deletion indication, delete forwarding-table item corresponding on this equipment with restarting equipment, and,
Described list item maintenance module detects and reconnects timer expiry and this equipment does not enter running status, then sends described deletion indication to the list item removing module.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN2007101192193A CN101094049B (en) | 2007-07-18 | 2007-07-18 | Smoothing restarting method and neighbor devices |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN2007101192193A CN101094049B (en) | 2007-07-18 | 2007-07-18 | Smoothing restarting method and neighbor devices |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN101094049A true CN101094049A (en) | 2007-12-26 |
| CN101094049B CN101094049B (en) | 2010-09-01 |
Family
ID=38992105
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN2007101192193A Active CN101094049B (en) | 2007-07-18 | 2007-07-18 | Smoothing restarting method and neighbor devices |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN101094049B (en) |
Cited By (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| WO2010102560A1 (en) * | 2009-03-10 | 2010-09-16 | 华为技术有限公司 | Method, device and system for exiting graceful restart |
| CN102098210A (en) * | 2009-12-15 | 2011-06-15 | 中兴通讯股份有限公司 | Method and device for recovering multiple label switch paths (LSPs) under tunnel in process of resource reservation protocol graceful restart (RSVP GR) |
| CN105656651A (en) * | 2014-11-13 | 2016-06-08 | 中兴通讯股份有限公司 | Method and device for deleting graceful restart (GR) function |
| CN113709042A (en) * | 2021-08-20 | 2021-11-26 | 深圳市风云实业有限公司 | Tunnel state recovery method and device in RSVP GR process |
Family Cites Families (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US7130304B1 (en) * | 2002-05-31 | 2006-10-31 | Redback Networks Inc. | Method and apparatus for graceful restart |
| CN1980224A (en) * | 2005-12-01 | 2007-06-13 | 华为技术有限公司 | Method and system for recovering business after apparatus state switching-over based on main and spare netgate |
-
2007
- 2007-07-18 CN CN2007101192193A patent/CN101094049B/en active Active
Cited By (7)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| WO2010102560A1 (en) * | 2009-03-10 | 2010-09-16 | 华为技术有限公司 | Method, device and system for exiting graceful restart |
| CN102098210A (en) * | 2009-12-15 | 2011-06-15 | 中兴通讯股份有限公司 | Method and device for recovering multiple label switch paths (LSPs) under tunnel in process of resource reservation protocol graceful restart (RSVP GR) |
| CN102098210B (en) * | 2009-12-15 | 2014-07-02 | 中兴通讯股份有限公司 | Method and device for recovering multiple label switch paths (LSPs) under tunnel in process of resource reservation protocol graceful restart (RSVP GR) |
| CN105656651A (en) * | 2014-11-13 | 2016-06-08 | 中兴通讯股份有限公司 | Method and device for deleting graceful restart (GR) function |
| CN105656651B (en) * | 2014-11-13 | 2020-12-04 | 中兴通讯股份有限公司 | Method and equipment for deleting GR function |
| CN113709042A (en) * | 2021-08-20 | 2021-11-26 | 深圳市风云实业有限公司 | Tunnel state recovery method and device in RSVP GR process |
| CN113709042B (en) * | 2021-08-20 | 2022-11-01 | 深圳市风云实业有限公司 | Tunnel state recovery method and device in RSVP GR process |
Also Published As
| Publication number | Publication date |
|---|---|
| CN101094049B (en) | 2010-09-01 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN103744809A (en) | Method for dual-computer hot-standby of vehicle information management system on basis of VRRP | |
| CN100558055C (en) | Reduce the method and the router of continuous duration of error smoothness rebooting status | |
| CN102098201B (en) | Method for realizing L2TP user access backup and network system | |
| CN101895437B (en) | Method and equipment of distributed bidirectional forwarding detection (BFD) | |
| CN101043370B (en) | Communication connection control systems and methods | |
| CN101355515B (en) | Method for restarting link aggregation control protocol with elegance | |
| US20130238738A1 (en) | Distributed method and system for implementing link aggregation control protocol (lacp) standard state machines | |
| CN101373990B (en) | Method and apparatus for link backup | |
| CN103780407A (en) | Gateway dynamic switching method and apparatus in distributed resilient network interconnection (DRNI) | |
| CN101094049B (en) | Smoothing restarting method and neighbor devices | |
| CN102045332A (en) | Method for processing control message in intelligent resilient framework and line card boards | |
| CN100388721C (en) | Method for protecting coupling based on flow control transfer protocol | |
| CN103825817A (en) | Achieving method and device of ceaseless routing after routing protocol restarting | |
| WO2013097366A1 (en) | Method for exception recovery of link aggregation and switching device | |
| CN100579076C (en) | Neighbourhood establishing method and router | |
| US10037253B2 (en) | Fault handling methods in a home service system, and associated household appliances and servers | |
| CN101931550B (en) | Method and device for synchronizing main and standby main control boards | |
| CN105450422A (en) | Wireless access point fault remote automatic recovery system based on access controller and POE switch | |
| CN101505277B (en) | Method, equipment and system for withdrawing from elegant restart | |
| WO2006053499A1 (en) | A method for detecting and resuming maintenance link | |
| US8935564B2 (en) | Method for backing up user information and apparatus in standby service node for backing up user information | |
| CN101645768B (en) | Router and main/standby switch method thereof | |
| CN101420378A (en) | Optimum restart implementing apparatus and method under resource reservation protocol flow engineering | |
| CN101582802B (en) | Operation maintenance system and method of network access device | |
| CN102983997A (en) | Method and device for migrating master services |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| C06 | Publication | ||
| PB01 | Publication | ||
| C10 | Entry into substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| C14 | Grant of patent or utility model | ||
| GR01 | Patent grant | ||
| CP03 | Change of name, title or address | ||
| CP03 | Change of name, title or address |
Address after: 310052 Binjiang District Changhe Road, Zhejiang, China, No. 466, No. Patentee after: Xinhua three Technology Co., Ltd. Address before: 310053 Hangzhou hi tech Industrial Development Zone, Zhejiang province science and Technology Industrial Park, No. 310 and No. six road, HUAWEI, Hangzhou production base Patentee before: Huasan Communication Technology Co., Ltd. |