CN102594582A - Looping back method and system of message - Google Patents
Looping back method and system of message Download PDFInfo
- Publication number
- CN102594582A CN102594582A CN2011100086545A CN201110008654A CN102594582A CN 102594582 A CN102594582 A CN 102594582A CN 2011100086545 A CN2011100086545 A CN 2011100086545A CN 201110008654 A CN201110008654 A CN 201110008654A CN 102594582 A CN102594582 A CN 102594582A
- Authority
- CN
- China
- Prior art keywords
- loopback
- message
- node
- destination node
- source node
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Granted
Links
Images
Landscapes
- Data Exchanges In Wide-Area Networks (AREA)
Abstract
The invention discloses a looping back method of a message, which comprises the following steps of: transmitting a Loop-back Request for requesting to perform loop-back operation by a loop-back source node via a current test path, wherein the Loop-back Request comprises a loop-back type field for presenting the type of the message to be looped back; receiving the Loop-back Request by a loop-back destination node on the current test path, and judging whether the message needs to be looped back according to the loop-back type field in the Loop-back Request; if the message needs to be looped back, returning a Loop-back Reply that means the loop-back state is successfully updated to the loop-back source node; if the message does not need to be looped back, returning the Loop-back Reply that carries the routing information to the loop-back source node; receiving the Loop-back Reply returned by the loop-back destination node, which represents that the loop-back state is successfully updated by the loop-back source node, then looping back the message to be looped back between the loop-back source node and the loop-back destination node. The invention also discloses a looping back system of the message, which can avoid the influence on the transmission of other service message and the monitoring and management of the path, and also improve the efficiency of the message loop-back test effectively.
Description
Technical field
The present invention relates to the loopback technology of message, relate in particular to a kind of message loop back method and system.
Background technology
Transmit net for current group; When realizing loopback (Loopback) function; Main have two kinds of situation: a kind of is that loopful non-service condition (Out-of-service) under returns (Full Loopback) technology, and this kind Loopback technology is mainly used in the connection or the correlated performance of test path, need carry out loopback to all messages and operate; Make all messages all can not transmit, have influence on professional normally carrying out according to normal operation flow; Another kind is operation management maintain (OAM, Operation Administration and Maintenance) the Loopback technology under non-interrupting service state (In-service), and this Loopback technology is that all OAM messages are carried out the loopback operation; Though do not influence the normal transmission of other messages such as Business Stream,, can have influence on the normal monitoring in path owing to need carry out loopback to all OAM messages; For example; When needs are tested two-way time of delay, only need the loopback of delay measurements (DM, Delay Measurement) message; But through above-mentioned OAM Loopback technology; Then all OAM messages are all carried out loopback, make that other OAM messages except that the DM message can not transmit according to normal operation flow, thereby cause other OAM(Operation Administration Maintenance) normally to implement.
In addition, two kinds of above-mentioned Loopback technology can not carried routing information in carrying out the message loop-back process; Also just can not follow the tracks of (RouterTrace) function by realizing route; Can not carry out the discovery and the failure location of path topology information, therefore, also need be after loopback test; Further carry out the discovery and the failure location of path topology information, be unfavorable for the eliminating of path failure.
Summary of the invention
In view of this, main purpose of the present invention is to provide a kind of message loop back method and system, can in loop-back process, only carry out the loopback operation to needed particular type message, can have influence on the professional normal problem of implementing to solve existing loopback technology.
For achieving the above object, technical scheme of the present invention is achieved in that
The invention provides a kind of message loop back method; Said method comprises: the loopback source node sends the loopback request (Loopback Request) that is used to ask to carry out the loopback operation through current test path, includes the loopback type field of the loopback type of message that is used to indicate among this LoopbackRequest; Loopback destination node on the current test path receives said Loopback Request; Judge whether needs loopback message according to the loopback type field among the said Loopback Request; If; Then the loopback destination node is according to said loopback type field, self wrapped state is updated to the wrapped state of wanting the loopback message to said, and returns the expression wrapped state to said loopback source node and upgrade successful Loopback Reply; If not, then the loopback destination node is extracted the routing iinformation of self, and returns to said loopback source node and to carry the Loopback Reply that extracts routing iinformation to some extent; Said loopback source node receives the expression wrapped state that said loopback destination node returns and upgrades successful Loopback Reply, then and carry out the said loopback of wanting the loopback message between the loopback destination node.
In such scheme; Said method also comprises: the LoopbackRequest that said loopback source node is sent also includes and is used to indicate loopback to overflow life span (TTL) field of time; Node on the current test path, that when ttl field is overflowed, receive said Loopback Request is as said loopback destination node; Upgrade the wrapped state of self, and return Loopback Reply to said loopback source node.
In such scheme; Said method also comprises: do not support the renewal of wrapped state in said loopback destination node, or when not supporting the said loopback of wanting the loopback message; Said loopback destination node can not be accomplished the renewal of said wrapped state; The failure of renewal wrapped state is then sent the Loopback Reply that the expression wrapped state is upgraded failure to said loopback source node.
In such scheme; Carry out the said loopback of wanting the loopback message between said loopback source node and the loopback destination node; Comprise: said loopback source node receives the Loopback Reply that said loopback destination node is returned; Judge whether said Loopback Reply is that the expression wrapped state is upgraded successful Loopback Reply, if carry out the said loopback of wanting the loopback message between said loopback source node and the loopback destination node; Otherwise, do not carry out the said loopback of wanting the loopback message between said loopback source node and the loopback destination node.
In such scheme; Carry out between said loopback source node and the loopback destination node after the said loopback of wanting the loopback message; Said method also comprises: when needs stop the operation of current loopback; Said loopback source node sends the Loopback Request of the current loopback operation of deletion to said loopback destination node; After said loopback destination node receives this Loopback Request, reduce self wrapped state, and return the Loopback Reply that current loopback is successfully removed to said loopback source node.
The present invention also provides a kind of message loopback system; Said system comprises: loopback source node and loopback destination node; Wherein, The loopback source node is used for sending the Loopback Request that is used to ask to carry out the loopback operation through current test path, includes the loopback type field of the loopback type of message that is used to indicate among this Loopback Request; Receiving after expression wrapped state that said loopback destination node returns upgrades successful Loopback Reply, and carrying out the said loopback of wanting the loopback message between the said loopback destination node; The loopback destination node; Be used to receive the Loopback Request that said loopback source node sends; Judge whether needs loopback message according to the loopback type field among the said Loopback Request, if then the loopback destination node is according to said loopback type field; The wrapped state of self is updated to the wrapped state of wanting the loopback message to said, and returns the expression wrapped state to said loopback source node and upgrade successful LoopbackReply; If not, then the loopback destination node is extracted the routing iinformation of self, and returns to said loopback source node and to carry the Loopback Reply that extracts routing iinformation to some extent.
In such scheme, said loopback source node sends Loopback Request and also includes and be used to indicate loopback to overflow life span (TTL) field of time; Said loopback destination node specifically is used for when the ttl field of said Loopback Request is overflowed, and self wrapped state is updated to the wrapped state of wanting the loopback message to said, and returns Loopback Reply to said loopback source node.
In such scheme; Said loopback source node; Specifically be used for, receive the Loopback Reply that said loopback destination node is returned, judge whether said Loopback Reply is that the expression wrapped state is upgraded successful Loopback Reply; If, and carry out the said loopback of wanting the loopback message between the said loopback destination node; Otherwise, do not carry out the said loopback of wanting the loopback message.
In such scheme, said loopback source node also is used for when needs stop the operation of current loopback, and said loopback source node sends the Loopback Request of the current loopback operation of deletion to said loopback destination node; Said loopback destination node, also be used to receive this Loopback Request after, reduce self wrapped state, and return the Loopback Reply that current loopback is successfully removed to said loopback source node.
In such scheme, said loopback source node is source node or any intermediate node except that the loopback destination node on the current test path; Said loopback destination node is any intermediate node or the endpoint node on the current test path on the current test path, except that the loopback source node.
Message loop back method of the present invention and system; Want the type of loopback message through indication in the loopback request; Realization is to specifying the loopback operation of type of message; Thereby can avoid influencing the transmission of other service messages and the monitor management in path, and can effectively improve the efficient of message loopback test, improve corresponding accuracy of test and speed.
In addition, the present invention also through setting the operation of Null loopback, realizes the RouterTrace function in the message loop-back process, thereby carries out the discovery of route information on the path and the location of abort situation.
Description of drawings
Fig. 1 is the realization flow figure of message loop back method of the present invention;
Fig. 2 is the message structure sketch map of Loopback Request;
Fig. 3 is the message structure sketch map of Loopback Reply;
Fig. 4 is the sketch map of message loop-back path in a kind of specific embodiment of the present invention;
Fig. 5 is the realization flow figure of message loop-back process in a kind of specific embodiment of the present invention.
Embodiment
Basic thought of the present invention is: only the type of message to source end node particular requirement carries out the loopback operation, realizes performance test and RouterTrace function to the path, thereby through a kind of novel Loopback function of expansion; Realization specifically, is exactly the loop fuction that utilizes expansion to the loopback operation of particular type message; Realization is to a certain path; Comprise the particular type message on label forwarding path (LSP, Label Switched Path), pseudo-line (PW, Pseudo wire) and the link layer (Section) etc.; The message that comprises specific a certain types such as test, OAM carries out loopback; Realizing to a certain performance on the path, as: the measurement of delays, Loss Rate etc., one side can be avoided influencing to the transmission of business and the monitor management in path; Through setting the operation of Null loopback, realize the RouterTrace function on the other hand, carry out the discovery of route information on the path and the location of abort situation.
Message loop back method of the present invention with reference to shown in Figure 1, mainly can may further comprise the steps:
Step 101: the loopback source node sends the loopback request (Loopback Request) that is used to ask to carry out the loopback operation through current test path, includes the loopback type field of the loopback type of message that is used to indicate among this Loopback Request;
Step 102: the loopback destination node on the current test path receives said Loopback Request; Judge whether needs loopback message according to the loopback type field among the said Loopback Request; If; Then the loopback destination node is according to said loopback type field, and self wrapped state is updated to the wrapped state of wanting the loopback message to said, and returns the expression wrapped state to said loopback source node and upgrade successful loopback and reply (Loopback Reply); If not, then the loopback destination node is extracted the routing iinformation of self, and returns to said loopback source node and to carry the Loopback Reply that extracts routing iinformation to some extent;
Step 103: said loopback source node receives the expression wrapped state that said loopback destination node returns and upgrades successful Loopback Reply, then and carry out the said loopback of wanting the loopback message between the loopback destination node.
Particularly, the loopback destination node is resolved said LoopbackRequest after receiving said Loopback Request, extracts said loopback type field, judges whether the message of needs loopback according to said loopback type field.For example, loopback destination node and loopback source node can be through consultation, the value of confirming that the idle loop of said loopback type field returns (Null loopback); When promptly not needing the message of loopback, the value of loopback type field, so; Whether the loopback destination node can be that the idle loop that is provided with in advance returns value through the value of judging the loopback type field, if then do not need the message of loopback; If not, the message that needs loopback is then arranged.
Here, the loopback destination node can be encapsulated into the routing iinformation of self in the said response message with the TLV form, returns to said loopback source node.If said loopback destination node is the endpoint node of current test path, said routing iinformation can comprise the address information of loopback destination node; If said loopback destination node is the intermediate node of current test path, said routing iinformation can comprise the address information of next node of address information and the loopback destination node of loopback destination node.
Here; Do not support the renewal of wrapped state in said loopback destination node, or when not supporting to the said loopback of wanting the loopback message; Said loopback destination node can not be accomplished the renewal of said wrapped state; The failure of renewal wrapped state is then sent the LoopbackReply that the expression wrapped state is upgraded failure to said loopback source node.
In the practical application; Said loopback destination node can be added in said Loopback Reply and is used to represent more newer field of state that wrapped state upgrades situation; Through the said state value of newer field more, indicating said Loopback Reply is that Loopback Reply or wrapped state that wrapped state is upgraded failure are upgraded successful Loopback Reply or carried the Loopback Reply of routing iinformation.
Here; Carry out the said loopback of wanting the loopback message between said loopback source node and the loopback destination node; Can comprise: said loopback source node receives the Loopback Reply that said loopback destination node is returned; Judge whether said Loopback Reply is that the expression wrapped state is upgraded successful Loopback Reply, if carry out the said loopback of wanting the loopback message between said loopback source node and the loopback destination node; Otherwise, do not carry out the said loopback of wanting the loopback message between said loopback source node and the loopback destination node.
Particularly; Said loopback source node receives the Loopback Reply that said loopback destination node is returned; Judge whether said Loopback Reply is that wrapped state is upgraded successful Loopback Reply; If then the loopback source node sends the message of wanting loopback through test path and arrives said loopback destination node; Said loopback destination node receives the said message of wanting loopback, according to the wrapped state of self, the contrary path of the said message of wanting loopback through said test path is returned to said loopback source node; Otherwise, directly finish current loopback operation.
Particularly; In step 101; The Loopback Request that the loopback source node is sent can also comprise and is used to indicate loopback to overflow the life span (TTL of time; Time To Live) field, node on the current test path, that when ttl field is overflowed, receive said Loopback Request upgrades the wrapped state of self as said loopback destination node.So, can be according to the actual detected needs, through the value of ttl field is set in advance, deciding said loopback destination node is the current intermediate node that will detect the path, or endpoint node.For example; Carry out the message loopback at the current a certain node in centre that will detect the path if desired; Through the value of ttl field is set, makes ttl field when Loopback Request is sent on this node, to overflow, thereby carry out the loopback of message as the loopback destination node by this node.
Particularly; After loopback test is accomplished; In the time of need stopping the operation of current loopback, said method can also comprise: said loopback source node sends the LoopbackRequest of the current loopback operation of deletion to said loopback destination node, after said loopback destination node receives this Loopback Request; Reduce self wrapped state, and return the Loopback Reply that current loopback is successfully removed to said loopback source node.
In the practical application; Can in said Loopback Request, add action type (Operation Type) field that is used to represent current LoopbackRequest type; Through the value of said action type field is set, indicate the Loopback Request of said Loopback Request for the current loopback operation of deletion.
Accordingly; The present invention also provides a kind of system of message loopback; Said system mainly can comprise: loopback source node and loopback destination node, wherein, the loopback source node; Be used for sending the Loopback Request that is used to ask to carry out the loopback operation, include the loopback type field of the loopback type of message that is used to indicate among this Loopback Request through current test path; Receiving after expression wrapped state that said loopback destination node returns upgrades successful Loopback Reply, and carrying out the said loopback of wanting the loopback message between the said loopback destination node; The loopback destination node; Be used to receive the LoopbackRequest that said loopback source node sends; Judge whether needs loopback message according to the loopback type field among the said Loopback Request, if then the loopback destination node is according to said loopback type field; The wrapped state of self is updated to the wrapped state of wanting the loopback message to said, and returns the expression wrapped state to said loopback source node and upgrade successful Loopback Reply; If not, then the loopback destination node is extracted the routing iinformation of self, and returns to said loopback source node and to carry the Loopback Reply that extracts routing iinformation to some extent.
Wherein, said loopback source node sends Loopback Request and also includes and be used to indicate loopback to overflow life span (TTL) field of time; Said loopback destination node specifically is used for when the ttl field of said LoopbackRequest is overflowed, and self wrapped state is updated to the wrapped state of wanting the loopback message to said, and returns Loopback Reply to said loopback source node.
Wherein, Said loopback source node specifically is used for; Receive the LoopbackReply that said loopback destination node is returned; Judge whether said Loopback Reply is that the expression wrapped state is upgraded successful LoopbackReply, if, and carry out the said loopback of wanting the loopback message between the said loopback destination node; Otherwise, do not carry out the said loopback of wanting the loopback message.
Here, said loopback source node also is used for when needs stop the operation of current loopback, and said loopback source node sends the Loopback Request of the current loopback operation of deletion to said loopback destination node; Said loopback destination node, also be used to receive this Loopback Request after, reduce self wrapped state, and return the Loopback Reply that current loopback is successfully removed to said loopback source node.
In the practical application, said loopback source node can be source node or any intermediate node except that the loopback destination node on the current test path; Said loopback destination node can be any intermediate node or the endpoint node on the current test path on the current test path, except that the loopback source node.
Embodiment one
Present embodiment will elaborate to a kind of embodiment of message loop back method of the present invention.
In the present embodiment; The message structure of Loopback Request is as shown in Figure 2, and Loopback Request can comprise following field: be used to represent current Loopback Request type action type (OperationType), be used to represent the loopback type operations type of message (Message Type), be used to represent the current loopback type of message (Loopback Type) of wanting the loopback type of message.In addition, also include among the Loopback Request and be used to indicate loopback to overflow the ttl field (Fig. 2 does not show) of time.
Wherein, present embodiment is as follows pre-configured: Message Type value is 0, and the expression type of message is a request message; Operation Type is used to represent that the current action type that will carry out carries out loopback, or deletion loopback; Can preestablish Operation Type value is 1 o'clock; Indicate to carry out loopback, the OperationType value is 2 o'clock, indicates to delete current loopback; Loopback Type representes the current type of wanting the loopback message, and when not needing the message of loopback, this Loopback Type representes that idle loop returns (Null loopback); Can preestablish; Loopback Type value is 0 o'clock, expression Null loopback, the promptly current message that does not need loopback; The value of Loopback Type can be come concrete the setting according to the type of wanting the loopback message, and for example, the value that can set Loopback Type is 1 o'clock, and the message of the loopback of indicating is the DM message.The concrete value of ttl field decides according to the current status transmission of test path and the interstitial content wanted, and is this area common technology means, repeats no more at this.
In addition; Can also comprise following field in the Loopback Request message: Return Code, Reserve, packet content or type lengths values (PDU Information or TLV); Be reserved field, all nonsensical in Loopback Request message.
Here; The structural similarity of the structure of Loopback Reply message and Loopback Request message; As shown in Figure 3; Also can comprise following field in the Loopback Reply message: Operation Type, Message Type, Loopback Type, Return Code, Reserve, PDU Information or TLV, wherein, Return Code is used to represent the wrapped state of peer node in the Loopback Reply message.
Predetermined configurations is following: Message Type value is 1, and the expression type of message is a response message; The ReturnCode value is 0 o'clock, representes that current Loopback Reply message is an infomational message, corresponding to the Null loopback; To return the routing iinformation of loopback destination node to the source end node; Return Code value is 1 o'clock, and expression loopback destination node is set self wrapped state success, and Return Code value is 2 o'clock; It is fixed that expression loopback destination node does not support wrapped state to reset, and the loopback destination node is set self wrapped state failure; PDUInformation or TLV is used to carry the routing iinformation of loopback destination node.Other each fields are identical with the implication of corresponding field among the above-mentioned Loopback Request, repeat no more.
As shown in Figure 4; Carry out loopback test at needs, as need measure the time, for transfer path A-B-C-D to the time-delay of transfer path A-B-C-D, Loss Rate etc.; Between the node A and node D at two ends on this path; Realize the loopback of a certain particular type message, detailed process is as shown in Figure 5, specifically can comprise the steps:
Step 501: source end node A generates Loopback Request (LoopbackRequest) message as the loopback source node, and transmits through said transfer path A-B-C-D;
Particularly; Source end node A generates Loopback Request according to structure shown in Figure 2, and wherein, concrete configuration is following: Message Type value is 0; The value of Operation Type is 1, and LoopbackType is provided with and the corresponding value of type of wanting the loopback message.For example, value that can Loopback Type is set to 1, representes that current to want the type of message of loopback be DM.In addition, also ttl field is set to overflow at peer node D.
Step 502: when peer node D received the Loopback Request message of source end node A transmission, the ttl field among the Loopback Request was overflowed, and then peer node D carries out dissection process as the loopback destination node to Loopback Request message.
Step 503: peer node D judges whether to carry out the operation of Null loopback, if then directly continue step 405 according to the Loopback Request message that is received; Otherwise, continue step 404;
Particularly, peer node D resolves received Loopback Request message, obtains Loopback the type field wherein; Judge whether said Loopback the type field value is 0, if then need carry out the Null loopback; Otherwise, need not carry out the Null loopback.
Step 504: according to the Loopback Request message that is received, peer node D resets the wrapped state of self;
Particularly; Peer node D at first judge self whether support said Loopback Type the loopback operation of corresponding message; If support, then the wrapped state with self changes to " to the Loopback state of the corresponding message of said Loopback Type ", and wrapped state is provided with success; If do not support, then wrapped state is provided with failure.
In the practical application, the prewired wrapped state sign that is equipped with among the peer node D, peer node D can judge whether to carry out the loopback operation according to the wrapped state sign.In this step; Peer node D is after receiving LoopbackRequest; Verify whether self current wrapped state sign is consistent with the Loopback Type in the said Loopback Request message, if unanimity, the wrapped state of then not changing self identifies; If inconsistent, then change to self loopback status indicator consistent with said Loopback Type.
Step 505: peer node D generates Loopback Reply message, and sends to source end node A according to self current wrapped state and the said Loopback Request message that receives;
In the present embodiment; Message Type in the peer node D Loopback Reply message is set to 1, representes that this message is a response message, is provided with among Operation Type, Loopback Type and the LoopbackRequest consistent; Operating result according to step 503～504; Return Code is set, generates the LoopbackReply message, and be sent to source end node A through reverse path D-C-B-A.
Here, corresponding Null loopback operation, peer node D is encapsulated in the Loopback Reply message with the routing iinformation of TLV mode with self, and packaged routing iinformation comprises the address information of self.
In the practical application, for intermediate node, packaged routing iinformation can comprise the address information of next node of address information and the said node of said node self in Loopback Reply message.
Step 506: source end node A receives the Loopback Reply message of peer node D feedback;
Step 507: source end node A judges the wherein value of Return Code according to received Loopback Reply message, continues step 408 or continuation step 409 or finishes current flow process;
Particularly, source end node A judges whether the value of Return Code in the said Loopback Reply message is 0, if, represent that then this Loopback Reply message is the info class message, continue step 408; If the value of Return Code is 1, then continue step 409; If the value of Return Code is 2, then finish current flow process.
Step 508: source end node A resolves received Loopback Reply message; Obtain the routing iinformation of TLV form packaged in this message; And resulting routing iinformation analyzed, the routing iinformation of study peer node D finishes current flow process;
Step 509: source end node A generates and wants the message of loopback and send to peer node D;
Particularly, source end node A generates the loopback message of corresponding types according to the value of Loopback Type in the said Loopback Reply message.
For example, when the corresponding type of message of the value of Loopback Type was DM, then end node A in source generated the DM message, and the DM message that is generated is sent to peer node D as the loopback message.
Step 510: the loopback message that peer node D reception sources end node A sends according to the wrapped state of self, returns to said source end node A with said loopback message;
Step 511: source end node A receives the loopback message that peer node D returns, and carries out the test of correlated performance and obtaining of peer node D address information.
For example, for the DM message, can be according to the timestamp on the DM message that is looped back to source end node A (Time Stamps) information, the unidirectional or two-way delay of calculating current test path.
Step 512: when needs stopped the operation of current loopback, source end node A generated the Loopback Request (UnLoopback Request) that is used to delete current loopback operation, and sends to peer node D;
Particularly, source end node A generates UnLoopback Request according to structure shown in Figure 2, and wherein, concrete configuration is following: Message Type value is 0, and the value of Operation Type is 2, and the value of other each fields can not be provided with, and is sky.
Step 513: after peer node D receives the UnLoopback Request of source end node A transmission, remove the wrapped state of self, generate corresponding UnLoopback Reply message and also return to source end node A;
Here, peer node D receives the UnLoopback Request that source end node A sends, and resolving and obtaining Operation Type value is 2; Then with the Loopback recovering state of self current setting to non-wrapped state, generate corresponding UnLoopback Reply message, promptly according to message structure shown in Figure 3; And concrete configuration is following: Message Type value is 1, and the value of Operation Type is 2, and the value of other each fields can not be provided with; Be sky, afterwards, send this UnLoopback Reply message to source end node A; To remove loopback Loopback state, recover normal condition and handle message the particular type message.
Step 514: source end node A stops the transmission of said loopback message after receiving said UnLoopback Reply message, and current loopback flow process finishes.
Need to prove; In the foregoing description; A certain intermediate node carries out the loopback operation of particular type message on the path if desired, for example, on Node B on the transfer path A-B-C-D or node C, carries out the loopback operation of particular type message; Can make the loopback operation of message on Node B or node C, to carry out through the ttl field in the said Loopback Request message is set.Here, it is similar with above-mentioned flow process shown in Figure 5 that a certain intermediate node carries out the idiographic flow of particular type message loopback operation on the test path, repeats no more at this.
The above is merely preferred embodiment of the present invention, is not to be used to limit protection scope of the present invention, all any modifications of within spirit of the present invention and principle, being done, is equal to replacement and improvement etc., all should be included within protection scope of the present invention.
Claims (10)
1. a message loop back method is characterized in that, said method comprises:
The loopback source node sends the loopback request (Loopback Request) that is used to ask to carry out the loopback operation through current test path, includes the loopback type field of the loopback type of message that is used to indicate among this Loopback Request;
Loopback destination node on the current test path receives said Loopback Request; Judge whether needs loopback message according to the loopback type field among the said Loopback Request; If; Then the loopback destination node is according to said loopback type field, self wrapped state is updated to the wrapped state of wanting the loopback message to said, and returns the expression wrapped state to said loopback source node and upgrade successful LoopbackReply; If not, then the loopback destination node is extracted the routing iinformation of self, and returns to said loopback source node and to carry the Loopback Reply that extracts routing iinformation to some extent;
Said loopback source node receives the expression wrapped state that said loopback destination node returns and upgrades successful Loopback Reply, then and carry out the said loopback of wanting the loopback message between the loopback destination node.
2. message loop back method according to claim 1 is characterized in that, said method also comprises:
The Loopback Request that said loopback source node is sent also includes and is used to indicate loopback to overflow life span (TTL) field of time; Node on the current test path, that when ttl field is overflowed, receive said Loopback Request is as said loopback destination node; Upgrade the wrapped state of self, and return Loopback Reply to said loopback source node.
3. message loop back method according to claim 1 is characterized in that, said method also comprises:
Do not support the renewal of wrapped state in said loopback destination node, or when not supporting to the said loopback of wanting the loopback message; Said loopback destination node can not be accomplished the renewal of said wrapped state; The failure of renewal wrapped state is then sent the Loopback Reply that the expression wrapped state is upgraded failure to said loopback source node.
4. according to each described message loop back method of claim 2 to 3, it is characterized in that, carry out the said loopback of wanting the loopback message between said loopback source node and the loopback destination node, comprising:
Said loopback source node receives the Loopback Reply that said loopback destination node is returned; Judge whether said Loopback Reply is that the expression wrapped state is upgraded successful Loopback Reply; If carry out the said loopback of wanting the loopback message between said loopback source node and the loopback destination node; Otherwise, do not carry out the said loopback of wanting the loopback message between said loopback source node and the loopback destination node.
5. message loop back method according to claim 4 is characterized in that, carries out between said loopback source node and the loopback destination node after the said loopback of wanting the loopback message, and said method also comprises:
When needs stop the operation of current loopback; Said loopback source node sends the Loopback Request of the current loopback operation of deletion to said loopback destination node; After said loopback destination node receives this LoopbackRequest; Reduce self wrapped state, and return the Loopback Reply that current loopback is successfully removed to said loopback source node.
6. message loopback system is characterized in that said system comprises: loopback source node and loopback destination node, wherein,
The loopback source node is used for sending the Loopback Request that is used to ask to carry out the loopback operation through current test path, includes the loopback type field of the loopback type of message that is used to indicate among this Loopback Request; Receiving after expression wrapped state that said loopback destination node returns upgrades successful Loopback Reply, and carrying out the said loopback of wanting the loopback message between the said loopback destination node;
The loopback destination node; Be used to receive the Loopback Request that said loopback source node sends; Judge whether needs loopback message according to the loopback type field among the said Loopback Request, if then the loopback destination node is according to said loopback type field; The wrapped state of self is updated to the wrapped state of wanting the loopback message to said, and returns the expression wrapped state to said loopback source node and upgrade successful LoopbackReply; If not, then the loopback destination node is extracted the routing iinformation of self, and returns to said loopback source node and to carry the Loopback Reply that extracts routing iinformation to some extent.
7. according to the said message loopback of claim 6 system, it is characterized in that said loopback source node sends Loopback Request and also includes and be used to indicate loopback to overflow life span (TTL) field of time;
Said loopback destination node specifically is used for when the ttl field of said Loopback Request is overflowed, and self wrapped state is updated to the wrapped state of wanting the loopback message to said, and returns Loopback Reply to said loopback source node.
8. according to the said message loopback of claim 7 system; It is characterized in that said loopback source node specifically is used for; Receive the Loopback Reply that said loopback destination node is returned; Judge whether said LoopbackReply is that the expression wrapped state is upgraded successful Loopback Reply, if, and carry out the said loopback of wanting the loopback message between the said loopback destination node; Otherwise, do not carry out the said loopback of wanting the loopback message.
9. according to each said message loopback system of claim 7 to 8; It is characterized in that; Said loopback source node also is used for when needs stop the operation of current loopback, and said loopback source node sends the Loopback Request of the current loopback operation of deletion to said loopback destination node;
Said loopback destination node, also be used to receive this Loopback Request after, reduce self wrapped state, and return the Loopback Reply that current loopback is successfully removed to said loopback source node.
10. according to each said message loopback system of claim 7 to 8, it is characterized in that said loopback source node is source node or any intermediate node except that the loopback destination node on the current test path; Said loopback destination node is any intermediate node or the endpoint node on the current test path on the current test path, except that the loopback source node.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201110008654.5A CN102594582B (en) | 2011-01-14 | 2011-01-14 | A kind of message loop back method and system |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201110008654.5A CN102594582B (en) | 2011-01-14 | 2011-01-14 | A kind of message loop back method and system |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN102594582A true CN102594582A (en) | 2012-07-18 |
| CN102594582B CN102594582B (en) | 2017-12-15 |
Family
ID=46482805
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201110008654.5A Expired - Fee Related CN102594582B (en) | 2011-01-14 | 2011-01-14 | A kind of message loop back method and system |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN102594582B (en) |
Cited By (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN105634944A (en) * | 2014-11-26 | 2016-06-01 | 华为技术有限公司 | Routing loop determination method and equipment |
| CN107317727A (en) * | 2017-06-30 | 2017-11-03 | 迈普通信技术股份有限公司 | Loop testing method, device and router |
| CN107342830A (en) * | 2016-05-03 | 2017-11-10 | 工业和信息化部电信研究院 | One kind realizes Packet Transport Network performance degradation localization method |
| CN108234317A (en) * | 2017-12-14 | 2018-06-29 | 北京华为数字技术有限公司 | A kind of tunnel loop back method and its relevant device |
| CN109660373A (en) * | 2017-10-10 | 2019-04-19 | 深圳市中兴微电子技术有限公司 | The method and communication equipment, computer readable storage medium of remote loopback detection |
| CN114245978A (en) * | 2019-09-05 | 2022-03-25 | 欧姆龙株式会社 | Host device, arithmetic processing device, programmable logic controller, network, and method |
Citations (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20040143781A1 (en) * | 2003-01-21 | 2004-07-22 | Dimambro Francesco | System and method for non-intrusive loopback testing |
| CN1992638A (en) * | 2005-12-26 | 2007-07-04 | 华为技术有限公司 | Method and system for obtaining path maximum transmission unit in network |
| CN101325584A (en) * | 2007-06-15 | 2008-12-17 | 华为技术有限公司 | Method for tracing route, MPLS network system and entry node thereof |
| US20100238812A1 (en) * | 2009-03-23 | 2010-09-23 | Cisco Technology, Inc. | Operating MPLS label switched paths and MPLS pseudowire in loopback mode |
| CN101848223A (en) * | 2010-05-25 | 2010-09-29 | 中兴通讯股份有限公司 | Network processor-based method and device for realizing quick bidirectional forwarding detection of messages |
| CN101895459A (en) * | 2009-05-19 | 2010-11-24 | 中兴通讯股份有限公司 | Method and device for transmitting extended BDI message |
-
2011
- 2011-01-14 CN CN201110008654.5A patent/CN102594582B/en not_active Expired - Fee Related
Patent Citations (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20040143781A1 (en) * | 2003-01-21 | 2004-07-22 | Dimambro Francesco | System and method for non-intrusive loopback testing |
| CN1992638A (en) * | 2005-12-26 | 2007-07-04 | 华为技术有限公司 | Method and system for obtaining path maximum transmission unit in network |
| CN101325584A (en) * | 2007-06-15 | 2008-12-17 | 华为技术有限公司 | Method for tracing route, MPLS network system and entry node thereof |
| US20100238812A1 (en) * | 2009-03-23 | 2010-09-23 | Cisco Technology, Inc. | Operating MPLS label switched paths and MPLS pseudowire in loopback mode |
| CN101895459A (en) * | 2009-05-19 | 2010-11-24 | 中兴通讯股份有限公司 | Method and device for transmitting extended BDI message |
| CN101848223A (en) * | 2010-05-25 | 2010-09-29 | 中兴通讯股份有限公司 | Network processor-based method and device for realizing quick bidirectional forwarding detection of messages |
Cited By (12)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN105634944A (en) * | 2014-11-26 | 2016-06-01 | 华为技术有限公司 | Routing loop determination method and equipment |
| US10003524B2 (en) | 2014-11-26 | 2018-06-19 | Huawei Technologies Co., Ltd. | Routing loop determining method and device |
| CN105634944B (en) * | 2014-11-26 | 2018-11-09 | 华为技术有限公司 | Route loop determines method and apparatus |
| CN107342830A (en) * | 2016-05-03 | 2017-11-10 | 工业和信息化部电信研究院 | One kind realizes Packet Transport Network performance degradation localization method |
| CN107342830B (en) * | 2016-05-03 | 2019-05-03 | 工业和信息化部电信研究院 | A kind of realization Packet Transport Network performance deterioration localization method |
| CN107317727A (en) * | 2017-06-30 | 2017-11-03 | 迈普通信技术股份有限公司 | Loop testing method, device and router |
| CN109660373A (en) * | 2017-10-10 | 2019-04-19 | 深圳市中兴微电子技术有限公司 | The method and communication equipment, computer readable storage medium of remote loopback detection |
| CN109660373B (en) * | 2017-10-10 | 2021-12-24 | 深圳市中兴微电子技术有限公司 | Method for far-end loopback detection, communication equipment and computer readable storage medium |
| CN108234317A (en) * | 2017-12-14 | 2018-06-29 | 北京华为数字技术有限公司 | A kind of tunnel loop back method and its relevant device |
| CN108234317B (en) * | 2017-12-14 | 2021-02-23 | 北京华为数字技术有限公司 | Tunnel loopback method and related equipment thereof |
| CN114245978A (en) * | 2019-09-05 | 2022-03-25 | 欧姆龙株式会社 | Host device, arithmetic processing device, programmable logic controller, network, and method |
| CN114245978B (en) * | 2019-09-05 | 2023-08-01 | 欧姆龙株式会社 | Host device, operation processing device, controller, network system, and method |
Also Published As
| Publication number | Publication date |
|---|---|
| CN102594582B (en) | 2017-12-15 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN102594582A (en) | Looping back method and system of message | |
| CN100417080C (en) | Method for detecting network chain fault and positioning said fault | |
| JP5836477B2 (en) | Data communication apparatus, data communication system, and data communication method | |
| CN101056215B (en) | A network performance measurement method and system | |
| JP5505875B2 (en) | Delay measurement system, delay measurement method, delay measurement apparatus, and delay measurement program | |
| CN102164051B (en) | Service-oriented fault detection and positioning method | |
| EP2688240B1 (en) | Method, system and device for switching and selecting clock source device | |
| CN104054304A (en) | Computer system, controller, switch, communication method, and recording medium in which network management program has been stored | |
| JP5875696B2 (en) | Data distribution system, distribution device, terminal device, and data distribution method | |
| CN110393001A (en) | Method and apparatus for modularly guiding AVB crossfire | |
| CN102136965B (en) | Method for detecting tunnel faults and traffic engineering (TE) node | |
| CN107645449B (en) | Path planning method and heaven-earth integrated network system | |
| CN108683568B (en) | Method and system for sectional detection of VPN service channel quality | |
| CN105960770A (en) | Method for operating node in network and node device | |
| JP2011188046A (en) | Packet communication system and method for controlling packet communication apparatus | |
| CN101895459B (en) | Method and device for transmitting extended BDI message | |
| EP3869739B1 (en) | Method for monitoring apparatus | |
| CN102740390B (en) | Machine-to-machine/man (M2M) system and communication method thereof, M2M platform and terminal | |
| EP2712121A1 (en) | Method, apparatus and system for detecting packet path signal degraded | |
| CN103580884B (en) | Method, system, sending ending equipment and the receiving device of relaying configuration | |
| CN105721296A (en) | Method for improving stability of chain structure ZigBee network | |
| CN112822105A (en) | Path planning method and device and data transmission system | |
| GB2537657A (en) | Subsea control system communication network | |
| CN117979388B (en) | Ad hoc network video communication method and system | |
| KR20130093745A (en) | System of delay tolerant network using the optimum number of fragment packet and the transmission method |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| C06 | Publication | ||
| PB01 | Publication | ||
| C10 | Entry into substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant | ||
| CF01 | Termination of patent right due to non-payment of annual fee | ||
| CF01 | Termination of patent right due to non-payment of annual fee |
Granted publication date: 20171215 Termination date: 20210114 |