WO2015035852A1

WO2015035852A1 - Method and device for announcing state between nodes

Info

Publication number: WO2015035852A1
Application number: PCT/CN2014/084900
Authority: WO
Inventors: 黄兆胜; 刘斌; 蒋维廉
Original assignee: 华为技术有限公司
Priority date: 2013-09-16
Filing date: 2014-08-21
Publication date: 2015-03-19
Also published as: CN104468158B; CN104468158A

Abstract

Disclosed are a method and device for announcing a state between nodes, which relate to the technical field of communications, and realize active notification of a state of a current node for other nodes in the same domain between nodes, other nodes being enabled to conduct corresponding processing on the state; meanwhile, active notification of a function support capability of the current node and a corresponding resource availability condition can occur between nodes, thereby improving the system response efficiency. The method comprises: when state information about a first node changes, packaging the changed state information about the first node into a first notification message, and sending the first notification message to other nodes, wherein the state information about the first node comprises: a management state of the first node, a supported function category and one piece or multiple pieces of resource information corresponding to the supported function category. The embodiments of the present invention can be applied to a maintenance end point inside the Ethernet.

Description

Method and device for status notification between nodes

The present application claims priority to Chinese Patent Application No. 201310422696.2, entitled "A Method and Apparatus for State Notification of Inter-Node Status", filed on September 16, 2013, the entire contents of which are incorporated herein by reference. In this application.

Technical field

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

Background technique

ETH-OAM (Ethernet-Operations, Administration and Maintenance), ETH-OAM mainly includes two functions: fault management and performance management. ETH-OAM compliance standards: electrical and electronic engineers The IEEE (Institute of Electrical and Electronics Engineers) standard 802. lag and International Telecommunications Union (ITU Telecommunications Union) ITU-TY.1731; The specific functions of ETH-0AM include: Connectivity Test CC (Continuity Check), ring Back detection LB (Loopback), Link Trace (LT), Loss Measurement LM (Loss Measurement), Time Delay Measurement (DMCDelay Measurement) and Synthetic Loss Measurement (SLM). The concepts involved in ETH-OAM include: maintenance domain MD (Maintenance Domain), Maintenance Alliance (MA), Maintenance Association End Point (MEP), and Maintenance Domain Intermediate Point (MIP). Here ETH_0AM is deployed based on MD, MA, MEP and MIP, and the detection body of MEP 3⁄4 ETH-OAM.

The CM (Continuity Check Message) in the prior art is a multicast frame generated by the MEP and broadcast to all other MEPs in the same MA. The CCM is periodically exchanged between MEPs to allow MEP discovery. One maintains connectivity between other MEPs in the domain MD. In order to detect the fault, the local MEP maintains a CCM list from the remote MEP. The CCM list is created based on the configured remote MEP. When the local MEP does not receive the configured CCM of the remote MEP in the preset period, The local MEP will issue an alarm.

The inventors have found that at least the following problems exist in the prior art: When the local MEP exceeds 3.5 times the private room If the CCM sent by a remote MEP is not received in the interval, the link between the local MEP and the remote MEP is faulty. As a result, the link between the local MEP and the remote MEP. When the path fails, the local MEP cannot obtain the status information of the remote MEP in time, which in turn increases the response time of the system.

Summary of the invention

Embodiments of the present invention provide a method and apparatus for inter-node status advertisement to improve system response efficiency.

In a first aspect, a method for status notification between nodes is provided, including:

When the state information of the first node is changed, the state information of the change of the first node is encapsulated into the first advertisement packet, and the first advertisement packet is sent to other nodes; The status information includes: one or more of a management status of the first node, a supported function type, and resource information corresponding to the type of the supported function.

In a first possible implementation manner of the first aspect, the first node is a maintenance alliance termination point

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 first MEP occurs. Transmitting the changed state information to the first CCM and transmitting the first CCM to the other MEPs includes: when the management state in the state information of the first MEP changes, the changed management state Encapsulating to the first CCM;

The encapsulated first CCM is sent to the other MEPs.

With the second possible implementation 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 encapsulates the obtained state information of the first MEP in a normal state to the first Two 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, the management state in the state information of the first MEP is The value is set to 0, and the management state change of the first MEP includes:

When the first MEP is deleted by the management device, the management status in the status information of the first MEP The value of the state changes from 0 to 1;

Or

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

Or,

When the active/standby switchover occurs on the management device where the first MEP is located, the value of the management state in the state information of the first MEP changes from 0 to 1.

In conjunction with the second or fourth possible implementation of the first aspect, in a fifth possible implementation manner of the first aspect, the sending the encapsulated first CCM to the other MEP includes : transmitting the first CCM to the other MEPs by triggering a continuous transmission.

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 status in the status information of the first MEP includes: And delete the active/standby switch of the device where the first MEP is located.

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 occurrence of the first MEP changes. The status information is encapsulated to the first CCM, and the first CCM is sent to the other MEP, including:

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

Encapsulating the re-set state information to the first CCM;

Sending the first CCM to the other MEPs.

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

In conjunction with any one of the first to eighth possible implementations of the first aspect, in a ninth implementation of the first aspect, the first CCM includes a Capab ili TLV, the Capab i 1 i ty The TLV is used 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 Capab ili TLV further includes a SubTLV, where the SubTLV is used to carry the status information of the first MEP. Management status, types of supported functions, and resource information corresponding to the types of functions supported One or more of them.

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

The acquiring unit is configured to acquire the state information of the first MEP, where the state information of the first MEP includes: a management state of the first MEP, a supported function type, and resource information corresponding to the supported functional category. One or more of

The sending unit is configured to, when the state information of the first MEP changes, encapsulate the state information of the change of the first MEP into the first connectivity detection message CCM, and the first CCM Send to other MEPs. In a first possible implementation manner of the second aspect, the sending unit includes:

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

And a sending subunit, configured to send the encapsulated first CCM to the other MEP.

With reference to the first possible implementation of the second aspect, in a second possible implementation manner of the second aspect, the encapsulating subunit is further configured to: change management status in status information of the first MEP Before 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 encapsulates the state information when the first MEP is in a normal state. Two CCM;

The sending subunit is further configured to send the second CCM to the other MEP according to the sending.

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, the management state in the current state information of the first MEP The value of the first MEP is changed to 0, and the management status change of the first MEP includes:

When the first MEP is deleted by the management device, the value of the management state in the state information of the first MEP is changed from 0 to 1;

Or

Or,

When the management device where the first MEP is located has an active/standby switchover, the status information of the first MEP The value of the management state in the message changes from 0 to 1.

In conjunction with the first or third possible implementation of the first aspect, in a fourth possible implementation 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, 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 in the status information of the first MEP The status includes: shutdown, deletion, and active/standby switchover of the device where the first MEP is located.

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

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

The package subunit is further configured to encapsulate the repositioned state information to the first CCM;

The sending subunit is further configured to send the first CCM to the other MEP by triggering continuous transmission. With reference to the second aspect, any one of the first to the sixth possible implementation manners of the second aspect, in a seventh possible implementation manner of the second aspect, the other MEP is located in the first MEP Within the same maintenance alliance MA.

With reference to the second aspect, any one of the first to the seventh possible implementation manners of the second aspect, in the eighth possible implementation manner of the second aspect, the first CCM includes a Capab ili TLV, The Capab ili TLV is configured to carry status information of the first MEP. In conjunction with the eighth possible implementation of the second aspect, in a ninth possible implementation manner of the second aspect, the Capab ili TLV further includes a SubTLV, where the SubTLV is configured to carry a state of the first MEP One or more of the management status in the information, the type of supported function, and the resource information corresponding to the type of the supported function.

The method and device for inter-node state notification according to the embodiment of the present invention, when the state information of the first node is changed, by changing the corresponding state value in the state information, and packaging the changed state information of the first node to the The other MEPs in the maintenance alliance in which the first node is located, and other nodes in the maintenance alliance in which the first node is located may perform corresponding operations according to the received state information of the first node, thereby solving the problem that the nodes can actively Notify other nodes in the same domain with their own status information, and The other nodes perform corresponding processing on the state information of the first node that is saved, and the nodes can actively announce the current function support capability and the corresponding resource availability to other nodes, thereby improving the system response efficiency. In addition, if the solution is applied to the Ethernet 0AM, the first node is the first MEP, and when the state of the first MEP changes, the first MEP encapsulates the changed state information of the first MEP into the CCM and sends the same Maintain other MEPs in the alliance so that other MEPs can know the status changes of the first MEP in time and handle them accordingly. If the link between the first MEP and the other MEPs in the maintenance alliance where the first MEP is located is not faulty, the other MEPs in the maintenance alliance where the first MEP is located may be distinguished in time. Know these two kinds of faults and deal with them accordingly.

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 embodiments or the description of the prior art will be briefly described below. Obviously, the drawings in the following description are only It is a certain embodiment of the present invention, and other drawings can be obtained from those skilled in the art without any creative work.

1(a) is a partial structural diagram of a Capabilial 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. 3 is a schematic flowchart of another method for status notification between MEPs according to an embodiment of the present invention; FIG. 4 is another schematic diagram of a method for status notification between MEPs according to an embodiment of the present invention; FIG. 5 is a schematic structural diagram of a first MEP according to an embodiment of the present invention; FIG.

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

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

FIG. 8 is a schematic structural diagram of still another first MEP according to an embodiment of the present invention.

detailed description

The technical solutions in the embodiments of the present invention will be clearly described in conjunction with the drawings in the embodiments of the present invention. It is obvious that the described embodiments are only a part of the embodiments of the present invention, and not all of the embodiments. All other embodiments obtained by a person of ordinary skill in the art based on the embodiments of the present invention without departing from the inventive scope are the scope of the present invention. The "nodes" mentioned in the embodiments of the present invention are node network devices, or functional entities deployed on network devices.

The present invention is applicable to the operation, management, and maintenance of Ethernet (ETH-OAM). Among them, the concepts involved in ETH-OAM include: Maintenance Domain (MD), Maintenance Association (MA), Maintenance Association End Point (MEP) and Maintenance Domain Intermediate Point (MIP). . The MD indicates the network covered by the ETH-OAM. The boundaries of the MD are defined by a series of MEPs configured on the port and identified by the "maintenance domain name". The concept of level (hierarchy) was introduced in the maintenance domain. The maintenance domain is divided into eight levels, identified by the integers 0~7. You can configure multiple maintenance alliance MAs in the maintenance domain as required. Each maintenance federation is a collection of maintenance endpoints in the maintenance domain. The MA is identified by "Maintain Domain Name + Maintenance Alliance Name". The MEP determines the range and boundary of the MD and is the edge node of the MA. MD and MA determine the service and level of the packets sent by the MEP. Here, the MEP is the session body of the ETH-0AM specific function deployment, and is used to send and receive the corresponding 0AM message, and the MEP is the detection body of the ETH-0AM. A method for inter-node state notification according to an embodiment of the present invention includes:

The first node acquires current state information of the first node.

The status information of the first node includes: one or more of a management status of the first node, a function type supported by the first node, and resource information corresponding to the supported function type.

Assume that the first node is a maintenance association end point MEP (hereinafter referred to as "first MEP") in the maintenance domain MD1, and the status information of the first node is carried in the first node multicast. The Capability TLV (Type-Length-Value) in the sent connectivity check message CCM is sent to other MEPs. Here, the "other MEPs" may be other MEPs in the maintenance domain MD1 where the first MEP is located, or other MEPs in the maintenance alliance MA where the first MEP is located. The Capability TLV is used to carry the management status of the MEP, the function support status of the MEP, and the resource status corresponding to the MEP support function. The structure of the Capability TLV is shown in Figure 1 (a), where the Capability TLV type TLV TYPE is 1 byte; the Capability TLV length TLV LENGTH is 2 bytes; C Ning bility TLV value TLV VALUE 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 the management status value of the MEP, the FUN_SUPP0RT_VALUE field indicates the MEP support function type value, and the FUN-RESOURCE-VALUE field indicates the MEP support function type. Resource information.

The bit of the Capability TLV is shown in Figure 2. The first line of Figure 2 includes the management status of the MEP. The management status of the MEP includes: Admin-Down, Admin-Del, and the Admin-Switch of the device where the MEP resides. The management status of the MEP may also include: Waiting time (Wait-switch-time). When any one of the management states of the MEP changes, the first MEP sends a Continuity Check Message (CCM) to the other MEPs, so that other MEPs can perform the management state value of the first MEP carried in the CCM. The corresponding processing.

The second line of Figure 2 includes the types of MEP support functions. The types of MEP support functions include: Synthetic Loss Measurement - Support SLM-S (Synthetic Loss Measurement - Support) Delay Measurement - Support DM-S (Delay) Measurement-Support) Loss of Packet Measurement - Supports LM-S (Loss Measurement-Support), Link Tracking - Supports LT-S (Link Trace-Support), Multicast Loopback - Supports MLB-S (Multicast Loopback-Support) and Loopback - Supports LB-S (Loopback-Support).

The third line of Figure 2 includes resource information for the types of supported functions of the MEP. The resource information of the MEP supporting function type includes: Synthetic Loss Measurement-Resource (Synthetic Loss Measurement-Resource), Delay Measurement-Resource (Delay Measurement-Resource), Packet Loss Measurement-Resource LM- R ( Loss Measurement-Resource), Link Trace-Resource, Link Loop-Resource, and Loopback-Resource .

When the type of the support function of the first MEP changes or the resource information corresponding to the supported function type changes, the first MEP encapsulates the changed status information into the CCM, and then sends the CCM multicast to the continuous transmission by triggering the continuous transmission. Other MEPs. In the embodiment of the present invention, the number of consecutive transmissions is three times as an example, and the actual situation is not specifically limited.

Optionally, any one or more of the management status of the Capability TLV in the CCM, the type of the supported function, and the resource information of the supported function type may be identified in a sub-TLV (SubTLV) manner, so that when the Capability needs to be extended Other functions of the TLV can also be achieved by adding Sub_TLV.

In this case, the structure of SubTLV is as shown in Figure 1 (b). SubTLV includes: SubTLV type SubTLV-TYPE (1 byte), SubTLV length SubTLV_LENGTH (2 bytes), and SubTLV The value of SubTLV - VALUE. The size of the SubTLV-VALUE is determined by SubTLV-LENGTH, wherein the SubTLV-VALUE can be the MEP state MEP_STATE_TLV, the function support FUN_SUPPORT_TLV, and the function resource FTO_RESOURCE_TLV.

When the current state information of the first node changes, the state information of the change of the first node is encapsulated into the first advertisement packet, and the first advertisement packet is sent to other nodes.

The first CCM carries the status information of the first node in the MD 1 where the first node (the first MEP) is located or the other MEPs in the maintenance alliance. The first CCM carries the current status information of the first node.

When the first node (the first MEP) is in the normal state, the first MEP obtains its current management state, for example: the management state value of the first MEP. Specifically, the current management status of the first MEP includes: whether the device where the first MEP is currently located has an active/standby switchover or whether the first MEP is currently in the deleted or closed state. The first MEP encapsulates the current management state of the first MEP into the Capab ili TLV of the second CCM, and then sends the second CCM multicast to the MD1 where the first MEP is located or where the first MEP is located according to the sending period. If other MEPs in the maintenance alliance are supported by other MEPs in the MD 1 or other MEPs in the same maintenance alliance as the first MEP support, the second CCM carrying the Capabili TLV is saved and/or updated. The Capab ili TLV carries status information corresponding to the current management status of the first MEP.

When the current management state of the first MEP changes, the first MEP encapsulates the changed state information into the first CCM, and sends the first CCM to the real-time by triggering the continuous transmission when the waiting for the transmission period does not arrive. Other MEPs in the MD 1 where the first MEP is located or other MEPs in the maintenance alliance where the first MEP is located, so that other MEPs in the MD 1 where the first MEP is located or other maintenance alliances in which the first MEP is located The MEP receives the first CCM, and finds that the received status information of the first MEP in the first CCM changes compared with the status information of the first MEP saved by the receiver, and performs corresponding processing.

The method for notifying the inter-node status of the embodiment of the present invention, when the current state information of the first node (the first MEP) is changed, the state information of the first MEP after the change state is encapsulated in the CCM, and the multicast is sent to the Other nodes (MEPs) in the MD where the first MEP is located or other MEPs in the maintenance alliance where the first MEP is located, so that other MEPs perform corresponding operations according to the changed state information of the first node, thereby causing the nodes to The status of other MEPs in the same maintenance domain can be actively notified, and the other MEPs in the same maintenance domain or other MEPs in the same maintenance domain can be saved. The status information of a MEP is processed correspondingly, and the nodes can actively notify their current function support capabilities and corresponding resource availability, thereby improving the system response efficiency. If the link between the first MEP and the other MEPs in the maintenance alliance where the first MEP is located is not faulty, the other MEPs in the maintenance alliance where the first MEP is located may be distinguished in time. Know these two kinds of faults and deal with them accordingly. For example, because only the first MEP itself has a special operation, and the link between the device where the first MEP is located and other devices is not faulty, the data service associated with the first MEP does not need to be switched.

Specifically, the following description will be made in conjunction with specific embodiments.

As shown in FIG. 3, an embodiment of the present invention provides another method for status notification between MEPs, where the method includes:

When the first MEP is in the normal state, the first MEP acquires the management state value in the current state information of the first MEP, and encapsulates the management state value in the current state information of the first MEP to the first CCM.

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

The management status in the status information of the first MEP includes: shutdown, deletion, and active/standby switchover of the device where the first MEP is located.

The first MEP of the CCM is a maintenance association end point MEP (hereinafter referred to as "the first MEP") in the maintenance domain MD1, and the status information of the first MEP is carried in the first MEP. The Capability TLV (Type-Length-Value) in the connectivity test packet sent by the multicast is sent to other MEPs in the MD1 or other MEPs in the maintenance association MA1 where the first MEP is located. The management status in the Capab ity TLV in the first CCM sent by the first MEP includes: Admin-Down, Admin-Del, and the active/standby switch of the device where the first MEP is located (Admin-Switch) ).

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

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

Of course, the first CCM may not carry the status information of the first MEP. 202. The first MEP multicasts, according to a preset sending period, the first CCM to the other MEP in the MD or MA where the first MEP is located.

203. When the management status in the current status information of the first MEP changes, the changed management status is encapsulated to the second CCM.

The management status change of the first MEP includes:

Or

When the first MEP is powered off by the management device, the value of the management state in the state information of the first MEP changes from 0 to 1;

Or,

Here, when the active/standby switchover occurs on the management device where the first MEP is located, the value of the Admin-Switch of the Capabiity TLV is set to 1 by 0, and the Capabiity TLV is encapsulated into the second CCM (Continuity Check Message). The multicast is sent to the other MEPs in MD1 or MA1 where the first MEP is located.

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 the continuous transmission, so that the MEP in which the first MEP is located or other MEPs in the MA And changing, according to the changed state information of the first MEP carried by the second CCM, the state information corresponding to the first MEP saved by itself.

Here, the second CCM multicast that is encapsulated is sent to the other MEPs in the MD or MA where the first MEP is located by triggering the continuous transmission, including:

Sending the second CCM multicast to the other MEPs in the MD or MA where the first MEP is located by triggering the continuous transmission, so that the other MEPs in the MD or MA in which the first MEP is located are deleted according to the second CCM. The status information corresponding to the first MEP, and the CC (Cont inuity Check) status position corresponding to the second CCM in the other MEP is off.

Here, when the first MEP is deleted, the corresponding Admin-Del in the Capabiity TLV will be set to 1, and trigger the continuous sending of the Capabiity TLV with the Admin-Del value of 1 in the second CCM group. Broadcast to other MEPs (such as the second MEP) in the MD or MA where the first MEP is located, and second The MEP does not have to wait 3.5 times of the transmission cycle time to receive the second CCM sent by the first MEP due to its own state change, but quickly receives the second CCM sent when the first MEP is deleted and is in the second MEP. The status information of the first MEP saved by the second MEP is deleted locally.

Specifically, when the other MEP in the MD or the MA (such as the second MEP) receives the second CCM sent by the first MEP, the comparison finds that the Admin-Del value and the second MEP are in the second CCM. If the saved ME-Del value of the first MEP is different, the second MEP performs the Admin-Del process, and the CC state location corresponding to the first MEP saved by the second MEP is Down.

Optionally, the second CCM multicast is sent to the other MEP (such as the second MEP) in the MD or the MA where the first MEP is located by triggering the continuous sending, so that the MD of the first MEP or other MEPs in the MA are in accordance with the The second CCM performs a shutdown process, and sets the CC state position of the first MEP in the MD or the other MEP in the MA of the first MEP to off.

Here, when the first MEP is closed, the corresponding Admin-Down in the Capability TLV in the second CCM sent by the first MEP is set to 1, and immediately triggers the continuous transmission to send the Capability TLV to the second CCM multicast to The other MEP (such as the second MEP) in the MD or MA of the first MEP, and the second MEP does not need to wait 3.5 times of the transmission cycle time to receive the second CCM sent by the first MEP due to its own state change.

Specifically, when the first MEP is in the MD or the other MEP in the MA (for example, the second MEP) receives the second CCM sent by the first MEP, the Admin-Down value in the second CCM is pre-stored with the second MEP. The Admin-Down value of the first MEP is different. The Admin-Down process is performed, and the corresponding CC (Continuity Check) status bit is set to the Admin-Down value carried in the second CCM.

Or,

Transmitting the encapsulated first CCM multicast to other nodes (such as the second MEP) in the MD or MA where the first MEP is located by triggering continuous transmission, so that the second MEP is to be the second according to the status information in the first CCM. The waiting aging time of the first MEP is set to the waiting time of the first CCM. If the waiting time of the first CCM is not received, the third node does not receive the third node. CCM, resets the waiting aging time.

When the first MEM is in the MD or the other MEP in the MA (for example, the second MEP), the Admin-Switch status information in the first CCM and the Admin-Switch status information of the first MEP saved in the second MEP are saved. If the two MEPs are different, the second MEP performs the Admin-Switch state change to 1 according to the Admin-Switch status information of the first MEP carried in the second CCM, and the waiting aging time of the corresponding CC status bit is Down. Waiting for Capability TLV Switching time ( Wait-switch-time ). When the Wait_switch_time ends, if the second MEP does not receive the third CCM sent by the first MEP, the second MEP sets the CC status bit to Down and triggers the generation of the remote fault identification (RDI).

When the second MEP in the Wait-switch-time receives the third CCM packet with the lj Admin-Switch status set to 0, the second MEP resets the transmission waiting period of 3-5 times.

If the second CCM with the Admin-Switch status of 1 is lost, the MD of the first MEP or other MEPs of the MA (such as the second MEP) can extend the Waiting for Waiting after the 3.5 times CCM transmission period according to the policy. The switch-time is set to Down and triggers the generation of the RDI. The policy mainly includes: 1. Waiting time of the application packet, aging according to 3.5 times CCM sending period plus waiting time; 2. Ignoring the packet Waiting time, aging according to 3.5 times the CCM transmission period.

In the embodiment provided by the present invention, the management status value of the MEP is only 0 or 1 as an example, and the waiting aging time setting is only described by taking the CCM transmission period as an example, and is not specifically limited.

The method for advertising status between MEPs provided by the embodiment of the present invention, when the management state in the state information of the first MEP changes, by changing the corresponding management state value in the state information, and after triggering continuous transmission, the package is changed after the state is changed. The status information is multicast and sent to other MEs (such as 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 status information of the first MEP, so that the MEP can The current state actively notifies the second MEP in the same maintenance domain or maintenance alliance, and causes the second MEP to process the status information of the corresponding first MEP saved by itself, and the MEP can actively notify the current function support capability and Corresponding to the availability of resources, the system response efficiency is improved. If the link between the first MEP and the other MEPs in the maintenance alliance where the first MEP is located is not faulty, the other MEPs in the maintenance alliance where the first MEP is located may be distinguished in time. Know these two kinds of faults and deal with them accordingly. For example, because only the first MEP itself has a special operation, and the link between the device where the first MEP is located and other devices is not faulty, the data service 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. A function type supported in status information when a function of a first MEP and/or a resource of a corresponding function is changed. And the value corresponding to the resource information corresponding to the support function is reset.

It is assumed that the first MEP is a maintenance domain of the maintenance domain MD1 or the maintenance alliance MA1, and the status information of the first MEP is carried in the Capabiity TLV of the connectivity detection message CCM sent by the first MEP multicast ( Type-Length-Value ) is sent to other MEPs in MD1 or MAI (than Such as the second MEP). When the local Ethernet corresponding operation, management, and maintenance of the ETH-0AM (Ethernet-Operat i ons, Admin i strat ion and Maintenance) function is globally changed or the session resources cannot meet the user requirements, the first MEP corresponds to The ETH-0AM function and the change in the resource bit value are reset and trigger the continuous transmission of the CCM.

Optionally, the first MEP encapsulates the reset ETH-0AM function and the resource bit value into the Capab ili TLV of the CCM before the global enabling change of the local ETH-0AM function or the situation in which the session resource fails to be required by the user. Medium, and multicast is sent to other MEPs in MD 1 or MA1 (such as the second MEP) according to the sending period.

302. The first MEP encapsulates the state information of the first MEP that is re-set to the first CCM.

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

The first MEP sends the first CCM to the other MEPs (such as the second MEP) in the MD 1 or MA1 where the first MEP is located by triggering the continuous transmission, so that the second MEP will carry the first one carried by the first CCM. The status information of the MEP is compared with the CCM sent when the first MEP is in the normal state, and the global enabling change of the ETH-0AM function of the first MEP or the shortage of the session resources is determined, that is, the ETH-0AM function and the resource bit value are changed. The function of the second MEP to report the first MEP to the management device where the second MEP is located may be caused by the ETH-0AM function of the first MEP being closed or the resource is insufficient, and the ETH-0AM function of the first MEP is saved. The first CCM sent when the resource bit value changes. This first CCM is used to display the view.

The method for informing the inter-MEP state in the embodiment of the present invention, when the function in the state information of the first MEP and/or the resource of the corresponding function is changed, by changing the corresponding function and/or corresponding in the state information of the first MEP And the second MEP in the MD or the MA in which the first MEP is located, so that the second MEP is based on the status information of the first MEP. Corresponding operations are performed, so that the first MEP can actively notify the second MEP in the same maintenance domain or maintenance alliance in the current state, and enable the second MEP to process the state information of the first MEP saved by itself, and MEPs can proactively announce their current functional support capabilities and corresponding resource availability, thereby improving system response efficiency. If the link between the first MEP and the other MEPs in the maintenance alliance where the first MEP is located is not faulty, the other MEPs in the maintenance alliance where the first MEP is located may be distinguished in time. Know these two A fault, and deal with it accordingly. For example, because only the first MEP itself has a special operation, and the link between the device where the first MEP is located and other devices is not faulty, the data service associated with the first MEP does not need to be switched.

The embodiment of the present invention is only described by taking the method of the first node to implement the inter-MEP state advertisement as an example. The other MEPs in the embodiment also have the function corresponding to the first MEP, that is, the first MEP. The method of state notification between the MEPs is also applicable to other MEPs. The first MEP can be interchanged with other MEPs at the functional location, which is not specifically limited by the present invention.

The embodiment of the present invention provides a first MEP 4, which may be any maintenance termination point in the Ethernet. In the embodiment of the present invention, the specific form of the first MEP is not specifically limited. The method of any of the foregoing MEP status notifications of the embodiments of the present invention may be implemented. Referring to FIG. 5, the first MEP 4 includes an acquisition unit 41 and a transmission unit 42. among them:

The obtaining unit 41 is configured to obtain current state information of the first MEP, where the current state information of the first MEP includes: one of a management state of the first MEP, a type of the supported function, and resource information corresponding to the type of the function. Multiple

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

Here, if the MD of the first MEP or another MEP in the MA receives the first CCM, the MD of the first MEP or other MEPs of the MA changes according to the state information of the first MEP carried in the first CCM. Perform corresponding processing.

The first MEP of the embodiment of the present invention, when the state information of the first MEP is changed, encapsulates the changed state information, and triggers continuous transmission to multicast the encapsulated state information to the MD or MA where the first MEP is located. Other MEPs, so that other MEPs perform corresponding operations according to the status information of the first MEP, so that MEPs can actively notify their own current status information to other MEPs in the same maintenance domain or MA, and save other MEPs to themselves. Corresponding processing is performed on the status information of the first MEP, and the MEP can actively announce its current function support capability and corresponding resource availability, thereby improving the system response efficiency. In the case that the first MEP fails and the link between the first MEP and another MEP in the maintenance alliance in which the first MEP is located is not faulty, the first MEP Other MEPs in the maintenance alliance can distinguish these two faults in time and deal with them accordingly. For example, because only the first MEP itself has a special operation, and the link between the device where the first MEP is located and other devices is not faulty, the data service associated with the first MEP does not need to be switched.

Further, referring to FIG. 6, the transmitting unit 42 may include: a packaging subunit 421 and a transmitting subunit 422, where:

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

The sending sub-unit 422 is configured to send the encapsulated first CCM multicast to the other MEPs in the MD or MA where the first MEP is located by triggering continuous transmission.

Optionally, the encapsulating subunit 421 is further configured to: before the management state change in the current state information of the first MEP, that is, when the first MEP is in a normal state, the first MEP acquires the current state information of the first MEP. Management state value, and encapsulating the current state information of the first MEP into the second CCM. When the first MEP is in the normal state, the value of the management state in the current state information of the first MEP is set to 0; The CCM may also not carry the status information of the first MEP.

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

Optionally, the management status change of the first MEP includes:

When the first MEP is deleted by the management device, the value of the management state in the state information of the first MEP changes from 0 to 1;

Or

Or,

Optionally, the sending subunit 422 is specifically configured to:

Sending the encapsulated first CCM multicast to the other MEPs in the MD or MA where the first MEP is located by triggering the continuous transmission, and the other MEPs in the MD or MA in which the first MEP is located receive the first MEP transmission. a CCM, the other MEP deletes the state information corresponding to the first MEP saved by the first CCM, and sets the connectivity detection CC status value corresponding to the first MEP saved by itself. For closing

Or,

Sending the encapsulated first CCM multicast to the other MEPs in the MD or MA where the first MEP is located by triggering the continuous transmission, and the other MEPs in the MD or MA in which the first MEP is located receive the first MEP transmission. a CCM, the MD in which the first MEP is located, or other MEPs in the MA, according to the first CCM, the state information of the first MEP saved by the first CCM is closed, and the CC state value corresponding to the first MEP saved by the first MEP is set. Bit is off;

Or,

Sending the encapsulated first CCM multicast to the other MEPs in the MD or the MA where the first MEP is located by triggering the continuous transmission, and the other MEPs in the MD where the first MEP is located receives the first CCM sent by the first MEP. And waiting for the aging time in which the other MEP sets the CC state corresponding to the first MEP to be closed to the waiting aging time in the state information of the first CCM according to the status information in the first CCM, if waiting for the switching time If the third CCM of the first MEP update is not received after the end, the waiting aging time is reset.

Optionally, the management status in the status information of the first MEP includes: off, deleting, and active/standby switching of the device where the first MEP is located.

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, The type of function supported in the current state information of a MEP and the value corresponding to the resource information of the corresponding supporting function are reset.

The package subunit 421 is further configured to encapsulate the state information of the first MEP after being repositioned to the first

CCM.

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

Here, if the other MEPs in the MD where the first MEP is located receive the first one sent by the first MEP

The CCM is configured to obtain the state information of the first MEP according to the first CCM, and feed back the current state information of the first MEP to the management device where the first CCM is located, and store the current MEP information. Current status information.

The first MEP of the embodiment of the present invention, when the state information of the first MEP changes, triggers the continuous transmission by changing the corresponding state value in the state information, and by changing the state information after the state is changed by the package The encapsulated state information is multicast and sent to the other MEPs in the MD or the MA where the first MEP is located, so that the MDs in which the first MEP is located or other MEPs in the MA perform corresponding operations according to the state information of the first MEP. Therefore, the response time of the system is saved. Therefore, the MEP can actively notify the other MEPs in the same maintenance domain or MA in the same maintenance domain or other MEPs in the same maintenance domain or ME. The status information is processed correspondingly, and the MEP can actively announce its current function support capability and corresponding resource availability, thereby improving the system response efficiency. If the link between the first MEP and the other MEPs in the maintenance alliance where the first MEP is located is not faulty, the other MEPs in the maintenance alliance where the first MEP is located may be distinguished in time. Know these two kinds of faults and deal with them accordingly. For example, because only the first MEP itself has a special operation, and the link between the device where the first MEP is located and other devices is not faulty, the data service associated with the first MEP does not need to be switched.

An embodiment of the present invention provides a first MEP 5, as shown in FIG. 8, the first MEP 5 includes: one or more processors 51, one or more memories 52, one or more communication interfaces 53 and a bus The processor 51, the memory 52, and the communication interface 53 are connected by a bus 54 and complete communication with each other.

The bus 54 can be an Industry Standard Architecture (ISA) bus or a Peripheral Component (PCI) bus or an Extended Industry Standard Architecture (EISA) bus. . The bus 54 can include an address bus, a data bus, a control bus, and the like. For ease of representation, only one thick line is shown in Figure 8, but it does not mean that there is only one bus or one type of bus. among them:

The memory 52 is for storing executable program code, the program code including computer operating instructions. The memory 52 may contain high speed RAM memory and may also include 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 specific integrated circuits (ASICs), or configured to implement the present invention. One or more integrated circuits of an embodiment of the invention.

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

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

The processor 51 is further configured to: when the current state information of the first MEP changes, trigger the continuous sending of the state information of the change of the first MEP to the first connectivity detection message CCM, and pass the first CCM. The communication interface 53 is multicast and sent to the maintenance domain MD where the first MEP is located or the other MEPs in the maintenance alliance MA. The other MEPs acquire 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 the other MEPs in the MD in which the first MEP is located receive the first CCM, the MDs in which the first MEP is located or other MEPs in the MA change according to the state information of the first MEP carried by the first CCM. Perform corresponding processing. The corresponding processing includes updating or saving or deleting status information related to the first MEP saved by itself.

In the first MEP of the embodiment of the present invention, when the state information of the first MEP is changed, the status information after the state is changed by the package is triggered to continuously send the encapsulated state information to the MD or MA where the first MEP is located. The other MEPs in the other MEPs, so that other MEPs can perform corresponding operations according to the current state information of the first MEP, so that the MEPs can actively notify their MEDs of other MEPs in the same MD or MA, and make other MEPs themselves. The saved MEP status information is processed correspondingly, and the MEP can actively announce its current function support capability and corresponding resource availability, thereby improving the system response efficiency. If the link between the first MEP and the other MEPs in the maintenance alliance where the first MEP is located is not faulty, the other MEPs in the maintenance alliance where the first MEP is located may be distinguished in time. Know these two kinds of faults and deal with them accordingly. 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 is not faulty, the data service 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 changes, package the changed management state to the first CCM;

The processor 51 is further configured to multicast the first CCM after being encapsulated by the continuous transmission to the other MEPs in the MD or MA where the first MEP is located by triggering continuous transmission.

Here, if the MD of the first MEP or another MEP in the MA receives the first CCM, the MD of the first MEP or another MEP of the MA changes the first MEP saved by itself according to the first CCM. status information.

Optionally, the processor 51 is further configured to: before the management state change in the current state information of the first MEP, that is, when the first MEP is in a normal state, the first MEP acquires a current state information of the first MEP. The management status value in the interest, and encapsulates the current status information of the first MEP (including the management status value in the current status information) to the second CCM. When the first MEP is in the normal state, the 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 state information of the first MEP.

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

Further, optionally, the management status change of the first MEP includes:

Or

Or,

Optionally, the processor 51 is specifically configured to:

The first CCM that is encapsulated is sent to the other MEPs in the MD or MA where the first MEP is located through the communication interface 53 by triggering the continuous transmission. If the MEP in which the first MEP is located or other MEPs in the MA receives the The first CCM sent by the first MEP, the MD of the first MEP or the other MEPs in the MA deletes the state information corresponding to the first MEP saved by the first CCM, and the corresponding connectivity detection status value Set to off;

Or,

Sending the encapsulated first CCM to the other MEPs in the MD where the first MEP is located through the communication interface 53 by triggering the continuous transmission, if the other MEPs in the MD where the first MEP is located receive the first MEP transmission. The first CCM text, the other MEPs in the MD in which the first MEP is located, according to the first CCM, the state information corresponding to the first MEP saved by the first CCM is closed, and the connectivity detection state corresponding to the first MEP saved by itself is connected. The value is set to off;

Or,

The first CCM that is encapsulated is sent to the other MEPs in the MD where the first MEP is located by using the communication interface 53 by triggering the continuous transmission, and the other MEPs in the MD where the first MEP is located receive the first The first CCM sent by the MEP, the other MEPs in the MD in which the first MEP is located, according to the status information of the first MEP in the first CCM, the first MEP corresponding to the first MEP is set to the connectivity detection state, and the waiting aging time is turned off. Set to wait for the switching time in the status information of the first CCM. If the third connectivity detection packet of the first MEP update is not received after the handover time is expired, the waiting for aging time is reset.

Optionally, the management status in the status information includes: shutdown, deletion, and active/standby switchover of the device where the first MEP is located.

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

The processor 51 is further configured to encapsulate the re-set state information to the first CCM.

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

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

The first MEP of the embodiment of the present invention, when the state information of the first MEP is changed, triggers the continuous transmission of the encapsulated state information group by changing the corresponding state value in the state information, and triggering the state information after the state is changed by the package. The broadcast is sent to the other MEPs in the MD or the MA where the first MEP is located, so that the MDs in which the first MEP is located or other MEPs in the MA perform corresponding operations according to the status information of the first MEP carried by the first CCM, thereby The response time of the system is saved, and the MEP can actively notify the other MEPs in the same maintenance domain of the current status information, and cause the other MEPs to process the status information corresponding to the first MEP. MEPs can proactively report their current functional support capabilities and corresponding resource availability, improving system response efficiency. If the link between the first MEP and the other MEPs in the maintenance alliance where the first MEP is located is not faulty, the other MEPs in the maintenance alliance where the first MEP is located may be distinguished in time. Know these two kinds of faults and deal with them accordingly. For example, because only the first MEP itself has a special operation, and the link between the device where the first MEP is located and other devices is not faulty, the data service associated with the first MEP does not need to be switched. The state information of the first MEPs 4 and 5 mentioned in the embodiment of the present invention may be carried by the Capabiity TLV in the CCM. The specific manner of carrying the status information of the MEP in the Capabi Tal in the CCM may refer to the foregoing method embodiment. Description of the drawings, Figures 1-4 and their corresponding descriptions.

Through the description of the above embodiments, it will be apparent to those skilled in the art that the present invention can be implemented in hardware, firmware implementation, or a combination thereof. When implemented in software, the functions described above may be stored in or transmitted 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 location to another. A storage medium may be any available media that can be accessed by a computer. By way of example and not limitation, the computer readable medium can comprise RAM, ROM, EEPROM, CD-ROM or other optical disk storage, disk storage media or other magnetic storage device, or can be used to carry or store an instruction or data structure. The desired program code and any other medium that can be accessed by the computer. Also. Any connection may suitably be a computer readable medium. For example, if the software is transmitted from a website, server, or other remote source using coaxial cable, fiber optic cable, twisted pair, digital subscriber line (DSL), or wireless technologies such as infrared, radio, and microwave, then the coaxial cable , fiber optic cable, twisted pair, DSL, or wireless technologies such as infrared, wireless, and microwaves are included in the fixing of the associated media. As used in the present invention, a disc (di sk) and a disc (di sc) include a compact disc (CD), a laser disc, a disc, a digital versatile disc (DVD), a floppy disk, and a Blu-ray disc, wherein the disc is usually magnetically copied, The disc uses a laser to optically replicate the data. Combinations of the above should also be included within the scope of the computer readable media.

In summary, the above description is only a preferred embodiment of the technical solution of the present invention, and is not intended to limit the scope of the present invention. Any modifications, equivalent substitutions, improvements, etc., made within the spirit and scope of the invention are intended to be included within the scope of the invention.

Claims

Rights request

1. A method of inter-node status notification, characterized in that it includes: when the status information of the first node changes, encapsulating the changed status information of the first node into a first notification message, and The first notification message is sent to other nodes; the status information of the first node includes: one of the management status of the first node, the functional type supported, and the resource information corresponding to supporting the functional type, or Various.

2. The method according to claim 1, characterized in that the first node is a maintenance alliance end point MEP.

3. The method according to claim 2, characterized in that: when the status information of the first MEP changes, the changed status information of the first MEP is encapsulated into the first CCM, and The first CCM is sent to the other MEP, including: when the management status in the status information of the first MEP changes, encapsulating the changed management status to the first CCM; The first CCM is sent to the other MEP.

4. The method according to claim 3, characterized in that, before the MEP management status in the status information of the first MEP is changed, the method includes: when the first MEP is in a normal state, the first MEP obtains manage the status value in the status information of the first MEP, and encapsulate the obtained status information when the first MEP is in the normal state to the second CCM; send the second CCM to the other MEP.

5. The method according to claim 3, characterized in that when the first MEP is in a normal state, the value of the management status in the status information of the first MEP is set to 0, and the management of the first MEP The status change includes: when the first MEP is deleted by the management device, the value of the management status in the status information of the first MEP changes from 0 to 1; or when the first MEP is shut down by the management device, the The value of the management status in the status information of the first MEP changes from 0 to 1; Or, when the management device where the first MEP is located undergoes active/standby switching, the value of the management status in the status information of the first MEP changes from 0 to 1.

6. The method according to claim 3 or 5, wherein the sending the encapsulated first CCM to the other MEPs includes: sending the first CCM to the other MEPs by triggering continuous sending. Describe other MEPs.

7. The method according to any one of claims 2, wherein the management status in the status information of the first MEP includes: shutdown, deletion, and active/standby switching of the device where the first MEP is located.

8. The method according to claim 2, characterized in that: when the status information of the first MEP changes, the changed status information of the first MEP is encapsulated into the first CCM, and The first CCM is sent to the other MEP, including: when the function of the first MEP and/or the resources corresponding to the function are changed, the function type and corresponding function type supported in the status information of the first MEP are changed. Reset the value corresponding to the resource information that supports the function; Encapsulate the reset status information to the first CCM; Send the first CCM to the other MEP.

9. The method according to any one of claims 2 to 8, characterized in that the other MEP and the first MEP are located in the same maintenance alliance MA.

10. The method according to any one of claims 2 to 9, characterized in that the first CCM includes a Capability TLV, and the Capability TLV is used to carry status information of the first MEP.

1 1. The method according to claim 10, characterized in that the Capability TLV further includes a SubTLV, and the SubTLV is used to carry the management status, supported function types in the status information of the first MEP, and Corresponds to one or more types of resource information supporting the functional type.

12. A first maintenance alliance endpoint MEP, characterized by including an acquisition unit and a sending unit, where:

The obtaining unit is used to obtain the status information of the first MEP. The status of the first MEP The information includes: one or more of the management status of the first MEP, supported function types, and resource information corresponding to supporting the functional types; the sending unit, used to receive the status information of the first MEP When a change occurs, the changed status information of the first MEP is encapsulated into a first connectivity detection message CCM, and the first CCM is sent to other MEPs.

13. The first MEP according to claim 12, characterized in that the sending unit includes: an encapsulation subunit, configured to encapsulate the changed management status in the status information of the first MEP when the management status changes. The management status is encapsulated into the first CCM; and a sending subunit is used to send the encapsulated first CCM to the other MEPs.

14. The first MEP according to claim 13, wherein the encapsulation subunit is further configured to, before the management status in the status information of the first MEP changes, when the first MEP is in a normal state When the first MEP is in the normal state, the first MEP obtains the management status value in the status information of the first MEP, and encapsulates the status information when the first MEP is in the normal state to the second CCM; the sending subunit also Used to send the second CCM to the other MEP according to the request.

15. The first MEP according to claim 13, wherein when the first MEP is in a normal state, the value of the management status in the current status information of the first MEP is set to 0, and the first MEP is in a normal state. The management status change of the MEP includes: when the first MEP is deleted by the management device, the value of the management status in the status information of the first MEP changes from 0 to 1; or when the first MEP is shut down by the management device When, the value of the management status in the status information of the first MEP changes from 0 to 1; or, when the management device where the first MEP is located undergoes a master-standby switchover, the value of the management status in the status information of the first MEP changes from 0 to 1; The value of the management status changes from 0 to 1.

16. The first MEP according to claim 13 or 15, characterized in that the sending subunit is specifically used for: Send the first CCM to the other MEP.

17. The first MEP according to any one of claims 12 to 16, wherein the management status in the status information of the first MEP includes: shutdown, deletion, and primary and backup of the device where the first MEP is located. switch.

18. The first MEP according to claim 12, characterized in that the sending unit further includes: a setting subunit, used when the function of the first MEP and/or the resources corresponding to the function are changed. , reset the value corresponding to the function type supported in the status information of the first MEP and the corresponding resource information supporting the function; the encapsulation subunit is also used to encapsulate the reset status information into The first CCM; the sending subunit is also used to send the first CCM to the other MEP by triggering continuous sending.

19. The first MEP according to any one of claims 12 to 18, characterized in that the other MEP and the first MEP are located in the same maintenance alliance MA.

20. The first MEP according to any one of claims 12-19, characterized in that, the first

The CCM includes a Capability TLV, which is used to carry status information of the first MEP.

21. The first MEP according to claim 20, wherein the Capability TLV further includes a SubTLV, and the SubTLV is used to carry the management status and supported function types in the status information of the first MEP. and one or more types of resource information corresponding to supporting the functional type.