CN102082678A - Processing method and equipment of port discarding OAM (Operation, Administration and Maintenance) protocol - Google Patents
Processing method and equipment of port discarding OAM (Operation, Administration and Maintenance) protocol Download PDFInfo
- Publication number
- CN102082678A CN102082678A CN2009102386956A CN200910238695A CN102082678A CN 102082678 A CN102082678 A CN 102082678A CN 2009102386956 A CN2009102386956 A CN 2009102386956A CN 200910238695 A CN200910238695 A CN 200910238695A CN 102082678 A CN102082678 A CN 102082678A
- Authority
- CN
- China
- Prior art keywords
- oam
- message
- value
- information
- entity
- 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.)
- Pending
Links
Images
Landscapes
- Mobile Radio Communication Systems (AREA)
Abstract
The invention discloses a processing method and equipment of a port discarding an Ethernet OAM (Operation, Administration and Maintenance) protocol, wherein the processing method comprises the following steps that: A, after OAM connection is established between a first OAM entity and a second OAM entity, the second OAM entity sends an OAM protocol discarding notice to the first OAM entity when needing to discard the configured OAM protocol; B, if the first OAM entity receives the OAM protocol discarding notice, the first OAM entity does not notify an upper layer to execute switching operation; and if the first OAM entity does not receive the OAM protocol discarding notice or receive an information OAM PDU (Protocol Data Unit) message sent by the second OAM entity for continuous preset value N seconds, the first OAM entity determines that a link is out of order and notify the upper layer to execute the switching operation. Due to the adoption of the processing method and equipment, an opposite end can know the information that an opposite end discards the OAM protocol so that different processes can be executed according to different reasons.
Description
Technical field
The present invention relates to network management technology, particularly a kind of port is cancelled ethernet operation, is administered and maintained the processing method and the equipment of (OAM:Operation, Administration and Maintenance) agreement.
Background technology
OAM is a kind of instrument of monitor network fault, is operated in data link layer, and its protocol massages is called as OAM Protocol Data Unit (OAMPDU:OAM Protocol Data Units).Referring to Fig. 1, Fig. 1 is the form schematic diagram of OAMPDU in the prior art.As shown in Figure 1, this OAMPDU mainly comprises destination address field (DAF) (Dest addr), source address field (Source addr), message protocol type field (Type), message protocol sub-type field (Subtype), identification field (Flags), type of message field (Code), data field (Data/Pad) and check field (CRC), wherein, the implication represented of each field is as shown in table 1 below:
In the prior art, mainly there are three types in the OAMPDU message, represents to be used to control loopback control (Loopback Control) OAMPDU message of the OAM wrapped state of remote equipment when information (Information) the OAMPDU message, value of representing to be used to notify the OAM entity status information when being respectively Code field value for 0x00 represents to be used for event notice (Event Notification) OAMPDU message that link failure is alarmed and value for 0x04 during for 0x01.Wherein, utilize information OAMPDU message can set up OAM between two OAM entities and connect, the OAM entity here is essentially the port that has disposed the OAM agreement.
Referring to Fig. 2, Fig. 2 is for setting up the flow chart that OAM connects in the prior art.Be connected if an OAM entity needs to set up OAM with the 2nd OAM entity, then as shown in Figure 2, this flow process can may further comprise the steps:
Step 201 after an OAM entity is configured the OAM agreement, sends primary information OAMPDU message to the opposite end every 1 second.Here, carried the local information of self in the information OAMPDU message that an OAM entity sends.
Step 202, the class of operation that an OAM entity is carried out in the 2nd OAM entity and the step 201 seemingly.
After step 203, an OAM entity receive the information OAMPDU message of opposite end transmission,, only carried the information of opposite end, then sent information OAMPDU message to the opposite end every 1 second again if the information OAMPDU message that receives does not carry the local information of self.Here, carried the local information of self in the information OAMPDU message that an OAM entity sends again and the information of the opposite end that the information OAMPDU message that receives from the opposite end carries.
We can say that when carrying out step 202, an OAM entity has just entered semi-connection state, also do not enter the OAM connection status fully.
Step 204, the class of operation that an OAM entity is carried out in the 2nd OAM entity and the step 203 seemingly.
Step 205, an OAM entity if this information OAMPDU message has carried the local information of self and the information of opposite end, then enter the OAM connection status after receiving the information OAMPDU message of opposite end transmission; Otherwise, return the operation of carrying out similar step 203.
Step 206, the class of operation that an OAM entity is carried out in the 2nd OAM entity and the step 205 seemingly.
So far, to step 206, realized OAM establishment of connection operation between an OAM entity and the 2nd OAM entity by above-mentioned steps 201.
Step 207, after setting up the OAM connection between an OAM entity and the 2nd OAM entity, the one OAM entity and the 2nd OAM entity also need send information OAMPDU message (this message carried local information and to client information) every 1 second, if an OAM entity or the 2nd OAM entity did not receive the information OAMPDU message that the opposite end sends in continuous 5 seconds, then determine link occurs fault, switch on the notice upper strata.
As can be seen, when an OAM entity or the 2nd OAM entity did not receive the information OAMPDU message of opposite end transmission in continuous 5 seconds in the above-mentioned steps 207, determine that all this is former because link occurs fault.And in fact an OAM entity or the 2nd OAM entity reason that do not receive the information OAMPDU message that the opposite end sends in continuous 5 seconds is not all to be caused by link occurs fault, also might be that to cause sending information OAMPDU message caused because the OAM agreement has been cancelled in the opposite end, and prior art unified processing according to the situation of link occurs fault when not receiving the information OAMPDU message that the opposite end sends obviously be irrational.
Summary of the invention
The invention provides a kind of processing method and equipment of port cancellation OAM agreement, so that set up the information that an end of OAM connection is clearly known opposite end cancellation OAM agreement, and then avoided prior art owing to can not distinguish link failure and cancel the problem that the OAM agreement is produced.
Technical scheme provided by the invention is achieved in that
A kind of processing method of port cancellation OAM agreement, this method may further comprise the steps:
A, after setting up OAM between an OAM entity and the 2nd OAM entity and connecting, the 2nd OAM entity sends the OAM abrogation of agreement and is notified to an OAM entity when the OAM agreement that the needs cancellation has been disposed;
B if an OAM entity receives described OAM abrogation of agreement notice, does not notify the upper strata to carry out handover operation; If do not receive the information OAM PDU message that described OAM abrogation of agreement notice and continuous preset value N do not receive the transmission of the 2nd OAM entity second, then determine link occurs fault, handover operation is carried out on the notice upper strata.
A kind of OAM entity comprises:
Receiving element, after being used to receive described OAM entity and opposite end and setting up OAM and be connected, the OAM abrogation of agreement notice that the opposite end sends when the OAM agreement that the needs cancellation has been disposed;
Determining unit when described receiving element receives OAM abrogation of agreement notice, does not notify the upper strata to carry out handover operation; When not receiving described OAM abrogation of agreement notice, if the continuous preset value N of described receiving element does not receive the information OAMPDU message that described opposite end sends second, then determine link occurs fault, handover operation is carried out on the notice upper strata.
As can be seen from the above technical solutions, among the present invention, after setting up the OAM connection between the one OAM entity and the 2nd OAM entity,, then do not notify the upper strata to carry out handover operation if an OAM entity receives the 2nd OAM entity determining the OAM abrogation of agreement notice that sends when needing to cancel the OAM agreement; Do not receive the information OAM PDU message that the 2nd OAM entity sends in second if receive described OAM abrogation of agreement notice and continuous preset value N, then determine link occurs fault, handover operation is carried out on the notice upper strata.As can be seen, by method provided by the invention, the one OAM entity is clearly known the information that the 2nd OAM entity is cancelled the OAM agreement, and, can make the first OAM entity be easy to distinguish opposite end cancellation OAM agreement and two kinds of situations of link failure, and then carry out different processing, avoid prior art owing to can not distinguish link failure and cancel the problem that the OAM agreement is produced at different situations, such as, unified handle according to the situation of link occurs fault etc.
Description of drawings
Fig. 1 is the form schematic diagram of OAMPDU in the prior art;
Fig. 2 is for setting up the flow chart that OAM connects in the prior art;
The flow chart that Fig. 3 provides for the embodiment of the invention;
The increase that Fig. 4 a provides for the embodiment of the invention form schematic diagram of information OAMPDU message of self-defined information;
When the OAM entity that Fig. 4 b provides for the embodiment of the invention receives the information OAMPDU message of the 2nd OAM entity transmission, do not notify the upper strata to carry out the flow chart of handover operation;
The form schematic diagram of the structure OAMPDU message that Fig. 4 c provides for the embodiment of the invention;
When the OAM entity that Fig. 4 d provides for the embodiment of the invention receives the information OAMPDU message of the 2nd OAM entity transmission, do not notify the upper strata to carry out another flow chart of handover operation;
The structure chart of the OAM entity that Fig. 5 provides for the embodiment of the invention.
Embodiment
In order to make the purpose, technical solutions and advantages of the present invention clearer, describe the present invention below in conjunction with the drawings and specific embodiments.
In the practical application, the reason that the OAM entity does not receive the information OAMPDU message that the opposite end sends continuously is not all to be caused by link occurs fault, might be that to cause sending information OAMPDU message caused because the OAM agreement has been cancelled in the opposite end yet; And cancel two kinds of situations of OAM agreement owing to not distinguishing link occurs fault and opposite end in the prior art, handle according to the situation of link occurs fault when being unified in the information OAMPDU message that does not receive the opposite end transmission, some irrational phenomenons have been caused, in view of the situation, the embodiment of the invention provides a kind of processing method of port cancellation OAM agreement, specifically referring to shown in Figure 3.
Referring to Fig. 3, the flow chart of the method that Fig. 3 provides for the embodiment of the invention.In the present embodiment, be connected if an OAM entity is set up OAM according to flow process shown in Figure 2 with the 2nd OAM entity, then as shown in Figure 3, this flow process can may further comprise the steps:
Step 301, after setting up OAM between an OAM entity and the 2nd OAM entity and connecting, the 2nd OAM entity sends the OAM abrogation of agreement and is notified to an OAM entity when the OAM agreement that the needs cancellation has been disposed.
In this step 301, the 2nd OAM entity can confirm that when the OAM that receives outside input annuls the agreement order current state is the OAM agreement that needs cancellation to dispose.
Here, can be in the prior art usually 5 of usefulness during preset value N specific implementation; Also can be the user according to other values that actual conditions are provided with, specifically do not limit in the present embodiment.
Preferably, an OAM entity is receiving the OAM abrogation of agreement notice that the 2nd OAM entity sends in the present embodiment, perhaps continuously when preset value N does not receive the information OAM PDU message of the 2nd OAM entity transmission in second, can further comprise: directly the OAM with between the 2nd OAM entity that set up of disconnection is connected, and enter set up with the 2nd OAM entity between OAM be connected initial condition before.
As can be seen, in the present embodiment, when an OAM entity is determined the 2nd OAM entity and need be cancelled the OAM agreement, and handle, promptly notify the upper strata to carry out handover operation not according to the situation of link occurs fault in the prior art; But do not notify the upper strata to carry out handover operation, directly get back to carry out with the 2nd OAM entity between set up the initial condition of OAM before being connected, avoided follow-up in the prior art and when receiving the information OAMPDU message of opposite end transmission, unified to handle the unreasonable problem of being brought according to the situation of link occurs fault.
So far, by aforesaid operations, realized the flow process that the embodiment of the invention provides.
Need to prove that in the embodiment of the invention, the OAM abrogation of agreement that the 2nd OAM entity sends can have multiple way of realization when notifying specific implementation, is described below by two kinds of embodiments when needs cancellation OAM agreement.Certainly, these two kinds of embodiments are a kind of giving an example, and the application of the non-limiting embodiment of the invention.
First kind of execution mode: the OAM abrogation of agreement notice that the 2nd OAM entity sends is for having increased the information OAMPDU message of self-defined information, specifically: existing information OAMPDU message is expanded, made this information OAMPDU message increase self-defined information.Here, self-defined information mainly comprises: organize detailed value field (Organization Specific Value), perhaps comprise: organize at least one the combination in detailed value field and information type field (Information Type), message length field (Information Length) and the equipment vendors' identification field (OUI:Organization Unique Identifier), it is example that present embodiment comprises these four fields with self-defined information.In the present embodiment, because the OAM entity of having set up the OAM connection in the prior art is when the information of transmission OAMPDU message, this information OAMPDU message need carry local information and to client information, so, in the OAMPDU message that the 2nd OAM entity sends in the present embodiment data/filling field comprise local information at least, to client information and self-defined information, specifically can be referring to shown in Fig. 4 a.
Wherein, the implication represented of each field of comprising of self-defined information is specific as follows:
Organize the detailed value field, the value 2 (or being other any one values except that value 1) of supposing the value 1 that comprises expression cancellation OAM protocol information and not carrying out processing, such as, when receive that the opposite end sends carried the information OAMPDU message of organizing specific field the time, if this tissue specific field value is value 1, can determine that then the opposite end need cancel the OAM agreement, otherwise, value is not then handled the information OAMPDU message of this reception for being worth at 2 o'clock.In the present embodiment, the value 1 by equipment vendors according to the actual conditions setting, such as, can be 0x01; Here, be 0x01, then be worth 2 to can be 0 any one among the 0x02-0xFF if be worth 1.Here, " 0x " expression hexadecimal.
Information type field: represent whether current information OAMPDU message has increased the information OAMPDU message of self-defined information, such as, when receiving the information OAMPDU message of opposite end transmission, if the information type field value that this information OAMPDU message carries has increased the value of self-defined information for this information of expression OAMPDU message.During such as 0xFE, represent that then the information OAMPDU message of current reception has increased self-defined information.
Message length field: be used to represent information type field, the message length field that self-defined information comprises and organize the shared byte number of detailed value field (these three fields abbreviate the TLV field as) that usually, this byte number is 6.
The OUI field: be used for the indication equipment identification of the manufacturer, such as, when value is 0x000FE2, represent magnificent three device identifications.
Description based on above-mentioned each field, comprising above-mentioned four fields with self-defined information is example, when then an OAM entity received the information OAMPDU message of the 2nd OAM entity transmission in the step 302 in the present embodiment, not notifying the upper strata to carry out the concrete step of handover operation can be referring to the flow process shown in Fig. 4 b.Shown in Fig. 4 b, this flow process can may further comprise the steps:
Here, judgement among the step 402b is specially: an OAM entity is judged equipment vendors' sign in equipment vendors' identification field that self-defined information comprised that this information OAMPDU message increases, and the equipment vendors' sign with self storage is identical, if identical, determine that then the equipment vendors in this equipment vendors' identification field are designated self discernible sign; Otherwise, determine that the equipment vendors' sign in this equipment vendors' identification field is not self discernible sign.
So far, can realize that by this first kind of execution mode an OAM entity knows whether the opposite end has cancelled the operation of OAM agreement.
Second kind of execution mode: the OAM abrogation of agreement notice that the 2nd OAM entity sends is the OAM PDU message of observing the OAM agreement of equipment vendor oneself structure, here, structure OAMPDU message is the same with OAMPDU message of the prior art, comprise each field as shown in Figure 1, need to prove, stipulate in the existing OAM agreement, when type of message field (Code) value that comprises when the OAMPDU message is 0xFE, represent that this OAMPDU is the OAMPDU message of equipment vendor oneself structure, therefore, in the present embodiment, for observing the OAM agreement, the type of message field that can make the OAMPDU message that equipment vendor oneself constructs fixedly value is 0xFE.
In the present embodiment, structure OAMPDU message is than existing OAMPDU message, also increased self-defining field, this self-defining field mainly comprises: message identification field, this message identification field specifically comprise message protocol type field (Type), OAM protocol command Value field (Value) and are used for representing the length field (Length) of Value field length or comprise: message identification field and equipment vendors' identification field and fill at least one combination of field (pad).Present embodiment is an example to comprise message identification field (specifically comprise message protocol type field, OAM protocol command Value field and be used to represent the length field of Value field length), equipment vendors' identification field and to fill field, specifically can be referring to the schematic diagram shown in Fig. 4 c.
Wherein, the implication represented of each field is specific as follows:
The message protocol type field, the Extended Protocol type of message that expression cancellation OAM agreement initiatively sends, comprise expression and determine the value of needs cancellation OAM agreement, in the present embodiment, for introducing conveniently, the value of supposing the message protocol type field is during for value 3, expression is determined to cancel the OAM agreement, when the value of message protocol type field during for value 4, then the OAMPDU message of structure is not carried out any processing, such as, when receive that the opposite end sends carried the structure OAMPDU message of message protocol type field the time, if this message protocol type field value, then can be determined the opposite end for being worth 3 and need cancel the OAM agreement; Otherwise,, do not handle the structure OAMPDU message of this reception when value is when being worth 4.In practice, the value 3 by equipment vendors according to the actual conditions setting, such as, can be 0; Here, be 0 if be worth 3, then be worth 4 any one that can be among the 0x01-0xFF.
Length field, the length of expression Value field, when the length field value was preset value M, expression needed to handle the Value field; Otherwise expression is not handled, and here, M can be 1 or other values.Such as, when receiving the structure OAMPDU message that has carried length field, if this length field value be preset value M such as 1, then the entrained Value field of this structure OAMPDU message need is handled in expression; Otherwise, do not handle the structure OAMPDU message of this reception.
What whether Value field, expression carried out cancellation OAM agreement sets up the opening operation that OAM is connected with the 2nd OAM entity; When Value field value is to be expressed as the value during such as 0x01 of carrying out cancellation OAM agreement, then disconnecting the OAM with between the 2nd OAM entity that has set up is connected, and enter set up with the 2nd OAM entity between OAM be connected initial condition before, but do not notify the upper strata to carry out handover operation; When other values of Value field value such as be 0 or 0x02-0xFF in any one the time, the structure OAMPDU message that has carried this Value field is not handled in expression.
The OUI field: be used for the indication equipment identification of the manufacturer, such as, when value is 0x000FE2, represent magnificent three device identifications.
Fill field, be used to guarantee the minimum length of Ethernet message, its value can be 0 or for other default values, does not limit here.
Description based on above-mentioned each field, comprising above-mentioned each field with self-defined information is example, when then an OAM entity received the information OAMPDU message of the 2nd OAM entity transmission in the step 302 in the present embodiment, not notifying the upper strata to carry out the concrete step of handover operation can be referring to the flow process shown in Fig. 4 d.Shown in Fig. 4 d, this flow process can may further comprise the steps:
Here, the value of expression structure OAMPDU message is the value 0xFE of OAM agreement regulation.
Here, step 402d can be similar with step 402b.
So far, can realize that by this second kind of execution mode an OAM knows the operation of the 2nd OAM entity cancellation OAM agreement.
The above-mentioned method that the embodiment of the invention is provided is described, and below in conjunction with specific embodiment equipment provided by the invention is described.
Referring to Fig. 5, a kind of structure chart of the OAM entity that Fig. 5 provides for the embodiment of the invention.This OAM entity is specially the port that has disposed the OAM agreement, is used for network and sets up OAM with another OAM entity (to call the opposite end in the following text) and be connected, to realize the fault management of network.As shown in Figure 5, this OAM entity comprises:
Receiving element 501 is used to receive and has set up the OAM abrogation of agreement notice that opposite end that OAM is connected sends with self when the OAM agreement that the needs cancellation has been disposed; And know that described OAM entity is current and whether need to cancel the OAM agreement that has disposed;
Determining unit 502 when receiving element 501 receives OAM abrogation of agreement notice, does not notify the upper strata to carry out handover operation; Do not receiving described OAM abrogation of agreement notice, and receiving element 501 continuous preset value N do not receive the information OAM PDU message that the opposite end sends, then definite link occurs fault, notice upper strata execution handover operation second.
Preferably, as shown in Figure 5, in the present embodiment, described OAM entity also can comprise: transmitting element 503.Wherein,
Transmitting element 503 is used for knowing at receiving element 501 and sends the OAM abrogation of agreement and be notified to described opposite end when the OAM agreement that needs cancellations local terminal OAM entity disposed, need cancel the OAM agreement that has disposed so that described OAM entity is known in the opposite end.
Preferably, in the present embodiment, the OAM abrogation of agreement that described opposite end sends can have multiple way of realization when notifying specific implementation, is that example is described with two kinds of implementations respectively below.
First kind of implementation:
The OAM abrogation of agreement notice that the opposite end sends is for having increased the information OAMPDU message of self-defined information; Described self-defined information comprises: organize the detailed value field, described first value of organizing the detailed value field to comprise to be used to represent to cancel the OAM agreement; So, receiving element 501 receives when having increased the information OAMPDU of self-defined information message, judges whether the value of organizing the detailed value field that self-defined information comprised that this information OAMPDU message increases is described first value; Determining unit 502, only disconnects the OAM with between the 2nd OAM entity that has set up and is connected when being in the judged result of receiving element 501, and enter set up with the 2nd OAM entity between OAM be connected initial condition before, but do not notify upper strata execution handover operation; For not the time, do not handle the information OAMPDU message of reception in judged result.
Wherein, described self-defined information can also comprise information type field and equipment vendors' identification field; As shown in Figure 5, receiving element 501 can comprise:
First judge module 5011 is used for judging whether the value of the information type field that the information OAMPDU message of reception exists is second value that expression has increased the information OAMPDU message of self-defined information; If then determining to receive has increased the information OAMPDU of self-defined information message;
Second judge module 5012, whether the equipment vendors' sign that is used for judging equipment vendors' identification field that self-defined information comprised that the information OAMPDU message of reception increases is self discernible sign, if continue to carry out whether the described value of organizing the detailed value field that self-defined information comprised of judging that this information OAMPDU message increases is the operation of first value;
Determining unit 502 in the judged result of second judge module 5012 when being, only disconnecting the OAM with between the 2nd OAM entity that has set up is connected, and enter set up with the 2nd OAM entity between OAM is connected initial condition before, but do not notify upper strata execution handover operation; For not the time, do not handle the information OAMPDU message of this reception in judged result.
Second kind of implementation:
The OAM abrogation of agreement notice that described opposite end sends is the OAMPDU message of observing the OAM agreement of equipment vendor oneself structure; Here, structure OAMPDU message comprises the message identification field; Described message identification field comprises the 3rd value that is used to represent to cancel the OAM agreement; So, when receiving element 501 receives structure OAMPDU message, judge whether the value of the message identification field that this structure OAMPDU message comprises is the 3rd value; Determining unit 502, only disconnects the OAM with between the 2nd OAM entity that has set up and is connected when being in the judged result of receiving element 501, and enter set up with the 2nd OAM entity between OAM be connected initial condition before, but do not notify upper strata execution handover operation; For not the time, do not handle the structure OAMPDU message of reception in judged result.
Wherein, described message identification field can comprise message protocol type field, OAM protocol command Value field and be used to represent the length field of Value field length; Receiving element 501 can comprise:
First judge module 5011 is used for judging whether the value of the message protocol type field of constructing the OAMPDU message is the 3rd value that is used to represent to determine needs cancellation OAM agreement;
Second judge module 5012, be used in the judged result of first judge module 5011 when being, if the value of described length field is preset value M, whether the value of then judging the described Value field in the structure OAMPDU message is to be used to represent to carry out cancellation OAM agreement and to disconnect and set up the value of OAM attended operation with the 2nd OAM entity;
Determining unit 502 in the judged result of second judge module 5012 when being, only disconnecting the OAM with between the 2nd OAM entity that has set up is connected, and enter set up with the 2nd OAM entity between OAM is connected initial condition before, but do not notify upper strata execution handover operation; In the judged result of first judge module 5011 for not the time, and in the judged result of second judge module 5012 for not the time, do not handle the structure OAMPDU message of this reception.
As can be seen from the above technical solutions, in the embodiment of the invention, after setting up the OAM connection between the one OAM entity and the 2nd OAM entity, if an OAM entity receives the 2nd OAM entity and determines the OAM abrogation of agreement notice that initiatively sends when needing cancellation OAM agreement, then only disconnecting the OAM with between the 2nd OAM entity that has set up is connected, and enter set up with the 2nd OAM entity between OAM is connected initial condition before, but do not notify upper strata execution handover operation; If do not receive the information OAM Protocol Data Unit PDU message that described OAM abrogation of agreement notice and continuous preset value N do not receive the 2nd OAM entity second, then determine link occurs fault, handover operation is carried out on the notice upper strata, like this, the first OAM entity is known the 2nd OAM entity cancellation OAM agreement, and then know according to this, carry out corresponding operation, promptly do not notify the upper strata to carry out handover operation, than prior art, can tell link occurs fault and two kinds of situations of cancellation OAM agreement by right area, and carry out different processing at different situations.
The above only is preferred embodiment of the present invention, and is in order to restriction the present invention, within the spirit and principles in the present invention not all, any modification of being made, is equal to replacement, improvement etc., all should be included within the scope of protection of the invention.
Claims (13)
1. the processing method of port cancellation OAM agreement is characterized in that this method may further comprise the steps:
A, after setting up OAM between an OAM entity and the 2nd OAM entity and connecting, the 2nd OAM entity sends the OAM abrogation of agreement and is notified to an OAM entity when the OAM agreement that the needs cancellation has been disposed;
B, if an OAM entity receives described OAM abrogation of agreement notice, only disconnect the OAM set up and be connected with between the 2nd OAM entity, and enter set up with the 2nd OAM entity between OAM be connected initial condition before, but do not notify upper strata execution handover operation; If do not receive the information OAM Protocol Data Unit PDU message that described OAM abrogation of agreement notice and continuous preset value N do not receive the transmission of the 2nd OAM entity second, then determine link occurs fault, handover operation is carried out on the notice upper strata.
2. method according to claim 1 is characterized in that, in the steps A, the OAM abrogation of agreement notice that described the 2nd OAM entity sends is for having increased the information OAMPDU message of self-defined information;
Described self-defined information comprises: organize the detailed value field, described first value of organizing the detailed value field to comprise to be used to represent to cancel the OAM agreement;
An OAM entity receives OAM abrogation of agreement notice and comprises among the described step B:
B11, an OAM entity receives when having increased the information OAMPDU of self-defined information message, judges whether the value of organizing the detailed value field that self-defined information comprised that this information OAMPDU message increases is described first value; If first value then continue to carry out the described OAM with between the 2nd OAM entity that has set up that only disconnects and is connected, and enter set up with the 2nd OAM entity between OAM be connected initial condition before, but do not notify upper strata execution handover operation; Otherwise, execution in step B12;
B12 does not handle the information OAMPDU message of this reception.
3. method according to claim 2 is characterized in that described self-defined information also comprises equipment vendors' identification field;
Judgement among the described step B11 comprises: whether the equipment vendors' sign in equipment vendors' identification field that self-defined information comprised that the information OAMPDU message that judgement receives increases is self discernible equipment vendors sign, if continue to carry out whether the described value of organizing the detailed value field that self-defined information comprised of judging that this information OAMPDU message increases is the operation of first value; Otherwise, execution in step B12.
4. according to claim 2 or 3 described methods, it is characterized in that described self-defined information also comprises: the information type field;
Among the described step B11, after an OAM entity receives information OAMPDU message, judge whether the value of the information type field that exists in the information OAMPDU message that receives is second value that expression has increased the information OAMPDU message of self-defined information; If then determining to receive has increased the information OAMPDU of self-defined information message.
5. method according to claim 1 is characterized in that, in the steps A, the OAM abrogation of agreement notice that described the 2nd OAM entity sends is the OAMPDU message of observing the OAM agreement of equipment vendor oneself structure; Described structure OAM PDU message comprises the message identification field; Described message identification field comprises the 3rd value that is used to represent to cancel the OAM agreement;
An OAM entity receives OAM abrogation of agreement notice and comprises among the described step B:
B21, when the one OAM entity receives structure OAMPDU message, whether the value of judging the message identification field that this structure OAMPDU message comprises is described the 3rd value, if, continuing to carry out the described OAM with between the 2nd OAM entity that has set up that only disconnects is connected, and enter set up with the 2nd OAM entity between OAM is connected initial condition before, but do not notify upper strata execution handover operation; Otherwise, execution in step B22;
B22 does not handle this structure OAMPDU message.
6. method according to claim 5 is characterized in that, described message identification field comprises message protocol type field, OAM protocol command Value field and is used to represent the length field of Value field length; Described step B21 comprises:
B211, an OAM entity judge whether the value of the message protocol type field in the structure OAMPDU message that receives is the 3rd value that is used to represent to cancel the OAM agreement, if, execution in step B212; Otherwise, execution in step B22;
B212, when the value of described length field is preset value M, whether the value of judging described Value field is to be used to represent to carry out cancellation OAM agreement and disconnection and described the 2nd OAM entity to set up the value of OAM attended operation, if then continue to carry out described step B21 and do not notify the upper strata to carry out handover operation; Otherwise, execution in step B22.
7. method according to claim 6 is characterized in that, described structure OAM PDU message comprises type of message field Code and equipment vendors' identification field;
Among the described step B211, after the one OAM entity receives the OAMPDU message, judge whether the type of message field that exists in this OAMPDU message is the 4th value of expression structure OAMPDU message, if determine that then the OAMPDU message that receives is the structure OAMPDU of equipment vendor oneself message;
The judgement of described step B211 comprises: whether the equipment vendors' sign in equipment vendors' identification field that the structure OAMPDU message that judgement receives comprises is self discernible sign, if continue to carry out described judgement and construct whether the value of the message protocol type field in the OAMPDU message is the 3rd value that is used to represent to cancel the OAM agreement; Otherwise, execution in step B22.
8. an OAM entity is characterized in that, this OAM entity comprises:
Receiving element, after being used to receive described OAM entity and opposite end and setting up OAM and be connected, the OAM abrogation of agreement notice that the opposite end sends when the OAM agreement that the needs cancellation has been disposed; And be used to know that described OAM entity is current whether needs to cancel the OAM agreement that has disposed;
Determining unit when described receiving element receives OAM abrogation of agreement notice, does not notify the upper strata to carry out handover operation; Do not receiving described OAM abrogation of agreement notice, and the continuous preset value N of described receiving element does not receive the information OAM Protocol Data Unit PDU message that described opposite end sends, then definite link occurs fault, notice upper strata execution handover operation second.
9. OAM entity according to claim 8 is characterized in that, described OAM entity also comprises transmitting element; Wherein,
Described transmitting element is used for sending the OAM abrogation of agreement and being notified to described opposite end when local terminal OAM entity receiving element knows that needs cancels the OAM agreement that has disposed, need cancel the OAM agreement that has disposed so that described OAM entity is known in the opposite end.
10. according to Claim 8 or 9 described OAM entities, it is characterized in that the OAM abrogation of agreement notice that described opposite end sends is for having increased the information OAMPDU message of self-defined information; Described self-defined information comprises: organize the detailed value field, described first value of organizing the detailed value field to comprise to be used to represent to cancel the OAM agreement;
Described receiving element receives when having increased the information OAMPDU of self-defined information message, judges whether the value of organizing the detailed value field that self-defined information comprised that this information OAMPDU message increases is described first value;
Described determining unit in the judged result of described receiving element when being, only disconnecting the OAM with between the 2nd OAM entity that has set up is connected, and enter set up with the 2nd OAM entity between OAM is connected initial condition before, but do not notify upper strata execution handover operation; For not the time, do not handle the information OAMPDU message of reception in judged result.
11. OAM entity according to claim 10 is characterized in that, described self-defined information also comprises information type field and equipment vendors' identification field;
Described receiving element comprises:
First judge module is used for judging whether the value of the information type field that the information OAMPDU message of reception exists is second value that expression has increased the information OAMPDU message of self-defined information; If then determining to receive has increased the information OAMPDU of self-defined information message;
Second judge module, whether the equipment vendors' sign that is used for judging equipment vendors' identification field that self-defined information comprised that the information OAMPDU message of reception increases is self discernible sign, if continue to carry out whether the described value of organizing the detailed value field that self-defined information comprised of judging that this information OAMPDU message increases is the operation of first value;
Described determining unit for not the time, is not handled the information OAMPDU message of this reception in the judged result of described second judge module.
12. according to Claim 8 or 9 described OAM entities, it is characterized in that the OAM abrogation of agreement notice that described opposite end sends is the OAMPDU message in accordance with the OAM agreement of equipment vendor oneself structure; Structure OAMPDU message comprises the message identification field; Described message identification field comprises the 3rd value that is used to represent to cancel the OAM agreement;
When described receiving element receives structure OAMPDU message, judge whether the value of the message identification field that this structure OAMPDU message comprises is the 3rd value;
Described determining unit in the judged result of described receiving element when being, only disconnecting the OAM with between the 2nd OAM entity that has set up is connected, and enter set up with the 2nd OAM entity between OAM is connected initial condition before, but do not notify upper strata execution handover operation; For not the time, do not handle the structure OAMPDU message of reception in judged result.
13. OAM entity according to claim 12 is characterized in that, described message identification field comprises message protocol type field, OAM protocol command Value field and is used to represent the length field of Value field length; Described receiving element comprises:
First judge module is used for judging whether the value of the structure OAMPDU message message protocol type field of reception is the 3rd value that is used to represent to cancel the OAM agreement;
Second judge module, be used in the judged result of described first judge module when being, if the value of described length field is preset value M, whether the value of then judging the Value field in the described structure OAMPDU message is to be used to represent to carry out the OAM with between the 2nd OAM entity that disconnection set up be connected, and enter set up with the 2nd OAM entity between OAM is connected initial condition before, but do not notify the value of upper strata execution handover operation;
Described determining unit, continues to carry out the described upper strata of not notifying and carries out handover operation when being in the judged result of described second judge module; In the judged result of described first judge module for not the time, and in the judged result of described second judge module for not the time, do not handle the structure OAMPDU message of this reception.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN2009102386956A CN102082678A (en) | 2009-12-01 | 2009-12-01 | Processing method and equipment of port discarding OAM (Operation, Administration and Maintenance) protocol |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN2009102386956A CN102082678A (en) | 2009-12-01 | 2009-12-01 | Processing method and equipment of port discarding OAM (Operation, Administration and Maintenance) protocol |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN102082678A true CN102082678A (en) | 2011-06-01 |
Family
ID=44088436
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN2009102386956A Pending CN102082678A (en) | 2009-12-01 | 2009-12-01 | Processing method and equipment of port discarding OAM (Operation, Administration and Maintenance) protocol |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN102082678A (en) |
Cited By (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN102333009A (en) * | 2011-10-09 | 2012-01-25 | 中兴通讯股份有限公司 | Link detection method and device, as well as OAM (operation administration and maintenance) entity |
| CN102420828A (en) * | 2011-12-15 | 2012-04-18 | 华为技术有限公司 | Method, device and system for setting protocol management status |
| CN102917389A (en) * | 2012-10-22 | 2013-02-06 | 大唐移动通信设备有限公司 | Method and device for transmission self-detection of base station in LTE (Long Term Evolution) system |
| CN106302146A (en) * | 2016-10-17 | 2017-01-04 | 杭州迪普科技有限公司 | The convergence method of link aggregation and device |
| WO2018120799A1 (en) * | 2016-12-29 | 2018-07-05 | 华为技术有限公司 | Slow protocol message processing method and related apparatus |
| CN108965204A (en) * | 2017-05-18 | 2018-12-07 | 中兴通讯股份有限公司 | A kind of method and device of automatic realization IOAM encapsulation |
Citations (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20060036735A1 (en) * | 2004-07-29 | 2006-02-16 | International Business Machines Corporation | Method for avoiding unnecessary provisioning/deprovisioning of resources in a utility services environment |
| CN101005445A (en) * | 2006-01-18 | 2007-07-25 | 华为技术有限公司 | Method for mapping service flow to service transmission path and optical network terminal |
| CN101119245A (en) * | 2007-08-31 | 2008-02-06 | 杭州华三通信技术有限公司 | Method and device for performing link monitoring using OAM protocol |
-
2009
- 2009-12-01 CN CN2009102386956A patent/CN102082678A/en active Pending
Patent Citations (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20060036735A1 (en) * | 2004-07-29 | 2006-02-16 | International Business Machines Corporation | Method for avoiding unnecessary provisioning/deprovisioning of resources in a utility services environment |
| CN101005445A (en) * | 2006-01-18 | 2007-07-25 | 华为技术有限公司 | Method for mapping service flow to service transmission path and optical network terminal |
| CN101119245A (en) * | 2007-08-31 | 2008-02-06 | 杭州华三通信技术有限公司 | Method and device for performing link monitoring using OAM protocol |
Cited By (12)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN102333009A (en) * | 2011-10-09 | 2012-01-25 | 中兴通讯股份有限公司 | Link detection method and device, as well as OAM (operation administration and maintenance) entity |
| CN102420828A (en) * | 2011-12-15 | 2012-04-18 | 华为技术有限公司 | Method, device and system for setting protocol management status |
| CN102917389A (en) * | 2012-10-22 | 2013-02-06 | 大唐移动通信设备有限公司 | Method and device for transmission self-detection of base station in LTE (Long Term Evolution) system |
| CN106302146A (en) * | 2016-10-17 | 2017-01-04 | 杭州迪普科技有限公司 | The convergence method of link aggregation and device |
| WO2018120799A1 (en) * | 2016-12-29 | 2018-07-05 | 华为技术有限公司 | Slow protocol message processing method and related apparatus |
| CN108259442A (en) * | 2016-12-29 | 2018-07-06 | 华为技术有限公司 | A kind of slow protocol message processing method and relevant apparatus |
| US10728260B2 (en) | 2016-12-29 | 2020-07-28 | Huawei Technologies Co., Ltd. | Slow protocol packet processing method and related apparatus |
| CN108259442B (en) * | 2016-12-29 | 2021-02-12 | 华为技术有限公司 | Slow protocol message processing method and related device |
| CN112887312A (en) * | 2016-12-29 | 2021-06-01 | 华为技术有限公司 | Slow protocol message processing method and related device |
| US11038898B2 (en) | 2016-12-29 | 2021-06-15 | Huawei Technologies Co., Ltd. | Slow protocol packet processing method and related apparatus |
| CN112887312B (en) * | 2016-12-29 | 2022-07-22 | 华为技术有限公司 | Slow protocol message processing method and related device |
| CN108965204A (en) * | 2017-05-18 | 2018-12-07 | 中兴通讯股份有限公司 | A kind of method and device of automatic realization IOAM encapsulation |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN102007729B (en) | Connectivity fault management traffic indication extension | |
| CN102082678A (en) | Processing method and equipment of port discarding OAM (Operation, Administration and Maintenance) protocol | |
| CN105871743B (en) | The machinery of consultation of aggregation port state and device | |
| US7660236B2 (en) | System and method of multi-nodal APS control protocol signaling | |
| CN104301146A (en) | Link switching method and device in software defined network | |
| CN101094121B (en) | Method, system and device for detecting Ethernet links among not direct connected devices | |
| US20140071810A1 (en) | Communication system and processing method therefor | |
| CN109088818A (en) | A kind of method and device of equipment linkage switching | |
| CN102891769A (en) | Link fault informing method and apparatus | |
| US11038898B2 (en) | Slow protocol packet processing method and related apparatus | |
| CN103067220A (en) | Two-way link transmission detecting method and two-way link transmission detecting device under the circumstance of parameter updating | |
| CN102035695A (en) | Bidirectional forwarding detection method and device | |
| CN104580346B (en) | Data transmission method and device | |
| CN103001822B (en) | The processing method of Network Abnormal and device | |
| CN105490970B (en) | A kind of method, apparatus and system of link Fast Convergent | |
| CN106664247B (en) | Communication device, communication system, and communication method | |
| CN106792797A (en) | Offline processing method and radio reception device on a kind of user terminal | |
| CN106302146A (en) | The convergence method of link aggregation and device | |
| CN105703967A (en) | Method and apparatus for detecting label switching path connectivity | |
| JP2009278451A (en) | Network equipment setting method | |
| CN104426700A (en) | Network element and ring network protection method | |
| KR101581510B1 (en) | Methods for changing an authority of control for a controller in multiple controller environment | |
| JP5647197B2 (en) | Network connection device, network control method, network control program, and network system | |
| CN101146042B (en) | A management method, device and system of BGP route | |
| JP2630283B2 (en) | Orderwire communication control method for ring network 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 | ||
| C12 | Rejection of a patent application after its publication | ||
| RJ01 | Rejection of invention patent application after publication |
Application publication date: 20110601 |