Method, Node, and Readable Storage Medium for Maintaining Creation of Intermediate Points of Entity Groups

Abstract

The present invention provides 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 includes: a first node sending a function trigger message carrying first information for indicating a request to create a maintenance entity group intermediate point (MIP) to a second node, so that the second node creates the MIP based on the first information. In an embodiment of the present invention, by utilizing the first node to send a function trigger message to the second node, and the function trigger message carries the first information for indicating a request to create a MIP, when the second node receives the function trigger message sent by the first node, the second node can automatically create the MIP based on 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.

Description

Technical Field

[0001] 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 Art

[0002] Ethernet Operation Administration and Maintenance (OAM) technology is an OAM mechanism used in Ethernet networks. It primarily performs network operations, management, and maintenance functions through Ethernet in the First Mile (EFM) and Connectivity Fault Management (CFM). Loopback (LB) and Link Trace (LT) are key CFM functions. LB verifies connectivity between a MEG End Point (MEP) and a MEG Intermediate Point (MIP) or a peer MEP. LT verifies end-to-end routing paths by sending Link Trace Messages (LTM).

[0003] In related technologies, when using CFM to diagnose intermediate nodes, it is typically necessary to deploy a MIP on the intermediate node. Once the MIP is deployed, LB and LT are then performed to diagnose the intermediate node. This means that creating a MIP is essential for diagnosing intermediate node faults. However, in related technologies, MIP creation can only be performed manually. In complex network topologies, manually creating a MIP each time LB and LT are performed on an intermediate node is a significant waste of time, significantly impacting the efficiency of development, testing, and engineering maintenance personnel. Summary of the Invention

[0004] The following is a summary of the subject matter described in detail herein. This summary is not intended to limit the scope of the claims.

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

[0006] In a first aspect, an embodiment of the present invention provides a method for creating an intermediate point of a maintenance entity group, comprising:

[0007] The first node sends a function trigger message carrying first information for requesting to create a maintenance entity group intermediate point (MIP) to the second node, so that the second node creates the MIP according to the first information.

[0008] In a second aspect, an embodiment of the present invention further provides a method for creating an intermediate point of a maintenance entity group, comprising:

[0009] The second node receives a function trigger message sent by the first node, where the function trigger message carries first information indicating a request to create an MIP;

[0010] The second node creates a MIP according to the first information.

[0011] In a third aspect, an embodiment of the present invention further provides a node, comprising: a memory, a processor, and a computer program stored in the memory and runnable on the processor, wherein when the processor executes the computer program, the method for creating an intermediate point of a maintenance entity group as described in the first aspect or the method for creating an intermediate point of a maintenance entity group as described in the second aspect is implemented.

[0012] In a fourth aspect, an embodiment of the present invention further provides a computer-readable storage medium storing computer-executable instructions, wherein the computer-executable instructions are used to execute the above-mentioned method for creating an intermediate point of a maintenance entity group.

[0013] An embodiment of the present invention includes: a first node sending a function trigger message carrying first information indicating a request to create a MIP to a second node, so that the second node creates a MIP based on the first information. According to the solution provided by this embodiment of the present invention, when the second node receives the function trigger message sent by the first node while executing the LT function or the LB function, because the function trigger message carries the first information indicating a request to create a MIP, the second node can create the MIP under the triggering of the first information. That is, the second node can automatically create the MIP based on the first information in the function trigger message, thereby reducing the burden of manually creating the MIP and improving the efficiency of MIP creation.

[0014] Other features and advantages of the present invention will be described in the following description, and in part will become apparent from the description, or will be understood by practicing the present invention. The purposes and other advantages of the present invention can be realized and obtained by the structures particularly pointed out in the description, claims and drawings. BRIEF DESCRIPTION OF THE DRAWINGS

[0015] 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.

[0016] Figure 1 1 is a schematic diagram of a network topology for executing a method for creating an intermediate point of a maintenance entity group provided by an embodiment of the present invention;

[0017] Figure 2 is a flowchart of a method for creating an intermediate point of a maintenance entity group provided by an embodiment of the present invention;

[0018] Figure 3 1 is a schematic diagram of the structure of a special LTM message provided by one embodiment of the present invention;

[0019] Figure 4 is a flowchart of a method for creating an intermediate point of a maintenance entity group provided by another embodiment of the present invention;

[0020] Figure 5 This is a schematic diagram of the structure of a special LTR message provided by one embodiment of the present invention;

[0021] Figure 6 is a flowchart of a method for creating an intermediate point of a maintenance entity group provided by another embodiment of the present invention;

[0022] Figure 7 is a flowchart of a method for creating an intermediate point of a maintenance entity group provided by another embodiment of the present invention;

[0023] Figure 8 is a flowchart of a method for creating an intermediate point of a maintenance entity group provided by another embodiment of the present invention;

[0024] Figure 9 This is a flowchart of a method for creating an intermediate point of a maintenance entity group provided by another embodiment of the present invention. DETAILED DESCRIPTION

[0025] In order to make the purpose, technical solutions and advantages of the present invention more clearly understood, the present invention will be further described in detail below with reference to the accompanying drawings and embodiments. It should be understood that the specific embodiments described herein are only used to explain the present invention and are not intended to limit the present invention.

[0026] It should be noted that although the device schematics illustrate functional module divisions and the flowcharts illustrate logical sequences, in certain circumstances, the steps shown or described may be performed in a sequence that differs from the module divisions in the device or the sequence in the flowcharts. The terms "first," "second," and so on, in the specification, claims, and drawings, are used to distinguish similar items and are not necessarily used to describe a specific sequence or precedence.

[0027] 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 executing an LT function or a LB function, a function trigger message is sent by a first node to a second node, and the function trigger message carries first information for indicating a request to create a MIP. Therefore, when the second node receives the function trigger message sent by the first node, the second node can automatically create the MIP based on 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.

[0028] The embodiments of the present invention are further described below with reference to the accompanying drawings.

[0029] like Figure 1 As shown, Figure 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 provided by an embodiment of the present invention. Figure 1 In the example of , the network topology includes a first node 100, a second node 200, and a third node 300, wherein the first node 100, the second node 200, and the third node 300 can all support Ethernet services.

[0030] The first node 100 is provided with an egress port, the second node 200 is provided with an ingress port and an egress port, and 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 egress port of the second node 200 is connected to the ingress port of the third node 300.

[0031] A set of 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 performed, a MIP can be created in the second node 200. For example, MIPs need to be created at the ingress port and egress port of the second node 200 respectively.

[0032] The first node 100 , the second node 200 , and the third node 300 may include a memory and a processor respectively, wherein the memory and the processor may be connected via a bus or other means.

[0033] The memory, as a non-transient computer-readable storage medium, can be used to store non-transient software programs and non-transient computer executable programs. In addition, the memory may include a high-speed random access memory and may also include a non-transient memory, such as at least one disk storage device, a flash memory device, or other non-transient solid-state storage device. In some embodiments, the memory may optionally include a memory remotely arranged relative to the processor, and these remote memories may be connected to the processor via a network. Examples of the above-mentioned network include, but are not limited to, the Internet, an intranet, a local area network, a mobile communication network, and combinations thereof.

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

[0035] It will be understood by those skilled in the art that Figure 1 The topological structure shown in the figure does not constitute a limitation on the embodiments of the present invention, and may include more or fewer components than shown in the figure, or combine certain components, or arrange the components differently.

[0036] exist Figure 1 In the network topology shown, each node can respectively call the maintenance entity group intermediate point creation program stored therein to execute the maintenance entity group intermediate point creation method.

[0037] Based on the above network topology structure, various embodiments of the method for establishing an intermediate point of a maintenance entity group of the present invention are proposed.

[0038] like Figure 2 As shown, Figure 2 This is a flowchart of a method for creating a midpoint of a maintenance entity group provided by an embodiment of the present invention. The method for creating a midpoint of a maintenance entity group includes but is not limited to step S100.

[0039] In step S100, a first node sends a function trigger message carrying first information indicating a request to create a MIP to a second node, so that the second node creates a MIP according to the first information.

[0040] In one embodiment, the function trigger message may be a special LTM message suitable for executing the LT function, or a special Loopback Message (LBM) message suitable for executing 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 carries the first information indicating a request to create a MIP.

[0041] It is worth noting that the special LTM message and the special LBM message differ only in the message format and application scenario, but the two messages are consistent in terms of the function of triggering the creation of the MIP and the field information required to implement the MIP creation function. In order to avoid excessive repetition and redundancy in the description content and to more clearly illustrate the specific content of this embodiment, the following explanation is given using the application scenario of automatically creating a MIP when executing the LT function as an example. For the relevant explanation of the application scenario of automatically creating a MIP when executing the LB function, please refer to the explanation of the application scenario of automatically creating a MIP when executing the LT function.

[0042] In one embodiment, assuming a pair of peer MEPs are established between a first node and a third node, and that, when executing the LT function, a MIP needs to be created on a second node located between the first and third nodes. When the second node receives a special LTM message sent by the first node, because the special LTM message carries first information indicating a request to create a MIP, the second node can create the MIP in response to the triggering of the first information. Specifically, the second node can automatically create the MIP based on the first information in the special LTM message, thereby reducing the burden of manually creating the MIP and improving the efficiency of MIP creation. It is worth noting that the first node and the second node can reside on the same network device or on different network devices, and this embodiment does not specifically limit this.

[0043] In one embodiment, since the special LTM message carrying the first information for requesting MIP creation is created by the first node, the first node may have regular LTM messages and special LTM messages (i.e., function trigger messages in this embodiment). The first node may be configured with an enable switch for requesting MIP creation. When requesting a second node to create a MIP, the first node may turn on the enable switch. While the enable switch is on, the first node sends a special LTM message carrying the first information for requesting MIP creation to the second node. When MIP creation is not required, the enable switch is off, and the first node sends regular LTM messages to the second node while performing the LT function.

[0044] Those skilled in the art will appreciate that the regular LTM message is a message required for executing the LT function in the related art. When executing the LT function, the end-to-end routing path between nodes can be viewed by sending the regular LTM message.

[0045] In one embodiment, the special LTM message can be improved on the basis of the regular LTM message. For example, a new field structure can be extended in the regular LTM message to carry the first information for indicating the request to create a MIP, or a field structure in the regular LTM message can be redefined to carry the first information for indicating the request to create a MIP. This embodiment is not particularly limited. Figure 3 , Figure 3 This is a schematic diagram of the structure of a special LTM message provided by an embodiment. The special LTM message structure includes an Ethernet message header and LTM message content. The main fields of the message structure are explained as follows:

[0046] DMAC: Used to indicate the destination address and encapsulated in the Ethernet header. Its specific value is different from that of regular LTM messages. For example, the value range of the DMAC field of regular LTM messages is 01-80-C2-00-00-38 to 01-80-C2-00-00-3F. In this embodiment, the value of the DMAC field of the special LTM message is 01-80-C2-00-00-40.

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

[0048] Type: used to indicate type;

[0049] MD level: used to indicate the level of the maintenance domain;

[0050] OpCode: used to indicate the message code. When the message is an LTM message, the value is 0x05.

[0051] Original MAC: indicates the address of the source node that performs the LT function, that is, the address of the node where the local MEP is located.

[0052] Target MAC: indicates the address of the target node for the LT function, that is, the address of the node where the peer MEP is located;

[0053] Additional LTM TLVs: indicates additional TLV fields. Different TLV contents can be added based on actual conditions.

[0054] It is worth noting that the interpretation of other fields in the special LTM message structure is the same as the interpretation of the corresponding fields contained in the regular LTM message, so it will not be repeated here.

[0055] In one embodiment, in the above Figure 3In the case of the special LTM message structure shown, the first information carried in the special LTM message, indicating a request to create a MIP, can be stored in the DMAC field and take a special value, such as 01-80-C2-00-00-40, indicating that the LTM message is a special LTM message requesting the creation of a MIP. For example, when a second node receives a special LTM message sent by a first node and the DMAC field value obtained by the second node after parsing the special LTM message is 01-80-C2-00-00-40, it indicates that the first node is requesting the creation of a MIP. At this time, if the address information in the Target MAC field of the special LTM message is not the address of the second node, it indicates that the second node is an intermediate node between a pair of peer MEPs. Therefore, the second node automatically creates a MIP based on the first information, thereby reducing the burden of manual MIP creation and improving the efficiency of MIP creation. It should be noted that the first information indicating the request to create a MIP may also be stored in the Additional LTM TLVs field in a TLV format, which is not specifically limited in this embodiment.

[0056] In one embodiment, the function trigger message also carries at least information such as level parameters and virtual local area network (VLAN) parameters for creating a MIP. For example, the level parameters can be stored in the aforementioned MD level field, while the VLAN parameters can be stored in the Ethernet message header. When a second node receives the function trigger message sent by the first node, it can automatically create a MIP based on the level parameters and VLAN parameters in the function trigger message. This reduces the burden of manual MIP creation and improves the efficiency of MIP creation.

[0057] In addition, refer to Figure 4 In one embodiment, after step S100, the method for creating an intermediate point of a maintenance entity group further includes the following steps:

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

[0059] Step S300: When the function response message carries the second information indicating successful creation of the MIP, the first node caches the second information.

[0060] In one embodiment, the function response message may be a LinkTrace Reply (LTR) message suitable for performing the LT function, or a Loopback Reply (LBR) message suitable for performing the LB function. It is worth noting that the function response message carrying the second information indicating the successful creation of the MIP is a special message that is different from a regular LTR message or a regular LBR message. When the function response message carries the second information indicating the successful creation of the MIP, the function response message may be a special LTR message or a special LBR message.

[0061] It is worth noting that the special LTR message and the special LBR message differ only in the message format and application scenario, but the two messages are used to trigger the function of creating MIP and the field information required to implement the MIP creation function. In order to avoid excessive repetition and redundancy in the description content and to more clearly explain the specific content of this embodiment, the following explanation is given using the application scenario of automatically creating MIP when executing the LT function as an example. For the relevant explanation of the application scenario of automatically creating MIP when executing the LB function, please refer to the explanation of the application scenario of automatically creating MIP when executing the LT function.

[0062] In one embodiment, when a first node sends a special LTM message to a second node so that the second node creates a MIP based on the first information in the special LTM message, the second node will reply to the first node with a special LTR message. When the special LTR message meets the timeliness condition, that is, when the first node receives the special LTR message within a preset time period, the first node can determine that the special LTR message is valid. At this time, the first node will parse the special LTR message. When the special LTR message carries the second information for indicating the successful creation of the MIP, 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 receiving a special LTR message, the first node may not report the second information in the special LTR message to the network manager. Instead, the first node may wait to receive special LTR messages sent by all intermediate nodes between the first node and the peer MEP after they have completed MIP creation. After the first node receives special LTR messages from all intermediate nodes that have created MIPs, the first node reports the second information in these special LTR messages to the network manager. Alternatively, the first node may report the second information in each special LTR message to the network manager after receiving it, but this embodiment does not impose any specific limitations thereon.

[0063] It is worth noting that the preset time period can be appropriately selected based on actual application needs and is not specifically limited in this embodiment. When the function response message does not meet the time limit, the first node will determine that the function response message is invalid. In this case, the first node can discard the function response message and wait to receive the next function response message.

[0064] In one embodiment, when the function response message carries second information indicating successful MIP creation, after the first node reports the second information in the function response message to the network manager, the network manager may store the information related to MIP creation carried in the second information, such as the node that created the MIP and the address of the node that created the MIP. Therefore, the network manager can determine whether each intermediate node has successfully created the MIP and can also obtain relevant information about the intermediate nodes in the entire maintenance domain, thereby facilitating the network manager's management of the entire maintenance domain.

[0065] In one embodiment, for example, when executing an LT function, because the function response message carrying the second information indicating successful MIP creation is a special LTR message created by the second node, both regular LTR messages and special LTR messages may be established in the second node. When the second node receives a regular LTM message sent by the first node, it responds with a regular LTR message based on the regular LTM message. Furthermore, when the second node receives a special LTM message sent by the first node, it responds with a special LTR message based on the special LTM message.

[0066] Those skilled in the art will understand that a regular LTR message is a message required to perform the LT function in the related technology. When performing the LT function, a regular LTR message can be replied after receiving a regular LTM message for viewing the end-to-end routing path between nodes.

[0067] In one embodiment, the function response message carrying the second information for indicating the successful creation of the MIP can be obtained by improving the format of the existing related message. For example, the special LTR message can be improved on the basis of the regular LTR message. For example, a new field structure can be extended in the regular LTR message to carry the second information for indicating the successful creation of the MIP, or the field structure in the regular LTR message can be redefined to carry the second information for indicating the successful creation of the MIP. This embodiment is not specifically limited. A specific example is used for illustration. Figure 5 , Figure 5 This is a schematic diagram of the structure of a special LTR message provided by an embodiment. The special LTR message structure includes an Ethernet message header and LTR message content. The main fields of the message structure are explained as follows:

[0068] DMAC: used to indicate the destination address, encapsulated in the Ethernet message header;

[0069] SMAC: used to represent the source address, encapsulated in the Ethernet message header. Its value corresponds to the value of the DMAC field of the special LTM message in the above embodiment;

[0070] Type: used to indicate type;

[0071] MD level: used to indicate the level of the maintenance domain;

[0072] OpCode: used to indicate the message code. When the message is an LTR message, the value is 0x04.

[0073] Additional LTM TLVs: indicates additional TLV fields used to store secondary information related to MIP creation.

[0074] It is worth noting that the interpretation of other fields in the special LTR message structure is the same as the interpretation of the corresponding fields contained in the LTR message in the related art, so it will not be repeated here.

[0075] In one embodiment, the first node can determine whether the current LTR message is a special LTR message carrying the second information related to the creation of the MIP by taking the value of the SMAC field, or can determine whether the current LTR message is a special LTR message carrying the second information related to the creation of the MIP by identifying whether the content in the Additional LTM TLVs field is related to the creation of the MIP. This embodiment does not make specific limitations.

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

[0077] Step S400: When the function response message does not carry the second information indicating successful creation of the MIP, the first node reports the cached second information to the network manager.

[0078] In one embodiment, when the first node caches the second information carried in the function response message for indicating successful creation of the MIP, if the first node receives a function response message that does not carry the second information for indicating successful creation of the MIP, for example, the first node receives an LTR message that does not carry the second information, then it means that the LTR message is a regular LTR message, and the regular LTR message comes from the opposite MEP of the first node. At this time, it means 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, such as the node that created the MIP, the address of the node that created the MIP, and other information to the network manager, so that the network manager can subsequently learn whether each intermediate node has successfully created the MIP, and can also obtain relevant information of the intermediate nodes in the entire maintenance domain through the network manager, which facilitates the network manager's management of the entire maintenance domain.

[0079] In addition, in one embodiment, the second information includes location information of the node that creates the MIP and flag information indicating success or failure of the MIP creation.

[0080] In one embodiment, the location information of the node that creates the MIP and the flag information used to indicate whether the MIP creation is successful or failed can be configured in the message structure of the function response message, for example, in the Figure 5 In the Additional LTM TLVs field of the special LTR message structure in the embodiment shown. The location information of the node that created the MIP may include at least one of the following information: the network element name, rack number, sub-rack number, slot number, etc., which is not specifically limited in this embodiment. In addition, the flag information used to indicate whether the MIP creation is successful or failed may be a single identifier indicating whether the node ingress port successfully created the MIP, or a single identifier indicating whether the node egress port successfully created the MIP. It may also include multiple identifiers indicating whether the node ingress port and egress port successfully created the MIP, which is not specifically limited in this embodiment. When the first node reports the location information and the flag information to the network manager, the network manager can learn whether each intermediate node successfully created the MIP, and can also obtain relevant information about the intermediate nodes in the entire maintenance domain through the network manager, thereby facilitating the network manager's management of the entire maintenance domain.

[0081] In addition, another embodiment of the present invention further provides a method for creating a maintenance entity group intermediate point, such as Figure 6 As shown, Figure 6Flowchart of a method for creating a maintenance entity group midpoint according to another embodiment of the present invention. The method for creating a maintenance entity group midpoint includes but is not limited to the following steps:

[0082] Step S510: The second node receives a function trigger message sent by the first node, where the function trigger message carries first information indicating a request to create a MIP.

[0083] Step S520: The second node creates a MIP according to the first information.

[0084] In one embodiment, the function trigger message can be a special LTM message suitable for executing the LT function, or a special LBM message suitable for executing 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 for indicating a request to create a MIP.

[0085] In one embodiment, assuming that a set of peer MEPs is established between a first node and a third node, and that when executing the LT function, a MIP needs to be created at a second node located between the first node and the third node. In this case, when the second node receives a special LTM message sent by the first node, since the special LTM message carries first information indicating a request to create a MIP, the second node can create the MIP under the triggering of the first information. That is, the second node can automatically create the MIP based on the first information in the special LTM message, thereby reducing the burden of manually creating the MIP and improving the efficiency of MIP creation.

[0086] In one embodiment, the function trigger message carrying the first information for indicating a request to create an MIP can be improved based on the format of an existing related message. For example, the special LTM message can be improved based on a regular LTM message. For example, a new field structure can be extended in a regular LTM message to carry the first information for indicating a request to create an MIP, or a field structure in a regular LTM message can be redefined to carry the first information for indicating a request to create an MIP. This embodiment does not make any specific limitations.

[0087] It is worth noting that the specific structure and specific meaning of the special LTM message in this embodiment are similar to those in the example Figure 3 The specific structure and specific meaning of the special LTM message in the embodiment shown are consistent. For the explanation of the specific structure and specific meaning of the special LTM message in this embodiment, please refer to the above Figure 3 The explanation of the specific structure and specific meaning of the special LTM message in the illustrated embodiment will not be repeated here.

[0088] In addition, in one embodiment, the method for establishing an intermediate point of a maintenance entity group further includes the following steps:

[0089] Step S530: determine the outbound port and forward the function trigger message.

[0090] In one embodiment, when the second node receives a 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 whether the content of the Target MAC field in the special LTM 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 second node will create a MIP according to the first information carried in the function trigger message for indicating a request to create a MIP. After completing the creation of the MIP, the second node will also determine the output port and forward the function trigger message to the next node, so that the function trigger message can flow through all intermediate nodes between the peer MEPs, so that all intermediate nodes can create a MIP according to the first information in the function trigger message.

[0091] 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 a function response message to the first node. If the intermediate node receives the function response message, the intermediate node will determine the output port and forward the function response message, and will not perform any related processing based on the function response message, that is, the intermediate node transparently transmits the function response message.

[0092] In addition, it is worth noting that if the peer MEP (e.g. Figure 1 When the third node in the illustrated embodiment receives a function trigger message sent by the first node, the peer MEP will first determine whether the content of the Target MAC field in the function trigger message is the address of the current node. If the content of the Target MAC field is the address of the current node, the peer MEP will first determine whether there is a MEP corresponding to the function trigger message at the corresponding flow point. If so, it means that the current node is the target node to which the function trigger message needs to be transmitted. At this time, the peer MEP will reply to the first node with a function response message that does not carry the second information related to creating the MIP and stop forwarding the function trigger message. In addition, if the peer MEP determines that there is no MEP corresponding to the function trigger message at the corresponding flow point, the peer MEP will directly discard the function trigger message.

[0093] In one embodiment, the function trigger message also carries at least information such as level parameters and virtual local area network parameters for creating MIP. For example, the level parameters can be stored in Figure 3 In the MDlevel field of the special LTM message structure of the embodiment shown, the virtual local area network parameters can be stored in Figure 3 In the Ethernet message header of the special LTM message structure of the embodiment shown, when the second node receives the function trigger message sent by the first node, the second node can automatically create a MIP based on information such as the level parameter and virtual local area network parameters in the function trigger message, thereby reducing the burden of manual MIP creation and improving the efficiency of MIP creation.

[0094] In addition, refer to Figure 7 In one embodiment, step S520 includes but is not limited to the following steps:

[0095] Step S521: The second node obtains the level parameter and the virtual local area network parameter in the function trigger message according to the first information;

[0096] Step S522: The second node creates a MIP at the ingress port and egress port of the second node according to the level parameter and the virtual local area network parameter.

[0097] In one embodiment, when a second node receives a function trigger message sent by a first node, the second node first determines whether the function trigger message carries first information indicating a request to create a MIP. If the function trigger message carries the first information, the second node parses and obtains the level parameter and virtual local area network parameter in the function trigger message, and automatically creates a MIP at the ingress port and egress port of the second node based on the level parameter and virtual local area network parameter. It is worth noting that the egress port for creating the MIP in the second node can be obtained based on information such as a Media Access Control Address (MAC) table in the second node.

[0098] Furthermore, in one embodiment, when the second node creates a MIP at its ingress port and egress port respectively, if the corresponding MIP already exists, the second node does not perform a specific creation operation and the MIP is deemed to have been created successfully.

[0099] In addition, in one embodiment, the method for establishing an intermediate point of a maintenance entity group further includes the following steps:

[0100] Step S540: The second node sends a function response message carrying second information indicating successful creation of the MIP to the first node, so that the first node caches the second information or reports it to the network manager.

[0101] In one embodiment, the function response message may be an LTR message suitable for executing the LT function, or an LBR message suitable for executing the LB function. It is worth noting that the function response message carrying the second information indicating the successful establishment of the MIP is a special message that is different from a regular LTR message or a regular LBR message. When the function response message carries the second information indicating the successful establishment of the MIP, the function response message may be a special LTR message or a special LBR message.

[0102] In one embodiment, after the second node creates a MIP based on the function trigger message sent by the first node, the second node will reply to the first node with a function response message. After the first node receives the function response message, the first node will parse the function response message. If the function response message carries the second information used to indicate the successful creation of the MIP, 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 function response message, or directly report the second information in the function response message to the network manager.

[0103] In one embodiment, for example, when executing an LT function, because the function response message carrying the second information indicating successful MIP creation is a special LTR message created by the second node, both regular LTR messages and special LTR messages may be established in the second node. When the second node receives a regular LTM message sent by the first node, it responds with a regular LTR message based on the regular LTM message. Furthermore, when the second node receives a special LTM message sent by the first node, it responds with a special LTR message based on the special LTM message.

[0104] In one embodiment, the function response message carrying the second information for indicating the successful creation of the MIP can be improved based on the format of the existing related message. For example, the special LTR message can be improved based on the regular LTR message. For example, a new field structure can be extended in the regular LTR message to carry the second information for indicating the successful creation of the MIP, or the field structure in the regular LTR message can be redefined to carry the second information for indicating the successful creation of the MIP. This embodiment does not make any specific limitations.

[0105] It is worth noting that the specific structure and specific meaning of the special LTR message in this embodiment are similar to those in the example Figure 5 The specific structure and specific meaning of the special LTR message in the embodiment shown are consistent. For the explanation of the specific structure and specific meaning of the special LTR message in this embodiment, please refer to the above Figure 5The explanation of the specific structure and specific meaning of the special LTR message in the illustrated embodiment will not be repeated here.

[0106] In addition, in one embodiment, the second information includes location information of the node that creates the MIP and flag information indicating success or failure of the MIP creation.

[0107] In one embodiment, the location information of the node that creates the MIP and the flag information used to indicate whether the MIP creation is successful or failed can be configured in the message structure of the function response message, for example, in the Figure 5 In the Additional LTM TLVs field of the special LTR message structure in the embodiment shown. The location information of the node that created the MIP may include at least one of the following information: the network element name, rack number, sub-rack number, slot number, etc., which is not specifically limited in this embodiment. In addition, the flag information used to indicate whether the MIP creation is successful or failed may be a single identifier indicating whether the node ingress port successfully created the MIP, or a single identifier indicating whether the node egress port successfully created the MIP. It may also include multiple identifiers indicating whether the node ingress port and egress port successfully created the MIP, which is not specifically limited in this embodiment. When the first node reports the location information and the flag information to the network manager, the network manager can learn whether each intermediate node successfully created the MIP, and can also obtain relevant information about the intermediate nodes in the entire maintenance domain through the network manager, thereby facilitating the network manager's management of the entire maintenance domain.

[0108] The methods for creating intermediate points of maintenance entity groups provided in the above embodiments are described in detail below using specific examples:

[0109] Example 1:

[0110] Reference Figure 8 , Figure 8 This is a flowchart of a method for establishing an intermediate point in a maintenance entity group, applied to a network topology including a first node 100, a second node 200, a third node 300, and a fourth node 400. Each of the first node 100, the second node 200, the third node 300, and the fourth node 400 can support Ethernet services. The first node 100 and the fourth node 400 establish a group of peer MEPs. The second node 200 and the third node 300 are intermediate nodes between the peer MEPs. When a load balancer or load transmission (LT) function needs to be performed within the maintenance domain of the first node 100, a MIP needs to be established on the second node 200 and the third node 300.

[0111] 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 that of a regular LTM message). The special LTM message will first be transmitted to the second node 200. When the second node 200 determines that the special LTM message meets the rules, that is, 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 the level parameters and virtual LAN parameters and other information in the special LTM message, and create a MIP at 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 A special LTM message is sent back to the first node 100. The special LTR message carries the network element name, rack number, subrack number, slot number, and flag information indicating whether the MIP has been successfully established at the ingress and egress ports of the second node 200. The second node 200 then determines the egress port for transmitting the special LTM message and forwards the special LTM message to the third node 300 via the egress port. Upon receiving 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. Upon receiving the special LTM message, the fourth node 400 determines that the Target MAC field in the special LTM message is the MAC address of the fourth node 400. Therefore, the fourth node 400 sends a regular LTR message back to the first node 100 and stops forwarding the special LTM message.

[0112] When the first node 100 obtains the special LTR messages sent by the second node 200 and the third node 300 respectively within the preset time period, the first node 100 will cache the positioning information of the node creating the MIP and the flag information indicating the success or failure of the MIP creation carried in the special LTR message. 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 the network manager.

[0113] Example 2:

[0114] Reference Figure 9 , Figure 9This is a flowchart of a method for creating an intermediate point in a maintenance entity group, applied to another network topology. The network topology includes a first node 100, a second node 200, a third node 300, and a fourth node 400. Each of the first node 100, the second node 200, the third node 300, and the fourth node 400 can support Ethernet services. The first node 100, the third node 300, and the fourth node 400 establish a point-to-multipoint MEP. Specifically, the first node 100 and the third node 300 form a set of peer MEPs, the first node 100 and the fourth node 400 form another set of peer MEPs, and the second node 200 is an intermediate node between the first node 100 and the third node 300. When a load balancer (LB) or load transmission (LT) function needs to be performed within the maintenance domain of the first node 100 and the third node 300, a MIP needs to be created on the second node 200.

[0115] When the LT function needs to be executed, 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 that of a regular LTM message). The special LTM message will first be transmitted to the second node 200. When the second node 200 determines that the special LTM message meets the rules, that is, 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 the level parameters and virtual LAN parameters and other information in the special LTM message, and send it to the second node 200. 0, creates a MIP for each of the ingress and egress ports of the second node 200. After the MIP is created, the second node 200 replies with a special LTR message to the first node 100. The special LTR message carries the network element name, rack number, subrack number, slot number, and flag information indicating whether the MIP is successfully created for the ingress and egress ports of the second node 200. Then, the second node 200 determines the egress port for transmitting the special LTM message and forwards the special LTM message to the third node 300 through the egress port. After the third node 300 receives the special LTM message, it determines that the content of the Target MAC field in the special LTM message is the MAC address of the third node 300. Therefore, the third node 300 replies with a regular LTR message to the first node 100 and stops forwarding the special LTM message.

[0116] When the first node 100 obtains a special LTR message sent by the second node 200 within a preset time period, the first node 100 will cache the positioning information of the node creating the MIP and the flag information indicating the success or failure of the MIP creation carried in the special LTR message. When the first node 100 receives a regular LTR message sent by the third node 300, the first node 100 will report all cached information to the network manager.

[0117] In addition, an embodiment of the present invention provides a node, which includes: a memory, a processor, and a computer program stored in the memory and executable on the processor.

[0118] The processor and the memory may be connected via a bus or other means.

[0119] It should be noted that the nodes in this embodiment can be applied to Figure 1 、 Figure 8 or Figure 9 The nodes in the embodiment shown in FIG. 1 can constitute Figure 1 、 Figure 8 or Figure 9 Part of the network topology in the illustrated embodiments, these embodiments all belong to the same inventive concept, so these embodiments have the same implementation principles and technical effects, and will not be described in detail here.

[0120] The non-transient software program and instructions required to implement the above embodiment of the maintenance entity group intermediate point creation method are stored in the memory. When executed by the processor, the above embodiment of the maintenance entity group intermediate point creation method is executed, for example, the above described method is executed. Figure 2 Method step S100, Figure 4 Method steps S200 to S300, Figure 6 Method steps S510 to S520 or Figure 7 Method steps S521 to S522 in .

[0121] The device embodiments described above are merely illustrative. The units described as separate components may or may not be physically separate, i.e., they may be located in one place or distributed across multiple network units. Some or all of the modules may be selected based on actual needs to achieve the objectives of this embodiment.

[0122] In addition, an embodiment of the present invention further provides a computer-readable storage medium, which stores computer-executable instructions. The computer-executable instructions are executed by a processor or controller, for example, by a processor in the above-mentioned node embodiment, so that the above-mentioned processor can execute the method for creating an intermediate point of the maintenance entity group in the above-mentioned embodiment, for example, executing the above-mentioned Figure 2 Method step S100, Figure 4 Method steps S200 to S300, Figure 6 Method steps S510 to S520 or Figure 7 Method steps S521 to S522 in .

[0123] Those skilled in the art will appreciate that all or some of the steps and systems in the method 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 implemented as hardware, or implemented as an integrated circuit, such as an application-specific integrated circuit. Such software can be distributed on a computer-readable medium, and the computer-readable medium can include computer storage media (or non-transitory media) and communication media (or temporary media). As known to those skilled in the art, the term computer storage media is included in any method or technology for storing information (such as computer-readable instructions, data structures, program modules, or other data) and is volatile and non-volatile, removable, and non-removable. Computer storage media includes, but is not limited to, RAM, ROM, EEPROM, flash memory, or other memory technology, CD-ROM, digital versatile disks (DVD), or other optical disk storage, magnetic cassettes, magnetic tapes, disk storage, or other magnetic storage devices, or any other medium that can be used to store desired information and can be accessed by a computer. Furthermore, as is well known to those skilled in the art, communication media typically embodies computer-readable instructions, data structures, program modules, or other data in a modulated data signal such as a carrier wave or other transport mechanism, and may include any information delivery media.

[0124] The above is a specific description of the preferred implementation of the present invention, but the present invention is not limited to the above implementation. Those skilled in the art can make various equivalent modifications or substitutions without violating the spirit of the present invention. These equivalent modifications or substitutions are all included in the scope defined by the claims of the present invention.

Claims

1. A method for creating an intermediate point of a maintenance entity group, comprising: The first node sends a function trigger message carrying first information for requesting to create a maintenance entity group intermediate point MIP to the second node, so that the second node creates the MIP according to the first information when receiving the function trigger message.

2. The method according to claim 1, characterized in that The function trigger message also carries level parameters and virtual local area network parameters for creating a MIP.

3. The method according to claim 1, characterized in that Also includes: 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 indicating that the MIP is successfully created, the first node caches the second information.

4. The method according to claim 3, characterized in that Also includes: When the function response message does not carry the second information indicating successful creation of the MIP, the first node reports the cached second information to the network manager.

5. The method according to claim 3, characterized in that Also includes: When the function response message carries the second information indicating that the MIP is successfully created, the first node reports the second information to the network manager.

6. The method according to any one of claims 3 to 5, characterized in that The second information includes positioning information of a node that creates the MIP and flag information indicating success or failure of the MIP creation.

7. A method for creating an intermediate point of a maintenance entity group, comprising: The second node receives a function trigger message sent by the first node, where the function trigger message carries first information indicating a request to create an MIP; The second node creates a MIP according to the first information.

8. The method according to claim 7, characterized in that The function trigger message also carries level parameters and virtual local area network parameters for creating a MIP.

9. The method according to claim 8, characterized in that The second node creating a MIP according to the first information includes: 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 a MIP at an ingress port and an egress port of the second node according to the level parameter and the virtual local area network parameter.

10. The method according to claim 7, characterized in that Also includes: The second node sends a function response message carrying second information indicating successful creation of the MIP to the first node, so that the first node caches the second information or reports it to the network manager.

11. The method according to claim 10, characterized in that The second information includes positioning information of a node that creates the MIP and flag information indicating success or failure of the MIP creation.

12. A node comprising: A memory, a processor, and a computer program stored in the memory and executable on the processor, wherein when the processor executes the computer program, the method for creating an intermediate point of a maintenance entity group as described in any one of claims 1 to 6 or the method for creating an intermediate point of a maintenance entity group as described in any one of claims 7 to 11 is implemented.

13. A computer-readable storage medium storing computer-executable instructions, wherein the computer-executable instructions are used to execute the method for creating a maintenance entity group intermediate point according to any one of claims 1 to 6 or the method for creating a maintenance entity group intermediate point according to any one of claims 7 to 11.

Images