WO2016101546A1

WO2016101546A1 - Method and device for implementing operations, administration and maintenance function

Info

Publication number: WO2016101546A1
Application number: PCT/CN2015/080709
Authority: WO
Inventors: 孙德胜; 赵福川
Original assignee: 中兴通讯股份有限公司
Priority date: 2014-12-23
Filing date: 2015-06-03
Publication date: 2016-06-30
Also published as: CN105790988B; CN105790988A

Abstract

Disclosed are a method and device for implementing an operations, administration and maintenance function. The method for implementing an operations, administration and maintenance function comprises: a controller carries OAM configuration information in a configuration packet, the OAM configuration information being used for instructing a forwarding device to carry out an OAM function of a path, the path being a path between forwarding devices; the controller sends the configuration packet to the forwarding device. Via the present invention, an OAM function is implemented on a forwarding device level, thereby satisfying OAM high real-time performance requirements.

Description

Method and device for implementing operation and maintenance management function

Technical field

The present invention relates to the field of communications, and in particular to an implementation method and apparatus for an operation and maintenance management function.

Background technique

Software Defined Network (SDN) is a research hotspot in the field of communication in recent years. The International Standards Organization Open Network Forum (ONF) formulates SDN related standard recommendations, focusing on decoupling between controllers (controllers, CP) and forwarding devices (forwarding devices, or switchers). The interface between the forwarding plane and the forwarding plane facilitates the joint networking of controllers and forwarding devices from different vendors.

The ONF has now released the OpenFlow Switch Specification for the interface between the controller and the forwarding plane. The protocol implemented based on this interface specification is the Openflow protocol. ONF has organized a number of interoperability tests in recent years, and is mature in supporting Layer 2 services and Layer 2 Virtual Private Network (VPN) services.

1 is a schematic structural diagram of an SDN network according to the related art. As shown in FIG. 1, an Openflow channel is used for Openflow protocol interaction between a controller and a forwarding device. After the protocol message sent by the controller is sent to the forwarding device, the protocol processing component of the forwarding device terminates the protocol to extract the content information carried by the protocol packet, and forwards the content information to the corresponding component. Similarly, the information sent to the controller by the relevant components in the forwarding device needs to be first passed to the protocol processing component packaged as an Openflow protocol and sent to the controller.

The Openflow protocol defines a series of messages, including controller-to-switch, asynchronous, and symmetric. Each class defines many types. The controller-to-switch message is initiated by the controller to manage or obtain the forwarding device status. The asynchronous message is initiated by the forwarding device to notify the controller of the network event or forwarding device status change; the symmetric message may be forwarded by the device or controlled. Launched.

In the aspect of the operation, maintenance, and maintenance (OAM), as shown in Figure 2, the controller sends a packet-out message in the controller-to-switch category and sends it through the Openflow protocol channel. To the forwarding device. The forwarding device sends the packet according to the specified port of the message. After receiving the message, the receiving device forwards the packet statistics and error packets according to the message indication, and sends the packet to the protocol processing component. The packet is encapsulated as a Packet-in message through the Openflow channel. Send to controller.

However, the above-mentioned mechanism is to perform message exchange between the controller and the forwarding device, and is not suitable for periodic fast transmission and reception, and is used for protection switching or other destination message packets. This fast packet generally needs to be at the forwarding device level. Fast send and receive. For example, the MPLS-TP (Packet Transmission Technical Standard of the International Standard Specification such as ITU-T ITU-T) requires a Fast Connectivity Detection Message (CCM) that supports 3.33 milliseconds of periodic transmission and reception.

Summary of the invention

The embodiment of the invention provides a method and a device for implementing an operation and maintenance management function, so as to at least solve the problem that the path OAM function cannot meet the high real-time requirement in the related art.

According to an aspect of the embodiments of the present invention, an implementation of an operation and maintenance management function is provided, including: the controller carries OAM configuration information in a configuration packet, where the OAM configuration information is used to indicate an OAM function of the path of the forwarding device implementation. The path is a path between the forwarding devices; the controller sends the configuration packet to the forwarding device.

Further, the foregoing OAM configuration information includes at least one of the following: the identifier information, the operation type, the feature information, and the port information, where the identifier information is used to identify an instance of the OAM function, and is different from other OAM instances that are in effect at the same time; The type used to indicate the OAM function; the feature information is used to indicate a parameter corresponding to the OAM function; the port information is used to indicate the local port to which the OAM function is bound.

Further, the foregoing feature information includes: an OAM message packet sending period, where the OAM message packet sending period is used to indicate a period in which the forwarding device sends a packet to the forwarding device at the other end of the path.

Further, the foregoing OAM operation type includes at least one of the following: adding, modifying, suspending, starting, or deleting the OAM function.

Further, the sending, by the controller, the configuration packet to the forwarding device includes at least one of the following: sending a configuration packet to the first-end forwarding device and/or the tail-end forwarding device of the bidirectional forwarding path, where the port information carried in the configuration packet includes Outbound port information and inbound port information, the outbound port information indicates the local port that sends the packet, the inbound port information indicates the local port that receives the packet, and the first endpoint forwarding device that sends the first configuration packet to the first endpoint forwarding path, and/or The second configuration packet is sent to the tail-end forwarding device of the one-way forwarding path, where the port information carried in the first configuration packet is the outbound port information, and the port information carried in the second configuration packet is the ingress port information. .

Further, the foregoing configuration packet is a packet type based on a Packet-out message extension.

Further, the foregoing OAM configuration information is carried in at least one of the following: a port field, an action set field, a reserved field, or a data field.

According to another aspect of the present invention, a method for implementing an operation and maintenance management function is provided, including: a forwarding device receiving a configuration message sent by a controller; and a forwarding device acquiring operation and maintenance management OAM configuration information from the configuration message, The OAM configuration information is used to indicate the OAM function of the path of the forwarding device, and the path is the path between the forwarding devices. The forwarding device performs the OAM function of the path according to the OAM configuration information.

Further, the OAM function of the forwarding device performing the path according to the OAM configuration information includes at least one of the following:

When the type of the OAM configuration information indicates that the type of the OAM function is new, the timer corresponding to the OAM message packet period is started according to the OAM message packet period indicated by the feature information in the OAM configuration information, and the timer is sent to the other end of the path. The forwarding device sends an OAM message and/or an OAM message sent by the forwarding device at the other end of the receiving path;

When the operation type indicates that the type of the OAM function is modified, the timer of the OAM message packet is stopped according to the OAM message packet period indicated by the feature information, and the timer corresponding to the OAM message packet period is started, and the forwarding device is sent to the other end of the path. Sending an OAM message and/or an OAM message sent by the forwarding device at the other end of the receiving path;

When the type of the operation indicates that the type of the OAM function is paused, the timer of the OAM message is suspended, and the OAM message is suspended and/or received.

When the type of the operation indicates that the type of the OAM function is restarted, the timer for restarting the OAM message is sent to the forwarding device at the other end of the path, and the OAM message sent by the forwarding device at the other end of the path is received.

When the type of the OAM function is deleted, the timer of the OAM message is deleted, and the identifier information in the OAM configuration information is deleted.

Further, when the binding object of the OAM configuration information is a unidirectional forwarding path, if the forwarding device is the first endpoint of the path, the forwarding device sends an OAM message to the forwarding device at the other end of the path according to the operation type; The end device of the forwarding device forwards the OAM message sent by the device to the other end of the receiving path according to the operation type.

Further, when the binding object of the OAM configuration information is a bidirectional forwarding path, the forwarding device sends an OAM message to the forwarding device at the other end of the path according to the operation type, and the other end of the path forwards the OAM message sent by the device.

Further, the method further includes: the forwarding device binding the corresponding local port according to the port information in the OAM configuration information; wherein the inflow port is identified by the flow table entry information, and the port is identified by the group table information, and the local port includes the physical port. Port and / or logical port.

According to still another aspect of the embodiments of the present invention, an apparatus for implementing an operation and maintenance management function is provided, including: a processing module, configured to carry operation and maintenance management OAM configuration information in a configuration message, where OAM configuration information is used to indicate The forwarding device implements the OAM function of the path, and the path is a path between the forwarding devices. The sending module is configured to send the configuration packet to the forwarding device.

Further, the foregoing OAM configuration information includes at least one of the following: the identifier information, the operation type, the feature information, and the port information, where the identifier information is used to identify an instance of the OAM function, and is different from other OAM instances that are effective at the same time; The type used to indicate the OAM function; the feature information is used to indicate a parameter corresponding to the OAM function; the port information is used to indicate the local port to which the OAM function is bound.

Further, the OAM operation type includes at least one of the following: adding, modifying, suspending, starting, or deleting the OAM function.

Further, the sending module includes at least one of the following: the first sending unit is configured to send a configuration packet to the first-end forwarding device and/or the tail-end forwarding device of the bidirectional forwarding path, where the port information carried in the packet is configured. Including the outbound port information and the ingress port information, the outbound port information indicates the local port that sends the packet, the ingress port information indicates the local port that receives the packet, and the second sending unit is configured to send the first to the first endpoint forwarding device of the one-way forwarding path. A configuration packet sends a second configuration packet to the tail-end forwarding device of the one-way forwarding path, where the port information carried in the first configuration packet is the outbound port information, and the port information carried in the second configuration packet is the ingress port. information.

Further, the processing module is configured to carry the OAM configuration information in at least one of the following: a port field, an action set field, a reserved field, or a data field.

According to still another aspect of the embodiments of the present invention, an apparatus for implementing an operation and maintenance management function includes: a receiving module configured to receive a configuration message sent by a controller; and an obtaining module configured to obtain an operation from the configuration message Maintain and manage OAM configuration information, where OAM configuration information is used to indicate the forwarding device implementation path. The OAM function, the path is the path between the forwarding devices; the execution module is set to perform the OAM function of the path according to the OAM configuration information.

Further, the foregoing execution module includes at least one of the following:

The first execution unit is configured to start the timing corresponding to the OAM message packet period according to the OAM message packet period indicated by the feature information in the OAM configuration information, when the type of the OAM configuration information indicates that the type of the OAM function is new. The device sends an OAM message to the forwarding device at the other end of the path and/or an OAM message sent by the forwarding device at the other end of the path;

The second execution unit is configured to stop the timer of the OAM message packet and start the timer corresponding to the OAM message packet period according to the OAM message packet period indicated by the feature information, when the operation type indicates that the type of the OAM function is modified. Sending an OAM message and/or an OAM message sent by the forwarding device at the other end of the path to the forwarding device at the other end of the path;

a third execution unit, configured to suspend the timer of the OAM message, suspend sending and/or receiving the OAM message, when the operation type indicates that the type of the OAM function is paused;

The fourth execution unit is configured to: when the operation type indicates that the type of the OAM function is restarted, restart the timer of the OAM message, and send the OAM message to the forwarding device at the other end of the path and/or the forwarding device at the other end of the receiving path. The sent OAM message packet;

The fifth execution unit is configured to cancel the timer of the OAM message when the operation type indicates that the type of the OAM function is deleted, and delete the identifier information corresponding to the OAM instance in the OAM configuration information.

Further, when the binding object of the OAM configuration information is a one-way forwarding path, if the forwarding device is the first endpoint of the path, the execution module is configured to send an OAM message to the forwarding device at the other end of the path according to the operation type; The device is the trailing edge of the path, and the execution module is configured to forward the OAM message sent by the device to the other end of the receiving path according to the operation type.

Further, when the binding object of the OAM configuration information is a bidirectional forwarding path, the execution module is configured to send an OAM message to the forwarding device of the other end of the path according to the operation type, and the other end of the path is forwarded to the OAM message sent by the device. Message.

Further, the foregoing execution module is further configured to bind the corresponding local port according to the port information in the OAM configuration information; wherein the inflow port is identified by the flow table entry information, and the port is identified by the group table information, and the local port includes the physical port and / or logical port.

Further, the foregoing configuration packet is a packet type based on a Packet-out message extension. .

According to the embodiment of the present invention, the controller carries the OAM configuration information for indicating the OAM function of the path of the forwarding device in the configuration packet, and sends the configuration packet to the forwarding device, thereby instructing the forwarding device to implement the OAM function of the path. The OAM function is implemented at the device level to avoid the problem of low real-time performance caused by the interaction between the forwarding device and the controller, and the high-real-time requirement of the path OAM function can be achieved.

DRAWINGS

The drawings described herein are intended to provide a further understanding of the invention, and are intended to be a part of the invention. In the drawing:

1 is a schematic structural diagram of an SDN network according to the related art;

2 is a schematic diagram of implementation of an OAM function according to the related art;

3 is a flowchart 1 of an implementation method of an operation and maintenance management function according to an embodiment of the present invention;

4 is a second flowchart of an implementation method of an operation and maintenance management function according to an embodiment of the present invention;

5 is a structural block diagram 1 of an apparatus for implementing an operation and maintenance management function according to an embodiment of the present invention;

FIG. 6 is a structural block diagram of an optional transmitting module 20 according to an embodiment of the present invention; FIG.

7 is a structural block diagram 2 of an apparatus for implementing an operation and maintenance management function according to an embodiment of the present invention;

FIG. 8 is a structural block diagram of an optional acquisition module 40 according to an embodiment of the present invention;

9 is a block diagram showing the structure of an optional execution module 50 in accordance with an embodiment of the present invention;

10 is a schematic diagram of a Packet-out message according to an embodiment of the present invention;

11 is a schematic diagram of an optional bidirectional forwarding path OAM configured according to an embodiment of the present invention;

FIG. 12 is a schematic diagram of optionally configuring a one-way forwarding path OAM according to an embodiment of the present invention; FIG.

FIG. 13 is a schematic diagram of an OAM of an endpoint forwarding device configured to configure only a bidirectional forwarding path according to an embodiment of the present invention; FIG.

FIG. 14 is a schematic diagram of an OAM configured to configure only a one-way forwarding path first-end forwarding device according to an embodiment of the present invention; FIG.

FIG. 15 is a schematic diagram of an OAM configured to configure only a one-way forwarding path tail endpoint forwarding device according to an embodiment of the present invention.

detailed description

The invention will be described in detail below with reference to the drawings in conjunction with the embodiments. It should be noted that the embodiments in the present application and the features in the embodiments may be combined with each other without conflict.

In this embodiment, a method for implementing an operation and maintenance management function is provided. FIG. 3 is a flowchart 1 of an implementation method of an operation and maintenance management function according to an embodiment of the present invention. As shown in FIG. 3, the process includes the following steps:

In the step S302, the controller carries the OAM configuration information in the configuration packet, where the OAM configuration information is used to indicate the OAM function of the path of the forwarding device, and the path is a path between the forwarding devices.

Step S304, the controller sends the configuration packet to the forwarding device.

In an optional implementation manner of the embodiment of the present invention, the foregoing OAM configuration information includes at least one of the following: the identifier information, the operation type, the feature information, and the port information, where the identifier information is used to identify an instance of the OAM function, and The other OAM instances that are in effect at the same time are distinguished; the feature information is used to indicate the parameter corresponding to the OAM function; the port information is used to indicate the local port to which the OAM function is bound.

In an optional implementation manner of the embodiment of the present invention, the foregoing feature information includes: an OAM message packet sending period, where the OAM message packet sending period is used to instruct the forwarding device to send a packet to the forwarding device at the other end of the path. cycle.

In an optional implementation manner of the embodiment of the present invention, the foregoing OAM operation type includes at least one of the following: adding, modifying, suspending, starting, or deleting an OAM function.

In an optional implementation manner of the embodiment of the present invention, the controller sends a configuration packet to the first-end forwarding device and/or the tail-end forwarding device of the bidirectional forwarding path, where the configuration is carried in the packet. The port information includes the outbound port information and the inbound port information. The outbound port information indicates the local port that sends the packet. The inbound port information indicates the local port that receives the packet. For the one-way forwarding path, the controller sends the first configuration packet to the first-end forwarding device of the one-way forwarding path, and/or sends the second configuration packet to the tail-end forwarding device of the one-way forwarding path, where the first The port information carried in the configuration packet is the outbound port information, and the port information carried in the second configuration packet is the ingress port information. Optionally, the ingress port is identified by the flow table entry information, and the port is identified by the group table information.

In an optional implementation manner of the embodiment of the present invention, the configuration packet is a packet type based on the packet-out message extension. Of course, in order to achieve the foregoing object, other messages may also be conceived, and the embodiment of the present invention is not Limited to this. One advantage of the Packet-out message is that it does not require additional messages to be added to the existing messages of the Openflow protocol.

In an optional implementation manner of the embodiment of the present invention, the OAM configuration information is carried by the unused field in the packet-out message. For example, the OAM configuration information is carried in at least one of the following in the Packet-out message: The port field, the action set field, the reserved field, or the data field, of course, other fields are also conceivable, and the embodiment of the present invention is not limited thereto, and is exemplified herein.

In the embodiment, another method for implementing the operation and maintenance management function is provided. FIG. 4 is a second flowchart of the method for implementing the operation and maintenance management function according to the embodiment of the present invention. As shown in FIG. 4, the flow includes the following steps. step:

Step S402, the forwarding device receives the configuration packet sent by the controller.

In the step S404, the forwarding device obtains the OAM configuration information from the configuration packet, where the OAM configuration information is used to indicate the OAM function of the forwarding device to implement the path, and the path is the path between the forwarding devices.

Step S406, the forwarding device performs the OAM function of the path according to the OAM configuration information.

According to the embodiment of the present invention, the forwarding device performs the OAM function of the path according to the OAM configuration information sent by the controller, which avoids the problem of low real-time performance caused by the interaction between the controller and the forwarding device, and can meet the requirements of high real-time performance.

In an optional implementation manner of the embodiment of the present invention, the forwarding device determines, according to the indication information carried in the packet, whether the received packet is a configuration packet, and when the identifier information indicates that the packet is a configuration packet, the forwarding device Obtain OAM configuration information from the configuration packet.

In an optional implementation manner of the embodiment of the present invention, the OAM configuration information may further include at least one of an operation type and a feature information, where the operation type is used to indicate a type of the OAM function, and the feature information is used to indicate the OAM function. Corresponding parameters.

Optionally, the foregoing step S406 may include at least one of the following:

In an optional implementation manner of the embodiment of the present invention, when the binding object of the OAM configuration information is a one-way forwarding path, if the forwarding device is the first endpoint of the path, the forwarding device sends the forwarding device to the other end of the path according to the operation type. The OAM message packet; if the forwarding device is the trailing edge of the path, the forwarding device forwards the OAM message sent by the device according to the operation type.

Optionally, when the binding object of the OAM configuration information is a bidirectional forwarding path, the forwarding device sends an OAM message to the forwarding device of the other end of the path according to the operation type, and the other end of the path forwards the OAM message sent by the device. .

In an optional implementation manner of the embodiment of the present invention, the method further includes: the forwarding device binding the corresponding local port according to the port information in the OAM configuration information; wherein the inflow port is identified by the flow table entry information, and the group table information is used. The port is identified, and the local port includes a physical port and/or a logical port.

The above ports refer to physical ports, such as Ethernet, OTN or WDM physical ports, or logical ports, such as Ethernet VLAN ports, MPLS or MPLS_TP tunnels or pseudowire ports, and OTN ODUk channel ports.

The above port can be represented by a series of controller-generated feature information, such as the KEY of the Openflow flow table, and the forwarding plane can find the corresponding physical port or logical port according to the KEY to match the flow table.

In an optional implementation manner of the embodiment of the present invention, the configuration packet is a packet type based on a Packet-out message extension. Of course, in order to achieve the above object, other messages are also conceivable, and embodiments of the present invention are not limited thereto. One advantage of the Packet-out message is that it does not require additional messages to be added to the existing messages of the Openflow protocol.

In this embodiment, an apparatus for implementing an operation and maintenance management function is provided. The apparatus is used to implement the foregoing embodiments and preferred embodiments, and details are not described herein. As used below, the term "module" may implement a combination of software and/or hardware of a predetermined function. Although the apparatus described in the following embodiments is preferably implemented in software, hardware, or a combination of software and hardware, is also possible and contemplated.

FIG. 5 is a structural block diagram 1 of an apparatus for implementing an operation and maintenance management function according to an embodiment of the present invention. As shown in FIG. 5, the apparatus may include:

The processing module 10 is configured to carry the operation and maintenance management OAM configuration information in the configuration packet, where the OAM configuration information is used to indicate the OAM function of the forwarding device to implement the path, and the path is a path between the forwarding devices;

The sending module 20 is connected to the processing module 10 and configured to send the configuration packet to the forwarding device.

In an optional implementation manner of the embodiment of the present invention, the foregoing OAM configuration information includes at least one of the following: the identifier information, the operation type, the feature information, and the port information, where the identifier information is used to identify an instance of the OAM function, and at the same time The other OAM instances that are in effect are distinguished; the operation type is used to indicate the type of the OAM function; the feature information is used to indicate the parameter corresponding to the OAM function; and the port information is used to indicate the local port to which the OAM function is bound.

In an optional implementation manner of the embodiment of the present invention, the foregoing feature information includes: an OAM message packet sending period, where the OAM message packet sending period is used to indicate that the forwarding device sends the packet to the forwarding device at the other end of the path. .

In an optional implementation manner of the embodiment of the present invention, the OAM operation type includes at least one of the following: adding, modifying, suspending, starting, or deleting the OAM function.

In an optional implementation manner of the embodiment of the present invention, as shown in FIG. 6, the sending module 20 may include at least one of the following: the first sending unit 210 is configured to forward the device and/or the tail to the first endpoint of the bidirectional forwarding path. The endpoint forwarding device sends a configuration packet, where the port information carried in the configuration packet includes the outbound port information and the inbound port information, the outbound port information indicates the local port that sends the packet, and the inbound port information indicates the local port that receives the packet; The sending unit 220 is configured to send the first configuration packet to the first endpoint forwarding device of the one-way forwarding path, and/or to send the second configuration packet to the tail endpoint forwarding device of the one-way forwarding path, where the first configuration packet is sent The port information carried is the outbound port information, and the port information carried in the second configuration packet is the ingress port information.

In an optional implementation manner of the embodiment of the present invention, the configuration packet is a packet type based on a Packet-out message extension.

In an optional implementation manner of the embodiment of the present invention, the processing module 10 is configured to carry the OAM configuration information in at least one of the following: a port field, an action set field, a reserved field, or a data field.

FIG. 7 is a structural block diagram 2 of an apparatus for implementing an operation and maintenance management function according to an embodiment of the present invention. As shown in FIG. 7, the apparatus includes:

The receiving module 30 is configured to receive a configuration message sent by the controller.

The obtaining module 40 is connected to the receiving module 30 and configured to obtain the OAM configuration information of the operation and maintenance management from the configuration packet, where the OAM configuration information is used to indicate the OAM function of the forwarding device to implement the path, and the path is the path between the forwarding devices.

The execution module 50 is connected to the acquisition module 40 and configured to perform an OAM function of the path according to the OAM configuration information.

In an optional implementation manner of the embodiment of the present invention, as shown in FIG. 8, the receiving module 30 may include: a determining unit 310, configured to determine whether the received packet is configured with a packet; and the forwarding unit 320 is configured to be When the packet is a configuration packet, the configuration packet is forwarded to the obtaining module 40.

In an optional implementation manner of the embodiment of the present invention, as shown in FIG. 9, the foregoing execution module 50 includes at least one of the following:

The first execution unit 510 is configured to start the OAM message packet period according to the OAM message packet period indicated by the feature information in the OAM configuration information, when the type of the OAM configuration information indicates that the type of the OAM function is new. The timer sends an OAM message to the forwarding device at the other end of the path and/or an OAM message sent by the forwarding device at the other end of the path;

The second execution unit 520 is configured to stop the timer of the OAM message packet and start the timer corresponding to the OAM message packet period according to the OAM message packet period indicated by the feature information when the operation type indicates that the type of the OAM function is modified. Sending an OAM message and/or an OAM message sent by the forwarding device at the other end of the path to the forwarding device at the other end of the path;

The third executing unit 530 is configured to suspend the timer of the OAM message, suspend sending and/or receiving the OAM message, when the type of the operation type indicates that the type of the OAM function is paused;

The fourth execution unit 540 is configured to: when the operation type indicates that the type of the OAM function is restarted, restart the timer of the OAM message, and send the OAM message to the forwarding device at the other end of the path and/or the forwarding of the other end of the receiving path. OAM message sent by the device;

The fifth execution unit 550 is configured to cancel the timer of the OAM message when the type of the operation type indicates that the type of the OAM function is deleted, and delete the identifier information corresponding to the OAM instance in the OAM configuration information.

In an optional implementation manner of the embodiment of the present invention, when the binding object of the OAM configuration information is a one-way forwarding path, if the forwarding device is the first endpoint of the path, the executing module 50 is set to another path according to the operation type. The one-end forwarding device sends an OAM message to the device. If the forwarding device is the trailing edge of the path, the executing module 50 is configured to forward the OAM message sent by the device according to the other end of the receiving path.

In an optional implementation manner of the embodiment of the present invention, when the binding object of the OAM configuration information is a bidirectional forwarding path, the executing module 50 is configured to send an OAM message to the forwarding device of the other end of the path according to the operation type, and The other end of the receiving path forwards the OAM message sent by the device.

In an optional implementation manner of the embodiment of the present invention, the executing module 50 is further configured to bind the corresponding local port according to the port information in the OAM configuration information, where the inflow port is identified by the flow table entry information, and the group table information is used. The port is identified, and the local port includes a physical port and/or a logical port.

Alternative embodiments of the embodiments of the present invention are described below.

Alternative embodiment 1

In the optional implementation manner, based on the existing ONF framework, an OAM implementation method is proposed based on the existing standard interface of the OpenFlow Switch Specification, and the fast OAM function that cannot be implemented by the existing SDN standard is solved to meet MPLS-TP. International standard requirements.

The optional implementation provides a method for implementing the OAM function, which is based on the Packet-out message structure of the existing Openflow protocol, and carries the OAM configuration information in the Packet-out message.

As shown in FIG. 10, the Packet-out message generally includes an Openflow protocol header (hereinafter referred to as a header), a port on which the forwarding device sends the message (hereinafter referred to as in_port), and an action set to be executed after the designated forwarding device receives the message (hereinafter referred to as the short message). Actions), reserved or padded bytes (hereinafter referred to as pads) and data fields/message contents (hereinafter referred to as data), all or part of the members.

In this alternative embodiment, the above-mentioned identification information (also referred to as OAM identification), operation type, feature information, port information, and the like are carried using the pad member or extension in_port or extended action or data of the message. After receiving the Packet-out message, the forwarding device identifies whether the packet is an OAM type packet by parsing the pad or the extended in_port of the message or the extended action or data. If the packet is an OAM type, the packet includes the packet content. Other message members within and implement related processing.

For the local port, it is divided into the inbound port and the outbound port; the port can be a physical port, such as a physical port such as Ethernet, OTN or WDM, or a logical port, such as an Ethernet VLAN port, MPLS or MPLS_TP tunnel or pseudo Line port, ODUk channel port of OTN. The software-defined network SDN uses the flow table entry information (including the Table id and match of the Flow Table) to identify the inbound port, and uses the group table information (including the Group id of the group table) to identify the outgoing port.

For the bidirectional forwarding path, the information about the OAM ID, the operation type, and the feature to be received is the same as that of the OAM, the operation type, and the feature. The local port bound to the OAM needs to carry the inbound port and the outbound port.

For the one-way forwarding path, the controller needs to send information such as the identifier, operation type, feature, and outgoing port of the OAM to the forwarding device of the first endpoint of the path, and send information such as the identifier, operation type, feature, and incoming port of the received OAM to the The end of the path forwards the device.

The foregoing method implements the OAM function of the bidirectional forwarding path for the SDN network composed of the controller and the forwarding device, and further includes the following steps:

Step 1: The controller initiates the configuration of the bidirectional forwarding path OAM function, constructs a Packet-out message, and the extended message related member carries the OAM identifier, operation type, feature information, and local port, and sends the first or last end of the bidirectional forwarding path through the Openflow channel. Endpoint forwarding device;

Step 2: After receiving the Packet-out message, the Openflow protocol processing component of the first endpoint or the tail endpoint forwarding device determines whether the OAM type packet is forwarded according to the information carried by the related message member, and then forwards the packet to the OAM component and proceeds to the next step; Process processing required for other Packet-out messages;

Step 3: After receiving the OAM message packet, the OAM component identifies the OAM identifier, binds the local port, the type of operation required to be performed, and the OAM-related feature information, and implements the extended message member.

The controller can send the OAM configuration information to the forwarding device (the first endpoint and the trailing endpoint) simultaneously or separately. In some special cases, such as the SDN network connecting to the traditional network or the different SDN networks, only one forwarding needs to be configured. OAM of the device (first or last endpoint). The above technical solutions cover these scenarios.

The foregoing method implements the OAM function of the one-way forwarding path for the SDN network composed of the controller and the forwarding device, and further includes the following steps:

Step 1: The controller initiates the configuration of the OAM function of the one-way forwarding path, constructs a Packet-out message, and the extended message related member carries the OAM configuration information, and sends the first-end forwarding device to the one-way forwarding path through the Openflow channel;

Step 2: After receiving the Packet-out message, the Openflow protocol processing component of the first-end forwarding device determines whether it is an OAM-type packet according to the information carried by the related message member, and then forwards it to the OAM component and proceeds to the next step; otherwise, according to other Packets -out message required process processing;

Step 3: After receiving the OAM message packet, the OAM component identifies the OAM identifier, the bound local port, the type of operation required to be performed, and the OAM-related feature information, and implements the extended message member.

Step 4: The controller constructs a Packet-out message, and extends the related member of the message, and carries the OAM configuration information of Step 1 and sends the device to the tail endpoint forwarding device of the one-way forwarding path through the Openflow channel;

Step 5: After receiving the Packet-out message, the Openflow protocol processing component of the tail endpoint forwarding device forwards to the OAM component according to whether the information carried by the related message member is an OAM type packet, and then proceeds to the next step; otherwise, according to other Packet- Out process required for out message processing;

Step 6: After receiving the OAM message packet, the OAM component identifies the OAM identifier, the type of operation required to be performed, and the OAM-related feature information, and implements the extended message member.

In some special cases, such as SDN network connection with traditional network, or different SDN network connection, only need to configure OAM of a forwarding device (first endpoint or tail endpoint). The above technical solution covers this scenario.

In the optional implementation manner, the foregoing step identification information (also referred to as an OAM identifier) may be a string of numbers or a string of characters, and the operation type may include adding, modifying, starting, pausing, or deleting, and the feature information includes an OAM sending period, and the like. information.

The type of the OAM type packet may be OAM for forwarding paths such as Ethernet, IP, MPLS, MPLS-TP, PBB, OTN, WDM, and the like.

The foregoing steps extend the information about the OAM identifier, the operation type, and the feature. The extension method includes extending the in_port member or the action member or the member of the pad to add an OAM identifier to distinguish other Packet-out messages. Then expand other unused members, including data, carrying OAM identifiers, operation types, features, and so on.

The above-mentioned bidirectional forwarding path and unidirectional forwarding path generally refer to transmission paths of various layers of communication technologies such as Ethernet, IP, MPLS, MPLS-TP, PBB, OTN, and WDM, such as Ethernet physical layer path and regenerative section of MPLS-TP. Path, tunnel layer path, pseudo-line layer path, etc.; such as OTN physical layer path, regenerator section path, multiplex section path, high-order ODU path, low-order ODU path, etc. of OTN network.

Through the optional implementation manner, the functions of adding, modifying, suspending, starting, or deleting the fast OAM function are completed by extending the definition of the member of the Packet-out message, and the advantages are simple and reliable.

Optional implementation method 2

In this optional implementation manner, in order to solve the problem that the current SDN network cannot complete the fast OAM function, the fast OAM function of the bidirectional and unidirectional forwarding paths is completed through the newly defined Packet-out message based on the existing interface extension.

FIG. 11 is a schematic diagram of an optional configuration of a bidirectional forwarding path OAM according to an embodiment of the present invention; FIG. 12 is a schematic diagram of an optional configuration of a unidirectional forwarding path OAM according to an embodiment of the present invention; FIG. FIG. 14 is a schematic diagram of an OAM configured to configure only one-way forwarding path for a first-end forwarding device according to an embodiment of the present invention; FIG. 15 is a schematic diagram of an OAM according to an embodiment of the present invention. A schematic diagram of an OAM that only configures a unidirectional forwarding path at the end of the endpoint forwarding device.

With reference to FIG. 1, FIG. 2, FIG. 10, and FIG. 11, the controller initiates a new bidirectional forwarding path AZ (the A port of the forwarding device NE1 to the Z port of the forwarding device NE2) to send a fast OAM function with a period of 10 milliseconds as an example. The process, which includes the following steps:

In the first step, the controller initiates the configuration of the A-Z fast OAM. The OAM is 1 and the type is bidirectional. The operation type is new. The sending period is 10 milliseconds. The traffic table entry information X is used to identify the binding. The inbound port of port A carries the group table information Y to identify the egress port bound to A. Construct a Packetout message, using the in_port identifier message with the value 0xffffff01 as the OAM type; setting the first byte of the pad pad[0] to 1, the identifier is the bidirectional forwarding path; setting the pad second byte pad[1] to 1 The operation type of the packet is new. The data packet carries the packet period of 10 milliseconds. The bound path is AZ and the local port is A. It is delivered to NE1 through the Openflow channel. Construct a Packetout message, and use the in_port identifier message with the value 0xffffff01 as the OAM type message packet; set the pad first byte pad[0] to 1, the identifier is the bidirectional forwarding path OAM; set the pad second byte pad[ 1] is 1, the identification operation type is newly added OAM; the data packet carries the packet period of 10 milliseconds, and the flow table entry information P is used to identify the inbound port of the binding port Z, and the group table information Q is carried to identify the binding A. The port is bound to AZ and the local port is Z. It is delivered to NE2 through the Openflow channel.

Step 2: The OpenFlow protocol processing component of the NE1 receives the Packet-out message, parses the packet, and determines that the value of the in_port is 0xffffff01, and determines that the OAM type is agreed with the controller and is forwarded to the OAM component. The Openflow protocol processing component of the NE2 receives the packet. The packet-out message is parsed into the OAM component according to the OAM type agreed upon by the controller according to the in_port value of 0xffffff01.

Step 3: The OAM component of the NE1 parses the Packet-out message structure, and determines the bidirectional forwarding path according to the value of pad[0]. The value of the pad[1] is 1 and the operation type is newly added OAM; according to the data packet. The OAM message, which is determined to be a 10-msec period, is bound to the inbound and outbound direction of the local port A. Then, the OAM message is configured, and the 10-ms timer is periodically sent to send the OAM message from the outbound direction of the A port. And receive the same type of OAM packet from the incoming detection of the A port. The OAM component of the NE2 parses the Packet-out message structure, and determines that the pad is a bidirectional forwarding path according to the value of pad[0]; the value of the pad[1] is 1 to determine the operation type as a new OAM; The OAM message of the 10 ms period is bound to the inbound and outbound direction of the local port Z. Then, the required OAM message is constructed, and the 10-ms timer is periodically sent from the Z outbound port to the port to send OAM messages. The inbound detection of the Z port receives the same type of OAM packet.

With reference to FIG. 1, FIG. 2, FIG. 10 and FIG. 11, the controller initiates an OAM transmission period of modifying the bidirectional forwarding path AZ (the A port of the forwarding device NE1 to the Z port of the forwarding device NE2), and the modification is changed from 10 milliseconds to 3.33 milliseconds. For example, the process includes the following steps:

Step 1: The controller initiates the configuration of the AZ fast OAM configuration. The OAM identifier is 1, the type is bidirectional, the operation type is modified, and the sending period is 3.33 milliseconds. The flow table entry information P is used to identify the inbound port of the binding port Z. The carrying group table information Q identifies the outgoing port of the binding A. Construct a Packetout message, and use the in_port identifier message with the value 0xffffff01 as the OAM type message packet; set the pad first byte pad[0] to 1, the identifier is the bidirectional forwarding path OAM; set the pad second byte pad[ 1) is 2, the identification operation type is modified OAM; the data packet carries a packet period of 3.33 milliseconds, the bound path is AZ, and the local port is A, Delivered to NE1 through the Openflow channel. Construct a Packetout message, and use the in_port identifier message with the value 0xffffff01 as the OAM type message packet; set the pad first byte pad[0] to 1, the identifier is the bidirectional forwarding path OAM; set the pad second byte pad[ 1] is 2, the identification operation type is modified OAM; the data packet carries the packet period of 3.33 milliseconds, and the flow table entry information P is used to identify the inbound port of the binding port Z, and the group table information Q is carried to identify the outgoing port of the binding A. . The bound path is A-Z and the local port is Z. It is delivered to NE2 through the Openflow channel.

Step 3: The OAM component of the NE1 parses the Packet-out message structure, and determines the bidirectional forwarding path according to the value of pad[0]. The value of the pad[1] is 2, and the operation type is modified OAM; The OAM message of the 3.33 millisecond period is bound to the inbound and outbound direction of the local port A. Then, the 10 millisecond instance that has been in effect is found, the transmission period of the OAM message is modified, the 10 millisecond timer is stopped, and the 3.33 is started. The millisecond timer updates the OAM message packet, periodically sends an OAM message from the outbound direction of the A port, and receives the same type of OAM packet from the incoming detection of the A port. The OAM component of the NE2 parses the packet-out message structure, and determines that the pad is a bidirectional forwarding path according to the value of pad[0]; the value of the pad[1] is 2 to determine the operation type as the modified OAM; The OAM message of the 3.33 millisecond period is bound to the inbound and outbound direction of the local port Z. Then, the 10 millisecond OAM instance that has been in effect is found, the transmission period of the OAM message is modified, the 10 millisecond timer is stopped, and the 3.33 millisecond timer is started. The OAM message packet is updated, and the OAM message is periodically sent from the outbound direction of the Z port, and the same type of OAM packet is received from the inbound detection of the Z port.

As shown in FIG. 1 , FIG. 2 , FIG. 10 , and FIG. 11 , the controller initiates the OAM of the bidirectional forwarding path A-Z (the forwarding of the A port of the device NE1 to the Z port of the forwarding device NE2) as an example. The process includes the following steps:

Step 1: The controller initiates the function of suspending the bidirectional forwarding path A-Z fast OAM. The OAM flag is 1, the type is bidirectional, the operation type is pause, and the sending period is 3.33 milliseconds. Construct a Packetout message, and use the in_port identifier message with the value 0xffffff01 as the OAM type message packet; set the pad first byte pad[0] to 1, the identifier is the bidirectional forwarding path OAM; set the pad second byte pad[ 1] is 3, the identification operation type is suspended OAM; the data packet carries the packet period of 3.33 milliseconds, and the flow table entry information P is used to identify the inbound port of the binding port Z, and the group table information Q is carried to identify the outgoing port of the binding A. . The bound path is A-Z and the local port is A. It is delivered to NE1 through the Openflow channel. Construct a Packetout message, and use the in_port identifier message with the value 0xffffff01 as the OAM type message packet; set the pad first byte pad[0] to 1, and the identifier is a bidirectional forwarding path. The path OAM is set to the second byte of the pad, pad[1] is 3, the identification operation type is pause OAM, the data packet carries the message period of 3.33 milliseconds, and the flow table entry information P is used to identify the ingress port of the binding port Z. The carrying group table information Q identifies the outgoing port of the binding A. The bound path is A-Z and the local port is Z. It is delivered to NE2 through the Openflow channel.

Step 3: The OAM component of the NE1 parses the Packet-out message structure, and determines the bidirectional forwarding path according to the value of pad[0]; the value of the pad[1] is 3, and the operation type is suspended OAM; according to the data packet parsing The OAM message of the 3.33 millisecond period is bound to the inbound and outbound direction of the local port A. Then, the 3.33 millisecond instance that has been in effect is found, the 3.33 millisecond timer is suspended, and the OAM packet is no longer sent. The OAM component of the NE2 parses the Packet-out message structure, and determines that the pad is a bidirectional forwarding path according to the value of pad[0]; the value of pad[1] is 3, and the operation type is suspended OAM; according to the data packet parsing, it is determined as The OAM message of the 3.33 millisecond period is bound to the inbound and outbound direction of the local port Z. Then, the 3.33 millisecond instance that has been in effect is found, the 3.33 millisecond timer is suspended, and the OAM packet is no longer sent.

With reference to FIG. 1 , FIG. 2 , FIG. 10 and FIG. 11 , the OAM of the bidirectional forwarding path AZ (the A port of the forwarding device NE1 to the Z port of the forwarding device NE2) that has been suspended is described as an example. The process includes the following steps:

Step 1: The controller initiates the configuration of the A-Z fast OAM that has been suspended. The OAM flag is 1, the type is bidirectional, the operation type is startup, and the sending period is 3.33 milliseconds. Construct a Packetout message, and use the in_port identifier message with the value 0xffffff01 as the OAM type message packet; set the pad first byte pad[0] to 1, the identifier is the bidirectional forwarding path OAM; set the pad second byte pad[ 1) is 4, the identification operation type is to start OAM; the data packet carries a packet period of 3.33 milliseconds, the bound path is AZ, and the local port is A, which is delivered to NE1 through the Openflow channel. Construct a Packetout message, and use the in_port identifier message with the value 0xffffff01 as the OAM type message packet; set the pad first byte pad[0] to 1, the identifier is the bidirectional forwarding path OAM; set the pad second byte pad[ 1) is 4, the identification operation type is to start OAM; the data packet carries a packet period of 3.33 milliseconds, the bound path is AZ, and the local port is Z, which is delivered to NE2 through the Openflow channel.

Step 2: The OpenFlow protocol processing component of the NE1 receives the Packet-out message, parses the packet, and determines the OAM type agreed with the controller to be forwarded to the OAM component according to the in_port value of 0xffffff01; NE2 The Openflow protocol processing component receives the Packet-out message, parses the message, and determines the OAM type agreed with the controller to be forwarded to the OAM component according to the in_port value of 0xffffff01.

Step 3: The OAM component of the NE1 parses the Packet-out message structure, and determines the bidirectional forwarding path according to the value of pad[0]. The value of the pad[1] is 4 to determine the operation type is OAM; the data packet is parsed according to the data packet. The OAM message of the 3.33 millisecond period is bound to the inbound port and the egress port of the local port A. Then, the 3.33 millisecond instance that has been in effect is found, the 3.33 millisecond timer is restarted, and the OAM packet is sent through the outbound direction of the port A. . The OAM component of the NE2 parses the packet-out message structure, and determines that the pad is a bidirectional forwarding path according to the value of pad[0]. The value of the pad[1] is 4 to determine the operation type as OAM; according to the data packet parsing, it is determined as The OAM message of the 3.33 millisecond period is bound to the outbound direction and the inbound direction of the local port Z. Then, the 3.33 millisecond instance that has been in effect is found, the 3.33 millisecond timer is restarted, and the OAM packet is sent through the outbound direction of the port Z.

As shown in FIG. 1 , FIG. 2 , FIG. 10 , and FIG. 11 , the OAM of the bidirectional forwarding path A-Z (the forwarding of the A port of the forwarding device NE1 to the Z port of the forwarding device NE2) is used as an example. The process includes the following steps:

Step 1: The controller initiates the configuration of deleting the A-Z fast OAM of the bidirectional forwarding path. The OAM identifier is 1, the type is bidirectional, the operation type is deleted, and the sending period is 3.33 milliseconds. Construct a Packetout message, and use the in_port identifier message with the value 0xffffff01 as the OAM type message packet; set the pad first byte pad[0] to 1, the identifier is the bidirectional forwarding path OAM; set the pad second byte pad[ 1) is 5, the identification operation type is deleted OAM; the data packet carries the packet period of 3.33 milliseconds, the bound path is AZ, the local port is A, and is delivered to NE1 through the Openflow channel. Construct a Packetout message, and use the in_port identifier message with the value 0xffffff01 as the OAM type message packet; set the pad first byte pad[0] to 1, the identifier is the bidirectional forwarding path OAM; set the pad second byte pad[ 1) is 5, the identification operation type is deleted OAM; the data packet carries the packet period of 3.33 milliseconds, the bound path is AZ, and the local port is Z, which is delivered to NE2 through the Openflow channel.

Step 3: The OAM component of the NE1 parses the Packet-out message structure, and determines the bidirectional forwarding path according to the value of pad[0]; the value of the pad[1] is 5, and the operation type is deleted OAM; according to the data packet parsing The OAM message, which is determined to be 3.33 milliseconds, is bound to the local port A; then it is found to have been valid. 3.33 millisecond instance, cancel the 3.33 millisecond timer, and delete this OAM instance. The OAM component of the NE2 parses the Packet-out message structure, and determines that it is a bidirectional forwarding path according to the value of pad[0]; the value of the pad[1] is 5, and the operation type is deleted OAM; The OAM message of the 3.33 millisecond period is bound to the local port Z. Then, the 3.33 millisecond instance that has been validated is found, the 3.33 millisecond timer is canceled, and the OAM instance is deleted.

Referring to FIG. 1, FIG. 2, FIG. 10, and FIG. 13, the controller initiates the addition, modification, suspension, activation, or deletion of the OAM of the bidirectional forwarding path AZ (the forwarding port A of the device NE1 to the Z port of the forwarding device NE2), but Only NE1 or NE2 is controlled by the controller. In this way, the controller only needs to interact with NE1 or NE2. In the above embodiments, each implementation step only considers the setting for NE1 or NE2, which is the embodiment in this scenario.

Referring to FIG. 1, FIG. 2, FIG. 10, and FIG. 12, the controller initiates a new one-way forwarding path AZ (the A port of the forwarding device NE1 to the Z port of the forwarding device NE2) to send a fast OAM function with a period of 10 milliseconds as an example. Explain that the process includes the following steps:

Step 1: The controller initiates the configuration of the unidirectional forwarding path A-Z fast OAM. The OAM flag is 1, the type is unidirectional, the operation type is new, and the sending period is 10 milliseconds. Construct a Packetout message, and use the in_port identifier message with the value 0xffffff01 as the OAM type message packet; set the pad first byte pad[0] to 2, the identifier is the one-way forwarding path OAM; set the pad second byte pad [1] is 1, the identification operation type is new OAM; the action [0] type is 0xfff0, the identification action is to send OAM message packets; the data message carries the message period is 10 milliseconds, and the bound path is AZ. The local port is delivered to NE1 through the Openflow channel. Construct a Packetout message, and use the in_port identifier message with the value 0xffffff01 as the OAM type message packet; set the pad first byte pad[0] to 2, the identifier is the one-way forwarding path OAM; set the pad second byte pad [1] is 1, the identification operation type is newly added OAM; the action [0] type is 0xfff1, the identification action is to receive OAM message packets; the data message carries the message period is 10 milliseconds, and the bound path is AZ. The local port is Z and is delivered to NE2 through the Openflow channel.

Step 3: The OAM component of the NE1 parses the Packet-out message structure, and determines the one-way forwarding path according to the value of pad[0]; and determines that the operation type is new OAM according to the value of pad[1]; according to actions[ The type of 0] is 0xfff0, and the action is to send an OAM message. According to the parsing of the data packet, the OAM message of the 10 millisecond period is bound to the local port A. Then, the required OAM message is constructed. 10 milliseconds The timer periodically sends OAM messages from the A port. The OAM component of NE2 parses the Packet-out message structure, and determines the one-way forwarding path according to the value of pad[0]; the value of pad[1] is 1 to determine the operation type as new OAM; according to actions[0] The type is 0xfff1, and the action is to receive the OAM message. According to the data packet parsing, the OAM message of the 10 millisecond period is bound to the local port Z. Then, the Z port probe is monitored to receive the OAM packet of this type.

With reference to FIG. 1, FIG. 2, FIG. 10 and FIG. 12, the OAM transmission period of the unidirectional forwarding path AZ (the A port of the forwarding device NE1 to the Z port of the forwarding device NE2) is modified by the controller, and is modified from 10 milliseconds to 3.33 milliseconds. As an example, the process includes the following steps:

Step 1: The controller initiates the configuration of the A-Z fast OAM configuration. The OAM identifier is 1, the type is one-way, the operation type is modified, and the sending period is 3.33 milliseconds. Construct a Packetout message, and use the in_port identifier message with the value 0xffffff01 as the OAM type message packet; set the pad first byte pad[0] to 2, the identifier is the one-way forwarding path OAM; set the pad second byte pad [1] is 2, the identification operation type is modified OAM; the type of operations[0] is set to 0xfff0, the identification action is to send an OAM message, the data packet carries a packet period of 3.33 milliseconds, and the bound path is AZ. The local port is A and is delivered to NE1 through the Openflow channel. Construct a Packetout message, and use the in_port identifier message with the value 0xffffff01 as the OAM type message packet; set the pad first byte pad[0] to 2, the identifier is the one-way forwarding path OAM; set the pad second byte pad [1] is 2, the identification operation type is modified OAM; the action [0] type is 0xfff1, the identification action is to receive the OAM message, the data message carries the message period is 3.33 milliseconds, and the bound path is AZ. The local port is Z and is delivered to NE2 through the Openflow channel.

Step 3: The OAM component of the NE1 parses the Packet-out message structure, and determines the one-way forwarding path according to the value of pad[0]; the value of the pad[1] is 2 to determine the operation type as the modified OAM; according to the actions[0] The type is 0xfff0, and the action is to send an OAM message. According to the data packet parsing, it is determined that the OAM message of the 3.33 millisecond period is bound to the local port A. Then, the 10 millisecond instance that has been valid is found, and the OAM is modified. The sending period of the message packet, the 10 millisecond timer is stopped, the 3.33 millisecond timer is started, the OAM message packet is updated, and the OAM message is periodically sent from the A port. The OAM component of NE2 parses the Packet-out message structure, and determines that it is a one-way forwarding path according to the value of pad[0]; and determines that the operation type is modified OAM according to the value of pad[1]; according to the type of actions[0] 0xfff1, the action is to receive the OAM message; according to the data packet parsing, it is determined that the OAM message is 3.33 milliseconds, and the local port Z is bound; The instance of the monitoring 10 ms OAM message that has been in effect is found to be modified to receive the 3.33 millisecond message from the Z port probe.

With reference to FIG. 1 , FIG. 2 , FIG. 10 and FIG. 12 , the OAM of the unidirectional forwarding path AZ (the forwarding of the A port of the forwarding device NE1 to the Z port of the forwarding device NE2) is used as an example. The process includes the following steps. :

Step 1: The controller initiates the function of suspending the one-way forwarding path A-Z fast OAM. The OAM flag is 1, the type is one-way, the operation type is pause, and the sending period is 3.33 milliseconds. Construct a Packetout message, and use the in_port identifier message with the value 0xffffff01 as the OAM type message packet; set the pad first byte pad[0] to 2, the identifier is the one-way forwarding path OAM; set the pad second byte pad [1] is 3, the identification operation type is pause OAM; the type of operations[0] is set to 0xfff0, the identification action is to send an OAM message, the data packet carries a packet period of 3.33 milliseconds, and the bound path is AZ. The local port is A and is delivered to NE1 through the Openflow channel. Construct a Packetout message, and use the in_port identifier message with the value 0xffffff01 as the OAM type message packet; set the pad first byte pad[0] to 2, the identifier is the one-way forwarding path OAM; set the pad second byte pad [1] is 3, the identification operation type is pause OAM; the type of operations[0] is set to 0xfff1, the identification action is to receive the OAM message, the data packet carries the packet period is 3.33 milliseconds, and the bound path is AZ. The local port is Z and is delivered to NE2 through the Openflow channel.

Step 3: The OAM component of the NE1 parses the Packet-out message structure, and determines the one-way forwarding path according to the value of pad[0]; the value of the pad[1] is 3 to determine the operation type is pause OAM; according to actions[0] The type is 0xfff0, and the action is to send an OAM message. According to the data packet parsing, it is determined that the OAM message is 3.33 milliseconds, and is bound to the local port A. Then, the current 3.33 millisecond instance is valid, and the pause is 3.33. The millisecond timer does not send this OAM packet. The OAM component of NE2 parses the Packet-out message structure, and determines the one-way forwarding path according to the value of pad[0]; the value of pad[1] determines that the operation type is pause OAM; according to the type of actions[0] If it is 0xfff1, it is determined that the action is to receive the OAM message. According to the data packet parsing, it is determined that the OAM message of the 3.33 millisecond period is bound to the local port Z. Then, the current 3.33 millisecond message instance that has been in effect is found. The Z port receives the monitoring of this OAM.

With reference to FIG. 1 , FIG. 2 , FIG. 10 and FIG. 12 , the OAM of the unidirectional forwarding path AZ (the forwarding of the A port of the forwarding device NE1 to the Z port of the forwarding device NE2) that has been suspended is described as an example. Including the following steps:

Step 1: The controller initiates the configuration of the A-Z fast OAM that has been suspended. The OAM flag is 1, the type is one-way, the operation type is start, and the sending period is 3.33 milliseconds. Construct a Packetout message, and use the in_port identifier message with the value 0xffffff01 as the OAM type message packet; set the pad first byte pad[0] to 2, the identifier is the one-way forwarding path OAM; set the pad second byte pad [1] is 4, the identification operation type is start OAM; the action [0] type is 0xfff0, the identification action is to send an OAM message message; the data message carries a message period of 3.33 milliseconds, and the bound path is AZ. The local port is A and is delivered to NE1 through the Openflow channel. Construct a Packetout message, and use the in_port identifier message with the value 0xffffff01 as the OAM type message packet; set the pad first byte pad[0] to 2, the identifier is the one-way forwarding path OAM; set the pad second byte pad [1] is 4, the identification operation type is start OAM; the action [0] type is 0xfff1, the identification action is to receive OAM message packets; the data message carries the message period is 3.33 milliseconds, and the bound path is AZ. The local port is Z and is delivered to NE2 through the Openflow channel.

Step 3: The OAM component of the NE1 parses the Packet-out message structure, and determines the unidirectional forwarding path according to the value of pad[0]; the value of the pad[1] is 4 to determine the operation type as the start OAM; according to the actions[0] The type is 0xfff0, and the action is to send an OAM message. According to the data packet parsing, the OAM message of the 3.33 millisecond period is bound to the local port A. Then, the 3.33 millisecond instance that has been valid is found. 3.33 millisecond timer, this OAM packet is sent. The OAM component of NE2 parses the Packet-out message structure, and determines that it is a one-way forwarding path according to the value of pad[0]; the value of the pad[1] is 4 to determine the operation type as the start OAM; according to the type of actions[0] It is 0xfff1, and the action is to receive the OAM message. According to the data packet parsing, the OAM message of the 3.33 millisecond period is bound to the local port Z. Then, an instance of the 3.33 millisecond OAM message that has been in effect is found. , restart the probe reception.

With reference to FIG. 1 , FIG. 2 , FIG. 10 and FIG. 12 , the OAM of the unidirectional forwarding path AZ (the forwarding of the A port of the forwarding device NE1 to the Z port of the forwarding device NE2) is used as an example. The process includes The following steps:

Step 1: The controller initiates the deletion of the A-Z fast OAM configuration. The OAM identifier is 1, the type is one-way, the operation type is deleted, and the sending period is 3.33 milliseconds. Construct a Packetout message, and use the in_port identifier message with the value 0xffffff01 as the OAM type message packet; set the pad first byte pad[0] to 2, the identifier is the one-way forwarding path OAM; set the pad second byte pad [1] is 5, the identification operation type is deleted OAM; the action[0] type is 0xfff0, the identification action is to send an OAM message message; the data message carries a message period of 3.33 milliseconds, and the bound path is AZ. The local port is A and is delivered to NE1 through the Openflow channel. Construct a Packetout message, and use the in_port identifier message with the value 0xffffff01 as the OAM type message packet; set the pad first byte pad[0] to 2, the identifier is the one-way forwarding path OAM; set the pad second byte pad [1] is 5, the identification operation type is deleted OAM; the action [0] type is 0xfff1, the identification action is to receive OAM message packets; the data message carries the packet period is 3.33 milliseconds, and the bound path is AZ. The local port is Z, and the action is received. It is sent to NE2 through the Openflow channel.

Step 3: The OAM component of the NE1 parses the Packet-out message structure, and determines the unidirectional forwarding path according to the value of pad[0]; the value of the pad[1] is 5, and the operation type is deleted OAM; according to actions[0] The type is 0xfff0, and the action is to send an OAM message. According to the data packet parsing, it is determined that the OAM message of the 3.33 millisecond period is bound to the local port A. Then, the 3.33 millisecond instance that has been valid is found, and the 3.33 cancellation is canceled. The millisecond timer and delete this OAM instance. The OAM component of NE2 parses the Packet-out message structure, and determines that it is a one-way forwarding path according to the value of pad[0]; the value of pad[1] is 5 to determine the operation type as deleting OAM; according to the type of actions[0] It is 0xfff1, and the action is to receive the OAM message. According to the data packet parsing, the OAM message of the 3.33 millisecond period is bound to the local port Z. Then, an instance of the 3.33 millisecond OAM message that has been in effect is found. , cancel the 3.33 millisecond timer and cancel the probe reception for this OAM.

In conjunction with FIG. 1, FIG. 2, FIG. 10, and FIG. 14, the OAM of the unidirectional forwarding path AZ (the A port of the forwarding device NE1 to the Z port of the forwarding device NE2) is initiated, modified, suspended, activated, or deleted by the controller. But only the NE1 belongs to the controller control, so the controller only needs to interact with NE1. In the above embodiment, each implementation step only considers the setting for NE1 as an embodiment in such a scenario.

In conjunction with FIG. 1, FIG. 2, FIG. 10, and FIG. 15, the OAM of the unidirectional forwarding path AZ (the A port of the forwarding device NE1 to the Z port of the forwarding device NE2) is initiated, modified, suspended, activated, or deleted by the controller. but Only the NE2 belongs to the controller control, so the controller only needs to interact with NE2. In the above embodiment, each implementation step only considers the setting for NE2, which is an embodiment in such a scenario.

For the non-packet transmission technology such as OTN, the OAM is inherently existing, and the OAM addition, deletion, and modification operations are not required. Only the OAM monitoring function needs to be enabled or suspended, and the OAM monitoring function is enabled to be activated. Indicates that the OAM monitoring function is disabled.

From the analysis of each of the above specific embodiments, it can be known that the required OAM function can be completed whether it is a bidirectional forwarding path or a one-way forwarding path.

In this optional implementation manner, based on the specification interface between the controller and the forwarding device of the existing SDN, the related member definition of the Packet-out message is extended, and the Ethernet, IP, MPLS, and MPLS for the packet-based transmission technology are completed. -TP, PBB and other networks, non-packet transmission technology such as OTN, WDM and other networks, for the two-way or one-way forwarding path fast OAM addition, modification, suspension, start, delete and other functions, with simple and reliable advantages.

It will be apparent to those skilled in the art that the various modules or steps of the present invention described above can be implemented by a general-purpose computing device that can be centralized on a single computing device or distributed across a network of multiple computing devices. Alternatively, they may be implemented by program code executable by the computing device such that they may be stored in the storage device by the computing device and, in some cases, may be different from the order herein. The steps shown or described are performed, or they are separately fabricated into individual integrated circuit modules, or a plurality of modules or steps thereof are fabricated as a single integrated circuit module. Thus, the invention is not limited to any specific combination of hardware and software.

The above are only the preferred embodiments of the present invention, and are not intended to limit the present invention, and various modifications and changes can be made to the present invention. Any modifications, equivalent substitutions, improvements, etc. made within the spirit and scope of the present invention are intended to be included within the scope of the present invention.

Industrial applicability

As described above, the method and apparatus for implementing the operation and maintenance management function provided by the embodiment of the present invention have the following beneficial effects: the controller carries the OAM configuration information indicating the OAM function of the path of the forwarding device in the configuration packet, The forwarding device sends the configuration packet to indicate that the forwarding device implements the OAM function of the path, and implements the OAM function at the forwarding device level, which avoids the problem that the forwarding device and the controller interact to cause low real-time performance, thereby achieving the path OAM function. High real-time requirements.

Claims

An implementation method of an operation and maintenance management function includes:

The controller carries the operation and maintenance management OAM configuration information in the configuration packet, where the OAM configuration information is used to indicate the OAM function of the forwarding device to implement the path, and the path is a path between the forwarding devices.

The controller sends the configuration packet to the forwarding device.
The method of claim 1, wherein the OAM configuration information comprises at least one of: identification information, operation type, feature information, port information, wherein:

The identifier information is used to identify an instance of the OAM function, and is different from other OAM instances that are in effect at the same time;

The operation type is used to indicate a type of the OAM function;

The feature information is used to indicate a parameter corresponding to the OAM function;

The port information is used to indicate a local port to which the OAM function is bound.
The method according to claim 2, wherein the feature information comprises: an OAM message packet sending period, wherein the OAM message packet sending period is used to indicate that the forwarding device forwards to the other end of the path The period during which the message is sent.
The method according to claim 2 or 3, wherein the OAM operation type comprises at least one of: addition, modification, suspension, activation or deletion of an OAM function.
The method according to claim 2, wherein the sending, by the controller, the configuration message to the forwarding device comprises at least one of the following:

Sending the configuration packet to the first-end forwarding device and/or the tail-end forwarding device of the bidirectional forwarding path, where the port information carried in the configuration packet includes outbound port information and ingress port information, and the outbound port information indicates sending a local port of the packet, where the ingress port information indicates a local port that receives the packet;

Transmitting the first configuration packet to the first-end forwarding device of the one-way forwarding path, and/or sending the second configuration packet to the tail-end forwarding device of the one-way forwarding path, where the first configuration packet is carried The port information is the outbound port information, and the port information carried in the second configuration packet is the ingress port information.
The method according to any one of claims 1 to 5, wherein the configuration message is a message type based on a Packet-out message extension.
The method of claim 6, wherein the OAM configuration information is carried in at least one of the following: a port field, an action set field, a reserved field, or a data field.
An implementation method of an operation and maintenance management function includes:

The forwarding device receives the configuration packet sent by the controller;

The forwarding device obtains operation and maintenance management OAM configuration information from the configuration packet, where the OAM configuration information is used to indicate that the forwarding device implements an OAM function of a path, where the path is a path between forwarding devices;

The forwarding device performs an OAM function of the path according to the OAM configuration information.
The method according to claim 8, wherein the forwarding device performs an OAM function of the path according to the OAM configuration information, including at least one of the following:

When the type of the OAM configuration information indicates that the type of the OAM function is new, the timer corresponding to the OAM message packet period is started according to the OAM message packet period indicated by the feature information in the OAM configuration information. Sending an OAM message to the forwarding device at the other end of the path and/or receiving an OAM message sent by the forwarding device at the other end of the path;

When the operation type indicates that the type of the OAM function is modified, the timer of the OAM message packet is stopped according to the OAM message packet period indicated by the feature information, and the timer corresponding to the OAM message packet period is started. Sending an OAM message to the forwarding device at the other end of the path and/or receiving an OAM message sent by the forwarding device at the other end of the path;

When the type of the operation indicates that the type of the OAM function is paused, the timer of the OAM message is suspended, and the OAM message is suspended and/or received.

And when the operation type indicates that the type of the OAM function is a restart, restarting the timer of the OAM message, sending an OAM message to the forwarding device at the other end of the path, and/or receiving the forwarding at the other end of the path. OAM message sent by the device;

When the type of the operation indicates that the type of the OAM function is deleted, the timer of the OAM message is cancelled, and the identifier information in the OAM configuration information is deleted.
The method according to claim 9, wherein when the binding object of the OAM configuration information is a one-way forwarding path,

If the forwarding device is the first endpoint of the path, the forwarding device sends an OAM message to the forwarding device at the other end of the path according to the operation type; and/or

If the forwarding device is the trailing endpoint of the path, the forwarding device receives the OAM message sent by the other end of the path according to the operation type.
The method according to claim 9 or 10, wherein when the binding object of the OAM configuration information is a bidirectional forwarding path,

The forwarding device sends an OAM message to the forwarding device of the other end of the path according to the operation type, and receives the OAM message sent by the other end of the path.
The method of claim 10, further comprising: the forwarding device binding the corresponding local port according to the port information in the OAM configuration information; wherein the ingress port is identified by the flow table entry information, and the group table information is used. A port is identified, the local port including a physical port and/or a logical port.
The method according to any one of claims 8 to 12, wherein the configuration message is a message type based on a Packet-out message extension.
An implementation device for an operation and maintenance management function, comprising:

The processing module is configured to carry the operation and maintenance management OAM configuration information in the configuration packet, where the OAM configuration information is used to indicate the OAM function of the forwarding device to implement the path, and the path is a path between the forwarding devices;

And a sending module, configured to send the configuration packet to the forwarding device.
The apparatus according to claim 14, wherein the OAM configuration information comprises at least one of: identification information, operation type, feature information, and port information, wherein:

The identifier information is used to identify an instance of the OAM function, and is distinguished by other OAM instances that are effective at the same time;

The operation type is used to indicate a type of the OAM function;

The feature information is used to indicate a parameter corresponding to the OAM function;

The port information is used to indicate a local port to which the OAM function is bound.
The device according to claim 15, wherein the feature information comprises: an OAM message packet sending period, wherein the OAM message packet sending period is used to indicate that the forwarding device forwards to the other end of the path The period during which the message is sent.
The apparatus according to claim 15 or 16, wherein the OAM operation type comprises at least one of: addition, modification, suspension, activation or deletion of an OAM function.
The apparatus of claim 15, wherein the transmitting module comprises at least one of:

The first sending unit is configured to send the configuration packet to the first-end forwarding device and/or the tail-end forwarding device of the bidirectional forwarding path, where the port information carried in the configuration packet includes the outbound port information and the ingress port information. The outbound port information indicates a local port that sends a packet, and the ingress port information indicates a local port that receives the packet;

a second sending unit, configured to send a first configuration packet to the first endpoint forwarding device of the one-way forwarding path, and/or to send a second configuration packet to the tail endpoint forwarding device of the one-way forwarding path, where The port information carried in the first configuration packet is the outbound port information, and the port information carried in the second configuration packet is the ingress port information.
The apparatus according to any one of claims 14 to 18, wherein the configuration message is a message type based on a Packet-out message extension.
The apparatus of claim 19, wherein the processing module is configured to carry the OAM configuration information in at least one of the following: a port field, an action set field, a reserved field, or a data field.
An implementation device for an operation and maintenance management function, comprising:

a receiving module, configured to receive a configuration message sent by the controller;

An acquiring module, configured to obtain operation and maintenance management OAM configuration information from the configuration packet, where the OAM configuration information is used to indicate an OAM function of a forwarding device to implement a path, where the path is a path between forwarding devices;

The execution module is configured to perform an OAM function of the path according to the OAM configuration information.
The apparatus of claim 21 wherein said execution module comprises at least one of:

The first execution unit is configured to start the OAM message according to the OAM message packet period indicated by the feature information in the OAM configuration information, when the type of the OAM configuration information indicates that the type of the OAM function is new. The timer corresponding to the message period, the rotation to the other end of the path The sending device sends an OAM message and/or receives an OAM message sent by the forwarding device at the other end of the path;

a second execution unit, configured to: when the type of the operation indicates that the type of the OAM function is modified, stop the timer of the OAM message according to the OAM message packet period indicated by the feature information, and start the OAM message. The timer corresponding to the packet period sends an OAM message to the forwarding device at the other end of the path and/or receives an OAM message sent by the forwarding device at the other end of the path;

a third execution unit, configured to suspend the timer of the OAM message, suspend sending and/or receiving the OAM message, when the operation type indicates that the type of the OAM function is paused;

And a fourth execution unit, configured to: when the operation type indicates that the type of the OAM function is a restart, restart a timer of the OAM message, and send an OAM message and/or receive to the forwarding device at the other end of the path. An OAM message sent by the forwarding device at the other end of the path;

And a fifth execution unit, configured to: when the operation type indicates that the type of the OAM function is deleted, cancel the timer of the OAM message, and delete the OAM instance corresponding to the identifier information in the OAM configuration information.
The apparatus according to claim 22, wherein when the binding object of the OAM configuration information is a one-way forwarding path,

If the forwarding device is the first endpoint of the path, the executing module is configured to send an OAM message to the forwarding device at the other end of the path according to the operation type; and/or

If the forwarding device is the trailing endpoint of the path, the executing module is configured to receive, according to the operation type, an OAM message sent by the other end of the path forwarding device.
The apparatus according to claim 22 or 23, wherein when the binding object of the OAM configuration information is a bidirectional forwarding path,

The execution module is configured to send an OAM message to the forwarding device of the other end of the path according to the operation type, and receive an OAM message sent by the other end of the path.
The apparatus according to claim 22, wherein the execution module is further configured to bind a corresponding local port according to port information in the OAM configuration information; wherein the inflow port is identified by flow table entry information, and the group table is used. The information identifies the port, which includes the physical port and/or the logical port.
The apparatus according to any one of claims 21 to 25, wherein the configuration message is a message type based on a Packet-out message extension.