CN113709049A

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

Info

Publication number: CN113709049A
Application number: CN202010428505.3A
Authority: CN
Inventors: 宋国伟
Original assignee: ZTE Corp
Current assignee: ZTE Corp
Priority date: 2020-05-20
Filing date: 2020-05-20
Publication date: 2021-11-26
Also published as: WO2021233202A1

Abstract

The invention provides a method for creating a middle point of a maintenance entity group, a node and a readable storage medium. The method for creating the intermediate point of the maintenance entity group comprises the following steps: the first node sends a function trigger message carrying first information for indicating that the maintenance entity group intermediate point MIP is requested to be created to the second node, so that the second node creates the MIP according to the first information. In the embodiment of the invention, the first node is used for sending the function triggering message to the second node, and the function triggering message carries the first information for indicating the request of creating the MIP, so that the second node can automatically create the MIP according to the first information in the function triggering message under the condition that the second node receives the function triggering message sent by the first node, thereby reducing the burden of manually creating the MIP and improving the efficiency of creating the MIP.

Description

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

Technical Field

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

Background

An Ethernet Operation and Maintenance (OAM) technology is an OAM mechanism applied in Ethernet, which mainly performs an Operation, Management and Maintenance function on a network through Ethernet in the First Mile (EFM) and Connectivity Fault Management (CFM). Among them, Loop Back (LB) and Link Trace (LT) are important functions of CFM. LB may be used to verify connectivity between a maintenance entity group boundary Point (MEP) and a maintenance entity group Intermediate Point (MEP) or peer MEP; the LT may view the end-to-end routing path by sending a Link Trace Message (LTM).

In the related art, when CFM is used to perform fault diagnosis on an intermediate node, MIP is generally required to be deployed at the intermediate node, and LB and LT are performed on the intermediate node to perform fault diagnosis on the intermediate node based on the MIP deployed at the intermediate node. That is, although the MIP is created as necessary for diagnosing a failure of the intermediate node, the MIP can be created only manually in the related art. Under the condition that the network topology is relatively complex, if LB and LT are executed on the intermediate node each time, manual MIP creation is required, a lot of time is inevitably wasted, and particularly, efficiency is affected for personnel such as development, testing, engineering maintenance and the like.

Disclosure of Invention

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.

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

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

the first node sends a function trigger message carrying first information for indicating that the maintenance entity group intermediate point MIP is requested to be created to the second node, so that the second node creates the MIP according to the first information.

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

a second node receives a function trigger message sent by a first node, wherein the function trigger message carries first information for indicating that the MIP is requested to be created;

the second node creates MIP according to the first information.

In a third aspect, an embodiment of the present invention further provides a node, including: a memory, a processor and a computer program stored on the memory and executable on the processor, the processor implementing a maintenance entity group intermediate point creation method as described above in the first aspect or implementing a maintenance entity group intermediate point creation method as described above in the second aspect when executing the computer program.

In a fourth aspect, an embodiment of the present invention further provides a computer-readable storage medium storing computer-executable instructions for performing the method for creating an intermediate point in a maintenance entity group as described above.

The embodiment of the invention comprises the following steps: the first node sends a function triggering message carrying first information used for indicating that the MIP is requested to be created to the second node, so that the second node creates the MIP according to the first information. According to the scheme provided by the embodiment of the invention, when the second node receives the function trigger message sent by the first node under the condition of executing the LT function or the LB function, the second node can create the MIP under the trigger of the first information because the function trigger message carries the first information for indicating the request of creating the MIP, namely, the second node can automatically create the MIP according to the first information in the function trigger message, so that the burden of manually creating the MIP can be reduced, and the efficiency of creating the MIP is improved.

Additional features and advantages of the invention will be set forth in the description which follows, and in part will be obvious from the description, or may be learned by practice of the invention. The objectives and other advantages of the invention will be realized and attained by the structure particularly pointed out in the written description and claims hereof as well as the appended drawings.

Drawings

The accompanying drawings are included to provide a further understanding of the invention and are incorporated in and constitute a part of this specification, illustrate embodiments of the invention and together with the example serve to explain the principles of the invention and not to limit the invention.

FIG. 1 is a schematic diagram of a network topology for performing a method for maintaining a creation of a group of entities intermediate points according to an embodiment of the present invention;

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

fig. 3 is a schematic structural diagram of a special LTM packet according to an embodiment of the present invention;

FIG. 4 is a flowchart of a method for creating intermediate points in a maintenance entity group according to another embodiment of the present invention;

fig. 5 is a schematic structural diagram of a special LTR message according to an embodiment of the present invention;

FIG. 6 is a flowchart of a method for creating intermediate points in a maintenance entity group according to another embodiment of the present invention;

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

FIG. 8 is a flowchart of a method for maintaining an entity group intermediate point creation provided by another embodiment of the present invention;

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

Detailed Description

In order to make the objects, technical solutions and advantages of the present invention more apparent, the present invention is described in further detail below with reference to the accompanying drawings and embodiments. It should be understood that the specific embodiments described herein are merely illustrative of the invention and are not intended to limit the invention.

It should be noted that although functional blocks are partitioned in a schematic diagram of an apparatus and a logical order is shown in a flowchart, in some cases, the steps shown or described may be performed in a different order than the partitioning of blocks in the apparatus or the order in the flowchart. The terms first, second and the like in the description and in the claims, and the drawings described above, are used for distinguishing between similar elements and not necessarily for describing a particular sequential or chronological order.

The 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 an LB function, a first node is utilized to send a function trigger message to a second node, and the function trigger message carries first information for indicating that MIP creation is requested, so that the second node can automatically create the MIP according to the first information in the function trigger message under the condition that the second node receives the function trigger message sent by the first node, thereby reducing the burden of manually creating the MIP and improving the MIP creation efficiency.

The embodiments of the present invention will be further explained with reference to the drawings.

As shown in fig. 1, fig. 1 is a schematic diagram of a network topology for performing 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 comprises 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 are each capable of supporting ethernet traffic.

The first node 100 is provided with an output port, the second node 200 is provided with an input port and an output port, the third node 300 is provided with an input port, the output port of the first node 100 is connected with the input port of the second node 200, and the output port of the second node 200 is connected with the input port of the third node 300.

A set of peer MEPs may be established between the first node 100 and the third node 300, and when it is required to perform the LT function or the LB function, a MIP may be created in the second node 200, for example, a MIP may be required to be created at an ingress port and an egress port of the second node 200, respectively.

The first node 100, the second node 200 and the third node 300 may comprise a memory and a processor, respectively, wherein the memory and the processor may be connected by a bus or other means.

The memory, which is a non-transitory computer readable storage medium, may be used to store non-transitory software programs as well as non-transitory computer executable programs. Further, the memory may include high speed random access memory, and may also include non-transitory memory, such as at least one disk storage device, flash memory device, or other non-transitory solid state storage device. In some embodiments, the memory optionally includes memory located remotely from the processor, and these remote memories may be connected to the processor through a network. Examples of such networks include, but are not limited to, the internet, intranets, local area networks, mobile communication networks, and combinations thereof.

The network topology and the application scenario described in the embodiment of the present invention are for more clearly illustrating the technical solution of the embodiment of the present invention, and do not form a limitation on the technical solution provided in the embodiment of the present invention, and it is known to those skilled in the art that the technical solution provided in the embodiment of the present invention is also applicable to similar technical problems along with the evolution of the network topology and the occurrence of new application scenarios.

Those skilled in the art will appreciate that the topology shown in fig. 1 is not meant to limit embodiments of the present invention and may include more or fewer components than those shown, or some components may be combined, or a different arrangement of components.

In the network topology shown in fig. 1, each node may invoke its stored maintenance entity group intermediate point creation program to execute the maintenance entity group intermediate point creation method.

Based on the above network topology structure, embodiments of the method for creating a middle point of a maintenance entity group according to the present invention are provided.

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, where 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 a function trigger packet carrying first information for indicating that MIP creation is requested to the second node, so that the second node creates MIP according to the first information.

In an embodiment, the function trigger packet may be a special LTM packet adapted to execute the LT function, or may also be a special Loopback Message (LBM) packet adapted to execute the LB function. It should be noted that, whether the function trigger packet is a special LTM packet or a special LBM packet, the function trigger packet carries first information indicating that the MIP is requested to be created.

It should be noted that the special LTM packet and the special LBM packet are only different in packet format and application scenario, but the two packets are used to trigger the function of creating MIP and the contents of field information and the like needed to implement the function of creating MIP are consistent, so as to avoid redundant description contents, and to enable a clearer description of the specific contents of this embodiment, the following explanation is given by taking the application scenario of automatically creating MIP when executing the LT function as an example, and the explanation of the application scenario of automatically creating MIP when executing the LB function may refer to the explanation of the application scenario of automatically creating MIP when executing the LT function.

In an embodiment, it is assumed that a group of peer MEPs is established between a first node and a third node, and when executing an LT function, a MIP needs to be created at a second node between the first node and the third node, and when the second node receives a special LTM packet sent by the first node, because the special LTM packet carries first information indicating that it is requested to create the MIP, the second node may create the MIP under the trigger of the first information, that is, the second node may automatically create the MIP according to the first information in the special LTM packet, so that a burden of manually creating the MIP can be reduced, and efficiency of creating the MIP is improved. It should be noted that the first node and the second node may be in the same network device, or may be in different network devices, which is not limited in this embodiment.

In an embodiment, since the special LTM packet carrying the first information indicating that the MIP is requested to be created is created by the first node, the first node may be created with a conventional LTM packet and a special LTM packet (i.e., the function trigger packet in this embodiment). The first node may be configured with an enable switch for requesting to create the MIP, when a second node needs to be requested to create the MIP, the first node may turn on the enable switch, and when the enable switch is in an on state, the first node may send a special LTM packet carrying first information for indicating that the MIP is requested to be created to the second node; and when the MIP does not need to be created, the enabling switch is in a closed state, and at the moment, the first node sends a conventional LTM message to the second node under the condition of executing the LT function.

It can be understood by those skilled in the art that the conventional LTM packet is a packet that is required to be used when executing the LT function in the related art, and when executing the LT function, the end-to-end routing path between nodes can be checked by sending the conventional LTM packet.

In an embodiment, the special LTM packet may be obtained by improving on the basis of a conventional LTM packet, for example, the field structure in the conventional LTM packet may be extended to carry the first information indicating that the MIP is requested to be created, or the field structure in the conventional LTM packet may be redefined to carry the first information indicating that the MIP is requested to be created, which is not limited in this embodiment. To illustrate by a specific example, referring to fig. 3, fig. 3 is a schematic structural diagram of a special LTM packet provided in an embodiment, where the special LTM packet structure includes an ethernet packet header and LTM packet content, where main fields of the packet structure are explained as follows:

DMAC: the value of the DMAC field of the conventional LTM packet is, for example, in the range of 01-80-C2-00-00-38 to 01-80-C2-00-00-3F, while in this embodiment, the value of the DMAC field of the special LTM packet is 01-80-C2-00-00-40;

SMAC: used for representing the source address, capsulate in the header of Ethernet message;

type: for representing a type;

MD level: for indicating a level of maintenance domain;

OpCode: the method is used for representing message coding, and when the message is an LTM message, the value is 0x 05;

origin MAC: the address used for indicating the source node performing the LT function, namely the address of the node where the home end MEP is located;

target MAC: the address used for expressing the target node for LT function, namely the address of the node where the opposite end MEP is located;

additional LTM TLVs: for indicating additional TLV fields, different TLV contents may be added according to the actual situation.

It should be noted that the explanations of other fields in the special LTM message structure are the same as those of corresponding fields included in the conventional LTM message, and therefore, the explanations thereof are omitted here.

In an embodiment, in the case of the special LTM packet structure shown in fig. 3, the first information carried in the special LTM packet for indicating that the MIP is requested to be created may be stored in the DMAC field, and is a special value, for example, a value of 01-80-C2-00-00-40, for indicating that the LTM packet is a special LTM packet, and is used to indicate that the MIP is requested to be created. For example, when the second node acquires the special LTM packet sent by the first node, and the value of the DMAC field obtained by the second node by parsing the special LTM packet is 01-80-C2-00-00-40, it indicates that the first node requests to create the MIP, and at this time, if the address information of the Target MAC field in the special LTM packet is not the address of the second node, it indicates that the second node is an intermediate node between a set of peer MEPs, and therefore, the second node automatically creates the MIP according to the first information, thereby reducing the burden of manually creating the MIP and improving the efficiency of creating the MIP. It should be noted that the first information indicating that the MIP is requested to be created may also be stored in the Additional LTM TLVs field in the format of TLV, and the embodiment is not limited in particular.

In an embodiment, the function trigger packet further carries at least information such as a level parameter and a virtual local area network parameter for creating the MIP. For example, the level parameter may be stored in the MD level field described above, and the vlan parameter may be stored in the ethernet header. When the second node receives the function trigger message sent by the first node, the second node can automatically create the MIP according to the level parameters, the virtual local area network parameters and other information in the function trigger message, so that the burden of manually creating the MIP can be reduced, and the MIP creating efficiency is improved.

In addition, referring to fig. 4, in an embodiment, after step S100, the method for creating an intermediate point of a 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 packet carries the second information for 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 Response (LTR) message adapted to execute an LT function, or may be a Loopback response (LBR) message adapted to execute an LB function. It should be noted that the functional response packet carrying the second information indicating that the MIP is successfully created is a special packet different from the conventional LTR packet or the conventional LBR packet, and when the functional response packet carries the second information indicating that the MIP is successfully created, the functional response packet may be the special LTR packet or the special LBR packet.

It should be noted that the special LTR packet and the special LBR packet are only different in packet format and application context, but the two packets are used to trigger the function of creating MIP and the content of field information and the like needed to implement the function of creating MIP are consistent, so as to avoid redundant description contents, and to enable a clearer description of the specific content of this embodiment, the following explanation is given by taking the application context of automatically creating MIP when executing the LT function as an example, and the explanation of the application context of automatically creating MIP when executing the LB function may refer to the explanation of the application context of automatically creating MIP when executing the LT function.

In an embodiment, when a first node sends a special LTM message to a second node, so that the second node creates an MIP according to first information in the special LTM message, the second node replies the special LTR message to the first node, when the special LTR message meets an aging condition, that is, when the first node receives the special LTR message within a preset time period, the first node may determine that the special LTR message is valid, at this time, the first node may parse the special LTR message, and when the special LTR message carries second information indicating that the MIP is successfully created, that is, the second node has successfully created the MIP, at this time, the first node may cache the second information in the received special LTR message, or directly report the second information in the special LTR message to a network manager. After the first node receives the special LTR message, the first node may first not report the second information in the special LTR message to the network manager, but wait to receive the special LTR message sent by all intermediate nodes between the first node and the opposite end MEP after the MIP creation is completed, and after the first node receives the special LTR messages replied by all intermediate nodes creating the MIP, the first node reports the second information in the special LTR messages to the network manager. In addition, the first node may also report the second information of the special LTR message to the network manager after receiving each special LTR message, which is not limited in this embodiment.

It should be noted that the preset time period may be appropriately selected according to the actual application requirement, and the embodiment is not particularly limited. When the function response message does not meet the aging condition, the first node may determine that the function response message is invalid, and at this time, the first node may discard the function response message and wait for receiving the next function response message.

In an embodiment, when the functional response packet carries the second information indicating that the MIP is successfully created, after the first node reports the second information in the functional response packet to the network manager, the network manager may store information content related to the MIP created in the second information, for example, an address of a node creating the MIP, and the like. Therefore, whether the MIP is successfully created by each intermediate node can be known through the network manager, and the related information of the intermediate nodes in the whole maintenance domain can be obtained, so that the management of the whole maintenance domain by the network manager can be facilitated.

In an embodiment, for example, when executing the LT function, since the function response packet carrying the second information indicating that the MIP is successfully created is the special LTR packet created by the second node, the second node may establish a normal LTR packet and a special LTR packet. When the second node receives the conventional LTM message sent by the first node, the second node replies a conventional LTR message according to the conventional LTM message; when the second node receives the special LTM message sent by the first node, the second node replies a special LTR message according to the special LTM message.

It will be understood by those skilled in the art that the conventional LTR packet is a packet that is required to be used in the related art to execute the LT function, and in the LT function, a conventional LTR packet may be replied after receiving the conventional LTM packet for checking an end-to-end routing path between nodes.

In an embodiment, the functional response packet carrying the second information indicating that the MIP is successfully created may be obtained by modifying an existing format of a related packet, such as a special LTR packet, may be obtained by modifying a conventional LTR packet, for example, by extending a new field structure in the conventional LTR packet to carry the second information indicating that the MIP is successfully created, or by redefining a field structure in the conventional LTR packet to carry the second information indicating that the MIP is successfully created, which is not limited in this embodiment. To illustrate by way of a specific example, referring to fig. 5, fig. 5 is a schematic structural diagram of a special LTR message provided in an embodiment, in the special LTR message structure, an ethernet message header and LTR message content are included, where main fields of the message structure are explained as follows:

DMAC: used for expressing the destination address, and is encapsulated in the Ethernet message header;

SMAC: the value of the DMAC field is corresponding to the value of the DMAC field of the special LTM packet in the above embodiment;

type: for representing a type;

MD level: for indicating a level of maintenance domain;

OpCode: the message coding unit is used for representing message coding, and when the message is an LTR message, the value is 0x 04;

additional LTM TLVs: an additional TLV field is indicated for holding second information related to the creation of the MIP.

It should be noted that the explanation of other fields in the special LTR message structure is the same as the explanation of corresponding fields contained in the LTR message in the related art, and therefore, the explanation is not repeated here.

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

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

step S400, when the function response packet does not carry the second information indicating that the MIP is successfully created, the first node reports the cached second information to the network manager.

In an embodiment, in a case that the first node caches the second information carried in the functional response message for indicating that the MIP is successfully created, if the first node receives a functional response message which does not carry the second information for indicating that the MIP is successfully created, for example, the first node receives an LTR message which does not carry the second information, it indicates that the LTR message is a normal LTR message, and the normal LTR message is from an opposite MEP of the first node, at this time, it indicates that the functional trigger message sent by the first node has been forwarded to the opposite MEP, and all intermediate nodes have completed creating the MIP, so that the first node reports the cached second information to a network manager, for example, information such as addresses of the node creating the MIP, and the like to the network manager, so that it can report whether each intermediate node has successfully created the MIP through the network manager or not, and the network manager can also acquire the related information of the middle nodes in the whole maintenance domain, so that the network manager can manage the whole maintenance domain conveniently.

In addition, in an embodiment, the second information includes location information of a node that creates the MIP and flag information indicating success or failure of MIP creation.

In an embodiment, the location information of the node creating the MIP and the flag information indicating the success or failure of MIP creation may be configured in the message structure of the functional response message, for example, in the Additional LTM TLVs field of the special LTR message structure in the embodiment shown in fig. 5. The location information of the node creating the MIP may include at least one of information such as a network element name, a rack number, a sub-rack number, and a slot number, and this embodiment is not limited in particular. In addition, the flag information used for indicating whether the MIP is successfully or unsuccessfully created may be a single identification information used for indicating whether the ingress port of the node successfully creates the MIP, may also be a single identification information used for indicating whether the egress port of the node successfully creates the MIP, and may also include multiple identification information used for indicating whether the ingress port of the node and the egress port successfully create the MIP, which is not specifically limited in this embodiment. When the first node reports the positioning information and the mark information to the network manager, the network manager can know whether each intermediate node successfully creates the MIP, and can acquire the related information of the intermediate nodes in the whole maintenance domain through the network manager, so that the management of the whole maintenance domain by the network manager can be facilitated.

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

step S510, the second node receives a function triggering message sent by the first node, wherein the function triggering message carries first information used for indicating a request for establishing MIP;

in step S520, the second node creates MIP according to the first information.

In an embodiment, the function trigger packet may be a special LTM packet adapted to execute the LT function, or may be a special LBM packet adapted to execute the LB function. It should be noted that, whether the function trigger packet is a special LTM packet or a special LBM packet, the function trigger packet carries first information indicating that the MIP is requested to be created.

In an embodiment, it is assumed that a group of peer MEPs is established between a first node and a third node, and when executing an LT function, a MIP needs to be created at a second node between the first node and the third node, and when the second node receives a special LTM packet sent by the first node, because the special LTM packet carries first information indicating that it is requested to create the MIP, the second node may create the MIP under the trigger of the first information, that is, the second node may automatically create the MIP according to the first information in the special LTM packet, so that a burden of manually creating the MIP can be reduced, and efficiency of creating the MIP is improved.

In an embodiment, the function trigger packet carrying the first information indicating that the MIP is requested to be created may be obtained by improving an existing format of a related packet, for example, a special LTM packet, and may be obtained by improving a conventional LTM packet, for example, by extending a new field structure in the conventional LTM packet to carry the first information indicating that the MIP is requested to be created, or by redefining the field structure in the conventional LTM packet to carry the first information indicating that the MIP is requested to be created, which is not limited in this embodiment.

It should be noted that, the specific structure and the specific meaning of the special LTM packet in this embodiment are consistent with the specific structure and the specific meaning of the special LTM packet in the embodiment shown in fig. 3, and for the explanation of the specific structure and the specific meaning of the special LTM packet in this embodiment, reference may be made to the explanation of the specific structure and the specific meaning of the special LTM packet in the embodiment shown in fig. 3, which is not described herein again.

step S530, determine the port and forward the function trigger packet.

In one embodiment, when the second node receives the function trigger packet sent by the first node, the second node first determines whether the content in the function trigger packet carries an address of the second node, for example to 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 indicates that the second node is an intermediate node between a set of peer MEPs, therefore, the second node will create the MIP according to the first information which is carried in the function trigger message and used for indicating the request to create the MIP, after finishing the creation of the MIP, the second node further determines an egress port and forwards the function trigger packet to the next node, so that the function trigger packet can flow through all intermediate nodes between the peer MEPs, so that all intermediate nodes can create the MIP according to the first information in the function trigger message.

It should be noted that, in the process of sending the function trigger packet to the opposite end MEP by the first node, if the intermediate node or the opposite end MEP receives the function trigger packet, a function response packet is replied to the first node, and if the intermediate node receives the function response packet, the intermediate node determines an output port and forwards the function response packet, and does not perform relevant processing according to the function response packet, that is, the intermediate node transparently transmits the function response packet.

In addition, it should be noted that, if the opposite end MEP (for example, the third node in the embodiment shown in fig. 1) receives the function trigger packet sent by the first node, the opposite end MEP may first determine whether the content of the Target MAC field in the function trigger packet is the address of the current node, if the content of the Target MAC field is the address of the current node, the opposite end MEP may first determine whether an MEP corresponding to the function trigger packet exists on the corresponding flow point, and if so, it indicates that the current node is a Target node to which the function trigger packet needs to be transmitted, at this time, the opposite end MEP may reply a function response packet that does not carry the second information related to the MIP to be created to the first node, and stop forwarding the function trigger packet. In addition, if the opposite end MEP determines that there is no MEP corresponding to the function trigger packet at the corresponding flow point, the opposite end MEP will directly discard the function trigger packet.

In an embodiment, the function trigger packet further carries at least information such as a level parameter and a virtual local area network parameter for creating 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 vlan parameter may be stored in the ethernet header in the special LTM message structure of the embodiment shown in fig. 3. When the second node receives the function trigger message sent by the first node, the second node can automatically create the MIP according to the level parameters, the virtual local area network parameters and other information in the function trigger message, so that the burden of manually creating the MIP can be reduced, and the MIP creating efficiency is improved.

Referring also to fig. 7, in an embodiment, step S520 includes, but is not limited to, the following steps:

step S521, the second node acquires the level parameter and the virtual local area network parameter in the function triggering message according to the first information;

in step S522, the second node creates MIP at the ingress port and the egress port of the second node according to the level parameter and the vlan parameter.

In an embodiment, after receiving the function trigger packet sent by the first node, the second node may first determine whether the function trigger packet carries first information indicating a request to create the MIP, and if the function trigger packet carries the first information, the second node may analyze and obtain a level parameter and a virtual local area network parameter in the function trigger packet, and automatically create the 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. It should be noted that the egress port of the MIP created in the second node may be obtained according to information such as a Media Access Control Address (MAC) table in the second node.

Furthermore, in an embodiment, when the second node creates MIPs at its ingress port and egress port, respectively, if the corresponding MIPs already exist, the second node does not perform a specific creation operation and considers that the creation has been successful.

step S540, the second node sends a functional response packet carrying the second information for indicating that the MIP is successfully created to the first node, so that the first node caches or reports the second information to the network manager.

In an embodiment, the function response message may be an LTR message adapted to perform the LT function, and may also be an LBR message adapted to perform the LB function. It should be noted that the functional response packet carrying the second information indicating that the MIP is successfully created is a special packet different from the conventional LTR packet or the conventional LBR packet, and when the functional response packet carries the second information indicating that the MIP is successfully created, the functional response packet may be the special LTR packet or the special LBR packet.

In an embodiment, after the second node creates the MIP according to the function trigger packet sent by the first node, the second node replies a function response packet to the first node, after the first node receives the function response packet, the first node parses the function response packet, and if the function response packet carries second information used for indicating that the MIP is successfully created, that is, the second node has successfully created the MIP, at this time, the first node may cache the second information in the received function response packet, or directly report the second information in the function response packet to the network manager.

In an embodiment, the functional response packet carrying the second information indicating that the MIP is successfully created may be obtained by modifying an existing format of a related packet, such as a special LTR packet, may be obtained by modifying a conventional LTR packet, for example, by extending a new field structure in the conventional LTR packet to carry the second information indicating that the MIP is successfully created, or by redefining a field structure in the conventional LTR packet to carry the second information indicating that the MIP is successfully created, which is not limited in this embodiment.

It should be noted 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. 5, and for the explanation of the specific structure and specific meaning of the special LTR message in this embodiment, reference may be made to the explanation of the specific structure and specific meaning of the special LTR message in the embodiment shown in fig. 5, which is not described herein again.

For the method for creating an intermediate point of a maintenance entity group provided in the foregoing embodiments, the following detailed description is made by using specific examples:

example one:

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, where the network topology includes a first node 100, a second node 200, a third node 300, and a fourth node 400, and 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 create a set of peer MEPs, and the second node 200 and the third node 300 are intermediate nodes between the set of peer MEPs, and when an LB function or an LT function needs to be performed within the maintenance domain of the first node 100, MIP needs to be created at 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 packet (the content of the DMAC field in the packet is 01-80-C2-00-40, and the content of other fields is the same as the conventional LTM packet) to the fourth node 400, the special LTM packet is first transmitted to the second node 200, when the second node 200 determines that the special LTM packet conforms to the rule, that is, the second node 200 determines that the content of the DMAC field in the special LTM packet is 01-80-C2-00-40, the second node 200 parses and obtains the information such as the level parameter and the virtual local area network parameter in the special LTM packet, and creates an MIP at the ingress port and the egress port of the second node 200, respectively, and when the creation of the MIP is completed, the second node 200 replies a special LTR packet to the first node 100, where the special LTR packet carries the network element name, the DMAC, the content of the DMAC field in the packet is 01-80-C2-00-40, and the content of other fields in the general LTM packet is the same as the normal LTM packet Rack number, sub-rack number, slot number, flag information for indicating whether the ingress port and egress port of the second node 200 successfully create MIP, and the like, and then the second node 200 determines the egress port transmitting the special LTM packet and forwards the special LTM packet to the third node 300 through the egress port; when the third node 300 receives the special LTM packet forwarded by the second node 200, the third node 300 performs the same processing as the second node 200, and forwards the special LTM packet to the fourth node 400; when the fourth node 400 receives the special LTM packet, the fourth node 400 determines that the content of the Target MAC field in the special LTM packet is the MAC address of the fourth node 400, so that the fourth node 400 replies a regular LTR packet to the first node 100 and stops forwarding the special LTM packet.

When the first node 100 acquires the special LTR messages sent by the second node 200 and the third node 300 within a preset time period, the first node 100 caches the location information of the node that creates the MIP and the flag information indicating success or failure of MIP creation, which are carried in the special LTR messages, and when the first node 100 receives the conventional LTR message sent by the fourth node 400, the first node 100 reports all cached information to the network manager.

Example two:

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, where the network topology includes a first node 100, a second node 200, a third node 300, and a fourth node 400, and 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 create a point-to-multipoint MEP, specifically, the first node 100 and the third node 300 are a set of peer MEPs, the first node 100 and the fourth node 400 are another set of peer MEPs, the second node 200 is an intermediate node between the first node 100 and the third node 300, and when an LB function or an LT function needs to be performed in a maintenance domain in which the first node 100 and the third node 300 are located, a MIP needs to be created in the second node 200.

When the LT function needs to be executed, the first node 100 sends a special LTM packet (the content of the DMAC field in the packet is 01-80-C2-00-40, and the content of other fields is the same as the conventional LTM packet) to the third node 300, the special LTM packet is first transmitted to the second node 200, when the second node 200 determines that the special LTM packet conforms to the rule, that is, the second node 200 determines that the content of the DMAC field in the special LTM packet is 01-80-C2-00-40, the second node 200 parses and obtains the information such as the level parameter and the virtual local area network parameter in the special LTM packet, and creates an MIP at the ingress port and the egress port of the second node 200, respectively, and when the creation of the MIP is completed, the second node 200 replies a special LTR packet to the first node 100, where the special LTR packet carries the network element name, the DMAC field, and the content of the other fields in the special LTM packet is the same as the conventional LTM packet, and when the creation of the special LTM packet is completed, the second node 200, Rack number, sub-rack number, slot number, flag information for indicating whether the ingress port and egress port of the second node 200 successfully create MIP, and the like, and then the second node 200 determines the egress port transmitting the special LTM packet and forwards the special LTM packet to the third node 300 through the egress port; when the third node 300 receives the special LTM packet, the third node 300 determines that the content of the Target MAC field in the special LTM packet is the MAC address of the third node 300, so that the third node 300 replies a regular LTR packet to the first node 100 and stops forwarding the special LTM packet.

When the first node 100 acquires the special LTR message sent by the second node 200 within a preset time period, the first node 100 caches the location information of the node that creates the MIP and the flag information indicating success or failure of MIP creation, which are carried in the special LTR message, and when the first node 100 receives the conventional LTR message sent by the third node 300, the first node 100 reports all cached information to the network manager.

Additionally, one embodiment of the present invention provides a node, comprising: a memory, a processor, and a computer program stored on the memory and executable on the processor.

The processor and memory may be connected by a bus or other means.

It should be noted that the node in this embodiment may be applied to the nodes in the embodiments shown in fig. 1, fig. 8, or fig. 9, the node in this embodiment can form a part of the network topology in the embodiments shown in fig. 1, fig. 8, or fig. 9, and these embodiments all belong to the same inventive concept, so these embodiments have the same implementation principle and technical effect, and are not described in detail here.

The non-transitory software programs and instructions required to implement the maintenance entity group intermediate point creation method of the above-described embodiment are stored in a memory, and when executed by a processor, perform the maintenance entity group intermediate point creation method of the above-described embodiment, for example, performing the above-described method steps S100 in fig. 2, method steps S200 to S300 in fig. 4, method steps S510 to S520 in fig. 6, or method steps S521 to S522 in fig. 7.

The above-described embodiments of the apparatus are merely illustrative, wherein the units illustrated as separate components may or may not be physically separate, i.e. may be located in one place, or may also be distributed over a plurality of network elements. Some or all of the modules may be selected according to actual needs to achieve the purpose of the solution of the present embodiment.

Furthermore, an embodiment of the present invention further provides a computer-readable storage medium, which stores computer-executable instructions, which are executed by a processor or a controller, for example, by a processor in the node embodiment, and can cause the processor to execute the method for creating the intermediate point of the maintenance entity group in the node embodiment, for example, execute the method steps S100 in fig. 2, S200 to S300 in fig. 4, S510 to S520 in fig. 6, or S521 to S522 in fig. 7 described above.

One of ordinary skill in the art will appreciate that all or some of the steps, systems, and methods disclosed above may be implemented as software, firmware, hardware, and suitable combinations thereof. Some or all of the physical components may be implemented as software executed by a processor, such as a central processing unit, digital signal processor, or microprocessor, or as hardware, or as an integrated circuit, such as an application specific integrated circuit. Such software may be distributed on computer readable media, which may include computer storage media (or non-transitory media) and communication media (or transitory media). The term computer storage media includes volatile and nonvolatile, removable and non-removable media implemented in any method or technology for storage of information such as computer readable instructions, data structures, program modules or other data, as is well known to those of ordinary skill in the art. 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 tape, magnetic disk storage or other magnetic storage devices, or any other medium which can be used to store the desired information and which can accessed by a computer. In addition, 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 includes any information delivery media as known to those skilled in the art.

While the preferred embodiments of the present invention have been described in detail, it will be understood by those skilled in the art that the foregoing and various other changes, omissions and deviations in the form and detail thereof may be made without departing from the scope of this invention.

Claims

1. A method of maintaining an entity group intermediate point creation, comprising:

2. The method of claim 1, wherein the function trigger packet further carries a level parameter and a virtual local area network parameter for creating the MIP.

3. The method of claim 1, further comprising:

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

and when the function response message carries second information used for indicating that the MIP is successfully created, the first node caches the second information.

4. The method of claim 3, further comprising:

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

5. The method of claim 3, further comprising:

and when the function response message carries second information used for 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, wherein the second information comprises location information of a node which creates the MIP and flag information for indicating success or failure of MIP creation.

7. A method of maintaining an entity group intermediate point creation, comprising:

the second node creates MIP according to the first information.

8. The method of claim 7, wherein the function trigger packet further carries a level parameter and a virtual local area network parameter for creating the MIP.

9. The method of claim 8, wherein the second node creates MIPs based on the first information, comprising:

the second node acquires the level parameter and the virtual local area network parameter in the function triggering message according to the first information;

and the second node respectively creates MIPs at an input port and an output port of the second node according to the level parameters and the virtual local area network parameters.

10. The method of claim 7, further comprising:

and the second node sends a function response message carrying second information for indicating that the MIP is successfully created to the first node so that the first node caches or reports the second information to a network manager.

11. The method according to claim 10, wherein the second information includes location information of a node which creates the MIP and flag information indicating success or failure of MIP creation.

12. A node, comprising: memory, processor and computer program stored on the memory and executable on the processor, characterized in that the processor when executing the computer program implements a method for creating a maintenance entity group intermediate point according to any of claims 1 to 6 or implements a method for creating a maintenance entity group intermediate point according to any of claims 7 to 11.

13. A computer-readable storage medium storing computer-executable instructions for performing the maintenance entity group intermediate point creation method of any one of claims 1 to 6 or performing the maintenance entity group intermediate point creation method of any one of claims 7 to 11.