CN105281953A

CN105281953A - Network fault handling method and provider edge routers (PEs)

Info

Publication number: CN105281953A
Application number: CN201510684402.2A
Authority: CN
Inventors: 郑俊敏
Original assignee: Beijing Star Net Ruijie Networks Co Ltd
Current assignee: Beijing Star Net Ruijie Networks Co Ltd
Priority date: 2015-10-20
Filing date: 2015-10-20
Publication date: 2016-01-27
Anticipated expiration: 2035-10-20
Also published as: CN105281953B

Abstract

The invention provides a network fault handling method and provider edge routers (PEs). The network fault handling method comprises the following steps that: a first PE sends an MDT-Join (Multicast Distribution Tree-Join) message to a second PE within a preset range, and judges whether a first message sent by the second PE is received or not within a preset time, wherein the first message is a message sent by the second PE after a failure in creating a de-encapsulation table of the received MDT-Join message; and if so, the first PE stops switching from Default-MDT (Default-Multicast Distribution Tree) to Data-MDT (Data-Multicast Distribution Tree). Through adoption of the network fault handling method and the PEs, the problem of cutoff of customer multicast streams in the prior art can be solved.

Description

The edge device of network failure processing method and service provider

Technical field

The present invention relates to communication technical field, be specifically related to the edge device of a kind of network failure processing method and service provider.

Background technology

VPN (virtual private network) (VirtualPrivateNetwork is called for short VPN) refers to without the need to setting up special physical link, for user provides ad-hoc networks in common network.VPN is by the core router (ProviderRouter of service provider network, be called for short P), the edge device (ProviderEdgeRouter of service provider, be called for short PE) and the edge device (CustomerEdgeRouter of user network, be called for short CE) composition, wherein, P equipment is connected with PE or P, and PE equipment and P equipment or CE equipment connection, CE equipment is connected with PE equipment or user network.

Multicasting VPN is a kind of based on multiprotocol label switching (Multi-ProtocolLabelSwitching, be called for short MPLS) network boundary gateway protocol (BorderGatewayProtocol, be called for short BGP) set up the technical of VPN, in VPN, propagate the technology of multicast packet.Multicasting VPN scheme popular is at present multicast domain (Multicast-Domain, be called for short MD) scheme, it is by safeguarding that for each VPN a multicast domain realizes, multicast distribution tree (the Default-MulticastDistributionTree that one default is had in each multicast domain, be called for short Default-MDT) connect PE in each territory, pass through Default-MDT, after the multicast data dissemination of CE to connected PE, this multicast packet propagates into along Default-MDT on all outlet ports PE of multicast domain.

In order to avoid the waste of public-network bandwidth, a kind of data multicast distribution tree (Data-MulticastDistributionTree is additionally provided in prior art, be called for short Data-MDT), when entry PE prepares a newly-built Data-MDT, it first creates a Data-MDT and encapsulates list item, then send a multicast packet multicast distribution tree by Default-MDT and add (MulticastDistributionTree-Join, be called for short MDT-Join) message, wherein carry the source address (Customers-Source of user multicast data flow, be called for short C-S), group address (the Customers-Group of user's group data stream, be called for short C-G), group address (Public-Group when public network is propagated, be called for short P-G) information, after outlet PE receives MDT-Join message, the outlet PE of demand is had to create a corresponding decapsulation list item to this multicast traffic stream, the public network added in MDT-Join message to public network propagates group address, pass through Data-MDT, after the multicast data dissemination of CE to connected PE, by propagate in multicast domain along Data-MDT have reception demand PE on.

But there is following problem in above-mentioned technical scheme: because outlet PE needed the decapsulation table first setting up a MDT-Join before adding MDT-Join distribution tree, when the resource of decapsulation table list item is depleted, when decapsulation table is set up unsuccessfully, entry PE is after carrying out MDT-Join switching, and outlet PE will produce the cutout of user multicast stream.Way at present for decapsulation table list item inadequate resource application failure in outlet PE is mainly applied for again by timer timing.Particularly, outlet PE is when receiving MDT-Join message, and according to the P-G information in MDT-Join message, the decapsulation table of an application Data-MDT, if decapsulation table creates successfully, adds to public network the P-G multicast group that MDT-Join message specifies; If decapsulation table creates unsuccessfully, start a delayed filing timer, when timer applies for decapsulation table again to after date.

Although above-mentioned timer timing applies for that the method creating decapsulation table can make user recover the reception of multicast traffic stream as far as possible again, before decapsulation table creates successfully, the multicast traffic stream of user's program request still can stop.

Summary of the invention

For defect of the prior art, the invention provides the edge device of a kind of network failure processing method and service provider, to solve the problem of user multicast stream cutout in prior art.

For solving the problems of the technologies described above, the invention provides following technical scheme:

First aspect, the invention provides a kind of network failure processing method, comprising:

One PE is after sending MDT-Join message to the 2nd PE in preset range, judge the first message whether receiving described 2nd PE transmission in Preset Time, described first message is the message sent after described 2nd PE creates the failure of decapsulation table according to the MDT-Join message received;

If so, then a described PE stops the switching carried out from Default-MDT to Data-MDT.

Further, described method also comprises:

If a PE does not receive the first message that described 2nd PE sends in Preset Time, then start to carry out the switching from Default-MDT to Data-MDT.

Further, a described PE, after sending MDT-Join message to the 2nd PE, judges the first message whether receiving described 2nd PE transmission in Preset Time, comprising:

One PE, after sending MDT-Join message to the 2nd PE, starts first timer;

Before arriving at described first timer the timing instant preset, judge whether a described PE receives the first message of described 2nd PE transmission.

Further, described method also comprises:

If a described PE receives the second message that described 2nd PE sends, then judge whether the 2nd PE sending described first message in described preset range has sent described second message all, if not, then a described PE stops the switching carried out from Default-MDT to Data-MDT;

Described second message is the message sent after described 2nd PE re-creates decapsulation telogenesis merit according to described MDT-Join message.

Further, described method also comprises:

If a described PE judges that the 2nd PE sending described first message in described preset range has sent described second message all, then a described PE starts to carry out the switching from Default-MDT to Data-MDT.

Second aspect, present invention also offers a kind of network failure processing method, comprising:

2nd PE, after the MDT-Join message receiving a PE transmission, creates decapsulation table according to described MDT-Join message;

If described 2nd PE creates the failure of described decapsulation table, then send the first message to a described PE,

A described PE is asked to stop the switching carrying out from Default-MDT to Data-MDT.

Further, after sending the first message to a described PE, also comprise:

Described 2nd PE re-creates decapsulation table according to described MDT-Join message;

If described 2nd PE creates described decapsulation telogenesis merit, then send the second message to a described PE, ask a described PE to start to carry out the switching from Default-MDT to Data-MDT.

The third aspect, present invention also offers the edge device of a kind of service provider, comprising:

First transmitting element, sends MDT-Join message for the edge device PE to another service provider in preset range;

First judging unit, for judging the first message whether receiving described another PE transmission in Preset Time, described first message is the message of another PE described according to transmission after the MDT-Join message establishment decapsulation table failure received;

First processing unit, during for determining the first message receiving described another PE transmission at described first judging unit, stops the switching carrying out from Default-MDT to Data-MDT.

Further, when described first processing unit also for not receiving the first message that another PE described sends in described first judging unit determination Preset Time, start to carry out the switching from Default-MDT to Data-MDT.

Further, described first judging unit, also for judging whether the second message receiving described another PE transmission, described second message is the message sent after another PE described re-creates decapsulation telogenesis merit according to described MDT-Join message;

And described equipment also comprises the second judging unit;

Described second judging unit, during for determining the second message receiving described another PE transmission at described first judging unit, judges whether another PE sending the first message in described preset range has sent the second message all;

Described first processing unit, when another PE also for determining to send in described preset range the first message at described second judging unit does not all send the second message, stops the switching carrying out from Default-MDT to Data-MDT.

Further, described first processing unit, when another PE also for determining to send in described preset range the first message at described second judging unit has sent the second message all, has started to carry out the switching from Default-MDT to Data-MDT.

Fourth aspect, present invention also offers the edge device of a kind of service provider, comprising:

Second processing unit, for after the MDT-Join message of edge device PE transmission receiving another service provider, creates decapsulation table according to described MDT-Join message;

Judging unit, for judging whether described second processing unit successfully creates described decapsulation table;

Second transmitting element, during for determining the described decapsulation table of the unsuccessful establishment of described second processing unit at described judging unit, sends the first message to another PE described, and request another PE described stops the switching carrying out from Default-MDT to Data-MDT.

Further, described second processing unit, also at described second transmitting element to after another PE described sends the first message, re-create decapsulation table according to described MDT-Join message;

Described judging unit, also whether successful for judging that described second processing unit re-creates described decapsulation table;

Described second transmitting element, time also for determining that described second processing unit re-creates described decapsulation telogenesis merit at described judging unit, send the second message to another PE described, request another PE described starts to carry out the switching from Default-MDT to Data-MDT.

As shown from the above technical solution, network failure processing method of the present invention, at a PE to after the 2nd PE in preset range sends MDT-Join message, by judging in Preset Time, whether the 2nd PE sends decapsulation table establishment failure, and then the switching whether decision is carried out from Default-MDT to Data-MDT.Particularly, after the 2nd PE creates the failure of decapsulation table, the 2nd PE can send the first message to a PE, suspends to ask a PE switching carried out from Default-MDT to Data-MDT.One PE is after receiving described first message, stop the switching carrying out from Default-MDT to Data-MDT, to avoid being switched in Data-MDT process at Default-MDT, there is the problem causing multicast traffic stream to stop because of the switching of multicast distribution tree in the 2nd PE.

Accompanying drawing explanation

In order to be illustrated more clearly in the embodiment of the present invention or technical scheme of the prior art, be briefly described to the accompanying drawing used required in embodiment or description of the prior art below, apparently, accompanying drawing in the following describes is some embodiments of the present invention, for those of ordinary skill in the art, under the prerequisite not paying creative work, other accompanying drawing can also be obtained according to these accompanying drawings.

Fig. 1 is the flow chart of a kind of network failure processing method that first embodiment of the invention provides;

Fig. 2 is the flow chart of a kind of network failure processing method that second embodiment of the invention provides;

Fig. 3 is the flow chart of a kind of network failure processing method that four embodiment of the invention provides;

Fig. 4 is the flow chart of a kind of network failure processing method that fifth embodiment of the invention provides;

Fig. 5 is multicasting VPN network design schematic diagram;

Fig. 6 is the flow chart of the another kind of network failure processing method that sixth embodiment of the invention provides;

Fig. 7 is the flow chart of the another kind of network failure processing method that seventh embodiment of the invention provides;

Fig. 8 is the flow chart of the another kind of network failure processing method that eighth embodiment of the invention provides;

Fig. 9 is the structural representation of the edge device of a kind of service provider that ninth embodiment of the invention provides;

Figure 10 is the structural representation of the edge device of a kind of service provider that eleventh embodiment of the invention provides;

Figure 11 is the structural representation of the edge device of the another kind of service provider that thirteenth embodiment of the invention provides;

Figure 12 is the structural representation of the edge device of the another kind of service provider that fifteenth embodiment of the invention provides.

Embodiment

For making the object of the embodiment of the present invention, technical scheme and advantage clearly, below in conjunction with the accompanying drawing in the embodiment of the present invention, clear, complete description is carried out to the technical scheme in the embodiment of the present invention, obviously, described embodiment is the present invention's part embodiment, instead of whole embodiments.Based on the embodiment in the present invention, those of ordinary skill in the art, not making the every other embodiment obtained under creative work prerequisite, belong to the scope of protection of the invention.

The edge device of network failure processing method provided by the invention and service provider, in order to solve in the multicast domain scheme of existing multicasting VPN, in handoff procedure from Default-MDT to Data-MDT, if outlet PE decapsulation table creates unsuccessfully, cannot join in Data-MDT distribution tree, cause the problem of the user's on-demand multicasting data flow cutout occurred.

Below the abbreviation noun occurred in embodiments of the invention and accompanying drawing is explained one by one.Wherein, VPN refers to VPN (virtual private network) VirtualPrivateNetwork, specifically refers to without the need to setting up special physical link, for user provides ad-hoc networks in common network.Wherein, P, PE, CE refer to the part of VPN.It is respectively: P refers to the core router ProviderRouter of service provider network, and PE refers to the edge device ProviderEdgeRouter of service provider, and CE refers to the edge device CustomerEdgeRouter of family network.Annexation wherein between P, PE, CE can be shown in Figure 5.Usually, P equipment is connected with PE or P, and PE equipment and P equipment or CE equipment connection, CE equipment is connected with PE equipment or user network.

Fig. 1 shows the flow chart of the network failure processing method that first embodiment of the invention provides, and see Fig. 1, the method comprises the steps:

Step 101 a: PE sends MDT-Join message to the 2nd PE in preset range.

In this step, when the Data-MDT that the private network multicast data flow that a PE receives reaches a PE setting switches threshold values, a PE creates a Data-MDT encapsulating sheet, and by the two PE transmission MDT-Join message of Default-MDT to this multicast domain.In this step, a PE can be regarded as entry PE, and the 2nd PE can be regarded as outlet PE.So-called entry PE refers to the PE being responsible for forwarding multicasting flow data in VPN multicast domain.So-called outlet PE refers to the PE receiving the multicast data flow data that entry PE forwards in VPN multicast domain.

Step 102 a: PE judges the first message whether receiving described 2nd PE transmission in Preset Time, if so, then performs step 102a.

In this step, described first message is the message sent after described 2nd PE creates the failure of decapsulation table according to the MDT-Join message received.

Wherein, the 2nd PE, after the MDT-Join message receiving a PE transmission, if do not receive demand to this multicast traffic stream, then directly abandons this MDT-Join message or does not process this MDT-Join message.If have reception demand to this multicast traffic stream, then according to the source address (Customers-Source of the user multicast data flow of carrying in MDT-Join message, be called for short C-S), group address (the Customers-Group of user's group data stream, be called for short C-G), group address (Public-Group, be called for short P-G) information creating decapsulation table when public network is propagated.When the resource of the decapsulation table list item on the 2nd PE is depleted, the 2nd PE decapsulation table will create failure.

Step 102a: the one PE stops the switching carrying out from Default-MDT to Data-MDT.

In this step, if a PE receives the first message that described 2nd PE sends in Preset Time, so prove that the 2nd PE creates the failure of decapsulation table, if a PE now starts to carry out the switching from Default-MDT to Data-MDT, so will cause the 2nd PE occur because multicast distribution tree switching and cause multicast traffic stream cutout problem.Therefore when a PE receives the first message of the 2nd PE transmission in Preset Time, a PE stops the switching carrying out from Default-MDT to Data-MDT, and now a PE continues to use Default-MDT forwarding multicasting flow data.In other embodiments of the invention, after a PE stops carrying out the switching from Default-MDT to Data-MDT, one PE is also responsible for the information that record sends the 2nd PE of described first message, judge whether the 2nd PE of transmission first message successfully creates decapsulation table for the later stage, after the 2nd PE of transmission first message all successfully creates decapsulation table, one PE starts to carry out the switching from Default-MDT to Data-MDT again, otherwise a PE does not carry out the switching from Default-MDT to Data-MDT, to ensure that the 2nd PE there will not be the problem of the multicast traffic stream cutout caused because of the switching of multicast distribution tree.

In the present embodiment, one PE is to after the 2nd PE in preset range sends MDT-Join message, by judging in Preset Time, whether the 2nd PE sends decapsulation table establishment failure, and then the switching whether decision is carried out from Default-MDT to Data-MDT.Here, the length of Preset Time can be arranged as required.

Particularly, after the 2nd PE creates the failure of decapsulation table, the 2nd PE can send the first message to a PE, suspends to ask a PE switching carried out from Default-MDT to Data-MDT.One PE is after receiving described first message, stop the switching carrying out from Default-MDT to Data-MDT, to avoid being switched in Data-MDT process at Default-MDT, there is the problem causing multicast traffic stream to stop because of the switching of multicast distribution tree in the 2nd PE.

It should be noted that, usually, because the 2nd PE can create decapsulation table immediately after receiving described MDT-Join message, if create unsuccessfully, 2nd PE can send the first message to a PE immediately, if therefore in Preset Time, a PE does not receive the first message of the 2nd PE transmission, then PE acquiescence the 2nd PE creates decapsulation telogenesis merit, and a PE carries out the switching from Default-MDT to Data-MDT automatically.

In addition, the network failure processing method described in the present embodiment, can also be applied in other network designs, and one-to-many equipment needs to carry out in the scene of Network operation mode switching controls.

In second embodiment of the invention, see Fig. 2, if in above-mentioned steps 102, a PE judges the first message not receiving described 2nd PE transmission in Preset Time, then perform following step 102b.

Step 102b: the one PE starts to carry out the switching from Default-MDT to Data-MDT.

In the present embodiment, if the 2nd PE does not send decapsulation table to a PE and creates failure in Preset Time, namely in Preset Time, a PE does not receive the first message of the 2nd PE transmission, then a PE can think that the 2nd PE creates decapsulation telogenesis merit, and therefore a PE starts to carry out the switching from Default-MDT to Data-MDT.Because the 2nd PE creates decapsulation telogenesis merit, therefore when carrying out multicast distribution tree and switching, the problem that multicast traffic stream stops can not be caused.

Wherein, the 2nd PE can add the P-G group of specifying in MDT-Join message to public network, complete adding of Data-MDT distribution tree after creating decapsulation telogenesis merit.

In third embodiment of the invention, the step 102 in above-described embodiment a: PE judges that a kind of specific implementation whether receiving the first message that described 2nd PE sends in Preset Time can be:

One PE, after sending MDT-Join message to the 2nd PE, starts first timer;

In the present embodiment, one PE is after sending MDT-Join message to the 2nd PE, the first message of the 2nd PE transmission is judged whether to receive in Preset Time by starting first timer, when first timer does not also reach default timing instant, if a PE receives the first message that the 2nd PE sends, then a PE stops the switching carried out from Default-MDT to Data-MDT.When first, device reaches default timing instant, if a PE does not also receive the first message that the 2nd PE sends, then a PE starts to carry out the switching from Default-MDT to Data-MDT.

In four embodiment of the invention, see Fig. 3, described method also comprises the steps 103-104a.

Step 103 a: PE receives the second message that described 2nd PE sends.

Step 104 a: PE judges whether the 2nd PE sending the first message in described preset range has sent the second message all, if not, then performs step 104a.

In this step, described second message is the message sent after described 2nd PE re-creates decapsulation telogenesis merit according to described MDT-Join message.

Step 104a: the one PE stops the switching carrying out from Default-MDT to Data-MDT.

In the present embodiment, one PE is after the first message receiving the 2nd PE transmission, one PE stops the switching carried out from Default-MDT to Data-MDT and waits for, after waiting for that the 2nd PE successfully creates decapsulation table, then carries out the switching from Default-MDT to Data-MDT.

Particularly, after a PE receives successful second message of decapsulation table establishment of the 2nd PE transmission, one PE starts to judge whether the 2nd PE sending the first message that decapsulation table creates unsuccessfully in described preset range has all sent decapsulation table and created successful second message, if not, then do not carry out the switching from Default-MDT to Data-MDT, but continue to wait for.Can ensure like this to be switched in Data-MDT process at Default-MDT, not have the 2nd PE to occur because the switching of multicast distribution tree and the problem that causes multicast traffic stream to stop.

In fifth embodiment of the invention, see Fig. 4, if in above-mentioned steps 104, a PE judges that the 2nd PE sending the first message in described preset range has sent described second message all, then perform following step 104b.

Step 104b: the one PE starts to carry out the switching from Default-MDT to Data-MDT.

In the present embodiment, when a PE receive the 2nd PE send decapsulation table create successful message after, one PE starts to judge whether the 2nd PE sending the first message that decapsulation table creates unsuccessfully in described preset range has all sent decapsulation table and created successful second message, if so, then start to carry out the switching from Default-MDT to Data-MDT.Thus ensure to be switched in Data-MDT process at Default-MDT, do not have the 2nd PE to occur because the switching of multicast distribution tree and the problem that causes multicast traffic stream to stop.

See Fig. 5, provide an instantiation below and the network failure processing method described in above-described embodiment explained:

S1, multicast source are connected with CE1, and the VPNA private network multicast packet that multicast source sends (192.168.1.1,225.1.1.1) flows on CE1, and this private network multicast traffic stream is forwarded on connected PE1 by CE1.

Multicast traffic stream, after receiving (192.168.1.1,225.1.1.1) multicast traffic stream, by Default-MDT, is distributed to PE2, on PE3 by S2, PE1.

Multicast data flow is transmitted to CE2 according to multicast distribution tree by (192.168.1.1,225.1.1.1) by S3, PE2, is finally transmitted to recipient; Multicast data flow is transmitted to CE3 according to multicast distribution tree by (192.168.1.1,225.1.1.1) by PE3, is finally transmitted to recipient.

S4, suppose (192.168.1.1, the flow of private network multicast traffic stream 225.1.1.1) reaches the flow threshold values of entry PE 1, PE1 will be (192.168.1.1,225.1.1.1) this private network multicast traffic stream carries out Data-MDT switching, the Data-MDT that the multicast address 239.1.1.2 that acquisition one is idle from address pool creates one (1.1.1.1.239.1.1.2) encapsulates list item, then sending C-S along Default-MDT is 192.168.1.1, the MDT-Join message of C-G to be 225.1.1.1, P-G be 239.1.1.2.

S5, the decapsulation list item resource supposed on PE2 reach the upper limit, PE2 is 192.168.1.1 at reception C-S, C-G is 225.1.1.1, P-G is after the MDT-Join message of 239.1.1.2, create (*, during Data-MDT decapsulation list item 239.1.1.2), failure, now, can not add the multicast group of 239.1.1.2 to public network.PE2, in order to avoid there is the problem that multicast traffic stream stops, sends the first message creating the failure of decapsulation table to PE1, the switching temporarily not carrying out from Default-MDT to Data-MDT to ask PE1.

S6, the decapsulation list item resource supposed on PE3 reach the upper limit, PE3 is 192.168.1.1 at reception C-S, C-G is 225.1.1.1, P-G is after the MDT-Join message of 239.1.1.2, create (*, during Data-MDT decapsulation list item 239.1.1.2), failure, now, can not add the multicast group of 239.1.1.2 to public network.PE3, in order to avoid there is the problem that multicast traffic stream stops, sends the first message creating the failure of decapsulation table to PE1, the switching temporarily not carrying out from Default-MDT to Data-MDT to ask PE1.

S7, PE4 are 192.168.1.1 receiving C-S, C-G is 225.1.1.1, P-G is after the MDT-Join message of 239.1.1.2, first set up (a *, 239.1.1.2) Data-MDT decapsulation list item, then add 239.1.1.2 multicast group to public network, complete adding of Data-MDT distribution tree.

After S8, PE1 receive the first message of described PE2 and described PE3 transmission in Preset Time, PE2 and PE3 of PE1 to transmission first message carries out record, and the switching that stopping is carried out from Default-MDT to Data-MDT, to avoid in handoff procedure, there is the problem that multicast traffic stream stops in PE2 and PE3.

S9, PE1 are after the decapsulation table receiving described PE2 transmission creates successful second message, record content before PE1 inquiry, judge whether the PE3 of transmission first message has sent the second message, if PE3 does not also send the second message, then PE1 continues the switching that stopping is carried out from Default-MDT to Data-MDT, and waits for that PE3 creates decapsulation table.

S10, when PE1 receive PE3 send the second message after, PE1 sends the first message PE2 and PE3 before judging has sent the second message all, now PE1 is by (192.168.1.1,225.1.1.1) private network multicast traffic stream is switched to Data-MDT from Default-MDT, multicast traffic stream to be distributed on PE2, PE3 and PE4 along Data-MDT thus to make the user recipient be connected with CE2, CE3, CE4 normally can receive the multicast traffic stream of (192.168.1.1,225.1.1.1) by this multicast traffic stream.

Sixth embodiment of the invention provides another kind of network failure processing method, and see Fig. 6, the method comprises the steps:

Step 201: the 2nd PE receives the MDT-Join message that a PE sends.

Step 202: the 2nd PE creates decapsulation table according to described MDT-Join message.

Step 203: whether unsuccessfully judge that the 2nd PE creates described decapsulation table, if so, then perform step 203a.

Step 203a: the two PE sends the first message to a PE, asks a described PE to stop the switching carrying out from Default-MDT to Data-MDT.

In the present embodiment, after the 2nd PE receives the MDT-Join message of a PE transmission, 2nd PE creates decapsulation table according to described MDT-Join message, if the 2nd PE creates the failure of decapsulation table, then send the first message to a PE, stop the switching carrying out from Default-MDT to Data-MDT to ask a PE, to avoid being switched in Data-MDT process at Default-MDT, occur the problem of the multicast traffic stream cutout caused because of the switching of multicast distribution tree.

In seventh embodiment of the invention, see Fig. 7, above-mentioned 6th network failure processing method described in embodiment also comprises the steps 204-205a.

Step 204: the 2nd PE re-creates decapsulation table according to described MDT-Join message.

In this step, the 2nd PE, after sending the first message to a PE, can re-create decapsulation table according to described MDT-Join message immediately, re-create decapsulation table again after preset time period of also can being separated by according to described MDT-Join message.

Step 205: whether successfully judge that the 2nd PE re-creates decapsulation table, if so, then perform step 205a.

Step 205a: the two PE sends the second message to a PE, asks a described PE to start to carry out the switching from Default-MDT to Data-MDT.

In the present embodiment, when the 2nd PE creates the failure of decapsulation table and to after a PE sends the first message, 2nd PE re-creates decapsulation table according to described MDT-Join message, if the 2nd PE creates decapsulation telogenesis merit, then send the second message to a PE, to inform that its decapsulation table of a PE creates successfully, a described PE is asked to start to carry out the switching from Default-MDT to Data-MDT.

In eighth embodiment of the invention, see Fig. 8, if in above-mentioned steps 205, the 2nd PE judges to re-create the failure of decapsulation table, then when the timing instant that each is preset arrives, repeat above-mentioned steps 204-205, until the 2nd PE creates described decapsulation telogenesis merit.

In the present embodiment, when the 2nd PE creates the failure of decapsulation table and to after a PE sends the first message, 2nd PE re-creates decapsulation table according to described MDT-Join message, if the 2nd PE re-creates the failure of decapsulation table, then at the timing instant that each is preset, 2nd PE continues to create decapsulation table according to described MDT-Join message, until the 2nd PE creates described decapsulation telogenesis merit, and sends the second message to a PE.

Ninth embodiment of the invention provides the edge device of a kind of service provider, comprises see Fig. 9:

First transmitting element 801, sends MDT-Join message for the edge device PE to another service provider in preset range;

First judging unit 802, for judging the first message whether receiving described another PE transmission in Preset Time, described first message is the message of another PE described according to transmission after the MDT-Join message establishment decapsulation table failure received;

First processing unit 803, during for determining the first message receiving described another PE transmission at described first judging unit, stops the switching carrying out from Default-MDT to Data-MDT.

At the edge device of the service provider that the present embodiment provides, by judging that the first message whether receiving described another PE transmission in Preset Time determines whether to carry out the switching from Default-MDT to Data-MDT.When receiving the first message that another PE described sends, the edge device of described service provider stops the switching carrying out from Default-MDT to Data-MDT, to avoid being switched in Data-MDT process at Default-MDT, there is the problem causing multicast traffic stream to stop because of the switching of multicast distribution tree in another PE.

In tenth embodiment of the invention, above-mentioned first processing unit 803 is also for determining the first message not receiving described another PE transmission in Preset Time during at described first judging unit 802, start to carry out the switching from Default-MDT to Data-MDT.

In the present embodiment, if the edge device of described service provider determines the first message not receiving described another PE transmission in Preset Time, then the edge device of described service provider thinks that another PE creates decapsulation telogenesis merit, and therefore the edge device of described service provider starts to carry out the switching from Default-MDT to Data-MDT.Because another PE creates decapsulation telogenesis merit, therefore when carrying out multicast distribution tree and switching, another PE there will not be the phenomenon of the multicast traffic stream cutout caused because multicast distribution tree switches.

In eleventh embodiment of the invention, described first judging unit 802, also for judging whether the second message receiving described another PE transmission, described second message is the message that another PE sending described first message sends, and described second message is the message sent after another PE described re-creates decapsulation telogenesis merit according to described MDT-Join message;

Correspondingly, see Figure 10, in the present embodiment, described equipment also comprises the second judging unit 804;

Described second judging unit 804, during for determining the second message receiving described another PE transmission at described first judging unit 802, judges whether another PE sending the first message in described preset range has sent the second message all;

Described first processing unit 803, also for when another PE that described second judging unit 804 determines to send in described preset range the first message does not all send the second message, stops the switching carrying out from Default-MDT to Data-MDT.

In the present embodiment, the edge device of described service provider is after the first message receiving another PE transmission, the edge device of described service provider stops the switching carried out from Default-MDT to Data-MDT and waits for, after waiting for that another PE described successfully creates decapsulation table, then carry out the switching from Default-MDT to Data-MDT.

Particularly, after the edge device of described service provider receives successful second message of decapsulation table establishment of another PE transmission, the edge device of described service provider starts to judge to send in described preset range another PE that decapsulation table creates the first message unsuccessfully and whether has all sent successful second message of decapsulation table establishment, if not, then do not carry out the switching from Default-MDT to Data-MDT, but continue to wait for.Can ensure like this to be switched in Data-MDT process at Default-MDT, occur the problem causing multicast traffic stream to stop because of the switching of multicast distribution tree without any another PE.

In twelveth embodiment of the invention, described first processing unit 803, also for when another PE that described second judging unit 804 determines to send in described preset range the first message has sent the second message all, start to carry out the switching from Default-MDT to Data-MDT.

In the present embodiment, when the edge device of described service provider receives after decapsulation table that another PE sends creates successful message, whether all send decapsulation table created successful second message when the edge device of described service provider starts to judge to send in described preset range another PE that decapsulation table creates the first message unsuccessfully, if so, then start to carry out the switching from Default-MDT to Data-MDT.Thus ensure to be switched in Data-MDT process at Default-MDT, do not have another PE to occur because the switching of multicast distribution tree and the problem that causes multicast traffic stream to stop.

Thirteenth embodiment of the invention provides the edge device of another kind of service provider, see Figure 11, comprising:

Second processing unit 901, for after the MDT-Join message of edge device PE transmission receiving another service provider, creates decapsulation table according to described MDT-Join message;

Judging unit 902, for judging whether described second processing unit 901 successfully creates described decapsulation table;

Second transmitting element 903, during for determining the described decapsulation table of the unsuccessful establishment of described second processing unit 901 at described judging unit 902, send the first message to another PE described, request another PE described stops the switching carrying out from Default-MDT to Data-MDT.

In the present embodiment, after the edge device of described service provider receives the MDT-Join message of another PE transmission, the edge device of described service provider creates decapsulation table according to described MDT-Join message, if the edge device of described service provider creates the failure of decapsulation table, then send the first message to another PE described, the switching carried out from Default-MDT to Data-MDT is stopped asking another PE described, to avoid being switched in Data-MDT process at Default-MDT, there is the problem of the multicast traffic stream cutout caused because of the switching of multicast distribution tree in the edge device of described service provider.

In fourteenth embodiment of the invention, described second processing unit 901, also at described second transmitting element 903 to after another PE described sends the first message, re-create decapsulation table according to described MDT-Join message;

Described judging unit 902, also whether successful for judging that described second processing unit 901 re-creates described decapsulation table;

Described second transmitting element 903, time also for determining that described second processing unit 901 re-creates described decapsulation telogenesis merit at described judging unit 902, send the second message to another PE described, request another PE described starts to carry out the switching from Default-MDT to Data-MDT.

In the present embodiment, when the edge device of described service provider creates the failure of decapsulation table and to after another PE described sends the first message, the edge device of described service provider re-creates decapsulation table according to described MDT-Join message, if the edge device of described service provider creates decapsulation telogenesis merit, then send the second message to another PE described, to inform that described its decapsulation table of another PE creates successfully, request another PE described starts to carry out the switching from Default-MDT to Data-MDT.

In fifteenth embodiment of the invention, see Figure 12, the edge device of above-mentioned 13 service provider that embodiment provides also comprises: timing unit 904;

Described timing unit 904, re-creates decapsulation table until described second processing unit 901 creates described decapsulation telogenesis merit for controlling described second processing unit 901 at each default timing instant according to described MDT-Join message.

In the present embodiment, when the edge device of described service provider creates the failure of decapsulation table and to after another PE sends the first message, the edge device of described service provider re-creates decapsulation table according to described MDT-Join message, if the edge device of described service provider re-creates the failure of decapsulation table, then at the timing instant that each is preset, the edge device of described service provider continues to create decapsulation table according to described MDT-Join message, until the edge device of described service provider creates described decapsulation telogenesis merit, and send the second message to another PE described, to inform another PE described, it creates decapsulation telogenesis merit, request another PE described starts to carry out the switching from Default-MDT to Data-MDT.

Wherein, the edge device of the service provider described in the present invention the nine to ten two embodiment may be used for performing the method described in above-mentioned the first to five embodiment, its principle and technique effect similar.In like manner, the edge device of the service provider described in the present invention the ten three to ten five embodiment may be used for performing the method described in above-mentioned six to eight embodiment, its principle and technique effect similar.All no longer describe in detail herein.

Above embodiment only for illustration of technical scheme of the present invention, is not intended to limit; Although with reference to previous embodiment to invention has been detailed description, those of ordinary skill in the art is to be understood that: it still can be modified to the technical scheme described in foregoing embodiments, or carries out equivalent replacement to wherein portion of techniques feature; And these amendments or replacement, do not make the essence of appropriate technical solution depart from the spirit and scope of various embodiments of the present invention technical scheme.

Claims

1. a network failure processing method, is characterized in that, comprising:

2. method according to claim 1, is characterized in that, also comprises:

3. method according to claim 1, is characterized in that, a described PE, after sending MDT-Join message to the 2nd PE, judges the first message whether receiving described 2nd PE transmission in Preset Time, comprising:

One PE, after sending MDT-Join message to the 2nd PE, starts first timer;

4. method according to claim 1, is characterized in that, also comprises:

5. method according to claim 4, is characterized in that, also comprises:

6. a network failure processing method, is characterized in that, comprising:

If described 2nd PE creates the failure of described decapsulation table, then send the first message to a described PE, ask a described PE to stop the switching carrying out from Default-MDT to Data-MDT.

7. method according to claim 6, is characterized in that, after sending the first message to a described PE, also comprises:

8. a service provider's edge device, is characterized in that, comprising:

9. equipment according to claim 8, it is characterized in that, when described first processing unit also for not receiving the first message that another PE described sends in described first judging unit determination Preset Time, start to carry out the switching from Default-MDT to Data-MDT.

10. equipment according to claim 8, it is characterized in that, described first judging unit, also for judging whether the second message receiving described another PE transmission, described second message is the message sent after another PE described re-creates decapsulation telogenesis merit according to described MDT-Join message;

And described equipment also comprises the second judging unit;

11. equipment according to claim 10, it is characterized in that, described first processing unit, when another PE also for determining to send in described preset range the first message at described second judging unit has sent the second message all, has started to carry out the switching from Default-MDT to Data-MDT.

The edge device of 12. 1 kinds of service providers, is characterized in that, comprising:

13. equipment according to claim 12, is characterized in that, described second processing unit, also at described second transmitting element to after another PE described sends the first message, re-create decapsulation table according to described MDT-Join message;