CN107645401A

CN107645401A - The detection of multiprotocol label switching, processing method, apparatus and system

Info

Publication number: CN107645401A
Application number: CN201610587250.9A
Authority: CN
Inventors: 彭少富
Original assignee: ZTE Corp
Current assignee: ZTE Corp
Priority date: 2016-07-22
Filing date: 2016-07-22
Publication date: 2018-01-30

Abstract

The invention provides a kind of detection of multiprotocol label switching, processing method, apparatus and system, wherein, the detection method of multiprotocol label switching includes：Detection initiator, which sends back, answers request message, wherein, responding request message includes being used to indicate the MPLS Alert Label of the response request message forwarding control plane；Detection initiator receives the response response message that transmission node or Egress node feed back under the triggering of the response request message, and detect whether the response response message matches with prestored information, by the present invention, solve the problems, such as in correlation technique P2P LSP functions and P2MP LSP detections it is poorly efficient with it is insufficient.

Description

The detection of multiprotocol label switching, processing method, apparatus and system

Technical field

The present invention relates to the communications field, in particular to a kind of detection of multiprotocol label switching, processing method, dress Put and system.

Background technology

In correlation technique, and P2P (peer to peer) label switched path (Label Switching Path, referred to as LSP) there is the problem of function in ping/trace standards：

1) according to rfc4379, when the target FEC of detection have ECMP, drawn by simulating load sharing in control plane It is multiple bursts to divide multipath information, is then based on the multiple echo request of division result transmission and (wraps respectively Containing different multipath information bursts) with it is expected travel through out complete path.Existing key issue is：a) It is identical that the simulation load sharing result of control plane not necessarily shares result with the actual load of datum plane；B) it is original Multipath information possibly can not meet the burst demand of load sharing, that is, the problem of not enough dividing be present.These are all Cause function.In fact, LSP ping essential requirement be detection data-plane connectivity and ensure datum plane with The forwarding-table item of control plane is consistent, as long as we are by multiprotocol label switching (Multi-protocol Label Switching, referred to as MPLS) Operations, Administration and Maintenance (Operation Administration and Maintenance, referred to as OAM) the strict true load sharing forwarding according to datum plane of message.

2) according to rfc6424, if forwarding equivalence class change (Forwarding Equivalence occur in detection process Class change, abbreviation FEC change), it is necessary to which the node for perceiving FEC change returns to FEC to Initiator nodes Change information, so that Initiator carries the target FEC stack after change in follow-up echo request.But The defects of standard has one substantially is to be only applicable to traceroute patterns, and perceives FEC change's during ping patterns Node is will not to return to FEC change information to Initiator nodes, it means that as long as to be held there occurs FEC change Row LSP ping will obtain the obstructed result in path.

In correlation technique, there is following detection in P2MP (peer to multiple peer) LSP ping/trace standards The problem of poorly efficient and insufficient：

1) initiate next after whether collecting according to rfc6425, the inaccurate control echo reply messages of Initiator Secondary echo request, that is to say, that it is indefinite to send the opportunity of request next time.If Initiator often receives one Individual echo reply just send next echo request, then it need to cache substantial amounts of history echo request so as to Wait the echo reply that those evenings arrive.

2) because echo request transmission does not control strictly, then the echo reply received may break out and Cause congestion.Although solution method is proposed, and it is imperfect.Such as return echo reply when random delay method Slow detection process can be dragged；Only allow specific node to return echo reply method then only to support to specify individual node or specify to single Egress along circuit node.

3) due to " Address in the Downstream Detailed Mapping TLV that are included in echo request Type " fields are arranged to IPv4Unnumbered or IPv6Unnumbered, and " Downstream IP Address " fields are set For ALLROUTERS multicast address, then cause that incoming interface consistency check can not be done on responder nodes, can not close inspection Whether the forwarding information of control plane and Forwarding plane is consistent.

Poorly efficient asked for P2P LSP functions present in correlation technique and P2MP LSP detections with insufficient Topic, at present it is not yet found that the solution of effect.

The content of the invention

The invention provides a kind of detection of multiprotocol label switching, processing method, apparatus and system, at least to solve phase P2P LSP functions and P2MP LSP detect the problem of poorly efficient and insufficient in the technology of pass.

A kind of according to an aspect of the invention, there is provided detection method of multiprotocol label switching, it is characterised in that bag Include：

Detection initiator, which sends back, answers request message, wherein, the response request message includes being used to indicate by described in Respond the MPLS Alert Label of request message forwarding control plane；

Detection initiator receives the response that transmission node or Egress node feed back under the triggering of the response request message Response message, and detect whether the response response message matches with prestored information.

Alternatively, also include in the response request message：Downstream map information, wherein, the downstream map information pair One or more next-hops route of request message is responded described in Ying Yu.

Alternatively, sending back answers request message also to include：Judge it is described response request message whether be start node first The response request message of transmission；In the case where the judgment result is yes, send back answer request message when, in the start node It is local to preserve the downstream map information responded in request message.

Alternatively, in judged result in the case of no, send back answer request message when, it is local in the start node Preserve the downstream map information carried in last round of response response message.

Alternatively, the MPLS Alert Label are encapsulated in the top label stack of the response request message.

Alternatively, detect response response message and the prestored information whether match including：Detect the response response report Whether Sender's Handle and first respective field responded in request message in text match, and described in detection Respond the sequence number in response message and whether second respective field responded in request message matches；Described Sender's Handle match with first respective field, and when the sequence number matches with second respective field, sentence The downstream map information that the disconnected Upstream Interface information responded in response message locally preserves with the start node whether Match somebody with somebody, the Upstream Interface information in the response response message matches with the downstream map information that the start node locally preserves When, determine that the response response message matches with prestored information.

Alternatively, when locally preserving multiple downstream map informations, the Upstream Interface in the response response message is judged Information and the downstream map information whether match including：Whether the multiple downstream map information for judging locally to preserve has The corresponding response response message matching；The multiple downstream map information for judging locally to preserve should with multiple responses Answer message the match is successful whether rate is more than predetermined threshold value.

Alternatively, whether after detecting the response response message and being matched with prestored information, methods described also includes：Root Determine whether with the testing result whether prestored information matches to send next response request message according to the response response message.

According to another aspect of the present invention, there is provided a kind of processing method of multiprotocol label switching, including：

It is received back to and answers request message, wherein, the response request message includes being used to indicate to respond request report by described The MPLS Alert Label of text forwarding control plane；

The response request message is forwarded to by control plane according to the MPLS Alert Label；

The response request message is handled according to default forwarding-table item.

Alternatively, handling the response request message according to default forwarding-table item includes one below：

According to the first default forwarding-table item feedback response response message for responding request message；

According to the first default forwarding-table item modification content for responding request message, and according to the second default forwarding-table item The response request message is forwarded to the next-hop node of datum plane.

Alternatively, included according to the first default forwarding-table item modification content for responding request message：Modification is described to return Answer the contents such as target FEC stacks and the downstream map information in request message.

According to another aspect of the present invention, there is provided a kind of detection means of multiprotocol label switching, applied to detection Initiator, including：

Sending module, request message is answered for sending back, wherein, the response request message includes being used to indicate institute State the MPLS Alert Label for responding request message forwarding control plane；

Detection module, time fed back for receiving transmission node or Egress node under the triggering of the response request message Response message is answered, and detects whether the response response message matches with prestored information.

According to another aspect of the present invention, there is provided a kind of processing unit for responding request message, including：

Receiving module, request message is answered for being received back to, wherein, the response request message includes being used to described to return Answer the MPLS Alert Label of request message forwarding control plane；

Forwarding module is flat for the response request message to be forwarded into control according to the MPLS Alert Label Face；

Processing module, for handling the response request message according to default forwarding-table item.

According to another aspect of the present invention, there is provided a kind of detecting system of multiprotocol label switching, including initial section Point, transmission node or Egress node, the start node also include：

Detection module, time fed back for receiving transmission node or Egress node under the triggering of the response request message Response message is answered, and detects whether the response response message matches with prestored information；

Transmission node or Egress node also include：

According to another aspect of the present invention, a kind of storage medium is additionally provided.The storage medium is arranged to storage and is used for Perform the program code of following steps：

Send back and answer request message, wherein, the response request message includes being used to indicate to respond request report by described The MPLS Alert Label of text forwarding control plane；

The response response message that transmission node or Egress node feed back under the triggering of the response request message is received, and Detect whether the response response message matches with prestored information.

By the present invention, send back and answer request message, wherein, the response request message includes being used to indicate by described in Respond the MPLS Alert Label of request message forwarding control plane；Receiving transmission node or Egress node please in the response The response response message fed back under the triggering of message is sought, and detects whether the response response message matches with prestored information.By In carried in request message is responded MPLS Alert Label so as to by it is described response request message forwarding control plane, and Message is voluntarily changed according to actual forwarding information by control plane, meanwhile, detection respond response message and prestored information whether With equivalent to entry consistency detection has been done, therefore, can solve P2P LSP functions and P2MP LSP in correlation technique The problem of poorly efficient and insufficient is detected, improves detection efficiency and the degree of accuracy.

Brief description of the drawings

Accompanying drawing described herein is used for providing a further understanding of the present invention, forms the part of the application, this hair Bright schematic description and description is used to explain the present invention, does not form inappropriate limitation of the present invention.In the accompanying drawings：

Fig. 1 is the flow chart of the detection method of multiprotocol label switching according to embodiments of the present invention；

Fig. 2 is the flow chart of the processing method of multiprotocol label switching according to embodiments of the present invention；

Fig. 3 is the structured flowchart of the detection means of multiprotocol label switching according to embodiments of the present invention；

Fig. 4 is the structured flowchart of the processing unit of multiprotocol label switching according to embodiments of the present invention；

Fig. 5 is the structured flowchart of the detecting system of multiprotocol label switching according to embodiments of the present invention；

Fig. 6 is the LSP ping echo request/reply message format figures according to the specific embodiment of the invention；

Fig. 7 is the format chart according to the Downstream Mapping TLV of the specific embodiment of the invention；

Fig. 8 is the format chart according to the Upstream Interface TLV of the specific embodiment of the invention；

Fig. 9 is the format chart according to the Responder Egress TLV of the specific embodiment of the invention；

Figure 10 is the format chart according to the Responder Transit TLV of the specific embodiment of the invention；

Figure 11 is the flow that echo request messages are sent according to the Initiator nodes of the specific embodiment of the invention Figure；

Figure 12 is to receive echo request messages according to Transit the or Egress nodes of the specific embodiment of the invention Flow chart；

Figure 13 is the flow that echo reply messages are sent according to the Responder nodes of the specific embodiment of the invention Figure；

Figure 14 is the flow that echo reply messages are received according to the Initiator nodes of the specific embodiment of the invention Figure；

Figure 15 is the network topological diagram according to the preferred embodiment of the present invention 1；

Figure 16 is the network topological diagram according to the preferred embodiment of the present invention 2；

Figure 17 is the network topological diagram according to the preferred embodiment of the present invention 3.

Embodiment

Describe the present invention in detail below with reference to accompanying drawing and in conjunction with the embodiments.It should be noted that do not conflicting In the case of, the feature in embodiment and embodiment in the application can be mutually combined.

It should be noted that term " first " in description and claims of this specification and above-mentioned accompanying drawing, " Two " etc. be for distinguishing similar object, without for describing specific order or precedence.

Embodiment 1

A kind of detection method of multiprotocol label switching is provided in the present embodiment, and Fig. 1 is according to embodiments of the present invention Multiprotocol label switching detection method flow chart, as shown in figure 1, the flow comprises the following steps：

Step S102, detection initiator, which sends back, answers request message, wherein, response request message includes will for instruction Respond the MPLS Alert Label of request message forwarding control plane；

Step S104, detection initiator receive what transmission node or Egress node fed back in the case where responding the triggering of request message Response message is responded, and detects and responds whether response message matches with prestored information.

By above-mentioned steps, send back and answer request message, wherein, responding request message includes being used to indicate described to return Answer the MPLS Alert Label of request message forwarding control plane；Receive transmission node or Egress node and respond request described The response response message fed back under the triggering of message, and detect whether the response response message matches with prestored information.Due to Carried in request message is responded MPLS Alert Label so as to by it is described response request message forwarding control plane, and by Control plane voluntarily changes message, and a whole set of corresponding detection procedure according to actual forwarding information, therefore, can solve Certainly in correlation technique P2P LSP functions and P2MP LSP detection it is poorly efficient and insufficient the problem of improve detection efficiency and The degree of accuracy.

Optionally, respond also includes in request message：Downstream map information, wherein, downstream map information, which corresponds to, to be responded One or more next-hops route of request message.

Request message is answered also to include specifically, sending back：

S11, judge to respond whether request message is response request message that start node is sent first；

S12, in the case where the judgment result is yes, send back answer request message when, start node locally preserve back Answer the downstream map information in request message.In judged result in the case of no, send back answer request message when, initial Node locally preserves the last round of downstream map information responded and carried in response message.

Optionally, MPLS Alert Label are encapsulated in the top label stack of the response request message.

Optionally, detection is responded response message and specifically included with whether prestored information matches：

S21, detection respond the Sender's Handle in response message and respond the first respective field in request message Whether match, and detection respond response message in sequence number and respond request message in the second respective field whether Match somebody with somebody；

S22, matched in Sender's Handle with the first respective field, and when sequence number matches with the second respective field, Whether the Upstream Interface information for judging to respond in response message matches with the downstream map information that start node locally preserves, and is returning When answering the Upstream Interface information in response message to be matched with the downstream map information that start node locally preserves, it is determined that responding response Message matches with prestored information.

Optionally, when locally preserving multiple downstream map informations, judge to respond the Upstream Interface information in response message Whether matched including following two modes with downstream map information：

The multiple downstream map informations for judging locally to preserve respond response message matching corresponding to whether having；

Judge multiple downstream map informations for locally preserving respond response messages the match is successful whether rate is more than with multiple Predetermined threshold value.

A kind of processing method of multiprotocol label switching is additionally provided in the present embodiment, with above-mentioned multiprotocol label switching Detection method it is corresponding, can apply in transmission node or Egress node, Fig. 2 is multi-protocols mark according to embodiments of the present invention The flow chart of the processing method exchanged is signed, as shown in Fig. 2 the flow comprises the following steps：

Step S202, is received back to and answers request message, wherein, responding request message includes being used to indicate that request report will be responded The MPLS Alert Label of text forwarding control plane；

Step S204, control plane is forwarded to by request message is responded according to MPLS Alert Label；

Step S206, handled according to default forwarding-table item and respond request message.

Optionally, being forwarded back to according to default forwarding-table item answers request message to include one below：

The response response message for answering request message is fed back to according to the first default forwarding-table item；

The content of request message is responded according to the first default forwarding-table item modification, and will be returned according to the second default forwarding-table item Request message is answered to be forwarded to the next-hop node of datum plane.

Optionally, the content for responding request message according to the first default forwarding-table item modification includes：Request report is responded in modification The contents such as target FEC stacks and downstream map information in text.

Through the above description of the embodiments, those skilled in the art can be understood that according to above-mentioned implementation The method of example can add the mode of required general hardware platform to realize by software, naturally it is also possible to by hardware, but a lot In the case of the former be more preferably embodiment.Based on such understanding, technical scheme is substantially in other words to existing The part that technology contributes can be embodied in the form of software product, and the computer software product is stored in a storage In medium (such as ROM/RAM, magnetic disc, CD), including some instructions to cause a station terminal equipment (can be mobile phone, calculate Machine, server, or network equipment etc.) method that performs each embodiment of the present invention.

Embodiment 2

The detection means and processing unit of a kind of multiprotocol label switching are additionally provided in the present embodiment, for realization Embodiment and preferred embodiment are stated, had carried out repeating no more for explanation.As used below, term " module " can be with Realize the combination of the software and/or hardware of predetermined function.Although the device described by following examples is preferably come real with software It is existing, but hardware, or the realization of the combination of software and hardware is also what may and be contemplated.

Fig. 3 is the structured flowchart of the detection means of multiprotocol label switching according to embodiments of the present invention, as shown in figure 3, The device is applied to detection initiator, including：

Sending module 30, request message is answered for sending back, wherein, responding request message includes being used to indicate to respond Request message forwards the MPLS Alert Label of control plane；

Detection module 32, the response fed back for receiving transmission node or Egress node in the case where responding the triggering of request message Response message, and detect and respond whether response message matches with prestored information.

Fig. 4 is the structured flowchart of the processing unit of multiprotocol label switching according to embodiments of the present invention, as shown in figure 4, The device includes：

Receiving module 40, request message is answered for being received back to, wherein, responding request message includes being used to respond asking Message forwards the MPLS Alert Label of control plane；

Forwarding module 42 is flat for the response request message to be forwarded into control according to the MPLS Alert Label Face；

Processing module 44, for handling the response request message according to default forwarding-table item.

Fig. 5 is the structured flowchart of the detecting system of multiprotocol label switching according to embodiments of the present invention, as shown in figure 5, The system includes：Including Initiator start nodes 50, Transit transmission nodes 52 or Egress Egress nodes 52,

Start node 50 also includes：

Sending module 502, request message is answered for sending back, wherein, responding request message includes being used to indicate to return Answer the MPLS Alert Label of request message forwarding control plane；

Detection module 504, fed back for receiving transmission node or Egress node under the triggering of the response request message Response response message, and detect it is described response response message whether matched with prestored information；

Transmission node 52 or Egress node 52 also include：

Receiving module 522, request message is answered for being received back to, wherein, the response request message includes being used for institute State the MPLS Alert Label for responding request message forwarding control plane；

Forwarding module 524, for the response request message to be forwarded into control according to the MPLS Alert Label Plane；

Processing module 526, for handling the response request message according to default forwarding-table item.

By the above-mentioned technical proposal of the present embodiment, send back and answer request message, wherein, wrapped in the response request message Include for indicating the MPLS Alert Label of the response request message forwarding control plane；Receive transmission node or outlet The response response message that node feeds back under the triggering of the response request message, and the response response message is detected with prestoring Whether information matches.Due to carrying MPLS Alert Label in request message is responded so as to by the response request message Control plane is forwarded, and is voluntarily changed at message, and a whole set of corresponding detection according to actual forwarding information by control plane Flow is managed, therefore, P2P LSP functions can be solved in correlation technique and P2MP LSP detections is poorly efficient is asked with insufficient Topic, improves detection efficiency and the degree of accuracy.

It should be noted that above-mentioned modules can be realized by software or hardware, for the latter, Ke Yitong Cross in the following manner realization, but not limited to this：Above-mentioned module is respectively positioned in same processor；Or above-mentioned modules are with any The form of combination is located in different processors respectively.

Embodiment 3

During this implementation according to an alternative embodiment of the invention, it is specific to the application progress detailed for combining specific scene Explanation：

The method of the MPLS LSP detections of the present embodiment comprises the following steps：

The first step：

Initiator nodes are when sending echo request (responding request) message, wherein can include multiple Downstream Mapping TLVs (Type Length Value, Type Length character), each Downstream Mapping Corresponding that the to be sent to next-hops of TLV.During P2P LSP even if exist ECMP also only in echo request include one Downstream Mapping TLV, and it is corresponding comprising multiple multicast member next-hops in echo request during P2MP LSP Multiple Downstream Mapping TLVs.

, it is necessary to preserve the Downstream of corresponding next-hop when Initiator sends first run echo request Mapping information, accurately matched for use in follow-up echo reply.During non-first echo request, Initiator What is preserved is the Downstream Mapping information copied in last round of echo reply.

The Downstream Mapping TLVs included in the echo request that Initiator is sent are pair all the time The next-hop that should be sent to, it is unrelated with the echo reply being successfully received.

Initiator needs the top label stack in echo request messages to additionally insert MPLS Alert Label.

Second step：

The datum plane of Transit nodes or Egress nodes is according to the stack top marks of the echo request messages received Sign MPLS Alert Label and by message up sending control plane.Control plane unpacks and is the discovery that LSP ping bags, then basis MPLS Alert Label search label forwarding list item with the service label of lower floor, if (TTL's takes the TTL=1 of service label Value is between 1-255) then to Initiator node reverts back echo reply, otherwise repaiied based on the next-hop that forwarding-table item provides After changing the information such as target FEC stack TLV and the Downstream Mapping TLVs in echo request messages, Again echo request messages are thrown into datum plane, label forwarding list item is searched according to service label by datum plane again After forward, control plane specify datum plane continue to additionally insert MPLS Alert Label in the top label stack to E-Packet.

3rd step：

After Initiator nodes receive Responde node echo reply, first according in echo reply Sender's Handle match with the respective field in Sequence Number and echo request, then according to echo Upstream Interface TLV in reply and the Downstream Mapping information matches locally preserved, to determine Whether all Downstream Mapping information locally preserved have corresponding echo reply to match, and deciding whether can be with Next echo request are sent, default policy is that all Downstream Mapping information locally preserved have accordingly Echo reply matching after just send next echo request, as long as can also take strategy locally preserve If next echo request can be transmitted more than certain threshold values in Downstream Mapping information matches success accounting, Or other strategies.Initiator is before the echo request of next round are sent, again from the echo that these have matched Downstream Mapping information is obtained in reply and is preserved, for the echo reply matchings with next round.

Using the technical scheme of the embodiment of the present invention, compared with prior art, P2P LSP and P2MP LSP are unified and have detected Flow, overcome P2P LSP functions present in prior art and P2MP LSP to detect the problem of poorly efficient and insufficient And defect, improve detection efficiency and the degree of accuracy.

The implementation to technical scheme is described in further detail below in conjunction with the accompanying drawings：

Fig. 6 is the LSP ping echo request/reply message format figures according to the specific embodiment of the invention, its Definition is identical with rfc4379, and here is omitted.

Fig. 7 is according to the Downstream Mapping TLV of specific embodiment of the invention format chart, wherein deleting Field related on multipath information Downstream Mapping TLV, is remained in rfc4379 Field definition and rfc4379 it is essentially identical, except：

1) three marks are increased in DS Flags newly：

E indicates：It is arranged to 1 and shows that next-hop corresponding to the Downstream Mapping TLV is ECMP member.For In echo reply.

M indicates：It is arranged to 1 and shows that next-hop corresponding to the Downstream Mapping TLV is multicast member.For In echo reply.

R indicates：It is arranged to 1 and shows that next-hop corresponding to the Downstream Mapping TLV is indirectly connected.For In echo request/reply.

2) Downstream Labels only refer to label corresponding to each FEC in target FEC stack, not comprising it is other more Outer layer label.

Fig. 8 is according to the Upstream Interface TLV of specific embodiment of the invention format chart, wherein deleting The related field of label information in Interface and Label Stack TLV in rfc4379, the field remained Define essentially identical with rfc4379.

Fig. 9 is that Figure 10 is basis according to the Responder Egress TLV of specific embodiment of the invention format chart The Responder Transit TLV of specific embodiment of the invention format chart, Egress and Transit nodes to Can include the address information of itself during Initiator node reverts back echo reply, so as to Initiator node evaluations whether Echo reply are all have received from desired node.

The present embodiment has also used the Target FEC Stack TLV defined in rfc4379, does not make an amendment.

Next we introduce lower echo request and echo reply messages specific transmitting-receiving flow.

Figure 11 is the flow that echo request messages are sent according to the Initiator nodes of the specific embodiment of the invention Figure, including

Step S601, Initiator node initiate the LSP ping or LSP for some target FEC Traceroute flows, then construct echo request messages.

Step S602, Initiator node is according to being constructed as below echo request PDU (Protocol Data Unit, protocol Data Unit)：

1) an a Sender's Handle and Sequence Number is selected, when continuously transmitting echo request When, Sequence Number are incremented by one.If pay attention to ECMP (Equal-Cost Multipath during P2P LSP being present Routing, equal-cost route), then echo request an ECMP member can only be sent thereto；And then can be to during P2MP LSP Each multicast member is sent, in the echo request that any wheel is sent to each multicast member in such cases simultaneously Sequence Number are identicals.

2) TimeStamp Sent fields are arranged to the relative time in one day, second and microsecond.

3) TimeStamp Received fields are arranged to 0.

4) Reply Mode are arranged to desired pattern, show to wish that certain mode returns echo reply along IP or other To Initiator nodes.Return Code and Subcode is arranged to 0.

5) target FEC stack TLV are included, represent detected target FEC.

6) during traceroute patterns, comprising Downstream Mapping TLV, the corresponding next-hop being sent to.DS Flags stamps I marks, shows to wish that responder nodes include Upstream Interface when replying echo reply TLV.Here next-hop refers to that top layer target FEC's in Initiator nodes up to target FEC stack is next Jump.Particularly when the forwarding-table item that Initiator nodes are found to top layer target FEC will enter the PIPE types of more outer layer During tunnel, then refer to the distal end next-hop before iteration Tunnel iteration, now the R traffic sign placements in DS Flags are effective；To Into more outer layer UNIFORM type tunnels when, then refer to the next-hop after iteration Tunnel iteration, now the R in DS Flags Traffic sign placement is invalid, and now Initiator can continue into the UNIFORM tunnels in target FEC stack top layers FEC。

Step S603, Initiator node is according to being constructed as below IP/UDP heads：

1) source IP is one routable IP address of transmitting terminal

2) purpose IP randomly chooses from 127/8, or from 0:0:0:0:0:FFFF:Randomly choosed in 127/104

3) IP TTL=1

4) source PORT is selected by transmitting terminal

5) purpose PORT is 3503

6) Router Alert option must be provided with

Step S604, Initiator node are echo request message encapsulated tags stacks, include target FEC Label corresponding to stack and any possible more outer layer tunnel label.

Step S605, Initiator node maintenance target responder identifiers, represent which expectation receives One of the echo replys of a little node reverts backs, the foundation for detecting whether to finish as follow-up judgement.

Step S606, Initiator node judges whether it is first run echo request.

Step S607, if first run echo request, then preserve the first run echo request next-hops to be sent to Corresponding Downstream Mapping information, for accurately matching next round echo reply.

During P2P LSP, refer to that top layer target FEC's in Initiator nodes up to target FEC stack is next Jump, if multiple next-hops form ECMP, echo request also only can be sent to one of next-hop, so Initiator need to only preserve Downstream Mapping information corresponding to this next-hop, and wherein DS Flags stamp E marks Will.As described in step 602, next-hop here will be according to whether the PIPE/UNIFORM types into more outer layer tunnel be true together It is fixed.

During P2MP LSP, refer in Initiator nodes up to target FEC multicast forwarding list item each multicast into Downstream Mapping information corresponding to member, Initiator need to preserve multiple Downstream Mapping information, its Middle DS Flags have stamped M marks.

Step S608, if not first run echo request, then preserve and obtained from the echo replys of last round of matching The Downstream Mapping information taken, for accurately matching next round echo reply.The echo of last round of matching Replys refers to those echo replys that echo request are matched in last round of echo request/reply flows, The Upstream Interface TLV that particularly these echo replys are included indicate them and saved with Initiator at that time The Downstream Mapping information that point preserves is matching, is specifically shown in following Initiator nodes and receives echo The flow of reply messages.

During P2P LSP, refer on Responder nodes for target FEC stack from top layer to bottom conduct first Next-hop corresponding to the target FEC (being designated as First Transit FEC) of transit nodes, if next-hop has multiple shapes Into ECMP, then multiple Downstream Mapping TLVs can be included in echo reply, wherein DS Flags have stamped E Mark, Initiator need to preserve multiple Downstream Mapping information.Particularly when Responder nodes find to When First Transit FEC forwarding-table item will enter the tunnel of more outer layer, it is also required to according to entrance more outer layer tunnel PIPE/UNIFORM types determine next-hop together, and the processing with the Initiator nodes described in preceding step 602 is similar , i.e., when the forwarding-table item that Responder nodes are found to First Transit FEC will enter the PIPE type tunnels of more outer layer During road, then refer to the distal end next-hop before iteration Tunnel iteration, now the R traffic sign placements in DS Flags are effective；To enter When entering the UNIFORM type tunnels of more outer layer, then refer to the next-hop after iteration Tunnel iteration, now the R marks in DS Flags Will is arranged to invalid.If First Transit FEC are not present, without including Downstream in echo reply Mapping TLV。

During P2MP LSP, refer in Responder nodes up to target FEC multicast forwarding list item each multicast into Downstream Mapping information corresponding to member, multiple Downstream Mapping TLVs can be included in echo reply, Wherein DS Flags have stamped M marks, and Initiator needs to preserve multiple Downstream Mapping information.

Step S609, Initiator start timer, wait echo reply.

Figure 12 is to receive echo request messages according to Transit the or Egress nodes of the specific embodiment of the invention Flow chart, including：

Step S701, Transit or Egress node receives echo request.

Step S702, datum plane are that MPLS Router Alert label send whole wrap of message according to stack top label To control plane.

Step S703, control plane, which unpacks, finds LSP ping bags, then after peeling MPLS Router Alert label off, Continue the label stack parsing action parsing label stack and IP heads according to standard, check whether following either condition exposes：

a)Router Alert option

b)IP TTL expiration

c)MPLS TTL expiration

d)MPLS Router Alert label

E) the purpose IP of 127/8 scope

The exposure of any of the above condition all represents to need to reply echo reply, otherwise needs to throw to datum plane hair after changing bag Send.

Step S704, judge whether to need reply echo reply still to need to throw to datum plane transmission after changing bag.

Step S705, if necessary to reply echo reply.

Control plane processing：

1) whether inspection tag value is effective, if corresponding ILM be present.Corresponding label behaviour is write down during traceroute Make, for filling in follow-up echo reply.

2) check next hop information in Downstream Mapping TLVs whether the incoming interface reached with message Match somebody with somebody.A Downstream Mapping TLV can be only included during P2P LSP, in echo request, it is necessary to check therein Whether the incoming interface reached with message matches next hop information；It can be included during P2MP LSP, in echo request multiple Downstream Mapping TLVs are, it is necessary to check any Downstream Mapping TLV next hop information and message The incoming interface matching of arrival.

3) check whether the label stack of message and target FEC stack are consistent.Due to Downstream Mapping Label corresponding to FEC in target FEC stack is contains only in TLV, so needing according to Downstream Mapping In the target FEC stack included in TLV the label number of plies corresponding to FEC according to the order from bottom to top layer from message The label of the corresponding number of plies is obtained in label stack, for doing consistency check with target FEC stack.During inspection, top is first checked Layer FEC, if top layer FEC shows to reach Egress nodes, continues checking for next layer of FEC, does not otherwise reexamine next layer FEC。

Step S706, judge that above-mentioned check whether all succeeds.

Step S707, inspection result are successfully.

1) it is corresponding with Return Subcode settings to Initiator node reverts back echo reply, Return Code Success return code.Include Upstream Interface TLV, Responder Egress TLV or Responder Transit TLV。

2) when Responder nodes are Transit, Downstream can also be contained according in echo request Mapping TLV and Downstream Mapping TLVs are included in ehco reply, stamp as needed E/M/R mark. During P2P LSP, refer to the next-hop of First Transit FEC in Responder nodes up to target FEC stack, such as Described in step 608, next-hop here will be according to whether the PIPE/UNIFORM types into more outer layer tunnel determine together, i.e., When the forwarding-table item that Responder nodes are found to First Transit FEC will enter the PIPE type tunnels of more outer layer, Then refer to the distal end next-hop before iteration Tunnel iteration, now the R traffic sign placements in DS Flags are effective；It is outer to entrance During the UNIFORM type tunnels of layer, then refer to the next-hop after iteration Tunnel iteration, now the R traffic sign placements in DS Flags To be invalid.If next-hop there are multiple formation ECMP, multiple Downstream Mapping can be included in echo reply TLVs, wherein DS Flags have stamped E marks.During P2MP LSP, refer to Responder nodes up to target FEC group Each Downstream Mapping information corresponding to multicast member in forwarding-table item is broadcast, can be included in echo reply multiple Downstream Mapping TLVs, wherein DS Flags have stamped M marks.

Step S708, inspection result are failure.

Lost to Initiator node reverts back echo reply, Return Code are corresponding with Return Subcode settings Lose return code.Include Upstream Interface TLV.

Step S709, if echo reply need not be replied, but need to throw to datum plane after changing bag and continue to forward.

Control plane processing：

According to forwarding information corresponding to First Transit FEC in target FEC stack, change in message Target FEC stack and Downstream Mapping TLVs, it is up that message is then thrown into datum plane, and specify number Continue according to plane in forwarding in outer layer additional package MPLS Router Alert label.

It is that bag is changed according to the next-hop of the First Transit FEC into target FEC stack during P2P LSP, As described in step 608, next-hop here will according to whether the PIPE/UNIFORM types into more outer layer tunnel determine together, I.e. when the forwarding-table item found to First Transit FEC will enter the PIPE type tunnels of more outer layer, then refer to iteration Distal end next-hop before Tunnel iteration, now the R traffic sign placements in DS Flags are effective；To enter more outer layer During UNIFORM type tunnels, then refer to the next-hop after iteration Tunnel iteration, now the R traffic sign placements in DS Flags are nothing Effect.If next-hop there are multiple formation ECMP, multiple Downstream can be included in amended echo request Mapping TLVs, wherein DS Flags have stamped E marks.During P2MP LSP, refer to target FEC multicast forwarding Each Downstream Mapping information corresponding to multicast member in list item, it can include in amended echo request more Individual Downstream Mapping TLVs, wherein DS Flags have stamped M marks.

In addition, if node finds that the R marks in the Downstream Mapping TLV before modification are effective, it is needed Compare whether the distal end next-hop specified in the Downstream Mapping TLV is oneself, only just need to press for oneself Downstream Mapping TLV are changed according to flow as above, are not otherwise changed.

Step S710, the up normal forwarding of tabling look-up of datum plane, in top label stack additional package MPLS Router again Alert label。

Figure 13 is the flow that echo reply messages are sent according to the Responder nodes of the specific embodiment of the invention Figure, including：

Step S801, Transit or Egress node is according to the place after control plane is sent on the echo request received Result is managed, as responder node reverts back echo reply.

Step S802, according to Echo reply PDU are constructed as below：

1) Sender's Handle, Sequence Number, TimeStamp Sent copy from request messages.

2) TimeStamp Received fields are arranged to the relative time in one day, second and microsecond.

3) target FEC Stack TLV can copy from request messages.

4) Return Code and Subcode must be set according to the result for receiving request.

5) Upstream Interface TLV, Responder Egress TLV or Responder Transit are included TLV。

6) when Responder nodes are Transit, Downstream Mapping TLVs can also be included, as needed Stamp E/M/R marks.As described in step 707, here Downstream Mapping TLVs next-hop be according to whether into What the PIPE/UNIFORM types of more outer layer tunnel determined together, here is omitted.

Step S803, according to IP/UDP is constructed as below：

1) source IP is one, Responder ends routable IP address

2) purpose IP copies source IP from request messages or copied from Reply-to TLV.

3) IP TTL=255

4) source PORT is 3503

5) purpose PORT copies source PORT from request messages

6)Router Alert option：It is " Reply via an that if reply mode are indicated in request IPv4UDP packet with Router Alert ", then Router Alert option must be included, now if return LSP is walked, then top layer label is Router Alert label (1)

Figure 14 is the flow that echo reply messages are received according to the Initiator nodes of the specific embodiment of the invention Figure, including：

Step S901, Initiator node receives echo reply messages.

Step S902, Initiator obtain the Sender's Handle and Sequence in echo reply messages Number, Sender's Handle corresponding with the echo request locally preserved match with Sequence Number.

Step S903, checks whether echo reply match with echo request.

Step S904, if it does not match, abandoning echo reply.

Step S905, if it does, then continuing to obtain in echo reply messages in traceroute patterns Upstream Interface TLV, matched with the Downstream Mapping information locally preserved.Check whether local All Downstream Mapping information preserved have corresponding echo reply to match.Contain the multiple of E marks Downstream Mapping only need to match one of them；It is required for matching containing M marks.During ping patterns, no Match, i.e., always think that the match is successful.

Step S906, wait the timer expiry for being ready to use in and waiting and receiving echo reply.

Step S907, after timer expiry, check whether as ping patterns.

Step S908, if ping patterns, then whole detection process terminates, and reports testing result, such as which node Reply echo reply, whether desired recovery of node has all replied etc..Initiator can open next round as needed Repeat to detect.

Step S909, if traceroute patterns, then continue checking for the Downstream Mapping locally preserved Whether information all have matched, or only whether part matches but meet to fit through strategy, for example match Downstream Mapping accountings have exceeded certain threshold values.During P2P LSP, it may locally save and multiple stamp E marks The Downstream Mapping entries of will, as long as there is one can be matched with echo reply in these entries, then it is assumed that they All by have matched.During P2MP LSP, multiple Downstream Mapping bars for having stamped M marks may be locally saved Mesh, these entries need individually to match with different echo reply.

If the Downstream Mapping matchings locally preserved are not over whole detection process terminates, report Testing result.

Step S910, if the Downstream Mapping locally preserved are fitted through, continue checking for it is expected back Whether multiple echo reply node has all replied echo reply.

If it is desire to nodes revert echo reply, then whole detection process terminates, and reports testing result.

Step S911, if also some desired nodes do not reply echo reply, continue checking for all echo Either with or without including any Downstream Mapping TLV in reply.

If all not comprising any Downstream Mapping TLV in all echo reply, then whole detection Process terminates, and reports testing result.

Step S912, all Downstream Mapping information deletions that will locally preserve, from all echo reply It is middle to obtain new Downstream Mapping information, locally preserve for the echo reply matchings with next round.Under transmission One wheel echo request, label TTL increases 1.Sender's Handle are constant, and Sequence Number increase 1.Other references Initiator nodes send the flow of echo request messages.

A kind of MPLS LSP detection methods are specifically introduced with reference to multiple preferred embodiments.

Preferred embodiment 1

The present embodiment will describe P2P LSP testing process, and Figure 15 is the network topology according to the preferred embodiment of the present invention 1 Figure, as shown in figure 15, A establish the LDP LSP to egress nodes for H as ingress nodes, on transit nodes B, There is ECMP in LDP LSP, one of next-hop is distal end next-hop D and forms LDP over TE, TE-tunnel from tunnel Road head node to the path of tunnel destination node is B-C-D, and LDP LSP another next-hop is E on B node.

LSP traceroute LDP FEC H now are initiated in A nodes, the testing process comprises the following steps, is succinct For the sake of, main flow related to the present invention is only described：

Step S1001：First run echo request messages are constructed on A nodes, Echo request PDU are set：

target FEC stack TLV：{LDP FEC H}

Downstream Mapping TLV：{DS Flags：I=1, E/M/R=0；Downstream Address=B＆ B.port1}.B represents that Router-id, port1 represent interface IP, similarly hereinafter.

Encapsulate IP/UDP heads and label stack, stack top label LDP Label TTL=1.

Downstream Mapping entries are locally preserved on A nodes：{DS Flags：E/M=0；Downstream Address=B＆B.port1 }；

Step S1002：B node receives echo request messages, because label stack top-level tab is MPLS Router Alert Label cause to send control plane.In control plane, unpacking is the discovery that LSP ping bags, then peels MPLS Router off After Alert label, continue to parse label stack and IP heads, find current stack top label LDP Label TTL=1, meet need Reply echo reply exposure condition.

Then control plane further does FEC verifications：Check and find that label value is effective, corresponding ILM be present and mark Label operation is SWAP；Check and find that the incoming interface that the next hop information in Donstream Mapping TLV reaches with message is Matching；Check that the label stack for finding message and target FEC stack are consistent.

B node replys echo reply messages, including：

Upstream Interface TLV：{B&B.port1}

Responder Transit TLV：{B}

Downstream Mapping TLV1：{DS Flags：I=1, E=1, R=1；Downstream Address= D&D}.It is assumed here that TE tunnel are PIPE types.

Downstream Mapping TLV2：{DS Flags：I=1, E=1, R=0；Downstream Address= E&E.port1}。

Step S1003：A nodes receive the ehco reply of B node, check that it is to match to find with current echo request , and the Upstream Interface TLV in echo reply：{ B＆B.port1 } and the Downstream locally preserved Mapping entries：{DS Flags：E/M=0；Downstream Address=B＆B.port1 } it is matching.

A nodes obtain new Downstream Address information from echo reply and locally saved as：

Downstream Mapping entries 1：{DS Flags：E=1, R=1；Downstream Address=D＆D }

Downstream Mapping entries 2：{DS Flags：E=1, R=0；Downstream Address=E＆ E.port1}

A initiates next round echo request, similar step S1001, only stack top label LDP Label TTL=2. It is identical in the Downstream Mapping TLV particularly included and step S1001.

Step S1004：B node receives echo request messages, because label stack top-level tab is MPLS Router Alert Label cause to send control plane.In control plane, unpacking is the discovery that LSP ping bags, then peels MPLS Router off After Alert label, continue to parse label stack and IP heads, find current stack top label LDP Label and TTL=2 and conduct LDP LSP Transit nodes will not continue to parse next layer of label/IP, be unsatisfactory for needing the exposure for replying echo reply Condition.

Then control plane further changes bag：According to the Downstream Mapping TLV before modification in echo request In next-hop be B, and be actually subjected to according to message to be sent to distal end next-hop D, and TE tunnel by LDP over TE For PIPE types, and the Downstream Mapping TLV of message are revised as：{DS Flags：I=1, E=1, R=1； Downstream Address=D＆D }.FEC does not change, without changing target FEC stack TLV.Then will Message according to instruction additionally inserts MPLS Router Alert Label mode of giving out a contract for a project in stack top, and to throw to datum plane up.

The up current top-level tab LDP Label based on message of datum plane and TTL=2 are tabled look-up forwarding, and label is handed over The outgoing label LDP Label TTL got in return, which are pressed into after label TTL subtracts 1, is arranged to 1, and outer layer TE Label TTL are arranged to 255. Then additionally forwarded after top label stack insertion MPLS Router Alert Label.

Step S1005：C nodes receive echo request messages, because label stack top-level tab is MPLS Router Alert Label cause to send control plane.In control plane, unpacking is the discovery that LSP ping bags, then peels MPLS Router off After Alert label, continue to parse label stack and IP heads, find current stack top label TE Label and TTL=255 and conduct TE LSP transit nodes will not continue to parse next layer of label/IP, be unsatisfactory for needing the exposure bar for replying echo reply Part.

Then control plane further changes bag：According to the Downstream Mapping TLV before modification in echo request In next-hop be C, and R marks are effective, then C knows that it is in some outer layer tunnel, so to Downstream Mapping TLV do not make an amendment.Same FEC does not change, without modification target FEC stack TLV.Then will Message according to instruction additionally inserts MPLS Router Alert Label mode of giving out a contract for a project in stack top, and to throw to datum plane up.

The up current top-level tab TE Label based on message of datum plane and TTL=255 are tabled look-up forwarding, and label is handed over The outgoing label TE Label TTL got in return, which are pressed into after label TTL subtracts 1, is arranged to 254.Then additionally inserted in top label stack Forwarded after MPLS Router Alert Label.

Step S1006：D nodes receive echo request messages, because label stack top-level tab is MPLS Router Alert Label cause to send control plane.In control plane, unpacking is the discovery that LSP ping bags, then peels MPLS Router off After Alert label, continue to parse label stack and IP heads.When due to TE Label, either the last two jump is ejected or parsed It is found to be TE LSP Egress nodes and continues to connect down next layer of label so that current stack top label exposes as LDP Label And TTL=1, meet that needs reply echo reply exposure condition.

D node reverts back echo reply messages, including：

Upstream Interface TLV：{D&D.port1}

Responder Transit TLV：{D}

Downstream Mapping TLV1：{DS Flags：I=1, E=0, R=0；Downstream Address= H&H.port1}

Step S1007：A nodes receive the ehco reply of D nodes, check that it is to match to find with current echo request , and the Upstream Interface TLV in echo reply：{ D＆D.port1 } and the Downstream locally preserved Mapping entries 1：{DS Flags：E=1, R=1；Downstream Address=D＆D } it is matching.Here because R is marked Will is effective, only matches Router-id.Because the E marks of Downstream Mapping entries 2 are effective, then it is assumed that it Matching is passed through.

Downstream Mapping entries：{DS Flags：E=0, R=0；Downstream Address=H＆ H.port1}

A initiates next round echo request, similar step S1001, only stack top label LDP Label TTL=3. It is identical in the Downstream Mapping TLV particularly included and step S1001.

Step S1008：D nodes receive echo request messages, similar step S1004, and control plane changes message Datum plane forwarded upstream is thrown to after Downstream Mapping TLV.

Step S1009：D nodes receive echo request messages, similar step S1005, and control plane does not change message, Throw to datum plane forwarded upstream.

Step S1010：D nodes receive echo request messages, because label stack top-level tab is MPLS Router Alert Label cause to send control plane.In control plane, unpacking is the discovery that LSP ping bags, then peels MPLS Router off After Alert label, continue to parse label stack and IP heads.When due to TE Label, either the last two jump is ejected or parsed It is found to be TE LSP Egress nodes and continues to connect down next layer of label so that current stack top label exposes as LDP Label And TTL=2 and the Transit nodes as LDP LSP will not continue to parse next layer of label/IP, it is unsatisfactory for needing to reply Echo reply exposure condition.

Then control plane further changes bag：According to the Downstream Mapping TLV before modification in echo request In next-hop be D, and R marks are effective, then are actually subjected to be sent to next-hop H according to message, and by the Downstream of message Mapping TLV are revised as：{DS Flags：I=1, E/M/R=0；Downstream Address=H＆H.port1 }.FEC Do not change, without changing target FEC stack TLV.Then message is additionally inserted according to instruction in stack top It is up that MPLS Router Alert Label mode of giving out a contract for a project throws to datum plane.

The up current top-level tab TE Label based on message of datum plane and TTL=254 table look-up forwarding, find TE LSP terminates, and continues to be tabled look-up forwarding according to next layer of label LDP Label and TTL=2, the outgoing label LDP that Tag switching is obtained Label TTL are pressed into after label TTL subtracts 1 and are arranged to 1.Then additionally in top label stack insertion MPLS Router Alert Forwarded after Label.

Step S1011：H nodes receive echo request messages, because label stack top-level tab is MPLS Router Alert Label cause to send control plane.In control plane, unpacking is the discovery that LSP ping bags, then peels MPLS Router off After Alert label, continue to parse label stack and IP heads, find current stack top label LDP Label TTL=1, or LDP Label the last two jumps are ejected and cause purpose IP (127/8) exposures, meet that needs reply echo reply exposure condition.

Then control plane further does FEC verifications：Check and find that label value is effective, corresponding ILM be present and mark Label operation is POP；Check that the incoming interface that the next hop information found in Donstream Mapping TLV reaches with message is Match somebody with somebody；Check that the label stack for finding message and target FEC stack are consistent.

H node reverts back echo reply messages, including：

Upstream Interface TLV：{H&H.port1}

Responder Egress TLV：{H}

Step S1012：A nodes receive the ehco reply of H nodes, check that it is to match to find with current echo request , and the Upstream Interface TLV in echo reply：{ H＆H.port1 } and the Downstream locally preserved Mapping entries：{DS Flags：E/M=0；Downstream Address=H＆H.port1 } it is matching.

A nodes are obtained from echo reply less than new Downstream Address information.Detection finishes, output inspection Result is surveyed, have received Egress nodes H echo reply.

Preferred embodiment 2

Figure 16 is basic according to the network topological diagram of the preferred embodiment of the present invention 2, this preferred embodiment and preferred embodiment 1 Identical, difference is that TE tunnel are UNIFORM types.The testing process comprises the following steps：

Step S1101：First run echo request messages are constructed on A nodes, Echo request PDU are set：

target FEC stack TLV：{LDP FEC H}

Encapsulate IP/UDP heads and label stack, stack top label LDP Label TTL=1.

Downstream Mapping entries are locally preserved on A nodes：{DS Flags：E/M=0；Downstream Address=B＆B.port1 }

Step S1102：B node receives echo request messages, because label stack top-level tab is MPLS Router Alert Label cause to send control plane.In control plane, unpacking is the discovery that LSP ping bags, then peels MPLS Router off After Alert label, continue to parse label stack and IP heads, find current stack top label LDP Label TTL=1, meet need Reply echo reply exposure condition.

B node replys echo reply messages, including：

Upstream Interface TLV：{B&B.port1}

Responder Transit TLV：{B}

Downstream Mapping TLV1：{DS Flags：I=1, E=1, R=0；Downstream Address= C&C.port1}.Here TE tunnel are UNIFORM types, then are filled according to the next-hop after Tunnel iteration Downstream Mapping TLV。

Downstream Mapping TLV2：{DS Flags：I=1, E=1, R=0；Downstream Address= E&E.port1}

Step S1103：A nodes receive the ehco reply of B node, check that it is to match to find with current echo request , and the Upstream Interface TLV in echo reply：{ B＆B.port1 } and the Downstream locally preserved Mapping entries：{DS Flags：E/M=0；Downstream Address=B＆B.port1 } it is matching.

Downstream Mapping entries 1：{DS Flags：E=1, R=0；Downstream Address=C＆ C.port1}

A initiates next round echo request, similar step S1101, only stack top label LDP Label TTL=2. It is identical in the Downstream Mapping TLV particularly included and step S1101.

Step S1104：B node receives echo request messages, because label stack top-level tab is MPLS Router Alert Label cause to send control plane.In control plane, unpacking is the discovery that LSP ping bags, then peels MPLS Router off After Alert label, continue to parse label stack and IP heads, find current stack top label LDP Label and TTL=2 and conduct LDP LSP Transit nodes will not continue to parse next layer of label/IP, be unsatisfactory for needing the exposure for replying echo reply Condition.

Then control plane further changes bag：According to the Downstream Mapping TLV before modification in echo request In next-hop be B, and be actually subjected to according to message to be sent to distal end next-hop D, and TE tunnel by LDP over TE For UNIFORM types, and the Downstream Mapping TLV of message are revised as：{DS Flags：I=1, E=1, R= 0；Downstream Address=C＆C.port1 }.FEC changes, and modification target FEC stack TLV are：{LDP FEC H,TE FEC D}.Then message is additionally inserted into giving out a contract for a project for MPLS Router Alert Label according to instruction in stack top It is up that mode throws to datum plane.

The up current top-level tab LDP Label based on message of datum plane and TTL=2 are tabled look-up forwarding, and label is handed over The outgoing label LDP Label TTL got in return, which are pressed into after label TTL subtracts 1, is arranged to 1, outer layer TE Label TTL copies LDP Label TTL are also configured as 1.Then additionally forwarded after top label stack insertion MPLS Router Alert Label.

Step S1105：C nodes receive echo request messages, because label stack top-level tab is MPLS Router Alert Label cause to send control plane.In control plane, unpacking is the discovery that LSP ping bags, then peels MPLS Router off After Alert label, continue to parse label stack and IP heads, find current stack top label TE Label TTL=1, meet needs Reply echo reply exposure condition.

C node reverts back echo reply messages, including：

Upstream Interface TLV：{C&C.port1}

Responder Transit TLV：{C}

Downstream Mapping TLV1：{DS Flags：I=1, E=0, R=0；Downstream Address= D&D.port1}。

Step S1106：A nodes receive the ehco reply of C nodes, check that it is to match to find with current echo request , and the Upstream Interface TLV in echo reply：{ C＆C.port1 } and the Downstream locally preserved Mapping entries 1：{DS Flags：E=1, R=0；Downstream Address=C＆C.port1 } it is matching, due to Downstream Mapping entries 2：{DS Flags：E=1, R=0；Downstream Address=E＆E.port1 } in E marks it is effective, then it is considered as matching.

Downstream Mapping entries 1：{DS Flags：E=0, R=0；Downstream Address=D＆ D.port1}

A initiates next round echo request, similar step S1101, only stack top label LDP Label TTL=3. It is identical in the Downstream Mapping TLV particularly included and step S1101.

Step S1107：Similar step S1104, control plane modification message target FEC stack TLV with After Downstream Mapping TLV, datum plane forwarded upstream is thrown to.

Step S1108：C nodes receive echo request messages, because label stack top-level tab is MPLS Router Alert Label cause to send control plane.In control plane, unpacking is the discovery that LSP ping bags, then peels MPLS Router off After Alert label, continue to parse label stack and IP heads, find current stack top label TE Label and TTL=2 and be used as TE LSP Transit nodes will not continue to parse next layer of label/IP, be unsatisfactory for needing the exposure condition for replying echo reply.

Then control plane further changes bag：According to the Downstream Mapping TLV before modification in echo request In next-hop be C, and the Downstream Mapping TLV of message are revised as：{DS Flags：I=1, E=0, R= 0；Downstream Address=D＆D.port1 }.FEC does not change, without changing target FEC stack TLV.Then the mode of giving out a contract for a project for message additionally being inserted to MPLS Router Alert Label according to instruction in stack top throws to data Plane is up.

The up current top-level tab TE Label based on message of datum plane and TTL=2 table look-up forwarding, by Tag switching Obtained outgoing label TE Label TTL, which are pressed into after label TTL subtracts 1, is arranged to 1.Then additionally MPLS is inserted in top label stack Forwarded after Router Alert Label.

Step S1109：D nodes receive echo request messages, because label stack top-level tab is MPLS Router Alert Label cause to send control plane.In control plane, unpacking is the discovery that LSP ping bags, then peels MPLS Router off After Alert label, continue to parse label stack and IP heads, find current stack top label TE Label TTL=1, meet needs Reply echo reply exposure condition.

Then control plane further does FEC verifications：Check find TE label values be effective, exist corresponding ILM and Tag operational is POP, then it is effective to continue checking for LDP label value, and corresponding ILM and tag operational be present is SWAP；Inspection Look into and find that the next hop information in Donstream Mapping TLV matches with the incoming interface that message reaches；Check and find The label stack of message and target FEC stack are consistent.

D node reverts back echo reply messages, including：

Upstream Interface TLV：{D&D.port1}

Responder Transit TLV：{D}

Step S1110：A nodes receive the ehco reply of D nodes, check that it is to match to find with current echo request , and the Upstream Interface TLV in echo reply：{ D＆D.port1 } and the Downstream locally preserved Mapping entries：{DS Flags：E/M=0；Downstream Address=D＆D.port1 } it is matching.

Downstream Mapping entries 1：{DS Flags：E=0, R=0；Downstream Address=H＆ H.port1}

A initiates next round echo request, similar step S1101, only stack top label LDP Label TTL=4. It is identical in the Downstream Mapping TLV particularly included and step S1101.

Step S1111：Similar step S1104, control plane modification message target FEC stack TLV with After Downstream Mapping TLV, datum plane forwarded upstream is thrown to.

Step S1112：After similar step S1108, the Downstream Mapping TLV of control plane modification message, throw away Give datum plane forwarded upstream.

Step S1113：D nodes receive echo request messages, because label stack top-level tab is MPLS Router Alert Label cause to send control plane.In control plane, unpacking is the discovery that LSP ping bags, then peels MPLS Router off After Alert label, continue to parse label stack and IP heads, find current stack top label TE Label and TTL=2, but be TE LSP Egress nodes, then continue to parse next layer of label so that current stack top label exposes as LDP Label, LDP Label TTL are according to taking small inheritance principles to be revised as TE Label TTL=2 from original 4, and as LDP LSP's It Transit nodes, then will not continue to parse next layer of label/IP, be unsatisfactory for needing the exposure condition for replying echo reply.

Then control plane further changes bag：According to the Downstream Mapping TLV before modification in echo request In next-hop be D, and the Downstream Mapping TLV of message are revised as：{DS Flags：I=1, E=0, R= 0；Downstream Address=H＆H.port1 }.FEC changes, and modification target FEC stack TLV are { LDP FEC H}.Then the mode of giving out a contract for a project for message additionally being inserted to MPLS Router Alert Label according to instruction in stack top is thrown to Datum plane is up.

The up current top-level tab TE Label based on message of datum plane and TTL=2 table look-up forwarding, find TE LSP Termination, continue to take small inherit to table look-up forwarding for 2 according to next layer of LDP Label and TTL, the outgoing label that Tag switching is obtained LDP Label TTL are pressed into after label TTL subtracts 1 and are arranged to 1.Then additionally in top label stack insertion MPLS Router Alert Forwarded after Label.

Step S1114：H nodes receive echo request messages, because label stack top-level tab is MPLS Router Alert Label cause to send control plane.In control plane, unpacking is the discovery that LSP ping bags, then peels MPLS Router off After Alert label, continue to parse label stack and IP heads, find current stack top label LDP Label TTL=1, or LDP Label the last two jumps are ejected and cause purpose IP (127/8) exposures, meet that needs reply echo reply exposure condition.

H node reverts back echo reply messages, including：

Upstream Interface TLV：{H&H.port1}

Responder Egress TLV：{H}

Step S1115：A nodes receive the ehco reply of H nodes, check that it is to match to find with current echo request , and the Upstream Interface TLV in echo reply：{ H＆H.port1 } and the Downstream locally preserved Mapping entries：{DS Flags：E/M=0；Downstream Address=H＆H.port1 } it is matching.

Preferred embodiment 3

This preferred embodiment will describe P2MP LSP testing process, and Figure 17 is the tool according to the specific embodiment of the invention The network topological diagram of body embodiment 3, it is the multicast distribution tree using R nodes as root node as shown in figure 17, establishing FEC is OpaqueX mLDP LSP.

LSP traceroute mLDP FEC opaqueX now are initiated in R nodes, the testing process includes following step Suddenly, for brevity, main flow related to the present invention is only described：

Step S1201：First run echo request messages are constructed on R nodes, respectively to multicast member next-hop A and multicast Member's next-hop B sends echo request.

The Echo request PDU sent to multicast member next-hop A/B are set：

target FEC stack TLV：{mLDP FEC opaqueX}

Downstream Mapping TLV1：{DS Flags：I=1, E/R=0, M=1；Downstream Address =A＆A.port1 }.A represents that Router-id, port1 represent interface IP, similarly hereinafter.

Downstream Mapping TLV2：{DS Flags：I=1, E/R=0, M=1；Downstream Address =B＆B.port1 }.

Encapsulate IP/UDP heads and label stack, stack top label LDP Label TTL=1.

Downstream Mapping entries 1 are locally preserved on R nodes：{DS Flags：E/R=0, M=1； Downstream Address=A＆A.port1 }, Downstream Mapping entries 2：{DS Flags：E/R=0, M=1； Downstream Address=B＆B.port1 }

Step S1202：A nodes receive echo request messages, because label stack top-level tab is MPLS Router Alert Label cause to send control plane.In control plane, unpacking is the discovery that LSP ping bags, then peels MPLS Router off After Alert label, continue to parse label stack and IP heads, find current stack top label LDP Label TTL=1, meet need Reply echo reply exposure condition.

Then control plane further does FEC verifications：Check and find that label value is effective, corresponding ILM be present and mark Label operation is SWAP；Check and find that the incoming interface that the next hop information in Donstream Mapping TLV1 reaches with message is Matching；Check that the label stack for finding message and target FEC stack are consistent.

A node reverts back echo reply messages, including：

Upstream Interface TLV：{A&A.port1}

Responder Transit TLV：{A}

Downstream Mapping TLV1：{DS Flags：I=1, E/R=0, M=1；Downstream Address =C＆C.port1 }.

Downstream Mapping TLV2：{DS Flags：I=1, E/R=0, M=1；Downstream Address =D＆D.port1 }.

Similar, B node receives echo request messages, replys echo reply messages, including：

Upstream Interface TLV：{B&B.port1}

Responder Transit TLV：{B}

Downstream Mapping TLV1：{DS Flags：I=1, E/R=0, M=1；Downstream Address=E＆E.port1 }.

Downstream Mapping TLV2：{DS Flags：I=1, E/R=0, M=1；Downstream Address=F＆F.port1 }.

Step S1203：R nodes receive the ehco reply of A nodes, check that it is to match to find with current echo request , and the Upstream Interface TLV in echo reply：{ A＆A.port1 } and the Downstream locally preserved Mapping entries 1：{DS Flags：E/R=0, M=1；Downstream Address=A＆A.port1 } it is matching.

Similar, R nodes receive the echo reply of B node, and the Upstream in echo reply Interface TLV：{ B＆B.port1 } and the Downstream Mapping entries 2 locally preserved：{DS Flags：E/R= 0, M=1；Downstream Address=B＆B.port1 } it is matching.

R nodes obtain new Downstream Address information from A echo reply and locally saved as：

Downstream Mapping entries 1：{DS Flags：E/R=0, M=1；Downstream Address=C＆ C.port1}

Downstream Mapping entries 2：{DS Flags：E/R=0, M=1；Downstream Address=D＆ D.port1}

R nodes obtain new Downstream Address information from B echo reply and locally saved as：

Downstream Mapping entries 3：{DS Flags：E/R=0, M=1；Downstream Address=E＆ E.port1}

Downstream Mapping entries 4：{DS Flags：E/R=0, M=1；Downstream Address=F＆ F.port1}

R initiates next round echo request, similar step S1201, only stack top label LDP Label TTL=2. It is identical in the Downstream Mapping TLV particularly included and step S1201.

Step S1204：A nodes receive echo request messages, because label stack top-level tab is MPLS Router Alert Label cause to send control plane.In control plane, unpacking is the discovery that LSP ping bags, then peels MPLS Router off After Alert label, continue to parse label stack and IP heads, find current stack top label LDP Label and TTL=2, but be It mLDP LSP Transit nodes, will not continue to parse next layer of label/IP, be unsatisfactory for needing to reply the sudden and violent of echo reply Dew condition.

Then control plane further changes bag：According to the Downstream Mapping before modification in echo request Next-hop in TLV1 is A, then is revised as Downstream Mapping TLVs：Downstream Mapping TLV1： {DS Flags：I=1, E/R=0, M=1；Downstream Address=C＆C.port1 }；Downstream Mapping TLV2：{DS Flags：I=1, E/R=0, M=1；Downstream Address=D＆D.port1 }.Then LDP Label TTL subtracts 1.E-Packet.

Similar, Downstream Mapping TLVs are revised as by B node：Downstream Mapping TLV1： {DS Flags：I=1, E/R=0, M=1；Downstream Address=E＆E.port1 }；Downstream Mapping TLV2：{DS Flags：I=1, E/R=0, M=1；Downstream Address=F＆F.port1 }.Then LDP Label TTL subtracts 1.E-Packet.

Step S1205：C nodes receive echo request messages, because label stack top-level tab is MPLS Router Alert Label cause to send control plane.In control plane, unpacking is the discovery that LSP ping bags, then peels MPLS Router off After Alert label, continue to parse label stack and IP heads, find current stack top label LDP Label TTL=1, meet need Reply echo reply exposure condition.

C node reverts back echo reply messages, including：

Upstream Interface TLV：{C&C.port1}

Responder Transit TLV：{C}

Downstream Mapping TLV1：{DS Flags：I=1, E/R=0, M=1；Downstream Address =G＆G.port1 }.

Downstream Mapping TLV2：{DS Flags：I=1, E/R=0, M=1；Downstream Address =H＆H.port1 }.

Similar, D nodes receive echo request messages, reply echo reply messages, including：

Upstream Interface TLV：{D&D.port1}

Responder Egress TLV：{D}

Similar, E nodes receive echo request messages, reply echo reply messages, including：

Upstream Interface TLV：{E&E.port1}

Responder Egress TLV：{E}

Similar, F nodes receive echo request messages, reply echo reply messages, including：

Upstream Interface TLV：{F&F.port1}

Responder Transit TLV：{F}

Downstream Mapping TLV1：{DS Flags：I=1, E/R=0, M=1；Downstream Address =I＆I.port1 }.

Downstream Mapping TLV2：{DS Flags：I=1, E/R=0, M=1；Downstream Address =J＆J.port1 }.

Step S1206：R nodes receive the ehco reply of C nodes, check that it is to match to find with current echo request , and the Upstream Interface TLV in echo reply：{ C＆C.port1 } and the Downstream locally preserved Mapping entries 1：{DS Flags：E/R=0, M=1；Downstream Address=C＆C.port1 } it is matching.

Similar, R nodes receive the echo reply of D nodes, and the Upstream in echo reply Interface TLV：{ D＆D.port1 } and the Downstream Mapping entries 2 locally preserved：{DS Flags：E/R= 0, M=1；Downstream Address=D＆D.port1 } it is matching.

Similar, R nodes receive the echo reply of E nodes, and the Upstream in echo reply Interface TLV：{ E＆E.port1 } and the Downstream Mapping entries 3 locally preserved：{DS Flags：E/R= 0, M=1；Downstream Address=E＆E.port1 } it is matching.

Similar, R nodes receive the echo reply of F nodes, and the Upstream in echo reply Interface TLV：{ F＆F.port1 } and the Downstream Mapping entries 4 locally preserved：{DS Flags：E/R= 0, M=1；Downstream Address=F＆F.port1 } it is matching.

R nodes obtain new Downstream Address information from C echo reply and locally saved as：

Downstream Mapping entries 1：{DS Flags：E/R=0, M=1；Downstream Address=G＆ G.port1}

Downstream Mapping entries 2：{DS Flags：E/R=0, M=1；Downstream Address=H＆ H.port1}

R nodes obtain new Downstream Address information from F echo reply and locally saved as：

Downstream Mapping entries 3：{DS Flags：E/R=0, M=1；Downstream Address=I＆ I.port1}

Downstream Mapping entries 4：{DS Flags：E/R=0, M=1；Downstream Address=J＆ J.port1}

R initiates next round echo request, similar step S1201, only stack top label LDP Label TTL=3. It is identical in the Downstream Mapping TLV particularly included and step S1201.

Step S1207：It is similar, A with step S1204, B node, which is respectively modified, is sent to respective multicast member next-hop E-Packeted after Downstream Mapping TLV in echo request messages.

Step S1208：It is similar, C with step S1204, F nodes, which are respectively modified, is sent to respective multicast member next-hop E-Packeted after Downstream Mapping TLV in echo request messages.

D, E node can be again to R node reverts back echo reply, but will not match what it was locally preserved on R nodes Downstream Mapping entries, these echo reply can be dropped.

Step S1209：It is similar, G node reverts back echo reply messages with step S1205, including：

Upstream Interface TLV：{G&G.port1}

Responder Egress TLV：{G}

Similar, H nodes receive echo request messages, reply echo reply messages, including：

Upstream Interface TLV：{H&H.port1}

Responder Egress TLV：{H}

Similar, inode receives echo request messages, replys echo reply messages, including：

Upstream Interface TLV：{I&I.port1}

Responder Egress TLV：{I}

Similar, J node receives echo request messages, replys echo reply messages, including：

Upstream Interface TLV：{J&J.port1}

Responder Egress TLV：{J}

Step S1210：It is similar with step S1203, R nodes receive echo reply and local from G, H, I, J respectively The Downstream Mapping entries 1~4 of preservation are matched.

R nodes are obtained from echo reply less than new Downstream Address information.Detection finishes, output inspection Result is surveyed, have received Egress nodes D, E, G, H, I, J echo reply.

Embodiment 4

Embodiments of the invention additionally provide a kind of storage medium.Alternatively, in the present embodiment, above-mentioned storage medium can The program code for performing following steps to be arranged to storage to be used for：

S1, send back and answer request message, wherein, responding request message includes being used to indicate that request message forwarding will be responded The MPLS Alert Label of control plane；

S2, the response response message that transmission node or Egress node feed back in the case where responding the triggering of request message is received, and Detection responds whether response message matches with prestored information.

Alternatively, in the present embodiment, above-mentioned storage medium can include but is not limited to：USB flash disk, read-only storage (ROM, Read-Only Memory), random access memory (RAM, Random Access Memory), mobile hard disk, magnetic disc or CD etc. is various can be with the medium of store program codes.

Alternatively, in the present embodiment, processor is performed to send back according to the program code stored in storage medium and answered Request message, wherein, responding request message includes being used to indicate that the MPLS of request message forwarding control plane will be responded Alert Label；

Alternatively, in the present embodiment, processor performs according to the program code stored in storage medium and receives transmission The response response message that node or Egress node feed back in the case where responding the triggering of request message, and detect respond response message with it is pre- Deposit whether information matches.

Alternatively, the particular preferred embodiment in the present embodiment may be referred to institute in above-described embodiment and optional embodiment The preferred embodiment of description, the present embodiment will not be repeated here.

S1, it is received back to and answers request message, wherein, responding request message includes being used to indicate that request message forwarding will be responded The MPLS Alert Label of control plane；

S2, the response request message is forwarded to by control plane according to the MPLS Alert Label；

S3, the response request message is handled according to default forwarding-table item.

Obviously, those skilled in the art should be understood that above-mentioned each module of the invention or each step can be with general Computing device realize that they can be concentrated on single computing device, or be distributed in multiple computing devices and formed Network on, alternatively, they can be realized with the program code that computing device can perform, it is thus possible to they are stored Performed in the storage device by computing device, and in some cases, can be with different from shown in order execution herein The step of going out or describing, they are either fabricated to each integrated circuit modules respectively or by multiple modules in them or Step is fabricated to single integrated circuit module to realize.So, the present invention is not restricted to any specific hardware and software combination.

The preferred embodiments of the present invention are the foregoing is only, are not intended to limit the invention, for the skill of this area For art personnel, the present invention can have various modifications and variations.Within the spirit and principles of the invention, that is made any repaiies Change, equivalent substitution, improvement etc., should be included in the scope of the protection.

Claims

A kind of 1. detection method of multiprotocol label switching, it is characterised in that including：

Detection initiator, which sends back, answers request message, wherein, the response request message includes being used to indicate the response The multiprotocol label switching MPLS alarm label A lert Label of request message forwarding control plane；

Detection initiator receives the response response that transmission node or Egress node feed back under the triggering of the response request message Message, and detect whether the response response message matches with prestored information.
2. according to the method for claim 1, it is characterised in that also include in the response request message：Downstream mapping letter Breath, wherein, the downstream map information corresponds to one or more next-hops route of the response request message.
3. according to the method for claim 2, it is characterised in that send back and answer request message also to include：

Judge whether the response request message is response request message that start node is sent first；

In the case where the judgment result is yes, send back answer request message when, locally preserve described return in the start node Answer the downstream map information in request message.
4. according to the method for claim 3, it is characterised in that in the case where judged result is no, should be asked sending back When seeking message, the last round of downstream map information responded and carried in response message is locally preserved in the start node.
5. according to the method for claim 1, it is characterised in that the MPLS AlertLabel are encapsulated in the response please In the top label stack for seeking message.
6. according to the method for claim 4, it is characterised in that detection response response message and the prestored information whether With including：

Detect the sender handle Sender's Handle in the response response message and it is described respond in request message the Whether one respective field matches, and the detection sequence number responded in response message and it is described respond in request message the Whether two respective fields match；

Matched in the Sender's Handle with first respective field, and sequence number word corresponding to described second During section matching, judge that the Upstream Interface information in the response response message maps with the downstream that the start node locally preserves Whether information matches, and the downstream that the Upstream Interface information in the response response message locally preserves with the start node is reflected When penetrating information matches, determine that the response response message matches with prestored information.
7. according to the method for claim 6, it is characterised in that when locally preserving multiple downstream map informations, judge institute State Upstream Interface information and the downstream map information responded in response message whether match including：

Whether the multiple downstream map information for judging locally to preserve has the corresponding response response message matching；

Judge the multiple downstream map information that locally preserves and multiple response response messages the match is successful whether is rate More than predetermined threshold value.
8. according to the method described in any one of claim 1 to 7, it is characterised in that in the detection response response message and in advance Deposit after whether information match, methods described also includes：

Determine whether that sending next response asks with the testing result whether prestored information matches according to the response response message Seek message.
A kind of 9. processing method of multiprotocol label switching, it is characterised in that including：

It is received back to and answers request message, wherein, the response request message includes being used to indicate to turn the response request message Send out the multiprotocol label switching MPLS alarm label A lert Label of control plane；

The response request message is forwarded to by control plane according to the MPLS Alert Label；

The response request message is handled according to default forwarding-table item.
10. according to the method for claim 9, it is characterised in that described respond is handled according to default forwarding-table item and asks report Text includes one below：

According to the first default forwarding-table item feedback response response message for responding request message；

According to the first default forwarding-table item modification content for responding request message, and forwarding-table item is preset by institute according to second State and respond the next-hop node that request message is forwarded to datum plane.
11. according to the method for claim 10, it is characterised in that changing the response according to the first default forwarding-table item please Seeking the content of message includes：Change the target forwarding equivalence class FEC stacks and downstream map information in the response request message.
A kind of 12. detection means of multiprotocol label switching, applied to detection initiator, it is characterised in that including：

Sending module, request message is answered for sending back, wherein, the response request message includes being used to indicate described to return Answer the multiprotocol label switching MPLS alarm label A lert Label of request message forwarding control plane；

Detection module, should for receiving the response that transmission node or Egress node feed back under the triggering of the response request message Message is answered, and detects whether the response response message matches with prestored information.
13. device according to claim 12, it is characterised in that also include in the response request message：Downstream maps Information, wherein, the downstream map information corresponds to one or more next-hops route of the response request message.
A kind of 14. processing unit of multiprotocol label switching, it is characterised in that including：

Receiving module, request message is answered for being received back to, wherein, the response request message includes being used to ask the response Seek the multiprotocol label switching MPLS alarm label A lert Label of message forwarding control plane；

Forwarding module, for the response request message to be forwarded into control plane according to the MPLS Alert Label；

Processing module, for handling the response request message according to default forwarding-table item.
15. a kind of detecting system of multiprotocol label switching, including start node, transmission node or Egress node, its feature exist In,

The start node also includes：

Sending module, request message is answered for sending back, wherein, the response request message includes being used to indicate described to return Answer the multiprotocol label switching MPLS alarm label A lert Label of request message forwarding control plane；

Detection module, should for receiving the response that transmission node or Egress node feed back under the triggering of the response request message Message is answered, and detects whether the response response message matches with prestored information；

Transmission node or Egress node also include：

Receiving module, request message is answered for being received back to, wherein, the response request message includes being used to ask the response Seek the MPLS Alert Label of message forwarding control plane；

Forwarding module, for the response request message to be forwarded into control plane according to the MPLS Alert Label；

Processing module, for handling the response request message according to default forwarding-table item.