CN102594582B - A kind of message loop back method and system - Google Patents
A kind of message loop back method and system Download PDFInfo
- Publication number
- CN102594582B CN102594582B CN201110008654.5A CN201110008654A CN102594582B CN 102594582 B CN102594582 B CN 102594582B CN 201110008654 A CN201110008654 A CN 201110008654A CN 102594582 B CN102594582 B CN 102594582B
- 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.)
- Expired - Fee Related
Links
Landscapes
- Data Exchanges In Wide-Area Networks (AREA)
Abstract
The invention discloses a kind of message loop back method, methods described includes：Loopback source node sends the Loopback Request for asking progress loops back by current test path, and the loopback type field that loopback type of message is wanted for expression is included in the Loopback Request；Loopback destination node on current test path receives Loopback Request, judges whether to need loopback message according to loopback type field therein, if it is, returning to the LoopbackReply for representing that wrapped state is updated successfully to the loopback source node；If it is not, then the Loopback Reply for carrying routing iinformation are returned to the loopback source node；The loopback source node receives the Loopback Reply that the expression wrapped state that the loopback destination node returns is updated successfully, then wants the loopback of loopback message described in progress between loopback destination node.The invention also discloses a kind of message looped-back system, can avoid influenceing the transmission of other service messages and the monitoring management in path, and can effectively improve the efficiency of message loopback test.
Description
Technical field
The present invention relates to the loopback technology of message, more particularly to a kind of message loop back method and system.
Background technology
For current group transmission net, when realizing loopback (Loopback) function, two kinds of situations are primarily present：One kind is
Loopful under non-traffic state (Out-of-service) returns (Full Loopback) technology, and this kind of Loopback technology is main
Connection or correlated performance for test path to all messages, it is necessary to carry out loops back so that all messages all can not be by
Transmitted according to normal operation flow, have influence on being normally carried out for business；Another kind is in non-interrupting service state (In-
Service the operation management maintainance (OAM, Operation Administration and Maintenance) under)
Loopback technologies, the Loopback technologies are to carry out loops back to all OAM messages, although not influenceing other messages such as
The normal transmission of Business Stream, but due to needing to carry out loopback to all OAM messages, the normal monitoring in path is influenced whether, for example,
When needing to test two-way time delay, it is only necessary to the loopback of delay measurements (DM, Delay Measurement) message, but it is logical
Above-mentioned OAM Loopback technologies are crossed, then loopback are all carried out to all OAM messages so that other in addition to DM messages
OAM message can not be transmitted according to normal operation flow, so as to cause other OAM(Operation Administration Maintenance)s normally to implement.
In addition, two kinds of above-mentioned Loopback technologies will not carry routing information, also in message loop-back process is carried out
It is unable to realizing route tracking (RouterTrace) function, it is impossible to the discovery of path topology information and the positioning of failure are carried out, because
This, it is also necessary to after loopback test, the discovery of path topology information and the positioning of failure are further carried out, is unfavorable for path event
The exclusion of barrier.
The content of the invention
In view of this, can be in loopback mistake it is a primary object of the present invention to provide a kind of message loop back method and system
Loops back only is carried out to required particular type message in journey, influences whether that business is normal to solve existing loopback technology
The problem of implementation.
To reach above-mentioned purpose, the technical proposal of the invention is realized in this way：
The invention provides a kind of message loop back method, methods described includes：Loopback source node passes through current test path
Send for asking the loopback for carrying out loops back to ask (Loopback Request), included in the LoopbackRequest
There is the loopback type field that loopback type of message is wanted for expression；Described in loopback destination node on current test path receives
Loopback Request, the loopback type field in the Loopback Request judge whether to need loopback report
Text, if it is, the wrapped state of itself is updated to want ring to described by loopback destination node according to the loopback type field
The wrapped state of text is returned, and the Loopback Reply for representing that wrapped state is updated successfully are returned to the loopback source node；
If it is not, then loopback destination node extracts the routing iinformation of itself, and return to carry to the loopback source node and extracted road
By the Loopback Reply of information；The loopback source node receives the expression wrapped state that the loopback destination node returns
The Loopback Reply being updated successfully, then the loopback of loopback message is wanted described in progress between loopback destination node.
In such scheme, methods described also includes：LoopbackRequest transmitted by the loopback source node is also wrapped
It is on current test path, when ttl field is overflowed containing for indicating that loopback overflows life span (TTL) field of time
The node of the Loopback Request is received as the loopback destination node, updates the wrapped state of itself, and to
The loopback source node returns to Loopback Reply.
In such scheme, methods described also includes：The loopback destination node do not support wrapped state renewal or
When person does not support the loopback for wanting loopback message to described, the loopback destination node can not complete the wrapped state more
Newly, wrapped state failure is updated, then the Loopback for representing wrapped state renewal failure is sent to the loopback source node
Reply。
The ring of loopback message is wanted described in being carried out in such scheme, between the loopback source node and loopback destination node
Return, including：The loopback source node receives the Loopback Reply that the loopback destination node returns, described in judgement
Whether Loopback Reply are to represent the Loopback Reply that wrapped state is updated successfully, if it is, the loopback source is saved
The loopback of loopback message is wanted described in being carried out between point and loopback destination node；Otherwise, the loopback source node and loopback purpose section
Without the loopback for wanting loopback message between point.
The loopback of loopback message is wanted described in being carried out in such scheme, between the loopback source node and loopback destination node
Afterwards, methods described also includes：When needing to stop current loops back, the loopback source node is to the loopback destination node
The Loopback Request for deleting current loops back are sent, the loopback destination node receives the Loopback
After Request, the wrapped state of itself is reduced, and return to the Loopback that current loopback successfully releases to the loopback source node
Reply。
Present invention also offers a kind of message looped-back system, the system includes：Loopback source node and loopback destination node,
Wherein, loopback source node, for sending the Loopback for asking progress loops back by current test path
Include the loopback type field that loopback type of message is wanted for expression in Request, the Loopback Request；Receiving
After the Loopback Reply that the expression wrapped state returned to the loopback destination node is updated successfully, with the loopback purpose
The loopback of loopback message is wanted described in being carried out between node；Loopback destination node, for receiving the loopback source node transmission
Loopback Request, the loopback type field in the Loopback Request judge whether to need loopback report
Text, if it is, the wrapped state of itself is updated to want ring to described by loopback destination node according to the loopback type field
The wrapped state of text is returned, and the LoopbackReply for representing that wrapped state is updated successfully is returned to the loopback source node；Such as
Fruit is no, then loopback destination node extracts the routing iinformation of itself, and returns to carry to the loopback source node and extracted route
The Loopback Reply of information.
In such scheme, the loopback source node sends Loopback Request and also included for indicating that loopback overflows
Go out life span (TTL) field of time；The loopback destination node, specifically for the Loopback Request's
When ttl field is overflowed, the wrapped state of itself is updated to the wrapped state for wanting loopback message, and to the loopback source
Node returns to Loopback Reply.
In such scheme, the loopback source node, it is specifically used for, receives what the loopback destination node returned
Loopback Reply, judge whether the Loopback Reply are to represent the Loopback that wrapped state is updated successfully
Reply, if it is, wanting the loopback of loopback message described in being carried out between the loopback destination node；Otherwise, wanted without described
The loopback of loopback message.
In such scheme, the loopback source node, it is additionally operable to when needing to stop current loops back, the loopback source
Node sends the Loopback Request for deleting current loops back to the loopback destination node；The loopback purpose section
Point, it is additionally operable to after receiving the Loopback Request, reduces the wrapped state of itself, and return to the loopback source node
The Loopback Reply that current loopback successfully releases.
In such scheme, the loopback source node is for the source node on current test path or in addition to loopback destination node
Any one intermediate node；The loopback destination node is any one on current test path, in addition to loopback source node
Endpoint node on intermediate node or current test path.
The message loop back method and system of the present invention, the type of loopback message is wanted by instruction in being asked in loopback, is realized
Loops back to specifying type of message, so as to avoid influenceing the monitoring management of the transmission of other service messages and path,
And the efficiency of message loopback test can be effectively improved, improves the degree of accuracy accordingly tested and speed.
In addition, the present invention realizes the RouterTrace work(in message loop-back process also by setting Null loops backs
Can, so as to carry out the positioning of the discovery of path route information and abort situation.
Brief description of the drawings
Fig. 1 is the implementation process figure of the message loop back method of the present invention；
Fig. 2 is Loopback Request message structure schematic diagram；
Fig. 3 is Loopback Reply message structure schematic diagram；
Fig. 4 is the schematic diagram of message loop-back path in a kind of specific embodiment of the present invention；
Fig. 5 is the implementation process figure of message loop-back process in a kind of specific embodiment of the present invention.
Embodiment
The present invention basic thought be：Loops back only is carried out to the type of message of source end node particular requirement, to realize
Performance test and RouterTrace functions to path, so as to by extending a kind of new Loopback functions, realize to spy
Determine the loops back of type message, specifically, be exactly using the loop fuction of extension, realize to a certain path, including label
On forward-path (LSP, Label Switched Path), pseudo-wire (PW, Pseudo wire) and link layer (Section) etc.
Particular type message, including the message of the specific a certain type such as test, OAM carry out loopback, to realize to a certain item on path
Can, such as：The measurement of delay, Loss Rate etc., it on the one hand can avoid influenceing the monitoring management of the transmission and path to business；It is another
Aspect realizes RouterTrace functions, carries out discovery and the fault bit of path route information by setting Null loops backs
The positioning put.
The message loop back method of the present invention, shown in reference picture 1, mainly may comprise steps of：
Step 101：Loopback source node is sent for asking the loopback for carrying out loops back to be asked by current test path
(Loopback Request), the loopback type for representing to want loopback type of message is included in the Loopback Request
Field；
Step 102：Loopback destination node on current test path receives the Loopback Request, according to described
Loopback type field in Loopback Request judges whether to need loopback message, if it is, loopback destination node root
According to the loopback type field, the wrapped state of itself is updated to the wrapped state for wanting loopback message, and to described
Loopback source node returns to the loopback response (Loopback Reply) for representing that wrapped state is updated successfully；If it is not, then loopback mesh
Node extraction itself routing iinformation, and return to carry to the loopback source node and extracted the Loopback of routing iinformation
Reply；
Step 103：The loopback source node receives the expression wrapped state that the loopback destination node returns and is updated to
The Loopback Reply of work(, then the loopback of loopback message is wanted described in progress between loopback destination node.
Specifically, after loopback destination node receives the Loopback Request, to the LoopbackRequest
Parsed, extract the loopback type field, judge whether the message of loopback in need according to the loopback type field.Example
Such as, loopback destination node through consultation, can determine that the idle loop of the loopback type field returns (Null rings with loopback source node
Return) value, i.e., when not needing the message of loopback, the value of loopback type field, in this way, loopback destination node can be by sentencing
Whether the value that abscission ring returns type field is that the idle loop pre-set returns value, if it is, not needing the message of loopback, such as
Fruit is not, then the message of loopback in need.
Here, the routing iinformation of itself can be encapsulated into the response message by loopback destination node in the form of TLV, be returned
Back to the loopback source node.If the loopback destination node is the endpoint node of current test path, the routing iinformation
The address information of loopback destination node can be included；If the loopback destination node is the intermediate node of current test path,
The routing iinformation can include the address of the address information of loopback destination node and the next node of loopback destination node
Information.
Here, the renewal of wrapped state is not supported in the loopback destination node or do not support to want loopback report to described
During the loopback of text, the loopback destination node can not complete the renewal of the wrapped state, renewal wrapped state failure, then to
The loopback source node sends the LoopbackReply for representing wrapped state renewal failure.
In practical application, the loopback destination node can be added in the Loopback Reply for representing loopback
State updates the state more newer field of situation, by the value of the state more newer field, indicates the Loopback Reply
The Loopback Reply or carry that Loopback Reply or wrapped state for wrapped state renewal failure are updated successfully
There are the Loopback Reply of routing iinformation.
Here, the loopback of loopback message is wanted described in being carried out between the loopback source node and loopback destination node, can be wrapped
Include：The loopback source node receives the Loopback Reply that the loopback destination node returns, and judges the Loopback
Whether Reply is to represent the Loopback Reply that wrapped state is updated successfully, if it is, the loopback source node and loopback mesh
Node between carry out described in want the loopback of loopback message；Otherwise, do not enter between the loopback source node and loopback destination node
The loopback of loopback message is wanted described in row.
Specifically, the loopback source node receives the Loopback Reply that the loopback destination node returns, and judges institute
State whether Loopback Reply are Loopback Reply that wrapped state is updated successfully, if it is, loopback source node leads to
Cross test path and send and want the message of loopback to the loopback destination node；The loopback destination node wants loopback described in receiving
Message, according to the wrapped state of itself, the message for loopback is returned to by the inverse path of the test path described
Loopback source node；Otherwise, current loops back is directly terminated.
Specifically, in a step 101, the Loopback Request transmitted by loopback source node can also include being used to refer to
Show that loopback overflows life span (TTL, Time To Live) field of time, it is on current test path, overflowed in ttl field
When receive the Loopback Request node as the loopback destination node, update the wrapped state of itself.Such as
This, can be according to actually detected needs, by pre-setting the value of ttl field, to determine that the loopback destination node is to work as
Before to detect the intermediate node or endpoint node in path.For example, if necessary to currently detect a certain section in centre in path
Point carries out message loopback, by the value for setting ttl field so that ttl field can be sent in Loopback Request
Overflowed when on the node, so as to carry out the loopback of message as loopback destination node by the node.
Specifically,, it is necessary to when stopping current loops back, methods described can also include after the completion of loopback test：Institute
State loopback source node and the LoopbackRequest for deleting current loops back, the loopback are sent to the loopback destination node
After destination node receives the Loopback Request, the wrapped state of itself is reduced, and return to the loopback source node
The Loopback Reply that current loopback successfully releases.
In practical application, it can be added in the Loopback Request for representing current
Action type (Operation Type) field of LoopbackRequest types, by setting the action type field
Value, it is the Loopback Request for deleting current loops back to indicate the Loopback Request.
Accordingly, present invention also offers a kind of system of message loopback, the system can mainly include：Save in loopback source
Point and loopback destination node, wherein, loopback source node, for being sent by current test path for asking to carry out loops back
Loopback Request, the loopback type for representing to want loopback type of message is included in the Loopback Request
Field；After the Loopback Reply that the expression wrapped state for receiving the loopback destination node return is updated successfully, with
The loopback of loopback message is wanted described in being carried out between the loopback destination node；Loopback destination node, for receiving the loopback source
The LoopbackRequest that node is sent, the loopback type field in the Loopback Request judge whether need
Loopback message is wanted, if it is, loopback destination node is according to the loopback type field, the wrapped state of itself is updated to pair
The wrapped state for wanting loopback message, and the Loopback for representing that wrapped state is updated successfully is returned to the loopback source node
Reply；If it is not, then loopback destination node extracts the routing iinformation of itself, and return and carried to the loopback source node
Extract the Loopback Reply of routing iinformation.
Wherein, the loopback source node sends Loopback Request and also included for indicating that loopback overflows the time
Life span (TTL) field；The loopback destination node, specifically for the ttl field spilling in the LoopbackRequest
When, the wrapped state of itself is updated to the wrapped state for wanting loopback message, and is returned to the loopback source node
Loopback Reply。
Wherein, the loopback source node is specifically used for, and receives the LoopbackReply that the loopback destination node returns,
Judge whether the Loopback Reply are to represent the LoopbackReply that is updated successfully of wrapped state, if it is, with it is described
The loopback of loopback message is wanted described in being carried out between loopback destination node；Otherwise, without the loopback for wanting loopback message.
Here, the loopback source node, it is additionally operable to when needing to stop current loops back, the loopback source node is to institute
State loopback destination node and send the Loopback Request for deleting current loops back；The loopback destination node, is additionally operable to
After receiving the Loopback Request, the wrapped state of itself is reduced, and current loopback is returned to the loopback source node
The Loopback Reply that success releases.
In practical application, the loopback source node can be source node on current test path or except loopback destination node
Any one outer intermediate node；The loopback destination node can be appointing on current test path, in addition to loopback source node
The endpoint node anticipated on an intermediate node or current test path.
Embodiment one
The present embodiment, a kind of embodiment of message loop back method of the present invention will be elaborated.
In the present embodiment, Loopback Request message structure is as shown in Fig. 2 Loopback Request can be wrapped
Containing following field：For representing the action type (OperationType) of current Loopback Request types, for representing
The type of message (Message Type) of loopback type operation, for representing currently to want the loopback type of message of loopback type of message
(Loopback Type).In addition, also include in Loopback Request for indicating that loopback overflows the ttl field of time
(Fig. 2 does not show).
Wherein, the present embodiment is pre-configured with as follows：Message Type values are 0, represent that type of message is request message；
Operation Type are used to represent that currently the action type to be carried out to be to carry out loopback or delete loopback, can set in advance
Determine Operation Type values for 1 when, expression will carry out loopback, and when OperationType values are 2, expression, which will delete, works as
Preceding loopback；Loopback Type represent the current type for wanting loopback message, should when not needing the message of loopback
Loopback Type represent that idle loop returns (Null loopbacks), can preset, and when Loopback Type values are 0, represent
Null loopbacks, i.e., currently without the message for needing loopback；Loopback Type value can be according to the type for wanting loopback message
Specifically set, for example, when can set Loopback Type value as 1, the message for representing to want loopback is DM messages.TTL
The specific value of field determines according to current status transmission and the interstitial content for wanting test path, is technology commonly used in the art
Means, it will not be repeated here.
In addition, following field can also be included in Loopback Request messages：Return Code, Reserve, number
It is reserved field, in Loopback Request according to perhaps type lengths values (PDU Information or TLV) in bag
It is nonsensical in message.
Here, the structure of Loopback Reply messages is similar to the structure of Loopback Request messages, such as Fig. 3 institutes
Show, following field can also be included in Loopback Reply messages：Operation Type、Message Type、
Loopback Type, Return Code, Reserve, PDU Information or TLV, wherein, Loopback Reply
Return Code are used for the wrapped state for representing peer node in message.
Predetermined configurations are as follows：Message Type values are 1, represent that type of message is response message；ReturnCode takes
Be worth for 0 when, it is infomational message to represent current Loopback Reply messages, corresponding to Null loopbacks, to be returned to source end node
The routing iinformation of loopback destination node, when Return Code values are 1, represent that loopback destination node sets itself wrapped state
Success, when Return Code values are 2, it is fixed to represent that loopback destination node does not support wrapped state to reset, loopback destination node is set
Fixed itself wrapped state failure；PDUInformation or TLV, for carrying the routing iinformation of loopback destination node.Other
Each field is identical with the implication of corresponding field in above-mentioned Loopback Request, repeats no more.
As shown in figure 4, needing to carry out loopback test, enter if desired for the delay to transmitting path A-B-C-D, Loss Rate etc.
During row measurement, for transmitting path A-B-C-D, on the path between the node A and node D at both ends, a certain spy is realized
Determine the loopback of type message, detailed process is as shown in figure 5, specifically may include steps of：
Step 501：Source end node A is as loopback source node, generation Loopback Request (LoopbackRequest)
Message, and transmitted by the transmitting path A-B-C-D；
Specifically, source end node A is according to the Request of structural generation Loopback shown in Fig. 2, wherein, concrete configuration is such as
Under：The value that Message Type values are 0, Operation Type is 1, and LoopbackType is set and wants loopback message
The corresponding value of type.For example, Loopback Type value can be arranged to 1, the current message for wanting loopback is represented
Type is DM.In addition, also ttl field is arranged to overflow in peer node D.
Step 502：When peer node D receives the Loopback Request messages of source end node A transmissions, Loopback
Ttl field in Request is overflowed, then peer node D is carried out as loopback destination node to Loopback Request messages
Dissection process.
Step 503：Peer node D judges whether to need to carry out according to the Loopback Request messages received
Null loops backs, if it is, continuing directly to step 405；Otherwise, step 404 is continued；
Specifically, peer node D parses to received Loopback Request messages, obtains therein
Loopback the type fields, judge whether the Loopback the type fields value is 0, if it is, needing to carry out Null
Loopback, otherwise, it is not necessary to carry out Null loopbacks.
Step 504：According to the Loopback Request messages received, peer node D resets the loopback of itself
State；
Specifically, peer node D first determines whether itself whether support the loopback of message corresponding to the Loopback Type
Operation, if supported, the wrapped state of itself is changed to " to correspond to the Loopback Type Loopback of message
State ", wrapped state are set successfully；If it does not, then wrapped state setup failed.
In practical application, wrapped state mark is pre-configured with peer node D, peer node D can be according to wrapped state mark
Knowledge judges whether to loops back.In this step, peer node D verifies that itself works as after LoopbackRequest is received
Whether preceding wrapped state mark is consistent with the Loopback Type in the Loopback Request messages, if unanimously,
Do not change then itself wrapped state mark, if it is inconsistent, by itself loopback status indicator be changed to it is described
Loopback Type are consistent.
Step 505：Peer node D is according to itself current wrapped state and the Loopback received
Request messages, Loopback Reply messages are generated, and be sent to source end node A；
In the present embodiment, the Message Type in Loopback Reply messages are arranged to 1 by peer node D, are represented
The message is response message, consistent in setting Operation Type, Loopback Type and LoopbackRequest, according to
The operating result of step 503~504, Return Code are set, generate LoopbackReply messages, and pass through reverse path D-
C-B-A is sent to source end node A.
Here, the routing iinformation of itself is encapsulated in by corresponding Null loops backs, peer node D in a manner of TLV
In Loopback Reply messages, packaged routing iinformation includes the address information of itself.
In practical application, for intermediate node, packaged routing iinformation can wrap in Loopback Reply messages
Include the address information of the node itself and the address information of the next node of the node.
Step 506：Source end node A receives the Loopback Reply messages of peer node D feedbacks；
Step 507：Source end node A judges wherein Return Code according to received Loopback Reply messages
Value, continue step 408 or continue step 409 or terminate current process；
Specifically, source end node A judges whether the value of Return Code in the Loopback Reply messages is 0,
If it is, representing that the Loopback Reply messages are info class message, continue step 408；If Return Code's takes
It is worth for 1, then continues step 409；If Return Code value is 2, terminate current process.
Step 508：Source end node A parses to received Loopback Reply messages, obtains in the message
The routing iinformation of packaged TLV forms, and resulting routing iinformation is analyzed, study peer node D route letter
Breath, terminate current process；
Step 509：Source end node A generations want the message of loopback and are sent to peer node D；
Specifically, source end node A is according to the value of Loopback Type in the Loopback Reply messages, generation
The loopback message of corresponding types.
For example, when type of message corresponding to value in Loopback Type is DM, then source end node A generates DM messages,
And the DM messages generated are sent to peer node D as loopback message.
Step 510：Peer node D receives the loopback message that source end node A is sent, according to the wrapped state of itself, by institute
State loopback message and return to the source end node A；
Step 511：Source end node A receives the loopback message that peer node D is returned, and carries out test and the opposite end of correlated performance
The acquisition of node D address informations.
For example, for DM messages, can be according to the timestamp (Time being looped back on source end node A DM messages
Stamps) information, to calculate the unidirectional or two-way delay of current test path.
Step 512：When needing to stop current loops back, source end node A is generated for deleting current loops back
Loopback Request (UnLoopback Request), and it is sent to peer node D；
Specifically, source end node A is according to the Request of structural generation UnLoopback shown in Fig. 2, wherein, concrete configuration is such as
Under：The value that Message Type values are 0, Operation Type is 2, and the value of other each fields can be not provided with,
For sky.
Step 513：After peer node D receives the UnLoopback Request of source end node A transmissions, itself is released
Wrapped state, UnLoopback Reply messages corresponding to generation simultaneously return to source end node A；
Here, peer node D receives the UnLoopback Request of source end node A transmissions, and parsing obtains
Operation Type values are 2, then the Loopback states currently set itself return to non-wrapped state, and generation is corresponding
UnLoopback Reply messages, i.e., according to message structure shown in Fig. 3, and concrete configuration is as follows：Message Type values
Value for 1, Operation Type is 2, and the value of other each fields can be not provided with, and be sky, afterwards, to source end node
A sends the UnLoopback Reply messages, to release the loopback Loopback states to particular type message, recovers normal shape
State handles message.
Step 514：After source end node A receives the UnLoopback Reply messages, stop the loopback message
Send, current loopback flow terminates.
It should be noted that in above-described embodiment, particular type message is carried out if necessary to a certain intermediate node on path
Loops back, for example, carrying out the loopback behaviour of particular type message on node B or node C on transmitting path A-B-C-D
Make, can be by setting the ttl field in the Loopback Request messages so that the loops back of message can save
Carried out on point B or node C.Here, a certain intermediate node carries out the specific stream of particular type message loops back on test path
Journey is similar to flow shown in above-mentioned Fig. 5, will not be repeated here.
The foregoing is only a preferred embodiment of the present invention, is not intended to limit the scope of the present invention, it is all
All any modification, equivalent and improvement made within the spirit and principles in the present invention etc., it should be included in the protection of the present invention
Within the scope of.
Claims (10)
1. a kind of message loop back method, it is characterised in that methods described includes：
Loopback source node is sent for asking the loopback for carrying out loops back to ask Loopback by current test path
Include the loopback type field that loopback type of message is wanted for expression in Request, the Loopback Request；
Loopback destination node on current test path receives the Loopback Request, according to the Loopback
Loopback type field in Request judges whether to need loopback message, if it is, loopback destination node is according to the loopback
Type field, the wrapped state of itself is updated to the wrapped state for wanting loopback message, and to the loopback source node
Return to the Loopback Reply for representing that wrapped state is updated successfully；If it is not, then loopback destination node extracts the route of itself
Information, and returned to the loopback source node and carry the Loopback Reply for having extracted routing iinformation；
The loopback source node receives the Loopback that the expression wrapped state that the loopback destination node returns is updated successfully
Reply, then loopback message is wanted described in generation and wants the loopback of loopback message described in progress between loopback destination node.
2. message loop back method according to claim 1, it is characterised in that methods described also includes：
Loopback Request transmitted by the loopback source node also include for indicating that loopback overflows the existence of time
Time ttl field, node on current test path, receiving when ttl field is overflowed the Loopback Request
As the loopback destination node, the wrapped state of itself is updated, and Loopback Reply are returned to the loopback source node.
3. message loop back method according to claim 1, it is characterised in that methods described also includes：
The renewal of wrapped state is not supported in the loopback destination node or is not supported to the loopback for wanting loopback message
When, the loopback destination node can not complete the renewal of the wrapped state, renewal wrapped state failure, then to the loopback
Source node sends the Loopback Reply for representing wrapped state renewal failure.
4. the message loop back method according to any one of claim 2 to 3, it is characterised in that the loopback source node and ring
Return between destination node and want the loopback of loopback message described in carrying out, including：
The loopback source node receives the Loopback Reply that the loopback destination node returns, and judges the Loopback
Whether Reply is to represent the Loopback Reply that wrapped state is updated successfully, if it is, the loopback source node and loopback mesh
Node between carry out described in want the loopback of loopback message；Otherwise, do not enter between the loopback source node and loopback destination node
The loopback of loopback message is wanted described in row.
5. message loop back method according to claim 4, it is characterised in that the loopback source node and loopback destination node
Between carry out described in want the loopback of loopback message after, methods described also includes：
When needing to stop current loops back, the loopback source node sends to the loopback destination node and deletes current loopback
The Loopback Request of operation, after the loopback destination node receives the Loopback Request, reduce itself
Wrapped state, and return to the Loopback Reply that current loopback successfully releases to the loopback source node.
6. a kind of message looped-back system, it is characterised in that the system includes：Loopback source node and loopback destination node, wherein,
Loopback source node, for sending the Loopback for asking progress loops back by current test path
Include the loopback type field that loopback type of message is wanted for expression in Request, the Loopback Request；Receiving
After the Loopback Reply that the expression wrapped state returned to the loopback destination node is updated successfully, loopback is wanted described in generation
Message and the loopback for wanting loopback message described in progress between the loopback destination node；
Loopback destination node, the Loopback Request sent for receiving the loopback source node, according to described
Loopback type field in Loopback Request judges whether to need loopback message, if it is, loopback destination node root
According to the loopback type field, the wrapped state of itself is updated to the wrapped state for wanting loopback message, and to described
Loopback source node returns to the Loopback Reply for representing that wrapped state is updated successfully；If it is not, then loopback destination node is extracted
The routing iinformation of itself, and returned to the loopback source node and carry the Loopback Reply for having extracted routing iinformation.
7. message looped-back system according to claim 6, it is characterised in that the loopback source node sends Loopback
Request also includes for indicating that loopback overflows the life span ttl field of time；
The loopback destination node, specifically for the Loopback Request ttl field spilling when, by the ring of itself
The state of returning is updated to the wrapped state for wanting loopback message, and returns to Loopback Reply to the loopback source node.
8. message looped-back system according to claim 7, it is characterised in that the loopback source node, be specifically used for, receive institute
The Loopback Reply of loopback destination node return are stated, judge whether the Loopback Reply are to represent wrapped state more
New successfully Loopback Reply, if it is, wanting the loopback of loopback message described in being carried out between the loopback destination node；
Otherwise, without the loopback for wanting loopback message.
9. according to any one of claim 7 to the 8 message looped-back system, it is characterised in that the loopback source node, be additionally operable to
When needing to stop current loops back, the loopback source node sends to the loopback destination node and deletes current loops back
Loopback Request；
The loopback destination node, it is additionally operable to after receiving the Loopback Request, reduces the wrapped state of itself, and to
The loopback source node returns to the Loopback Reply that current loopback successfully releases.
10. according to any one of claim 7 to the 8 message looped-back system, it is characterised in that the loopback source node is current
Source node on test path or any one intermediate node in addition to loopback destination node；The loopback destination node is current
The endpoint node on any one intermediate node or current test path on test path, in addition to 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 CN102594582A (en) | 2012-07-18 |
| CN102594582B true 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) |
Families Citing this family (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN105634944B (en) * | 2014-11-26 | 2018-11-09 | 华为技术有限公司 | Route loop determines method and apparatus |
| 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 |
| CN109660373B (en) * | 2017-10-10 | 2021-12-24 | 深圳市中兴微电子技术有限公司 | Method for far-end loopback detection, communication equipment and computer readable storage medium |
| CN108234317B (en) * | 2017-12-14 | 2021-02-23 | 北京华为数字技术有限公司 | Tunnel loopback method and related equipment thereof |
| JP7327017B2 (en) * | 2019-09-05 | 2023-08-16 | オムロン株式会社 | Master Device, Processing Unit, Programmable Logic Controller, Network, and Method |
Family Cites Families (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 |
| CN101325584B (en) * | 2007-06-15 | 2012-08-29 | 华为技术有限公司 | Method for tracing route, MPLS network system and entry node thereof |
| US8391163B2 (en) * | 2009-03-23 | 2013-03-05 | Cisco Technology, Inc. | Operating MPLS label switched paths and MPLS pseudowire in loopback mode |
| CN101895459B (en) * | 2009-05-19 | 2015-01-28 | 中兴通讯股份有限公司 | Method and device for transmitting extended BDI message |
| CN101848223B (en) * | 2010-05-25 | 2014-08-13 | 中兴通讯股份有限公司 | Network processor-based method and device for realizing quick bidirectional forwarding detection of messages |
-
2011
- 2011-01-14 CN CN201110008654.5A patent/CN102594582B/en not_active Expired - Fee Related
Also Published As
| Publication number | Publication date |
|---|---|
| CN102594582A (en) | 2012-07-18 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN102594582B (en) | A kind of message loop back method and system | |
| US20220086073A1 (en) | Data packet detection method, device, and system | |
| US7869376B2 (en) | Communicating an operational state of a transport service | |
| CN102164051B (en) | Service-oriented fault detection and positioning method | |
| CA2602289A1 (en) | Using a fixed network wireless data collection system to improve utility responsiveness to power outages | |
| CN101729296B (en) | Method and system for statistical analysis of ethernet traffic | |
| CN101094121B (en) | Method, system and device for detecting Ethernet links among not direct connected devices | |
| EP1819096A1 (en) | A method for acquiring network key performance indicators and the key performance indicators groupware thereof | |
| CN106817301A (en) | Fault recovery method and device, controller, software defined network | |
| CN101145977B (en) | A QoS monitoring system and its measuring method of IP data network | |
| CN106656791A (en) | Device state switching method, device and system | |
| CN110381467A (en) | A kind of car networking emergency communication method, apparatus and system | |
| CN104518936B (en) | Link dynamic aggregation method and apparatus | |
| CN105490936B (en) | A kind of rapid data transmission method for avoiding conflict based on SDN | |
| CN101420331A (en) | Fast fault locating method for ultra-long connection in T-MPLS network | |
| CN102611610B (en) | The method and system of a kind of many same paths tunnels centralized management | |
| CN110048872A (en) | A kind of network alarm method, apparatus, system and terminal | |
| CN101777997A (en) | Method and system for switching flow of network link | |
| JP2013519261A (en) | Network communication link test equipment and test method | |
| CN106453074A (en) | Switching method and apparatus | |
| CN105897580B (en) | A kind of unrelated forwarding network quick fault testing of agreement and traffic protection switching method | |
| EP2858302B1 (en) | Connectivity check method of service stream link, related apparatus and system | |
| CN102916883B (en) | LINK detection method and routing forwarding equipment | |
| CN105960770A (en) | Method for operating node in network and node device | |
| CN101232406A (en) | OAM fast detecting method, apparatus and system |
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 |