CN104468158B

CN104468158B - The method and apparatus of state advertisement between a kind of node

Info

Publication number: CN104468158B
Application number: CN201310422696.2A
Authority: CN
Inventors: 黄兆胜; 刘斌; 蒋维廉
Original assignee: Huawei Technologies Co Ltd
Current assignee: Changzhou Hengtang Technology Industry Co ltd
Priority date: 2013-09-16
Filing date: 2013-09-16
Publication date: 2018-07-13
Anticipated expiration: 2033-09-16
Also published as: WO2015035852A1; CN104468158A

Abstract

The method and apparatus that the embodiment of the present invention discloses state advertisement between a kind of node, it is related to field of communication technology, solves the state for capableing of the same domain others node present node of proactive notification between node, and other nodes is made to carry out corresponding processing to it, the function tenability and corresponding resource for capableing of proactive notification present node between node simultaneously can use situation, and then improve system response efficiency.This method includes：When the status information of first node changes, the changed status information of the first node is encapsulated to the first notification packet, and first notification packet is sent to other nodes；The status information of the first node includes：One or more in the controlled state of the first node, the functional type of support and the corresponding resource information for supporting the functional type, the embodiment of the present invention is applied to Ethernet internal maintenance destination node.

Description

Method and equipment for state notification between nodes

Technical Field

The present invention relates to the field of communications technologies, and in particular, to a method and a device for notifying a status between nodes.

Background

With respect to Ethernet-based Operations, Administration and Maintenance ETH-OAM (Ethernet-Operations, Administration and Maintenance), the ETH-OAM mainly includes two functional sets of fault management and performance management, and the ETH-OAM complies with the standard: institute of Electrical and electronics Engineers IEEE (Institute of Electrical and electronics Engineers) standard 802.1ag and International Telecommunications Union Standard (International Telecommunications Union) ITU-TY.1731; the specific functions of ETH-OAM include: connectivity Check CC (connectivity Check), Loopback Check LB (Loopback), Link Trace LT (Link Trace), Loss Measurement LM (Loss Measurement), Delay Measurement DM (Delay Measurement), and synthetic Loss Measurement SLM (synthetic Loss Measurement). The concept involved in ETH-OAM mainly includes: a Maintenance Domain MD (Maintenance Domain), a Maintenance alliance MA (Maintenance Association), a Maintenance alliance end Point MEP (Maintenance Association end Point), and a Maintenance Intermediate Point MIP (Maintenance Domain Intermediate Point). Here, ETH-OAM is deployed based on MD, MA, MEP, and MIP, and MEP is the detection subject of ETH-OAM.

In the prior art, a connectivity Check Message CCM (connectivity Check Message) is a multicast frame generated by an MEP and is broadcast to all other MEPs in the same MA; wherein CCMs are periodically exchanged between MEPs, allowing MEPs to discover connectivity between other MEPs in a maintenance domain MD. In order to detect a failure, the local MEP maintains a CCM list from the remote MEP, the CCM list is created based on the configured remote MEP, and the local MEP sends an alarm when the local MEP does not receive the CCMs of the configured remote MEP within a preset period.

The inventor finds that at least the following problems exist in the prior art: when the CCM sent by a remote MEP is not received within the time that the local MEP exceeds 3.5 times of the packet sending interval, it is considered that the link between the local MEP and the remote MEP fails, and as a result, when the link between the local MEP and the remote MEP fails, the local MEP cannot acquire the state information of the remote MEP in time, so that the system response time is prolonged.

Disclosure of Invention

The embodiment of the invention provides a method and equipment for state notification between nodes, which are used for improving the response efficiency of a system.

In a first aspect, a method for state advertisement between nodes is provided, including:

when the state information of a first node changes, packaging the changed state information of the first node into a first notification message, and sending the first notification message to other nodes; the state information of the first node includes: one or more of a management status of the first node, a supported function category, and resource information corresponding to the supported function category.

In a first possible implementation manner of the first aspect, the first node is a maintenance alliance end MEP.

With reference to the first possible implementation manner of the first aspect, in a second possible implementation manner of the first aspect, when the state information of the first MEP changes, the encapsulating the changed state information of the first MEP in a first CCM, and sending the first CCM to the other MEPs includes:

when a management state in the state information of the first MEP is changed, packaging the changed management state into the first CCM;

sending the packaged first CCM to the other MEPs.

With reference to the second possible implementation manner of the first aspect, in a third possible implementation manner of the first aspect, before the MEP management state in the state information of the first MEP is changed, the method includes:

when the first MEP is in a normal state, the first MEP acquires a management state value in the state information of the first MEP, and packages the acquired state information when the first MEP is in the normal state to a second CCM;

sending the second CCM to the other MEPs.

With reference to the second possible implementation manner of the first aspect, in a fourth possible implementation manner of the first aspect, when the first MEP is in a normal state, a value of a management state in the state information of the first MEP is set to 0, and the changing of the management state of the first MEP includes:

when the first MEP is deleted by a management apparatus, a value of a management status in status information of the first MEP is changed from 0 to 1;

or

When the first MEP is closed by a management device, the value of the management status in the status information of the first MEP is changed from 0 to 1;

or,

when the master-slave switching of the management device where the first MEP is located occurs, the value of the management state in the state information of the first MEP is changed from 0 to 1.

With reference to the second or fourth possible implementation manner of the first aspect, in a fifth possible implementation manner of the first aspect, the sending the packaged first CCM to the other MEPs includes:

sending the first CCM to the other MEPs by triggering consecutive transmissions.

With reference to any one of the first to fourth possible implementation manners of the first aspect, in a sixth possible implementation manner of the first aspect, the management state in the state information of the first MEP includes: closing, deleting and switching the main equipment and the standby equipment of the first MEP.

With reference to the first possible implementation manner of the first aspect, in a seventh implementation manner of the first aspect, when the state information of the first MEP changes, the encapsulating the changed state information of the first MEP into a first CCM, and sending the first CCM to the other MEPs includes:

resetting the function type supported in the state information of the first MEP and the value corresponding to the corresponding resource information supporting the function when the function of the first MEP and/or the resource corresponding to the function are/is changed;

packaging the reset state information into a first CCM;

sending the first CCM to the other MEPs.

With reference to any one of the first to seventh possible implementation manners of the first aspect, in an eighth implementation manner of the first aspect, the other MEPs and the first MEP are located in the same maintenance alliance MA.

With reference to any one of the first to eighth possible implementation manners of the first aspect, in a ninth implementation manner of the first aspect, the first CCM includes a Capability TLV, and the Capability TLV is configured to carry status information of the first MEP.

With reference to the ninth possible implementation manner of the first aspect, in a tenth implementation manner of the first aspect, the Capability TLV further includes a subltlv, and the subltlv is configured to carry one or more of a management state, a supported function category, and resource information corresponding to the supported function category in the state information of the first MEP.

In a second aspect, a first maintenance alliance end point MEP includes an obtaining unit and a sending unit, wherein:

the acquiring unit is configured to acquire status information of the first MEP, where the status information of the first MEP includes: one or more of a management status of the first MEP, a supported function category, and resource information corresponding to the supported function category;

the sending unit is configured to encapsulate the state information of the first MEP, which changes when the state information of the first MEP changes, into a first connectivity detection message CCM, and send the first CCM to other MEPs.

In a first possible implementation manner of the second aspect, the sending unit includes:

a packaging subunit, configured to package, when a management state in the state information of the first MEP is changed, the changed management state to the first CCM;

a sending subunit, configured to send the first CCM after encapsulation to the other MEPs.

With reference to the first possible implementation manner of the second aspect, in a second possible implementation manner of the second aspect, the encapsulating subunit is further configured to, before the management state in the state information of the first MEP is changed, when the first MEP is in a normal state, the first MEP obtains a management state value in the state information of the first MEP, and encapsulates the state information when the first MEP is in the normal state to the second CCM;

the sending subunit is further configured to send the second CCM to the other MEPs according to the sending of the second CCM.

With reference to the first possible implementation manner of the second aspect, in a third possible implementation manner of the second aspect, when the first MEP is in a normal state, a value of a management state in the current state information of the first MEP is set to 0, and the changing of the management state of the first MEP includes:

or

or,

With reference to the first or third possible implementation manner of the first aspect, in a fourth possible implementation manner of the second aspect, the sending subunit is specifically configured to:

sending the first CCM to the other MEPs.

With reference to the second aspect and any one of the first to fifth possible implementation manners of the second aspect, in a fifth possible implementation manner of the second aspect, the management state in the state information of the first MEP includes: closing, deleting and switching the main equipment and the standby equipment of the first MEP.

With reference to the second aspect, in a sixth possible implementation manner of the second aspect, the sending unit further includes:

a setting subunit, configured to, when a function of the first MEP and/or a resource corresponding to the function is changed, reset a value corresponding to a function type supported in the state information of the first MEP and corresponding resource information supporting the function;

the packaging subunit is further configured to package the reset state information to the first CCM;

the sending subunit is further configured to send the first CCM to the other MEPs by triggering continuous sending.

With reference to the second aspect and any one of the first to sixth possible implementation manners of the second aspect, in a seventh possible implementation manner of the second aspect, the other MEPs are located in the same maintenance federation MA as the first MEP.

With reference to the second aspect and any one of the first to seventh possible implementation manners of the second aspect, in an eighth possible implementation manner of the second aspect, the first CCM includes a Capability TLV, and the Capability TLV is configured to carry status information of the first MEP.

With reference to the eighth possible implementation manner of the second aspect, in a ninth possible implementation manner of the second aspect, the Capability TLV further includes a subltlv, and the subltlv is configured to carry one or more of a management state, a supported function category, and resource information corresponding to the supported function category in the state information of the first MEP.

According to the method and the device for state notification between the nodes, when the state information of the first node changes, the corresponding state value in the state information is changed, the changed state information of the first node is packaged and then sent to other MEPs in the maintenance alliance where the first node is located, and other nodes in the maintenance alliance where the first node is located can perform corresponding operation according to the received state information of the first node, so that the problem that the nodes can actively notify other nodes in the same domain of the state information of the nodes, the other nodes can correspondingly process the state information of the first node stored by the other nodes is solved, the current function supporting capability and the corresponding resource availability of the nodes can be actively notified to the other nodes, and the response efficiency of a system is improved. In addition, if the scheme is applied to Ethernet OAM, and a first node is a first MEP, when the state of the first MEP changes, the first MEP packages the changed state information of the first MEP into a CCM and sends the information to other MEPs in the same maintenance alliance, so that the other MEPs can timely know the state change of the first MEP and make corresponding processing. When the first MEP fails and the link from the first MEP to other MEPs in the maintenance federation where the first MEP is located has no failure, the other MEPs in the maintenance federation where the first MEP is located can timely distinguish and know the two failures and perform corresponding processing.

Drawings

In order to more clearly illustrate the embodiments of the present invention or the technical solutions in the prior art, the drawings used in the description of the embodiments or the prior art will be briefly described below, it is obvious that the drawings in the following description are only some embodiments of the present invention, and for those skilled in the art, other drawings can be obtained according to the drawings without creative efforts.

FIG. 1(a) is a schematic diagram of a partial component structure of a Capability TLV according to an embodiment of the present invention;

FIG. 1(b) is a partial structural diagram of a sub-TLV according to an embodiment of the present invention;

FIG. 2 is a bit schematic diagram of a Capability TLV according to an embodiment of the present invention;

fig. 3 is a flowchart illustrating another method for inter-MEP status notification according to an embodiment of the present invention;

fig. 4 is a flowchart illustrating a method for inter-MEP status notification according to another embodiment of the present invention;

FIG. 5 is a schematic structural diagram of a first MEP in accordance with embodiments of the present invention;

FIG. 6 is a schematic structural diagram of another first MEP of an embodiment of the present invention;

FIG. 7 is a schematic structural diagram of yet another first MEP of an embodiment of the present invention;

fig. 8 is a schematic structural diagram of a further first MEP according to an embodiment of the present invention.

Detailed Description

The technical solutions in the embodiments of the present invention will be described clearly below with reference to the drawings in the embodiments of the present invention, and it is obvious that the described embodiments are only a part of the embodiments of the present invention, and not all embodiments. All other embodiments, which can be derived by a person skilled in the art from the embodiments given herein without making any creative effort, shall fall within the protection scope of the present invention.

The "nodes" mentioned in the embodiments of the present invention are all node network devices or functional entities deployed on network devices.

The invention is suitable for the operation, management and Maintenance of the Ethernet (ETH-OAM). The concept related to ETH-OAM mainly includes: a Maintenance Domain MD (Maintenance Domain), a Maintenance alliance MA (Maintenance Association), a Maintenance alliance End Point MEP (Maintenance Association End Point), and a Maintenance intermediate Point MIP (Maintenance Domain intermediate Point). The MD indicates the network covered by the ETH-OAM. The boundaries of an MD are defined by a series of MEPs configured on a port and identified by a "maintenance domain name". The concept of a level (hierarchy) is introduced in the maintenance domain. The maintenance domain is divided into eight stages in total and is identified by integers of 0-7. Multiple maintenance federation MAs may be configured as needed within a maintenance domain. Each maintenance association is a collection of some maintenance endpoints within a maintenance domain. Where the MA is identified by "maintain domain name + maintain federation name". The MEP determines the extent and boundaries of the MD, which are edge nodes of the MA. Wherein the MD and MA determine the traffic and level of the message sent by the MEP. Here, the MEP is a session body of specific function deployment of ETH-OAM, and is used to receive and transmit a corresponding OAM message, and the MEP is a detection body of ETH-OAM. The method for state notification between nodes in the embodiment of the invention comprises the following steps:

the first node obtains the current state information of the first node.

Wherein the state information of the first node includes: one or more of a management state of the first node, a function category supported by the first node, and resource information corresponding to the supported function category.

Assuming that a first node is a maintenance alliance End Point (MEP) (hereinafter referred to as "first MEP") in a maintenance domain MD1, state information of the first node is carried in a Capability TLV (Type-Length-Value) in a connectivity detection message CCM multicast-sent by the first node and sent to other MEPs. Here, the "other MEP" may be another MEP in the maintenance domain MD1 where the first MEP is located, or may be another MEP in the maintenance federation MA where the first MEP is located. The Capability TLV is used for carrying the management state of the MEP, the function support state of the MEP and the resource state corresponding to the MEP support function. The structure of the Capability TLV is shown in FIG. 1(a), wherein the TYPE TLV TYPE of the Capability TLV is 1 byte; the length TLV LENGTH of the Capability TLV is 2 bytes; the VALUE TLV VALUE of Capability TLV contains: MEP status (MEP _ STATE _ VALUE: 2 bytes), function SUPPORT (FUN _ SUPPORT _ VALUE: 2 bytes), and function RESOURCE (FUN _ RESOURCE _ VALUE: 2 bytes).

The MEP _ STATE _ VALUE field indicates a management STATE VALUE of the MEP, the FUN _ SUPPORT _ VALUE field indicates a MEP SUPPORT function category VALUE, and the FUN-RESOURCE-VALUE field indicates RESOURCE information of the SUPPORT function category of the MEP.

Wherein, bits of the Capability TLV are shown in FIG. 2. The management state of the MEP is included in the first row of fig. 2. Wherein the management state of the MEP includes: closing (Admin-Down), deleting (Admin-Del) and main-standby switching (Admin-Switch) of the equipment where the MEP is located. The management state of the MEP may further include: waiting for a switching time (Wait-switch-time). When any one of the management states of the MEPs changes, the first MEP sends a connectivity Check Message CCM (connectivity Check Message) to the other MEPs, so that the other MEPs perform corresponding processing according to the management state value of the first MEP carried in the CCM.

The second row of fig. 2 includes the support function categories of MEPs, wherein the support function categories of MEPs include: the method comprises the steps of synthesizing packet Loss Measurement-Support SLM-S (synchronous Loss Measurement-Support), Delay Measurement-Support DM-S (Delay Measurement-Support), packet Loss Measurement-Support LM-S (Loss Measurement-Support), Link tracking-Support LT-S (Link Trace-Support), Multicast Loopback-Support MLB-S (Multicast Loopback-Support) and Loopback-Support LB-S (Loopback-Support).

The third row of fig. 2 includes resource information of the supported functional category of the MEP. Wherein, the resource information of the MEP supporting the function category comprises: synthesizing a lost packet Measurement-Resource SLM-R (Synthetic Loss Measurement-Resource), a Delay Measurement-Resource DM-R (Delay Measurement-Resource), a lost packet Measurement-Resource LM-R (Loss Measurement-Resource), a Link tracking-Resource LT-R (Link Trace-Resource), a Multicast Loopback-Resource MLB-R (Multicast Loopback-Resource) and a Loopback-Resource LB-R (Loop Back-Resource).

When the support function type of the first MEP changes or the resource information corresponding to the support function type changes, the first MEP encapsulates the changed state information into a CCM, and then sends the CCM multicast to other MEPs by triggering continuous sending. In the embodiment of the present invention, the number of times of continuous transmission is 1 to 3, and the actual situation is not particularly limited.

Optionally, any one or more of the management status of the Capability TLV in the CCM, the supported function type, and the resource information of the supported function type may also be identified in a Sub-TLV (Sub-TLV), so that when other functions of the Capability TLV need to be extended, the Sub-TLV may also be added.

In this case, the structure of the subltlv is shown in fig. 1(b), and the subltlv includes: TYPE of sub tlv-TYPE (1 byte), LENGTH of sub tlv-LENGTH (2 bytes), and VALUE of sub tlv-VALUE. The size of the sub TLV-VALUE is determined by the sub TLV-LENGTH, wherein the sub TLV-VALUE can be MEP STATE MEP _ STATE _ TLV, function SUPPORT FUN _ SUPPORT _ TLV and function RESOURCE FUN _ RESOURCE _ TLV.

When the current state information of the first node changes, the changed state information of the first node is packaged into a first notification message, and the first notification message is sent to other nodes.

The method includes that a MD1 where a first node (a first MEP) is located or other MEPs in a maintenance alliance acquire state information of the first node through a first CCM, and the first CCM carries current state information of the first node.

When a first node (first MEP) is in a normal state, the first MEP obtains its current management state, for example: management status value of the first MEP. Specifically, the current management state of the first MEP includes: whether the equipment where the first MEP is currently located is subjected to active-standby switching or whether the first MEP is currently in a deleted or closed state. The first MEP packages the current management state of the first MEP into the Capability TLV of the second CCM, then sends the second CCM multicast to the MD1 where the first MEP is located or other MEPs in the maintenance alliance where the first MEP is located according to the sending period, and if the other MEPs in the MD1 or other MEPs in the same maintenance alliance as the first MEP support the second CCM carrying the Capability TLV, the state information corresponding to the current management state of the first MEP carried by the Capability TLV and stored by the first MEP is saved and/or updated.

When the current management state of the first MEP changes, the first MEP packages the changed state information into the first CCM, and continuously sends the first CCM to other MEPs in the MD1 where the first MEP is located or other MEPs in the maintenance alliance where the first MEP is located in real time by triggering and sending the first CCM when a sending period does not wait for the arrival, so that the other MEPs in the MD1 where the first MEP is located or the other MEPs in the maintenance alliance where the first MEP is located receive the first CCM, and the received state information of the first MEP in the first CCM is found to change compared with the state information of the first MEP stored by a receiver, and corresponding processing is performed.

According to the method for state notification among nodes in the embodiment of the invention, when the current state information of a first node (first MEP) changes, the state information of the first MEP after the state change is packaged in CCM and is multicast-sent to other nodes (MEPs) in an MD where the first MEP is located or other MEPs in a maintenance alliance where the first MEP is located, so that the other MEPs can perform corresponding operations according to the changed state information of the first node, the current states of the other MEPs in the same maintenance domain can be actively notified among the nodes, the stored state information of the first MEP can be correspondingly processed by the other MEPs in the same maintenance domain or the other MEPs in the same maintenance alliance, and the current function support capability and the corresponding resource availability of the nodes can be actively notified among the nodes, so that the system response efficiency is improved. When the first MEP fails and the link from the first MEP to other MEPs in the maintenance federation where the first MEP is located has no failure, the other MEPs in the maintenance federation where the first MEP is located can timely distinguish and know the two failures and perform corresponding processing. For example, since only the first MEP itself has a special operation, and the link between the device where the first MEP is located and other devices does not fail, the data traffic associated with the first MEP does not need to be switched.

Specifically, the following description will be given with reference to specific examples.

As shown in fig. 3, another method for inter-MEP status notification is provided in an embodiment of the present invention, where the method includes:

when the first MEP is in a normal state, the first MEP acquires a management state value in the current state information of the first MEP, and packages the management state value in the current state information of the first MEP to the first CCM.

When the first MEP is in a normal state, the value of the management state in the current state information of the first MEP is set to 0.

Here, the management state in the state information of the first MEP includes: closing, deleting and switching the main equipment and the standby equipment where the first MEP is located.

A first MEP of the CCM is a maintenance alliance End Point (MEP) (hereinafter referred to as "first MEP") in a maintenance domain MD1, and the state information of the first MEP is carried in a Capability TLV (Type-Length-Value) in a connectivity detection message CCM multicast-sent by the first MEP and sent to other MEPs in the MD1 or other MEPs in a maintenance alliance MA1 where the first MEP is located. Wherein the management status in the Capability TLV in the first CCM sent by the first MEP includes: closing (Admin-Down), deleting (Admin-Del) and switching (Admin-Switch) the main equipment of the first MEP.

When the first MEP is in a normal state, values corresponding to Admin-Down, Admin-Del, and Admin-Switch are all set to 0.

In the embodiment of the present invention, the MEP management state value is set only by setting the values corresponding to Admin-Down, Admin-Del, and Admin-Switch to 0, which is not specifically limited.

Of course, the first CCM may not carry the status information of the first MEP.

202. And the first MEP multicast-sends the first CCM to other MEPs in the MD or MA where the first MEP is located according to a preset sending period.

203. And when the management state in the current state information of the first MEP is changed, packaging the changed management state into the second CCM.

Wherein the change of the management state of the first MEP comprises:

when the first MEP is deleted by the management apparatus, the value of the management status in the status information of the first MEP is changed from 0 to 1;

or

When a first MEP is closed by a management device, the value of the management status in the status information of the first MEP is changed from 0 to 1;

or,

When the master-slave switching of the management device where the first MEP is located occurs, a value corresponding to Admin-Switch of the Capability TLV is set to 1 from 0, and the Capability TLV is packaged into a second CCM (Continuity check message) and multicast-transmitted to MD1 or other MEPs in MA1 where the first MEP is located.

204. And the first MEP sends the encapsulated second CCM multicast to the MD where the first MEP is located or other MEPs in the maintenance alliance MA by triggering continuous sending, so that the MD where the first MEP is located or other MEPs in the MA change the state information corresponding to the first MEP stored by the first MEP according to the received changed state information of the first MEP carried by the second CCM.

Here, the sending of the encapsulated second CCM multicast to other MEPs in the MD or MA where the first MEP is located by triggering continuous sending includes:

and triggering continuous sending to send the second CCM multicast to other MEPs in the MD or MA where the first MEP is located, so that the other MEPs in the MD or MA where the first MEP is located delete the state information corresponding to the first MEP stored by the other MEPs according to the second CCM, and the state position of a Connectivity Check (CC) corresponding to the second CCM in the other MEPs is closed.

Here, when the first MEP is deleted, corresponding Admin-Del in the Capability TLV is set to 1, and the Capability TLV encapsulating the Admin-Del value to 1 is triggered to be continuously sent to the second CCM, and multicast-sent to other MEPs (such as the second MEP) in the MD or MA where the first MEP is located, and the second MEP does not wait for 3.5 times of sending cycle time and then sends the second CCM by receiving the first MEP due to its state change, but quickly receives the second CCM sent when the first MEP is deleted and locally deletes the state information of the first MEP stored in the second MEP.

Specifically, when other MEPs (for example, a second MEP) in the MD or MA where the first MEP is located receive a second CCM sent by the first MEP, if the Admin-Del value in the second CCM is found by comparison to be different from the Admin-Del value of the first MEP pre-stored by the second MEP, the second MEP performs Admin-Del processing, and the CC state position corresponding to the first MEP stored by the second MEP is a close Down.

Optionally, the second CCM multicast is sent to other MEPs (for example, second MEPs) in the MD or MA where the first MEP is located by triggering continuous sending, so that the MD or other MEPs in the MA where the first MEP is located perform closing processing according to the second CCM, and the CC state location of the first MEP in the MD or other MEPs in the MA where the first MEP is located is closed.

Here, when the first MEP is closed, the corresponding Admin-Down in the Capability TLV in the second CCM sent by the first MEP will be set to 1, and immediately trigger continuous sending to send the Capability TLV to other MEPs (such as the second MEP) in the MD or MA where the first MEP is located through the second CCM multicast, and the second MEP does not need to wait for 3.5 times of sending cycle time and then send the second CCM due to the change of its own state by receiving the first MEP.

Specifically, when other MEPs (such as a second MEP) in the MD or MA where the first MEP is located receive a second CCM sent by the first MEP, according to the difference between the value of Admin-Down in the second CCM and the value of Admin-Down of the first MEP pre-stored by the second MEP, Admin-Down processing is performed, and the corresponding CC (Continuity Check) state position is set to the value of Admin-Down carried in the second CCM.

Or,

and multicast sending the encapsulated first CCM to other nodes (such as a second MEP) in the MD or MA where the first MEP is located by triggering continuous sending, so that the second MEP sets the waiting aging time for setting the CC state value of the first MEP stored by the second MEP to be closed according to the state information in the first CCM as the waiting switching time carried in the first CCM, and if the third CCM sent by the first node is not received after the waiting switching time carried in the first CCM is over, the waiting aging time is reset.

When the MD or other MEPs (such as the second MEP) in the MA where the first MEP is located receive the first CCM, comparing the Admin-Switch state information in the first CCM with the Admin-Switch state information of the first MEP pre-stored by the second MEP, and finding that the Admin-Switch state information is different from the Admin-Switch state information of the first MEP, the second MEP performs processing of changing the Admin-Switch state into 1 according to the Admin-Switch state information of the first MEP carried by the second CCM, that is, setting the waiting aging time of the corresponding CC state position bit Down to be waiting switching time (Wait-Switch-time) in Capability TLV. When the Wait-switch-time is over, if the second MEP does not receive the third CCM sent by the first MEP, the second MEP sets the CC state bit to Down and triggers the generation of a Remote fault identification RDI (Remote fault identification).

And when the second MEP receives the third CCM message with the Admin-Switch state set to be 0 in the Wait-Switch-time, the second MEP resets the sending period with the waiting aging time of 3.5 times.

If the second CCM with the Admin-Switch state of 1 is lost, the other MEPs (for example, the second MEP) in the MD or the MA where the first MEP is located may extend the Wait-Switch-time waiting for storage after 3.5 times of the CCM transmission period according to the policy, and then set to Down and trigger to generate RDI, where the policy mainly includes: 1. aging the waiting time of the application message according to the CCM sending period which is 3.5 times of the waiting time; 2. and (4) ignoring the waiting time of the message, and aging according to 3.5 times of the CCM sending period.

In the embodiment of the present invention, the management state value of the MEP is only 0 or 1, and the setting of the aging waiting time is also only 3.5 times of the CCM transmission cycle, which is not specifically limited.

In the method for notifying the state among the MEPs provided in the embodiment of the present invention, when the management state in the state information of the first MEP is changed, by changing the corresponding management state value in the state information and triggering the continuous sending of the state information after the state change is multicast-sent to other MEPs (for example, the second MEP) in the MD or MA where the first MEP is located, so that the second MEP performs corresponding operations according to the state information of the first MEP, the MEP can actively notify the second MEP in the same maintenance domain or maintenance alliance of the current state of the MEP itself, and the second MEP can correspondingly process the state information corresponding to the first MEP stored in the second MEP itself, and the MEPs can actively notify the current function support capability and the resource availability of the second MEP, thereby improving the system response efficiency. When the first MEP fails and the link from the first MEP to other MEPs in the maintenance federation where the first MEP is located has no failure, the other MEPs in the maintenance federation where the first MEP is located can timely distinguish and know the two failures and perform corresponding processing. For example, since only the first MEP itself has a special operation, and the link between the device where the first MEP is located and other devices does not fail, the data traffic associated with the first MEP does not need to be switched.

Referring to fig. 4, a method for inter-MEP status notification according to an embodiment of the present invention includes:

301. and resetting the types of the functions supported in the state information and the values corresponding to the resource information of the corresponding supported functions when the functions of the first MEP and/or the resources of the corresponding functions are changed.

Assuming that the first MEP is a maintenance end node in the maintenance domain MD1 or the maintenance alliance MA1, the status information of the first MEP is carried in a Capability TLV (Type-Length-Value) of a connectivity check message CCM multicast-sent by the first MEP and sent to other MEPs (such as the second MEP) in the MD1 or the MA 1. When the global enabling of the operation, Administration and Maintenance (ETH-OAM) function corresponding to the local Ethernet changes or the session resource cannot meet the user requirement, the ETH-OAM function corresponding to the first MEP and the resource bit value change and are reset, and continuous sending of CCM is triggered.

Optionally, before a global enabling change of a local ETH-OAM function or a situation that a session resource cannot be demanded by a user occurs, the first MEP packages the reset ETH-OAM function and a resource bit value into a Capability TLV of the CCM, and multicasts the information to other MEPs (such as the second MEP) in MD1 or MA1 according to a transmission cycle.

302. The first MEP encapsulates the reset state information of the first MEP to the first CCM.

303. The first MEP multicast-sends the first CCM to other MEPs, so that the other MEPs obtain the state information of the first MEP according to the first CCM, feed back the state information of the first MEP to the management equipment where the other MEP is located according to the state information of the first MEP carried by the first CCM, and store the current state information of the first MEP.

The first MEP continuously sends the first CCM to MD1 where the first MEP is located or other MEPs (such as second MEPs) in MA1 through triggering, so that the second MEP compares the received state information of the first MEP carried by the first CCM with the CCMs sent when the first MEP is in a normal state, determines that the global enable of the ETH-OAM function of the first MEP changes or the session resource is insufficient, that is, the ETH-OAM function and the resource bit value change, and reports the function failure corresponding to the first MEP to the management device where the second MEP is located, which may be due to the fact that the ETH-OAM function of the first MEP is closed or the resource is insufficient, and stores the first CCM sent when the ETH-OAM function of the first MEP and the resource bit value change. The first CCM is for display viewing.

In the inter-MEP status notification method of the embodiment of the present invention, when the function in the status information of the first MEP and/or the resource of the corresponding function are changed, by changing the corresponding function and/or the resource value of the corresponding function in the status information of the first MEP, and multicast-sending the state information after the encapsulation changes the state to a second MEP in the MD or MA where the first MEP is located by triggering continuous sending so that the second MEP makes corresponding operation according to the state information of the first MEP, so that a first MEP can actively inform a second MEP within the same maintenance domain or maintenance federation of its current state, and the second MEP carries out corresponding processing on the state information of the first MEP stored by the second MEP, and MEPs can actively inform the current function support capability and the corresponding resource availability condition of the MEPs, thereby improving the response efficiency of the system. When the first MEP fails and the link from the first MEP to other MEPs in the maintenance federation where the first MEP is located has no failure, the other MEPs in the maintenance federation where the first MEP is located can timely distinguish and know the two failures and perform corresponding processing. For example, since only the first MEP itself has a special operation, and the link between the device where the first MEP is located and other devices does not fail, the data traffic associated with the first MEP does not need to be switched.

Here, the embodiment corresponding to any one of fig. 1 to fig. 4 is described by taking as an example only a method for implementing the inter-MEP status notification by the first node, and other MEPs in the embodiment also have the function of the first MEP, that is, the method for implementing the inter-MEP status notification by the first MEP is also applicable to other MEPs, and the first MEP can be interchanged with other MEPs in the functional position, which is not particularly limited in the present invention.

An embodiment of the present invention provides a first MEP4, where the first MEP4 may specifically be any maintenance termination point in an ethernet network, and a specific form of the first MEP is not specifically limited in the embodiment of the present invention, which is subject to a method that can implement the state notification between any MEP in the embodiment of the present invention. Referring to fig. 5, the first MEP4 includes an acquisition unit 41 and a transmission unit 42. Wherein:

an obtaining unit 41, configured to obtain current state information of a first MEP, where the current state information of the first MEP includes: one or more of a management status of the first MEP, a supported function category, and resource information corresponding to the supported function category;

a sending unit 42, configured to trigger continuous sending of the state information of the first MEP, which is encapsulated to the first connectivity detection message CCM, when the current state information of the first MEP changes, and send the first CCM multicast to the maintenance domain MD where the first MEP is located or another node in the maintenance alliance MA, where the other MEPs obtain the current state information of the first MEP located in the same maintenance domain or the maintenance alliance MA through the first CCM. The first CCM carries current state information of the first MEP.

Here, if the MD or other MEP in the MA where the first MEP is located receives the first CCM, the MD or other MEP in the MA where the first MEP is located performs corresponding processing according to the change of the state information of the first MEP carried in the first CCM.

According to the first MEP provided by the embodiment of the invention, when the state information of the first MEP is changed, the changed state information is packaged, and the packaged state information is triggered to be continuously sent to other MEPs in the MD or MA where the first MEP is located, so that the other MEPs can perform corresponding operation according to the state information of the first MEP, the current state information of the MEP can be actively notified to other MEPs in the same maintenance domain or MA among the MEPs, the other MEPs can correspondingly process the state information corresponding to the first MEP stored by the MEP, and the current function support capability and the corresponding resource availability of the MEP can be actively notified among the MEPs, so that the system response efficiency is improved. When the first MEP fails and the link from the first MEP to other MEPs in the maintenance federation where the first MEP is located has no failure, the other MEPs in the maintenance federation where the first MEP is located can timely distinguish and know the two failures and perform corresponding processing. For example, since only the first MEP itself has a special operation, and the link between the device where the first MEP is located and other devices does not fail, the data traffic associated with the first MEP does not need to be switched.

Further, referring to fig. 6, the sending unit 42 may include: an encapsulation subunit 421 and a sending subunit 422, wherein:

a packaging subunit 421, configured to package, when the management state in the current state information of the first MEP is changed, the changed management state into the first CCM;

a sending subunit 422, configured to send the encapsulated first CCM multicast to other MEPs in the MD or MA where the first MEP is located by triggering continuous sending.

Optionally, the encapsulating subunit 421 is further configured to, before the management state in the current state information of the first MEP is changed, that is, when the first MEP is in a normal state, the first MEP obtains a management state value in the current state information of the first MEP, and encapsulates the current state information of the first MEP to the second CCM, where when the first MEP is in the normal state, a value of the management state in the current state information of the first MEP is set to 0; of course, the first CCM may not carry the status information of the first MEP.

The sending subunit 422 is further configured to send, according to a preset sending period, the second CCM multicast to other MEPs in the MD or MA where the first MEP is located.

Optionally, the changing the management state of the first MEP includes:

when a first MEP is deleted by a management apparatus, the value of the management status in the status information of the first MEP is changed from 0 to 1;

or

or,

Optionally, the sending subunit 422 is specifically configured to:

sending the encapsulated first CCM multicast to other MEPs in the MD or MA where the first MEP is located by triggering continuous sending, wherein the other MEPs in the MD or MA where the first MEP is located receive the first CCM sent by the first MEP, and then deleting the state information corresponding to the first MEP stored by the other MEPs according to the first CCM, and setting the CC state value corresponding to the first MEP stored by the other MEP as closed;

or,

sending the encapsulated first CCM multicast to other MEPs in the MD or MA where the first MEP is located by triggering continuous sending, wherein the other MEPs in the MD or MA where the first MEP is located receive the first CCM sent by the first MEP, and then the other MEPs in the MD or MA where the first MEP is located close the state information of the first MEP stored in the MD or MA according to the first CCM, and setting the CC state value corresponding to the first MEP stored in the other MEP as closed;

or,

and multicast sending the encapsulated first CCM to other MEPs in the MD or MA where the first MEP is located by triggering continuous sending, wherein the other MEPs in the MD where the first MEP is located receive the first CCM sent by the first MEP, and then the waiting aging time for setting the CC state corresponding to the first MEP stored by the other MEPs as closed according to the state information in the first CCM is set as the waiting switching time in the state information of the first CCM by the other MEPs, and if the third CCM updated by the first MEP is not received after the waiting switching time is over, the waiting aging time is reset.

Optionally, the management state in the state information of the first MEP includes: closing, deleting and switching the main equipment and the standby equipment of the first MEP.

Optionally, referring to fig. 7, the sending unit 42 further includes a setting subunit 423, where:

the setting subunit 423 is configured to, when the function of the first MEP and/or the resource of the corresponding function is changed, reset the function type supported in the current state information of the first MEP and the value corresponding to the resource information of the corresponding supported function.

The encapsulating subunit 421 is further configured to encapsulate the status information of the reset first MEP into the first CCM.

The sending subunit 422 is further configured to send the first CCM multicast to other MEPs in the MD or MA where the first MEP is located by triggering continuous sending.

Here, if other MEPs in the MD where the first MEP is located receive the first CCM sent by the first MEP, the other MEPs can conveniently acquire the state information of the first MEP according to the first CCM, feed back the current state information of the first MEP to the management device where the other MEPs are located according to the state information carried by the first CCM, and store the current state information of the first MEP.

According to the first MEP provided by the embodiment of the invention, when the state information of the first MEP is changed, the corresponding state value in the state information is changed, and the state information after the state is changed is packaged to trigger continuous sending of the packaged state information multicast to other MEPs in the MD or MA where the first MEP is located, so that the other MEPs in the MD or MA where the first MEP is located perform corresponding operations according to the state information of the first MEP, and thus the response time of the system is saved. When the first MEP fails and the link from the first MEP to other MEPs in the maintenance federation where the first MEP is located has no failure, the other MEPs in the maintenance federation where the first MEP is located can timely distinguish and know the two failures and perform corresponding processing. For example, since only the first MEP itself has a special operation, and the link between the device where the first MEP is located and other devices does not fail, the data traffic associated with the first MEP does not need to be switched.

An embodiment of the present invention provides a first MEP5, shown with reference to fig. 8, the first MEP5 including: one or more processors 51, one or more memories 52, one or more communication interfaces 53 and a bus 54, the processors 51, the memories 52 and the communication interfaces 53 being connected by the bus 54 and performing communication with each other.

The bus 54 may be an Industry Standard Architecture (ISA) bus or a Peripheral Component Interconnect (PCI) bus or an Extended ISA (EISA) bus. The bus 54 may include an address bus, a data bus, a control bus, and the like. For ease of illustration, only one thick line is shown in FIG. 8, but this is not intended to represent only one bus or type of bus. Wherein:

the memory 52 is used to store executable program code, including computer operating instructions. The memory 52 may comprise high-speed RAM memory, and may also include non-volatile memory (non-volatile memory), such as at least one disk memory.

The processor 51 may be one or more Central Processing Units (CPUs), or one or more Application Specific Integrated Circuits (ASICs), or one or more Integrated circuits configured to implement embodiments of the present invention.

The communication interface 53 is mainly used to implement communication between MEPs in this embodiment.

The processor 51 is configured to acquire current state information of a first MEP, where the current state information of the first MEP includes: at least one or more of a management status of the first MEP, a supported function category, and resource information corresponding to the supported function category;

the processor 51 is further configured to trigger continuous sending of the state information of the first MEP, which is encapsulated to the first connectivity detection message CCM, when the current state information of the first MEP changes, and multicast the first CCM to the maintenance domain MD where the first MEP is located or another MEP in the maintenance alliance MA through the communication interface 53, where the other MEPs obtain the current state information of the first MEP located in the same MD or MA through the first CCM. The first CCM carries current state information of the first MEP.

Here, if other MEPs in the MD where the first MEP is located receive the first CCM, the MD where the first MEP is located or other MEPs in the MA perform corresponding processing according to the change of the state information of the first MEP carried by the first CCM. The corresponding processing includes updating or saving or deleting the state information related to the first MEP saved by the corresponding processing.

According to the first MEP provided by the embodiment of the invention, when the state information of the first MEP is changed, the state information after the state change is encapsulated to trigger continuous sending of the encapsulated state information multicast to other MEPs in the MD or MA where the first MEP is located, so that the other MEPs can perform corresponding operation according to the current state information of the first MEP, the MEPs can actively inform the current state information of the MEP to other MEPs in the same MD or MA, the other MEPs can correspondingly process the state information of the corresponding MEP stored in the MEP, and the MEPs can actively inform the current function support capability and the corresponding resource availability condition of the MEP, so that the system response efficiency is improved. When the first MEP fails and the link from the first MEP to other MEPs in the maintenance federation where the first MEP is located has no failure, the other MEPs in the maintenance federation where the first MEP is located can timely distinguish and know the two failures and perform corresponding processing. For example, since only the first MEP itself has a special operation, and the link between the device where the first MEP is located and other devices does not fail, the data traffic associated with the first MEP does not need to be switched.

Further, the processor 51 is further configured to, when the management state in the current state information of the first MEP is changed, package the changed management state into the first CCM;

the processor 51 is further configured to multicast, by triggering continuous transmission, the encapsulated first CCM to other MEPs in the MD or MA where the first MEP is located through the communication interface 53.

Here, if the other MEP in the MD or MA where the first MEP is located receives the first CCM, the other MEP in the MD or MA where the first MEP is located changes the state information of the first MEP stored by itself according to the first CCM.

Optionally, the processor 51 is further configured to, before the management state in the current state information of the first MEP is changed, that is, when the first MEP is in a normal state, the first MEP obtains a management state value in the current state information of the first MEP, and encapsulates the current state information (including the management state value in the current state information) of the first MEP in the second CCM. When the first MEP is in a normal state, setting the value of the management state in the current state information of the first MEP to be 0; of course, the first CCM may not carry the status information of the first MEP.

And the processor 51 is further configured to multicast, according to a preset sending period, the second CCM to other MEPs in the MD or MA where the first MEP is located through the communication interface 53.

Further, optionally, the changing the management state of the first MEP includes:

or

or,

Optionally, the processor 51 is specifically configured to:

multicast sending the encapsulated first CCM to other MEPs in the MD or MA where the first MEP is located through triggering continuous sending through a communication interface 53, if the other MEPs in the MD or MA where the first MEP is located receive the first CCM sent by the first MEP, deleting the state information corresponding to the first MEP stored by the other MEP in the MD or MA where the first MEP is located according to the first CCM, and setting the corresponding connection detection state value as closed;

or,

multicast-sending the encapsulated first CCM to other MEPs in the MD where the first MEP is located through a communication interface 53 by triggering continuous sending, if the other MEPs in the MD where the first MEP is located receive a first CCM message sent by the first MEP, closing the state information corresponding to the first MEP stored by the other MEPs in the MD where the first MEP is located according to the first CCM, and setting the communication detection state value corresponding to the first MEP stored by the other MEP to be closed;

or,

and multicast-sending the encapsulated first CCM to other MEPs in the MD where the first MEP is located through triggering continuous sending through the communication interface 53, wherein the other MEPs in the MD where the first MEP is located receive the first CCM sent by the first MEP, and then the other MEPs in the MD where the first MEP is located set the aging waiting time for closing the corresponding communication detection state setting of the first MEP stored by the other MEPs according to the state information of the first MEP in the first CCM as the switching waiting time in the state information of the first CCM. And resetting the waiting aging time if the third connectivity detection message updated by the first MEP is not received after the set waiting switching time is over.

Optionally, the management state in the state information includes: closing, deleting and switching the main equipment and the standby equipment of the first MEP.

Optionally, the processor 51 is further configured to reset, when the function of the first MEP and/or the resource of the corresponding function is changed, the function type supported in the current state information of the first MEP and the value corresponding to the resource information of the corresponding support function.

The processor 51 is further configured to encapsulate the reset status information into the first CCM.

The processor 51 is further configured to multicast, by triggering continuous transmission, the first CCM to other MEPs in the MD or MA where the first MEP is located through the communication interface 53.

Here, if other MEPs in the MD where the first MEP is located receive the first CCM sent by the first MEP, the MD where the first MEP is located or the other MEPs in the MA conveniently acquire the state information of the first MEP according to the first CCM, feed back the current state information of the first MEP to the management device where the management device is located according to the state information of the first MEP carried by the first CCM, and store the current state information of the first MEP carried by the first CCM.

According to the first MEP provided by the embodiment of the invention, when the state information of the first MEP is changed, the corresponding state value in the state information is changed, and the state information after the state is changed is packaged to trigger continuous sending of the packaged state information multicast to other MEPs in the MD or MA where the first MEP is located, so that the other MEPs in the MD or MA where the first MEP is located perform corresponding operations according to the state information of the first MEP carried by the first CCM, the response time of a system is saved, the current state information of the MEP can be actively notified to other MEPs in the same maintenance domain among the MEPs, the state information corresponding to the first MEP and stored by the other MEPs is correspondingly processed, the current function support capability and the corresponding resource availability of the MEP can be actively notified among the MEPs, and the response efficiency of the system is improved. When the first MEP fails and the link from the first MEP to other MEPs in the maintenance federation where the first MEP is located has no failure, the other MEPs in the maintenance federation where the first MEP is located can timely distinguish and know the two failures and perform corresponding processing. For example, since only the first MEP itself has a special operation, and the link between the device where the first MEP is located and other devices does not fail, the data traffic associated with the first MEP does not need to be switched.

The status information of the first MEPs 4 and 5 mentioned in the embodiment of the present invention may be carried by the Capability TLV in CCM, and the detailed manner that the Capability TLV in CCM carries the status information of the MEPs may refer to the description of the foregoing method embodiment, fig. 1 to 4 and the description corresponding thereto.

From the above description of the embodiments, it is clear to those skilled in the art that the present invention can be implemented by hardware, firmware, or a combination thereof. When implemented in software, the functions described above may be stored on or transmitted over as one or more instructions or code on a computer-readable medium. Computer-readable media includes both computer storage media and communication media including any medium that facilitates transfer of a computer program from one place to another. A storage media may be any available media that can be accessed by a computer. Taking this as an example but not limiting: computer-readable media can include RAM, ROM, EEPROM, CD-ROM or other optical disk storage, magnetic disk storage or other magnetic storage devices, or any other medium that can be used to carry or store desired program code in the form of instructions or data structures and that can be accessed by a computer. Furthermore, the method is simple. Any connection is properly termed a computer-readable medium. For example, if software is transmitted from a website, a server, or other remote source using a coaxial cable, a fiber optic cable, a twisted pair, a Digital Subscriber Line (DSL), or a wireless technology such as infrared, radio, and microwave, the coaxial cable, the fiber optic cable, the twisted pair, the DSL, or the wireless technology such as infrared, radio, and microwave are included in the fixation of the medium. Disk and disc, as used herein, includes Compact Disc (CD), laser disc, optical disc, Digital Versatile Disc (DVD), floppy Disk and blu-ray disc where disks usually reproduce data magnetically, while discs reproduce data optically with lasers. Combinations of the above should also be included within the scope of computer-readable media.

In short, the above description is only a preferred embodiment of the present invention, and is not intended to limit the scope of the present invention. Any modification, equivalent replacement, or improvement made within the spirit and principle of the present invention should be included in the protection scope of the present invention.

Claims

1. A method for maintaining state advertisement between MEP nodes of a alliance endpoint is characterized by comprising the following steps:

when the state information of a first MEP changes, packaging the changed state information of the first MEP into a first notification message CCM, and sending the first CCM to other MEPs in real time when a sending period does not need to be waited for; the state information of the first MEP includes: one or more of a management status of the first MEP, a supported function category, and resource information corresponding to the supported function category.

2. The method of claim 1, wherein encapsulating the changed state information of the first MEP in a first CCM when the state information of the first MEP changes and transmitting the first CCM to the other MEPs in real time without waiting for a transmission period to arrive comprises:

sending the packaged first CCM to the other MEPs.

3. The method of claim 2, wherein prior to the MEP management state change in the state information of the first MEP, comprising:

sending the second CCM to the other MEPs.

4. The method of claim 2, wherein when the first MEP is in a normal state, a management state value in the state information of the first MEP is set to 0, and wherein the management state change of the first MEP comprises:

or

or,

5. The method of claim 2 or 4, wherein sending the packaged first CCM to the other MEPs comprises:

6. The method according to any of claims 1-4, wherein managing the state in the state information of the first MEP comprises: closing, deleting and switching the main equipment and the standby equipment of the first MEP.

7. The method of claim 1, wherein encapsulating the changed state information of the first MEP in a first CCM when the state information of the first MEP changes and transmitting the first CCM to the other MEPs in real time without waiting for a transmission period to arrive comprises:

packaging the reset state information into a first CCM;

sending the first CCM to the other MEPs.

8. The method of any of claims 1-4, 7, wherein said other MEPs are located within the same maintenance alliance MA as said first MEP.

9. The method of any of claims 1-4 and 7, wherein the first CCM comprises a Capability TLV used to carry status information of the first MEP.

10. The method of claim 9, wherein the Capability TLV further comprises a subltlv for carrying one or more of management status in the status information of the first MEP, supported function categories, and resource information corresponding to the supported function categories.

11. A first maintenance alliance end point, MEP, comprising an obtaining unit and a sending unit, wherein:

the sending unit is configured to encapsulate the state information of the first MEP, which changes when the state information of the first MEP changes, into a first connectivity detection message CCM, and send the first CCM to other MEPs in real time when a sending period does not need to be waited for.

12. The first MEP as recited in claim 11, wherein the transmitting unit includes:

13. The first MEP of claim 12,

the encapsulating subunit is further configured to, before a management state in the state information of the first MEP is changed, when the first MEP is in a normal state, the first MEP obtains a management state value in the state information of the first MEP, and encapsulates the state information of the first MEP in the normal state to the second CCM;

the sending subunit is further configured to send the second CCM to the other MEPs.

14. The first MEP as recited in claim 12, wherein when the first MEP is in a normal state, a management state value in current state information of the first MEP is set to 0, and the management state change of the first MEP comprises:

or

or,

15. The first MEP as recited in claim 12 or 14, wherein the sending subunit is specifically configured to:

sending the first CCM to the other MEPs.

16. The first MEP as recited in any one of claims 11-14, wherein the management state in the state information of the first MEP comprises: closing, deleting and switching the main equipment and the standby equipment of the first MEP.

17. The first MEP as recited in claim 11, wherein the transmitting unit further comprises:

18. The first MEP as recited in any one of claims 11-14 and 17, wherein the other MEPs are located within the same maintenance alliance MA as the first MEP.

19. The first MEP as recited in any one of claims 11-14 and 17, wherein the first CCM comprises a Capability TLV for carrying status information of the first MEP.

20. The first MEP as recited in claim 19, wherein the capability tlv further includes a subltlv for carrying one or more of management status, supported function categories, and resource information corresponding to the supported function categories in the status information of the first MEP.