CN101159691B - Originated multi-protocol label switching packet maximum length determining method and node - Google Patents
Originated multi-protocol label switching packet maximum length determining method and node Download PDFInfo
- Publication number
- CN101159691B CN101159691B CN2007101779357A CN200710177935A CN101159691B CN 101159691 B CN101159691 B CN 101159691B CN 2007101779357 A CN2007101779357 A CN 2007101779357A CN 200710177935 A CN200710177935 A CN 200710177935A CN 101159691 B CN101159691 B CN 101159691B
- Authority
- CN
- China
- Prior art keywords
- mpls
- lsp
- request message
- message
- length
- 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
Images
Landscapes
- Data Exchanges In Wide-Area Networks (AREA)
Abstract
The invention discloses a method for determining maximum length of an originally transmitted multi protocol label switching (MPLS) message, a label switched path (LSP) header node, and a LSP middle node. The method comprises transmitting a MPLS echo request message from a LSP header node, and determining the maximum length of originally transmitted MPLS message when receiving a MPLS echo responsemessage indicating that the maximum transmission unit (MTU) of an interface is not enough and returned from a LSP middle node, according to the label stack depth and the interface MTU of the LSP middle node in the response message. By the invention, when the network allocation is changed, the LSP header node can timely regulate the maximum length of originally transmitted MPLS message, so as to prevent retransmission failure of the MPLS message.
Description
Technical field
The present invention relates to multiprotocol label switching (MPLS, Multi Protocol Label Switching) technical field, be specifically related to a kind of MPLS of starting packet maximum length and determine method and a kind of label switched path (LSP, Label Switched Path) head node, a kind of LSP intermediate node.
Background technology
The MPLS system mainly comprises two parts: signaling control plane and data forwarding plane.Wherein, the signaling control plane is responsible for the foundation of MPLS forward-path: LSP, but can't detect LSP transmission data failure mistake.The situation of upstream and downstream and whole piece LSP also can't be known then based on isolated node in the data forwarding plane.Therefore, the MPLS system provides a kind of MPLS Ping/Trace Route mechanism specially, is used for validity and the accessibility of LSP are detected.
Fig. 1 is the flow chart of existing MPLS Ping/Trace Route, and as shown in Figure 1, its concrete steps are as follows:
LSP head node structure MPLS echo request message in the step 101:MPLS network carries LSP destination node address, life span (TTL, Time to Live) in this message, this MPLSecho request message is sent.
In MPLS Ping, the initial value of TTL is 255; In MPLS Trace Route, the initial value of TTL is 1.The LSP head node is whenever received a MPLS echo response message, and ttl value is added 1.
LSP receiving node in the step 102:MPLS network is received this MPLS echo request message, judges whether the destination node address in this message is this LSP receiving node address, if, execution in step 107; Otherwise, execution in step 103.
The LSP receiving node may be the intermediate node on the LSP, also may be the destination node of LSP.
Step 103:LSP receiving node judges whether the ttl value in the MPLS echo request message is 0 after subtracting 1, if, execution in step 105; Otherwise, execution in step 104.
Step 104:LSP receiving node forwards this MPLS echo request message, goes to step 102.
Step 105:LSP receiving node returns MPLS echo response message to the LSP head node, and this message carries the address of this LSP receiving node, and the indication of the error code of message: TTL is overtime.
Step 106:LSP head node is received MPLS echo response message, LSP receiving node address in the recorded message re-constructs MPLS echo request message, writes this MPLS echo request message after current ttl value is added 1, MPLS echo request message is sent, go to step 102.
Step 107:LSP receiving node is determined to return MPLS echo response message from as the LSP destination node to the LSP head node, the error code indication in the message: arrived destination node.
Step 108:LSP head node is received MPLS echo response message, learns according to the error code in the message: MPLS echo request message has arrived destination node, determines that then LSP is effective, can reach.
As can be seen, MPLS Ping/Trace Route can detect effective, the accessibility of LSP.But, for non-the Internet agreement (IP, Internet Protocol) but burst MPLS message, whether message can transmission success, not only relevant, also relevant with the interface maximum transmission unit (MTU, Maximum Transmission Unit) of the node of message institute road warp with LSP.Each node all has interface mtu separately, and the MPLS message length that receives when node is during greater than the interface mtu of this node, and this MPLS message can't be forwarded away, thereby cause MPLS message retransmission failure.Therefore, must rationally determine the length of the MPLS message that starts.
The MPLS message is message to be encapsulated in the MPLS head transmit processing, and message also can be stamped various labels in repeating process, makes message length increase.As shown in Figure 2, the MPLS message can be stamped virtual-circuit label (VC-Label) and outer label through router RTA the time, when this MPLS message arrives router RTB, and the outer label of first exchange, and, need to give the MPLS message to stamp tunnel label owing to walk the MPLS tunnel between RTB and the RTC.As can be seen, the length of MPLS message has increased in transmission course.
At present, when initial network planning finishes, can determine the label situation of MPLS message in the MPLS network transmission process, go up the interface mtu of each node then in conjunction with LSP, determine the maximum length of the MPLS message that starts according to the network design situation.After this according to this MPLS packet maximum length structure MPLS message that starts.But along with the upgrading of network application, improvement etc., network design for example can change: the tunnel in the MPLS network increases, thereby causes the change of the label situation of MPLS message in network transmission process.Because the MPLS network equipment may adhere to different manufacturers separately, therefore, the change that the whole network is disposed possibly can't in time be learnt by the manufacturer of the head node of LSP ownership, thereby can't in time adjust the maximum length of the MPLS message that starts, and causes MPLS message retransmission failure.
Summary of the invention
The embodiment of the invention provides the MPLS packet maximum length that starts to determine method and LSP head node, LSP intermediate node, with the start accuracy of MPLS packet maximum length of raising.
The technical scheme of the embodiment of the invention is achieved in that
A kind of MPLS of starting packet maximum length is determined method, and this method comprises:
A, LSP head node send MPLS echo request message;
B, LSP head node receive the not enough MPLS echo response message of indication interface mtu that the LSP intermediate node returns, the interface mtu of dark this LSP intermediate node in according to the outgoing label stack of this LSP intermediate node in this response message, the MPLS packet maximum length of determining to start.
The length of the described MPLS echo of steps A request message equals the interface mtu length of described LSP head node.
The described MPLS packet maximum length of determining to start of step B comprises:
The length of the interface mtu length of MPLS packet maximum length=described LSP intermediate node-(the outgoing label stack of described LSP intermediate node is dark-label stack in the MPLS echo request message that described LSP head node sends is dark) * each label starts.
Label in the MPLS echo request message that described LSP head node sends is: 0 label.
The MPLS echo response message that the indication interface mtu that the described LSP intermediate node of step B returns is not enough further carries: the overtime indication of life span TTL;
And the described LSP head node of step B is determined to start and is further comprised after the MPLS packet maximum length:
The LSP head node re-constructs MPLS echo request message, the length of message equals described definite MPLS packet maximum length that starts, the ttl value that ttl value in the message equals in the last MPLS echo request message that sends adds 1, this MPLS echo request message is sent, go to step B.
The MPLS echo response message that the indication interface mtu that the described LSP intermediate node of step B returns is not enough further carries: the not overtime indication of TTL;
And, inlet LSR re-constructs MPLS echo request message, the length of message equals described definite MPLS packet maximum length that starts, ttl value in the message equals the ttl value in the last MPLS echo request message that sends, this MPLS echo request message is sent, go to step B.
Further comprise after the described step B:
C, LSP head node receive that indication MPLS echo request message has arrived the MPLS echo response message of destination node, and then the MPLS packet maximum length of determining with the last time that starts is as final definite MPLS packet maximum length that starts.
The outgoing label stack of the described LSP intermediate node of step B interface mtu dark and the LSP intermediate node is carried among the MPLS MTU type lengths values TLV of MPLS echo response message.
A kind of LSP head node comprises:
MPLS packet sending and receiving module, send MPLS echo request message, receive the not enough MPLS echo response message of indication interface mtu that the LSP intermediate node returns, the outgoing label stack of this LSP intermediate node in response message interface mtu dark and this LSP intermediate node is sent to the message length computing module that starts;
The message length computing module starts: the dark and interface mtu of the outgoing label stack of the LSP intermediate node of sending according to MPLS packet sending and receiving module, the MPLS packet maximum length of determining to start.
The described message length computing module that starts further comprises, described definite MPLS packet maximum length that starts is sent to the module of MPLS packet sending and receiving module,
And, described MPLS packet sending and receiving module further comprises, be used to receive the MPLS packet maximum length that starts that the message length computing module sends that starts, and, if MPLS echo response message carries the overtime indication of TTL, then re-construct MPLS echo request message, the length of request message equals described definite initial MPLS packet maximum length, the ttl value that ttl value in the request message equals in the last MPLS echo request message that sends adds 1, the module that the request message of structure is sent.
The described message length computing module that starts further comprises, described definite MPLS packet maximum length that starts is sent to the module of MPLS packet sending and receiving module,
And, described MPLS packet sending and receiving module further comprises, be used to receive the MPLS packet maximum length that starts that the message length computing module sends that starts, and, if MPLS echo response message carries the not overtime indication of TTL, then re-construct MPLS echo request message, the length of request message equals described definite initial MPLS packet maximum length, ttl value in the request message equals the ttl value in the last MPLSecho request message that sends, the module that the request message of structure is sent.
Described MPLS packet sending and receiving module further comprises, receive that indication MPLSecho request message that the LSP destination node is sent has arrived the MPLS echo response message of destination node, then the module of MPLS packet maximum length of sending with the message length computing module the last time of starting that start as the final MPLS packet maximum length of determining that starts.
A kind of LSP intermediate node comprises:
MPLS packet sending and receiving module, receive the MPLS echo request message that the LSP head node is sent, request message is sent to the interface mtu detection module, the interface mtu that receiving interface MTU detection module is sent is indicated inadequately, and interface mtu is indicated inadequately and the outgoing label stack of this LSP intermediate node dark with carrying, the MPLS echo response message of the interface mtu length of this LSP intermediate node returns to the LSP head node;
The interface mtu detection module receives the MPLS echo request message that MPLS packet sending and receiving module is sent, and detects the interface mtu length of request message length greater than this LSP intermediate node, then indicates inadequately to MPLS packet sending and receiving module transmission interface MTU.
Described LSP intermediate node further comprises: the overtime detection module of TTL, receive the MPLS echo request message that MPLS packet sending and receiving module is sent, ttl value in the request message is subtracted 1,, then return the not overtime indication of TTL to MPLS packet sending and receiving module if the difference that obtains is not 0; If the difference that obtains equals 0, then return the overtime indication of TTL to MPLS packet sending and receiving module;
And described MPLS packet sending and receiving module further comprises, receives not overtime indication of TTL or the overtime indication of TTL that the overtime detection module of TTL is sent, and the not overtime indication of this TTL or the overtime indication of TTL are carried at module in the MPLS echo response message.
Compared with prior art, in the embodiment of the invention, the LSP head node sends MPLS echo request message, when receiving the not enough MPLS echo response message of indication interface mtu that the LSP intermediate node returns, the interface mtu of dark this LSP intermediate node in according to the outgoing label stack of this LSP intermediate node in this response message, the MPLS packet maximum length of determining to start.The embodiment of the invention makes that when network design changes the LSP head node can in time be adjusted the MPLS packet maximum length that starts, thereby has avoided MPLS message retransmission failure.
Description of drawings
Fig. 1 is the flow chart of existing MPLS Ping/Trace Route;
Fig. 2 is that existing MPLS message is transmitted schematic diagram;
The flow chart of the MPLS Ping/Trace Route that Fig. 3 provides for the embodiment of the invention;
Start system's composition diagram of MPLS packet maximum length of determining of providing of the embodiment of the invention is provided Fig. 4.
Embodiment
The present invention is further described in more detail below in conjunction with drawings and the specific embodiments.
The embodiment of the invention is adjusted the MPLS packet maximum length that starts by MPLS Ping/Trace Route.
The flow chart of the MPLS Ping/Trace Route that Fig. 3 provides for the embodiment of the invention, as shown in Figure 3, its concrete steps are as follows:
The LSP head node of step 301:MPLS network is found the MPLS message retransmission failure of certain application, with the interface mtu of this LSP head node as the MPLS packet maximum length L that starts, structure MPLS echo request message, the length of this message equals the interface mtu length of this LSP head node, use the number of tags that should be pressed into when initial according to this, in MPLS echo request message, be pressed into 0 label of similar number, carry LSP destination node address in the message, and in message, increase MPLS MTU type-length-value (TLV, Type-Length-Value), this MPLS MTU TLV comprises: the interface mtu length of dark and this LSP head node of 0 label stack, and the not burst (DF, Don ' t Fragment) of the IP message in message sign is set to not allow burst.
It is dark that 0 label stack in the MPLS echo request message in this step is called the test label stack deeply.
In actual applications, the LSP head node may be found the MPLS message retransmission failure of certain application, the MPLS message of other application is then transmitted normally, this kind situation is likely because the MPLS message length of this kind application is excessive causes, at this moment, the LSP head node can adopt MPLSPing/Trace Route to adjust the MPLS packet maximum length that starts at this application.
According to the regulation of mpls protocol, after the node on the LSP is received the MPLS echo request message that has 0 label,, can earlier 0 label be ejected if will handle to this message, remake subsequent treatment.
Same as the prior art, if the LSP head node is initiated MPLS Ping, then the TTL initial value in the MPLS echo request message is 255; If the LSP head node is initiated MPLS Trace Route, then the TTL initial value in the MPLSecho request message is 1.
Step 302:LSP head node sends MPLS echo request message.
LSP receiving node in the step 303:MPLS network is received this MPLS echo request message, judges whether the destination node address in the message is this LSP receiving node address, if, execution in step 316; Otherwise, execution in step 304.
Step 304:LSP receiving node judges whether the ttl value in the message is 0 after subtracting 1, if, execution in step 305～310; Otherwise, execution in step 311～315.
Whether the length that step 305:LSP receiving node is judged MPLS echo request message greater than the interface mtu length of this LSP receiving node, if, execution in step 306; Otherwise, execution in step 309.
Step 306:LSP receiving node structure MPLS echo response message, overtime and the interface mtu of error code in this message indication: TTL is transmitted the MPLS message inadequately, and increase MPLSMTU TLV in this message, this MPLS MTU TLV comprises: the interface mtu length of dark and this LSP receiving node of the outgoing label stack of this LSP receiving node.
Here, the outgoing label stack of this LSP receiving node among the MPLS MTU TLV deeply not only comprises: the label stack that MPLS echo request message is comprised when just entering this LSP receiving node is dark, and it is dark to comprise that also MPLS echo request message is signed the label stack that newly is pressed into after the exchange at the enterprising rower of this LSP receiving node.
Step 307:LSP head node is received MPLS echo response message, learn according to the error code in this message: the interface mtu of LSP receiving node transmit the MPLS message inadequately and TTL overtime, (* is a) for the interface mtu length of the LSP receiving node in the MPLS echo response message-(the outgoing label stack of the LSP receiving node in the MPLS echo response message dark-the test label stack is dark) then to recomputate the MPLS packet maximum length L=that starts.
Here, the unit of L can be byte, and at this moment, the unit of interface mtu length is a byte, and the outgoing label stack is the outgoing label number deeply, and the test label stack is the test label number deeply, the byte number that a comprises for each label.
Step 308:LSP head node re-constructs MPLS echo request message, the MPLS packet maximum length L that starts that the length of this message equals to obtain in the step 307, ttl value is added the MPLS echo request message of putting into this neotectonics after 1, the out of Memory that carries in the message is identical with the MPLS echo request message of structure in the step 301, goes to step 303.
Step 309:LSP receiving node returns MPLS echo response message to the LSP head node, and the overtime and interface mtu of error code in this message indication: TTL is enough transmitted the MPLS message.
Consider the form consistency of MPLS echo response message, the MPLS echo response message in this step can increase MPLS MTU TLV, and this MPLS MTU TLV comprises: the interface mtu of dark and this LSP receiving node of the outgoing label stack of this LSP receiving node.
Step 310:LSP head node receives MPLS echo response message, learn according to the error code in this message: the overtime and interface mtu LSP receiving node of TTL is enough transmitted the MPLS message, then re-construct MPLS echo request message, the equal in length of the length of message and the last MPLS echo request message that sends, ttl value is added the MPLS echo request message of putting into neotectonics after 1, the out of Memory that carries in the message is identical with the MPLS echo request message of structure in the step 301, this message is sent, go to step 303.
Whether the length that step 311:LSP receiving node is judged MPLS echo request message greater than the interface mtu of this LSP receiving node, if, execution in step 313; Otherwise, execution in step 312.
Step 312:LSP receiving node forwards this MPLS echo request message, goes to step 303.
Step 313:LSP receiving node structure MPLS echo response message, the not overtime and MTU length this LSP receiving node of the error code of this message indication: TTL is transmitted the MPLS message inadequately, and in message, increase MPLS MTU TLV, this MPLS MTU TLV comprises: the interface mtu of dark and this LSP receiving node of the outgoing label stack of this LSP receiving node returns to the LSP head node with MPLS echo response message.
Step 314:LSP head node is received MPLS echo response message, error code according to this message is learnt: the not overtime and interface mtu LSP receiving node of TTL is transmitted the MPLS message inadequately, and (* a) for the interface mtu length of the LSP receiving node in the MPLS echo response message-(the outgoing label stack of the LSP receiving node in the MPLS echo response message dark-the test label stack is dark) then to recomputate the MPLS packet maximum length L=that starts.
Here, the unit of L can be byte, and at this moment, the unit of interface mtu length is a byte, and the outgoing label stack is the outgoing label number deeply, and the test label stack is the test label number deeply, the byte number that a comprises for each label.
Step 315:LSP head node re-constructs MPLS echo request message, the MPLS packet maximum length L that starts that the length of message equals to obtain in the step 314, ttl value in the message is identical with ttl value in the last MPLS echo request message that sends, the out of Memory that carries in the message is identical with the MPLS echo request message of structure in the step 301, goes to step 303.
Step 316:LSP receiving node is determined to return MPLS echo response message from as the LSP destination node to the LSP head node, the error code indication in this message: arrived destination node.
Step 317:LSP head node receives MPLS echo response message, learn according to the error code in this message: MPLS echo request message has arrived the LSP destination node, and then the MPLS packet maximum length L that starts that obtains with the last time is as the final MPLS packet maximum length of determining that starts.
After this, the LSP head node sends the MPLS message according to the MPLS packet maximum length L that starts that should finally determine, that is: the length of the MPLS message of transmission can not be greater than this MPLS packet maximum length L that starts that finally determines.
Fig. 4 determines system's composition diagram for the MPLS packet maximum length that starts that the embodiment of the invention provides, and as shown in Figure 4, it mainly comprises: LSP head node 41, LSP intermediate node 42 and LSP destination node 43, wherein:
MPLS packet sending and receiving module 411: send MPLS echo request message to LSP intermediate node 42, receive the interface mtu that carries this LSP intermediate node of indication that LSP intermediate node 42 returns and transmit the MPLS echo response message of the error code that MPLS transmits inadequately, the outgoing label stack interface mtu dark and this LSP intermediate node of this LSP intermediate node of carrying in the MPLS echo response message is sent to the message length computing module 412 that starts; The reception MPLS packet maximum length that starts that message length computing module 412 is sent that starts, re-construct MPLS echo request message, the length of MPLS echo request message equals described initial MPLS packet maximum length, and, if MPLS echo response message carries the overtime indication of TTL, then, ttl value in the MPLS echo request message of the last time transmission is added the MPLSecho request message of putting into structure after 1, if MPLS echo response message carries the not overtime indication of TTL, then the ttl value in the MPLS echo request message that the last time is sent is put into the MPLS echo request message of structure, and the MPLS echo request message of constructing is sent to LSP intermediate node 42; Receive that indication MPLS echo request message that LSP destination node 43 is sent has arrived the MPLS echo response message of destination node, then the MPLS packet maximum length of sending with 412 the last times of message length computing module of starting that starts is as the final MPLS packet maximum length of determining that starts.
Message length computing module 412 starts: the dark and interface mtu of the outgoing label stack of the LSP intermediate node of sending according to MPLS packet sending and receiving module 411 42, the MPLS packet maximum length of determining to start sends to MPLS packet sending and receiving module 411 with this MPLS packet maximum length that starts.
LSP intermediate node 42 mainly comprises: MPLS packet sending and receiving module 421, the overtime detection module 422 of TTL and interface mtu detection module 423, and each module functions is as follows:
MPLS packet sending and receiving module 421: receive the MPLS echo request message that LSP head node 41 is sent, MPLS echo request message is sent to overtime detection module 422 of TTL and interface mtu detection module 423; The interface mtu that receiving interface MTU detection module 423 is sent is indicated inadequately, if receive the not overtime indication of TTL that the overtime detection module 422 of TTL is sent, then will carry the not overtime and interface mtu of indication TTL and transmit the error code of MPLS message inadequately, and the outgoing label stack of this LSP intermediate node 42 is dark and the MPLS echo response message of the MPLS MTU TLV of the interface mtu length of this LSP intermediate node 42 returns to LSP head node 41, if receive the overtime indication of TTL that the overtime detection module 422 of TTL is sent, then will carry the error code that the overtime and interface mtu of indication TTL is transmitted the MPLS message inadequately, and the outgoing label stack of this LSP intermediate node 42 is dark and the MPLS echo response message of the MPLS MTU TLV of the interface mtu length of this LSP intermediate node 42 returns to LSP head node 41.
The overtime detection module 422 of TTL: receive the MPLS echo request message that MPLS packet sending and receiving module 42 1 is sent, ttl value in the MPLS echo request message is subtracted 1, if the difference that obtains is not 0, then return the not overtime indication of TTL to MPLS packet sending and receiving module 421; If the difference that obtains equals 0, then return the overtime indication of TTL to MPLS packet sending and receiving module 421.
Interface mtu detection module 423: receive the MPLS echo request message that MPLS packet sending and receiving module 421 is sent, detect the interface mtu length of MPLS echo request message length, then indicate inadequately to MPLS packet sending and receiving module 421 transmission interface MTU greater than this LSP intermediate node 42.
LSP destination node 43: receive the MPLS echo request message that LSP intermediate node 42 is sent, detect the destination node address of carrying in the MPLS echo request message and be self address, return the MPLS echo response message that carries the error code that indication arrived destination node to LSP head node 41.
The above only is process of the present invention and method embodiment, in order to restriction the present invention, all any modifications of being made within the spirit and principles in the present invention, is not equal to replacement, improvement etc., all should be included within protection scope of the present invention.
Claims (9)
1. an originated multi-protocol label exchange MPLS packet maximum length is determined method, it is characterized in that this method comprises:
A, label switching path LSP head node send MPLS echo request message;
B, LSP head node receive the not enough MPLS echo response message of indication interface maximum transmission unit MTU that the LSP intermediate node returns, the interface mtu of dark this LSP intermediate node in according to the outgoing label stack of this LSP intermediate node in this response message, the MPLS packet maximum length of determining to start, and
If this response message carries: the overtime indication of life span TTL, then re-construct MPLS echo request message, the length of message equals the determined MPLS of starting packet maximum length, the ttl value that ttl value in the message equals in the last MPLS echo request message that sends adds 1, this MPLS echo request message is sent, go to step B;
If this response message carries: the not overtime indication of TTL, then re-construct MPLS echo request message, the length of message equals the determined MPLS of starting packet maximum length, ttl value in the message equals the ttl value in the last MPLS echo request message that sends, this MPLS echo request message is sent, go to step B.
2. the method for claim 1 is characterized in that, the length of the described MPLS echo of steps A request message equals the interface mtu length of described LSP head node.
3. the method for claim 1 is characterized in that, the described MPLS packet maximum length of determining to start of step B comprises:
The length of the interface mtu length of MPLS packet maximum length=described LSP intermediate node-(the outgoing label stack of described LSP intermediate node is dark-label stack in the MPLS echo request message that described LSP head node sends is dark) * each label starts.
4. method as claimed in claim 3 is characterized in that, the label in the MPLSecho request message that described LSP head node sends is: 0 label.
5. the method for claim 1 is characterized in that, further comprises after the described step B:
C, LSP head node receive that indication MPLS echo request message has arrived the MPLS echo response message of destination node, and then the MPLS packet maximum length of determining with the last time that starts is as final definite MPLS packet maximum length that starts.
6. the method for claim 1 is characterized in that, the outgoing label stack of the described LSP intermediate node of step B interface mtu dark and the LSP intermediate node is carried among the MPLSMTU type lengths values TLV of MPLS echo response message.
7. a label switching path LSP head node is characterized in that, comprising:
Multiprotocol label switching MPLS packet sending and receiving module, send MPLS echo request message, receive the not enough MPLS echo response message of indication interface maximum transmission unit MTU that the LSP intermediate node returns, the outgoing label stack of this LSP intermediate node in response message interface mtu dark and this LSP intermediate node is sent to the message length computing module that starts; The reception MPLS packet maximum length that starts that the message length computing module is sent that starts, and, if MPLS echo response message carries the overtime indication of life span TTL, then re-construct MPLS echo request message, the length of request message equals described definite initial MPLS packet maximum length, the ttl value that ttl value in the request message equals in the last MPLS echo request message that sends adds 1, the request message of structure is sent, if MPLS echo response message carries the not overtime indication of TTL, then re-construct MPLS echo request message, the length of request message equals described definite initial MPLS packet maximum length, ttl value in the request message equals the ttl value in the last MPLSecho request message that sends, and the request message of constructing is sent;
The message length computing module starts, dark and the interface mtu of the outgoing label stack of the LSP intermediate node of sending according to MPLS packet sending and receiving module, the MPLS packet maximum length of determining to start sends to the determined MPLS of starting packet maximum length the module of MPLS packet sending and receiving module.
8. LSP head node as claimed in claim 7, it is characterized in that, described MPLS packet sending and receiving module further comprises, receive that indication MPLS echo request message that the LSP destination node is sent has arrived the MPLS echo response message of destination node, then the module of MPLS packet maximum length of sending with the message length computing module the last time of starting that start as the final MPLS packet maximum length of determining that starts.
9. a label switching path LSP intermediate node is characterized in that, comprising:
Multiprotocol label switching MPLS packet sending and receiving module, receive the MPLS echo request message that the LSP head node is sent, request message is sent to interface maximum transmission unit MTU detection module and the overtime detection module of life span TTL, the interface mtu that receiving interface MTU detection module is sent is indicated inadequately, receive not overtime indication of TTL or the overtime indication of TTL that the overtime detection module of TTL is sent, will carry not overtime indication of the TTL that receives or the overtime indication of TTL, interface mtu is indicated inadequately, and the outgoing label stack of this LSP intermediate node is dark, the MPLS echo response message of the interface mtu length of this LSP intermediate node returns to the LSP head node;
The interface mtu detection module receives the MPLS echo request message that MPLS packet sending and receiving module is sent, and detects the interface mtu length of request message length greater than this LSP intermediate node, then indicates inadequately to MPLS packet sending and receiving module transmission interface MTU;
The overtime detection module of TTL receives the MPLS echo request message that MPLS packet sending and receiving module is sent, and the ttl value in the request message is subtracted 1, if the difference that obtains is not 0, then returns the not overtime indication of TTL to MPLS packet sending and receiving module; If the difference that obtains equals 0, then return the overtime indication of TTL to MPLS packet sending and receiving module.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN2007101779357A CN101159691B (en) | 2007-11-22 | 2007-11-22 | Originated multi-protocol label switching packet maximum length determining method and node |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN2007101779357A CN101159691B (en) | 2007-11-22 | 2007-11-22 | Originated multi-protocol label switching packet maximum length determining method and node |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN101159691A CN101159691A (en) | 2008-04-09 |
| CN101159691B true CN101159691B (en) | 2010-11-10 |
Family
ID=39307616
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN2007101779357A Active CN101159691B (en) | 2007-11-22 | 2007-11-22 | Originated multi-protocol label switching packet maximum length determining method and node |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN101159691B (en) |
Families Citing this family (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| JP5672836B2 (en) * | 2010-08-09 | 2015-02-18 | 日本電気株式会社 | COMMUNICATION DEVICE, COMMUNICATION METHOD, AND COMMUNICATION PROGRAM |
| CN106688209B (en) | 2014-10-29 | 2020-12-01 | 柏思科技有限公司 | Method and system for transmitting broadcast data |
| EP3613226B1 (en) * | 2017-05-15 | 2022-09-28 | Samsung Electronics Co., Ltd. | Method and system for notifying state of members of mission critical service (mcx) groups |
| CN109873763B (en) * | 2017-12-05 | 2021-12-03 | 北京华为数字技术有限公司 | Communication method and device |
-
2007
- 2007-11-22 CN CN2007101779357A patent/CN101159691B/en active Active
Also Published As
| Publication number | Publication date |
|---|---|
| CN101159691A (en) | 2008-04-09 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN108964943B (en) | Method and device for realizing IOAM packaging | |
| US11228515B2 (en) | Data packet detection method, device, and system | |
| CN102273136B (en) | Method and apparatus for detecting multi-service performance in tunnel | |
| JP5462954B2 (en) | Packet loss detection method and apparatus, and router | |
| CN102437931B (en) | Detection method and device of service path | |
| CN101529811B (en) | A method and system for verifying connectivity of multi- segment pseudo-wires by tracing | |
| US8305882B2 (en) | Methods, systems, and computer program products for detecting and/or correcting faults in a multiprotocol label switching network by using redundant paths between nodes | |
| CN100387003C (en) | Chain-circuit time delay detecting method | |
| CN101778113B (en) | Method for detection of RP state in multicast network, device, RP device and multicast system | |
| CN102035692B (en) | Method and device for detecting quality of link | |
| CN101459547B (en) | Label forwarding path failure detection method and system | |
| CN101316225A (en) | Fault detection method, communication system and label exchange router | |
| WO2011055837A1 (en) | Node, monitoring and administration method used thereupon, and transfer system, input circuit, and output circuit using same | |
| CN101174975A (en) | Periodic line fault location method and system in Ethernet | |
| US8724451B2 (en) | Method for protecting a pseudo-wire | |
| CN101159691B (en) | Originated multi-protocol label switching packet maximum length determining method and node | |
| CN101848155A (en) | Detection method of label switching path and label switching router | |
| CN102055619A (en) | Method and system for realize fault detection in bidirectional path segment | |
| EP2442494A1 (en) | Method and network device for associated channel capability negotiation | |
| CN100563140C (en) | The method of a kind of multicast network system and detection multicast network link defective | |
| CN102185719A (en) | Service link tracking realization method and device | |
| CN100454900C (en) | Method and system for quick responding IP banding message | |
| CN101729201B (en) | Method for detecting signal degradation defect | |
| CN104350706A (en) | Oam power packet | |
| US8599680B2 (en) | Virtual circuit configuration 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 | ||
| CP03 | Change of name, title or address | ||
| CP03 | Change of name, title or address |
Address after: 310052 Binjiang District Changhe Road, Zhejiang, China, No. 466, No. Patentee after: Xinhua three Technology Co., Ltd. Address before: 310053 Hangzhou hi tech Industrial Development Zone, Zhejiang province science and Technology Industrial Park, No. 310 and No. six road, HUAWEI, Hangzhou production base Patentee before: Huasan Communication Technology Co., Ltd. |