WO2016101582A1 - 一种操作维护管理功能的配置、实现方法及转发设备 - Google Patents

一种操作维护管理功能的配置、实现方法及转发设备 Download PDF

Info

Publication number
WO2016101582A1
WO2016101582A1 PCT/CN2015/083093 CN2015083093W WO2016101582A1 WO 2016101582 A1 WO2016101582 A1 WO 2016101582A1 CN 2015083093 W CN2015083093 W CN 2015083093W WO 2016101582 A1 WO2016101582 A1 WO 2016101582A1
Authority
WO
WIPO (PCT)
Prior art keywords
oam
port
packet
information
forwarding device
Prior art date
Application number
PCT/CN2015/083093
Other languages
English (en)
French (fr)
Inventor
孙德胜
赵福川
Original Assignee
中兴通讯股份有限公司
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 中兴通讯股份有限公司 filed Critical 中兴通讯股份有限公司
Priority to EP15871657.1A priority Critical patent/EP3223455A4/en
Priority to RU2017121483A priority patent/RU2678713C2/ru
Publication of WO2016101582A1 publication Critical patent/WO2016101582A1/zh

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/08—Configuration management of networks or network elements
    • H04L41/0895—Configuration of virtualised networks or elements, e.g. virtualised network function or OpenFlow elements
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/02—Standardisation; Integration
    • H04L41/0213—Standardised network management protocols, e.g. simple network management protocol [SNMP]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/08—Configuration management of networks or network elements
    • H04L41/0803—Configuration setting
    • H04L41/0823—Configuration setting characterised by the purposes of a change of settings, e.g. optimising configuration for enhancing reliability
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/34—Signalling channels for network management communication
    • H04L41/342—Signalling channels for network management communication between virtual entities, e.g. orchestrators, SDN or NFV entities
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/40—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks using virtualisation of network functions or resources, e.g. SDN or NFV entities
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L43/00—Arrangements for monitoring or testing data switching networks
    • H04L43/02—Capturing of monitoring data
    • H04L43/026—Capturing of monitoring data using flow identification
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L43/00—Arrangements for monitoring or testing data switching networks
    • H04L43/04—Processing captured monitoring data, e.g. for logfile generation
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L43/00—Arrangements for monitoring or testing data switching networks
    • H04L43/20—Arrangements for monitoring or testing data switching networks the monitoring system or the monitored elements being virtualised, abstracted or software-defined entities, e.g. SDN or NFV

Definitions

  • This document relates to the operation and maintenance management (OAM) function, especially the implementation method of the operation and maintenance management function and the corresponding forwarding device.
  • OAM operation and maintenance management
  • SDN Software Defined Network
  • CP controller
  • Forwarder forwarding device
  • SDN related standard recommendations focusing on the decoupling between the controller and the forwarding device (Forwarder), and standardizing the interface between the controller and the forwarding plane.
  • 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, and is relatively mature in supporting Layer 2 services and Layer 2 VPN services.
  • the Openflow channel is used for the Openflow protocol interaction between the controller (hereinafter referred to as Controller) and the forwarding device (hereinafter referred to as Forwarder, also referred to as switch, also referred to as forwarding device).
  • Controller the controller
  • Forwarder also referred to as switch
  • forwarding device the forwarding device
  • the protocol processing component of the forwarding device terminates the protocol, and the content information carried by the protocol packet is extracted and forwarded to the corresponding component.
  • the information sent to the controller by the relevant components in the forwarding device needs to be first passed to the protocol processing component and encapsulated into an Openflow protocol message 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 forwarder state.
  • the asynchronous message is initiated by the forwarder to notify the controller of the network event or forwarder state change.
  • the symmetric message can be initiated by the forwarder or the controller.
  • the controller sends a Packet-out message of the controller-to-switch category to the Forwarder through the Openflow channel.
  • Forwarder based on the message
  • the Receiver receives the message and completes the related work according to the message (such as sending and receiving packet statistics, error packet statistics, etc.), and sends it to the protocol processing component, which is encapsulated as a Packet-in message through Openflow.
  • the channel is sent to the controller, as shown in Figure 2. In this way, the controller completes the detection function of the specified path between the forwarding devices through the Packet-out and Packet-in messages.
  • this mechanism is suitable for user-initiated and on-demand detection scenarios with low real-time requirements; it is not suitable for periodic fast transmission and reception, and is used for protection switching or other destination packets, such as MPLS-TP (ITU ITU) -T and other international standard specification packet transmission technology standards)
  • MPLS-TP ITU ITU
  • CCM Connectivity Detection Packet
  • Such fast packets generally need to be sent and received quickly at the Forwarder device level.
  • a method of configuring an operation and maintenance management function including:
  • the controller initiates the configuration of the forwarding path operation maintenance management OAM function, and constructs an OAM configuration message, where the OAM configuration message carries OAM configuration information;
  • the controller sends the OAM configuration message to the first endpoint forwarding device and/or the tail endpoint forwarding device of the forwarding path through an Openflow channel.
  • the message type carried in the OpenFlow protocol header in the OAM configuration packet is a new message type obtained by extending the message type defined by the Openflow protocol.
  • the OAM configuration information includes all or part of the following information:
  • OAM identifier which indicates the identifier of the configured OAM instance.
  • the type of operation that indicates the type of operation to be performed
  • the period in which the packet is sent is the period in which the forwarding device sends OAM packets.
  • the local port is a physical port or a logical port, including:
  • Inbound port indicating the port that receives OAM packets
  • Outbound port indicating the port that sends OAM packets.
  • the forwarding path is a bidirectional forwarding path, and the controller constructs an OAM configuration packet, including:
  • the forwarding path is a unidirectional forwarding path, and the controller constructs an OAM configuration packet, including:
  • the operation type is one of adding, modifying, starting, pausing, and deleting.
  • the network protocol layer where the forwarding path is located is one of the following network protocol layers:
  • the physical layer VLAN layer, IP layer, and service layer of Ethernet;
  • the physical layer, the optical transmission segment layer, the optical multiplexing segment layer, the optical channel layer, and the regeneration segment layer of the wavelength division multiplexing WDM network are the physical layer, the optical transmission segment layer, the optical multiplexing segment layer, the optical channel layer, and the regeneration segment layer of the wavelength division multiplexing WDM network.
  • An implementation method for operation and maintenance management OAM functions including:
  • the forwarding device at the forwarding path receives the Openflow packet through the Openflow channel and parses the Openflow protocol header.
  • the forwarding device parses the OAM configuration packet, obtains the OAM configuration information, and performs corresponding processing, according to the analysis result, if the OpenFlow packet is determined to be an OAM configuration packet.
  • the forwarding device parses the Openflow protocol header, and determines that the Openflow packet is an OAM configuration packet, including:
  • the forwarding device parses the OpenFlow protocol header, and if the message type is a message type of the OAM configuration packet, it is determined that the OpenFlow packet is an OAM configuration packet, where the OAM configuration packet is sent.
  • the type is a new message type derived from the extension of the message type defined by the Openflow protocol.
  • the OAM configuration information acquired by the forwarding device includes all or part of the following information:
  • OAM identifier which indicates the identifier of the configured OAM instance.
  • the type of operation that indicates the type of operation to be performed
  • the period in which the packet is sent is the period in which the forwarding device sends OAM packets.
  • the OAM configuration information obtained by the forwarding device includes information about a local port, where the local port is a physical port or a logical port, and includes:
  • Inbound port indicating the port that receives OAM packets
  • Outbound port indicating the port that sends OAM packets.
  • the forwarding path is a bidirectional forwarding path
  • the local port information acquired by the forwarding device includes inbound port information represented by flow table entry information and outgoing port information represented by group table information;
  • the forwarding device performs the corresponding processing, including: searching for the local inbound port according to the flow table entry information, and matching the local outbound port according to the group table information matching.
  • the forwarding path is a one-way forwarding path
  • the local port information acquired by the forwarding device includes inbound port information represented by flow table entry information or outgoing port information represented by group table information;
  • the forwarding device performs the corresponding processing, including: searching for the local inbound port according to the flow table entry information matching, or finding the local outgoing port according to the group table information matching.
  • the operation type obtained by the forwarding device is newly added; the forwarding device performs corresponding processing, including: creating an OAM instance having the OAM identifier and binding the specified inbound port and/or the outbound port, where The inbound port receives the OAM packet, and/or sends the OAM packet according to the packet sending period on the outbound port; or
  • the operation type obtained by the forwarding device is modified; the forwarding device performs corresponding processing, including: finding an OAM instance to be configured according to the OAM identifier, and updating the configuration of the OAM instance according to the received OAM configuration information, according to the new Configuration to send and/or receive OAM messages; or
  • the operation type obtained by the forwarding device is deleted.
  • the forwarding device performs corresponding processing, including: finding an OAM instance to be configured according to the OAM identifier, and deleting the OAM instance. Save; or
  • the operation type obtained by the forwarding device is a pause; the forwarding device performs a corresponding process, including: finding an OAM instance to be configured according to the OAM identifier, and stopping the sending and/or receiving of the OAM packet; or
  • the operation type obtained by the forwarding device is a restart; the forwarding device performs the corresponding processing, including: finding an OAM instance to be configured according to the OAM identifier, and restarting sending and/or receiving the OAM packet.
  • the network protocol layer where the forwarding path is located is one of the following network protocol layers:
  • the physical layer VLAN layer, IP layer, and service layer of Ethernet;
  • the physical layer, the optical transmission segment layer, the optical multiplexing segment layer, the optical channel layer, and the regeneration segment layer of the wavelength division multiplexing WDM network are the physical layer, the optical transmission segment layer, the optical multiplexing segment layer, the optical channel layer, and the regeneration segment layer of the wavelength division multiplexing WDM network.
  • a controller that can configure a forwarding path operation maintenance management OAM function including:
  • the message construction module is configured to: when the configuration of the forwarding path OAM function is initiated, the OAM configuration packet is configured, and the OAM configuration packet carries the OAM configuration information;
  • the packet sending module is configured to send the OAM configuration packet to the first endpoint forwarding device and/or the tail endpoint forwarding device of the forwarding path through the Openflow channel.
  • the message type carried by the Openflow protocol header is a new message type obtained by extending the message type defined by the Openflow protocol.
  • the OAM configuration information carried in the OAM configuration packet configured by the packet construction module includes all or part of the following information:
  • OAM identifier which indicates the identifier of the configured OAM instance.
  • the type of operation that indicates the type of operation to be performed
  • the period in which the packet is sent is the period in which the forwarding device sends OAM packets.
  • the local port that is carried in the OAM configuration packet that is configured by the packet construction module is a physical port or a logical port, and includes:
  • Inbound port indicating the port that receives OAM packets
  • Outbound port indicating the port that sends OAM packets.
  • the forwarding path is a bidirectional forwarding path
  • the message construction module is set to:
  • the forwarding path is a one-way forwarding path
  • the packet construction module constructs an OAM configuration packet, including:
  • the operation type in the OAM configuration information carried in the OAM configuration packet of the packet construction module is one of adding, modifying, starting, suspending, and deleting.
  • the packet construction module constructs an OAM configuration packet when the forwarding path OAM function is configured, where the network protocol layer where the forwarding path is located is one of the following network protocol layers:
  • the physical layer VLAN layer, IP layer, and service layer of Ethernet;
  • the physical layer, the optical transmission segment layer, the optical multiplexing segment layer, the optical channel layer, and the regeneration segment layer of the wavelength division multiplexing WDM network are the physical layer, the optical transmission segment layer, the optical multiplexing segment layer, the optical channel layer, and the regeneration segment layer of the wavelength division multiplexing WDM network.
  • a forwarding device that implements the OAM function of the forwarding path operation and maintenance management, including:
  • the Openflow protocol processing component is configured to: receive an Openflow packet sent by the controller through the Openflow channel, and parse the Openflow protocol header, and determine that the Openflow packet is an OAM configuration packet, and forward the packet to the OAM component for processing;
  • the OAM component is configured to parse the OAM configuration packet, obtain the OAM configuration information, and perform corresponding processing.
  • the Openflow protocol processing component is configured to: parse the Openflow protocol header, and determine the message type of the OAM configuration packet, and determine that the Openflow packet is an OAM configuration packet;
  • the message type of the OAM configuration packet is a new message type obtained by extending the message type defined by the Openflow protocol.
  • the OAM configuration information acquired by the OAM component includes all or part of the following information:
  • OAM identifier which indicates the identifier of the configured OAM instance.
  • the type of operation that indicates the type of operation to be performed
  • the period in which the packet is sent is the period in which the forwarding device sends OAM packets.
  • the OAM configuration information acquired by the OAM component includes information of a local port, where the local port is a physical port or a logical port, including:
  • Inbound port indicating the port that receives OAM packets
  • Outbound port indicating the port that sends OAM packets.
  • the information of the local port includes the inbound port information represented by the flow table entry information and the outgoing port information represented by the group table information;
  • the OAM component performs corresponding processing, including: searching for a local inbound port according to the flow table entry information matching, and matching the local outbound port according to the group table information matching.
  • the information of the local port includes the inbound port information represented by the flow table entry information, or the outgoing port information represented by the group table information;
  • the OAM component performs corresponding processing, including: searching for a local inbound port according to the flow table entry information matching, or finding a local outgoing port according to the group table information matching.
  • the operation type acquired by the OAM component is newly added; the OAM component is configured to: create an OAM instance having the OAM identifier and bind with a specified inbound port and/or an outbound port, where the inbound port is Receiving an OAM message, and/or transmitting an OAM message according to the message sending period on the outbound port; or
  • the operation type of the OAM component is modified.
  • the OAM component is configured to: find an OAM instance to be configured according to the OAM identifier, and update the corresponding configuration of the OAM instance according to the received OAM configuration information, according to the new configuration. Configuration to send and/or receive OAM messages; or
  • the operation type of the OAM component is deleted; the OAM component is configured to: find the OAM instance to be configured according to the OAM identifier, and delete the OAM instance; or
  • the operation type acquired by the OAM component is a pause; the OAM component is configured to: find an OAM instance to be configured according to the OAM identifier, and stop sending and/or receiving OAM packets; or
  • the operation type of the OAM component is restarted.
  • the OAM component is configured to: find an OAM instance to be configured according to the OAM identifier, and restart the sending and/or receiving of the OAM message.
  • the network protocol layer where the forwarding path associated with the forwarding device is located is one of the following network protocol layers:
  • the physical layer VLAN layer, IP layer, and service layer of Ethernet;
  • the physical layer, the optical transmission segment layer, the optical multiplexing segment layer, the optical channel layer, and the regeneration segment layer of the wavelength division multiplexing WDM network are the physical layer, the optical transmission segment layer, the optical multiplexing segment layer, the optical channel layer, and the regeneration segment layer of the wavelength division multiplexing WDM network.
  • a computer readable storage medium storing computer executable instructions for performing the method of any of the above.
  • the OAM configuration packet is transmitted through the OAM configuration packet, and the OAM packet is transmitted and received at the Forwarder device level according to the standard requirements.
  • the newly defined OAM message completes the configuration functions of adding, modifying, suspending, starting, or deleting the OAM function, and has the advantages of simplicity and reliability.
  • FIG. 1 is a simplified schematic diagram of an SDN network
  • 2 is a schematic diagram of packet transmission of SDN network Packet-out and Packet-in;
  • FIG. 3 is a flow chart of a method according to an embodiment of the present invention.
  • FIG. 4 is a block diagram of a controller according to an embodiment of the present invention.
  • FIG. 5 is a flowchart of a method according to Embodiment 2 of the present invention.
  • FIG. 6 is a block diagram of a forwarding device according to Embodiment 2 of the present invention.
  • FIG. 7 is a schematic diagram of configuring a bidirectional path OAM according to an application example of the present invention.
  • FIG. 8 is a schematic diagram of configuring a unidirectional path OAM according to an application example of the present invention.
  • FIG. 9 is a schematic diagram of an OAM in which only one bidirectional path of one endpoint Forwarder is configured according to an application example of the present invention
  • FIG. 10 is a schematic diagram of an OAM for configuring only one-way path first endpoint Forwarder according to an application example of the present invention
  • FIG. 11 is a schematic diagram of an OAM for configuring only one-way path tail endpoint Forwarder according to an application example of the present invention.
  • the network protocol layer (also referred to as the layer network in some standards) in which the forwarding path (also referred to as a transmission path or a transmission path in some standards) is one of the following network protocol layers:
  • the physical layer VLAN layer, IP layer, and service layer of Ethernet;
  • the physical layer, the optical transmission segment layer, the optical multiplexing segment layer, the optical channel layer, and the regeneration segment layer of the wavelength division multiplexing WDM network are the physical layer, the optical transmission segment layer, the optical multiplexing segment layer, the optical channel layer, and the regeneration segment layer of the wavelength division multiplexing WDM network.
  • protocol layers are not exhaustive, such as the protocol layers of the Provider Backbone Bridge (PBB) network, and so on.
  • PBB Provider Backbone Bridge
  • the configuration method of the operation and maintenance management function in this embodiment is as shown in FIG. 3, and includes:
  • Step 110 The controller initiates a configuration of the path maintenance and management OAM function, and constructs an OAM configuration message, where the OAM configuration message carries OAM configuration information.
  • the message type carried in the OpenFlow protocol header in the OAM configuration packet is a new message type obtained by extending the message type defined by the Openflow protocol.
  • the OAM configuration information includes all or part of the following information:
  • OAM identifier which indicates the identifier of the configured OAM instance.
  • the type of operation that indicates the type of operation to be performed
  • the period in which the packet is sent is the period in which the forwarding device sends OAM packets.
  • the operation type may be one of adding, modifying, starting, pausing, and deleting;
  • the local port is a physical port (such as a physical port such as Ethernet, OTN, or WDM) or a logical port (such as a VLAN port of the Ethernet network, a tunnel or pseudowire port of MPLS or MPLS_TP, an ODUk channel port of the OTN, etc.)
  • the port includes the inbound port, which indicates the port that receives the OAM packet, and/or the outbound port, which indicates the port that sends the OAM packet.
  • the forwarding path is a bidirectional forwarding path
  • the local port in the OAM configuration packet can include the inbound port and the outbound port.
  • the port sends OAM packets such as OAM detection packets
  • it can also include only the inbound direction.
  • a port can only include an outbound port when it receives OAM packets on a port.
  • the controller constructs an OAM configuration packet, including:
  • the first port forwarding device Constructing a first OAM configuration message to be sent to the first-end forwarding device of the bidirectional forwarding path, where the first port forwarding device carries the local port information, including the flow table entry information. (such as the flow table (Table id), key value (KEY), etc.), the inbound port information and the group table information (such as the group table (Group id) group identifier (Group id), etc. ) indicates the outgoing port information;
  • the flow table entry information such as the flow table (Table id), key value (KEY), etc.
  • the inbound port information and the group table information such as the group table (Group id) group identifier (Group id), etc.
  • the controller constructs an OAM configuration packet, including:
  • the local port can be represented by the KEY of the Openflow flow table, and the forwarding device can find the corresponding physical port or logical port by matching the flow table according to the KEY.
  • Step 120 The controller sends the OAM configuration packet to the first endpoint forwarding device and/or the tail endpoint forwarding device of the forwarding path through an Openflow channel.
  • the controller sends the configured first OAM configuration packet to the first endpoint forwarding device, and sends the configured second OAM configuration packet to the tail endpoint forwarding device.
  • the embodiment is to construct two OAM configuration messages, the forwarding device is sent to the first port and the tail end.
  • the controller can also construct only one OAM configuration message and send it to a forwarding device on the first port or the tail port.
  • controller that can configure the forwarding path operation maintenance management OAM function in this embodiment is as shown in FIG. 4, and includes:
  • the message construction module 10 is configured to: when the configuration of the forwarding path OAM function is initiated, the OAM configuration message is configured, and the OAM configuration message carries the OAM configuration information;
  • the packet sending module 20 is configured to: send the OAM configuration packet to the first endpoint forwarding device and/or the tail endpoint forwarding device of the forwarding path through an Openflow channel.
  • the message type carried by the Openflow protocol header is a new message type obtained by extending the message type defined by the Openflow protocol.
  • the OAM configuration information carried in the OAM configuration packet configured by the packet construction module includes all or part of the following information:
  • OAM identifier which indicates the identifier of the configured OAM instance.
  • the type of operation that indicates the type of operation to be performed
  • the period in which the packet is sent is the period in which the forwarding device sends OAM packets.
  • the OAM configuration information of the OAM configuration packet that is configured by the packet construction module further includes: a sending and receiving indication, which is set to: send an OAM packet on the local port, or receive an OAM packet, or send and receive at the same time. OAM message.
  • the operation type in the OAM configuration information carried in the OAM configuration packet of the packet construction module is one of adding, modifying, starting, suspending, and deleting.
  • the local port information in the OAM configuration information carried by the packet construction module is represented by the feature information generated by the controller, and the feature information is forwarded to the first endpoint forwarding device and/or
  • the local port on the tail endpoint forwarding device has a correspondence, and the local port is a physical port or a logical port.
  • the packet construction module constructs an OAM configuration packet, including: constructing a first OAM configuration packet for the first endpoint forwarding device, and constructing a second OAM configuration packet for the tail endpoint forwarding device;
  • the packet sending module sends the OAM configuration packet to the first endpoint forwarding device and/or the tail endpoint forwarding device of the forwarding path by using the OpenFlow channel, including: sending the first OAM configuration packet to the The first endpoint forwarding device sends the second OAM configuration packet to the tail endpoint forwarding device.
  • the packet construction module constructs an OAM configuration packet when the forwarding path OAM function is configured, where the network protocol layer where the forwarding path is located is one of the following network protocol layers:
  • the physical layer VLAN layer, IP layer, and service layer of Ethernet;
  • the physical layer, the optical transmission segment layer, the optical multiplexing segment layer, the optical channel layer, and the regeneration segment layer of the wavelength division multiplexing WDM network are the physical layer, the optical transmission segment layer, the optical multiplexing segment layer, the optical channel layer, and the regeneration segment layer of the wavelength division multiplexing WDM network.
  • the forwarding device at one end of the forwarding path receives the OAM configuration packet, and the OAM function is implemented.
  • the network protocol layer where the forwarding path is located may be one of the following network protocol layers:
  • the physical layer VLAN layer, IP layer, and service layer of Ethernet;
  • the physical layer, the optical transmission segment layer, the optical multiplexing segment layer, the optical channel layer, and the regeneration segment layer of the wavelength division multiplexing WDM network are the physical layer, the optical transmission segment layer, the optical multiplexing segment layer, the optical channel layer, and the regeneration segment layer of the wavelength division multiplexing WDM network.
  • protocol layers are not exhaustive, such as the protocol layers of the Provider Backbone Bridge (PBB) network, and so on.
  • PBB Provider Backbone Bridge
  • the implementation method of the OAM function in this embodiment includes:
  • Step 210 The forwarding device at one end of the forwarding path receives the Openflow packet through the Openflow channel and parses the Openflow protocol header therein.
  • Step 220 The forwarding device, according to the analysis result, determines that the OpenFlow packet is an OAM configuration packet, parses the OAM configuration packet, obtains the OAM configuration information, and performs corresponding processing.
  • the forwarding device parses the Openflow protocol header, and determines that the Openflow packet is an OAM configuration packet
  • the method includes: the forwarding device parses the Openflow protocol header, and determines that the message type carried in the OAM is OAM.
  • the message type of the packet is configured to determine that the OpenFlow packet is an OAM configuration packet.
  • the message type of the OAM configuration packet is a new message type obtained by extending the message type defined by the Openflow protocol.
  • the obtained OAM configuration information includes all or part of the following information:
  • OAM identifier which indicates the identifier of the configured OAM instance.
  • the type of operation that indicates the type of operation to be performed
  • the period in which the packet is sent is the period in which the forwarding device sends OAM packets.
  • the OAM configuration information obtained by the forwarding device includes information of a local port, where the local port is a physical port or a logical port, and includes: an inbound port, indicating a port that receives OAM packets; and/or, Outbound port, indicating the port that sends OAM packets.
  • the forwarding path is a bidirectional forwarding path
  • the local port information acquired by the forwarding device includes inbound port information represented by flow table entry information and outgoing port information represented by group table information;
  • the forwarding device performs the corresponding processing, including: searching for the local inbound port according to the flow table entry information, and matching the local outbound port according to the group table information matching.
  • the forwarding path is a one-way forwarding path
  • the local port information acquired by the forwarding device includes inbound port information represented by flow table entry information or outgoing port information represented by group table information;
  • the forwarding device performs the corresponding processing, including: searching for the local inbound port according to the flow table entry information matching, or finding the local outgoing port according to the group table information matching.
  • the local port information is represented by the feature information generated by the controller, and the forwarding device performs corresponding processing, including: searching for a corresponding local port according to the feature information, and The local port binding found, the local port is a physical port or a logical port.
  • the operation type obtained by the forwarding device is newly added; the forwarding device performs corresponding processing, including: creating an OAM instance having the OAM identifier and binding the specified inbound port and/or the outbound port, where The inbound port receives the OAM packet, and/or sends the OAM packet according to the packet sending period on the outbound port; or
  • the operation type obtained by the forwarding device is modified; the forwarding device performs corresponding processing, including: finding an OAM instance to be configured according to the OAM identifier, and updating the configuration of the OAM instance according to the received OAM configuration information, according to the new Configuration to send and/or receive OAM messages; or
  • the operation type obtained by the forwarding device is deleted; the forwarding device performs corresponding processing, including: finding an OAM instance to be configured according to the OAM identifier, and deleting the OAM instance; or
  • the operation type obtained by the forwarding device is a pause; the forwarding device performs a corresponding process, including: finding an OAM instance to be configured according to the OAM identifier, and stopping the sending and/or receiving of the OAM packet; or
  • the operation type obtained by the forwarding device is a restart; the forwarding device performs the corresponding processing, including: finding an OAM instance to be configured according to the OAM identifier, and restarting sending and/or receiving the OAM packet.
  • the forwarding device that implements the OAM function of the forwarding path operation and maintenance management is implemented, and the forwarding device is a forwarding device at one end of the forwarding path, which can be shown in FIG. 6 (see also 7), including:
  • the OpenFlow protocol processing component 50 is configured to: receive an Openflow message sent by the controller through the Openflow channel, and parse the Openflow protocol header, and determine that the Openflow packet is an OAM configuration packet, and forward the packet to the OAM component for processing;
  • the OAM component 60 is configured to parse the OAM configuration packet, obtain OAM configuration information, and perform corresponding processing.
  • the Openflow protocol processing component parses the Openflow protocol header, and determines that the Openflow packet is an OAM configuration packet, and includes: parsing the Openflow protocol header, and determining a message type of the OAM configuration packet. And determining that the Openflow packet is an OAM configuration packet, where the message type of the OAM configuration packet is a new message type obtained by extending a message type defined by the Openflow protocol.
  • the OAM configuration information acquired by the OAM component includes all or part of the following information:
  • OAM identifier which indicates the identifier of the configured OAM instance.
  • the type of operation that indicates the type of operation to be performed
  • the period in which the packet is sent is the period in which the forwarding device sends OAM packets.
  • the OAM configuration information acquired by the OAM component includes information of a local port, where the local port is a physical port or a logical port, including:
  • Inbound port indicating the port that receives OAM packets
  • Outbound port indicating the port that sends OAM packets.
  • the information of the local port includes the inbound port information represented by the flow table entry information and the outgoing port information represented by the group table information;
  • the OAM component performs corresponding processing, including: matching, according to the flow table entry information Find the local inbound port, and find the local outbound port according to the group table information match.
  • the information of the local port includes the inbound port information represented by the flow table entry information, or the outgoing port information represented by the group table information;
  • the OAM component performs corresponding processing, including: searching for a local inbound port according to the flow table entry information matching, or finding a local outgoing port according to the group table information matching.
  • the operation type acquired by the OAM component is newly added; the OAM component performs corresponding processing, including: creating an OAM instance having the OAM identifier and binding with a specified inbound port and/or an outbound port, where The inbound port receives the OAM packet, and the OAM packet is sent according to the packet sending period; or
  • the operation type of the OAM component is modified.
  • the OAM component performs the corresponding processing, including: finding an OAM instance to be configured according to the OAM identifier, and updating the corresponding configuration of the OAM instance according to the received OAM configuration information. , sending and/or receiving OAM messages according to the new configuration; or
  • the operation type obtained by the OAM component is deleted; the OAM component performs corresponding processing, including: finding an OAM instance to be configured according to the OAM identifier, and deleting the OAM instance; or
  • the operation type of the OAM component is a pause; the OAM component performs the corresponding processing, including: finding an OAM instance to be configured according to the OAM identifier, and stopping the sending and/or receiving of the OAM packet; or
  • the operation type of the OAM component is restarted.
  • the OAM component performs the corresponding processing, including: finding an OAM instance to be configured according to the OAM identifier, and restarting the sending and/or receiving of the OAM packet.
  • the network protocol layer where the forwarding path associated with the forwarding device is located is one of the following network protocol layers:
  • the physical layer VLAN layer, IP layer, and service layer of Ethernet;
  • the physical layer, the optical transmission segment layer, the optical multiplexing segment layer, the optical channel layer, and the regeneration segment layer of the wavelength division multiplexing WDM network are the physical layer, the optical transmission segment layer, the optical multiplexing segment layer, the optical channel layer, and the regeneration segment layer of the wavelength division multiplexing WDM network.
  • the required OAM function can be completed whether it is a two-way path or a one-way path.
  • This example uses the controller to initiate a new bidirectional path AZ (that is, from the A port of the Forwarder NE1 to the Z port of the Forwarder NE2, and the NE1 and NE2 are the exemplary device names of the Forwarder).
  • AZ that is, from the A port of the Forwarder NE1 to the Z port of the Forwarder NE2
  • the NE1 and NE2 are the exemplary device names of the Forwarder.
  • the implementation includes the following steps:
  • Step 1 The controller initiates the configuration of the new bidirectional path A-Z fast OAM, and constructs the first OAM configuration packet and the second OAM configuration packet, and sends the two OAM configuration packets to the Forwarder NE1 and the Forwarder NE2 through the Openflow channel respectively.
  • the first OAM configuration packet and the second OAM configuration packet are both OpenFlow packets.
  • the message type carried by the Openflow protocol header (represented by the value of the type member) is selected, and 240 is selected as the message type of the OAM configuration message from the values not used by the type member.
  • the method is used to identify the OAM configuration packet, which is not described here.
  • the OAM configuration information (which can be carried in the common members) in the OAM configuration packet is as follows:
  • the group table information Y identifies that the bound A port is an outbound port, that is, sends and receives OAM packets on the same port.
  • the data packet of the first OAM configuration packet (referred to as the payload part) also carries the OAM packet transmission period and other required information, and the OAM packet transmission period is set to 10 milliseconds.
  • the local port includes two values, where the flow table entry information X identifies the bound Z port as an inbound port, and the group table information Q identifies the bound Z port as an outgoing port, and carries the other OAM configuration information carried. Same as the first OAM configuration message.
  • Step 2 The Openflow protocol processing component of the NE1 receives the Openflow packet and parses the type member in the protocol header.
  • the type value is 240, and the OAM configuration packet is forwarded to the OAM component.
  • the Openflow protocol processing component of the NE2 receives the Openflow packet. The packet is parsed by the type member in the protocol header. According to the type value of 240, the OAM configuration packet is forwarded to the OAM component.
  • Step 3 The OAM component of the NE1 parses the OAM configuration packet, and the value of the member action is 1 to determine the operation type is new.
  • the value of the member local port is X and Y, and the inbound port and the outgoing port bound to the OAM instance are determined. All are A ports.
  • the OAM packet sending period is 10 milliseconds. Create an OAM instance with the OAM ID of 1 (as part of the OAM component), construct the required OAM packets, start the 10-ms timer, periodically send OAM packets from the A port, and receive the same type from the A port probe. OAM message (message receipt)
  • the implementation is implemented by the forwarding component).
  • the OAM component of the NE2 resolves the OAM configuration packet.
  • the value of the member action is 1 and the operation type is new.
  • the member local port is P and Q.
  • the inbound port and the outgoing port bound to the OAM instance are both Z. Port: According to the parsing of the data packet, the OAM packet sending period is 10 milliseconds. Create an OAM instance with the OAM ID of 1. Configure the required OAM packet, start the 10-ms timer, periodically send OAM packets from the Z-port, and receive the same type of OAM packets from the Z-port probe.
  • This example illustrates the implementation of the present example by using the Controller to initiate an OAM transmission period in which the bidirectional path A-Z (the A port of the Forwarder NE1 to the Z port of the Forwarder NE2) is modified from 10 milliseconds to 3.33 milliseconds.
  • the implementation includes the following steps:
  • the controller initiates the configuration of the AZ fast OAM, and constructs the first OAM configuration packet, where the message member ID is 1; the message member action is 2, and the operation type is modified; the message member localPort includes 2
  • the value of the flow table entry information X indicates that the bound A port is an inbound port, and the group table information Y indicates that the bound A port is an outgoing port; the data packet carries a packet period of 3.33 milliseconds, and can carry other required information.
  • the first OAM configuration packet is sent to NE1 through the Openflow channel.
  • the second OAM configuration packet is configured, and the message member localPort includes two values, wherein the flow table entry information P identifies the bound Z port as an inbound port, and the group table information Q identifies the bound Z port as an outgoing port; the other OAM The configuration information is the same as that of the first OAM configuration packet.
  • the second OAM configuration packet is sent to NE2 through the Openflow channel.
  • Step 2 The Openflow protocol processing component of the NE1 receives the Openflow packet and parses the type member in the protocol header.
  • the type value is 240, and the OAM configuration packet is forwarded to the OAM component.
  • the Openflow protocol processing component of the NE2 receives the Openflow packet. The packet is parsed by the type member in the protocol header. According to the type value of 240, the OAM configuration packet is forwarded to the OAM component.
  • Step 3 The OAM component of the NE1 parses the OAM message structure, and the value of the member action is 2 to determine the operation type as the modified OAM; and the member local port takes the value X and Y to determine the OAM.
  • the inbound port and the outbound port bound to the instance are all A ports.
  • the OAM packet sending period is 3.33 milliseconds.
  • the OAM instance is valid and the OAM packet is sent.
  • the 10 millisecond timer is stopped, the 3.33 millisecond timer is started periodically, the OAM packet is periodically sent from the A port according to the new transmission period, and the same type of OAM packet is received from the A port.
  • the OAM component of the NE2 resolves the OAM message structure.
  • the value of the member action is 2, and the operation type is changed to OAM.
  • the value of the member local port is P and Q.
  • the inbound port and the outbound port bound to the OAM instance are both Z ports.
  • the OAM packet sending period is 3.33 milliseconds.
  • the OAM identifier 1 the 10 millisecond instance that has been in effect is found, the OAM packet sending period is modified, the 10 millisecond timer is stopped, and the 3.33 millisecond timer is started.
  • the OAM packet is periodically sent from the Z port according to the new transmission period, and the same type of OAM packet is received from the Z port detection.
  • the example of the present embodiment is to start the OAM of the bidirectional path A-Z (the A port of the Forwarder NE1 to the Z port of the Forwarder NE2).
  • the implementation includes the following steps:
  • the controller initiates the suspension of the AZ fast OAM to construct the first OAM configuration packet.
  • the message member action is 3, the identifier operation type is paused, and the value of other message members and the OAM packet are The value of the sending period is the same as that of the first OAM configuration packet of the second example.
  • the first OAM configuration packet is sent to NE1 through the Openflow channel.
  • the second OAM configuration packet is configured, and the message member action is 3, and the identifier operation type is paused.
  • the value of the other message member and the OAM packet sending period are the same as the second OAM configuration packet of the second example.
  • the OpenFlow channel sends the second OAM configuration packet to NE2.
  • Step 2 The Openflow protocol processing component of the NE1 receives the Openflow packet and parses the type member in the protocol header.
  • the type value is 240, and the OAM configuration packet is forwarded to the OAM component.
  • the Openflow protocol processing component of the NE2 receives the Openflow packet. The packet is parsed by the type member in the protocol header. According to the type value of 240, the OAM configuration packet is forwarded to the OAM component.
  • Step 3 The OAM component of the NE1 parses the OAM message structure, and determines that the operation type is suspended OAM according to the member action value of 3; and the inbound port and the outgoing port bound to the OAM instance are determined according to the member local port values of X and Y. It is the A port. According to the data packet parsing, the OAM packet sending period is 3.33 milliseconds. The OAM instance 1 is used to find the current OAM instance. The 3.33 millisecond timer is stopped and the OAM packet is sent and received from the A port. The OAM component of the NE2 resolves the OAM message structure. The value of the member action is 3, and the operation type is paused. The value of the local port is P and Q.
  • the inbound port and the outbound port bound to the OAM instance are both Z ports.
  • the OAM packet sending period is 3.33 milliseconds.
  • the OAM instance 1 is found to be valid.
  • the 3.33 millisecond timer is stopped and the OAM packet is sent and received from the Z port.
  • This example illustrates an embodiment of the present example by taking the OAM of the bidirectional path A-Z (the A port of the Forwarder NE1 to the Z port of the Forwarder NE2) that has been suspended.
  • the implementation includes the following steps:
  • the controller initiates the suspension of the two-way path AZ fast OAM, and constructs the first OAM configuration packet.
  • the message member action is 4, the identifier operation type is restart, and the values of other message members are
  • the value of the OAM packet sending period is the same as that of the first OAM configuration packet of the second example.
  • the first OAM configuration packet is sent to the NE1 through the Openflow channel.
  • the second OAM configuration packet is configured, and the message member action is 4, and the identifier operation type is restarted.
  • the value of the other message member and the OAM packet sending period are the same as the second OAM configuration packet of the second example.
  • the OpenFlow channel sends the second OAM configuration packet to NE2.
  • Step 2 The Openflow protocol processing component of the NE1 receives the Openflow packet and parses the type member in the protocol header.
  • the type value is 240, and the OAM configuration packet is forwarded to the OAM component.
  • the Openflow protocol processing component of the NE2 receives the Openflow packet. The packet is parsed by the type member in the protocol header. According to the type value of 240, the OAM configuration packet is forwarded to the OAM component.
  • Step 3 The OAM component of the NE1 parses the OAM message structure.
  • the value of the member action is 4 and the operation type is the restart OAM.
  • the member local port is X and Y.
  • the inbound port and the outbound port bound to the OAM instance are determined. It is the A port.
  • the OAM packet sending period is 3.33 milliseconds.
  • the OAM instance 1 is found to be valid.
  • the 3.33 millisecond timer is restarted and the OAM packet is sent and received from the A port.
  • the OAM component of the NE2 resolves the OAM message structure.
  • the value of the member action is 4 and the operation type is the restart OAM.
  • the member local port is P and Q.
  • the inbound port and the outbound port bound to the OAM instance are both Z ports.
  • the OAM packet sending period is 3.33 milliseconds.
  • the OAM instance that has been validated is found according to the OAM identifier 1.
  • the 3.33 millisecond timer is restarted, and the OAM packet is sent and received from the Z port.
  • This example illustrates an embodiment of the present example by taking the OAM of the controller to delete the bidirectional path A-Z (the A port of the Forwarder NE1 to the Z port of the Forwarder NE2).
  • the implementation includes the following steps:
  • Step 1 The CMC initiates the deletion of the fast OAM of the bidirectional path AZ to construct the first OAM configuration packet.
  • the message member action is 5
  • the identifier operation type is deleted
  • the value of other message members and the OAM report are The value of the packet sending period is the same as that of the first OAM configuration packet of the second example.
  • the first OAM configuration packet is sent to the NE1 through the Openflow channel.
  • the second OAM configuration packet is configured, and the message member action is 5, and the identifier operation type is deleted.
  • the value of the other message member and the OAM packet sending period are the same as the second OAM configuration packet of the second example.
  • the OpenFlow channel sends the second OAM configuration packet to NE2.
  • Step 2 The Openflow protocol processing component of the NE1 receives the Openflow packet and parses the type member in the protocol header.
  • the type value is 240, and the OAM configuration packet is forwarded to the OAM component.
  • the Openflow protocol processing component of the NE2 receives the Openflow packet. The packet is parsed by the type member in the protocol header. According to the type value of 240, the OAM configuration packet is forwarded to the OAM component.
  • Step 3 The OAM component of the NE1 parses the OAM message structure; 5: Determine the operation type to delete the OAM; determine the local port to be bound to the A port according to the value of the local port of the member; determine the OAM sending period as 3.33 milliseconds according to the data packet parsing; find the OAM instance that has been valid according to the OAM identifier, and delete the OAM instance.
  • the OAM instance (with the 3.33 millisecond timer being deleted) cancels the sending and receiving of OAM packets on the A port.
  • the OAM component of the NE2 resolves the OAM message structure.
  • the value of the member action is 5, and the operation type is deleted.
  • the local port of the member is determined to be the Z port.
  • the data is parsed according to the data packet.
  • the OAM sending period is 3.33.
  • the OAM instance is deleted based on the OAM ID.
  • the OAM instance is deleted.
  • the OAM instance is deleted (the 3.33 ms timer
  • Step 3 The OAM component of the NE1 parses the OAM message structure.
  • the value of the member action is 5, and the operation type is deleted.
  • the member port is X and Y.
  • the inbound port and the outbound port bound to the OAM instance are determined. It is the A port.
  • the OAM packet sending period is 3.33 milliseconds.
  • the OAM instance that has been validated is found according to the OAM identifier 1.
  • the OAM instance is deleted (the 3.33 millisecond timer is deleted at the same time), that is, the A port is deleted. Send and receive OAM packets.
  • the OAM component of the NE2 resolves the OAM message structure.
  • the value of the member action is 5, and the operation type is deleted.
  • the value of the local port is P and Q.
  • the inbound port and the outbound port bound to the OAM instance are both Z ports.
  • the OAM packet sending period is 3.33 milliseconds.
  • the OAM instance is validated according to the OAM identifier 1.
  • the OAM instance is deleted (the 3.33 millisecond timer is deleted). Send and receive.
  • the controller initiates the addition, modification, suspension, activation, or deletion of the OAM of the bidirectional path A-Z (the A port of the Forwarder NE1 to the Z port of the Forwarder NE2), but only the NE1 or NE2 belongs to the CMC control, refer to FIG. 9. So CMC only needs to interact with NE1 or NE2.
  • each implementation step only considers a separate setting for NE1 or NE2, which is each example in such a scenario.
  • the controller initiates the addition, modification, suspension, restart, and deletion of the one-way path A-Z (the A port of the Forwarder NE1 to the Z port of the Forwarder NE2).
  • the OAM function is taken as an example to illustrate the implementation of this document.
  • This example uses the controller to initiate a new one-way path A-Z (the A port of the Forwarder NE1 to the Z port of the Forwarder NE2) to send a fast OAM function with a period of 10 milliseconds.
  • the implementation includes the following steps:
  • Step 1 The CMC initiates the configuration of the fast OAM of the unidirectional path AZ, and constructs the first OAM configuration packet, where the message member id takes the value 1, the message member action is set to 1, and the identification operation type is new;
  • the member local port uses the group table information Y to identify the bound A port as the outbound port.
  • the data packet carries the packet period of 10 milliseconds. It can also carry other required information.
  • the first OAM configuration packet is sent to NE1 through the Openflow channel.
  • the second OAM configuration packet is constructed, and the message member localPort uses the flow table entry information P to identify the binding Z port as the inbound port.
  • the other OAM configuration information is the same as the first OAM configuration packet, and the second OAM is adopted through the Openflow channel. Configure the packet to be delivered to NE2.
  • Step 2 The Openflow protocol processing component of the NE1 receives the Openflow packet and parses the type member in the protocol header.
  • the type value is 240, and the OAM configuration packet is forwarded to the OAM component.
  • the Openflow protocol processing component of the NE2 receives the Openflow packet. The packet is parsed by the type member in the protocol header. According to the type value of 240, the OAM configuration packet is forwarded to the OAM component.
  • Step 3 The OAM component of the NE1 parses the OAM configuration packet, and the value of the member action is 1 to determine that the operation type is new.
  • the outbound port bound to the OAM instance is the A port.
  • the data packet is parsed to determine that the OAM packet sending period is 10 milliseconds.
  • the OAM component of the NE2 resolves the OAM configuration packet.
  • the value of the member action is 1 to determine the operation type. If the value of the local port is P, the inbound port bound to the OAM instance is the Z port. Analyze and determine that the OAM packet sending period is 10 milliseconds. An OAM instance with the OAM ID of 1 is created. The Z-port probe receives this type of OAM packet.
  • This example uses the Controller to modify the OAM transmission period of the unidirectional path A-Z (the A port of the Forwarder NE1 to the Z port of the Forwarder NE2), which is modified from 10 milliseconds to 3.33 milliseconds.
  • the implementation includes the following steps:
  • Step 1 The CMC initiates the modification of the fast OAM of the unidirectional path AZ, and constructs the first OAM configuration packet, wherein the message member id takes a value of 1, the message member action is 2, the identification operation type is modified, and the message member localPort uses the group.
  • Table Y indicates that the bound A port is the outbound port.
  • the data packet carries the packet period of 3.33 milliseconds. It can also carry other required information.
  • the first OAM configuration packet is sent to NE1 through the Openflow channel.
  • the second OAM configuration packet is constructed, and the message member localPort uses the flow table entry information P to identify the binding Z port as the inbound port.
  • the other OAM configuration information is the same as the first OAM configuration packet, and the second OAM is adopted through the Openflow channel. Configure the packet to be sent to NE2.
  • Step 2 The Openflow protocol processing component of the NE1 receives the Openflow packet and parses the type member in the protocol header.
  • the type value is 240, and the OAM configuration packet is forwarded to the OAM component.
  • the Openflow protocol processing component of the NE2 receives the Openflow packet. The packet is parsed by the type member in the protocol header. According to the type value of 240, the OAM configuration packet is forwarded to the OAM component.
  • Step 3 The OAM component of the NE1 parses the OAM configuration packet, and the value of the member action is 2, and the operation type is modified.
  • the outgoing port bound to the OAM instance is the A port.
  • the packet is parsed to determine that the OAM packet sending period is 3.33 milliseconds.
  • the OAM instance is valid.
  • the OAM instance is valid.
  • the OAM packet is sent from the A port.
  • the OAM component of E2 parses the OAM configuration packet, and the value of the member action is 2, and the operation type is modified.
  • the inbound port bound to the OAM instance is the Z port.
  • the judgment period of the OAM packet is 3.33 milliseconds.
  • the OAM instance that has been validated is found according to the OAM identifier 1.
  • the OAM packet with the transmission period of 3.33 milliseconds is received from the Z port.
  • This example uses the OAM that the Controller initiates to suspend the unidirectional path A-Z (the A port of the Forwarder NE1 to the Z port of the Forwarder NE2).
  • the implementation includes the following steps:
  • Step 1 The CMC initiates the suspension of the fast OAM of the unidirectional path AZ, and constructs the first OAM configuration packet, wherein the message member id takes a value of 1, the message member action is 3, the identification operation type is paused, and the message member localPort uses the group.
  • Table Y indicates that the bound A port is the outbound port.
  • the data packet carries the packet period of 3.33 milliseconds. It can also carry other required information.
  • the first OAM configuration packet is sent to NE1 through the Openflow channel.
  • the second OAM configuration packet is constructed, and the message member localPort uses the flow table entry information P to identify the binding Z port as the inbound port.
  • the other OAM configuration information is the same as the first OAM configuration packet, and the second OAM is adopted through the Openflow channel. Configure the packet to be sent to NE2.
  • Step 2 The Openflow protocol processing component of the NE1 receives the Openflow packet and parses the type member in the protocol header.
  • the type value is 240, and the OAM configuration packet is forwarded to the OAM component.
  • the Openflow protocol processing component of the NE2 receives the Openflow packet. The packet is parsed by the type member in the protocol header. According to the type value of 240, the OAM configuration packet is forwarded to the OAM component.
  • Step 3 The OAM component of the NE1 parses the OAM configuration packet, and the value of the member action is 3, and the operation type is paused.
  • the outgoing port bound to the OAM instance is the A port.
  • the packet is parsed to determine that the OAM packet sending period is 3.33 milliseconds.
  • the OAM instance that has been validated is found according to OAM ID 1.
  • the 3.33 millisecond timer is suspended and the OAM packet is sent from the A port.
  • the OAM component of the E2 resolves the OAM configuration packet.
  • the value of the member action is 3, and the operation type is paused.
  • the value of the member local port is P.
  • the inbound port bound to the OAM instance is the Z port.
  • the data packet is parsed according to the data packet.
  • the judgment period of the OAM packet is 3.33 milliseconds.
  • the OAM instance that has been validated is found according to the OAM identifier 1.
  • the OAM packet with the transmission period of 3.33 milliseconds is received from the Z port.
  • This example uses the OAM of the unidirectional path A-Z (the A port of the Forwarder NE1 to the Z port of the Forwarder NE2) that has been suspended.
  • the implementation includes the following steps:
  • Step 1 The CMC initiates a fast OAM to restart the unidirectional path AZ, and constructs a first OAM configuration packet, where the message member id takes a value of 1, the message member action is 4, the identification operation type is restart, and the message member localPort uses the group.
  • Table Y indicates that the bound A port is the outbound port.
  • the data packet carries the packet period of 3.33 milliseconds. It can also carry other required information.
  • the first OAM configuration packet is sent to NE1 through the Openflow channel.
  • the second OAM configuration packet is constructed, and the message member localPort uses the flow table entry information P to identify the binding Z port as the inbound port.
  • the other OAM configuration information is the same as the first OAM configuration packet, and the second OAM is adopted through the Openflow channel. Configure the packet to be sent to NE2.
  • Step 2 The Openflow protocol processing component of the NE1 receives the Openflow packet and parses the type member in the protocol header.
  • the type value is 240, and the OAM configuration packet is forwarded to the OAM component.
  • the Openflow protocol processing component of the NE2 receives the Openflow packet. The packet is parsed by the type member in the protocol header. According to the type value of 240, the OAM configuration packet is forwarded to the OAM component.
  • Step 3 The OAM component of the NE1 parses the OAM configuration packet, and the value of the member action is 4, and the operation type is restarted.
  • the outgoing port bound to the OAM instance is the A port.
  • the packet is parsed to determine that the OAM packet sending period is 3.33 milliseconds.
  • the OAM instance is valid.
  • the OAM instance is valid.
  • the OAM packet is sent from the A port.
  • the OAM component of the E2 resolves the OAM configuration packet.
  • the value of the member action is 4 and the operation type is restarted.
  • the member port is the P port.
  • the inbound port bound to the OAM instance is the Z port.
  • the data packet is parsed according to the data packet.
  • the judgment period of the OAM packet is 3.33 milliseconds.
  • the OAM instance that has been validated is found according to the OAM identifier 1.
  • the OAM packet with the transmission period of 3.33 milliseconds is received from the Z port.
  • This example uses the Controller to initiate the deletion of the one-way path A-Z (the Forwarder NE1 A port to For example, OAM of the Z port of the Forwarder NE2.
  • the implementation includes the following steps:
  • Step 1 The CMC initiates a fast OAM to restart the unidirectional path AZ, and constructs a first OAM configuration packet, where the message member id takes a value of 1, the message member action is 5, the identification operation type is deleted, and the message member localPort uses the group.
  • Table Y indicates that the bound A port is the outbound port.
  • the data packet carries the packet period of 3.33 milliseconds. It can also carry other required information.
  • the first OAM configuration packet is sent to NE1 through the Openflow channel.
  • the second OAM configuration packet is constructed, and the message member localPort uses the flow table entry information P to identify the binding Z port as the inbound port.
  • the other OAM configuration information is the same as the first OAM configuration packet, and the second OAM is adopted through the Openflow channel. Configure the packet to be sent to NE2.
  • Step 2 The Openflow protocol processing component of the NE1 receives the Openflow packet and parses the type member in the protocol header.
  • the type value is 240, and the OAM configuration packet is forwarded to the OAM component.
  • the Openflow protocol processing component of the NE2 receives the Openflow packet. The packet is parsed by the type member in the protocol header. According to the type value of 240, the OAM configuration packet is forwarded to the OAM component.
  • Step 3 The OAM component of the NE1 parses the OAM configuration packet, and the value of the member action is 5, and the operation type is deleted.
  • the outgoing port bound to the OAM instance is the A port.
  • the packet is parsed to determine that the OAM packet sending period is 3.33 milliseconds. If the OAM instance is valid, the OAM instance is deleted. The OAM instance is deleted. The OAM packet is deleted from the A port.
  • the OAM component of the E2 resolves the OAM configuration packet.
  • the value of the member action is 5, and the operation type is deleted.
  • the inbound port bound to the OAM instance is the Z port.
  • the data packet is parsed according to the data packet. The judgment period of the OAM packet is 3.33 milliseconds. If the OAM instance is valid, the OAM instance is deleted. The OAM instance is deleted. The OAM packet is sent to the Z-port.
  • the controller initiates the addition, modification, suspension, activation, or deletion of the OAM of the unidirectional path AZ (the A port of the Forwarder NE1 to the Z port of the Forwarder NE2), but only the NE1 belongs to the CMC control, as shown in FIG. . So the Controller only needs to interact with NE1.
  • each implementation step only considers the setting for NE1 as an embodiment in such a scenario.
  • the controller initiates the addition, modification, suspension, activation, or deletion of the OAM of the unidirectional path AZ (the A port of the Forwarder NE1 to the Z port of the Forwarder NE2), but only the NE2 belongs to the CMC control, as shown in FIG. . So the Controller only needs to interact with NE2.
  • each implementation step only considers the setting for NE2, which is an embodiment in such a scenario.
  • the OAM is inherently existing, and the operation of adding, deleting, and modifying the OAM is not required. Only the OAM monitoring function needs to be enabled or suspended, and the OAM monitoring function is enabled. Monitoring function, pause means that the OAM monitoring function is disabled.
  • the above solution is based on the specification interface between the Controller and the Forwarder of the existing SDN (not limited to SDN), and expands the message type to complete networks such as Ethernet, IP, MPLS, MPLS-TP, PBB, etc. based on packet transmission technology, and non-grouping.
  • the OTN and WDM networks of the transmission technology have the advantages of simplicity, reliability, and the like for adding, modifying, suspending, starting, and deleting the two-way or one-way path fast OAM.
  • all or part of the steps of the above embodiments may also be implemented by using an integrated circuit. These steps may be separately fabricated into individual integrated circuit modules, or multiple modules or steps may be fabricated into a single integrated circuit module. achieve.
  • the device/function module/functional unit in the above embodiments may be implemented by using a general-purpose computing device, which may be concentrated on a single computing device or distributed in multiple computing devices. On the network.
  • the device/function module/functional unit in the above embodiment When the device/function module/functional unit in the above embodiment is implemented in the form of a software function module and sold or used as a stand-alone product, it can be stored in a computer readable storage medium.
  • the above mentioned computer readable storage medium may be a read only memory, a magnetic disk or an optical disk or the like.
  • the OAM configuration message is used, and the OAM configuration is performed on the forwarding end of the forwarding path, so that the OAM packet can be sent and received at the Forwarder device level according to the standard requirements.
  • the newly defined OAM message completes the configuration functions of adding, modifying, suspending, starting, or deleting the OAM function, and has the advantages of simplicity and reliability.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Data Mining & Analysis (AREA)
  • Data Exchanges In Wide-Area Networks (AREA)

Abstract

一种操作维护管理功能的配置、实现方法及转发设备，控制器发起转发路径操作维护管理OAM功能的配置，构造OAM配置报文，所述OAM配置报文中携带OAM配置信息；所述控制器将所述OAM配置报文通过Openflow通道发送至所述转发路径的首端点转发设备和/或尾端点转发设备。转发路径一端的转发设备通过Openflow通道接收Openflow报文并解析Openflow协议头；所述转发设备根据解析结果，如确定所述Openflow报文为OAM配置报文，则对所述OAM配置报文进行解析，获取其中的OAM配置信息并实施相应的处理。

Description

一种操作维护管理功能的配置、实现方法及转发设备 技术领域
本文涉及操作维护管理(OAM:Operation,administration and maintenance)功能，尤其涉及一种操作维护管理功能的实现方法及相应的转发设备。
背景技术
软件定义网络(Software defined network，简称SDN)是近年来通信领域的研究热点。国际标准组织ONF(Open networking forum，简称ONF)拟定SDN相关标准建议，重点在于控制器(Controller，简称CP)和转发设备(Forwarder)之间解耦，规范控制器与转发面之间的接口，方便不同厂家的控制器、转发设备联合组网。
ONF目前已经发布了控制器与转发面之间接口规范OpenFlow Switch Specification，基于此接口规范实施的协议为Openflow协议。ONF近几年组织了多次互联互通测试，在支持二层业务、二层VPN业务方面比较成熟。
如图1所示，Openflow通道用于控制器(后文简称Controller)与转发设备(后文简称Forwarder，也有简称为switch的，同样指转发设备)之间的Openflow协议交互。控制器发送的协议消息至转发设备后，转发设备的协议处理组件终结协议，提取协议报文携带的内容信息，转发至相应组件。同样转发设备内相关组件发送至控制器的信息，需要先传递至协议处理组件封装为Openflow协议消息并发送至控制器。
Openflow协议定义了一系列消息，包括controller-to-switch，asynchronous和symmetric三种大类，每个大类又定义了很多类型。controller-to-switch消息由控制器发起，用来管理或获取forwarder状态；asynchronous消息由forwarder发起，用来将网络事件或forwarder状态变化通知到控制器；symmetric消息可由forwarder或控制器发起。
在支持OAM功能方面，控制器通过发起controller-to-switch类别的Packet-out的消息，通过Openflow通道发送至Forwarder。Forwarder根据消息 指定的端口发送，接收端Forwarder收到此消息后，根据消息指示完成相关的工作(比如收发包统计、错包统计等等)，并上送至协议处理组件，封装为Packet-in消息通过Openflow通道上送至控制器，如图2所示。如此，控制器通过Packet-out和Packet-in消息完成了转发设备之间指定路径的检测功能。但这种机制适合用户发起，且对实时性要求不高的按需检测场景；不适合需要周期性快速发送和接收，用于保护倒换或其他目的报文，比如MPLS-TP(国际电联ITU-T等国际标准规范的分组传送技术标准)标准要求支持3.33毫秒周期性收发的快速CCM(连通性检测报文)。这种快速报文一般需要在Forwarder设备层面快速收发。
发明内容
如何在OpenFlow Switch Specification已有标准接口基础上进行OAM配置，以按照标准的要求实现OAM报文在Forwarder设备层面的收发，是急待解决的技术问题。
一种操作维护管理功能的配置方法，包括：
控制器发起转发路径操作维护管理OAM功能的配置，构造OAM配置报文，所述OAM配置报文中携带OAM配置信息；
所述控制器将所述OAM配置报文通过Openflow通道发送至所述转发路径的首端点转发设备和/或尾端点转发设备。
可选地；
所述OAM配置报文中Openflow协议头携带的消息类型，是对Openflow协议定义的消息类型扩展得到的新的消息类型。
可选地；
所述OAM配置信息包括以下全部或部分信息：
OAM标识，表示所配置的OAM实例的标识；
操作类型，表示要实施的操作的类型；
本地端口，表示转发设备上OAM实例绑定的端口；
报文发送周期，表示转发设备发送OAM报文的周期。
可选地；
所述本地端口为物理端口或逻辑端口，包括：
入向端口，表示接收OAM报文的端口；和/或
出向端口，表示发送OAM报文的端口。
可选地；
所述转发路径为双向转发路径，所述控制器构造OAM配置报文，包括：
构造要发送到所述双向转发路径首端点转发设备的第一OAM配置报文，其中携带所述首端点转发设备上的本地端口信息，包括用流表条目信息表示的入向端口信息和用组表信息表示的出向端口信息；
构造要发送到所述双向转发路径尾端点转发设备的第二OAM配置报文，其中携带所述尾端点转发设备上的本地端口信息，包括用流表条目信息表示的入向端口信息和用组表信息表示的出向端口信息。
可选地；
所述转发路径为单向转发路径，所述控制器构造OAM配置报文，包括：
构造要发送到所述单向转发路径首端点转发设备的第一OAM配置报文，其中携带所述首端点转发设备上的本地端口信息，包括用组表信息表示的出向端口信息；
构造要发送到所述单向转发路径尾端点转发设备的第二OAM配置报文，其中携带所述尾端点转发设备上的本地端口信息，包括用流表条目信息表示的入向端口信息。
可选地；
所述操作类型为新增、修改、启动、暂停和删除中的一种。
可选地；
所述转发路径所在的网络协议层为以下网络协议层中的一种：
以太网的物理层、VLAN层、IP层和业务层；
多协议标签交换MPLS网络或多协议标签交换-传送架构MPLS-TP网络的隧道层、伪线层和业务层；
光传送网络OTN的物理层、段层和ODUk层；
波分复用WDM网络的物理层、光传输段层、光复用段层、光通道层和再生段层。
一种操作维护管理OAM功能的实现方法，包括：
转发路径一端的转发设备通过Openflow通道接收Openflow报文并解析其中的Openflow协议头；
所述转发设备根据解析结果，如确定所述Openflow报文为OAM配置报文，则对所述OAM配置报文进行解析，获取其中的OAM配置信息并实施相应的处理。
可选地；
所述转发设备解析所述Openflow协议头，确定所述Openflow报文为OAM配置报文，包括：
所述转发设备解析所述Openflow协议头，如判断其中携带的消息类型为OAM配置报文的消息类型，则确定所述Openflow报文为OAM配置报文；其中，所述OAM配置报文的消息类型是对Openflow协议定义的消息类型扩展得到的新的消息类型。
可选地；
所述转发设备获取的所述OAM配置信息包括以下全部或部分信息：
OAM标识，表示所配置的OAM实例的标识；
操作类型，表示要实施的操作的类型；
本地端口，表示转发设备上OAM实例绑定的端口；
报文发送周期，表示转发设备发送OAM报文的周期。
可选地；
所述转发设备获取的所述OAM配置信息包括本地端口的信息，所述本地端口为物理端口或逻辑端口，包括：
入向端口，表示接收OAM报文的端口；和/或
出向端口，表示发送OAM报文的端口。
可选地；
所述转发路径为双向转发路径；
所述转发设备获取的所述本地端口信息包括用流表条目信息表示的入向端口信息和用组表信息表示的出向端口信息；
所述转发设备实施相应的处理，包括：根据所述流表条目信息匹配查找到本地的入向端口，及根据所述组表信息匹配查找到本地的出向端口。
可选地；
所述转发路径为单向转发路径；
所述转发设备获取的本地端口信息包括用流表条目信息表示的入向端口信息或用组表信息表示的出向端口信息；
所述转发设备实施相应的处理，包括：根据所述流表条目信息匹配查找到本地的入向端口，或根据所述组表信息匹配查找到本地的出向端口。
可选地；
所述转发设备获取的操作类型为新增；所述转发设备实施相应的处理，包括：创建具有所述OAM标识的OAM实例并与指定的入向端口和/或出向端口绑定，在所述入向端口接收OAM报文，和/或在所述出向端口按照所述报文发送周期发送OAM报文；或者
所述转发设备获取的操作类型为修改；所述转发设备实施相应的处理，包括：根据所述OAM标识找到要配置的OAM实例，根据接收的OAM配置信息更新所述OAM实例的配置，按照新的配置发送和/或接收OAM报文；或者
所述转发设备获取的操作类型为删除；所述转发设备实施相应的处理，包括：根据所述OAM标识找到要配置的OAM实例，将所述OAM实例删 除；或者
所述转发设备获取的操作类型为暂停；所述转发设备实施相应的处理，包括：根据所述OAM标识找到要配置的OAM实例，停止OAM报文的发送和/或接收；或者
所述转发设备获取的操作类型为重启；所述转发设备实施相应的处理，包括：根据所述OAM标识找到要配置的OAM实例，重启OAM报文的发送和/或接收。
可选地；
所述转发路径所在的网络协议层为以下网络协议层中的一种：
以太网的物理层、VLAN层、IP层和业务层；
多协议标签交换MPLS网络或多协议标签交换-传送架构MPLS-TP网络的隧道层、伪线层和业务层；
光传送网络OTN的物理层、段层和ODUk层；
波分复用WDM网络的物理层、光传输段层、光复用段层、光通道层和再生段层。
一种可配置转发路径操作维护管理OAM功能的控制器，包括：
报文构造模块，设置为：在发起转发路径OAM功能的配置时，构造OAM配置报文，所述OAM配置报文中携带OAM配置信息；
报文发送模块，设置为：将所述OAM配置报文通过Openflow通道发送至所述转发路径的首端点转发设备和/或尾端点转发设备。
可选地；
所述报文构造模块构造的所述OAM配置报文中，Openflow协议头携带的消息类型是对Openflow协议定义的消息类型扩展得到的新的消息类型。
可选地；
所述报文构造模块构造的所述OAM配置报文中，携带的OAM配置信息包括以下全部或部分信息：
OAM标识，表示所配置的OAM实例的标识；
操作类型，表示要实施的操作的类型；
本地端口，表示转发设备上OAM实例绑定的端口；
报文发送周期，表示转发设备发送OAM报文的周期。
可选地；
所述报文构造模块构造的所述OAM配置报文中，携带的所述本地端口为物理端口或逻辑端口，包括：
入向端口，表示接收OAM报文的端口；和/或
出向端口，表示发送OAM报文的端口。
可选地；
所述转发路径为双向转发路径；
所述报文构造模块是设置为：
构造要发送到所述双向转发路径首端点转发设备的第一OAM配置报文，其中携带所述首端点转发设备上的本地端口信息，包括用流表条目信息表示的入向端口信息和用组表信息表示的出向端口信息；
构造要发送到所述双向转发路径尾端点转发设备的第二OAM配置报文，其中携带所述尾端点转发设备上的本地端口信息，包括用流表条目信息表示的入向端口信息和用组表信息表示的出向端口信息。
可选地；
所述转发路径为单向转发路径；
所述报文构造模块构造OAM配置报文，包括：
构造要发送到所述单向转发路径首端点转发设备的第一OAM配置报文，其中携带所述首端点转发设备上的本地端口信息，包括用组表信息表示的出向端口信息；
构造要发送到所述单向转发路径尾端点转发设备的第二OAM配置报文，其中携带所述尾端点转发设备上的本地端口信息，包括用流表条目信息表示的入向端口信息。
可选地；
所述报文构造模块构造的所述OAM配置报文中，携带的OAM配置信息中的操作类型为新增、修改、启动、暂停和删除中的一种。
可选地；
报文构造模块在发起转发路径OAM功能的配置时构造OAM配置报文，其中，所述转发路径所在的网络协议层为以下网络协议层中的一种：
以太网的物理层、VLAN层、IP层和业务层；
多协议标签交换MPLS网络或多协议标签交换-传送架构MPLS-TP网络的隧道层、伪线层和业务层；
光传送网络OTN的物理层、段层和ODUk层；
波分复用WDM网络的物理层、光传输段层、光复用段层、光通道层和再生段层。
一种可实现转发路径操作维护管理OAM功能的转发设备，包括：
Openflow协议处理组件，设置为：通过Openflow通道接收控制器发送的Openflow报文并解析其中的Openflow协议头，如确定所述Openflow报文为OAM配置报文，转发到OAM组件处理；
OAM组件，设置为：对所述OAM配置报文进行解析，获取其中的OAM配置信息并实施相应的处理。
可选地；
所述Openflow协议处理组件是设置为：解析所述Openflow协议头，如判断其中携带的消息类型为OAM配置报文的消息类型，则确定所述Openflow报文为OAM配置报文；其中，所述OAM配置报文的消息类型是对Openflow协议定义的消息类型扩展得到的新的消息类型。
可选地；
所述OAM组件获取的OAM配置信息包括以下全部或部分信息：
OAM标识，表示所配置的OAM实例的标识；
操作类型，表示要实施的操作的类型；
本地端口，表示转发设备上OAM实例绑定的端口；
报文发送周期，表示转发设备发送OAM报文的周期。
可选地；
所述OAM组件获取的OAM配置信息包括本地端口的信息，其中，所述本地端口为物理端口或逻辑端口，包括：
入向端口，表示接收OAM报文的端口；和/或
出向端口，表示发送OAM报文的端口。
可选地；
所述OAM组件获取的OAM配置信息中，本地端口的信息包括用流表条目信息表示的入向端口信息和用组表信息表示的出向端口信息；
所述OAM组件实施相应的处理，包括：根据所述流表条目信息匹配查找到本地的入向端口，及根据所述组表信息匹配查找到本地的出向端口。
可选地；
所述OAM组件获取的OAM配置信息中，本地端口的信息包括用流表条目信息表示的入向端口信息，或用组表信息表示的出向端口信息；
所述OAM组件实施相应的处理，包括：根据所述流表条目信息匹配查找到本地的入向端口，或根据所述组表信息匹配查找到本地的出向端口。
可选地；
所述OAM组件获取的操作类型为新增；所述OAM组件是设置为：创建具有所述OAM标识的OAM实例并与指定的入向端口和/或出向端口绑定，在所述入向端口接收OAM报文，和/或在所述出向端口按照所述报文发送周期发送OAM报文；或者
所述OAM组件获取的操作类型为修改；所述OAM组件是设置为：根据所述OAM标识找到要配置的OAM实例，根据此次接收的OAM配置信息更新所述OAM实例的相应配置，按照新的配置发送和/或接收OAM报文；或者
所述OAM组件获取的操作类型为删除；所述OAM组件是设置为：根据所述OAM标识找到要配置的OAM实例，将所述OAM实例删除；或者
所述OAM组件获取的操作类型为暂停；所述OAM组件是设置为：根据所述OAM标识找到要配置的OAM实例，停止OAM报文的发送和/或接收；或者
所述OAM组件获取的操作类型为重启；所述OAM组件是设置为：根据所述OAM标识找到要配置的OAM实例，重启OAM报文的发送和/或接收。
可选地；
所述转发设备关联的所述转发路径所在的网络协议层为以下网络协议层中的一种：
以太网的物理层、VLAN层、IP层和业务层；
多协议标签交换MPLS网络或多协议标签交换-传送架构MPLS-TP网络的隧道层、伪线层和业务层；
光传送网络OTN的物理层、段层和ODUk层；
波分复用WDM网络的物理层、光传输段层、光复用段层、光通道层和再生段层。
一种计算机可读存储介质，存储有计算机可执行指令，所述计算机可执行指令用于执行上述任一项的方法。
上述实施方案通过OAM配置报文，在转发路径首、尾端点Forwarder进行OAM配置，从而可以按照标准的要求实现OAM报文在Forwarder设备层面的收发。而通过扩展Openflow协议头的消息类型，新定义OAM消息完成OAM功能的新增、修改、暂停、启动或删除等配置功能，具备简洁、可靠的优点。
附图概述
图1是SDN网络简单示意图；
图2是SDN网络Packet-out和Packet-in消息收发示意图；
图3是本发明实施例一方法的流程图；
图4是本发明实施例一控制器的模块图；
图5是本发明实施例二方法的流程图；
图6是本发明实施例二转发设备的模块图；
图7是本发明应用示例配置双向路径OAM的示意图；
图8是本发明应用示例配置单向路径OAM的示意图；
图9是本发明应用示例只配置双向路径一个端点Forwarder的OAM的示意图；
图10是本发明应用示例只配置单向路径首端点Forwarder的OAM的示意图；
图11是本发明应用示例只配置单向路径尾端点Forwarder的OAM的示意图。
本发明的实施方式
下文中将结合附图对本发明的实施方式进行详细说明。
实施例一
本实施例基于已有Openflow协议，扩展协议头的消息类型，通过新定义的OAM配置报文，完成双向/单向转发路径的OAM功能配置管理。所述转发路径(在一些标准中也称为传输路径或传送路径)所在的网络协议层(一些标准中也称为层网络)为以下网络协议层中的一种：
以太网的物理层、VLAN层、IP层和业务层；
多协议标签交换MPLS网络或多协议标签交换-传送架构MPLS-TP网络的隧道层、伪线层和业务层；
光传送网络OTN的物理层、段层和ODUk(光通道数据单元)-层；
波分复用WDM网络的物理层、光传输段层、光复用段层、光通道层和再生段层。
上述协议层并不是穷举的，如还可以是运营商骨干桥接(PBB：Provider Backbone Bridge)网络的各个协议层，等等。
本实施例操作维护管理功能的配置方法如图3所示，包括：
步骤110，控制器发起转发路径操作维护管理OAM功能的配置，构造OAM配置报文，所述OAM配置报文中携带OAM配置信息；
所述OAM配置报文中Openflow协议头携带的消息类型，是对Openflow协议定义的消息类型扩展得到的新的消息类型。
所述OAM配置信息包括以下全部或部分信息：
OAM标识，表示所配置的OAM实例的标识；
操作类型，表示要实施的操作的类型；
本地端口，表示转发设备上OAM实例绑定的端口；
报文发送周期，表示转发设备发送OAM报文的周期。
其中，操作类型可以为新增、修改、启动、暂停和删除中的一种；
其中，所述本地端口为物理端口(如以太网、OTN或WDM等物理端口等)或逻辑端口(如太网的VLAN端口，MPLS或MPLS_TP的隧道或伪线端口，OTN的ODUk通道端口等)，包括：入向端口，表示接收OAM报文的端口；和/或，出向端口，表示发送OAM报文的端口。当转发路径为双向转发路径时，OAM配置报文中的本地端口可以包括入向端口和出向端口，但只在端口上发送OAM报文(如OAM检测报文)时，也可以只包括入向端口，只在端口上接收OAM报文时，也可以只包括出向端口。
本步骤中，所述转发路径为双向转发路径时，所述控制器构造OAM配置报文，包括：
构造要发送到所述双向转发路径首端点转发设备的第一OAM配置报文，其中携带所述首端点转发设备上的本地端口信息，包括用流表条目信息 (如流表(Flow Table)的表标识(Table id)、键值(KEY)等)表示的入向端口信息和用组表信息(如组表(Group table)的组标识(Group id)等)表示的出向端口信息；
构造要发送到所述双向转发路径尾端点转发设备的第二OAM配置报文，其中携带所述尾端点转发设备上的本地端口信息，包括用流表条目信息表示的入向端口信息和用组表信息表示的出向端口信息。
本步骤中，所述转发路径为单向转发路径时，所述控制器构造OAM配置报文，包括：
构造要发送到所述单向转发路径首端点转发设备的第一OAM配置报文，其中携带所述首端点转发设备上的本地端口信息，包括用组表信息表示的出向端口信息；
构造要发送到所述单向转发路径尾端点转发设备的第二OAM配置报文，其中携带所述尾端点转发设备上的本地端口信息，包括用流表条目信息表示的入向端口信息。
例如，本地端口可以用Openflow流表的KEY表示，转发设备根据所述KEY去匹配流表就可以找到对应的物理端口或逻辑端口。
步骤120，所述控制器将所述OAM配置报文通过Openflow通道发送至所述转发路径的首端点转发设备和/或尾端点转发设备。
本步骤中，控制器将构造的第一OAM配置报文发送给首端点转发设备，将构造的第二OAM配置报文发送给尾端点转发设备。
虽然实施例是构造两个OAM配置报文，发送给首端口和尾端点的转发设备。但在特殊的应用场景下(下文将提到)，控制器也可以只构造一个OAM配置报文，发送给首端口或尾端口的一个转发设备。
相应地，本实施例可配置转发路径操作维护管理OAM功能的控制器如图4所示，包括：
报文构造模块10，设置为：在发起转发路径OAM功能的配置时，构造OAM配置报文，所述OAM配置报文中携带OAM配置信息；
报文发送模块20，设置为：将所述OAM配置报文通过Openflow通道发送至所述转发路径的首端点转发设备和/或尾端点转发设备。
可选地，
所述报文构造模块构造的所述OAM配置报文中，Openflow协议头携带的消息类型是对Openflow协议定义的消息类型扩展得到的新的消息类型。
可选地，
所述报文构造模块构造的所述OAM配置报文中，携带OAM配置信息包括以下全部或部分信息：
OAM标识，表示所配置的OAM实例的标识；
操作类型，表示要实施的操作的类型；
本地端口，表示转发设备上OAM实例绑定的端口；
报文发送周期，表示转发设备发送OAM报文的周期。
可选地，
所述报文构造模块构造的所述OAM配置报文中，携带OAM配置信息还包括：收发指示，设置为：表示在本地端口上发送OAM报文，或接收OAM报文，或同时发送和接收OAM报文。
可选地，
所述报文构造模块构造的所述OAM配置报文中，携带的OAM配置信息中的操作类型为新增、修改、启动、暂停和删除中的一种。
可选地，
所述报文构造模块构造的所述OAM配置报文中，携带的OAM配置信息中的本地端口信息用所述控制器生成的特征信息表示，所述特征信息与所述首端点转发设备和/或尾端点转发设备上的本地端口具有对应关系，所述本地端口为物理端口或逻辑端口。
可选地，
所述报文构造模块构造OAM配置报文，包括：为所述首端点转发设备构造第一OAM配置报文，为所述尾端点转发设备构造第二OAM配置报文；
所述报文发送模块将所述OAM配置报文通过Openflow通道发送至所述转发路径的首端点转发设备和/或尾端点转发设备，包括：将所述第一OAM配置报文发送给所述首端点转发设备，将所述第二OAM配置报文发送给所述尾端点转发设备。
可选地，
报文构造模块在发起转发路径OAM功能的配置时构造OAM配置报文，其中，所述转发路径所在的网络协议层为以下网络协议层中的一种：
以太网的物理层、VLAN层、IP层和业务层；
多协议标签交换MPLS网络或多协议标签交换-传送架构MPLS-TP网络的隧道层、伪线层和业务层；
光传送网络OTN的物理层、段层和ODUk层；
波分复用WDM网络的物理层、光传输段层、光复用段层、光通道层和再生段层。
实施例二
本实施例涉及转发路径一端的转发设备接收到OAM配置报文后，如何实现OAM功能，所述转发路径所在的网络协议层可以为以下网络协议层中的一种：
以太网的物理层、VLAN层、IP层和业务层；
多协议标签交换MPLS网络或多协议标签交换-传送架构MPLS-TP网络的隧道层、伪线层和业务层；
光传送网络OTN的物理层、段层和ODUk层；
波分复用WDM网络的物理层、光传输段层、光复用段层、光通道层和再生段层。
上述协议层并不是穷举的，如还可以是运营商骨干桥接(PBB：Provider Backbone Bridge)网络的各个协议层，等等。
如图5所示，本实施例OAM功能的实现方法包括：
步骤210，转发路径一端的转发设备通过Openflow通道接收Openflow报文并解析其中的Openflow协议头；
步骤220，所述转发设备根据解析结果，如确定所述Openflow报文为OAM配置报文，则对所述OAM配置报文进行解析，获取其中的OAM配置信息并实施相应的处理。
本实施例中，所述转发设备解析所述Openflow协议头，确定所述Openflow报文为OAM配置报文，包括：所述转发设备解析所述Openflow协议头，如判断其中携带的消息类型为OAM配置报文的消息类型，则确定所述Openflow报文为OAM配置报文；其中，所述OAM配置报文的消息类型是对Openflow协议定义的消息类型扩展得到的新的消息类型。
获取的所述OAM配置信息包括以下全部或部分信息：
OAM标识，表示所配置的OAM实例的标识；
操作类型，表示要实施的操作的类型；
本地端口，表示转发设备上OAM实例绑定的端口；
报文发送周期，表示转发设备发送OAM报文的周期。
本步骤中，所述转发设备获取的所述OAM配置信息包括本地端口的信息，所述本地端口为物理端口或逻辑端口，包括：入向端口，表示接收OAM报文的端口；和/或，出向端口，表示发送OAM报文的端口。
在一示例中，所述转发路径为双向转发路径；
所述转发设备获取的所述本地端口信息包括用流表条目信息表示的入向端口信息和用组表信息表示的出向端口信息；
所述转发设备实施相应的处理，包括：根据所述流表条目信息匹配查找到本地的入向端口，及根据所述组表信息匹配查找到本地的出向端口。
在一示例中，所述转发路径为单向转发路径；
所述转发设备获取的本地端口信息包括用流表条目信息表示的入向端口信息或用组表信息表示的出向端口信息；
所述转发设备实施相应的处理，包括：根据所述流表条目信息匹配查找到本地的入向端口，或根据所述组表信息匹配查找到本地的出向端口。
本步骤中，所述本地端口信息如用所述控制器生成的特征信息表示；所述转发设备实施相应的处理，包括：根据所述特征信息查找到对应的本地端口，将所述OAM实例与查找到的所述本地端口绑定，所述本地端口为物理端口或逻辑端口。
本步骤中，根据获取的操作类型，可以分别执行以下处理：
所述转发设备获取的操作类型为新增；所述转发设备实施相应的处理，包括：创建具有所述OAM标识的OAM实例并与指定的入向端口和/或出向端口绑定，在所述入向端口接收OAM报文，和/或在所述出向端口按照所述报文发送周期发送OAM报文；或者
所述转发设备获取的操作类型为修改；所述转发设备实施相应的处理，包括：根据所述OAM标识找到要配置的OAM实例，根据接收的OAM配置信息更新所述OAM实例的配置，按照新的配置发送和/或接收OAM报文；或者
所述转发设备获取的操作类型为删除；所述转发设备实施相应的处理，包括：根据所述OAM标识找到要配置的OAM实例，将所述OAM实例删除；或者
所述转发设备获取的操作类型为暂停；所述转发设备实施相应的处理，包括：根据所述OAM标识找到要配置的OAM实例，停止OAM报文的发送和/或接收；或者
所述转发设备获取的操作类型为重启；所述转发设备实施相应的处理，包括：根据所述OAM标识找到要配置的OAM实例，重启OAM报文的发送和/或接收。
相应地，本实施例可实现转发路径操作维护管理OAM功能的转发设备，所述转发设备为转发路径一端的转发设备，可图6所示(可同时参见图 7)，包括：
Openflow协议处理组件50，设置为：通过Openflow通道接收控制器发送的Openflow报文并解析其中的Openflow协议头，如确定所述Openflow报文为OAM配置报文，转发到OAM组件处理；
OAM组件60，设置为：对所述OAM配置报文进行解析，获取其中的OAM配置信息并实施相应的处理。
可选地，
所述Openflow协议处理组件解析所述Openflow协议头，确定所述Openflow报文为OAM配置报文，包括：解析所述Openflow协议头，如判断其中携带的消息类型为OAM配置报文的消息类型，则确定所述Openflow报文为OAM配置报文；其中，所述OAM配置报文的消息类型是对Openflow协议定义的消息类型扩展得到的新的消息类型。
可选地，
所述OAM组件获取的OAM配置信息包括以下全部或部分信息：
OAM标识，表示所配置的OAM实例的标识；
操作类型，表示要实施的操作的类型；
本地端口，表示转发设备上OAM实例绑定的端口；
报文发送周期，表示转发设备发送OAM报文的周期。
可选地，
所述OAM组件获取的OAM配置信息包括本地端口的信息，其中，所述本地端口为物理端口或逻辑端口，包括：
入向端口，表示接收OAM报文的端口；和/或
出向端口，表示发送OAM报文的端口。
可选地，
所述OAM组件获取的OAM配置信息中，本地端口的信息包括用流表条目信息表示的入向端口信息和用组表信息表示的出向端口信息；
所述OAM组件实施相应的处理，包括：根据所述流表条目信息匹配查 找到本地的入向端口，及根据所述组表信息匹配查找到本地的出向端口。
可选地，
所述OAM组件获取的OAM配置信息中，本地端口的信息包括用流表条目信息表示的入向端口信息，或用组表信息表示的出向端口信息；
所述OAM组件实施相应的处理，包括：根据所述流表条目信息匹配查找到本地的入向端口，或根据所述组表信息匹配查找到本地的出向端口。
可选地，
所述OAM组件获取的操作类型为新增；所述OAM组件实施相应的处理，包括：创建具有所述OAM标识的OAM实例并与指定的入向端口和/或出向端口绑定，在所述入向端口接收OAM报文，在所述出向端口按照所述报文发送周期发送OAM报文；或者
所述OAM组件获取的操作类型为修改；所述OAM组件实施相应的处理，包括：根据所述OAM标识找到要配置的OAM实例，根据此次接收的OAM配置信息更新所述OAM实例的相应配置，按照新的配置发送和/或接收OAM报文；或者
所述OAM组件获取的操作类型为删除；所述OAM组件实施相应的处理，包括：根据所述OAM标识找到要配置的OAM实例，将所述OAM实例删除；或者
所述OAM组件获取的操作类型为暂停；所述OAM组件实施相应的处理，包括：根据所述OAM标识找到要配置的OAM实例，停止OAM报文的发送和/或接收；或者
所述OAM组件获取的操作类型为重启；所述OAM组件实施相应的处理，包括：根据所述OAM标识找到要配置的OAM实例，重启OAM报文的发送和/或接收。
可选地，
所述转发设备关联的所述转发路径所在的网络协议层为以下网络协议层中的一种：
以太网的物理层、VLAN层、IP层和业务层；
多协议标签交换MPLS网络或多协议标签交换-传送架构MPLS-TP网络的隧道层、伪线层和业务层；
光传送网络OTN的物理层、段层和ODUk层；
波分复用WDM网络的物理层、光传输段层、光复用段层、光通道层和再生段层。
从上面每个实施方式分析可知，无论是双向路径，还是单向路径，都可以完成所需的OAM功能。
请结合图7-11，以几个应用示例作进一步的描述。
应用示例一
本示例以Controller发起新增双向路径A-Z(即从Forwarder NE1的A端口到Forwarder NE2的Z端口，NE1,NE2为Forwarder示例性的的设备名称)发送周期10毫秒的快速OAM功能为例说明本实施例的实施方案。
实施方案包括如下步骤：
步骤一、Controller发起新增双向路径A-Z快速OAM的配置，构造第一OAM配置报文和第二OAM配置报文，将两个OAM配置报文通过Openflow通道分别发送给Forwarder NE1和Forwarder NE2；
Openflow协议头的通用成员如下表所示：
Figure PCTCN2015083093-appb-000001
第一OAM配置报文和第二OAM配置报文均为Openflow报文，通过扩 展Openflow协议头携带的消息类型(用type成员的值表示)，从type成员未用到的值中选择240作为OAM配置消息的消息类型。其他示例中，均是使用该方式来标识OAM配置报文，在下文不再赘述。
OAM配置报文中的OAM配置信息(可携带在通用成员中)如下表所示：
header Openflow协议头
id OAM标识
localPort OAM绑定的本地端口
data 报文内容
本示例中，ID值为1，表示OAM标识为1；action值为1，表示操作类型为新增；消息成员localPort包括2个值，其中流表条目信息X标识绑定A端口为入向端口，组表信息Y标识绑定A端口为出向端口，即在同一端口上发送和接收OAM报文。第一OAM配置报文的data报文(指净荷部分)还携带有OAM报文发送周期和其他所需信息，OAM报文发送周期设为10毫秒。第二OAM配置报文中，localPort包括两个值，其中流表条目信息X标识绑定Z端口为入向端口，组表信息Q标识绑定Z端口为出向端口，携带的上述其他OAM配置信息与第一OAM配置报文相同。
步骤二、NE1的Openflow协议处理组件接收到Openflow报文，解析协议头中的type成员，根据type值为240，判断是OAM配置报文，转发至OAM组件；NE2的Openflow协议处理组件接收到Openflow报文，解析协议头中的type成员，根据type值为240，判断是OAM配置报文，转发至OAM组件；
步骤三、NE1的OAM组件解析OAM配置报文，根据成员action取值为1判断操作类型为新增；根据成员localPort取值为X和Y，判断与OAM实例绑定的入向端口和出向端口均为A端口；根据data报文解析，判断OAM报文发送周期为10毫秒。创建OAM标识为1的OAM实例(可视为OAM组件的一部分)，构造所需的OAM报文，启动10毫秒定时器，周期性从A端口发送OAM报文，并从A端口探测接收同样类型的OAM报文(报文收 发通过转发组件实现)。NE2的OAM组件解析OAM配置报文，根据成员action取值为1判断操作类型为新增；根据成员localPort取值为P和Q，判断与OAM实例绑定的入向端口和出向端口均为Z端口；根据data报文解析，判断OAM报文发送周期为10毫秒。创建OAM标识为1的OAM实例，构造所需的OAM报文，启动10毫秒定时器，周期性从Z端口发送OAM报文，并从Z端口探测接收同样类型的OAM报文。
应用示例二
本示例以Controller发起修改双向路径A-Z(Forwarder NE1的A端口到Forwarder NE2的Z端口)的OAM发送周期，从10毫秒修改为3.33毫秒为例说明本示例的实施方案。
实施方案包括如下步骤：
步骤一、Controller发起修改双向路径A-Z快速OAM的配置，构造第一OAM配置报文，其中的消息成员id取值为1；设置消息成员action为2，标识操作类型为修改；消息成员localPort包括2个值，其中流表条目信息X标识绑定A端口为入向端口，组表信息Y标识绑定A端口为出向端口；data报文携带报文周期为3.33毫秒，还可携带其他所需信息，通过Openflow通道将第一OAM配置报文下发至NE1。同时，构造第二OAM配置报文，消息成员localPort包括两个值，其中流表条目信息P标识绑定Z端口为入向端口，组表信息Q标识绑定Z端口为出向端口；上述其他OAM配置信息与第一OAM配置报文相同，通过Openflow通道将第二OAM配置报文下发至NE2。
步骤二、NE1的Openflow协议处理组件接收到Openflow报文，解析协议头中的type成员，根据type值为240，判断是OAM配置报文，转发至OAM组件；NE2的Openflow协议处理组件接收到Openflow报文，解析协议头中的type成员，根据type值为240，判断是OAM配置报文，转发至OAM组件；
步骤三、NE1的OAM组件解析OAM消息结构，根据成员action取值为2判断操作类型为修改OAM；根据成员localPort取值为X和Y，判断与OAM 实例绑定的入向端口和出向端口均为A端口；根据data报文解析，判断OAM报文发送周期为3.33毫秒；根据OAM标识1找到当前已经生效的OAM实例，修改OAM报文的发送周期，停止10毫秒定时器，启动3.33毫秒定时器周期性，按新的发送周期从A端口周期性发送OAM报文，并从A端口探测接收同样类型的OAM报文。NE2的OAM组件解析OAM消息结构，根据成员action取值为2判断操作类型为修改OAM；根据成员localPort取值为P和Q，判断与OAM实例绑定的入向端口和出向端口均为Z端口；根据data报文解析，判断OAM报文发送周期为3.33毫秒；根据OAM标识1找到当前已经生效的10毫秒实例，修改OAM报文的发送周期，停止10毫秒定时器，启动3.33毫秒定时器，按照新的发送周期周期性从Z端口发送OAM报文，并从Z端口探测接收同样类型的OAM包。
应用示例三
本示例Controller发起暂停双向路径A-Z(Forwarder NE1的A端口到Forwarder NE2的Z端口)的OAM为例说明本示例的实施方案。
实施方案包括如下步骤：
步骤一、Controller发起暂停双向路径A-Z快速OAM，构造第一OAM配置报文，第一OAM配置报文中，消息成员action为3，标识操作类型为暂停，其他消息成员的取值及OAM报文发送周期的取值与示例二的第一OAM配置报文相同；通过Openflow通道将所述第一OAM配置报文下发至NE1。同时构造第二OAM配置报文，其消息成员action为3，标识操作类型为暂停，其他消息成员的取值及OAM报文发送周期的取值与示例二的第二OAM配置报文相同，通过Openflow通道将第二OAM配置报文下发至NE2。
步骤二、NE1的Openflow协议处理组件接收到Openflow报文，解析协议头中的type成员，根据type值为240，判断是OAM配置报文，转发至OAM组件；NE2的Openflow协议处理组件接收到Openflow报文，解析协议头中的type成员，根据type值为240，判断是OAM配置报文，转发至OAM组件；
步骤三、NE1的OAM组件解析OAM消息结构，根据成员action取值为3判断操作类型为暂停OAM；根据成员localPort取值为X和Y，判断与OAM实例绑定的入向端口和出向端口均为A端口；根据data报文解析，判断OAM报文发送周期为3.33毫秒；根据OAM标识1找到当前已经生效的OAM实例，停止3.33毫秒定时器，停止从A端口发送和接收OAM报文。NE2的OAM组件解析OAM消息结构，根据成员action取值为3判断操作类型为暂停OAM；根据成员localPort取值为P和Q，判断与OAM实例绑定的入向端口和出向端口均为Z端口；根据data报文解析，判断OAM报文发送周期为3.33毫秒；根据OAM标识1找到当前已经生效的OAM实例，停止3.33毫秒定时器，停止从Z端口发送和接收OAM报文。
应用示例四
本示例以Controller发起启动已经暂停的双向路径A-Z(Forwarder NE1的A端口到Forwarder NE2的Z端口)的OAM为例说明本示例的实施方案。
实施方案包括如下步骤：
步骤一、Controller发起启动已经暂停的双向路径A-Z快速OAM，构造第一OAM配置报文，第一OAM配置报文中，消息成员action为4，标识操作类型为重启，其他消息成员的取值及OAM报文发送周期的取值与示例二的第一OAM配置报文相同；通过Openflow通道将所述第一OAM配置报文下发至NE1。同时构造第二OAM配置报文，其消息成员action为4，标识操作类型为重启，其他消息成员的取值及OAM报文发送周期的取值与示例二的第二OAM配置报文相同，通过Openflow通道将第二OAM配置报文下发至NE2。
步骤二、NE1的Openflow协议处理组件接收到Openflow报文，解析协议头中的type成员，根据type值为240，判断是OAM配置报文，转发至OAM组件；NE2的Openflow协议处理组件接收到Openflow报文，解析协议头中的type成员，根据type值为240，判断是OAM配置报文，转发至OAM组件；
步骤三、NE1的OAM组件解析OAM消息结构，根据成员action取值为4判断操作类型为重启OAM；根据成员localPort取值为X和Y，判断与OAM实例绑定的入向端口和出向端口均为A端口；根据data报文解析，判断OAM报文发送周期为3.33毫秒；根据OAM标识1找到当前已经生效的OAM实例，重启3.33毫秒定时器，开始从A端口发送和接收OAM报文。NE2的OAM组件解析OAM消息结构，根据成员action取值为4判断操作类型为重启OAM；根据成员localPort取值为P和Q，判断与OAM实例绑定的入向端口和出向端口均为Z端口；根据data报文解析，判断OAM报文发送周期为3.33毫秒；根据OAM标识1找到当前已经生效的OAM实例，重启3.33毫秒定时器，开始从Z端口发送和接收OAM报文。
应用示例五
本示例以Controller发起删除双向路径A-Z(Forwarder NE1的A端口到Forwarder NE2的Z端口)的OAM为例说明本示例的实施方案。
实施方案包括如下步骤：
步骤一、CMC发起删除双向路径A-Z的快速OAM，构造第一OAM配置报文，第一OAM配置报文中，消息成员action为5，标识操作类型为删除，其他消息成员的取值及OAM报文发送周期的取值与示例二的第一OAM配置报文相同；通过Openflow通道将所述第一OAM配置报文下发至NE1。同时构造第二OAM配置报文，其消息成员action为5，标识操作类型为删除，其他消息成员的取值及OAM报文发送周期的取值与示例二的第二OAM配置报文相同，通过Openflow通道将第二OAM配置报文下发至NE2。
步骤二、NE1的Openflow协议处理组件接收到Openflow报文，解析协议头中的type成员，根据type值为240，判断是OAM配置报文，转发至OAM组件；NE2的Openflow协议处理组件接收到Openflow报文，解析协议头中的type成员，根据type值为240，判断是OAM配置报文，转发至OAM组件；
步骤三、NE1的OAM组件解析OAM消息结构；根据成员action取值为 5判断操作类型为删除OAM；根据成员localPort取值判断绑定的本地端口为A端口；根据data报文解析，判断OAM发送周期为3.33毫秒；根据OAM标识找到当前已经生效的OAM实例，删除此OAM实例(同时删除3.33毫秒定时器)，取消A端口上OAM报文的收发。NE2的OAM组件解析OAM消息结构；根据成员action取值为5判断操作类型为删除OAM；根据成员localPort取值判断绑定的本地端口为Z端口；根据data报文解析，判断OAM发送周期为3.33毫秒；根据OAM标识找到当前已经生效的OAM实例，删除此OAM实例(同时删除3.33毫秒定时器)，取消Z端口上OAM报文的收发。
步骤三、NE1的OAM组件解析OAM消息结构，根据成员action取值为5判断操作类型为删除OAM；根据成员localPort取值为X和Y，判断与OAM实例绑定的入向端口和出向端口均为A端口；根据data报文解析，判断OAM报文发送周期为3.33毫秒；根据OAM标识1找到当前已经生效的OAM实例，删除此OAM实例(同时删除3.33毫秒定时器)，即取消A端口上OAM报文的收发。NE2的OAM组件解析OAM消息结构，根据成员action取值为5判断操作类型为删除OAM；根据成员localPort取值为P和Q，判断与OAM实例绑定的入向端口和出向端口均为Z端口；根据data报文解析，判断OAM报文发送周期为3.33毫秒；根据OAM标识1找到当前已经生效的OAM实例，删除此OAM实例(同时删除3.33毫秒定时器)，即取消Z端口上OAM报文的收发。
在一些场景下，Controller发起新增、修改、暂停、启动或删除双向路径A-Z(Forwarder NE1的A端口到Forwarder NE2的Z端口)的OAM，但只有NE1或NE2归属CMC控制，请参照图9。如此CMC只需要和NE1或NE2交互即可。上述示例中，每个实施步骤只考虑针对NE1或NE2的单独设置即为此种场景下的每个示例。
下面结合图8、图10和图11，以Controller发起新增、修改、暂停、重启和删除单向路径A-Z(Forwarder NE1的A端口到Forwarder NE2的Z端口) 的OAM功能为例说明本文的实施方案。
应用示例六，
本示例以Controller发起新增单向路径A-Z(Forwarder NE1的A端口到Forwarder NE2的Z端口)发送周期10毫秒的快速OAM功能为例。
实施方案包括如下步骤：
步骤一、CMC发起新增单向路径A-Z的快速OAM的配置，构造第一OAM配置报文，其中的消息成员id取值为1；设置消息成员action为1，标识操作类型为新增；消息成员localPort用组表信息Y标识绑定A端口为出向端口；data报文携带报文周期为10毫秒，还可携带其他所需信息，通过Openflow通道将第一OAM配置报文下发至NE1。同时，构造第二OAM配置报文，消息成员localPort用流表条目信息P标识绑定Z端口为入向端口，上述其他OAM配置信息与第一OAM配置报文相同，通过Openflow通道将第二OAM配置报文下发至NE2。
步骤二、NE1的Openflow协议处理组件接收到Openflow报文，解析协议头中的type成员，根据type值为240，判断是OAM配置报文，转发至OAM组件；NE2的Openflow协议处理组件接收到Openflow报文，解析协议头中的type成员，根据type值为240，判断是OAM配置报文，转发至OAM组件；
步骤三、NE1的OAM组件解析OAM配置报文，根据成员action取值为1判断操作类型为新增；根据成员localPort取值为Y，判断与OAM实例绑定的出向端口均为A端口；根据data报文解析，判断OAM报文发送周期为10毫秒。创建OAM标识为1的OAM实例，构造所需的OAM报文并启动10毫秒定时器，周期性从A端口发送OAM报文。NE2的OAM组件解析OAM配置报文，根据成员action取值为1判断操作类型为新增；根据成员localPort取值为P，判断与OAM实例绑定的入向端口为Z端口；根据data报文解析，判断OAM报文发送周期为10毫秒。创建OAM标识为1的OAM实例，在Z端口探测接收此类型的OAM报文。
应用示例七
本示例以Controller发起修改单向路径A-Z(Forwarder NE1的A端口到Forwarder NE2的Z端口)的OAM发送周期，从10毫秒修改为3.33毫秒为例。
实施方案包括如下步骤：
步骤一、CMC发起修改单向路径A-Z的快速OAM，构造第一OAM配置报文，其中的消息成员id取值为1；设置消息成员action为2，标识操作类型为修改；消息成员localPort用组表信息Y标识绑定A端口为出向端口；data报文携带报文周期为3.33毫秒，还可携带其他所需信息，通过Openflow通道将第一OAM配置报文下发至NE1。同时，构造第二OAM配置报文，消息成员localPort用流表条目信息P标识绑定Z端口为入向端口，上述其他OAM配置信息与第一OAM配置报文相同，通过Openflow通道将第二OAM配置报文下发至NE2；
步骤二、NE1的Openflow协议处理组件接收到Openflow报文，解析协议头中的type成员，根据type值为240，判断是OAM配置报文，转发至OAM组件；NE2的Openflow协议处理组件接收到Openflow报文，解析协议头中的type成员，根据type值为240，判断是OAM配置报文，转发至OAM组件；
步骤三、NE1的OAM组件解析OAM配置报文，根据成员action取值为2判断操作类型为修改；根据成员localPort取值为Y，判断与OAM实例绑定的出向端口均为A端口；根据data报文解析，判断OAM报文发送周期为3.33毫秒。根据OAM标识1找到已经生效的OAM实例，取消10毫秒定时器，启动3.33毫秒定时器，周期性从A端口发送OAM报文。E2的OAM组件解析OAM配置报文，根据成员action取值为2判断操作类型为修改；根据成员localPort取值为P，判断与OAM实例绑定的入向端口为Z端口；根据data报文解析，判断OAM报文发送周期为3.33毫秒。根据OAM标识1找到已经生效的OAM实例，从Z端口探测接收发送周期为3.33毫秒的OAM报文。
应用示例八
本示例以Controller发起暂停单向路径A-Z(Forwarder NE1的A端口到Forwarder NE2的Z端口)的OAM为例。
实施方案包括如下步骤：
步骤一、CMC发起暂停单向路径A-Z的快速OAM，构造第一OAM配置报文，其中的消息成员id取值为1；设置消息成员action为3，标识操作类型为暂停；消息成员localPort用组表信息Y标识绑定A端口为出向端口；data报文携带报文周期为3.33毫秒，还可携带其他所需信息，通过Openflow通道将第一OAM配置报文下发至NE1。同时，构造第二OAM配置报文，消息成员localPort用流表条目信息P标识绑定Z端口为入向端口，上述其他OAM配置信息与第一OAM配置报文相同，通过Openflow通道将第二OAM配置报文下发至NE2；
步骤二、NE1的Openflow协议处理组件接收到Openflow报文，解析协议头中的type成员，根据type值为240，判断是OAM配置报文，转发至OAM组件；NE2的Openflow协议处理组件接收到Openflow报文，解析协议头中的type成员，根据type值为240，判断是OAM配置报文，转发至OAM组件；
步骤三、NE1的OAM组件解析OAM配置报文，根据成员action取值为3判断操作类型为暂停；根据成员localPort取值为Y，判断与OAM实例绑定的出向端口均为A端口；根据data报文解析，判断OAM报文发送周期为3.33毫秒。根据OAM标识1找到已经生效的OAM实例，暂停3.33毫秒定时器，暂停从A端口发送OAM报文。E2的OAM组件解析OAM配置报文，根据成员action取值为3判断操作类型为暂停；根据成员localPort取值为P，判断与OAM实例绑定的入向端口为Z端口；根据data报文解析，判断OAM报文发送周期为3.33毫秒。根据OAM标识1找到已经生效的OAM实例，暂停从Z端口探测接收发送周期为3.33毫秒的OAM报文。
应用示例九
本示例以Controller发起启动已经暂停的单向路径A-Z(Forwarder NE1的A端口到Forwarder NE2的Z端口)的OAM为例。
实施方案包括如下步骤：
步骤一、CMC发起重启单向路径A-Z的快速OAM，构造第一OAM配置报文，其中的消息成员id取值为1；设置消息成员action为4，标识操作类型为重启；消息成员localPort用组表信息Y标识绑定A端口为出向端口；data报文携带报文周期为3.33毫秒，还可携带其他所需信息，通过Openflow通道将第一OAM配置报文下发至NE1。同时，构造第二OAM配置报文，消息成员localPort用流表条目信息P标识绑定Z端口为入向端口，上述其他OAM配置信息与第一OAM配置报文相同，通过Openflow通道将第二OAM配置报文下发至NE2；
步骤二、NE1的Openflow协议处理组件接收到Openflow报文，解析协议头中的type成员，根据type值为240，判断是OAM配置报文，转发至OAM组件；NE2的Openflow协议处理组件接收到Openflow报文，解析协议头中的type成员，根据type值为240，判断是OAM配置报文，转发至OAM组件；
步骤三、NE1的OAM组件解析OAM配置报文，根据成员action取值为4判断操作类型为重启；根据成员localPort取值为Y，判断与OAM实例绑定的出向端口均为A端口；根据data报文解析，判断OAM报文发送周期为3.33毫秒。根据OAM标识1找到已经生效的OAM实例，重启3.33毫秒定时器，开始从A端口发送OAM报文。E2的OAM组件解析OAM配置报文，根据成员action取值为4判断操作类型为重启；根据成员localPort取值为P，判断与OAM实例绑定的入向端口为Z端口；根据data报文解析，判断OAM报文发送周期为3.33毫秒。根据OAM标识1找到已经生效的OAM实例，重新开始从Z端口探测接收发送周期为3.33毫秒的OAM报文。
应用示例十
本示例以Controller发起删除单向路径A-Z(Forwarder NE1的A端口到 Forwarder NE2的Z端口)的OAM为例。
实施方案包括如下步骤：
步骤一、CMC发起重启单向路径A-Z的快速OAM，构造第一OAM配置报文，其中的消息成员id取值为1；设置消息成员action为5，标识操作类型为删除；消息成员localPort用组表信息Y标识绑定A端口为出向端口；data报文携带报文周期为3.33毫秒，还可携带其他所需信息，通过Openflow通道将第一OAM配置报文下发至NE1。同时，构造第二OAM配置报文，消息成员localPort用流表条目信息P标识绑定Z端口为入向端口，上述其他OAM配置信息与第一OAM配置报文相同，通过Openflow通道将第二OAM配置报文下发至NE2；
步骤二、NE1的Openflow协议处理组件接收到Openflow报文，解析协议头中的type成员，根据type值为240，判断是OAM配置报文，转发至OAM组件；NE2的Openflow协议处理组件接收到Openflow报文，解析协议头中的type成员，根据type值为240，判断是OAM配置报文，转发至OAM组件；
步骤三、NE1的OAM组件解析OAM配置报文，根据成员action取值为5判断操作类型为删除；根据成员localPort取值为Y，判断与OAM实例绑定的出向端口均为A端口；根据data报文解析，判断OAM报文发送周期为3.33毫秒。根据OAM标识1找到已经生效的OAM实例，删除此OAM实例(同时删除3.33毫秒定时器)，即取消从A端口发送OAM报文。E2的OAM组件解析OAM配置报文，根据成员action取值为5判断操作类型为删除；根据成员localPort取值为P，判断与OAM实例绑定的入向端口为Z端口；根据data报文解析，判断OAM报文发送周期为3.33毫秒。根据OAM标识1找到已经生效的OAM实例，删除此OAM实例(同时删除3.33毫秒定时器)，即取消在Z端口探测接收发送周期为3.33毫秒的OAM报文。
在另一些场景下，Controller发起新增、修改、暂停、启动或删除单向路径A-Z(Forwarder NE1的A端口到Forwarder NE2的Z端口)的OAM，但只有NE1归属CMC控制，如图10所示。如此Controller只需要和NE1交互 即可。上述实施例中，每个实施步骤只考虑针对NE1的设置即为此种场景下的实施例。
在另一些场景下，Controller发起新增、修改、暂停、启动或删除单向路径A-Z(Forwarder NE1的A端口到Forwarder NE2的Z端口)的OAM，但只有NE2归属CMC控制，如图11所示。如此Controller只需要和NE2交互即可。上述实施例中，每个实施步骤只考虑针对NE2的设置即为此种场景下的实施例。
需要说明的是，对于OTN等非分组的传输技术，其OAM固有存在，则不需要OAM的增加、删除和修改等操作，只需要启动或暂停，确定是否启用OAM监视功能，启动即标识启用OAM监视功能，暂停即表示禁用OAM监视功能。
上述方案以已有SDN(不限于SDN)的Controller和Forwarder之间规范接口为基础，扩展消息类型，完成针对基于分组传送技术的以太网、IP、MPLS、MPLS-TP、PBB等网络，非分组传送技术的OTN、WDM等网络，针对双向或单向路径快速OAM的新增、修改、暂停、启动、删除等功能，具备简洁、可靠的优点。
本领域普通技术人员可以理解上述实施例的全部或部分步骤可以使用计算机程序流程来实现，所述计算机程序可以存储于一计算机可读存储介质中，所述计算机程序在相应的硬件平台上(如系统、设备、装置、器件等)执行，在执行时，包括方法实施例的步骤之一或其组合。
可选地，上述实施例的全部或部分步骤也可以使用集成电路来实现，这些步骤可以被分别制作成一个个集成电路模块，或者将它们中的多个模块或步骤制作成单个集成电路模块来实现。
上述实施例中的装置/功能模块/功能单元可以采用通用的计算装置来实现，它们可以集中在单个的计算装置上，也可以分布在多个计算装置所组成 的网络上。
上述实施例中的装置/功能模块/功能单元以软件功能模块的形式实现并作为独立的产品销售或使用时，可以存储在一个计算机可读取存储介质中。上述提到的计算机可读取存储介质可以是只读存储器，磁盘或光盘等。
工业实用性
本发明实施例通过OAM配置报文，在转发路径首、尾端点Forwarder进行OAM配置，从而可以按照标准的要求实现OAM报文在Forwarder设备层面的收发。而通过扩展Openflow协议头的消息类型，新定义OAM消息完成OAM功能的新增、修改、暂停、启动或删除等配置功能，具备简洁、可靠的优点。

Claims (33)

  1. 一种操作维护管理功能的配置方法，包括：
    控制器发起转发路径操作维护管理OAM功能的配置，构造OAM配置报文，所述OAM配置报文中携带OAM配置信息；
    所述控制器将所述OAM配置报文通过Openflow通道发送至所述转发路径的首端点转发设备和/或尾端点转发设备。
  2. 如权利要求1所述的配置方法，其中：
    所述OAM配置报文中Openflow协议头携带的消息类型，是对Openflow协议定义的消息类型扩展得到的新的消息类型。
  3. 如权利要求1或2所述的配置方法，其中：
    所述OAM配置信息包括以下全部或部分信息：
    OAM标识，表示所配置的OAM实例的标识；
    操作类型，表示要实施的操作的类型；
    本地端口，表示转发设备上OAM实例绑定的端口；
    报文发送周期，表示转发设备发送OAM报文的周期。
  4. 如权利要求3所述的配置方法，其中：
    所述本地端口为物理端口或逻辑端口，包括：
    入向端口，表示接收OAM报文的端口；和/或
    出向端口，表示发送OAM报文的端口。
  5. 如权利要求4所述的配置方法，其中：
    所述转发路径为双向转发路径，所述控制器构造OAM配置报文，包括：
    构造要发送到所述双向转发路径首端点转发设备的第一OAM配置报文，其中携带所述首端点转发设备上的本地端口信息，包括用流表条目信息表示的入向端口信息和用组表信息表示的出向端口信息；
    构造要发送到所述双向转发路径尾端点转发设备的第二OAM配置报 文，其中携带所述尾端点转发设备上的本地端口信息，包括用流表条目信息表示的入向端口信息和用组表信息表示的出向端口信息。
  6. 如权利要求4所述的配置方法，其中：
    所述转发路径为单向转发路径，所述控制器构造OAM配置报文，包括：
    构造要发送到所述单向转发路径首端点转发设备的第一OAM配置报文，其中携带所述首端点转发设备上的本地端口信息，包括用组表信息表示的出向端口信息；
    构造要发送到所述单向转发路径尾端点转发设备的第二OAM配置报文，其中携带所述尾端点转发设备上的本地端口信息，包括用流表条目信息表示的入向端口信息。
  7. 如权利要求3所述的配置方法，其中：
    所述操作类型为新增、修改、启动、暂停和删除中的一种。
  8. 如权利要求1或2或4或5或6或7所述的配置方法，其中：
    所述转发路径所在的网络协议层为以下网络协议层中的一种：
    以太网的物理层、VLAN层、IP层和业务层；
    多协议标签交换MPLS网络或多协议标签交换-传送架构MPLS-TP网络的隧道层、伪线层和业务层；
    光传送网络OTN的物理层、段层和ODUk层；
    波分复用WDM网络的物理层、光传输段层、光复用段层、光通道层和再生段层。
  9. 一种操作维护管理OAM功能的实现方法，包括：
    转发路径一端的转发设备通过Openflow通道接收Openflow报文并解析其中的Openflow协议头；
    所述转发设备根据解析结果，如确定所述Openflow报文为OAM配置报文，则对所述OAM配置报文进行解析，获取其中的OAM配置信息并实施相应的处理。
  10. 如权利要求9所述的实现方法，其中：
    所述转发设备解析所述Openflow协议头，确定所述Openflow报文为OAM配置报文，包括：
    所述转发设备解析所述Openflow协议头，如判断其中携带的消息类型为OAM配置报文的消息类型，则确定所述Openflow报文为OAM配置报文；其中，所述OAM配置报文的消息类型是对Openflow协议定义的消息类型扩展得到的新的消息类型。
  11. 如权利要求9所述的实现方法，其中：
    所述转发设备获取的所述OAM配置信息包括以下全部或部分信息：
    OAM标识，表示所配置的OAM实例的标识；
    操作类型，表示要实施的操作的类型；
    本地端口，表示转发设备上OAM实例绑定的端口；
    报文发送周期，表示转发设备发送OAM报文的周期。
  12. 如权利要求11所述的实现方法，其中：
    所述转发设备获取的所述OAM配置信息包括本地端口的信息，所述本地端口为物理端口或逻辑端口，包括：
    入向端口，表示接收OAM报文的端口；和/或
    出向端口，表示发送OAM报文的端口。
  13. 如权利要求12所述的实现方法，其中：
    所述转发路径为双向转发路径；
    所述转发设备获取的所述本地端口信息包括用流表条目信息表示的入向端口信息和用组表信息表示的出向端口信息；
    所述转发设备实施相应的处理，包括：根据所述流表条目信息匹配查找到本地的入向端口，及根据所述组表信息匹配查找到本地的出向端口。
  14. 如权利要求12所述的实现方法，其中：
    所述转发路径为单向转发路径；
    所述转发设备获取的本地端口信息包括用流表条目信息表示的入向端口信息或用组表信息表示的出向端口信息；
    所述转发设备实施相应的处理，包括：根据所述流表条目信息匹配查找到本地的入向端口，或根据所述组表信息匹配查找到本地的出向端口。
  15. 如权利要求12或13或14所述的实现方法，其中：
    所述转发设备获取的操作类型为新增；所述转发设备实施相应的处理，包括：创建具有所述OAM标识的OAM实例并与指定的入向端口和/或出向端口绑定，在所述入向端口接收OAM报文，和/或在所述出向端口按照所述报文发送周期发送OAM报文；或者
    所述转发设备获取的操作类型为修改；所述转发设备实施相应的处理，包括：根据所述OAM标识找到要配置的OAM实例，根据接收的OAM配置信息更新所述OAM实例的配置，按照新的配置发送和/或接收OAM报文；或者
    所述转发设备获取的操作类型为删除；所述转发设备实施相应的处理，包括：根据所述OAM标识找到要配置的OAM实例，将所述OAM实例删除；或者
    所述转发设备获取的操作类型为暂停；所述转发设备实施相应的处理，包括：根据所述OAM标识找到要配置的OAM实例，停止OAM报文的发送和/或接收；或者
    所述转发设备获取的操作类型为重启；所述转发设备实施相应的处理，包括：根据所述OAM标识找到要配置的OAM实例，重启OAM报文的发送和/或接收。
  16. 如权利要求9至14中任一所述的实现方法，其中：
    所述转发路径所在的网络协议层为以下网络协议层中的一种：
    以太网的物理层、VLAN层、IP层和业务层；
    多协议标签交换MPLS网络或多协议标签交换-传送架构MPLS-TP网络的隧道层、伪线层和业务层；
    光传送网络OTN的物理层、段层和ODUk层；
    波分复用WDM网络的物理层、光传输段层、光复用段层、光通道层和再生段层。
  17. 一种可配置转发路径操作维护管理OAM功能的控制器，包括：
    报文构造模块，设置为：在发起转发路径OAM功能的配置时，构造OAM配置报文，所述OAM配置报文中携带OAM配置信息；
    报文发送模块，设置为：将所述OAM配置报文通过Openflow通道发送至所述转发路径的首端点转发设备和/或尾端点转发设备。
  18. 如权利要求17所述的控制器，其中：
    所述报文构造模块构造的所述OAM配置报文中，Openflow协议头携带的消息类型是对Openflow协议定义的消息类型扩展得到的新的消息类型。
  19. 如权利要求17或18所述的控制器，其中：
    所述报文构造模块构造的所述OAM配置报文中，携带的OAM配置信息包括以下全部或部分信息：
    OAM标识，表示所配置的OAM实例的标识；
    操作类型，表示要实施的操作的类型；
    本地端口，表示转发设备上OAM实例绑定的端口；
    报文发送周期，表示转发设备发送OAM报文的周期。
  20. 如权利要求19所述的控制器，其中：
    所述报文构造模块构造的所述OAM配置报文中，携带的所述本地端口为物理端口或逻辑端口，包括：
    入向端口，表示接收OAM报文的端口；和/或
    出向端口，表示发送OAM报文的端口。
  21. 如权利要求20所述的控制器，其中：
    所述转发路径为双向转发路径；
    所述报文构造模块是设置为：
    构造要发送到所述双向转发路径首端点转发设备的第一OAM配置报 文，其中携带所述首端点转发设备上的本地端口信息，包括用流表条目信息表示的入向端口信息和用组表信息表示的出向端口信息；
    构造要发送到所述双向转发路径尾端点转发设备的第二OAM配置报文，其中携带所述尾端点转发设备上的本地端口信息，包括用流表条目信息表示的入向端口信息和用组表信息表示的出向端口信息。
  22. 如权利要求20所述的控制器，其中：
    所述转发路径为单向转发路径；
    所述报文构造模块是设置为：
    构造要发送到所述单向转发路径首端点转发设备的第一OAM配置报文，其中携带所述首端点转发设备上的本地端口信息，包括用组表信息表示的出向端口信息；
    构造要发送到所述单向转发路径尾端点转发设备的第二OAM配置报文，其中携带所述尾端点转发设备上的本地端口信息，包括用流表条目信息表示的入向端口信息。
  23. 如权利要求19所述的控制器，其中：
    所述报文构造模块构造的所述OAM配置报文中，携带的OAM配置信息中的操作类型为新增、修改、启动、暂停和删除中的一种。
  24. 如权利要求17或18或20或21或22所述的控制器，其中：
    报文构造模块在发起转发路径OAM功能的配置时构造OAM配置报文，其中，所述转发路径所在的网络协议层为以下网络协议层中的一种：
    以太网的物理层、VLAN层、IP层和业务层；
    多协议标签交换MPLS网络或多协议标签交换-传送架构MPLS-TP网络的隧道层、伪线层和业务层；
    光传送网络OTN的物理层、段层和ODUk层；
    波分复用WDM网络的物理层、光传输段层、光复用段层、光通道层和再生段层。
  25. 一种可实现转发路径操作维护管理OAM功能的转发设备，包括：
    Openflow协议处理组件，设置为：通过Openflow通道接收控制器发送的Openflow报文并解析其中的Openflow协议头，如确定所述Openflow报文为OAM配置报文，转发到OAM组件处理；
    OAM组件，设置为：对所述OAM配置报文进行解析，获取其中的OAM配置信息并实施相应的处理。
  26. 如权利要求25所述的转发设备，其中：
    所述Openflow协议处理组件是设置为：解析所述Openflow协议头，如判断其中携带的消息类型为OAM配置报文的消息类型，则确定所述Openflow报文为OAM配置报文；其中，所述OAM配置报文的消息类型是对Openflow协议定义的消息类型扩展得到的新的消息类型。
  27. 如权利要求25所述的转发设备，其中：
    所述OAM组件获取的OAM配置信息包括以下全部或部分信息：
    OAM标识，表示所配置的OAM实例的标识；
    操作类型，表示要实施的操作的类型；
    本地端口，表示转发设备上OAM实例绑定的端口；
    报文发送周期，表示转发设备发送OAM报文的周期。
  28. 如权利要求27所述的转发设备，其中：
    所述OAM组件获取的OAM配置信息包括本地端口的信息，其中，所述本地端口为物理端口或逻辑端口，包括：
    入向端口，表示接收OAM报文的端口；和/或
    出向端口，表示发送OAM报文的端口。
  29. 如权利要求28所述的转发设备，其中：
    所述OAM组件获取的OAM配置信息中，本地端口的信息包括用流表条目信息表示的入向端口信息和用组表信息表示的出向端口信息；
    所述OAM组件是设置为：根据所述流表条目信息匹配查找到本地的入向端口，及根据所述组表信息匹配查找到本地的出向端口。
  30. 如权利要求28所述的转发设备，其中：
    所述OAM组件获取的OAM配置信息中，本地端口的信息包括用流表条目信息表示的入向端口信息，或用组表信息表示的出向端口信息；
    所述OAM组件是设置为：根据所述流表条目信息匹配查找到本地的入向端口，或根据所述组表信息匹配查找到本地的出向端口。
  31. 如权利要求28或29或30中任一所述的转发设备，其中：
    所述OAM组件获取的操作类型为新增；所述OAM组件是设置为：创建具有所述OAM标识的OAM实例并与指定的入向端口和/或出向端口绑定，在所述入向端口接收OAM报文，和/或在所述出向端口按照所述报文发送周期发送OAM报文；或者
    所述OAM组件获取的操作类型为修改；所述OAM组件是设置为：根据所述OAM标识找到要配置的OAM实例，根据此次接收的OAM配置信息更新所述OAM实例的相应配置，按照新的配置发送和/或接收OAM报文；或者
    所述OAM组件获取的操作类型为删除；所述OAM组件是设置为：根据所述OAM标识找到要配置的OAM实例，将所述OAM实例删除；或者
    所述OAM组件获取的操作类型为暂停；所述OAM组件是设置为：根据所述OAM标识找到要配置的OAM实例，停止OAM报文的发送和/或接收；或者
    所述OAM组件获取的操作类型为重启；所述OAM组件是设置为：根据所述OAM标识找到要配置的OAM实例，重启OAM报文的发送和/或接收。
  32. 如权利要求25至30中任一所述的转发设备，其中：
    所述转发设备关联的所述转发路径所在的网络协议层为以下网络协议层中的一种：
    以太网的物理层、VLAN层、IP层和业务层；
    多协议标签交换MPLS网络或多协议标签交换-传送架构MPLS-TP网络的隧道层、伪线层和业务层；
    光传送网络OTN的物理层、段层和ODUk层；
    波分复用WDM网络的物理层、光传输段层、光复用段层、光通道层和再生段层。
  33. 一种计算机可读存储介质，存储有计算机可执行指令，所述计算机可执行指令用于执行权利要求1-16任一项的方法。
PCT/CN2015/083093 2014-12-23 2015-07-01 一种操作维护管理功能的配置、实现方法及转发设备 WO2016101582A1 (zh)

Priority Applications (2)

Application Number Priority Date Filing Date Title
EP15871657.1A EP3223455A4 (en) 2014-12-23 2015-07-01 Method for configuring and implementing operations, administration and maintenance function, and forwarding device
RU2017121483A RU2678713C2 (ru) 2014-12-23 2015-07-01 Способ конфигурирования и реализации функции эксплуатации, администрирования и обслуживания, а также устройство пересылки

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201410812061.8 2014-12-23
CN201410812061.8A CN105790984B (zh) 2014-12-23 2014-12-23 一种操作维护管理功能的配置、实现方法及转发设备

Publications (1)

Publication Number Publication Date
WO2016101582A1 true WO2016101582A1 (zh) 2016-06-30

Family

ID=56149137

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2015/083093 WO2016101582A1 (zh) 2014-12-23 2015-07-01 一种操作维护管理功能的配置、实现方法及转发设备

Country Status (4)

Country Link
EP (1) EP3223455A4 (zh)
CN (1) CN105790984B (zh)
RU (1) RU2678713C2 (zh)
WO (1) WO2016101582A1 (zh)

Families Citing this family (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US10498639B2 (en) * 2018-03-13 2019-12-03 Futurewei Technologies, Inc. Collecting network OAM flow data using out-of-band messages
CN108881064B (zh) * 2018-06-26 2022-07-22 新华三技术有限公司 报文信息获取方法和发送方法
CN112087338B (zh) * 2020-09-14 2022-09-27 武汉虹信科技发展有限责任公司 一种控制消息传输方法及系统

Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101997711A (zh) * 2009-08-17 2011-03-30 中兴通讯股份有限公司 实现操作管理维护消息发送的方法及分组数据网系统
CN102332987A (zh) * 2010-07-12 2012-01-25 中兴通讯股份有限公司 一种伪线oam属性配置的方法和系统
US20130010600A1 (en) * 2011-07-08 2013-01-10 Telefonaktiebolaget L M Ericsson (Publ) Controller Driven OAM for OpenFlow
CN104113792A (zh) * 2014-07-30 2014-10-22 上海斐讯数据通信技术有限公司 一种OpenFlow控制通道建立方法及系统
CN104734876A (zh) * 2013-12-24 2015-06-24 中兴通讯股份有限公司 一种实现以太网oam配置的方法及装置

Family Cites Families (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
EP1976185B1 (en) * 2007-03-27 2019-05-01 Nokia Solutions and Networks GmbH & Co. KG Operating network entities in a communication system comprising a management network with agent and management levels
CN101378330A (zh) * 2007-08-27 2009-03-04 华为技术有限公司 对设备实现远程管理的方法、设备及系统
JPWO2012023538A1 (ja) * 2010-08-17 2013-10-28 日本電気株式会社 通信装置、通信システム、通信方法、および記録媒体
JP5919046B2 (ja) * 2012-03-13 2016-05-18 株式会社日立製作所 パス計算方法
EP2800304A1 (en) * 2013-04-30 2014-11-05 Telefonaktiebolaget L M Ericsson (Publ) Technique for configuring a Software-Defined Network

Patent Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101997711A (zh) * 2009-08-17 2011-03-30 中兴通讯股份有限公司 实现操作管理维护消息发送的方法及分组数据网系统
CN102332987A (zh) * 2010-07-12 2012-01-25 中兴通讯股份有限公司 一种伪线oam属性配置的方法和系统
US20130010600A1 (en) * 2011-07-08 2013-01-10 Telefonaktiebolaget L M Ericsson (Publ) Controller Driven OAM for OpenFlow
CN104734876A (zh) * 2013-12-24 2015-06-24 中兴通讯股份有限公司 一种实现以太网oam配置的方法及装置
CN104113792A (zh) * 2014-07-30 2014-10-22 上海斐讯数据通信技术有限公司 一种OpenFlow控制通道建立方法及系统

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
See also references of EP3223455A4 *

Also Published As

Publication number Publication date
RU2017121483A3 (zh) 2019-01-25
CN105790984A (zh) 2016-07-20
CN105790984B (zh) 2020-11-03
RU2678713C2 (ru) 2019-01-31
EP3223455A4 (en) 2017-12-20
RU2017121483A (ru) 2019-01-25
EP3223455A1 (en) 2017-09-27

Similar Documents

Publication Publication Date Title
US10756994B2 (en) Switch, controller, system, and link quality detection method
CN110572293B (zh) 一种数据报文的检测方法、设备及系统
KR102342286B1 (ko) Dcn 메시지 처리 방법, 네트워크 디바이스, 및 네트워크 시스템
US9667537B2 (en) Transport system, packet transport apparatus, and packet transport method
WO2019184752A1 (zh) 网络设备的管理方法、装置及系统
WO2016101546A1 (zh) 操作维护管理功能的实现方法及装置
WO2017036180A1 (zh) 报文的处理方法及装置
US11489836B2 (en) Method, apparatus, and system for collecting access control list
JP2013500612A (ja) 電気通信網における方法及び装置
US8964749B2 (en) Method, device and system for establishing a pseudo wire
US9071457B2 (en) Provider network and provider edge apparatus
US20170012900A1 (en) Systems, methods, and apparatus for verification of a network path
WO2016101582A1 (zh) 一种操作维护管理功能的配置、实现方法及转发设备
US20190305987A1 (en) Forwarding packet
EP3461080A1 (en) Topology determination method, message response method, controller and switch
CN112671644B (zh) 一种基于mpls的sdn业务隔离及选路的方法
US20160094367A1 (en) Migrating multicast flow
CN106161065B (zh) 路径的保护倒换处理方法、装置、系统及转发设备
JPWO2014104277A1 (ja) 制御装置、通信システム、通信ノードの制御方法及びプログラム
WO2012062106A1 (zh) 线性保护组隧道复用方法和隧道尾节点
CN103609066B (zh) 操作、管理、维护配置信息查询的方法及节点
EP3468101B1 (en) Method for controlling network transmission and related apparatus
US9917726B2 (en) Method and apparatus for bundling multiple logger events
WO2023273941A1 (zh) 路径切换方法、控制器、节点以及存储介质
US8396955B2 (en) Systems and methods for discovery of network topology using service OAM

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 15871657

Country of ref document: EP

Kind code of ref document: A1

REEP Request for entry into the european phase

Ref document number: 2015871657

Country of ref document: EP

NENP Non-entry into the national phase

Ref country code: DE

ENP Entry into the national phase

Ref document number: 2017121483

Country of ref document: RU

Kind code of ref document: A