WO2021233202A1

WO2021233202A1 - Method for creating maintenance entity group intermediate point, node, and readable storage medium

Info

Publication number: WO2021233202A1
Application number: PCT/CN2021/093648
Authority: WO
Inventors: 宋国伟
Original assignee: 中兴通讯股份有限公司
Priority date: 2020-05-20
Filing date: 2021-05-13
Publication date: 2021-11-25
Also published as: CN113709049A

Abstract

A method for creating a maintenance entity group intermediate point, a node, and a readable storage medium. The method for creating a maintenance entity group intermediate point comprises: a first node sends to a second node a function trigger message carrying first information expressing a request for the creation of a maintenance entity group intermediate point (MIP), so that the second node creates the MIP according to the first information (S100).

Description

Method for creating intermediate point of maintenance entity group, node and readable storage medium

Cross-references to related applications

This application is based on a Chinese patent application with an application number of 202010428505.3 and an application date of May 20, 2020, and claims the priority of the Chinese patent application. The entire content of the Chinese patent application is hereby incorporated by reference into this application.

Technical field

The embodiments of the present invention relate to, but are not limited to, the field of communication technology, and in particular to a method for creating an intermediate point of a maintenance entity group, a node, and a computer-readable storage medium.

Background technique

Ethernet operation and maintenance management (Operation Administration and Maintenance, OAM) technology is an OAM mechanism applied in Ethernet, mainly through Ethernet in the First Mile (EFM) and Connectivity Fault Management (CFM) ) Perform operation, management and maintenance functions on the network. Among them, Loop Back (LB) and Link Trace (LT) are important functions of CFM. LB can be used to check the connectivity between a maintenance entity group boundary point (MEG End Point, MEP) and a maintenance entity group intermediate point (MEG Intermediate Point, MIP) or equivalent MEP; LT can track the transmission link Message (Link Trace Message, LTM) to view the end-to-end routing path.

In some cases, when using CFM to diagnose the fault of an intermediate node, it is usually necessary to deploy MIP on the intermediate node. After the MIP is deployed on the intermediate node, perform LB and LT to diagnose the fault of the intermediate node. That is, to perform fault diagnosis on the intermediate node, the creation of the MIP is necessary, but in some cases, the creation of the MIP can only be performed manually. In the case of complex network topology, if you need to manually create MIPs every time you execute LB and LT on intermediate nodes, it will inevitably waste a lot of time, especially for development, testing, engineering maintenance, etc. personnel, which will particularly affect efficiency .

Summary of the invention

The following is an overview of the topics detailed in this article. This summary is not intended to limit the scope of protection of the claims.

The embodiment of the present invention provides a method for creating an intermediate point of a maintenance entity group, a node, and a computer-readable storage medium, which can reduce the burden of manually creating a MIP, thereby improving the efficiency of creating a MIP.

In a first aspect, an embodiment of the present invention provides a method for creating an intermediate point of a maintenance entity group, which includes: a first node sends a function trigger message carrying first information for requesting to create an intermediate point MIP of a maintenance entity group to a second node. Text, so that the second node creates a MIP according to the first information.

In a second aspect, an embodiment of the present invention also provides a method for creating an intermediate point of a maintenance entity group, which includes: a second node receives a function trigger message sent by a first node, and the function trigger message carries a message for requesting creation. The first information of the MIP; the second node creates the MIP according to the first information.

In the third aspect, embodiments of the present invention also provide a node, including: a memory, a processor, and a computer program stored in the memory and capable of running on the processor. The processor executes the computer program as described above. The method for creating an intermediate point of a maintenance entity group in the first aspect or the method for creating an intermediate point of a maintenance entity group in the second aspect is implemented.

In a fourth aspect, an embodiment of the present invention also provides a computer-readable storage medium that stores computer-executable instructions, and the computer-executable instructions are used to execute the method for creating an intermediate point of a maintenance entity group as described above.

Other features and advantages of the present invention will be described in the following description, and partly become obvious from the description, or understood by implementing the present invention. The purpose and other advantages of the present invention can be realized and obtained through the structures specifically pointed out in the specification, claims and drawings.

Description of the drawings

The accompanying drawings are used to provide a further understanding of the technical solution of the present invention, and constitute a part of the specification. Together with the embodiments of the present invention, they are used to explain the technical solution of the present invention, and do not constitute a limitation to the technical solution of the present invention.

FIG. 1 is a schematic diagram of a network topology for executing a method for creating an intermediate point of a maintenance entity group according to an embodiment of the present invention;

2 is a flowchart of a method for creating an intermediate point of a maintenance entity group according to an embodiment of the present invention;

FIG. 3 is a schematic diagram of the structure of a special LTM message provided by an embodiment of the present invention;

4 is a flowchart of a method for creating an intermediate point of a maintenance entity group according to another embodiment of the present invention;

FIG. 5 is a schematic diagram of the structure of a special LTR message provided by an embodiment of the present invention;

6 is a flowchart of a method for creating an intermediate point of a maintenance entity group according to another embodiment of the present invention;

FIG. 7 is a flowchart of a method for creating an intermediate point of a maintenance entity group according to another embodiment of the present invention;

FIG. 8 is a flowchart of a method for creating an intermediate point of a maintenance entity group according to another embodiment of the present invention;

FIG. 9 is a flowchart of a method for creating an intermediate point of a maintenance entity group according to another embodiment of the present invention;

Fig. 10 is a schematic diagram of a node provided by an embodiment of the present invention.

Detailed ways

In order to make the objectives, technical solutions, and advantages of the present invention clearer, the following further describes the present invention in detail with reference to the accompanying drawings and embodiments. It should be understood that the specific embodiments described here are only used to explain the present invention, but not used to limit the present invention.

It should be noted that although functional modules are divided in the schematic diagram of the device, and the logical sequence is shown in the flowchart, in some cases, it can be performed in a different order from the module division in the device or in the sequence of the flowchart. Steps shown or described. The terms "first", "second", etc. in the specification and claims and the above-mentioned drawings are used to distinguish similar objects, and not necessarily used to describe a specific sequence or sequence.

The embodiment of the present invention provides a method for creating an intermediate point of a maintenance entity group, a node, and a computer-readable storage medium. When the LT function or the LB function is executed, the first node sends a function trigger message to the second node, and the The function trigger message carries the first information used to indicate that the MIP is requested to be created. Therefore, in the case that the second node receives the function trigger message sent by the first node, the second node can trigger the message according to the function. MIP is automatically created based on the first information, thereby reducing the burden of manually creating MIPs and improving the efficiency of creating MIPs.

The embodiments of the present invention will be further described below in conjunction with the accompanying drawings.

As shown in FIG. 1, FIG. 1 is a schematic diagram of a network topology for executing a method for creating an intermediate point of a maintenance entity group according to an embodiment of the present invention. In the example of FIG. 1, the network topology includes a first node 100, a second node 200, and a third node 300, where the first node 100, the second node 200, and the third node 300 can all support Ethernet services.

The first node 100 is provided with an out port, the second node 200 is provided with an ingress port and an egress port, the third node 300 is provided with an ingress port, the egress port of the first node 100 is connected to the ingress port of the second node 200, and the second node The outgoing port of 200 is connected to the incoming port of the third node 300.

A set of peer-to-peer MEPs can be established between the first node 100 and the third node 300. When the LT function or the LB function needs to be executed, the MIP can be created in the second node 200. Create MIPs for ingress and egress ports.

The first node 100, the second node 200, and the third node 300 may respectively include a memory and a processor, where the memory and the processor may be connected by a bus or in other ways.

As a non-transitory computer-readable storage medium, the memory can be used to store non-transitory software programs and non-transitory computer-executable programs. In addition, the memory may include a high-speed random access memory, and may also include a non-transitory memory, such as at least one magnetic disk storage device, a flash memory device, or other non-transitory solid-state storage devices. In some implementations, the memory may include a memory remotely provided with respect to the processor, and these remote memories may be connected to the processor through a network. Examples of the aforementioned networks include, but are not limited to, the Internet, corporate intranets, local area networks, mobile communication networks, and combinations thereof.

The network topology and application scenarios described in the embodiments of the present invention are to illustrate the technical solutions of the embodiments of the present invention more clearly, and do not constitute a limitation on the technical solutions provided by the embodiments of the present invention. Those skilled in the art will know that with the network topology With the evolution of and the emergence of new application scenarios, the technical solutions provided in the embodiments of the present invention are equally applicable to similar technical problems.

Those skilled in the art can understand that the topology shown in FIG. 1 does not constitute a limitation to the embodiment of the present invention, and may include more or less components than those shown in the figure, or a combination of certain components, or different components. Layout.

In the network topology shown in FIG. 1, each node can respectively call its stored maintenance entity group intermediate point creation program to execute the maintenance entity group intermediate point creation method.

Based on the above-mentioned network topology structure, various embodiments of the method for creating an intermediate point of a maintenance entity group of the present invention are proposed.

As shown in FIG. 2, FIG. 2 is a flowchart of a method for creating an intermediate point of a maintenance entity group according to an embodiment of the present invention. The method for creating an intermediate point of a maintenance entity group includes but is not limited to step S100.

Step S100: The first node sends to the second node a function trigger message carrying first information for requesting to create a MIP, so that the second node creates a MIP according to the first information.

In an embodiment, the function trigger message may be a special LTM message suitable for performing the LT function, or a special loopback message (Loopback Message, LBM) message suitable for performing the LB function. It is worth noting that, regardless of whether the function trigger message is a special LTM message or a special LBM message, it will carry the first information used to indicate a request to create a MIP.

It is worth noting that the special LTM message and the special LBM message are only different in message format and application scenarios, but the two kinds of messages are used to trigger the function of creating MIP and the fields needed to realize the function of creating MIP The information and other contents are the same. In order to avoid excessive repetition and redundancy of the contents of the manual, and to explain the specific contents of this embodiment more clearly, the following takes the application scenario of automatically creating MIP when the LT function is executed as an example for explanation. For the relevant explanations of the application scenarios of automatically creating MIPs when the LB function is executed, you can refer to the explanations of the application scenarios of automatically creating MIPs when executing the LT function.

In an embodiment, it is assumed that a set of peer MEPs is established between the first node and the third node, and when the LT function is executed, the MIP needs to be created on the second node between the first node and the third node , Then, in the case that the second node receives the special LTM message sent by the first node, since the special LTM message carries the first information used to indicate the request to create the MIP, the second node can The MIP is created under the trigger of information, that is, the second node can automatically create the MIP according to the first information in the special LTM message, thereby reducing the burden of manually creating the MIP and improving the efficiency of creating the MIP. It is worth noting that the first node and the second node may be located in the same network device, or may be located in different network devices, which is not specifically limited in this embodiment.

In an embodiment, since the special LTM message carrying the first information for requesting the creation of the MIP was created by the first node, the first node may have a regular LTM message and a special LTM message. Text (that is, the function trigger message in this embodiment). The first node can be configured with an enable switch for requesting the creation of a MIP. When the second node needs to be requested to create a MIP, the first node can turn on the enable switch, and when the enable switch is on, the first node The second node will send a special LTM message carrying the first information for requesting the creation of a MIP; when there is no need to create a MIP, the enable switch will be turned off. At this time, the first node will execute In the case of the LT function, a regular LTM message is sent to the second node.

Those skilled in the art can understand that conventional LTM messages are messages that need to be used when performing LT functions in some situations. When performing LT functions, you can send regular LTM messages to view the end-to-end information between nodes. Routing path.

In an embodiment, the special LTM message may be improved on the basis of the conventional LTM message. For example, a new field structure may be extended in the conventional LTM message to carry the first information used to indicate a request to create a MIP. It is also possible to redefine the field structure in the conventional LTM message to carry the first information used to indicate the request to create the MIP, which is not specifically limited in this embodiment. To illustrate with a specific example, referring to FIG. 3, FIG. 3 is a schematic diagram of the structure of a special LTM message provided by an embodiment. The structure of the special LTM message includes an Ethernet message header and LTM message content. , The explanation of each main field of the message structure is as follows:

DMAC: used to indicate the destination address, encapsulated in the Ethernet message header, the specific value is different from the regular LTM message, for example, the value range of the DMAC field of the regular LTM message is 01-80-C2-00-00 -38 to 01-80-C2-00-00-3F, and in this embodiment, the value of the DMAC field of the special LTM message is 01-80-C2-00-00-40;

SMAC: used to indicate the source address, encapsulated in the Ethernet packet header;

Type: used to indicate the type;

MD level: used to indicate the level of the maintenance domain;

OpCode: used to indicate the message code, when the message is an LTM message, the value is 0x05;

Original MAC: used to indicate the address of the source node performing the LT function, that is, the address of the node where the local MEP is located;

Target MAC: used to indicate the address of the target node performing the LT function, that is, the address of the node where the opposite MEP is located;

Additional LTM TLVs: used to indicate additional TLV fields, and different TLV contents can be added according to the actual situation.

It is worth noting that the explanation of other fields in the structure of the special LTM message is the same as the explanation of the corresponding fields included in the conventional LTM message, so it will not be repeated here.

In an embodiment, in the case of the special LTM message structure shown in FIG. 3, the first information that is carried in the special LTM message and used to indicate a request to create a MIP can be stored in the DMAC field, and It is a special value, for example, the value is 01-80-C2-00-00-40, which is used to indicate that the LTM message is a special LTM message and is used to indicate a request to create a MIP. For example, when the second node obtains a special LTM message sent by the first node, and the DMAC field obtained by the second node by parsing the special LTM message has a value of 01-80-C2-00-00-40 , It means that the first node requests to create a MIP. At this time, if the address information of the Target MAC field in the special LTM message is not the address of the second node, it means that the second node is an intermediate node between a group of peer MEPs Therefore, the second node will automatically create a MIP based on the first information, which can reduce the burden of manually creating a MIP and improve the efficiency of creating a MIP. It is worth noting that the first information used to indicate the request to create the MIP can also be stored in the Additional LTM TLVs field in the format of TLV, which is not specifically limited in this embodiment.

In an embodiment, the function trigger message also carries at least information such as level parameters and virtual local area network parameters used to create the MIP. For example, the level parameter can be stored in the above MD level field, and the virtual local area network parameter can be stored in the Ethernet packet header. When the second node receives the function trigger message sent by the first node, the second node can automatically create a MIP based on the level parameter and virtual local area network parameters in the function trigger message, thereby reducing the burden of manually creating MIP. Improve the efficiency of creating MIP.

In addition, referring to FIG. 4, in an embodiment, after step S100, the method for creating an intermediate point of the maintenance entity group further includes the following steps:

Step S200: The first node receives a function response message from the second node within a preset time period;

Step S300: When the function response message carries the second information indicating that the MIP is successfully created, the first node caches the second information.

In an embodiment, the function response message may be a Link Trace Reply (LTR) message suitable for performing the LT function, or may be a Loopback Reply (LBR) suitable for performing the LB function. Message. It is worth noting that the function response message that carries the second information to indicate the successful creation of the MIP is a special message that is different from the regular LTR message or the regular LBR message. When the function response message carries the message to indicate success When creating the second message of the MIP, the function response message can be a special LTR message or a special LBR message.

It is worth noting that the special LTR message and the special LBR message are only different in message format and application scenarios, but the two kinds of messages are used to trigger the function of creating MIP and the fields needed to realize the function of creating MIP The information and other contents are the same. In order to avoid excessive repetition and redundancy of the contents of the manual, and to explain the specific contents of this embodiment more clearly, the following takes the application scenario of automatically creating MIP when the LT function is executed as an example for explanation. For the relevant explanations of the application scenarios of automatically creating MIPs when the LB function is executed, you can refer to the explanations of the application scenarios of automatically creating MIPs when executing the LT function.

In an embodiment, when the first node sends a special LTM message to the second node so that the second node creates an MIP based on the first information in the special LTM message, the second node will reply to the first node with the special LTR message. When the special LTR message meets the aging condition, that is, when the first node receives the special LTR message within the preset time period, the first node can determine that the special LTR message is valid. , The first node will parse the special LTR message. When the special LTR message carries the second information indicating that the MIP is successfully created, it means that the second node has successfully created the MIP. At this time, the first node can Cache the second information in the received special LTR message, or directly report the second information in the special LTR message to the network manager. After the first node receives the special LTR message, the first node may not report the second information in the special LTR message to the network manager, but wait for all intermediate nodes between the receiving and the opposite MEP to complete Special LTR messages sent for the creation of MIP, when the first node receives the special LTR messages replies from all intermediate nodes that created the MIP, the first node then reports the second information in these special LTR messages to Network manager. In addition, the first node may also report the second information of the special LTR message to the network manager every time it receives a special LTR message, which is not specifically limited in this embodiment.

It is worth noting that the preset time period can be appropriately selected according to actual application needs, and this embodiment does not specifically limit it. When the function response message does not meet the aging condition, the first node will determine that the function response message is invalid. At this time, the first node may discard the function response message and wait to receive the next function response message.

In one embodiment, when the function response message carries the second information indicating that the MIP is successfully created, after the first node reports the second information in the function response message to the network manager, the network manager can The information content related to the creation of the MIP carried in the second information is stored, such as the node that created the MIP, the address of the node that created the MIP, and so on. Therefore, the network manager can know whether each intermediate node has successfully created the MIP, and can also obtain the relevant information of the intermediate nodes in the entire maintenance domain, which can facilitate the network manager's management of the entire maintenance domain.

In an embodiment, for example, when the LT function is executed, since the function response message carrying the second information indicating that the MIP is successfully created is a special LTR message created by the second node, the second node can establish There are regular LTR messages and special LTR messages. When the second node receives the regular LTM message sent by the first node, the second node will reply with a regular LTR message according to the regular LTM message; and when the second node receives the special LTM message sent by the first node When sending a message, the second node will reply a special LTR message according to the special LTM message.

Those skilled in the art can understand that a conventional LTR message is a message that needs to be used when performing the LT function in some situations. When the LT function is performed, it can be used to view the end-to-end routing between nodes when received. After the regular LTM message of the path, a regular LTR message is returned.

In an embodiment, the function response message carrying the second information indicating that the MIP is successfully created can be improved on the basis of the existing related message format. For example, a special LTR message may be a regular LTR message. Improved on the basis of the text, for example, you can extend the new field structure in the regular LTR message to carry the second information used to indicate the successful creation of the MIP, or you can redefine the field structure in the regular LTR message to carry The second information used to indicate the successful creation of the MIP is not specifically limited in this embodiment. To illustrate with a specific example, referring to FIG. 5, FIG. 5 is a schematic diagram of the structure of a special LTR message provided by an embodiment. The structure of the special LTR message includes an Ethernet message header and LTR message content. , The explanation of each main field of the message structure is as follows:

DMAC: used to indicate the destination address, encapsulated in the Ethernet packet header;

SMAC: used to indicate the source address, encapsulated in the Ethernet packet header, and its value corresponds to the value of the DMAC field of the special LTM packet in the foregoing embodiment;

Type: used to indicate the type;

MD level: used to indicate the level of the maintenance domain;

OpCode: used to indicate the message code, when the message is an LTR message, the value is 0x04;

Additional LTM TLVs: indicates additional TLV fields, which are used to store the second information related to the creation of MIPs.

It is worth noting that the explanation of other fields in the structure of the special LTR message is the same as the explanation of the corresponding fields included in the LTR message in some situations, so it will not be repeated here.

In an embodiment, the first node may determine whether the current LTR message is a special LTR message carrying the second information related to the creation of MIP through the value of the SMAC field, or may identify the value in the Additional LTM TLVs field. Whether the content is related to the creation of the MIP and determining whether the current LTR message is a special LTR message carrying the second information related to the creation of the MIP is not specifically limited in this embodiment.

In addition, in an embodiment, the method for creating an intermediate point of the maintenance entity group further includes the following steps:

Step S400: When the function response message does not carry the second information for indicating that the MIP is successfully created, the first node reports the cached second information to the network manager.

In an embodiment, in the case that the first node caches the second information carried in the function response message to indicate the successful creation of the MIP, if the first node receives a message that does not carry the second information used to indicate the successful creation of the MIP A function response message for the second information. For example, if the first node receives an LTR message that does not carry the second information, it means that the LTR message is a regular LTR message, and the regular LTR message comes from the pairing of the first node. The end MEP, at this time, indicates that the function trigger message sent by the first node has been forwarded to the opposite MEP, and the intermediate nodes have completed the creation of the MIP. Therefore, the first node will report the cached second information To the network manager, for example, the information such as the node that created the MIP and the address of the node that created the MIP are reported to the network manager, so that you can learn through the network manager whether each intermediate node has successfully created the MIP, and can also pass The network manager obtains the relevant information of the intermediate nodes in the entire maintenance domain, which is convenient for the network manager to manage the entire maintenance domain.

In addition, in an embodiment, the second information includes location information of the node that created the MIP and flag information used to indicate the success or failure of the MIP creation.

In an embodiment, the location information of the node that created the MIP and the flag information used to indicate the success or failure of the MIP creation can be configured in the message structure of the function response message, for example, as shown in FIG. 5 In the embodiment, in the Additional LTM TLVs field of the special LTR message structure. Wherein, the location information of the node that creates the MIP may include at least one of the network element name, rack number, sub-rack number, slot number, and other information, which is not specifically limited in this embodiment. In addition, the flag information used to indicate the success or failure of the MIP creation can be a single identification information used to indicate whether the node's inbound port successfully created the MIP, or it may be a single identification information used to indicate whether the node's outbound port successfully created the MIP, and It may include multiple pieces of identification information used to indicate whether the ingress port and egress port of the node successfully create the MIP, which is not specifically limited in this embodiment. When the first node reports the positioning information and the flag information to the network manager, the network manager can learn whether each intermediate node has successfully created the MIP, and can also obtain the intermediate nodes in the entire maintenance domain through the network manager , Which can facilitate the management of the entire maintenance domain by the network manager.

In addition, another embodiment of the present invention also provides a method for creating an intermediate point of a maintenance entity group, as shown in FIG. 6, which is a flowchart of a method for creating an intermediate point of a maintenance entity group according to another embodiment of the present invention. The method for creating the intermediate point of the maintenance entity group includes but is not limited to the following steps:

Step S510: The second node receives a function trigger message sent by the first node, where the function trigger message carries first information used to indicate a request to create a MIP;

Step S520, the second node creates a MIP according to the first information.

In an embodiment, the function trigger message may be a special LTM message suitable for performing the LT function, or a special LBM message suitable for performing the LB function. It is worth noting that, regardless of whether the function trigger message is a special LTM message or a special LBM message, it will carry the first information used to indicate a request to create a MIP.

In an embodiment, it is assumed that a set of peer-to-peer MEPs is established between the first node and the third node, and when the LT function is executed, the MIP needs to be created on the second node between the first node and the third node. , Then, in the case that the second node receives the special LTM message sent by the first node, since the special LTM message carries the first information used to indicate the request to create the MIP, the second node can The MIP is created under the trigger of information, that is, the second node can automatically create the MIP according to the first information in the special LTM message, thereby reducing the burden of manually creating the MIP and improving the efficiency of creating the MIP.

In an embodiment, the function trigger message that carries the first information for requesting to create a MIP can be improved on the basis of the existing related message format. For example, a special LTM message can be a regular LTM message. Improved on the basis of the text, for example, you can extend a new field structure in a conventional LTM message to carry the first information used to indicate a request to create a MIP, or you can redefine the field structure in a conventional LTM message to carry The first information used to indicate the request to create the MIP is not specifically limited in this embodiment.

It is worth noting that the specific structure and specific meaning of the special LTM message in this embodiment are consistent with the specific structure and specific meaning of the special LTM message in the embodiment shown in FIG. For the explanation of the specific structure and specific meaning of the special LTM message, please refer to the relevant explanation of the specific structure and specific meaning of the special LTM message in the embodiment shown in FIG. 3, which will not be repeated here.

Step S530: Determine the outgoing port and forward the function trigger message.

In an embodiment, when the second node receives the function trigger message sent by the first node, the second node will first determine whether the content of the function trigger message carries the address of the second node, for example, determine a special LTM Whether the content of the Target MAC field in the message is the address of the second node, if the content of the Target MAC field is not the address of the second node, it means that the second node is an intermediate node between a group of peer MEPs. Therefore, the first The second node will create the MIP according to the first information contained in the function trigger message to indicate the request to create the MIP, and when the creation of the MIP is completed, the second node will also determine the port and forward the function to the next node Trigger messages, so that the function trigger messages can flow through all intermediate nodes between peer MEPs, so that all intermediate nodes can create MIPs according to the first information in the function trigger message.

It is worth noting that when the first node sends a function trigger message to the opposite MEP, if the intermediate node or the opposite MEP receives the function trigger message, it will reply to the first node with a function response message, if When the intermediate node receives the function response message, the intermediate node will determine the port and forward the function response message, and will not perform related processing according to the function response message, that is, the intermediate node transparently transmits the function response message.

In addition, it is worth noting that if the peer MEP (for example, the third node in the embodiment shown in FIG. 1) receives the function trigger message sent by the first node, the peer MEP will first determine that the function trigger message is If the content of the Target MAC field is the address of the current node, if the content of the Target MAC field is the address of the current node, the opposite MEP will first determine whether there is a MEP corresponding to the function trigger message on the corresponding flow point. , It means that the current node is the target node to which the function trigger message needs to be transmitted. At this time, the opposite MEP will reply to the first node a function response message that does not carry the second information related to the creation of the MIP, and stop forwarding This function triggers a message. In addition, if the opposite end MEP determines that there is no MEP corresponding to the function trigger message on the corresponding flow point, the opposite end MEP will directly discard the function trigger message.

In an embodiment, the function trigger message also carries at least information such as level parameters and virtual local area network parameters used to create the MIP. For example, the level parameter may be stored in the MD level field in the special LTM message structure of the embodiment shown in FIG. 3, and the virtual local area network parameters may be stored in the special LTM message structure of the embodiment shown in FIG. 3 In the Ethernet packet header. When the second node receives the function trigger message sent by the first node, the second node can automatically create a MIP based on the level parameter and virtual local area network parameters in the function trigger message, thereby reducing the burden of manually creating MIP. Improve the efficiency of creating MIP.

In addition, referring to FIG. 7, in an embodiment, step S520 includes but is not limited to the following steps:

Step S521, the second node triggers the level parameter and the virtual local area network parameter in the message according to the first information acquisition function;

In step S522, the second node creates an MIP on the ingress port and egress port of the second node respectively according to the level parameter and the virtual local area network parameter.

In an embodiment, after the second node receives the function trigger message sent by the first node, the second node will first determine whether the function trigger message carries the first information used to indicate the request to create a MIP. If the trigger message carries the first information, the second node will parse and obtain the level parameters and virtual local area network parameters in the function trigger message, and according to the level parameters and virtual local area network parameters, the ingress and egress ports of the second node MIP is created automatically. It is worth noting that the outgoing port of the MIP created in the second node can be obtained according to information such as the Media Access Control Address (MAC) table in the second node.

In addition, in an embodiment, when the second node separately creates MIPs on its ingress port and egress port, if the corresponding MIP already exists, the second node does not perform a specific creation operation and is deemed to have been successfully created.

Step S540: The second node sends to the first node a function response message carrying the second information indicating that the MIP is successfully created, so that the first node caches the second information or reports the second information to the network manager.

In an embodiment, the function response message may be an LTR message suitable for performing the LT function, or may be an LBR message suitable for performing the LB function. It is worth noting that the function response message that carries the second information to indicate the successful creation of the MIP is a special message that is different from the regular LTR message or the regular LBR message. When the function response message carries the message to indicate success When creating the second message of the MIP, the function response message can be a special LTR message or a special LBR message.

In one embodiment, after the second node creates the MIP according to the function trigger message sent by the first node, the second node will reply to the first node with a function response message, and when the first node receives the function response message After the text, the first node will parse the function response message. If the function response message carries the second information indicating that the MIP is successfully created, it means that the second node has successfully created the MIP. At this time, the first The node may buffer the second information in the received function response message, or directly report the second information in the function response message to the network manager.

In an embodiment, the function response message carrying the second information indicating that the MIP is successfully created can be improved on the basis of the existing related message format. For example, a special LTR message may be a regular LTR message. Improved on the basis of the text, for example, you can extend the new field structure in the regular LTR message to carry the second information used to indicate the successful creation of the MIP, or you can redefine the field structure in the regular LTR message to carry The second information used to indicate the successful creation of the MIP is not specifically limited in this embodiment.

It is worth noting that the specific structure and specific meaning of the special LTR message in this embodiment are consistent with the specific structure and specific meaning of the special LTR message in the embodiment shown in FIG. For the explanation of the specific structure and specific meaning of the special LTR message, please refer to the relevant explanation of the specific structure and specific meaning of the special LTR message in the embodiment shown in FIG. 5, which will not be repeated here.

Regarding the method for creating the intermediate point of the maintenance entity group provided by the foregoing embodiments, the following is a detailed description with a specific example:

Example 1:

Referring to FIG. 8, FIG. 8 is a flowchart of a method for creating an intermediate point of a maintenance entity group applied to a network topology. The network topology includes a first node 100, a second node 200, a third node 300, and a fourth node 400, wherein , The first node 100, the second node 200, the third node 300, and the fourth node 400 can all support Ethernet services. The first node 100 and the fourth node 400 create a set of peer MEPs, and the second node 200 and the third node 300 are both intermediate nodes between the set of peer MEPs. When it needs to be in the maintenance domain of the first node 100 When performing the LB function or the LT function, MIPs need to be created on the second node 200 and the third node 300.

When the LT function needs to be executed, the first node 100 sends a special LTM message to the fourth node 400 (the content of the DMAC field in the message is 01-80-C2-00-40, and the content of other fields is the same as the regular LTM message Same), the special LTM message will be transmitted to the second node 200 first. After the second node 200 determines that the special LTM message conforms to the rule, the second node 200 determines that the content of the DMAC field of the special LTM message is 01-80-C2-00-40, the second node 200 will parse and obtain information such as level parameters and virtual local area network parameters in the special LTM message, and create a MIP on the ingress port and egress port of the second node 200 respectively After the creation of the MIP is completed, the second node 200 will reply to the first node 100 a special LTR message that carries the network element name, rack number, subrack number, slot number, and It indicates whether the ingress port and egress port of the second node 200 have successfully created the MIP flag information, etc. Then, the second node 200 will determine the egress port for transmitting the special LTM message, and forward the special LTM message through the egress port To the third node 300; when the third node 300 receives the special LTM message forwarded by the second node 200, the third node 300 performs the same processing as the second node 200, and forwards the special LTM message to the fourth node 400 LTM message; when the fourth node 400 receives the special LTM message, the fourth node 400 determines that the content of the Target MAC field in the special LTM message is the MAC address of the fourth node 400, so the fourth node 400 Reply a regular LTR message to the first node 100, and stop forwarding the special LTM message.

When the first node 100 obtains the special LTR messages sent by the second node 200 and the third node 300 within the preset time period, the first node 100 will carry the information of the node that created the MIP carried in the special LTR message. The location information and the flag information used to indicate the success or failure of MIP creation are cached, and when the first node 100 receives the regular LTR message sent by the fourth node 400, the first node 100 will report all the cached information to Network manager.

Example 2:

Referring to FIG. 9, FIG. 9 is a flowchart of a method for creating an intermediate point of a maintenance entity group applied to another network topology, which includes a first node 100, a second node 200, a third node 300, and a fourth node 400, Among them, the first node 100, the second node 200, the third node 300, and the fourth node 400 can all support Ethernet services. The first node 100, the third node 300, and the fourth node 400 create a point-to-multipoint MEP. Specifically, the first node 100 and the third node 300 are a set of peer-to-peer MEPs, and the first node 100 and the fourth node The node 400 is another set of peer-to-peer MEPs, and the second node 200 is an intermediate node between the first node 100 and the third node 300. When it is necessary to perform LB in the maintenance domain where the first node 100 and the third node 300 are located In the case of function or LT function, a MIP needs to be created in the second node 200.

When the LT function needs to be performed, the first node 100 sends a special LTM message to the third node 300 (the content of the DMAC field in the message is 01-80-C2-00-40, and the content of other fields is the same as the regular LTM message Same), the special LTM message will be transmitted to the second node 200 first. When the second node 200 determines that the special LTM message conforms to the rule, the second node 200 determines that the content of the DMAC field of the special LTM message is 01-80-C2-00-40, the second node 200 will parse and obtain information such as level parameters and virtual local area network parameters in the special LTM message, and create a MIP on the ingress port and egress port of the second node 200 respectively After the creation of the MIP is completed, the second node 200 will reply to the first node 100 a special LTR message that carries the network element name, rack number, subrack number, slot number, and It indicates whether the ingress port and egress port of the second node 200 have successfully created the MIP flag information, etc. Then, the second node 200 will determine the egress port for transmitting the special LTM message, and forward the special LTM message through the egress port To the third node 300; when the third node 300 receives the special LTM message, the third node 300 determines that the content of the Target MAC field in the special LTM message is the MAC address of the third node 300, so the third node 300 The node 300 replies a regular LTR message to the first node 100 and stops forwarding the special LTM message.

When the first node 100 obtains the special LTR message sent by the second node 200 within a preset time period, the first node 100 will carry the location information of the node that created the MIP carried in the special LTR message and use it to indicate The flag information indicating the success or failure of MIP creation is cached, and when the first node 100 receives the regular LTR message sent by the third node 300, the first node 100 will report all the cached information to the network manager.

In addition, referring to FIG. 10, an embodiment of the present invention provides a node, which includes a memory 501, a processor 502, and a computer program stored in the memory and running on the processor.

The processor and the memory can be connected by a bus or in other ways.

It should be noted that the node in this embodiment can be applied to the node in the embodiment shown in Figure 1, Figure 8 or Figure 9. The node in this embodiment can form the one shown in Figure 1, Figure 8 or Figure 9. As part of the network topology in the embodiments, these embodiments belong to the same inventive concept. Therefore, these embodiments have the same implementation principles and technical effects, which will not be described in detail here.

The non-transitory software programs and instructions required to implement the method for creating the intermediate point of the maintenance entity group of the foregoing embodiment are stored in the memory. When executed by the processor, the method for creating the intermediate point of the maintenance entity group of the foregoing embodiment is executed, for example, executing The method step S100 in FIG. 2, the method steps S200 to S300 in FIG. 4, the method steps S510 to S520 in FIG. 6, or the method steps S521 to S522 in FIG. 7 are described above.

The device embodiments described above are merely illustrative, and the units described as separate components may or may not be physically separated, that is, they may be located in one place, or they may be distributed on multiple network units. Some or all of the modules can be selected according to actual needs to achieve the objectives of the solutions of the embodiments.

In addition, an embodiment of the present invention also provides a computer-readable storage medium, the computer-readable storage medium stores computer-executable instructions, and the computer-executable instructions are executed by a processor or a controller, for example, by the aforementioned The execution of a processor in the node embodiment can make the above-mentioned processor execute the method for creating the intermediate point of the maintenance entity group in the above-mentioned embodiment, for example, execute the method step S100 in FIG. 2 and the method step S200 in FIG. 4 described above. To S300, the method steps S510 to S520 in FIG. 6 or the method steps S521 to S522 in FIG. 7.

A person of ordinary skill in the art can understand that all or some of the steps and systems in the methods disclosed above can be implemented as software, firmware, hardware, and appropriate combinations thereof. Some physical components or all physical components can be implemented as software executed by a processor, such as a central processing unit, a digital signal processor, or a microprocessor, or as hardware, or as an integrated circuit, such as an application specific integrated circuit . Such software may be distributed on a computer-readable medium, and the computer-readable medium may include a computer storage medium (or a non-transitory medium) and a communication medium (or a transitory medium). As is well known to those of ordinary skill in the art, the term computer storage medium includes volatile and non-volatile data implemented in any method or technology for storing information (such as computer-readable instructions, data structures, program modules, or other data). Sexual, removable and non-removable media. Computer storage media include but are not limited to RAM, ROM, EEPROM, flash memory or other memory technologies, CD-ROM, digital versatile disk (DVD) or other optical disk storage, magnetic cassettes, magnetic tapes, magnetic disk storage or other magnetic storage devices, or Any other medium used to store desired information and that can be accessed by a computer. In addition, as is well known to those of ordinary skill in the art, communication media usually contain computer-readable instructions, data structures, program modules, or other data in a modulated data signal such as carrier waves or other transmission mechanisms, and may include any information delivery media. .

In the embodiment of the present invention, the first node is used to send a function trigger message to the second node, and the function trigger message carries the first information used to indicate the request to create the MIP. Therefore, the second node receives the message from the first node. In the case of the function trigger message sent by the node, the second node can automatically create the MIP according to the first information in the function trigger message, thereby reducing the burden of manually creating the MIP and improving the efficiency of creating the MIP.

The embodiment of the present invention includes: a first node sends a function trigger message carrying first information for requesting creation of a MIP to a second node, so that the second node creates a MIP according to the first information. According to the solution provided by the embodiment of the present invention, when the LT function or the LB function is executed, when the second node receives the function trigger message sent by the first node, since the function trigger message carries a request to create a MIP The first information, therefore, the second node can create MIPs triggered by the first information, that is, the second node can automatically create MIPs based on the first information in the function trigger message, thereby reducing the burden of manually creating MIPs , Improve the efficiency of creating MIP.

The above is a specific description of some implementations of the present invention, but the present invention is not limited to the above-mentioned embodiments. Those skilled in the art can make various equivalent modifications or substitutions without departing from the scope of the present invention. These are equivalent. Variations or replacements of are included within the scope defined by the claims of the present invention.

Claims

A method for creating intermediate points of maintenance entity groups, including:

The first node sends to the second node a function trigger message carrying the first information for requesting the creation and maintenance of the intermediate point MIP of the entity group, so that the second node creates the MIP according to the first information.
The method according to claim 1, wherein the function trigger message also carries level parameters and virtual local area network parameters used to create the MIP.
The method according to claim 1, further comprising:

The first node receives a function response message from the second node within a preset time period;

When the function response message carries the second information used to indicate that the MIP is successfully created, the first node caches the second information.
The method according to claim 3, further comprising:

When the function response message does not carry the second information used to indicate that the MIP is successfully created, the first node reports the cached second information to the network manager.
The method according to claim 3, further comprising:

When the function response message carries the second information used to indicate that the MIP is successfully created, the first node reports the second information to the network manager.
The method according to any one of claims 3 to 5, wherein the second information includes location information of the node that created the MIP and flag information used to indicate the success or failure of the MIP creation.
A method for creating intermediate points of maintenance entity groups, including:

The second node receives a function trigger message sent by the first node, where the function trigger message carries first information used to indicate a request to create a MIP;

The second node creates the MIP according to the first information.
The method according to claim 7, wherein the function trigger message also carries level parameters and virtual local area network parameters used to create the MIP.
The method according to claim 8, wherein the second node creating the MIP according to the first information comprises:

The second node obtains the level parameter and the virtual local area network parameter in the function trigger message according to the first information;

The second node creates an MIP at the ingress port and the egress port of the second node respectively according to the level parameter and the virtual local area network parameter.
The method according to claim 7, further comprising:

The second node sends to the first node a function response message carrying the second information indicating that the MIP is successfully created, so that the first node caches or reports the second information to the network manager.
The method according to claim 10, wherein the second information includes location information of the node that created the MIP and flag information used to indicate the success or failure of the MIP creation.
A node comprising: a memory, a processor, and a computer program stored in the memory and capable of running on the processor, wherein the processor executes the computer program as described in any one of claims 1 to 6 The method for creating an intermediate point of a maintenance entity group or implements the method for creating an intermediate point of a maintenance entity group according to any one of claims 7 to 11.
A computer-readable storage medium storing computer-executable instructions, wherein the computer-executable instructions are used to execute the method for creating an intermediate point of a maintenance entity group according to any one of claims 1 to 6 or execute claim 7 The method for creating an intermediate point of a maintenance entity group described in any one of to 11.