CN102571534B - Service transmission method based on ring network protection and node used for service transmission - Google Patents
Service transmission method based on ring network protection and node used for service transmission Download PDFInfo
- Publication number
- CN102571534B CN102571534B CN201010598510.5A CN201010598510A CN102571534B CN 102571534 B CN102571534 B CN 102571534B CN 201010598510 A CN201010598510 A CN 201010598510A CN 102571534 B CN102571534 B CN 102571534B
- Authority
- CN
- China
- Prior art keywords
- p2mp
- spme
- label
- ring
- node
- 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.)
- Active
Links
Landscapes
- Data Exchanges In Wide-Area Networks (AREA)
Abstract
The invention discloses a service transmission method based on ring network protection and a node used for service transmission, which are used for realizing the correct transmission of the service. The method comprises the following steps: in the process of building P2MP (point-to-multipoint) LSP (Label Switched Path) on a ring or after the P2MP LSP is built, a ring entering node of the ring judges whether working P2MP SPME (Sub-Path Maintenance Element) and P2MP SPME protection exist on the ring, if yes, a label value is distributed in an upstream label distribution mode; the label value is sent to all leaf nodes of the P2MP LSP on the ring; the ring entering node uses the label value to transmit service on the P2MP LSP by the working P2MP SPME and/ or P2MP SPME protection; and the node comprises a judgment module, a label distribution module, a transmitting module and a service packaging module. With the service transmission method, each leaf node can identify a label used when the ring entering node transmits the service so as to correctly forward the service.
Description
Technical field
The present invention relates to data network communication field, particularly relate to a kind of business transmitting method based on looped network protection and the node for business transmission.
Background technology
Under the promotion of telecommunication service IPization trend; the business of transport network carrying is from time division multiplexing (TDM; Time Division Multiplexing) be main to IP for main transformation; this just needs one effectively can transmit Packet Service; and the packet transport technologies of carrier class operation management maintain (OAM, Operations Administration and Maintain) and protection is provided.Under this demand, industry proposes Packet Transport Network (PTN, Packet Transport Network) concept, multiprotocol label switching transport frame (MPLS-TP, Transport Profile for Multi-Protocol Label Switching) is exactly the technology of a kind of PTN.
MPLS-TP technology is developed jointly by IETF (Internet Engineering Task group) and ITU-T (International Telecommunication Union's telecommunication standardsization tissue); in RFC5654 (MPLS-TP demand), point out that MPLS-TP needs to support point-to-point and point-to-multipoint transfer path; support arbitrary topological structure; as mesh (latticed) and ring (ring-type); and can protect above-mentioned transfer path, namely detailed demand (concrete demand is shown in 2.5 chapters and sections of RFC5654) be proposed to survivability.
Network survivability refer to cause traffic transport to be interrupted due to network failure or performance degradation time a kind of ability recovering traffic transport is provided, this recovery capability we be referred to as Recovery.In transport network; the transmitting of survivability to business plays vital effect; and SLAs (Service Level Agreements; service-level agreement) the guaranteed service that provides also requires network energy fast detecting to equipment fault and can complete protection operation in official hour, namely recovers the transmission of business.The Recovery of current definition comprises two kinds of mechanism: Protection (protection) and Restoration (recovery).Protection is one is that one or more operating path sets up one or more Protection path in advance, and for Protection path distributes the mechanism of resource, and the simplest mechanism is that a Protection path is used for protection operating path.Restoration then can use any available resource, refers generally to after operating path lost efficacy, trigger by rerouting mechanism the operating path set up a new transfer path and replace losing efficacy.Therefore, Protection can recover by finishing service fast, and claimed the switching of usual packet network can complete within the time of 50ms; And the time that Restoration recovers business is relatively long.
In addition, the application of point-to-multipoint (P2MP, Point To Multipoint); as IPTV is subject to paying attention to more and more widely; and most traditional transport network is all based on ring-network topology, therefore, the protection studying looped network P2MP business is significant.
At existing transmitted in packets network technology as in MPLS-TP, two large classes are mainly contained to the protection scheme of looped network.Wherein a large class is that each working LSP (Label Switching Path, label switched path) configures a protection LSP, and the protection quantity of LSP and the quantity of working LSP are directly proportional, as the protection rings scheme that ITU-T formulates.Second largest class is that establishment Protection path is used for protecting many working LSP, the protection of current this one-to-many has two kinds of solutions, scheme one is expansion LDP (Label Distribution Protocol, tag distribution protocol) or RSVP-TE (Resource ReSerVation Protocol-Traffic Engineering, RSVP based on Traffic Engineering extensions) support looped network protection, in this scheme, the protection LSP of a pre-configured closed loop on ring, all service LSPs (business LSP) that this protection LSP can be used on guard ring, in this scenario, under normal circumstances, business transmits according to normal label forwarding mechanism in working LSP, when a certain link or nodes break down, the upstream neighbor node of fault also need be pressed into the label of protection LSP except normal LSP Tag switching on label stack, according to the Label Forwarding Information Base of protection LSP business is sent to the downstream neighbor of fault like this, downstream node ejects outer field protection LSP label, and be the outgoing label of this node by the LSP Tag switching of internal layer, then continue to forward according to the Label Forwarding Information Base of working LSP.LDP or the RSVP-TE protocol extension of the program is the problem in order to vpn label when solving Node Protection exchanges.Scheme two is on ring, configure SPME (Sub-Path Maintenance Element; subpath maintenance entity); namely on protected link or protected section, create a work SPME; then the rightabout along ring is that work SPME creates a protection SPME; SPME uses linear protection structure; this protected mode can reduce the quantity of the Protection path of configuration, simultaneously this also one of MPLS-TP protection demand (minimizing the quantity of Protection path) just.But the guard method of this employing SPME needs label pop down, and internal layer LSP label replaces with outgoing label entering link point, and is pressed into the label of SPME; When for during to P2MP trail protection, the SPME configured here is P2MP, and each node on ring is the leaf node of SPME, forwards after ejecting outer field SPME label on each node according to the label of internal layer again.
P2MP business as shown in Figure 1; after the work be configured with as shown in Figure 2 and protection P2MPSPME; business arrives, into during link point A point, business is replaced with B peer distribution to the label Y of node A at the label X that enters of A node; and be pressed into the label Z1 of work P2MP SPME; such P2MP business forwards along work P2MP SPME; but upper node C, D, E and F of work P2MP LSP are when receiving this business, None-identified label Y, thus occur cannot the phenomenon of correct forwarding service.
Summary of the invention
The technical problem to be solved in the present invention is to provide a kind of business transmitting method based on looped network protection and the node for business transmission, realizes the correct transmission of business.
For solving the problems of the technologies described above, the invention provides a kind of business transmitting method based on looped network protection, comprising:
Ring create in the process of point-to-multipoint label switch paths (P2MP LSP), or after P2MPLSP has created, if the link point that enters of described ring judges described ring to exist the point-to-multipoint subpath maintenance entity of work (P2MP SPME) and protection P2MP SPME, then adopt the upper tag method of salary distribution to distribute a label value, sent to by described label value described P2MP LSP to be positioned at all leaf nodes on ring; Described enter link point use described label value by the business on P2MP LSP by described work P2MP SPME and/or protection P2MP SPME transmission.
Further; described enter link point use described label value the business on P2MP LSP to be referred to by described work P2MP SPME and/or protection P2MP SPME transmission: described in enter link point when sending business to downstream leaf node; described label value is transmitted the vpn label of label stack used as described business, the outermost layer of described label stack is the label of work P2MP SPME and/or protection P2MP SPME.
Further, the described step being sent to by label value described P2MP LSP to be arranged in all leaf nodes on ring: send to described P2MP LSP to be positioned at all leaf nodes on ring by path (Path) message described label value.
Further, described enter link point sent to by label value P2MP LSP to be arranged in the step of all leaf nodes on ring: described in enter link point and send to described P2MP LSP to be positioned at all leaf nodes on ring the PATH of the described label value of carrying respectively by mode of unicast, or to be sent to by the PATH of the described label value of carrying described P2MP LSP to be positioned at all leaf nodes on ring by described work P2MP SPME.
Further, described enter link point while described label value is sent to all leaf nodes, the identification information of described work P2MP SPME and/or routing information are also sent to all leaf nodes, makes described leaf node all know the work P2MP LSP at its place and the incidence relation of described work P2MP SPME.
For solving the problems of the technologies described above, present invention also offers a kind of node for business transmission, described node is as entering link point, and described node comprises judge module, label distribution module, sending module and business packed module, wherein:
Described judge module, in the process creating point-to-multipoint label switch paths (P2MP LSP) on ring, or after P2MP LSP has created, if judge described ring to exist the point-to-multipoint subpath maintenance entity of work (P2MP SPME) and protection P2MP SPME, then notified tag distribution module;
Described label distribution module, distributes a label value for adopting the upper tag method of salary distribution;
Described sending module, is positioned at all leaf nodes on ring for described label value being sent to described P2MP LSP;
Described business packed module, for using described label value by the business on P2MP LSP by described work P2MP SPME and/or protection P2MP SPME transmission.
Further; described business packed module; for using described label value the business on P2MP LSP to be transmitted by described work P2MP SPME and/or protection P2MP SPME in such a way: when sending business to downstream leaf node; described label value is transmitted the vpn label of label stack used as described business, the outermost layer of described label stack is the label of work P2MP SPME and/or protection P2MP SPME.
Further, described sending module is for being sent to by described label value described P2MP LSP to be positioned at all leaf nodes on ring in such a way: send to described P2MP LSP to be positioned at all leaf nodes on ring by PATH described label value.
Further, described sending module is for being sent to by described label value described P2MP LSP to be positioned at all leaf nodes on ring in such a way: sent to by the PATH of the described label value of carrying described P2MP LSP to be positioned at all leaf nodes on ring respectively by mode of unicast, or to be sent to by the PATH of the described label value of carrying described P2MP LSP to be positioned at all leaf nodes on ring by described work P2MP SPME.
Further, described sending module, also for while described label value is sent to all leaf nodes, the identification information of described work P2MP SPME and/or routing information are also sent to all leaf nodes, makes described leaf node all know the work P2MP LSP at its place and the incidence relation of described work P2MPSPME.
The label distribution method adopting the embodiment of the present invention to provide and node; on the ring that there is work and protection SPME; by P2MP LSP on ring enter link point be each leaf node distribute one for business transmit label value; enter link point when sending business to downstream leaf node; use this label value as vpn label; to make each leaf node can identify label into using during link point transport service, thus realize the correct forwarding of business.
Accompanying drawing explanation
Fig. 1 is the instance graph of P2MP business on looped network;
Fig. 2 is the configuration example figure of SPME on looped network;
Fig. 3 is the Establishing process figure of embodiment of the present invention work P2MP LSP;
Fig. 4 is the label distribution exemplary plot of a kind of label distribution method of the embodiment of the present invention;
Fig. 5 is the label distribution exemplary plot of the another kind of label distribution method of the embodiment of the present invention;
Fig. 6 is the exemplary plot of the label distribution instance three of embodiment of the present invention looped network protection;
Fig. 7 a and 7b is the protection exemplary plot of single place link failure in embodiment of the present invention method;
Fig. 8 is embodiment of the present invention node structure schematic diagram.
Embodiment
Prior art analysis is found, the vpn label of the business that some the leaf node None-identified due to work P2MP LSP receives, thus may cause cannot the phenomenon of correct forwarding data.Example as described in background, after A node receives business, the label X that enters in business is replaced with B peer distribution to the label Y of node A, and be pressed into the label of work P2MP SPME, like this when business arrives leaf node B, C and D along work P2MP SPME, leaf node B, C, D eject the label of outer SPME, but leaf node C and D is after ejection outer layer label, None-identified label Y, thus cause cannot the problem of correct forwarding service.
For solving the problem, need each node can identify internal layer LSP label, the present invention adopts following proposal to realize:
Ring create in the process of P2MP LSP, or after P2MP LSP has created, if the link point that enters on described ring judges that described ring exists work P2MP SPME and protection P2MP SPME, then adopt the upper tag method of salary distribution to distribute a label value, sent to by described label value described P2MP LSP to be positioned at all leaf nodes on ring; Described enter link point use described label value by the business on P2MP LSP by described work P2MP SPME and/or protection P2MP SPME transmission.
Entering link point uses this label value the business on P2MP LSP to be referred to by this work P2MP SPME and/or protection P2MP SPME transmission: this enters link point when sending business to downstream leaf node; described label value is transmitted the vpn label of label stack used as described business; namely enter link point and the label that enters in business is replaced with the label value that this enters ring peer distribution, the outermost layer of label stack is the label of work P2MPSPME and/or protection P2MP SPME.
In the process creating P2MP LSP, enter link point after receiving establishment message, judge whether ring exists work P2MP SPME and protection P2MP SPME, if existed, distributing labels value; After establishment P2MP LSP completes, entering link point after receiving refresh message, then can judge whether ring exists work P2MP SPME and protection P2MP SPME.Above-mentioned establishment message, refresh message are all carried in path (Path) message and send to leaf node.
Enter the label value that link point can be distributed and send to each leaf node respectively by mode of unicast, or this label value is sent to each leaf node by work SPME.
After each leaf node receives business, eject outer SPME label, the label value namely entering ring peer distribution according to vpn label forwards.In order to prevent the label value into ring peer distribution identical with the label value that certain leaf node distributes to other LSP, thus cause leaf node to carry out data retransmission, preferably, this enters link point while this label value is sent to all leaf nodes, the identification information of work P2MPSPME and/or routing information are also sent to all leaf nodes, these leaf nodes are made all to know the work P2MP LSP at its place and the incidence relation of work P2MP SPME, like this, each leaf node is when to downstream leaf node forwarding service, according to the path of the incidence relation determination forwarding service of the outer operative P2MPSPME label of described business and work P2MP LSP and described work P2MP SPME.
" adopt the upper tag method of salary distribution " and refer to that by upstream node be downstream node distributing labels.
Hereinafter will be described in detail to embodiments of the invention by reference to the accompanying drawings.It should be noted that, when not conflicting, the embodiment in the application and the feature in embodiment can combination in any mutually.
First link point is entered for root node with certain on ring; create job P2MP SPME and protection P2MP SPME along ring, on work P2MP SPME and protection P2MP SPME, run the connectedness of detection of connectivity mechanism Real-Time Monitoring SPME end to end simultaneously.These two P2MP SPME all in order to protect pass through ring P2MP LSP on business create.Wherein, work P2MPSPME and the protection transmission direction of P2MP SPME on ring are contrary, and are all be root node into link point, and all the other nodes on ring are the leaf node of P2MP SPME.
Introduce the flow process of distributing labels value in the process of establishing of work P2MP LSP below, as shown in Figure 3, comprise the following steps:
Step 301, the root node of work P2MP LSP, according to the establishment message of existing standard structure LSP, starts to create a point-to-multipoint LSP;
Here, creating message can be RSVP-TE Path message.
Step 302, when certain arrival on ring of Path message of work P2MP LSP enters link point, this enters link point and has judged whether that segment protect exists, and namely whether there is work P2MP SPME and protection P2MPSPME; If there is segment protect path, then perform step 303; If there is no segment protect path, perform step 304;
Step 303, determines to belong to the leaf node of total node (be leaf node on work P2MP SPME be also leaf node) on P2MP LSP; Entering link point adopts the upper tag method of salary distribution to distribute a label value, sends one or more Path message to the total node determined, and carries an identical label value in all Path message;
Owing to entering the root node that link point is work P2MP SPME, therefore this enters link point and knows all leaf nodes on this work P2MP SPME, when determining the leaf node belonging to total node, enter link point according to the leaf node carried in Path message, the matching degree of the leaf node of judgement work P2MP SPME and the leaf node of work P2MP LSP, thus know which leaf node is total node.
Here the transmission of Path message can be issue each leaf node respectively in the mode of clean culture, or sends to all leaf nodes by work P2MP SPME.
When forwarding Path message with mode of unicast, destination address is set to the IP address of corresponding object leaf node, and by the correlated branch information deletion of other total leaf node in Path message, this refers to and delete ERO (route display object) information relevant to other total leaf node or SERO (secondary route display object) information, like this, the branch information that in this Path message, only the leaf node of surplus object IP address designation is corresponding, the information (as address information) of other any node between Ingress node and object leaf node is deleted from this branch information, object is to not allow those middle these Path message of node processing, only allow the process of object leaf node.
Preferably, in the clean culture Path message sent, carry identification information and/or the routing information of work SPME, make the leaf node understanding work P2MP LSP of work P2MP LSP and the incidence relation of work P2MPSPME.
When forwarding Path message by work P2MP SPME, enter in the Path message that link point sends to downstream node and can do following setting: in Path message, add alert label (alarm label), be positioned at the top layer of label stack, object processes this Path message to allow each leaf node go.In addition, if carry identification information and/or the routing information of work SPME, in IF_ID RSVP_HOP object, then carry session (session) object of work P2MP SPME and optionally carry sender template (transmit leg template) object, carrying out unique identification P2MP SPME by those objects.
Step 304, if do not have segment protect, then sends Path message according to the rule of RFC4875.
Step 305, a certain leaf node on work P2MP SPME receives Path message and processes according to following rule:
If what receive is clean culture Path message, preserve the label value in Path message and the incidence relation with P2MPSPME, judge that whether this node is the destination node of branch simultaneously, if the destination node of a branch unique in Path message, then build Resv message and send and feed link point; Otherwise generate new Path message to continue to forward to downstream node.Label value in the information of no longer carrying work P2MP SPME here in new Path message and the Path message received.
If the Path message received by work P2MP SPME, then preserve information corresponding in Path message, here label value etc. is comprised, simultaneously chain of command process after the new Path message of regeneration then continue down to forward along work P2MP SPME, here delete the branch information relevant with this leaf node in new Path message, continue to carry the label value received simultaneously.In addition, to the process of Alert label according to existing standard process.
After a certain leaf node of work SPME receives the Resv message of work P2MP LSP, no longer distributing labels, does not also carry label in the Resv message that upstream nodes sends.
Step 306, work SPME root node receive the Resv message of P2MP LSP after, according to the predetermined processing of RFC4875.
By above step, after the root node of the Resv message arrival work P2MP LSP of the successful reservation of all branches, this P2MP LSP has just created successfully.
The present embodiment introduces the protection flow process of P2MP SPME:
Under normal circumstances, when the business on work P2MP LSP arrives into link point (root node of the P2MPSPME that namely works), business is sent on work P2MP SPME and protection P2MP SPME simultaneously.
Particularly; enter link point and the label that enters of the business of P2MP LSP is replaced with the label value distributed in step 303; then be the label of the outer field work P2MP SPME of a stream press-in; for the label of P2MP SPME is protected in a stream press-in in addition; namely forwarding service stream while of on work SPME and protection SPME, all runs OAM at work SPME and protection SPME simultaneously and monitors connective.On this ring, first forward according to the label of SPME, after the leaf node of P2MP SPME receives business, first eject the label of SPME, then judge ensuing forward-path according to the label of internal layer LSP, namely forward according to the Label Forwarding Information Base of LSP.
When the SPME that works breaks down; leaf node by fault effects does not receive the detection of connectivity message that root node sends within the regular hour; then this leaf node thinks that root node breaks down to this node branch, thus is switched to reception business from protection SPME.Leaf node not by fault effects does not perform switching.
When after the fault recovery on work SPME, original leaf node by fault effects can be selected to continue to receive from protection SPME, or switchback receives to from work SPME.
Below by way of specific embodiment, the present invention is described in detail.
Embodiment one
The present embodiment is the SPME profile instance that looped network P2MP LSP protects.
With on looped network each enter link point for root node, create two P2MP SPME respectively, wherein one for work SPME, and one is protection SPME, and the direction of two SPME is contrary.Generally, ring there are at most two nodes for entering link point, other any node can be link point, here illustrate with the simplest example, namely only have node A for entering link point, as shown in Figure 2, the root node of work SPME is node A, B, C, D, E and F are its leaf nodes, and along the clockwise direction of ring; The root node of protection SPME is also node A, and B, C, D, E and F are its leaf nodes, and along the counter clockwise direction of ring.Work SPME and protection SPME is respectively as shown in the actual situation line in Fig. 2 and some actual situation line.
Embodiment two
This gives an example of the label distribution of looped network protection, as shown in Figure 4, adopt the mode distributing labels value of clean culture, concrete step is as follows:
For P2MP LSP 1, the leaf node of this P2MP LSP and the leaf node of P2MP SPME fit like a glove.
Step 401: node A initiation P2MP LSP sets up message, here be RSVP-TE Path message, and node A judges to need protection and there are two SPME respectively as work and protection, so node A distributes a label value (as 20) respectively to Node B, C, D, E and F, is carried at by this label value in the clean culture Path message of transmission;
Here, the explicit route information of the P2MP LSP that node A receives is as shown in table 1, the source IP address mailing to the clean culture Path message of each leaf node is the address of node A, object IP address and the ERO/SERO of correspondence are as shown in table 2, and do not arrange alert option in the IP header of each Path message sent out.
Table 1
| Branch | Leaf node | Explicit route |
| 1 | B | B |
| 2 | C | B，C |
| 3 | D | C，D |
| 4 | E | D，E |
| 5 | F | E，F |
Table 2
| Path message destination address | ERO | SERO | Upper tag |
| The IP address of B | B | Nothing | 20 |
| The IP address of C | C | Nothing | 20 |
| The IP address of D | D | Nothing | 20 |
| The IP address of E | E | Nothing | 20 |
| The IP address of F | F | Nothing | 20 |
In the clean culture Path message sent, carry the mark of work P2MP SPME simultaneously; this can be realized by expansion affiliated partner; namely the association type that definition one is new is segment protect association; associated source node address is set to the address of node A, and association ID is set to the LSP ID (or LSP ID and Tunnel ID (Tunnel Identifier)) of work P2MP SPME.The form of affiliated partner can with reference to RFC4872.
Step 402: other nodes on ring, as B, C, D, E and F, receive RSVP-TE Path message, preserves this label value and the incidence relation with P2MP SPME, and judges the destination address of the branch being all ERO instruction.So Node B, C, D, E and F go to build respective Resv message respectively, issue node A, no longer distributing labels in Resv process.
Step 403: when node A receives the Resv message of the successful reservation of all leaf nodes, then this P2MP LSP has just created successfully.
The path of the work P2MP LSP1 set up according to the method described above and the label value of distribution are as shown in Figure 4.
Embodiment three
As shown in Figure 5, the Path message entering the establishment of link point sends to the mode of all leaf nodes by work P2MP SPME, step is as follows:
Step 501: what node A received P2MP LSP sets up message, here be RSVP-TE Path message, and node A judges to need protection and there are two SPME respectively as work and protection, so node A distributes a label value (20), is carried at by this label value in the Path message sent;
Here, the explicit route information in the Path message of the P2MP LSP that node A receives is as follows, but the information that the Path message that node A receives comprises is not limited only to content below:
S2L SUB-LSP-B ERO：A，B<S2L_SUB_LSP>object-B
S2L SUB-LSP-D SERO：B，C，D<S2L_SUB_LSP>object-D
S2L SUB-LSP-E SERO：D，E<S2L_SUB_LSP>object-E
S2L SUB-LSP-F SERO：E，F<S2L_SUB_LSP>object-F
In addition, the label of the Path message encapsulation work SPME sent out at node A and alert label (alert label is at the outermost layer of label stack).In IF_ID RSVP_HOP object, carry the session object of work P2MPSPME and optionally carry sender template object.
The information that the Path message that node A sends out comprises is as follows, but is not limited only to content below:
Up_Stream Label：20
S2L SUB-LSP-B ERO：B<S2L_SUB_LSP>object-B
S2L SUB-LSP-C SERO：B，C<S2L_SUB_LSP>object-C
S2L SUB-LSP-D SERO：C，D<S2L_SUB_LSP>object-D
S2L SUB-LSP-E SERO：D，E<S2L_SUB_LSP>object-E
S2L SUB-LSP-F SERO：E，F<S2L_SUB_LSP>object-F
The session+sender template object of IF_ID RSVP_HOP object:P2MP SPME
Step 502: the node on work P2MP SPME receives Path message, if this node is certain leaf node of work P2MP LSP, preserve this label value and the incidence relation with P2MP SPME, and complete the follow-up continuous Path of transmission to downstream node message in chain of command process, in the Path message sent out, delete the branch information corresponding with this node.
As in the present embodiment, Node B is a leaf node of work P2MP LSP, so B preserves the information of this label value and work P2MP SPME, and the Path that after chain of command process completes, structure is new continues to send out, and the branch information that the Path message sent out comprises is as follows:
Up_Stream Label：20
S2L SUB-LSP-C ERO：C<S2L_SUB_LSP>object-C
S2L SUB-LSP-D SERO：C，D<S2L_SUB_LSP>object-D
S2L SUB-LSP-E SERO：D，E<S2L_SUB_LSP>object-E
S2L SUB-LSP-F SERO：E，F<S2L_SUB_LSP>object-F
The session+sender template object of IF_ID RSVP_HOP object:P2MP SPME
For the node C in the present embodiment, owing to not being a leaf node of work P2MP LSP, so the process of node C and the process difference of Node B are that node C does not preserve the information of label value and work P2MP SPME.
The same Node B of the process of all the other nodes as D, E and F, is not described in detail here.
Step 503: when the root node of work P2MP LSP receives the Resv message of the successful reservation of all leaf nodes, then this P2MP LSP has just created successfully.
Embodiment four
For P2MP LSP 2, the leaf node of this P2MP LSP and the leaf node stapled section of P2MP SPME, as shown in Figure 6.
Step 601: node x1 initiation P2MP LSP 2 sets up message, is RSVP-TE Path message here.
Indicating source node address in session object is within the message the information such as x1, and the P2MPID of correspondence, and explicit route information is as shown in table 3.
Table 3
| Branch | Leaf node | Explicit route |
| 1 | B | A，B |
| 3 | D | B，C，D |
| 4 | F | D，E，F |
| 5 | x3 | F，x2，x3 |
Step 602: node A receives the Path message of P2MP LSP2; judge that existence two SPME are respectively as work and protection; and decision node B, D and F are the leaf nodes total with the P2MP SPME that works; so node A distributes a label value (as 30) respectively to Node B, D and F, is carried at by this label value in the clean culture Path message sending above several node.
Here, the source IP address that node A mails to the clean culture Path message of each leaf node is the address of node A, corresponding object IP address and ERO/SERO as shown in table 4.
Table 4
| Path message destination address | ERO | SERO |
| The IP address of B | B | Nothing |
| The IP address of D | D | Nothing |
| The IP address of F | F | F，x2，x3 |
In the clean culture Path message sent, carry the mark of work P2MP SPME simultaneously; this can be realized by expansion affiliated partner; namely the association type that definition one is new is segment protect association; associated source node address is set to the address of node A, and association ID is set to the LSP ID (or LSP ID+Tunnel ID) of work P2MP SPME.The form of affiliated partner can with reference to RFC4872.
Step 603: other nodes on ring are as B, D or F, receive RSVP-TE Path message, preserve this label value and the incidence relation with P2MP SPME, and judge that B and D is the destination address of the branch of corresponding ERO instruction, and node F not the destination address of corresponding SERO.So Node B, D go to build respective Resv message respectively, issue node A, need not go distributing labels again in Resv message, and node F sends Path message establishing branch (F, x2, x3) to downstream simultaneously.
Here, identification information and/or the routing information of label value (30) and work P2MP SPME is not carried in the Path message sent when node F creates branch (F, x2, x3).
Step 604: when node x1 receives the Resv message of the successful reservation of all leaf nodes, then this P2MP LSP has just created successfully.
The path of the work P2MP LSP2 set up according to the method described above and the label value of distribution are as shown in Figure 6.
Embodiment five
The protection of single place fault on looped network, as shown in figs. 7 a and 7b:
Step 701: under normal circumstances, the business on P2MP LSP is two on work SPME and protection SPME to be sent out, and leaf node receives business from work SPME;
Step 702: when on work SPME, break down in somewhere, as the link occurs fault between Fig. 7 b interior joint C and node D, leaf node D, E and F can detect this fault.
Here, the connectivity testing message sent by sending in cycle time the root node that do not receive expectation the detection of connectivity message of 3.5 times that leaf node judgement work SPME breaks down is learnt.
Step 703: leaf node D, E and F are switched to and will receive from protection SPME, leaf node B and C still selects to receive from work SPME.
Step 704: when after the fault recovery on work SPME, leaf node D, E and F switchback receives to from work SPME.
Here, when after the fault recovery on work SPME, be originally subject to leaf node corresponding to the branch of fault effects once the detection of connectivity message that sends of the root node that can receive expectation, then the fault on this leaf node judgement work SPME is recovered.
Embodiment six
The present embodiment introduction realizes the node for business transmission of said method, and this node, as entering link point, comprises judge module, label distribution module, sending module and business packed module, as shown in Figure 8, wherein:
Described judge module, in the process creating P2MP LSP on ring, or after P2MP LSP created, if judge described ring to exist work P2MP SPME and protection P2MP SPME, then notified tag distribution module;
Described label distribution module, distributes a label value for adopting the upper tag method of salary distribution;
Described sending module, is positioned at all leaf nodes on ring for described label value being sent to described P2MP LSP;
Described business packed module, for using described label value by the business on P2MP LSP by described work P2MP SPME and/or protection P2MP SPME transmission.
Preferably; described business packed module; for using described label value the business on P2MP LSP to be transmitted by described work P2MP SPME and/or protection P2MP SPME in such a way: when sending business to downstream leaf node; described label value is transmitted the vpn label of label stack used as described business, the outermost layer of described label stack is the label of work P2MP SPME and/or protection P2MP SPME.
Preferably, label value sends to described P2MP LSP to be positioned at all leaf nodes on ring by described PATH for generation pass message by described sending module.
Preferably, described sending module is for being sent to by described label value described P2MP LSP to be positioned at all leaf nodes on ring in such a way: sent to by the PATH of carrying label value P2MP LSP to be positioned at all leaf nodes on ring respectively by mode of unicast, or to be sent to by the PATH of carrying label value P2MP LSP to be positioned at all leaf nodes on ring by aforementioned operation P2MPSPME.
Preferably, sending module is also for while sending to all leaf nodes by label value, the identification information of work P2MP SPME and/or routing information are also sent to all leaf nodes, makes described leaf node all know the work P2MP LSP at its place and the incidence relation of work P2MP SPME.
The all or part of step that one of ordinary skill in the art will appreciate that in said method is carried out instruction related hardware by program and is completed, and described program can be stored in computer-readable recording medium, as read-only memory, disk or CD etc.Alternatively, all or part of step of above-described embodiment also can use one or more integrated circuit to realize.Correspondingly, each module/unit in above-described embodiment can adopt the form of hardware to realize, and the form of software function module also can be adopted to realize.The present invention is not restricted to the combination of the hardware and software of any particular form.
More than illustrate; be only the present invention's preferably embodiment, but protection scope of the present invention is not limited thereto, is anyly familiar with those skilled in the art in the technical scope that the present invention discloses; the change that can expect easily or replacement, all should be encompassed within protection scope of the present invention.Therefore, protection scope of the present invention should be as the criterion with the protection range of claims.
Claims (8)
1., based on a business transmitting method for looped network protection, comprising:
Ring create in the process of point-to-multipoint label switch paths P2MP LSP, or after P2MP LSP has created, if the link point that enters of described ring judges described ring to exist work point-to-multipoint subpath maintenance entity P2MP SPME and protection P2MP SPME, then adopt the upper tag method of salary distribution to distribute a label value, sent to by described label value described P2MP LSP to be positioned at all leaf nodes on ring; Described enter link point use described label value by the business on P2MP LSP by described work P2MP SPME and/or protection P2MP SPME transmission;
Described enter link point use described label value the business on P2MP LSP to be referred to by described work P2MP SPME and/or protection P2MP SPME transmission:
Described enter link point when sending business to downstream leaf node, described label value is transmitted the vpn label of label stack used as described business, the outermost layer of described label stack is the label of work P2MP SPME and/or protection P2MP SPME.
2. the method for claim 1, is characterized in that:
The described step being sent to by label value described P2MP LSP to be arranged in all leaf nodes on ring:
Described P2MP LSP is sent to be positioned at all leaf nodes on ring by path P ath message described label value.
3. the method for claim 1, is characterized in that:
Described enter link point sent to by label value P2MP LSP to be arranged in the step of all leaf nodes on ring:
Described enter link point send to described P2MP LSP to be positioned at all leaf nodes on ring the PATH of the described label value of carrying respectively by mode of unicast, or to be sent to by the PATH of the described label value of carrying described P2MP LSP to be positioned at all leaf nodes on ring by described work P2MP SPME.
4. the method for claim 1, is characterized in that:
Described enter link point while described label value is sent to all leaf nodes, the identification information of described work P2MP SPME and/or routing information are also sent to all leaf nodes, makes described leaf node all know the work P2MP LSP at its place and the incidence relation of described work P2MP SPME.
5., for a node for business transmission, it is characterized in that, described node is as entering link point, and described node comprises judge module, label distribution module, sending module and business packed module, wherein:
Described judge module, in the process creating point-to-multipoint label switch paths P2MP LSP on ring, or after P2MP LSP has created, if judge described ring to exist work point-to-multipoint subpath maintenance entity P2MP SPME and protection P2MP SPME, then notified tag distribution module;
Described label distribution module, distributes a label value for adopting the upper tag method of salary distribution;
Described sending module, is positioned at all leaf nodes on ring for described label value being sent to described P2MP LSP;
Described business packed module, for using described label value in such a way, the business on P2MP LSP is transmitted by described work P2MP SPME and/or protection P2MP SPME:
When sending business to downstream leaf node, described label value is transmitted the vpn label of label stack used as described business, the outermost layer of described label stack is the label of work P2MP SPME and/or protection P2MP SPME.
6. node as claimed in claim 5, is characterized in that:
Described sending module is for being sent to by described label value described P2MP LSP to be positioned at all leaf nodes on ring in such a way: send to described P2MP LSP to be positioned at all leaf nodes on ring by PATH described label value.
7. node as claimed in claim 5, is characterized in that:
Described sending module is for being sent to by described label value described P2MP LSP to be positioned at all leaf nodes on ring in such a way:
Send to described P2MP LSP to be positioned at all leaf nodes on ring the PATH of the described label value of carrying respectively by mode of unicast, or to be sent to by the PATH of the described label value of carrying described P2MP LSP to be positioned at all leaf nodes on ring by described work P2MP SPME.
8. node as claimed in claim 5, is characterized in that:
Described sending module, also for while described label value is sent to all leaf nodes, the identification information of described work P2MP SPME and/or routing information are also sent to all leaf nodes, makes described leaf node all know the work P2MP LSP at its place and the incidence relation of described work P2MP SPME.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201010598510.5A CN102571534B (en) | 2010-12-21 | 2010-12-21 | Service transmission method based on ring network protection and node used for service transmission |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201010598510.5A CN102571534B (en) | 2010-12-21 | 2010-12-21 | Service transmission method based on ring network protection and node used for service transmission |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN102571534A CN102571534A (en) | 2012-07-11 |
| CN102571534B true CN102571534B (en) | 2015-06-03 |
Family
ID=46416049
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201010598510.5A Active CN102571534B (en) | 2010-12-21 | 2010-12-21 | Service transmission method based on ring network protection and node used for service transmission |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN102571534B (en) |
Families Citing this family (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN103595507A (en) * | 2013-11-15 | 2014-02-19 | 烽火通信科技股份有限公司 | Internal information transmission device and internal information transmission method in packet network system |
| CN105490906A (en) * | 2015-12-07 | 2016-04-13 | 中国船舶重工集团公司第七二二研究所 | Ring network protection method and device |
| US10715428B2 (en) * | 2018-06-26 | 2020-07-14 | Juniper Networks, Inc. | Resource reservation techniques for point-to-multipoint tunnels on a ring network |
| CN112445825B (en) * | 2020-11-19 | 2024-05-14 | 北京思特奇信息技术股份有限公司 | SLA time limit processing method, device and storage medium |
Citations (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| WO2005104447A2 (en) * | 2004-03-26 | 2005-11-03 | Metro Packet Systems Inc. | Method of sending information through a tree and ring topology of a network system |
| CN101729348A (en) * | 2009-06-01 | 2010-06-09 | 中兴通讯股份有限公司 | Method and system for protecting point to multi-point ring |
Family Cites Families (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US8085676B2 (en) * | 2006-06-29 | 2011-12-27 | Nortel Networks Limited | Method and system for looping back traffic in QIQ ethernet rings and 1:1 protected PBT trunks |
-
2010
- 2010-12-21 CN CN201010598510.5A patent/CN102571534B/en active Active
Patent Citations (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| WO2005104447A2 (en) * | 2004-03-26 | 2005-11-03 | Metro Packet Systems Inc. | Method of sending information through a tree and ring topology of a network system |
| CN101729348A (en) * | 2009-06-01 | 2010-06-09 | 中兴通讯股份有限公司 | Method and system for protecting point to multi-point ring |
Also Published As
| Publication number | Publication date |
|---|---|
| CN102571534A (en) | 2012-07-11 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US7848224B2 (en) | Method and apparatus for constructing a repair path for multicast data | |
| US9350650B2 (en) | Switching to a backup traffic path by a label switching router in a multi-protocol label switching network | |
| US7298693B1 (en) | Reverse notification tree for data networks | |
| US7710860B2 (en) | Data relay apparatus and data relay method | |
| CN102316016B (en) | Method and device for forwarding multicasting flow | |
| CN102035712B (en) | Multiprotocol label exchanged ring network protection method, device and system | |
| CN101193052B (en) | Method and system for sub-network connection protection in multi-protocol label switching | |
| US8902729B2 (en) | Method for fast-re-routing (FRR) in communication networks | |
| CN101369958A (en) | Fast rerouting method and label exchange router | |
| CN102201985B (en) | Ring protection switching method adopting multi-protocol label switching transport profile (MPLS TP) and node | |
| CN101316225A (en) | Fault detection method, communication system and label exchange router | |
| EP2761829A2 (en) | Point-to-point based multicast label distribution protocol local protection solution | |
| US8611211B2 (en) | Fast reroute protection of logical paths in communication networks | |
| CN101785261A (en) | rsvp-te enhancement for mpls-frr bandwidth optimization | |
| Hariyawan | Comparison analysis of recovery mechanism at MPLS network | |
| CN101247354A (en) | Method for fast recovering heavy route aiming at T-MPLS network multicast | |
| CN102571534B (en) | Service transmission method based on ring network protection and node used for service transmission | |
| US20080232246A1 (en) | System and Method For Protection of a Multicast Traffic Path | |
| CN101374106A (en) | Method for forwarding data packet on MPLS LSP, network node and system | |
| CN101964743A (en) | Multiprotocol label-switched path APS (Active Protection System) protection and management method, equipment and system | |
| CN102546352B (en) | A kind of method and system realizing point-to-multipoint label switch paths protection | |
| CN101232453A (en) | Heavy route method for fast searching path in T-MPLS network | |
| CN102185773B (en) | Multi-protocol label switching transport profile ring protection switching method and node | |
| CN101729348B (en) | Method and system for protecting point to multi-point ring | |
| CN101977141B (en) | MPLS-TP-based multicast protection method |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| C06 | Publication | ||
| PB01 | Publication | ||
| C10 | Entry into substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| C14 | Grant of patent or utility model | ||
| GR01 | Patent grant | ||
| TR01 | Transfer of patent right |
Effective date of registration: 20200715 Address after: 510000 unit 2414-2416, building, No. five, No. 371, Tianhe District, Guangdong, China Patentee after: GUANGDONG GAOHANG INTELLECTUAL PROPERTY OPERATION Co.,Ltd. Address before: 518057 Nanshan District Guangdong high tech Industrial Park, South Road, science and technology, ZTE building, Ministry of Justice Patentee before: ZTE Corp. Effective date of registration: 20200715 Address after: 215500 No.13, Caotang Road, Changshu, Suzhou, Jiangsu Province Patentee after: Changshu intellectual property operation center Co.,Ltd. Address before: 510000 unit 2414-2416, building, No. five, No. 371, Tianhe District, Guangdong, China Patentee before: GUANGDONG GAOHANG INTELLECTUAL PROPERTY OPERATION Co.,Ltd. |
|
| TR01 | Transfer of patent right | ||
| CP02 | Change in the address of a patent holder |
Address after: 215500 5th floor, building 4, 68 Lianfeng Road, Changfu street, Changshu City, Suzhou City, Jiangsu Province Patentee after: Changshu intellectual property operation center Co.,Ltd. Address before: No.13 caodang Road, Changshu City, Suzhou City, Jiangsu Province Patentee before: Changshu intellectual property operation center Co.,Ltd. |
|
| CP02 | Change in the address of a patent holder |