WO2016058245A1 - Processing method and apparatus for operation, administration and maintenance (oam) message - Google Patents

Processing method and apparatus for operation, administration and maintenance (oam) message Download PDF

Info

Publication number
WO2016058245A1
WO2016058245A1 PCT/CN2014/092178 CN2014092178W WO2016058245A1 WO 2016058245 A1 WO2016058245 A1 WO 2016058245A1 CN 2014092178 W CN2014092178 W CN 2014092178W WO 2016058245 A1 WO2016058245 A1 WO 2016058245A1
Authority
WO
WIPO (PCT)
Prior art keywords
packet
oam
sfc
udp
service function
Prior art date
Application number
PCT/CN2014/092178
Other languages
French (fr)
Chinese (zh)
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 中兴通讯股份有限公司
Publication of WO2016058245A1 publication Critical patent/WO2016058245A1/en

Links

Images

Classifications

    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/34Signalling channels for network management communication

Definitions

  • the present invention relates to the field of communications, and in particular to an operation, management, and maintenance (OAM) message processing method and apparatus.
  • OAM operation, management, and maintenance
  • the network edge Since the development of the data center network to the Overlay network, the network edge has become the demarcation point between the virtual network and the physical network, wherein the network edge can be Server or ToR, and possibly Gateway.
  • the network edge can be Server or ToR, and possibly Gateway.
  • Overlay technology does not solve all the problems.
  • Middleware in the data center, such as firewall/load balancer. These devices process data based on user services. If you traverse these devices through tunnels, it is obviously not feasible.
  • This deployment model of the data center requires that the virtual firewall/load balancer can be deployed arbitrarily in the network, that is, independent of the network topology.
  • the new question is how to handle traffic flexibly through a virtual firewall/load balancer? Service processing functions such as these virtual firewalls/load balancers are independent of the original network topology and are implemented by standard servers.
  • the service processing function such as the virtual firewall/load balancer/gateway is called a service function (Service Function, referred to as SF), and the traffic is processed through a series of SFs to form a service function chain (Service Function Chaining). , referred to as SFC).
  • the business function chain is an orderly arrangement of a series of abstract business functions.
  • the SFCs are not defined in the order of which SFFs and/or SFs are ordered when the specific service traffic is forwarded.
  • 1 is an exemplary diagram of an SFC in the related art. As shown in FIG. 1, solid lines and broken lines indicate two SFCs, sometimes called a service chain Service Chain. The following describes the framework of the SFC.
  • the SFC can be divided into the following components:
  • Service Overlay that is, Overlay technology that each service function node needs to communicate
  • GSCP Generic Service Control Plane
  • SC Service Classifier
  • Service function (referred to as SF), a component that performs business processing on data packets;
  • the Service Function Forwarder is responsible for forwarding between multiple internal SFs of the same service node. After the data packet of the overlay is encapsulated and decapsulated by the network forwarding device of the service node, the network packet header is encapsulated, decapsulated, and updated by the network service header (NSH).
  • NSH network service header
  • Network Forwarder which is responsible for forwarding between multiple SFFs of the same service node; and encapsulating and decapsulating the Overlay layer of data packets of the Overlay; and processing different service nodes at the same time Forwarding
  • Service Function Path (SFP).
  • Figure 3 is a schematic diagram of the service function path in the related art. As shown in Figure 3, the SFP starts from the classifier and passes through several ordered specific service function instances. , a business processing path to the destination. In some cases, the general service control platform GSCP does not know all the service function instances that pass through the path, such as the load sharing scenario or the service service level scenario. At this time, the abstract service function chain SFC and the real specific traffic forwarding are passed. A description of such a business function chain between paths formed by an ordered business instance, also referred to as a business function path. A service function chain may include multiple service function paths, and different service function paths correspond to different policies.
  • Control plane metadata (Dataplane Metadata), which is a major feature. Metadata allows each business function node to exchange information with each other to achieve certain business processing purposes.
  • the SFC can separate the network device service function and forwarding, thereby implementing independent operation and processing of the service function, and improving the forwarding performance of the network device.
  • OAM technology is a network transmission technology for network connectivity detection, fault location, and troubleshooting, and a trigger mechanism for providing protection switching when a fault occurs. It includes the Link Connectivity Verification (CV) mechanism, the Ping mechanism, and the Trace mechanism.
  • CV Link Connectivity Verification
  • Ping the Ping mechanism
  • Trace the Trace mechanism.
  • OAM OAM mechanism
  • Ethernet has an Ethernet OAM protocol
  • IP network has an IP OAM protocol
  • MPLS network has an MPLS OAM.
  • the IP Ping and IP Traceroute mechanisms in IP OAM are based on the ICMP protocol.
  • the IP ping implements the request request and the reply reply message by extending the type field of the ICMP protocol.
  • the IP Traceroute implements the Traceroute request request packet by modifying the TTL value in the IP Ping request message, and implements the Traceroute through the TTL overdue ICMP error message.
  • the response is replying to the message; however, there are two major problems with the ICMP bearer: 1.
  • the protocols involving the two IP layers are ICMPv4 and ICMPv6 respectively.
  • LSP ping and LSP Trace mechanisms of the MPLS OAM are based on the UDP protocol and use the destination port number 3503.
  • LSP Ping and LSP Trace are not used based on ICMP for different types of LSPs, such as IPv4 LDP LSPs, IPv6 LDP LSPs, IPv4 RSVP LSPs, IPv6 RSVP LSPs, and PW LSPs.
  • the Ping and Traceroute extensions of the mechanism are extended based on the UDP protocol.
  • FIG. 4 is a schematic diagram of a SFC OAM technology framework in the related art.
  • the technical framework of the SFC OAM is mainly used for diagnosing link status between service function chains or service functions.
  • FIG. 5 is a schematic diagram of the SFC OAM packet format 1 in the related art.
  • a field is reserved in the service function packet header NSH for marking
  • the OAM packet and the OAM packet type are shown in Figure 6.
  • Figure 6 is a schematic diagram of the SFC OAM packet format 2 in the related art.
  • the service function packet header NSH is pre-defined. A bit is reserved for the OAM packet.
  • the OAM packet is placed in a packet other than the NSH of the service function header.
  • the protocol packet which is the extension of the ICMP packet, or the extension of the UDP packet, or other.
  • the present invention provides a method and a device for processing, managing, and maintaining an OAM packet, so as to at least solve the problem that the SFC OAM packet content cannot be determined in the related art, and the protocol is carried based on the protocol.
  • a method for processing, managing, and maintaining an OAM packet including: determining, by the source service node, an OAM packet for sending on a service function chain SFC, where the OAM packet The payload of the Payload, the OAM packet header, and the service function packet header, where the OAM packet is carried by a predetermined SFC OAM network port number; the source service node will be carried in the predetermined SFC OAM network port.
  • the OAM packet on the number is sent to the destination service node on the SFC for processing.
  • the OAM packet adopts at least one of the following formats: a Payload, an OAM packet header, and a service function packet header, where the SFC OAM type is carried in the OAM packet header; the Payload and the OAM packet header.
  • a service function packet header where the SFC OAM type is carried in the service function packet header.
  • the SFC OAM packet carried by the UDP protocol includes at least one of the following: a UDP source port number, a UDP destination port number used to identify the SFC OAM packet port number, and a version number used to identify the SFC OAM packet.
  • Information that is randomly generated by the request packet information for identifying the time point at which the packet is sent, information for identifying the time point at which the packet is received, for requesting the TLV to be extended in the packet, or for responding to the packet
  • the method further includes: a response mode carried in the SFC OAM packet
  • the destination service node does not carry the IPv4/IPv6 UDP packet of the service function packet header, where the IPv4/IPv6 UDP packet carries the OAM report.
  • the document carries the processing result obtained after processing the OAM packet.
  • the source service node is a service classifier or one of the service nodes on the service function chain.
  • a method for processing, managing, and maintaining an OAM packet including: the destination service node receives an OAM message sent on a service function chain SFC, where the OAM message includes: The payload of the Payload, the OAM packet header, and the service function packet header, wherein the OAM packet is carried by a predetermined SFC OAM network port number; and the destination service node processes the received OAM packet.
  • the OAM packet adopts at least one of the following formats: a Payload, an OAM packet header, and a service function packet header, where the SFC OAM type is carried in the OAM packet header; the Payload and the OAM packet header.
  • a service function packet header where the SFC OAM type is carried in the service function packet header.
  • the SFC OAM packet carried by the UDP protocol includes at least one of the following: a UDP source port number, a UDP destination port number used to identify the SFC OAM packet port number, and a version number used to identify the SFC OAM packet.
  • Information that is randomly generated by the request packet information for identifying the time point at which the packet is sent, information for identifying the time point at which the packet is received, for requesting the TLV to be extended in the packet, or for responding to the packet
  • the method further includes: when the response mode carried in the SFC OAM packet is an IPv4/IPv6 user data protocol UDP packet, The IPv4/IPv6 UDP packet of the function packet header is sent to the source service node or the next hop service node that sends the OAM packet, and the SFC OAM packet is carried in the SFC OAM packet.
  • the response mode is the SFC OAM UDP packet
  • the processing result of the OAM packet processing is sent to the source service node or the next hop service node that sends the OAM packet through the SFC OAM UDP packet. .
  • the destination service node is a combination of the other service node or the multiple service nodes except the source service node on the service function chain.
  • an OAM message processing apparatus which is located in a source service node, and includes: a determining module, configured to determine an OAM message for sending on a service function chain SFC.
  • the OAM packet includes: a payload Payload, an OAM packet header, and a service function packet header, wherein the OAM packet is carried by a predetermined SFC OAM network port number; and the first sending module is configured to: The OAM packet that is carried on the predetermined SFC OAM network port number is sent to the destination service node on the SFC for processing.
  • the OAM packet adopts at least one of the following formats: a Payload, an OAM packet header, and a service function packet header, where the SFC OAM type is carried in the OAM packet header; the Payload and the OAM packet header.
  • a service function packet header where the SFC OAM type is carried in the service function packet header.
  • the SFC OAM packet carried by the UDP protocol includes at least one of the following: a UDP source port number, a UDP destination port number used to identify the SFC OAM packet port number, and a version number used to identify the SFC OAM packet.
  • Information that is randomly generated by the request packet information for identifying the time point at which the packet is sent, information for identifying the time point at which the packet is received, for requesting the TLV to be extended in the packet, or for responding to the packet
  • the apparatus further includes: a first receiving module, configured to receive, when the response mode carried in the SFC OAM packet is an IPv4/IPv6 user data protocol UDP packet, the destination service node does not carry a service function report.
  • the response mode is the SFC OAM UDP packet
  • the SFC OAM UDP packet sent by the destination service node is received, where the SFC OAM UDP packet carries the processing result obtained after processing the OAM packet.
  • the source service node is a service classifier or one of the service nodes on the service function chain.
  • an OAM packet processing apparatus which is located in a destination service node, and includes: a third receiving module, configured to receive an OAM packet sent on a service function chain SFC.
  • the OAM packet includes: a payload Payload, an OAM packet header, and a service function packet header, wherein the OAM packet is carried by a predetermined SFC OAM network port number; and the processing module is configured to receive the OAM The message is processed.
  • the OAM packet adopts at least one of the following formats: a Payload, an OAM packet header, and a service function packet header, where the SFC OAM type is carried in the OAM packet header; the Payload and the OAM packet header.
  • a service function packet header where the SFC OAM type is carried in the service function packet header.
  • the SFC OAM packet carried by the UDP protocol includes at least one of the following: a UDP source port number, a UDP destination port number used to identify the SFC OAM packet port number, and a version number used to identify the SFC OAM packet.
  • Information that is randomly generated by the request packet information for identifying the time point at which the packet is sent, information for identifying the time point at which the packet is received, for requesting the TLV to be extended in the packet, or for responding to the packet
  • the apparatus further includes: a second sending module, configured to: when the response mode carried in the SFC OAM packet is an IPv4/IPv6 user data protocol UDP packet, by using an IPv4/IPv6 UDP that does not carry a service function packet header The packet is sent to the source service node or the next hop service node that sends the OAM packet, and the third sending module is configured to be carried in the SFC OAM packet.
  • the response mode is the SFC OAM UDP packet
  • the processing result of the OAM packet processing is sent to the source service node or the next hop service node that sends the OAM packet by using the SFC OAM UDP packet.
  • the destination service node is a combination of the other service node or the multiple service nodes except the source service node on the service function chain.
  • the source service node determines the OAM message to be sent on the service function chain SFC, where the OAM message includes: a payload Payload, an OAM packet header, and a service function packet header, where the The OAM packet is carried by the predetermined SFC OAM network port number; the source service node sends the OAM packet that is carried on the predetermined SFC OAM network port number to the destination service node on the SFC for processing.
  • the problem that the SFC OAM message content cannot be determined and the protocol is carried according to the protocol is solved, and the effect of determining a complete SFC OAM message and improving the SFC OAM scalability is achieved.
  • FIG. 1 is an exemplary diagram of an SFC in the related art
  • FIG. 2 is a schematic diagram of a packet format of a service function packet header in the related art
  • FIG. 3 is a schematic diagram of a service function path in the related art
  • FIG. 4 is a schematic diagram of a SFC OAM technology framework in the related art
  • FIG. 5 is a schematic diagram of a format 1 of an SFC OAM message in the related art
  • FIG. 6 is a schematic diagram of a second format of an SFC OAM packet in the related art
  • FIG. 7 is a flowchart of a method 1 for processing, managing, and maintaining an OAM packet according to an embodiment of the present invention
  • FIG. 8 is a flowchart of a method 2 for processing, managing, and maintaining an OAM packet according to an embodiment of the present invention
  • FIG. 9 is a structural block diagram of an apparatus for processing, managing, and maintaining an OAM message according to an embodiment of the present invention.
  • FIG. 10 is a block diagram showing a preferred structure of an OAM message processing apparatus 1 for operating, managing, and maintaining according to an embodiment of the present invention
  • FIG. 11 is a structural block diagram of an operation, management, and maintenance OAM message processing apparatus 2 according to an embodiment of the present invention.
  • FIG. 12 is a block diagram showing a preferred structure of an operation, management, and maintenance OAM message processing apparatus 2 according to an embodiment of the present invention.
  • FIG. 13 is a schematic diagram of a packet format of a UDP protocol carrying an SFC OAM packet according to an embodiment of the present invention
  • FIG. 14 is a schematic diagram of a format of a complete SFC OAM packet based on a UDP bearer after an Overlay encapsulation according to an embodiment of the present invention
  • FIG. 15 is a schematic diagram of a packet format for implementing an SFC ping function according to an embodiment of the present invention.
  • FIG. 16 is a schematic diagram of implementing an SFC Trace function according to an embodiment of the present invention.
  • FIG. 7 is a flowchart of a method for processing, managing, and maintaining an OAM packet according to an embodiment of the present invention. The process includes the following steps:
  • Step S702 the source service node determines an OAM message to be sent on the service function chain SFC, where the OAM message includes: a payload, a OAM packet header, and a service function packet header, where the OAM packet is scheduled.
  • SFC OAM network port number bearer
  • Step S704 The source service node sends the OAM packet that is carried on the predetermined SFC OAM network port number to the destination service node on the SFC for processing.
  • an OAM packet is determined, and the OAM packet is carried by the predetermined SFC OAM network port number, and the determined OAM packet is sent to the destination service node, and the SFC OAM report cannot be determined in the related technology.
  • the content of the text, and the question of what protocol is used to carry the message achieves the effect of determining a complete SFC OAM message and improving the scalability of the SFC OAM.
  • the foregoing OAM packet may be in a plurality of formats, for example, at least one of the following formats: a Payload, an OAM packet header, and a service function packet header, where the SFC OAM type is carried in the OAM packet header; the Payload and the OAM packet
  • the header of the service function is the header of the service function.
  • the SFC OAM type is carried in the service function header.
  • the protocol for carrying the SFC OAM packet may be multiple.
  • the following uses the UDP protocol as an example.
  • the SFC OAM packet carried by the UDP protocol may include at least one of the following: a UDP source port number, a UDP destination port number for identifying the SFC OAM packet port number, and version information for identifying the version number of the SFC OAM packet.
  • the packet type information used to identify the SFC OAM packet, the response mode information used to identify the response packet, the return coding information used to identify the cause of the fault, the frequency information used to identify the frequency of the packet transmission, and the request message The information randomly generated by the text, the information used to identify the time point of the message transmission, the information used to identify the time point of the message reception, the TLV to be used in the request message, or the identifier in the response message.
  • the source service node may be sent according to the response mode carried in the SFC OAM packet.
  • Different response messages as exemplified below.
  • the response mode carried in the SFC OAM packet is the IPv4/IPv6 user data protocol UDP packet
  • the IPv4/IPv6 UDP packet of the service function packet header is not received by the destination service node, where the IPv4/IPv6 UDP packet is received.
  • the SFC OAM UDP packet sent by the destination service node is received, and the SFC OAM UDP packet sent by the destination service node is received, for example, when the SFC OAM packet carries the SFC OAM UDP packet.
  • the UDP packet carries the processing result obtained after processing the OAM packet.
  • the response mode carried in the SFC OAM packet is not replied, the response packet sent by the destination service node is not received.
  • the source service node is a service classifier or one of the service nodes on the service function chain.
  • FIG. 8 is a flowchart of a second method for processing, managing, and maintaining an OAM packet according to an embodiment of the present invention. The process includes the following steps:
  • the destination service node receives the OAM packet sent by the service function chain SFC, where the OAM packet includes: a payload Payload, an OAM packet header, and a service function packet header, where the OAM packet adopts a predetermined SFC OAM.
  • Network port number bearer
  • Step S804 The destination service node processes the received OAM packet.
  • the OAM packet sent by the SFC OAM network port number sent by the SFC is received, and the received OAM packet is processed, and the SFC OAM packet content cannot be determined in the related art. And the problem of what protocol is used to carry the message, thereby achieving the effect of determining a complete SFC OAM message and improving the scalability of the SFC OAM.
  • the OAM packet After receiving the OAM packet that is sent by the SFC and using the predetermined SFC OAM network port number, the OAM packet is decapsulated, and the port number in the packet is found to be an SFC OAM packet. The OAM packet is processed.
  • the OAM packet can be in multiple formats, for example, at least one of the following formats: a Payload, an OAM packet header, and a service function packet header, where the SFC OAM type is carried in the OAM packet header; Payload, OAM A packet header and a service function packet header, where the SFC OAM type is carried in the service function packet header.
  • the SFC OAM packet can be carried in multiple protocols, and is described below by being carried in the UDP protocol.
  • the SFC OAM packet that is carried by the UPD protocol may include at least one of the following: a UDP source port number, a UDP destination port number used to identify the SFC OAM packet port number, and is used to identify the SFC OAM.
  • Frequency information information for requesting packet random generation, information for identifying the time point at which the message is sent, information for identifying the time point at which the message is received, for requesting the TLV to be extended in the message, or A TLV for identifying the service function link information obtained in the response message, and padding field information for identifying the padding field.
  • the response packet sent by the SFC OAM packet may be sent to the source service node according to the response mode.
  • the response mode carried in the SFC OAM packet is the IPv4/IPv6 user data protocol UDP packet
  • the processing result of the OAM packet processing is sent to the IPv4/IPv6 UDP packet without the service function packet header.
  • the source service node or the next hop service node of the OAM packet for example, when the response mode carried in the SFC OAM packet is SFC OAM UDP packet, the OAM packet processing is processed through the SFC OAM UDP packet.
  • the result is sent to the source service node or the next hop service node that sends the OAM message.
  • the destination service node does not need to send a response packet after receiving the OAM packet.
  • the destination service node is a combination of the other service node or the plurality of service nodes except the source service node on the service function chain.
  • an OAM packet processing device is also provided, which is used to implement the foregoing embodiments and preferred embodiments, and details are not described herein.
  • the term "module” may implement a combination of software and/or hardware of a predetermined function.
  • the apparatus described in the following embodiments is preferably implemented in software, hardware, or a combination of software and hardware, is also possible and contemplated.
  • FIG. 9 is a structural block diagram of an apparatus for processing, managing, and maintaining an OAM packet according to an embodiment of the present invention. As shown in FIG. 9, the apparatus is located in a source service node, and includes: a determining module 92 and a first sending module 94. The device will be described below.
  • the determining module 92 is configured to determine an OAM packet to be sent on the service function chain SFC, where the OAM packet includes: a payload Payload, an OAM packet header, and a service function packet header, where the OAM packet adopts a predetermined The SFC OAM network port number bearer; the first sending module 94 is connected to the determining module 92, and is configured to send the OAM packet that is carried on the predetermined SFC OAM network port number to the destination service node on the SFC for processing.
  • the OAM packet can be in multiple formats, for example, at least one of the following formats: a Payload, an OAM packet header, and a service function packet header, where the SFC OAM type is carried in the OAM packet header; Payload, OAM A packet header and a service function packet header, where the SFC OAM type is carried in the service function packet header.
  • the SFC OAM packet carried by the UDP protocol may include at least one of the following: a UDP source port number, a UDP destination port number used to identify the SFC OAM packet port number, and a version number used to identify the SFC OAM packet.
  • Information randomly generated in the request packet information indicating the time point at which the packet is sent, information indicating the time point at which the packet is received, TLV to be used in the request packet, or response message
  • TLV TLV identifying the acquired service function link information
  • padding field information for identifying the padding field.
  • FIG. 10 is a block diagram showing a preferred structure of an OAM packet processing apparatus according to an embodiment of the present invention. As shown in FIG. 10, the apparatus includes at least one of the following, in addition to all the modules shown in FIG. The first receiving module 102 and the second receiving module 104 are described below.
  • the first receiving module 102 is connected to the first sending module 94, and is configured to receive the service function node without receiving the service function node when the response mode carried in the SFC OAM packet is the IPv4/IPv6 user data protocol UDP packet.
  • the IPv4/IPv6 UDP packet wherein the IPv4/IPv6 UDP packet carries the processing result obtained after processing the OAM packet;
  • the second receiving module 104 is connected to the first sending module 94 and configured to be in the SFC OAM packet.
  • the SFC OAM UDP packet is received, the SFC OAM UDP packet is received by the destination service node.
  • the SFC OAM UDP packet carries the processing result obtained after the OAM packet is processed.
  • the source service node is a service classifier or one of the service nodes on the service function chain.
  • FIG. 11 is a structural block diagram of an operation, management, and maintenance OAM packet processing apparatus 2 according to an embodiment of the present invention. As shown in FIG. 11, the apparatus is located in a destination service node, and includes: a third receiving module 112 and a processing module 114. The device will be described below.
  • the third receiving module 112 is configured to receive the OAM packet sent by the service function chain SFC, where the OAM packet includes: a payload Payload, an OAM packet header, and a service function packet header, where the OAM packet adopts a predetermined The SFC OAM network port number bearer; the processing module 114 is connected to the third receiving module 112, and configured to process the received OAM message.
  • the OAM packet may be in at least one of the following formats: a Payload, an OAM packet header, and a service function packet header, where the SFC OAM type is carried in the OAM packet header; the Payload, the OAM packet header, and the service function.
  • the packet header in which the SFC OAM type is carried in the service function packet header.
  • the SFC OAM packet carried by the UDP protocol includes at least one of the following: a UDP source port number, a UDP destination port number used to identify the SFC OAM packet port number, and is used to identify the SFC OAM packet.
  • the frequency information the information used to randomly generate the request packet, the information used to identify the time point at which the message is sent, the information used to identify the time point of the message reception, the TLV to be used in the request message, or A TLV for identifying the obtained service function link information in the response message, and padding field information for identifying the padding field.
  • FIG. 12 is a block diagram showing a preferred structure of an operation, management, and maintenance OAM message processing apparatus 2 according to an embodiment of the present invention. As shown in FIG. 12, the apparatus includes at least one of the following, in addition to all the modules shown in FIG. The second transmitting module 122 and the third transmitting module 124 are described below.
  • the second sending module 122 is connected to the processing module 114, and is configured to pass the IPv4/IPv6 UDP packet that does not carry the service function packet header when the response mode carried in the SFC OAM packet is the IPv4/IPv6 user data protocol UDP packet.
  • the processing result of the OAM packet processing is sent to the source service node or the next hop service node that sends the OAM packet.
  • the third sending module 124 is connected to the processing module 114 and configured to be carried in the SFC OAM packet. When the response mode is SFC OAM UDP packet, the SFC OAM UDP packet is used to send the OAM packet processing result to the source service node or the next hop service node that sends the OAM packet.
  • the destination service node is a combination of the other service node or the plurality of service nodes except the source service node on the service function chain.
  • FIG. 13 is a schematic diagram of a packet format of a UDP protocol carrying an SFC OAM packet according to an embodiment of the present invention, as shown in FIG.
  • Source Port identifies the UDP source port number.
  • Destination Port identifies the UDP destination port number.
  • a new port number is defined to carry the SFC OAM packet.
  • Version Number identifies the version number of the SFC OAM packet.
  • Message Type identifies the SFC OAM packet type, including the Ping Request packet, the ping reply packet, the connectivity request packet, and the connectivity Reply packet.
  • Reply Mode identifies the response mode of the response packet.
  • the response packet can respond with a normal IPv4/IPv6UDP packet or send a message response through the service function path SFP.
  • the response packet carries the number of the fault (for example, the request packet is incorrect, the TLV is not recognized, the service function is abnormal, etc.); the field in the request packet is 0;
  • Sender’s Handle The request message is randomly generated; the field in the response message is consistent with the request message;
  • Timestamp Sent identifies the time point at which the message is sent.
  • Timestamp Received indicates the time point at which the message is received.
  • the SFP information is included in the service function header and is carried to the last hop service node along the path. Therefore, the SFC ping or SFC Trace request packet may not carry the field.
  • the field needs to obtain the service function link information or the service function related information of the service function chain (for example, bandwidth information, resource information, delay information, etc.)
  • the TLV field needs to be carried in response to the initiator of the SFC Trace. Different types correspond to different information.
  • Padding identifies the padding field to meet the byte requirements required by the message
  • FIG. 14 is a schematic diagram of a format of a complete SFC OAM packet based on UDP bearer after Overlay encapsulation, as shown in FIG. 14 .
  • the service function chain of the embodiment based on the SFC ping function includes: SF1 -> SF2 -> SF3; wherein the Overlay network is an IP network.
  • FIG. 15 is a schematic diagram of a packet format for implementing the SFC ping function according to an embodiment of the present invention. As shown in Figure 15, the SFC OAM dedicated port number is used in the UDP header, and the packet type in the SFC ping request packet is a request packet. Text, the response mode is configured as above. In this embodiment, implementing the Ping function includes the following steps:
  • the Classifier sends the OAM packet in Figure 15 and forwards the packet to the first hop service node 1 of the service function path;
  • the service node 1 decapsulates the Overlay layer, and forwards the packet carrying the SFC service function header to the SFF1.
  • the SFF1 determines that the message is an OAM ping protocol packet, and then forwards the packet to the SFC OAM protocol module.
  • the SFC OAM protocol module invokes the first hop service function SF1 to check whether it is running normally, and if yes, forwards the packet back to SFF1;
  • SFF1 forwards the packet to the service node 1, and the service node 1 performs Overlay encapsulation on the packet, and forwards the packet to the next hop service node 2;
  • the ping response message is configured to carry the service function fault information; and the response message is forwarded to SFF1;
  • SFF1 forwards the corresponding packet to the service node 1, and the service node 1 performs Overlay encapsulation on the packet, and forwards the packet to the Classifier.
  • the service node 2 receives the packet, first decapsulates the Overlay layer, and forwards the packet carrying the SFC service function header to the SFF2.
  • the SFF2 determines that the packet is an OAM protocol packet, and then forwards the packet to the SFC OAM protocol module. ;
  • the SFC OAM protocol module invokes the second hop service function SF2 to check whether it is running normally. If yes, the packet is forwarded back to SFF2.
  • SFF2 forwards the packet to the service node 2, and the service node 2 performs Overlay encapsulation on the packet, and forwards the packet to the next hop service node 3;
  • the ping response message is configured to carry the service function fault information; and the response message is forwarded to the SFF2;
  • SFF2 forwards the corresponding packet to the service node 2, and the service node 2 performs Overlay encapsulation on the packet, forwards the packet to the service node 1 along the reverse path, and then forwards the packet to the Classifier;
  • the service node 3 receives the packet, first decapsulates the Overlay layer, and forwards the packet carrying the SFC service function header to the SFF3.
  • the SFF3 determines that this is an OAM protocol packet and is the last hop of the service function path. , continue to forward to the SFC OAM protocol module processing;
  • the SFC OAM protocol module invokes the third hop service function SF3 to check whether it is running normally. If yes, construct a Ping response message and forward the message back to SFF3; if not, construct a Ping response message to carry Faulty service function fault information; and forwards the packet back to SFF3;
  • SFF3 forwards the packet to the service node 3, and the service node 3 performs Overlay encapsulation on the packet, forwards the packet to the service node 2 and the service node 1 along the reverse path, and then forwards the packet to the Classifier;
  • the Classifier After receiving the Ping response packet, the Classifier displays to the operator whether the Ping succeeds. If it is not successful, the reason for the operator failure is displayed.
  • the service function chain of the specific embodiment based on the SFC Trace function includes: SF1--->SF2--->SF3, where the Overlay network is an IP network.
  • FIG. 16 is a schematic diagram of implementing the SFC Trace function according to the embodiment of the present invention, as shown in FIG. 16 , wherein the UDP header uses the SFC OAM dedicated port number, and the SFC Trace request packet has the packet type as the request packet.
  • the response mode is configured as above; the embodiment includes the following steps:
  • the Classifier sends the OAM packet in FIG. 16 and sets the TTL field in the packet to 1, and forwards the packet to the first hop service node 1 of the service function path;
  • the service node 1 decapsulates the Overlay layer, and forwards the packet carrying the SFC service function header to the SFF1.
  • the SFF1 determines that the packet is an OAM Trace protocol packet and the TTL is 1, and then forwards the packet to the SFC OAM protocol module.
  • the SFC OAM protocol module invokes the first hop service function SF1 to check whether it is in normal operation. If yes, the service information, the resource information, and the delay information of the SF1 are obtained, and are encapsulated in the TLV of the response packet, and the packet is encapsulated. Forwarded to SFF1; if not, constructs a response packet, carries the service function fault information, and forwards the packet back to SFF1;
  • SFF1 forwards the packet to the service node 1, and the service node 1 performs Overlay encapsulation on the packet, and forwards the packet to the Classifier along the IP path.
  • the classifier receives the corresponding packet of the first hop service node, and displays the message to the operator whether the trace is successful. If the success is successful, the information is obtained.
  • the classifier constructs the SFC Trace packet with the TTL of 2 and forwards the packet to the service.
  • the service node 1 receives the packet, first decapsulates the Overlay layer, and forwards the packet carrying the SFC service function header to the SFF1.
  • the SFF1 determines that the packet is an OAM protocol packet, and then forwards the packet to the SFC OAM protocol module. At the same time, SFF1 will decrement the TTL value in the message by one;
  • the SFC OAM protocol module invokes the first hop service function SF1 to check whether it is running normally. If yes, the packet is forwarded back to SFF1.
  • SFF1 forwards the packet to the service node 1, and the service node 1 performs Overlay encapsulation on the packet, and forwards the packet to the next hop service node 2;
  • the service node 2 receives the packet, first decapsulates the Overlay layer, and forwards the packet carrying the SFC service function header to the SFF2.
  • the SFF2 determines that the packet is an OAM protocol packet and the TTL is 1. SFC OAM protocol module processing;
  • the SFC OAM protocol module invokes the second hop service function SF2 to check whether it is running normally. If yes, the service information, the resource information, and the delay information of the SF2 are obtained, and are encapsulated in the TLV of the response packet, and the packet is sent. Forwarding to SFF2; if not, constructing a response packet, carrying the service function fault information, and forwarding the packet back to SFF2;
  • the SFF2 forwards the packet to the service node 2, and the service node 2 performs Overlay encapsulation on the packet, and forwards the packet to the Classifier along the IP path.
  • the classifier receives the corresponding packet of the second hop service node, and displays the message to the operator whether the trace is successful. If the success is successful, the information is obtained.
  • the classifier constructs the SFC Trace packet with the TTL of 3 and forwards the packet to the service.
  • the service node 1 receives the packet, first decapsulates the Overlay layer, and forwards the packet carrying the SFC service function header to the SFF1.
  • the SFF1 determines that the packet is an OAM protocol packet, and then forwards the packet to the SFC OAM protocol module. At the same time, SFF1 will decrement the TTL value in the message by one;
  • the protocol module invokes the first hop service function SF1 to check whether it is running normally, and if yes, forwards the packet back to SFF1;
  • SFF1 forwards the packet to the service node 1, and the service node 1 performs Overlay encapsulation on the packet, and forwards the packet to the next hop service node 2;
  • the service node 2 receives the packet, first decapsulates the Overlay layer, and forwards the packet carrying the SFC service function header to the SFF2.
  • the SFF2 determines that the packet is an OAM protocol packet, and then forwards the packet to the SFC OAM protocol module. At the same time, SFF2 will decrement the TTL value in the message by one;
  • the protocol module invokes the first hop service function SF2 to check whether it is running normally. If yes, the packet is forwarded back to SFF2.
  • SFF2 forwards the packet to the service node 2, and the service node 2 performs Overlay encapsulation on the packet, and forwards the packet to the next hop service node 3;
  • the service node 3 receives the packet, first decapsulates the Overlay layer, and forwards the packet carrying the SFC service function header to the SFF3.
  • the SFF3 determines that the packet is an OAM protocol packet and the TTL is 1. SFC OAM protocol module processing;
  • the protocol module invokes the third hop service function SF3 to check whether it is running normally. If yes, the SF3 service information, resource information, and delay information are obtained, encapsulated in the TLV of the response packet, and the packet is forwarded back. SFF3; if not, construct a response message, carry the service function fault information, and forward the message back to SFF3;
  • SFF3 forwards the packet to the service node 3, and the service node 3 performs Overlay encapsulation on the packet, and forwards the packet to the Classifier along the IP path.
  • the classifier receives the corresponding packet of the third hop service node, and displays to the operator whether the trace is successful. If successful, the obtained information is displayed; if the sending is unsuccessful, the reason for the failure is displayed.
  • modules or steps of the present invention described above can be implemented by a general-purpose computing device that can be centralized on a single computing device or distributed across a network of multiple computing devices. Alternatively, they may be implemented by program code executable by the computing device such that they may be stored in the storage device by the computing device and, in some cases, may be different from the order herein.
  • the steps shown or described are performed, or they are separately fabricated into individual integrated circuit modules, or a plurality of modules or steps thereof are fabricated as a single integrated circuit module.
  • the invention is not limited to any specific combination of hardware and software.
  • the embodiment of the present invention provides a method and an apparatus for processing, managing, and maintaining an OAM packet, and solves the problem that the SFC OAM packet content cannot be determined in the related art, and the protocol is carried based on the protocol. Achieved a complete SFC OAM message and improved SFC OAM scalability.

Abstract

Disclosed are a processing method and apparatus for an operation, administration and maintenance (OAM) message. The method comprises: a source-end service node determines an OAM message to be sent on service function chaining (SFC), wherein the OAM message includes a load Payload, an OAM message header and a service function message header, and the OAM message is carried by a pre-determined SFC OAM network port number; and the source-end service node sends the OAM message which is carried on the pre-determined SFC OAM network port number to a destination service node on the SFC for processing. By means of the present invention, the problems in the prior art that the content of the SFC OAM message cannot be determined and a protocol based on which the message is carried cannot be determined can be solved, and the effects of determining a complete SFC OAM message and improving the SFC OAM expandability are further achieved.

Description

操作、管理和维护OAM报文处理方法及装置Operation, management and maintenance OAM message processing method and device 技术领域Technical field
本发明涉及通信领域,具体而言,涉及一种操作、管理和维护(Operation Administration and Maintenance,简称为OAM)报文处理方法及装置。The present invention relates to the field of communications, and in particular to an operation, management, and maintenance (OAM) message processing method and apparatus.
背景技术Background technique
自从数据中心网络向Overlay网络发展以后,网络边缘成为了虚拟网络与物理网络的分界点,其中,网络边缘可以为Server或者ToR,以及可能为Gateway。然而Overlay技术并没有解决所有问题,数据中心中还有很多Middleware,如防火墙/负载均衡器等,这些设备都是基于用户业务来处理数据的,如果通过隧道而穿越这些设备,显然是不行的。Since the development of the data center network to the Overlay network, the network edge has become the demarcation point between the virtual network and the physical network, wherein the network edge can be Server or ToR, and possibly Gateway. However, Overlay technology does not solve all the problems. There are many Middleware in the data center, such as firewall/load balancer. These devices process data based on user services. If you traverse these devices through tunnels, it is obviously not feasible.
数据中心的这种部署模型,要求虚拟防火墙/负载均衡器可以在网络中任意部署,也就是与网络拓扑无关。这样新问题是,如何将流量能够灵活的通过虚拟防火墙/负载均衡器进行处理?这些虚拟防火墙/负载均衡器等业务处理功能,独立于原网络拓扑,由标准服务器来实现。This deployment model of the data center requires that the virtual firewall/load balancer can be deployed arbitrarily in the network, that is, independent of the network topology. The new question is how to handle traffic flexibly through a virtual firewall/load balancer? Service processing functions such as these virtual firewalls/load balancers are independent of the original network topology and are implemented by standard servers.
在相关技术中,把虚拟防火墙/负载均衡器/网关等业务处理功能,称为业务功能(Service Function,简称为SF),而流量经过一系列的SF的处理,形成业务功能链(Service Function Chaining,简称为SFC)。业务功能链是一系列抽象的业务功能的有序排列,具体业务流量转发时到底经过的哪些SFFs和/或哪些SFs的有序组合,SFC是不定义的。图1是相关技术中SFC的示例图,如图1所示,实线与虚线表示两条SFC,有时也叫业务链Service Chain。下面对SFC的框架进行说明。In the related art, the service processing function such as the virtual firewall/load balancer/gateway is called a service function (Service Function, referred to as SF), and the traffic is processed through a series of SFs to form a service function chain (Service Function Chaining). , referred to as SFC). The business function chain is an orderly arrangement of a series of abstract business functions. The SFCs are not defined in the order of which SFFs and/or SFs are ordered when the specific service traffic is forwarded. 1 is an exemplary diagram of an SFC in the related art. As shown in FIG. 1, solid lines and broken lines indicate two SFCs, sometimes called a service chain Service Chain. The following describes the framework of the SFC.
该SFC可以分为如下组件:The SFC can be divided into the following components:
1.业务叠加(Service Overlay),即各个业务功能节点需要通信的Overlay(叠加)技术;1. Service Overlay, that is, Overlay technology that each service function node needs to communicate;
2.通用业务控制平面(Generic Service Control Plane,简称为GSCP),形成SFC的控制器;2. Generic Service Control Plane (GSCP), which forms the controller of the SFC;
3.业务分类器(Service Classifier,简称为SC),即需要进行者流识别,然后特定的流,进行特定的SFC处理; 3. Service Classifier (referred to as SC), that is, need to identify the flow of the person, and then perform a specific SFC process for the specific stream;
4、业务功能(Service Function,简称为SF),对数据报文进行业务处理的组件;4. Service function (referred to as SF), a component that performs business processing on data packets;
5.业务功能转发器(Service Function Forwarder,简称为SFF),负责同一业务节点的内部多个SFs之间的转发。Overlay的数据报文经过业务节点的网络转发器NF封装、解封装外层overlay层后,主要在SFF组件上进行封装、解封装、更新业务功能报文头(Network Service Header,简称为NSH)。图2是相关技术中业务功能报文头的报文格式示意图,如图2所示;5. The Service Function Forwarder (SFF) is responsible for forwarding between multiple internal SFs of the same service node. After the data packet of the overlay is encapsulated and decapsulated by the network forwarding device of the service node, the network packet header is encapsulated, decapsulated, and updated by the network service header (NSH). 2 is a schematic diagram of a packet format of a service function packet header in the related art, as shown in FIG. 2;
6.网络转发器(Network Forwarder,简称为NF),负责同一业务节点的内部多个SFFs之间的转发;以及对Overlay的数据报文进行封装、解封装Overlay层;同时,处理不同业务节点之间的转发;6. Network Forwarder (NF), which is responsible for forwarding between multiple SFFs of the same service node; and encapsulating and decapsulating the Overlay layer of data packets of the Overlay; and processing different service nodes at the same time Forwarding
7.业务功能路径(Service Function Path,简称为SFP),图3是相关技术中业务功能路径的示意图,如图3所示,SFP是从分类器开始,经过若干有序的具体的业务功能实例,达到目的地的一条业务处理路径。在某些情况下,通用业务控制平台GSCP并不能知晓沿途经过的所有业务功能实例,比如负荷分担场景或者业务服务等级场景等,此时,位于抽象的业务功能链SFC和真实具体的流量转发经过的有序业务实例构成的路径之间的这种业务功能链的描述,也称之为业务功能路径。一条业务功能链可能包括多个业务功能路径,不同的业务功能路径对应于不同的策略。7. Service Function Path (SFP). Figure 3 is a schematic diagram of the service function path in the related art. As shown in Figure 3, the SFP starts from the classifier and passes through several ordered specific service function instances. , a business processing path to the destination. In some cases, the general service control platform GSCP does not know all the service function instances that pass through the path, such as the load sharing scenario or the service service level scenario. At this time, the abstract service function chain SFC and the real specific traffic forwarding are passed. A description of such a business function chain between paths formed by an ordered business instance, also referred to as a business function path. A service function chain may include multiple service function paths, and different service function paths correspond to different policies.
8.控制平面元数据(Dataplane Metadata),这是一大特点,元数据(Metadata)允许各个业务功能节点,能够互相交换信息,达到某种业务处理目的。8. Control plane metadata (Dataplane Metadata), which is a major feature. Metadata allows each business function node to exchange information with each other to achieve certain business processing purposes.
综上所述,SFC能够将网络设备业务功能和转发分离开来,从而实现了业务功能的独立运算和处理,提升网络设备的转发性能。In summary, the SFC can separate the network device service function and forwarding, thereby implementing independent operation and processing of the service function, and improving the forwarding performance of the network device.
OAM技术是针对网络连通性检测、故障定位、排查的网络传输技术,以及出现故障的时候,能够提供保护倒换的触发机制。它包含了链路连通性检测(Connectivity Verification,简称为CV)机制、Ping机制以及Trace机制。对于不同的承载网协议,均有相应的OAM机制。例如,以太网有以太OAM协议,IP网络有IP OAM协议,MPLS网络有MPLS OAM。OAM technology is a network transmission technology for network connectivity detection, fault location, and troubleshooting, and a trigger mechanism for providing protection switching when a fault occurs. It includes the Link Connectivity Verification (CV) mechanism, the Ping mechanism, and the Trace mechanism. For different bearer network protocols, there is a corresponding OAM mechanism. For example, Ethernet has an Ethernet OAM protocol, an IP network has an IP OAM protocol, and an MPLS network has an MPLS OAM.
其中,IP OAM中的IP Ping和IP Traceroute机制是基于ICMP协议的。其中,IP Ping通过扩展ICMP协议的type的字段实现请求request和应答reply消息;IP Traceroute通过修改IP Ping request消息中的TTL值实现Traceroute的请求request报文,通过TTL超期的ICMP差错报文实现Traceroute的应答reply报文;但是通过ICMP承载存在两大问题:1.涉及两种IP层的协议,分别是ICMPv4和ICMPv6,当扩展SFC OAM时, 从两个协议层面都去扩展显得略微繁琐;2.ICMP报文不方便用于扩展来携带Trace响应信息。The IP Ping and IP Traceroute mechanisms in IP OAM are based on the ICMP protocol. The IP ping implements the request request and the reply reply message by extending the type field of the ICMP protocol. The IP Traceroute implements the Traceroute request request packet by modifying the TTL value in the IP Ping request message, and implements the Traceroute through the TTL overdue ICMP error message. The response is replying to the message; however, there are two major problems with the ICMP bearer: 1. The protocols involving the two IP layers are ICMPv4 and ICMPv6 respectively. When the SFC OAM is extended, It is slightly cumbersome to extend from both protocol levels; 2. ICMP messages are not convenient for extension to carry Trace response information.
另外,MPLS OAM的LSP Ping和LSP Trace机制是基于UDP协议的,使用目的端口号3503。因为需要考虑到对不同类型的LSP(比如,IPv4LDP LSP、IPv6LDP LSP、IPv4RSVP LSP、IPv6RSVP LSP、PW LSP等)进行不同的LSP Ping和LSP Trace,为了方便扩展,LSP Ping和LSP Trace没有使用基于ICMP机制的Ping和Traceroute扩展,而是基于UDP协议进行扩展。In addition, the LSP ping and LSP Trace mechanisms of the MPLS OAM are based on the UDP protocol and use the destination port number 3503. LSP Ping and LSP Trace are not used based on ICMP for different types of LSPs, such as IPv4 LDP LSPs, IPv6 LDP LSPs, IPv4 RSVP LSPs, IPv6 RSVP LSPs, and PW LSPs. The Ping and Traceroute extensions of the mechanism are extended based on the UDP protocol.
图4是相关技术中SFC OAM技术框架示意图,如图4所示,SFC OAM的技术框架主要用于诊断业务功能链或者业务功能之间的链路状况。其中的一种实现方式如图5所示,图5是相关技术中SFC OAM报文格式一的示意图,如图5所示,在业务功能报文头NSH中预留一个字段,用于标识是OAM报文以及OAM报文类型;另一种实现方式如图6所示,图6是相关技术中SFC OAM报文格式二的示意图,如图6所示,在业务功能报文头NSH中预留1个Bit,用于标识是OAM报文,至于是哪种类型的OAM报文,放在业务功能报文头NSH以外的报文中。但是无论哪种方案,都没有涉及到具体的SFC OAM报文内容,到底承载在什么协议报文之上,是ICMP报文的扩展呢,还是UDP报文的扩展呢,还是其他。4 is a schematic diagram of a SFC OAM technology framework in the related art. As shown in FIG. 4, the technical framework of the SFC OAM is mainly used for diagnosing link status between service function chains or service functions. As shown in FIG. 5, FIG. 5 is a schematic diagram of the SFC OAM packet format 1 in the related art. As shown in FIG. 5, a field is reserved in the service function packet header NSH for marking The OAM packet and the OAM packet type are shown in Figure 6. Figure 6 is a schematic diagram of the SFC OAM packet format 2 in the related art. As shown in Figure 6, the service function packet header NSH is pre-defined. A bit is reserved for the OAM packet. The OAM packet is placed in a packet other than the NSH of the service function header. However, no matter which solution, the content of the specific SFC OAM packet is not involved. What is the protocol packet, which is the extension of the ICMP packet, or the extension of the UDP packet, or other.
因此,在相关技术中,存在无法确定SFC OAM报文内容,以及基于什么协议承载该报文的问题。Therefore, in the related art, there is a problem that the content of the SFC OAM message cannot be determined, and based on what protocol carries the message.
发明内容Summary of the invention
本发明提供了一种操作、管理和维护OAM报文处理方法及装置,以至少解决相关技术中存在无法确定SFC OAM报文内容,以及基于什么协议承载该报文的问题。The present invention provides a method and a device for processing, managing, and maintaining an OAM packet, so as to at least solve the problem that the SFC OAM packet content cannot be determined in the related art, and the protocol is carried based on the protocol.
根据本发明的一个方面,提供了一种操作、管理和维护OAM报文处理方法,包括:源端业务节点确定用于在业务功能链SFC上发送的OAM报文,其中,所述OAM报文包括:载荷Payload、OAM报文头、业务功能报文头,其中,所述OAM报文采用预定的SFC OAM网络端口号承载;所述源端业务节点将承载在所述预定的SFC OAM网络端口号上的所述OAM报文发送给所述SFC上的目的业务节点处理。According to an aspect of the present invention, a method for processing, managing, and maintaining an OAM packet is provided, including: determining, by the source service node, an OAM packet for sending on a service function chain SFC, where the OAM packet The payload of the Payload, the OAM packet header, and the service function packet header, where the OAM packet is carried by a predetermined SFC OAM network port number; the source service node will be carried in the predetermined SFC OAM network port. The OAM packet on the number is sent to the destination service node on the SFC for processing.
优选地,所述OAM报文采用以下格式至少之一:Payload、OAM报文头、业务功能报文头,其中,SFC OAM类型承载于所述OAM报文头中;Payload、OAM报文头、业务功能报文头,其中,SFC OAM类型承载于所述业务功能报文头中。 Preferably, the OAM packet adopts at least one of the following formats: a Payload, an OAM packet header, and a service function packet header, where the SFC OAM type is carried in the OAM packet header; the Payload and the OAM packet header. A service function packet header, where the SFC OAM type is carried in the service function packet header.
优选地,基于UDP协议承载的SFC OAM报文包括以下信息至少之一:UDP源端口号、用于标识SFC OAM报文端口号的UDP目的端口号、用于标识SFC OAM报文的版本号的版本信息、用于标识SFC OAM报文的报文类型信息、用于标识响应报文的响应模式信息、用于标识故障原因的返回编码信息、用于标识报文发送频率的频率信息、用于请求报文随机生成的信息、用于标识报文发送的时间点的信息、用于标识报文接收的时间点的信息、用于请求报文中待扩展的TLV,或者用于响应报文中标识获取的业务功能链路信息的TLV、用于标识填充字段的填充字段信息。Preferably, the SFC OAM packet carried by the UDP protocol includes at least one of the following: a UDP source port number, a UDP destination port number used to identify the SFC OAM packet port number, and a version number used to identify the SFC OAM packet. The version information, the packet type information used to identify the SFC OAM packet, the response mode information used to identify the response packet, the return encoding information used to identify the cause of the fault, and the frequency information used to identify the frequency of the packet transmission. Information that is randomly generated by the request packet, information for identifying the time point at which the packet is sent, information for identifying the time point at which the packet is received, for requesting the TLV to be extended in the packet, or for responding to the packet A TLV identifying the acquired service function link information, and padding field information for identifying the padding field.
优选地,在将承载在所述预定的SFC OAM网络端口号上的所述OAM报文发送给所述SFC上的目的业务节点处理之后,还包括:在所述SFC OAM报文携带的响应模式为IPv4/IPv6用户数据协议UDP报文时,接收到所述目的业务节点不携带业务功能报文头的IPv4/IPv6UDP报文,其中,所述IPv4/IPv6UDP报文中携带有对所述OAM报文处理后获得的处理结果;在所述SFC OAM报文携带的响应模式为SFC OAM UDP报文时,接收到所述目的业务节点发送的SFC OAM UDP报文,其中,所述SFC OAM UDP报文携带有对所述OAM报文处理后获得的处理结果。Preferably, after the OAM packet sent on the predetermined SFC OAM network port number is sent to the destination service node on the SFC, the method further includes: a response mode carried in the SFC OAM packet When the IPv4/IPv6 user data protocol UDP packet is received, the destination service node does not carry the IPv4/IPv6 UDP packet of the service function packet header, where the IPv4/IPv6 UDP packet carries the OAM report. The SFC OAM UDP packet sent by the destination service node, where the SFC OAM UDP packet is received, when the response mode of the SFC OAM packet is SFC OAM UDP packet, the SFC OAM UDP packet is received by the destination service node. The document carries the processing result obtained after processing the OAM packet.
优选地,所述源端业务节点为业务分类器或者业务功能链上的其中一个业务节点。Preferably, the source service node is a service classifier or one of the service nodes on the service function chain.
根据本发明的另一方面,提供了一种操作、管理和维护OAM报文处理方法,包括:目的业务节点接收在业务功能链SFC上发送的OAM报文,其中,所述OAM报文包括:载荷Payload、OAM报文头、业务功能报文头,其中,OAM报文采用预定的SFC OAM网络端口号承载;所述目的业务节点对接收的所述OAM报文进行处理。According to another aspect of the present invention, a method for processing, managing, and maintaining an OAM packet is provided, including: the destination service node receives an OAM message sent on a service function chain SFC, where the OAM message includes: The payload of the Payload, the OAM packet header, and the service function packet header, wherein the OAM packet is carried by a predetermined SFC OAM network port number; and the destination service node processes the received OAM packet.
优选地,所述OAM报文采用以下格式至少之一:Payload、OAM报文头、业务功能报文头,其中,SFC OAM类型承载于所述OAM报文头中;Payload、OAM报文头、业务功能报文头,其中,SFC OAM类型承载于所述业务功能报文头中。Preferably, the OAM packet adopts at least one of the following formats: a Payload, an OAM packet header, and a service function packet header, where the SFC OAM type is carried in the OAM packet header; the Payload and the OAM packet header. A service function packet header, where the SFC OAM type is carried in the service function packet header.
优选地,基于UDP协议承载的SFC OAM报文包括以下信息至少之一:UDP源端口号、用于标识SFC OAM报文端口号的UDP目的端口号、用于标识SFC OAM报文的版本号的版本信息、用于标识SFC OAM报文的报文类型信息、用于标识响应报文的响应模式信息、用于标识故障原因的返回编码信息、用于标识报文发送频率的频率信息、用于请求报文随机生成的信息、用于标识报文发送的时间点的信息、用于标识报文接收的时间点的信息、用于请求报文中待扩展的TLV,或者用于响应报文中标识获取的业务功能链路信息的TLV、用于标识填充字段的填充字段信息。Preferably, the SFC OAM packet carried by the UDP protocol includes at least one of the following: a UDP source port number, a UDP destination port number used to identify the SFC OAM packet port number, and a version number used to identify the SFC OAM packet. The version information, the packet type information used to identify the SFC OAM packet, the response mode information used to identify the response packet, the return encoding information used to identify the cause of the fault, and the frequency information used to identify the frequency of the packet transmission. Information that is randomly generated by the request packet, information for identifying the time point at which the packet is sent, information for identifying the time point at which the packet is received, for requesting the TLV to be extended in the packet, or for responding to the packet A TLV identifying the acquired service function link information, and padding field information for identifying the padding field.
在所述目的业务节点对接收的所述OAM报文进行处理之后,还包括:在所述SFC OAM报文携带的响应模式为IPv4/IPv6用户数据协议UDP报文时,通过不携带业务 功能报文头的IPv4/IPv6UDP报文将对所述OAM报文处理后的处理结果发送给发送所述OAM报文的源端业务节点或者下一跳业务节点;在所述SFC OAM报文携带的响应模式为SFC OAM UDP报文时,通过所述SFC OAM UDP报文将对所述OAM报文处理后的处理结果发送给发送所述OAM报文的源端业务节点或者下一跳业务节点。After the destination service node processes the received OAM packet, the method further includes: when the response mode carried in the SFC OAM packet is an IPv4/IPv6 user data protocol UDP packet, The IPv4/IPv6 UDP packet of the function packet header is sent to the source service node or the next hop service node that sends the OAM packet, and the SFC OAM packet is carried in the SFC OAM packet. When the response mode is the SFC OAM UDP packet, the processing result of the OAM packet processing is sent to the source service node or the next hop service node that sends the OAM packet through the SFC OAM UDP packet. .
优选地,所述目的业务节点为业务功能链上除所述源端业务节点之外的其余一个业务节点或多个业务节点的组合。Preferably, the destination service node is a combination of the other service node or the multiple service nodes except the source service node on the service function chain.
根据本发明的另一方面,提供了一种操作、管理和维护OAM报文处理装置,位于源端业务节点中,包括:确定模块,用于确定用于在业务功能链SFC上发送的OAM报文,其中,所述OAM报文包括:载荷Payload、OAM报文头、业务功能报文头,其中,所述OAM报文采用预定的SFC OAM网络端口号承载;第一发送模块,用于将承载在所述预定的SFC OAM网络端口号上的所述OAM报文发送给所述SFC上的目的业务节点处理。According to another aspect of the present invention, an OAM message processing apparatus is provided, which is located in a source service node, and includes: a determining module, configured to determine an OAM message for sending on a service function chain SFC. The OAM packet includes: a payload Payload, an OAM packet header, and a service function packet header, wherein the OAM packet is carried by a predetermined SFC OAM network port number; and the first sending module is configured to: The OAM packet that is carried on the predetermined SFC OAM network port number is sent to the destination service node on the SFC for processing.
优选地,所述OAM报文采用以下格式至少之一:Payload、OAM报文头、业务功能报文头,其中,SFC OAM类型承载于所述OAM报文头中;Payload、OAM报文头、业务功能报文头,其中,SFC OAM类型承载于所述业务功能报文头中。Preferably, the OAM packet adopts at least one of the following formats: a Payload, an OAM packet header, and a service function packet header, where the SFC OAM type is carried in the OAM packet header; the Payload and the OAM packet header. A service function packet header, where the SFC OAM type is carried in the service function packet header.
优选地,基于UDP协议承载的SFC OAM报文包括以下信息至少之一:UDP源端口号、用于标识SFC OAM报文端口号的UDP目的端口号、用于标识SFC OAM报文的版本号的版本信息、用于标识SFC OAM报文的报文类型信息、用于标识响应报文的响应模式信息、用于标识故障原因的返回编码信息、用于标识报文发送频率的频率信息、用于请求报文随机生成的信息、用于标识报文发送的时间点的信息、用于标识报文接收的时间点的信息、用于请求报文中待扩展的TLV,或者用于响应报文中标识获取的业务功能链路信息的TLV、用于标识填充字段的填充字段信息。Preferably, the SFC OAM packet carried by the UDP protocol includes at least one of the following: a UDP source port number, a UDP destination port number used to identify the SFC OAM packet port number, and a version number used to identify the SFC OAM packet. The version information, the packet type information used to identify the SFC OAM packet, the response mode information used to identify the response packet, the return encoding information used to identify the cause of the fault, and the frequency information used to identify the frequency of the packet transmission. Information that is randomly generated by the request packet, information for identifying the time point at which the packet is sent, information for identifying the time point at which the packet is received, for requesting the TLV to be extended in the packet, or for responding to the packet A TLV identifying the acquired service function link information, and padding field information for identifying the padding field.
优选地,该装置还包括:第一接收模块,设置为在所述SFC OAM报文携带的响应模式为IPv4/IPv6用户数据协议UDP报文时,接收到所述目的业务节点不携带业务功能报文头的IPv4/IPv6UDP报文,其中,所述IPv4/IPv6UDP报文中携带有对所述OAM报文处理后获得的处理结果;第二接收模块,设置为在所述SFC OAM报文携带的响应模式为SFC OAM UDP报文时,接收到所述目的业务节点发送的SFC OAM UDP报文,其中,所述SFC OAM UDP报文携带有对所述OAM报文处理后获得的处理结果。Preferably, the apparatus further includes: a first receiving module, configured to receive, when the response mode carried in the SFC OAM packet is an IPv4/IPv6 user data protocol UDP packet, the destination service node does not carry a service function report. The IPv4/IPv6 UDP packet of the header, wherein the IPv4/IPv6 UDP packet carries a processing result obtained by processing the OAM packet; and the second receiving module is configured to be carried in the SFC OAM packet. When the response mode is the SFC OAM UDP packet, the SFC OAM UDP packet sent by the destination service node is received, where the SFC OAM UDP packet carries the processing result obtained after processing the OAM packet.
优选地,所述源端业务节点为业务分类器或者业务功能链上的其中一个业务节点。 Preferably, the source service node is a service classifier or one of the service nodes on the service function chain.
根据本发明的还一方面,提供了一种操作、管理和维护OAM报文处理装置,位于目的业务节点中,包括:第三接收模块,设置为接收在业务功能链SFC上发送的OAM报文,其中,所述OAM报文包括:载荷Payload、OAM报文头、业务功能报文头,其中,OAM报文采用预定的SFC OAM网络端口号承载;处理模块,设置为对接收的所述OAM报文进行处理。According to still another aspect of the present invention, an OAM packet processing apparatus is provided, which is located in a destination service node, and includes: a third receiving module, configured to receive an OAM packet sent on a service function chain SFC. The OAM packet includes: a payload Payload, an OAM packet header, and a service function packet header, wherein the OAM packet is carried by a predetermined SFC OAM network port number; and the processing module is configured to receive the OAM The message is processed.
优选地,所述OAM报文采用以下格式至少之一:Payload、OAM报文头、业务功能报文头,其中,SFC OAM类型承载于所述OAM报文头中;Payload、OAM报文头、业务功能报文头,其中,SFC OAM类型承载于所述业务功能报文头中。Preferably, the OAM packet adopts at least one of the following formats: a Payload, an OAM packet header, and a service function packet header, where the SFC OAM type is carried in the OAM packet header; the Payload and the OAM packet header. A service function packet header, where the SFC OAM type is carried in the service function packet header.
优选地,基于UDP协议承载的SFC OAM报文包括以下信息至少之一:UDP源端口号、用于标识SFC OAM报文端口号的UDP目的端口号、用于标识SFC OAM报文的版本号的版本信息、用于标识SFC OAM报文的报文类型信息、用于标识响应报文的响应模式信息、用于标识故障原因的返回编码信息、用于标识报文发送频率的频率信息、用于请求报文随机生成的信息、用于标识报文发送的时间点的信息、用于标识报文接收的时间点的信息、用于请求报文中待扩展的TLV,或者用于响应报文中标识获取的业务功能链路信息的TLV、用于标识填充字段的填充字段信息。Preferably, the SFC OAM packet carried by the UDP protocol includes at least one of the following: a UDP source port number, a UDP destination port number used to identify the SFC OAM packet port number, and a version number used to identify the SFC OAM packet. The version information, the packet type information used to identify the SFC OAM packet, the response mode information used to identify the response packet, the return encoding information used to identify the cause of the fault, and the frequency information used to identify the frequency of the packet transmission. Information that is randomly generated by the request packet, information for identifying the time point at which the packet is sent, information for identifying the time point at which the packet is received, for requesting the TLV to be extended in the packet, or for responding to the packet A TLV identifying the acquired service function link information, and padding field information for identifying the padding field.
优选地,该装置还包括:第二发送模块,设置为在所述SFC OAM报文携带的响应模式为IPv4/IPv6用户数据协议UDP报文时,通过不携带业务功能报文头的IPv4/IPv6UDP报文将对所述OAM报文处理后的处理结果发送给发送所述OAM报文的源端业务节点或者下一跳业务节点;第三发送模块,设置为在所述SFC OAM报文携带的响应模式为SFC OAM UDP报文时,通过所述SFC OAM UDP报文将对所述OAM报文处理后的处理结果发送给发送所述OAM报文的源端业务节点或者下一跳业务节点。Preferably, the apparatus further includes: a second sending module, configured to: when the response mode carried in the SFC OAM packet is an IPv4/IPv6 user data protocol UDP packet, by using an IPv4/IPv6 UDP that does not carry a service function packet header The packet is sent to the source service node or the next hop service node that sends the OAM packet, and the third sending module is configured to be carried in the SFC OAM packet. When the response mode is the SFC OAM UDP packet, the processing result of the OAM packet processing is sent to the source service node or the next hop service node that sends the OAM packet by using the SFC OAM UDP packet.
优选地,所述目的业务节点为业务功能链上除所述源端业务节点之外的其余一个业务节点或多个业务节点的组合。Preferably, the destination service node is a combination of the other service node or the multiple service nodes except the source service node on the service function chain.
通过本发明,源端业务节点确定用于在业务功能链SFC上发送的OAM报文,其中,所述OAM报文包括:载荷Payload、OAM报文头、业务功能报文头,其中,所述OAM报文采用预定的SFC OAM网络端口号承载;所述源端业务节点将承载在所述预定的SFC OAM网络端口号上的所述OAM报文发送给所述SFC上的目的业务节点处理,解决了相关技术中存在无法确定SFC OAM报文内容,以及基于什么协议承载该报文的问题,进而达到了确定了一种完整SFC OAM报文,以及提高SFC OAM扩展性的效果。 The source service node determines the OAM message to be sent on the service function chain SFC, where the OAM message includes: a payload Payload, an OAM packet header, and a service function packet header, where the The OAM packet is carried by the predetermined SFC OAM network port number; the source service node sends the OAM packet that is carried on the predetermined SFC OAM network port number to the destination service node on the SFC for processing. The problem that the SFC OAM message content cannot be determined and the protocol is carried according to the protocol is solved, and the effect of determining a complete SFC OAM message and improving the SFC OAM scalability is achieved.
附图说明DRAWINGS
此处所说明的附图用来提供对本发明的进一步理解,构成本申请的一部分,本发明的示意性实施例及其说明用于解释本发明,并不构成对本发明的不当限定。在附图中:The drawings described herein are intended to provide a further understanding of the invention, and are intended to be a part of the invention. In the drawing:
图1是相关技术中SFC的示例图;1 is an exemplary diagram of an SFC in the related art;
图2是相关技术中业务功能报文头的报文格式示意图;2 is a schematic diagram of a packet format of a service function packet header in the related art;
图3是相关技术中业务功能路径的示意图;3 is a schematic diagram of a service function path in the related art;
图4是相关技术中SFC OAM技术框架示意图;4 is a schematic diagram of a SFC OAM technology framework in the related art;
图5是相关技术中SFC OAM报文格式一的示意图;5 is a schematic diagram of a format 1 of an SFC OAM message in the related art;
图6是相关技术中SFC OAM报文格式二的示意图;6 is a schematic diagram of a second format of an SFC OAM packet in the related art;
图7是根据本发明实施例的操作、管理和维护OAM报文处理方法一的流程图;7 is a flowchart of a method 1 for processing, managing, and maintaining an OAM packet according to an embodiment of the present invention;
图8是根据本发明实施例的操作、管理和维护OAM报文处理方法二的流程图;FIG. 8 is a flowchart of a method 2 for processing, managing, and maintaining an OAM packet according to an embodiment of the present invention;
图9是根据本发明实施例的操作、管理和维护OAM报文处理装置一的结构框图;9 is a structural block diagram of an apparatus for processing, managing, and maintaining an OAM message according to an embodiment of the present invention;
图10是根据本发明实施例的操作、管理和维护OAM报文处理装置一的优选结构框图;FIG. 10 is a block diagram showing a preferred structure of an OAM message processing apparatus 1 for operating, managing, and maintaining according to an embodiment of the present invention; FIG.
图11是根据本发明实施例的操作、管理和维护OAM报文处理装置二的结构框图;11 is a structural block diagram of an operation, management, and maintenance OAM message processing apparatus 2 according to an embodiment of the present invention;
图12是根据本发明实施例的操作、管理和维护OAM报文处理装置二的优选结构框图;FIG. 12 is a block diagram showing a preferred structure of an operation, management, and maintenance OAM message processing apparatus 2 according to an embodiment of the present invention; FIG.
图13是根据本发明实施例的UDP协议承载SFC OAM报文的报文格式示意图;FIG. 13 is a schematic diagram of a packet format of a UDP protocol carrying an SFC OAM packet according to an embodiment of the present invention;
图14是根据本发明实施例的Overlay封装后的基于UDP承载后的完整SFC OAM报文格式示意图;14 is a schematic diagram of a format of a complete SFC OAM packet based on a UDP bearer after an Overlay encapsulation according to an embodiment of the present invention;
图15是根据本发明实施例的实现SFC Ping功能的报文格式示意图;FIG. 15 is a schematic diagram of a packet format for implementing an SFC ping function according to an embodiment of the present invention; FIG.
图16是根据本发明实施例的实现SFC Trace功能的示意图。 FIG. 16 is a schematic diagram of implementing an SFC Trace function according to an embodiment of the present invention.
具体实施方式detailed description
下文中将参考附图并结合实施例来详细说明本发明。需要说明的是,在不冲突的情况下,本申请中的实施例及实施例中的特征可以相互组合。The invention will be described in detail below with reference to the drawings in conjunction with the embodiments. It should be noted that the embodiments in the present application and the features in the embodiments may be combined with each other without conflict.
在本实施例中提供了一种操作、管理和维护OAM报文处理方法,图7是根据本发明实施例的操作、管理和维护OAM报文处理方法一的流程图,如图7所示,该流程包括如下步骤:In this embodiment, a method for processing, managing, and maintaining an OAM packet is provided. FIG. 7 is a flowchart of a method for processing, managing, and maintaining an OAM packet according to an embodiment of the present invention. The process includes the following steps:
步骤S702,源端业务节点确定用于在业务功能链SFC上发送的OAM报文,其中,OAM报文包括:载荷Payload、OAM报文头、业务功能报文头,其中,OAM报文采用预定的SFC OAM网络端口号承载;Step S702, the source service node determines an OAM message to be sent on the service function chain SFC, where the OAM message includes: a payload, a OAM packet header, and a service function packet header, where the OAM packet is scheduled. SFC OAM network port number bearer;
步骤S704,源端业务节点将承载在预定的SFC OAM网络端口号上的OAM报文发送给SFC上的目的业务节点处理。Step S704: The source service node sends the OAM packet that is carried on the predetermined SFC OAM network port number to the destination service node on the SFC for processing.
通过上述步骤,确定一种OAM报文,采用预定的SFC OAM网络端口号承载该OAM报文,并将确定的该OAM报文发送给目的业务节点,解决了相关技术中存在无法确定SFC OAM报文内容,以及基于什么协议承载该报文的问题,进而达到了确定了一种完整SFC OAM报文,以及提高SFC OAM扩展性的效果。Through the foregoing steps, an OAM packet is determined, and the OAM packet is carried by the predetermined SFC OAM network port number, and the determined OAM packet is sent to the destination service node, and the SFC OAM report cannot be determined in the related technology. The content of the text, and the question of what protocol is used to carry the message, achieves the effect of determining a complete SFC OAM message and improving the scalability of the SFC OAM.
上述OAM报文可以采用多种格式,例如,可以采用以下格式至少之一:Payload、OAM报文头、业务功能报文头,其中,SFC OAM类型承载于OAM报文头中;Payload、OAM报文头、业务功能报文头,其中,SFC OAM类型承载于业务功能报文头中。The foregoing OAM packet may be in a plurality of formats, for example, at least one of the following formats: a Payload, an OAM packet header, and a service function packet header, where the SFC OAM type is carried in the OAM packet header; the Payload and the OAM packet The header of the service function is the header of the service function. The SFC OAM type is carried in the service function header.
需要说明的是,承载该SFC OAM报文的协议可以为多种,下面以UDP协议为例进行说明。基于UDP协议承载的SFC OAM报文可以包括以下信息至少之一:UDP源端口号、用于标识SFC OAM报文端口号的UDP目的端口号、用于标识SFC OAM报文的版本号的版本信息、用于标识SFC OAM报文的报文类型信息、用于标识响应报文的响应模式信息、用于标识故障原因的返回编码信息、用于标识报文发送频率的频率信息、用于请求报文随机生成的信息、用于标识报文发送的时间点的信息、用于标识报文接收的时间点的信息、用于请求报文中待扩展的TLV,或者用于响应报文中标识获取的业务功能链路信息的TLV、用于标识填充字段的填充字段信息。It should be noted that the protocol for carrying the SFC OAM packet may be multiple. The following uses the UDP protocol as an example. The SFC OAM packet carried by the UDP protocol may include at least one of the following: a UDP source port number, a UDP destination port number for identifying the SFC OAM packet port number, and version information for identifying the version number of the SFC OAM packet. The packet type information used to identify the SFC OAM packet, the response mode information used to identify the response packet, the return coding information used to identify the cause of the fault, the frequency information used to identify the frequency of the packet transmission, and the request message The information randomly generated by the text, the information used to identify the time point of the message transmission, the information used to identify the time point of the message reception, the TLV to be used in the request message, or the identifier in the response message. The TLV of the service function link information, and the padding field information used to identify the padding field.
优选地,在将承载在预定的SFC OAM网络端口号上的OAM报文发送给SFC上的目的业务节点处理之后,还可以依据SFC OAM报文携带的响应模式不同,接收到源端业务节点发送的不同的响应报文,下面举例说明。 Preferably, after the OAM packet carried on the predetermined SFC OAM network port number is sent to the destination service node on the SFC, the source service node may be sent according to the response mode carried in the SFC OAM packet. Different response messages, as exemplified below.
例如,在SFC OAM报文携带的响应模式为IPv4/IPv6用户数据协议UDP报文时,接收到目的业务节点不携带业务功能报文头的IPv4/IPv6UDP报文,其中,IPv4/IPv6UDP报文中携带有对OAM报文处理后获得的处理结果;又例如,在SFC OAM报文携带的响应模式为SFC OAM UDP报文时,接收到目的业务节点发送的SFC OAM UDP报文,其中,SFC OAM UDP报文携带有对OAM报文处理后获得的处理结果。而在SFC OAM报文携带的响应模式为不回复时,即接收不到目的业务节点发送的响应报文。For example, when the response mode carried in the SFC OAM packet is the IPv4/IPv6 user data protocol UDP packet, the IPv4/IPv6 UDP packet of the service function packet header is not received by the destination service node, where the IPv4/IPv6 UDP packet is received. The SFC OAM UDP packet sent by the destination service node is received, and the SFC OAM UDP packet sent by the destination service node is received, for example, when the SFC OAM packet carries the SFC OAM UDP packet. The UDP packet carries the processing result obtained after processing the OAM packet. When the response mode carried in the SFC OAM packet is not replied, the response packet sent by the destination service node is not received.
需要说明的是,上述源端业务节点为业务分类器或者业务功能链上的其中一个业务节点。It should be noted that the source service node is a service classifier or one of the service nodes on the service function chain.
在本实施例中,还提供了一种操作、管理和维护OAM报文处理方法,图8是根据本发明实施例的操作、管理和维护OAM报文处理方法二的流程图,如图8所示,该流程包括如下步骤:In this embodiment, a method for processing, managing, and maintaining an OAM packet is provided. FIG. 8 is a flowchart of a second method for processing, managing, and maintaining an OAM packet according to an embodiment of the present invention. The process includes the following steps:
步骤S802,目的业务节点接收在业务功能链SFC上发送的OAM报文,其中,OAM报文包括:载荷Payload、OAM报文头、业务功能报文头,其中,OAM报文采用预定的SFC OAM网络端口号承载;In step S802, the destination service node receives the OAM packet sent by the service function chain SFC, where the OAM packet includes: a payload Payload, an OAM packet header, and a service function packet header, where the OAM packet adopts a predetermined SFC OAM. Network port number bearer;
步骤S804,目的业务节点对接收的OAM报文进行处理。Step S804: The destination service node processes the received OAM packet.
通过上述步骤,通过接收SFC上发送的采用预定的SFC OAM网络端口号承载的该OAM报文,并对接收的该OAM报文进行处理,解决了相关技术中存在无法确定SFC OAM报文内容,以及基于什么协议承载该报文的问题,进而达到了确定了一种完整SFC OAM报文,以及提高SFC OAM扩展性的效果。Through the foregoing steps, the OAM packet sent by the SFC OAM network port number sent by the SFC is received, and the received OAM packet is processed, and the SFC OAM packet content cannot be determined in the related art. And the problem of what protocol is used to carry the message, thereby achieving the effect of determining a complete SFC OAM message and improving the scalability of the SFC OAM.
需要说明的是,在接收SFC上发送的采用预定的SFC OAM网络端口号承载的该OAM报文后,对该OAM报文进行解封装后,解析报文中的端口号发现是SFC OAM报文,对该OAM报文进行处理。It is to be noted that, after receiving the OAM packet that is sent by the SFC and using the predetermined SFC OAM network port number, the OAM packet is decapsulated, and the port number in the packet is found to be an SFC OAM packet. The OAM packet is processed.
其中,OAM报文可以采用多种格式,例如,可以采用以下格式至少之一:Payload、OAM报文头、业务功能报文头,其中,SFC OAM类型承载于OAM报文头中;Payload、OAM报文头、业务功能报文头,其中,SFC OAM类型承载于业务功能报文头中。The OAM packet can be in multiple formats, for example, at least one of the following formats: a Payload, an OAM packet header, and a service function packet header, where the SFC OAM type is carried in the OAM packet header; Payload, OAM A packet header and a service function packet header, where the SFC OAM type is carried in the service function packet header.
对应地,该SFC OAM报文可以承载于多种协议,下面以承载于UDP协议进行说明。例如,基于UPD协议承载的SFC OAM报文可以包括以下信息至少之一:UDP源端口号、用于标识SFC OAM报文端口号的UDP目的端口号、用于标识SFC OAM 报文的版本号的版本信息、用于标识SFC OAM报文的报文类型信息、用于标识响应报文的响应模式信息、用于标识故障原因的返回编码信息、用于标识报文发送频率的频率信息、用于请求报文随机生成的信息、用于标识报文发送的时间点的信息、用于标识报文接收的时间点的信息、用于请求报文中待扩展的TLV,或者用于响应报文中标识获取的业务功能链路信息的TLV、用于标识填充字段的填充字段信息。Correspondingly, the SFC OAM packet can be carried in multiple protocols, and is described below by being carried in the UDP protocol. For example, the SFC OAM packet that is carried by the UPD protocol may include at least one of the following: a UDP source port number, a UDP destination port number used to identify the SFC OAM packet port number, and is used to identify the SFC OAM. The version information of the version number of the packet, the packet type information used to identify the SFC OAM packet, the response mode information used to identify the response packet, the return encoding information used to identify the cause of the fault, and the frequency of sending the packet. Frequency information, information for requesting packet random generation, information for identifying the time point at which the message is sent, information for identifying the time point at which the message is received, for requesting the TLV to be extended in the message, or A TLV for identifying the service function link information obtained in the response message, and padding field information for identifying the padding field.
优选地,在目的业务节点对接收的OAM报文进行处理之后,还可以依据SFC OAM报文携带的响应模式不同,向源端业务节点发送响应报文,下面举例说明。例如,在SFC OAM报文携带的响应模式为IPv4/IPv6用户数据协议UDP报文时,通过不携带业务功能报文头的IPv4/IPv6UDP报文将对OAM报文处理后的处理结果发送给发送OAM报文的源端业务节点或者下一跳业务节点;又例如,在SFC OAM报文携带的响应模式为SFC OAM UDP报文时,通过SFC OAM UDP报文将对OAM报文处理后的处理结果发送给发送OAM报文的源端业务节点或者下一跳业务节点。而在而在SFC OAM报文携带的响应模式为不回复时,目的业务节点收到此OAM报文后,不用发送响应报文。Preferably, after the destination service node processes the received OAM packet, the response packet sent by the SFC OAM packet may be sent to the source service node according to the response mode. For example, when the response mode carried in the SFC OAM packet is the IPv4/IPv6 user data protocol UDP packet, the processing result of the OAM packet processing is sent to the IPv4/IPv6 UDP packet without the service function packet header. The source service node or the next hop service node of the OAM packet; for example, when the response mode carried in the SFC OAM packet is SFC OAM UDP packet, the OAM packet processing is processed through the SFC OAM UDP packet. The result is sent to the source service node or the next hop service node that sends the OAM message. On the other hand, when the response mode carried in the SFC OAM packet is not replied, the destination service node does not need to send a response packet after receiving the OAM packet.
优选地,目的业务节点为业务功能链上除源端业务节点之外的其余一个业务节点或多个业务节点的组合。Preferably, the destination service node is a combination of the other service node or the plurality of service nodes except the source service node on the service function chain.
在本实施例中还提供了一种操作、管理和维护OAM报文处理装置,该装置用于实现上述实施例及优选实施方式,已经进行过说明的不再赘述。如以下所使用的,术语“模块”可以实现预定功能的软件和/或硬件的组合。尽管以下实施例所描述的装置较佳地以软件来实现,但是硬件,或者软件和硬件的组合的实现也是可能并被构想的。In this embodiment, an OAM packet processing device is also provided, which is used to implement the foregoing embodiments and preferred embodiments, and details are not described herein. As used below, the term "module" may implement a combination of software and/or hardware of a predetermined function. Although the apparatus described in the following embodiments is preferably implemented in software, hardware, or a combination of software and hardware, is also possible and contemplated.
图9是根据本发明实施例的操作、管理和维护OAM报文处理装置一的结构框图,如图9所示,该装置位于源端业务节点中,包括:确定模块92和第一发送模块94,下面对该装置进行说明。FIG. 9 is a structural block diagram of an apparatus for processing, managing, and maintaining an OAM packet according to an embodiment of the present invention. As shown in FIG. 9, the apparatus is located in a source service node, and includes: a determining module 92 and a first sending module 94. The device will be described below.
确定模块92,设置为确定用于在业务功能链SFC上发送的OAM报文,其中,OAM报文包括:载荷Payload、OAM报文头、业务功能报文头,其中,OAM报文采用预定的SFC OAM网络端口号承载;第一发送模块94,连接至上述确定模块92,设置为将承载在预定的SFC OAM网络端口号上的OAM报文发送给SFC上的目的业务节点处理。The determining module 92 is configured to determine an OAM packet to be sent on the service function chain SFC, where the OAM packet includes: a payload Payload, an OAM packet header, and a service function packet header, where the OAM packet adopts a predetermined The SFC OAM network port number bearer; the first sending module 94 is connected to the determining module 92, and is configured to send the OAM packet that is carried on the predetermined SFC OAM network port number to the destination service node on the SFC for processing.
其中,OAM报文可以采用多种格式,例如,可以采用以下格式至少之一:Payload、OAM报文头、业务功能报文头,其中,SFC OAM类型承载于OAM报文头中;Payload、OAM报文头、业务功能报文头,其中,SFC OAM类型承载于业务功能报文头中。 The OAM packet can be in multiple formats, for example, at least one of the following formats: a Payload, an OAM packet header, and a service function packet header, where the SFC OAM type is carried in the OAM packet header; Payload, OAM A packet header and a service function packet header, where the SFC OAM type is carried in the service function packet header.
优选地,基于UDP协议承载的SFC OAM报文可以包括以下信息至少之一:UDP源端口号、用于标识SFC OAM报文端口号的UDP目的端口号、用于标识SFC OAM报文的版本号的版本信息、用于标识SFC OAM报文的报文类型信息、用于标识响应报文的响应模式信息、用于标识故障原因的返回编码信息、用于标识报文发送频率的频率信息、用于请求报文随机生成的信息、用于标识报文发送的时间点的信息、用于标识报文接收的时间点的信息、用于请求报文中待扩展的TLV,或者用于响应报文中标识获取的业务功能链路信息的TLV、用于标识填充字段的填充字段信息。Preferably, the SFC OAM packet carried by the UDP protocol may include at least one of the following: a UDP source port number, a UDP destination port number used to identify the SFC OAM packet port number, and a version number used to identify the SFC OAM packet. The version information, the packet type information used to identify the SFC OAM packet, the response mode information used to identify the response packet, the return encoding information used to identify the cause of the fault, and the frequency information used to identify the frequency of the packet transmission. Information randomly generated in the request packet, information indicating the time point at which the packet is sent, information indicating the time point at which the packet is received, TLV to be used in the request packet, or response message A TLV identifying the acquired service function link information, and padding field information for identifying the padding field.
图10是根据本发明实施例的操作、管理和维护OAM报文处理装置一的优选结构框图,如图10所示,该装置除包括图9所示的所有模块外,还包括以下至少之一:第一接收模块102、第二接收模块104,下面对该装置进行说明。FIG. 10 is a block diagram showing a preferred structure of an OAM packet processing apparatus according to an embodiment of the present invention. As shown in FIG. 10, the apparatus includes at least one of the following, in addition to all the modules shown in FIG. The first receiving module 102 and the second receiving module 104 are described below.
第一接收模块102,连接至上述第一发送模块94,设置为在SFC OAM报文携带的响应模式为IPv4/IPv6用户数据协议UDP报文时,接收到目的业务节点不携带业务功能报文头的IPv4/IPv6UDP报文,其中,IPv4/IPv6UDP报文中携带有对OAM报文处理后获得的处理结果;第二接收模块104,连接至上述第一发送模块94,设置为在SFC OAM报文携带的响应模式为SFC OAM UDP报文时,接收到目的业务节点发送的SFC OAM UDP报文,其中,SFC OAM UDP报文携带有对OAM报文处理后获得的处理结果。The first receiving module 102 is connected to the first sending module 94, and is configured to receive the service function node without receiving the service function node when the response mode carried in the SFC OAM packet is the IPv4/IPv6 user data protocol UDP packet. The IPv4/IPv6 UDP packet, wherein the IPv4/IPv6 UDP packet carries the processing result obtained after processing the OAM packet; the second receiving module 104 is connected to the first sending module 94 and configured to be in the SFC OAM packet. When the SFC OAM UDP packet is received, the SFC OAM UDP packet is received by the destination service node. The SFC OAM UDP packet carries the processing result obtained after the OAM packet is processed.
优选地,源端业务节点为业务分类器或者业务功能链上的其中一个业务节点。Preferably, the source service node is a service classifier or one of the service nodes on the service function chain.
图11是根据本发明实施例的操作、管理和维护OAM报文处理装置二的结构框图,如图11所示,该装置位于目的业务节点中,包括:第三接收模块112和处理模块114,下面对该装置进行说明。11 is a structural block diagram of an operation, management, and maintenance OAM packet processing apparatus 2 according to an embodiment of the present invention. As shown in FIG. 11, the apparatus is located in a destination service node, and includes: a third receiving module 112 and a processing module 114. The device will be described below.
第三接收模块112,设置为接收在业务功能链SFC上发送的OAM报文,其中,OAM报文包括:载荷Payload、OAM报文头、业务功能报文头,其中,OAM报文采用预定的SFC OAM网络端口号承载;处理模块114,连接至上述第三接收模块112,设置为对接收的OAM报文进行处理。The third receiving module 112 is configured to receive the OAM packet sent by the service function chain SFC, where the OAM packet includes: a payload Payload, an OAM packet header, and a service function packet header, where the OAM packet adopts a predetermined The SFC OAM network port number bearer; the processing module 114 is connected to the third receiving module 112, and configured to process the received OAM message.
优选地,上述OAM报文可以采用以下格式至少之一:Payload、OAM报文头、业务功能报文头,其中,SFC OAM类型承载于OAM报文头中;Payload、OAM报文头、业务功能报文头,其中,SFC OAM类型承载于业务功能报文头中。Preferably, the OAM packet may be in at least one of the following formats: a Payload, an OAM packet header, and a service function packet header, where the SFC OAM type is carried in the OAM packet header; the Payload, the OAM packet header, and the service function. The packet header, in which the SFC OAM type is carried in the service function packet header.
优选地,基于UDP协议承载的SFC OAM报文包括以下信息至少之一:UDP源端口号、用于标识SFC OAM报文端口号的UDP目的端口号、用于标识SFC OAM报 文的版本号的版本信息、用于标识SFC OAM报文的报文类型信息、用于标识响应报文的响应模式信息、用于标识故障原因的返回编码信息、用于标识报文发送频率的频率信息、用于请求报文随机生成的信息、用于标识报文发送的时间点的信息、用于标识报文接收的时间点的信息、用于请求报文中待扩展的TLV,或者用于响应报文中标识获取的业务功能链路信息的TLV、用于标识填充字段的填充字段信息。Preferably, the SFC OAM packet carried by the UDP protocol includes at least one of the following: a UDP source port number, a UDP destination port number used to identify the SFC OAM packet port number, and is used to identify the SFC OAM packet. The version information of the version number, the packet type information used to identify the SFC OAM packet, the response mode information used to identify the response packet, the return encoding information used to identify the cause of the fault, and the frequency used to identify the packet transmission frequency. The frequency information, the information used to randomly generate the request packet, the information used to identify the time point at which the message is sent, the information used to identify the time point of the message reception, the TLV to be used in the request message, or A TLV for identifying the obtained service function link information in the response message, and padding field information for identifying the padding field.
图12是根据本发明实施例的操作、管理和维护OAM报文处理装置二的优选结构框图,如图12所示,该装置除包括图11所示的所有模块外,还包括以下至少之一:第二发送模块122、第三发送模块124,下面对该装置进行说明。FIG. 12 is a block diagram showing a preferred structure of an operation, management, and maintenance OAM message processing apparatus 2 according to an embodiment of the present invention. As shown in FIG. 12, the apparatus includes at least one of the following, in addition to all the modules shown in FIG. The second transmitting module 122 and the third transmitting module 124 are described below.
第二发送模块122,连接至上述处理模块114,设置为在SFC OAM报文携带的响应模式为IPv4/IPv6用户数据协议UDP报文时,通过不携带业务功能报文头的IPv4/IPv6UDP报文将对OAM报文处理后的处理结果发送给发送OAM报文的源端业务节点或者下一跳业务节点;第三发送模块124,连接至上述处理模块114,设置为在SFC OAM报文携带的响应模式为SFC OAM UDP报文时,通过SFC OAM UDP报文将对OAM报文处理后的处理结果发送给发送OAM报文的源端业务节点或者下一跳业务节点。The second sending module 122 is connected to the processing module 114, and is configured to pass the IPv4/IPv6 UDP packet that does not carry the service function packet header when the response mode carried in the SFC OAM packet is the IPv4/IPv6 user data protocol UDP packet. The processing result of the OAM packet processing is sent to the source service node or the next hop service node that sends the OAM packet. The third sending module 124 is connected to the processing module 114 and configured to be carried in the SFC OAM packet. When the response mode is SFC OAM UDP packet, the SFC OAM UDP packet is used to send the OAM packet processing result to the source service node or the next hop service node that sends the OAM packet.
优选地,目的业务节点为业务功能链上除源端业务节点之外的其余一个业务节点或多个业务节点的组合。Preferably, the destination service node is a combination of the other service node or the plurality of service nodes except the source service node on the service function chain.
针对相关技术中的上述问题,在本实施例中,提供了一种承载业务功能链操作、管理和维护报文的方法。通过定义一个新的UDP/TCP端口号,用来承载SFC OAM的各种消息;以下以承载的协议为UDP协议为例进行说明。图13是根据本发明实施例的UDP协议承载SFC OAM报文的报文格式示意图,如图13所示:For the above problems in the related art, in this embodiment, a method for carrying a service chain operation, management, and maintenance message is provided. By defining a new UDP/TCP port number, it is used to carry various messages of the SFC OAM. The following uses the bearer protocol as the UDP protocol as an example. FIG. 13 is a schematic diagram of a packet format of a UDP protocol carrying an SFC OAM packet according to an embodiment of the present invention, as shown in FIG.
Source Port:标识UDP源端口号;Source Port: identifies the UDP source port number.
Destination Port:标识UDP目的端口号,在本实施例中,定义一个新的端口号,用来承载SFC OAM报文;Destination Port: identifies the UDP destination port number. In this embodiment, a new port number is defined to carry the SFC OAM packet.
Version Number:标识SFC OAM报文的版本号;Version Number: identifies the version number of the SFC OAM packet.
Message Type:标识SFC OAM报文类型,主要有Ping Request报文、Ping Reply报文、连通性Request报文、连通性Reply报文等;Message Type: identifies the SFC OAM packet type, including the Ping Request packet, the ping reply packet, the connectivity request packet, and the connectivity Reply packet.
Reply Mode:标识响应报文的响应模式,响应报文可以通过普通IPv4/IPv6UDP报文应答、或通过业务功能路径SFP发送报文应答;等等; Reply Mode: identifies the response mode of the response packet. The response packet can respond with a normal IPv4/IPv6UDP packet or send a message response through the service function path SFP.
Return Code:响应报文中携带,标识故障原因(例如,请求报文错误、携带不识别的TLV、业务功能运行异常等);请求报文中该字段为0;Return Code: The response packet carries the number of the fault (for example, the request packet is incorrect, the TLV is not recognized, the service function is abnormal, etc.); the field in the request packet is 0;
Frequency:对于周期性的SFC OAM报文,该字段用于标识报文发送的频率;对于主动触发的SFC OAM报文(Ping或Trace),该字段为0;Frequency: For a periodic SFC OAM packet, this field is used to identify the frequency of packet transmission. For an actively triggered SFC OAM packet (Ping or Trace), this field is 0.
Sender’s Handle:请求报文随机生成;响应报文中该字段和请求报文一致;Sender’s Handle: The request message is randomly generated; the field in the response message is consistent with the request message;
Timestamp Sent:标识报文发送的时间点;Timestamp Sent: identifies the time point at which the message is sent.
Timestamp Received:标识报文接收的时间点;Timestamp Received: indicates the time point at which the message is received.
TLV:对于SFC Ping或者SFC Trace,考虑到SFP的信息包含在业务功能头中,并且沿途携带到最后一跳业务节点,故SFC Ping或SFC Trace请求报文中,可以不携带该字段,该字段可选,用于后续扩展;对于SFC Trace的响应报文中,该字段需要将获取的业务功能链路信息或者业务功能链的业务功能相关信息(比如,带宽信息、资源信息、延迟信息等)响应给SFC Trace的发起者,故需要携带该TLV字段,不同的type对应于不同的信息;TLV: For SFC ping or SFC Trace, the SFP information is included in the service function header and is carried to the last hop service node along the path. Therefore, the SFC ping or SFC Trace request packet may not carry the field. Optional, for subsequent extension; in the response packet of the SFC Trace, the field needs to obtain the service function link information or the service function related information of the service function chain (for example, bandwidth information, resource information, delay information, etc.) The TLV field needs to be carried in response to the initiator of the SFC Trace. Different types correspond to different information.
Padding:标识填充字段,满足报文需要的字节要求;Padding: identifies the padding field to meet the byte requirements required by the message;
图14是根据本发明实施例的Overlay封装后的基于UDP承载后的完整SFC OAM报文格式示意图,如图14所示。FIG. 14 is a schematic diagram of a format of a complete SFC OAM packet based on UDP bearer after Overlay encapsulation, as shown in FIG. 14 .
下面将结合附图对本发明实施例进行描述。The embodiments of the present invention will be described below with reference to the accompanying drawings.
实施例1:Example 1:
在本实施例1中,基于SFC Ping功能的实施例的业务功能链包括:SF1--->SF2--->SF3;其中,Overlay网络为IP网络。In the first embodiment, the service function chain of the embodiment based on the SFC ping function includes: SF1 -> SF2 -> SF3; wherein the Overlay network is an IP network.
首先,操作者配置Relay Mode为通过业务功能路径发送响应报文,并从Classifier开始进行该业务功能路径的Ping请求功能,则从Classifier发出的Ping报文格式。图15是根据本发明实施例的实现SFC Ping功能的报文格式示意图,如图15中所示,UDP头中使用的是SFC OAM专用端口号,SFC Ping请求报文中报文类型为请求报文,响应模式如上配置。本实施例中,实现Ping功能包括如下步骤:First, the operator configures the Relay Mode to send a response packet through the service function path, and starts the Ping request function of the service function path from the Classifier, and then the ping packet format sent from the Classifier. Figure 15 is a schematic diagram of a packet format for implementing the SFC ping function according to an embodiment of the present invention. As shown in Figure 15, the SFC OAM dedicated port number is used in the UDP header, and the packet type in the SFC ping request packet is a request packet. Text, the response mode is configured as above. In this embodiment, implementing the Ping function includes the following steps:
101:Classifier发送图15中的OAM报文,转发报文到业务功能路径的第一跳业务节点1; 101: The Classifier sends the OAM packet in Figure 15 and forwards the packet to the first hop service node 1 of the service function path;
102:业务节点1解封装Overlay层,将携带有SFC业务功能头的报文转发给SFF1处理,SFF1判断这是一个OAM Ping协议报文,于是转发给SFC OAM协议模块处理;102: The service node 1 decapsulates the Overlay layer, and forwards the packet carrying the SFC service function header to the SFF1. The SFF1 determines that the message is an OAM ping protocol packet, and then forwards the packet to the SFC OAM protocol module.
103:该SFC OAM协议模块调用第一跳业务功能SF1,检查其是否正常运行,如果是,则将报文转发回给SFF1;103: The SFC OAM protocol module invokes the first hop service function SF1 to check whether it is running normally, and if yes, forwards the packet back to SFF1;
104:SFF1将报文转发给业务节点1,业务节点1对该报文进行Overlay封装,转发该报文到下一跳业务节点2;104: SFF1 forwards the packet to the service node 1, and the service node 1 performs Overlay encapsulation on the packet, and forwards the packet to the next hop service node 2;
105:如果检查第一跳业务功能SF1没有正常运行,则构造Ping响应报文,携带业务功能故障信息;并将该响应报文转发会给SFF1;105: If the first hop service function SF1 is not in normal operation, the ping response message is configured to carry the service function fault information; and the response message is forwarded to SFF1;
106:SFF1将该相应报文转发给业务节点1,业务节点1对该报文进行Overlay封装,转发该报文到Classifier;106: SFF1 forwards the corresponding packet to the service node 1, and the service node 1 performs Overlay encapsulation on the packet, and forwards the packet to the Classifier.
107:业务节点2接收到该报文,先解封装Overlay层,将携带有SFC业务功能头的报文转发给SFF2处理,SFF2判断这是一个OAM协议报文,于是转发给SFC OAM协议模块处理;107: The service node 2 receives the packet, first decapsulates the Overlay layer, and forwards the packet carrying the SFC service function header to the SFF2. The SFF2 determines that the packet is an OAM protocol packet, and then forwards the packet to the SFC OAM protocol module. ;
108:该SFC OAM协议模块调用第二跳业务功能SF2,检查其是否正常运行,如果是,则将报文转发回给SFF2;108: The SFC OAM protocol module invokes the second hop service function SF2 to check whether it is running normally. If yes, the packet is forwarded back to SFF2.
109:SFF2将报文转发给业务节点2,业务节点2对该报文进行Overlay封装,转发该报文到下一跳业务节点3;109: SFF2 forwards the packet to the service node 2, and the service node 2 performs Overlay encapsulation on the packet, and forwards the packet to the next hop service node 3;
110:如果检查第二跳业务功能SF2没有正常运行,则构造Ping响应报文,携带业务功能故障信息;并将该响应报文转发会给SFF2;110: If the second hop service function SF2 is not in normal operation, the ping response message is configured to carry the service function fault information; and the response message is forwarded to the SFF2;
111:SFF2将该相应报文转发给业务节点2,业务节点2对该报文进行Overlay封装,沿着反向的路径转发给业务节点1,然后再转发该报文到Classifier;111: SFF2 forwards the corresponding packet to the service node 2, and the service node 2 performs Overlay encapsulation on the packet, forwards the packet to the service node 1 along the reverse path, and then forwards the packet to the Classifier;
112:业务节点3接收到该报文,先解封装Overlay层,将携带有SFC业务功能头的报文转发给SFF3处理,SFF3判断这是一个OAM协议报文且是业务功能路径的最后一跳,继续转发给SFC OAM协议模块处理;112: The service node 3 receives the packet, first decapsulates the Overlay layer, and forwards the packet carrying the SFC service function header to the SFF3. The SFF3 determines that this is an OAM protocol packet and is the last hop of the service function path. , continue to forward to the SFC OAM protocol module processing;
113:该SFC OAM协议模块调用第三跳业务功能SF3,检查其是否正常运行,如果是,则构造Ping响应报文并将该报文转发回给SFF3;如果不是,也构造Ping响应报文携带故障业务功能故障信息;并将该报文转发回给SFF3; 113: The SFC OAM protocol module invokes the third hop service function SF3 to check whether it is running normally. If yes, construct a Ping response message and forward the message back to SFF3; if not, construct a Ping response message to carry Faulty service function fault information; and forwards the packet back to SFF3;
114:SFF3将报文转发给业务节点3,业务节点3对该报文进行Overlay封装,沿着反向的路径转发给业务节点2和业务节点1,然后再转发该报文到Classifier;114: SFF3 forwards the packet to the service node 3, and the service node 3 performs Overlay encapsulation on the packet, forwards the packet to the service node 2 and the service node 1 along the reverse path, and then forwards the packet to the Classifier;
115:Classifier收到Ping响应报文后,显示给操作者是否Ping成功,如果没有成功,显示给操作者失败原因。115: After receiving the Ping response packet, the Classifier displays to the operator whether the Ping succeeds. If it is not successful, the reason for the operator failure is displayed.
具体实施例2:Specific embodiment 2:
在本实施例中,基于SFC Trace功能的具体实施例的业务功能链包括:SF1--->SF2--->SF3,其中,Overlay网络为IP网络。In this embodiment, the service function chain of the specific embodiment based on the SFC Trace function includes: SF1--->SF2--->SF3, where the Overlay network is an IP network.
首先,操作者配置Relay Mode为通过IP路径发送响应报文,并从Classifier开始进行该业务功能路径的Trace(路径)请求功能,则从Classifier发出的Trace报文格式。图16是根据本发明实施例的实现SFC Trace功能的示意图,如图16中所示,其中,UDP头中使用的是SFC OAM专用端口号,SFC Trace请求报文中报文类型为请求报文,响应模式如上配置;本实施例包括如下步骤:First, the operator configures the Relay Mode to send a response packet through the IP path, and starts the Trace request of the service function path from the Classifier, and then outputs the Trace packet format from the Classifier. FIG. 16 is a schematic diagram of implementing the SFC Trace function according to the embodiment of the present invention, as shown in FIG. 16 , wherein the UDP header uses the SFC OAM dedicated port number, and the SFC Trace request packet has the packet type as the request packet. The response mode is configured as above; the embodiment includes the following steps:
201:Classifier发送图16中OAM报文,设置报文中的TTL字段为1,转发报文到业务功能路径的第一跳业务节点1;201: The Classifier sends the OAM packet in FIG. 16 and sets the TTL field in the packet to 1, and forwards the packet to the first hop service node 1 of the service function path;
202:业务节点1解封装Overlay层,将携带有SFC业务功能头的报文转发给SFF1处理,SFF1判断这是一个OAM Trace协议报文且TTL为1,于是转发给SFC OAM协议模块处理;202: The service node 1 decapsulates the Overlay layer, and forwards the packet carrying the SFC service function header to the SFF1. The SFF1 determines that the packet is an OAM Trace protocol packet and the TTL is 1, and then forwards the packet to the SFC OAM protocol module.
203:该SFC OAM协议模块调用第一跳业务功能SF1,检查其是否正常运行,如果是,则获取SF1的业务信息、资源信息、延迟信息等,封装在响应报文的TLV中,将报文转发回给SFF1;如果不是,也构造响应报文,携带业务功能故障信息,并将报文转发回给SFF1;203: The SFC OAM protocol module invokes the first hop service function SF1 to check whether it is in normal operation. If yes, the service information, the resource information, and the delay information of the SF1 are obtained, and are encapsulated in the TLV of the response packet, and the packet is encapsulated. Forwarded to SFF1; if not, constructs a response packet, carries the service function fault information, and forwards the packet back to SFF1;
204:SFF1将报文转发给业务节点1,业务节点1对该报文进行Overlay封装,沿着IP路径转发给Classifier;204: SFF1 forwards the packet to the service node 1, and the service node 1 performs Overlay encapsulation on the packet, and forwards the packet to the Classifier along the IP path.
205:Classifier收到第一跳业务节点的相应报文,显示给操作者是否Trace成功,如果成功,显示获取到的信息;同时,Classifier构造TTL为2的SFC Trace报文,转发报文到业务功能路径的第二跳业务节点1;发送如果不成功,显示失败原因; 205: The classifier receives the corresponding packet of the first hop service node, and displays the message to the operator whether the trace is successful. If the success is successful, the information is obtained. The classifier constructs the SFC Trace packet with the TTL of 2 and forwards the packet to the service. The second hop service node 1 of the function path; if the transmission is unsuccessful, the reason for the failure is displayed;
206:业务节点1接收到该报文,先解封装Overlay层,将携带有SFC业务功能头的报文转发给SFF1处理,SFF1判断这是一个OAM协议报文,于是转发给SFC OAM协议模块处理;同时,SFF1会将报文中的TTL值减1;206: The service node 1 receives the packet, first decapsulates the Overlay layer, and forwards the packet carrying the SFC service function header to the SFF1. The SFF1 determines that the packet is an OAM protocol packet, and then forwards the packet to the SFC OAM protocol module. At the same time, SFF1 will decrement the TTL value in the message by one;
207:该SFC OAM协议模块调用第一跳业务功能SF1,检查其是否正常运行,如果是,则将报文转发回给SFF1;207: The SFC OAM protocol module invokes the first hop service function SF1 to check whether it is running normally. If yes, the packet is forwarded back to SFF1.
208:SFF1将报文转发给业务节点1,业务节点1对该报文进行Overlay封装,转发该报文到下一跳业务节点2;208: SFF1 forwards the packet to the service node 1, and the service node 1 performs Overlay encapsulation on the packet, and forwards the packet to the next hop service node 2;
209:业务节点2接收到该报文,先解封装Overlay层,将携带有SFC业务功能头的报文转发给SFF2处理,SFF2判断这是一个OAM协议报文且是TTL为1,继续转发给SFC OAM协议模块处理;209: The service node 2 receives the packet, first decapsulates the Overlay layer, and forwards the packet carrying the SFC service function header to the SFF2. The SFF2 determines that the packet is an OAM protocol packet and the TTL is 1. SFC OAM protocol module processing;
210:该SFC OAM协议模块调用第二跳业务功能SF2,检查其是否正常运行,如果是,则获取SF2的业务信息、资源信息、延迟信息等,封装在响应报文的TLV中,将报文转发回给SFF2;如果不是,也构造响应报文,携带业务功能故障信息,并将报文转发回给SFF2;210: The SFC OAM protocol module invokes the second hop service function SF2 to check whether it is running normally. If yes, the service information, the resource information, and the delay information of the SF2 are obtained, and are encapsulated in the TLV of the response packet, and the packet is sent. Forwarding to SFF2; if not, constructing a response packet, carrying the service function fault information, and forwarding the packet back to SFF2;
211:SFF2将报文转发给业务节点2,业务节点2对该报文进行Overlay封装,沿着IP路径转发给Classifier;211: The SFF2 forwards the packet to the service node 2, and the service node 2 performs Overlay encapsulation on the packet, and forwards the packet to the Classifier along the IP path.
212:Classifier收到第二跳业务节点的相应报文,显示给操作者是否Trace成功,如果成功,显示获取到的信息;同时,Classifier构造TTL为3的SFC Trace报文,转发报文到业务功能路径的第二跳业务节点1;发送如果不成功,显示失败原因;212: The classifier receives the corresponding packet of the second hop service node, and displays the message to the operator whether the trace is successful. If the success is successful, the information is obtained. The classifier constructs the SFC Trace packet with the TTL of 3 and forwards the packet to the service. The second hop service node 1 of the function path; if the transmission is unsuccessful, the reason for the failure is displayed;
213:业务节点1接收到该报文,先解封装Overlay层,将携带有SFC业务功能头的报文转发给SFF1处理,SFF1判断这是一个OAM协议报文,于是转发给SFC OAM协议模块处理;同时,SFF1会将报文中的TTL值减1;213: The service node 1 receives the packet, first decapsulates the Overlay layer, and forwards the packet carrying the SFC service function header to the SFF1. The SFF1 determines that the packet is an OAM protocol packet, and then forwards the packet to the SFC OAM protocol module. At the same time, SFF1 will decrement the TTL value in the message by one;
214:该协议模块调用第一跳业务功能SF1,检查其是否正常运行,如果是,则将报文转发回给SFF1;214: The protocol module invokes the first hop service function SF1 to check whether it is running normally, and if yes, forwards the packet back to SFF1;
215:SFF1将报文转发给业务节点1,业务节点1对该报文进行Overlay封装,转发该报文到下一跳业务节点2; 215: SFF1 forwards the packet to the service node 1, and the service node 1 performs Overlay encapsulation on the packet, and forwards the packet to the next hop service node 2;
216:业务节点2接收到该报文,先解封装Overlay层,将携带有SFC业务功能头的报文转发给SFF2处理,SFF2判断这是一个OAM协议报文,于是转发给SFC OAM协议模块处理;同时,SFF2会将报文中的TTL值减1;216: The service node 2 receives the packet, first decapsulates the Overlay layer, and forwards the packet carrying the SFC service function header to the SFF2. The SFF2 determines that the packet is an OAM protocol packet, and then forwards the packet to the SFC OAM protocol module. At the same time, SFF2 will decrement the TTL value in the message by one;
217:该协议模块调用第一跳业务功能SF2,检查其是否正常运行,如果是,则将报文转发回给SFF2;217: The protocol module invokes the first hop service function SF2 to check whether it is running normally. If yes, the packet is forwarded back to SFF2.
218:SFF2将报文转发给业务节点2,业务节点2对该报文进行Overlay封装,转发该报文到下一跳业务节点3;218: SFF2 forwards the packet to the service node 2, and the service node 2 performs Overlay encapsulation on the packet, and forwards the packet to the next hop service node 3;
219:业务节点3接收到该报文,先解封装Overlay层,将携带有SFC业务功能头的报文转发给SFF3处理,SFF3判断这是一个OAM协议报文且是TTL为1,继续转发给SFC OAM协议模块处理;219: The service node 3 receives the packet, first decapsulates the Overlay layer, and forwards the packet carrying the SFC service function header to the SFF3. The SFF3 determines that the packet is an OAM protocol packet and the TTL is 1. SFC OAM protocol module processing;
220:该协议模块调用第三跳业务功能SF3,检查其是否正常运行,如果是,则获取SF3的业务信息、资源信息、延迟信息等,封装在响应报文的TLV中,将报文转发回给SFF3;如果不是,也构造响应报文,携带业务功能故障信息,并将报文转发回给SFF3;220: The protocol module invokes the third hop service function SF3 to check whether it is running normally. If yes, the SF3 service information, resource information, and delay information are obtained, encapsulated in the TLV of the response packet, and the packet is forwarded back. SFF3; if not, construct a response message, carry the service function fault information, and forward the message back to SFF3;
221:SFF3将报文转发给业务节点3,业务节点3对该报文进行Overlay封装,沿着IP路径转发给Classifier;221: SFF3 forwards the packet to the service node 3, and the service node 3 performs Overlay encapsulation on the packet, and forwards the packet to the Classifier along the IP path.
222:Classifier收到第三跳业务节点的相应报文,显示给操作者是否Trace成功,如果成功,显示获取到的信息;发送如果不成功,显示失败原因。222: The classifier receives the corresponding packet of the third hop service node, and displays to the operator whether the trace is successful. If successful, the obtained information is displayed; if the sending is unsuccessful, the reason for the failure is displayed.
显然,本领域的技术人员应该明白,上述的本发明的各模块或各步骤可以用通用的计算装置来实现,它们可以集中在单个的计算装置上,或者分布在多个计算装置所组成的网络上,可选地,它们可以用计算装置可执行的程序代码来实现,从而,可以将它们存储在存储装置中由计算装置来执行,并且在某些情况下,可以以不同于此处的顺序执行所示出或描述的步骤,或者将它们分别制作成各个集成电路模块,或者将它们中的多个模块或步骤制作成单个集成电路模块来实现。这样,本发明不限制于任何特定的硬件和软件结合。It will be apparent to those skilled in the art that the various modules or steps of the present invention described above can be implemented by a general-purpose computing device that can be centralized on a single computing device or distributed across a network of multiple computing devices. Alternatively, they may be implemented by program code executable by the computing device such that they may be stored in the storage device by the computing device and, in some cases, may be different from the order herein. The steps shown or described are performed, or they are separately fabricated into individual integrated circuit modules, or a plurality of modules or steps thereof are fabricated as a single integrated circuit module. Thus, the invention is not limited to any specific combination of hardware and software.
以上所述仅为本发明的优选实施例而已,并不用于限制本发明,对于本领域的技术人员来说,本发明可以有各种更改和变化。凡在本发明的精神和原则之内,所作的任何修改、等同替换、改进等,均应包含在本发明的保护范围之内。 The above description is only the preferred embodiment of the present invention, and is not intended to limit the present invention, and various modifications and changes can be made to the present invention. Any modifications, equivalent substitutions, improvements, etc. made within the spirit and scope of the present invention are intended to be included within the scope of the present invention.
工业实用性Industrial applicability
如上所述,本发明实施例提供一种操作、管理和维护OAM报文处理方法及装置,解决了相关技术中存在无法确定SFC OAM报文内容,以及基于什么协议承载该报文的问题,进而达到了确定了一种完整SFC OAM报文,以及提高SFC OAM扩展性的效果。 As described above, the embodiment of the present invention provides a method and an apparatus for processing, managing, and maintaining an OAM packet, and solves the problem that the SFC OAM packet content cannot be determined in the related art, and the protocol is carried based on the protocol. Achieved a complete SFC OAM message and improved SFC OAM scalability.

Claims (20)

  1. 一种操作、管理和维护OAM报文处理方法,包括:An OAM packet processing method for operating, managing, and maintaining, including:
    源端业务节点确定用于在业务功能链SFC上发送的OAM报文,其中,所述OAM报文包括:载荷Payload、OAM报文头、业务功能报文头,其中,所述OAM报文采用预定的SFC OAM网络端口号承载;The source service node determines an OAM message to be sent on the service function chain SFC, where the OAM message includes: a payload Payload, an OAM packet header, and a service function packet header, where the OAM packet is adopted. The predetermined SFC OAM network port number bearer;
    所述源端业务节点将承载在所述预定的SFC OAM网络端口号上的所述OAM报文发送给所述SFC上的目的业务节点处理。The source service node sends the OAM packet that is carried on the predetermined SFC OAM network port number to the destination service node on the SFC for processing.
  2. 根据权利要求1所述的方法,其中,所述OAM报文采用以下格式至少之一:The method according to claim 1, wherein the OAM message adopts at least one of the following formats:
    Payload、OAM报文头、业务功能报文头,其中,SFC OAM类型承载于所述OAM报文头中;a payload, an OAM packet header, and a service function packet header, where the SFC OAM type is carried in the OAM packet header;
    Payload、OAM报文头、业务功能报文头,其中,SFC OAM类型承载于所述业务功能报文头中。The Payload, the OAM packet header, and the service function packet header, where the SFC OAM type is carried in the service function packet header.
  3. 根据权利要求1所述的方法,其中,基于UDP协议承载的SFC OAM报文包括以下信息至少之一:The method according to claim 1, wherein the SFC OAM message carried based on the UDP protocol comprises at least one of the following information:
    UDP源端口号、用于标识SFC OAM报文端口号的UDP目的端口号、用于标识SFC OAM报文的版本号的版本信息、用于标识SFC OAM报文的报文类型信息、用于标识响应报文的响应模式信息、用于标识故障原因的返回编码信息、用于标识报文发送频率的频率信息、用于请求报文随机生成的信息、用于标识报文发送的时间点的信息、用于标识报文接收的时间点的信息、用于请求报文中待扩展的TLV,或者用于响应报文中标识获取的业务功能链路信息的TLV、用于标识填充字段的填充字段信息。The UDP source port number, the UDP destination port number used to identify the SFC OAM packet port number, the version information used to identify the version number of the SFC OAM packet, and the packet type information used to identify the SFC OAM packet. The response mode information of the response packet, the return encoding information used to identify the cause of the fault, the frequency information used to identify the frequency of sending the packet, the information used to request the random generation of the packet, and the information used to identify the time point at which the packet is sent. The TLV for identifying the time of receiving the packet, the TLV for requesting the extension of the packet, or the TLV for identifying the service function link information obtained in the response packet, and the padding field for identifying the padding field. information.
  4. 根据权利要求3所述的方法,其中,在将承载在所述预定的SFC OAM网络端口号上的所述OAM报文发送给所述SFC上的目的业务节点处理之后,还包括:The method of claim 3, wherein after the sending of the OAM message carried on the predetermined SFC OAM network port number to the destination service node on the SFC, the method further comprises:
    在所述SFC OAM报文携带的响应模式为IPv4/IPv6用户数据协议UDP报文时,接收到所述目的业务节点不携带业务功能报文头的IPv4/IPv6 UDP报文,其中,所述IPv4/IPv6 UDP报文中携带有对所述OAM报文处理后获得的处理结果; When the response mode carried in the SFC OAM packet is an IPv4/IPv6 user data protocol UDP packet, the IPv4/IPv6 UDP packet that does not carry the service function packet header is received by the destination service node, where the IPv4 The IPv6 UDP packet carries the processing result obtained after processing the OAM packet.
    在所述SFC OAM报文携带的响应模式为SFC OAM UDP报文时,接收到所述目的业务节点发送的SFC OAM UDP报文,其中,所述SFC OAM UDP报文携带有对所述OAM报文处理后获得的处理结果。Receiving, by the SFC OAM UDP packet, the SFC OAM UDP packet sent by the destination service node, where the SFC OAM UDP packet carries the OAM packet The processing result obtained after the processing.
  5. 根据权利要求1至4中任一项所述的方法,其中,The method according to any one of claims 1 to 4, wherein
    所述源端业务节点为业务分类器或者业务功能链上的其中一个业务节点。The source service node is a service classifier or one of the service nodes on the service function chain.
  6. 一种操作、管理和维护OAM报文处理方法,包括:An OAM packet processing method for operating, managing, and maintaining, including:
    目的业务节点接收在业务功能链SFC上发送的OAM报文,其中,所述OAM报文包括:载荷Payload、OAM报文头、业务功能报文头,其中,OAM报文采用预定的SFC OAM网络端口号承载;The destination service node receives the OAM message sent by the service function chain SFC, where the OAM message includes: a payload Payload, an OAM packet header, and a service function packet header, where the OAM packet uses a predetermined SFC OAM network. Port number bearer;
    所述目的业务节点对接收的所述OAM报文进行处理。The destination service node processes the received OAM packet.
  7. 根据权利要求6所述的方法,其中,所述OAM报文采用以下格式至少之一:The method according to claim 6, wherein the OAM message adopts at least one of the following formats:
    Payload、OAM报文头、业务功能报文头,其中,SFC OAM类型承载于所述OAM报文头中;a payload, an OAM packet header, and a service function packet header, where the SFC OAM type is carried in the OAM packet header;
    Payload、OAM报文头、业务功能报文头,其中,SFC OAM类型承载于所述业务功能报文头中。The Payload, the OAM packet header, and the service function packet header, where the SFC OAM type is carried in the service function packet header.
  8. 根据权利要求6所述的方法,其中,基于UDP协议承载的SFC OAM报文包括以下信息至少之一:The method according to claim 6, wherein the SFC OAM message carried based on the UDP protocol comprises at least one of the following information:
    UDP源端口号、用于标识SFC OAM报文端口号的UDP目的端口号、用于标识SFC OAM报文的版本号的版本信息、用于标识SFC OAM报文的报文类型信息、用于标识响应报文的响应模式信息、用于标识故障原因的返回编码信息、用于标识报文发送频率的频率信息、用于请求报文随机生成的信息、用于标识报文发送的时间点的信息、用于标识报文接收的时间点的信息、用于请求报文中待扩展的TLV,或者用于响应报文中标识获取的业务功能链路信息的TLV、用于标识填充字段的填充字段信息。The UDP source port number, the UDP destination port number used to identify the SFC OAM packet port number, the version information used to identify the version number of the SFC OAM packet, and the packet type information used to identify the SFC OAM packet. The response mode information of the response packet, the return encoding information used to identify the cause of the fault, the frequency information used to identify the frequency of sending the packet, the information used to request the random generation of the packet, and the information used to identify the time point at which the packet is sent. The TLV for identifying the time of receiving the packet, the TLV for requesting the extension of the packet, or the TLV for identifying the service function link information obtained in the response packet, and the padding field for identifying the padding field. information.
  9. 根据权利要求6所述的方法,其中,在所述目的业务节点对接收的所述OAM报文进行处理之后,还包括:The method according to claim 6, wherein after the destination service node processes the received OAM packet, the method further includes:
    在所述SFC OAM报文携带的响应模式为IPv4/IPv6用户数据协议UDP报文时,通过不携带业务功能报文头的IPv4/IPv6 UDP报文将对所述OAM报文 处理后的处理结果发送给发送所述OAM报文的源端业务节点或者下一跳业务节点;When the response mode carried in the SFC OAM packet is an IPv4/IPv6 user data protocol UDP packet, the OAM packet is sent through the IPv4/IPv6 UDP packet that does not carry the service function packet header. The processed result is sent to the source service node or the next hop service node that sends the OAM message;
    在所述SFC OAM报文携带的响应模式为SFC OAM UDP报文时,通过所述SFC OAM UDP报文将对所述OAM报文处理后的处理结果发送给发送所述OAM报文的源端业务节点或者下一跳业务节点。When the response mode carried in the SFC OAM packet is an SFC OAM UDP packet, the processing result of the OAM packet processing is sent to the source end of the OAM packet by using the SFC OAM UDP packet. Service node or next hop service node.
  10. 根据权利要求6至9中任一项所述的方法,其中,The method according to any one of claims 6 to 9, wherein
    所述目的业务节点为业务功能链上除所述源端业务节点之外的其余一个业务节点或多个业务节点的组合。The destination service node is a combination of the other service node or multiple service nodes except the source service node on the service function chain.
  11. 一种操作、管理和维护OAM报文处理装置,位于源端业务节点中,包括:An operation, management, and maintenance OAM packet processing device is located in a source service node, and includes:
    确定模块,设置为确定用于在业务功能链SFC上发送的OAM报文,其中,所述OAM报文包括:载荷Payload、OAM报文头、业务功能报文头,其中,所述OAM报文采用预定的SFC OAM网络端口号承载;a determining module, configured to determine an OAM packet to be sent on the service function chain SFC, where the OAM packet includes: a payload Payload, an OAM packet header, and a service function packet header, where the OAM packet Hosted by a predetermined SFC OAM network port number;
    第一发送模块,设置为将承载在所述预定的SFC OAM网络端口号上的所述OAM报文发送给所述SFC上的目的业务节点处理。The first sending module is configured to send the OAM packet that is carried on the predetermined SFC OAM network port number to the destination service node on the SFC for processing.
  12. 根据权利要求11所述的装置,其中,所述OAM报文采用以下格式至少之一:The apparatus according to claim 11, wherein the OAM message adopts at least one of the following formats:
    Payload、OAM报文头、业务功能报文头,其中,SFC OAM类型承载于所述OAM报文头中;a payload, an OAM packet header, and a service function packet header, where the SFC OAM type is carried in the OAM packet header;
    Payload、OAM报文头、业务功能报文头,其中,SFC OAM类型承载于所述业务功能报文头中。The Payload, the OAM packet header, and the service function packet header, where the SFC OAM type is carried in the service function packet header.
  13. 根据权利要求11所述的装置,其中,基于UDP协议承载的SFC OAM报文包括以下信息至少之一:The apparatus according to claim 11, wherein the SFC OAM message carried based on the UDP protocol comprises at least one of the following information:
    UDP源端口号、用于标识SFC OAM报文端口号的UDP目的端口号、用于标识SFC OAM报文的版本号的版本信息、用于标识SFC OAM报文的报文类型信息、用于标识响应报文的响应模式信息、用于标识故障原因的返回编码信息、用于标识报文发送频率的频率信息、用于请求报文随机生成的信息、用于标识报文发送的时间点的信息、用于标识报文接收的时间点的信息、用于请求报文中待扩展的TLV,或者用于响应报文中标识获取的业务功能链路信息的TLV、用于标识填充字段的填充字段信息。The UDP source port number, the UDP destination port number used to identify the SFC OAM packet port number, the version information used to identify the version number of the SFC OAM packet, and the packet type information used to identify the SFC OAM packet. The response mode information of the response packet, the return encoding information used to identify the cause of the fault, the frequency information used to identify the frequency of sending the packet, the information used to request the random generation of the packet, and the information used to identify the time point at which the packet is sent. The TLV for identifying the time of receiving the packet, the TLV for requesting the extension of the packet, or the TLV for identifying the service function link information obtained in the response packet, and the padding field for identifying the padding field. information.
  14. 根据权利要求13所述的装置,其中,还包括: The device according to claim 13, further comprising:
    第一接收模块,设置为在所述SFC OAM报文携带的响应模式为IPv4/IPv6用户数据协议UDP报文时,接收到所述目的业务节点不携带业务功能报文头的IPv4/IPv6 UDP报文,其中,所述IPv4/IPv6 UDP报文中携带有对所述OAM报文处理后获得的处理结果;The first receiving module is configured to: when the response mode carried in the SFC OAM packet is an IPv4/IPv6 user data protocol UDP packet, receive the IPv4/IPv6 UDP packet that the destination service node does not carry the service function packet header. The IPv4/IPv6 UDP packet carries the processing result obtained after processing the OAM packet;
    第二接收模块,设置为在所述SFC OAM报文携带的响应模式为SFC OAM UDP报文时,接收到所述目的业务节点发送的SFC OAM UDP报文,其中,所述SFC OAM UDP报文携带有对所述OAM报文处理后获得的处理结果。The second receiving module is configured to: when the response mode carried in the SFC OAM packet is an SFC OAM UDP packet, receive the SFC OAM UDP packet sent by the destination service node, where the SFC OAM UDP packet Carrying the processing result obtained after processing the OAM packet.
  15. 根据权利要求11至14中任一项所述的装置,A device according to any one of claims 11 to 14,
    所述源端业务节点为业务分类器或者业务功能链上的其中一个业务节点。The source service node is a service classifier or one of the service nodes on the service function chain.
  16. 一种操作、管理和维护OAM报文处理装置,位于目的业务节点中,包括:An operation, management, and maintenance OAM packet processing device is located in a destination service node, and includes:
    第三接收模块,设置为接收在业务功能链SFC上发送的OAM报文,其中,所述OAM报文包括:载荷Payload、OAM报文头、业务功能报文头,其中,OAM报文采用预定的SFC OAM网络端口号承载;The third receiving module is configured to receive the OAM packet sent by the service function chain SFC, where the OAM packet includes: a payload Payload, an OAM packet header, and a service function packet header, where the OAM packet is scheduled SFC OAM network port number bearer;
    处理模块,设置为对接收的所述OAM报文进行处理。The processing module is configured to process the received OAM packet.
  17. 根据权利要求16所述的装置,其中,所述OAM报文采用以下格式至少之一:The apparatus of claim 16, wherein the OAM message is in at least one of the following formats:
    Payload、OAM报文头、业务功能报文头,其中,SFC OAM类型承载于所述OAM报文头中;a payload, an OAM packet header, and a service function packet header, where the SFC OAM type is carried in the OAM packet header;
    Payload、OAM报文头、业务功能报文头,其中,SFC OAM类型承载于所述业务功能报文头中。The Payload, the OAM packet header, and the service function packet header, where the SFC OAM type is carried in the service function packet header.
  18. 根据权利要求16所述的装置,其中,基于UDP协议承载的SFC OAM报文包括以下信息至少之一:The apparatus according to claim 16, wherein the SFC OAM message carried based on the UDP protocol comprises at least one of the following information:
    UDP源端口号、用于标识SFC OAM报文端口号的UDP目的端口号、用于标识SFC OAM报文的版本号的版本信息、用于标识SFC OAM报文的报文类型信息、用于标识响应报文的响应模式信息、用于标识故障原因的返回编码信息、用于标识报文发送频率的频率信息、用于请求报文随机生成的信息、用于标识报文发送的时间点的信息、用于标识报文接收的时间点的信息、用于请求报文中待扩展的TLV,或者用于响应报文中标识获取的业务功能链路信息的TLV、用于标识填充字段的填充字段信息。The UDP source port number, the UDP destination port number used to identify the SFC OAM packet port number, the version information used to identify the version number of the SFC OAM packet, and the packet type information used to identify the SFC OAM packet. The response mode information of the response packet, the return encoding information used to identify the cause of the fault, the frequency information used to identify the frequency of sending the packet, the information used to request the random generation of the packet, and the information used to identify the time point at which the packet is sent. The TLV for identifying the time of receiving the packet, the TLV for requesting the extension of the packet, or the TLV for identifying the service function link information obtained in the response packet, and the padding field for identifying the padding field. information.
  19. 根据权利要求16所述的装置,其中,还包括: The apparatus of claim 16 further comprising:
    第二发送模块,设置为在所述SFC OAM报文携带的响应模式为IPv4/IPv6用户数据协议UDP报文时,通过不携带业务功能报文头的IPv4/IPv6 UDP报文将对所述OAM报文处理后的处理结果发送给发送所述OAM报文的源端业务节点或者下一跳业务节点;The second sending module is configured to: when the response mode carried in the SFC OAM packet is an IPv4/IPv6 user data protocol UDP packet, the OAM is performed by using an IPv4/IPv6 UDP packet that does not carry the service function packet header. The processing result of the packet processing is sent to the source service node or the next hop service node that sends the OAM message;
    第三发送模块,设置为在所述SFC OAM报文携带的响应模式为SFC OAM UDP报文时,通过所述SFC OAM UDP报文将对所述OAM报文处理后的处理结果发送给发送所述OAM报文的源端业务节点或者下一跳业务节点。The third sending module is configured to: when the response mode carried in the SFC OAM packet is an SFC OAM UDP packet, send the processing result of the OAM packet processing to the sending station by using the SFC OAM UDP packet The source service node or the next hop service node of the OAM packet.
  20. 根据权利要求16至19中任一项所述的装置,其中,The apparatus according to any one of claims 16 to 19, wherein
    所述目的业务节点为业务功能链上除所述源端业务节点之外的其余一个业务节点或多个业务节点的组合。 The destination service node is a combination of the other service node or multiple service nodes except the source service node on the service function chain.
PCT/CN2014/092178 2014-10-17 2014-11-25 Processing method and apparatus for operation, administration and maintenance (oam) message WO2016058245A1 (en)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201410555236.1 2014-10-17
CN201410555236.1A CN105577413B (en) 2014-10-17 2014-10-17 Operations, Administration and Maintenance OAM message processing method and processing device

Publications (1)

Publication Number Publication Date
WO2016058245A1 true WO2016058245A1 (en) 2016-04-21

Family

ID=55746008

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2014/092178 WO2016058245A1 (en) 2014-10-17 2014-11-25 Processing method and apparatus for operation, administration and maintenance (oam) message

Country Status (2)

Country Link
CN (1) CN105577413B (en)
WO (1) WO2016058245A1 (en)

Cited By (26)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
EP3273640A1 (en) * 2016-07-21 2018-01-24 Cisco Technology, Inc. Link selection for communication with a service function cluster
US10148577B2 (en) 2014-12-11 2018-12-04 Cisco Technology, Inc. Network service header metadata for load balancing
US10187306B2 (en) 2016-03-24 2019-01-22 Cisco Technology, Inc. System and method for improved service chaining
US10218593B2 (en) 2016-08-23 2019-02-26 Cisco Technology, Inc. Identifying sources of packet drops in a service function chain environment
US10225270B2 (en) 2016-08-02 2019-03-05 Cisco Technology, Inc. Steering of cloned traffic in a service function chain
US10225187B2 (en) 2017-03-22 2019-03-05 Cisco Technology, Inc. System and method for providing a bit indexed service chain
US10237379B2 (en) 2013-04-26 2019-03-19 Cisco Technology, Inc. High-efficiency service chaining with agentless service nodes
US10257033B2 (en) 2017-04-12 2019-04-09 Cisco Technology, Inc. Virtualized network functions and service chaining in serverless computing infrastructure
US10320664B2 (en) 2016-07-21 2019-06-11 Cisco Technology, Inc. Cloud overlay for operations administration and management
US10333855B2 (en) 2017-04-19 2019-06-25 Cisco Technology, Inc. Latency reduction in service function paths
US10397271B2 (en) 2017-07-11 2019-08-27 Cisco Technology, Inc. Distributed denial of service mitigation for web conferencing
US10419550B2 (en) 2016-07-06 2019-09-17 Cisco Technology, Inc. Automatic service function validation in a virtual network environment
US10541893B2 (en) 2017-10-25 2020-01-21 Cisco Technology, Inc. System and method for obtaining micro-service telemetry data
US10554689B2 (en) 2017-04-28 2020-02-04 Cisco Technology, Inc. Secure communication session resumption in a service function chain
US10666612B2 (en) 2018-06-06 2020-05-26 Cisco Technology, Inc. Service chains for inter-cloud traffic
US10673698B2 (en) 2017-07-21 2020-06-02 Cisco Technology, Inc. Service function chain optimization using live testing
USRE48131E1 (en) 2014-12-11 2020-07-28 Cisco Technology, Inc. Metadata augmentation in a service function chain
US10735275B2 (en) 2017-06-16 2020-08-04 Cisco Technology, Inc. Releasing and retaining resources for use in a NFV environment
US10791065B2 (en) 2017-09-19 2020-09-29 Cisco Technology, Inc. Systems and methods for providing container attributes as part of OAM techniques
US10798187B2 (en) 2017-06-19 2020-10-06 Cisco Technology, Inc. Secure service chaining
US10884807B2 (en) 2017-04-12 2021-01-05 Cisco Technology, Inc. Serverless computing and task scheduling
US10931793B2 (en) 2016-04-26 2021-02-23 Cisco Technology, Inc. System and method for automated rendering of service chaining
US11018981B2 (en) 2017-10-13 2021-05-25 Cisco Technology, Inc. System and method for replication container performance and policy validation using real time network traffic
US11063856B2 (en) 2017-08-24 2021-07-13 Cisco Technology, Inc. Virtual network function monitoring in a network function virtualization deployment
CN114143380A (en) * 2022-01-04 2022-03-04 烽火通信科技股份有限公司 Method and system for solving SRv6 tail node power failure scene OAM and service inconsistency
CN115766536A (en) * 2022-11-11 2023-03-07 北京百度网讯科技有限公司 Service chain detection system, method and device and electronic equipment

Families Citing this family (8)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN107925613B (en) 2016-07-01 2020-07-07 华为技术有限公司 Method, device and system for forwarding message in Service Function Chain (SFC)
CN113055289B (en) 2016-07-01 2023-12-08 华为技术有限公司 Message forwarding method, device and system based on service function chain SFC
CN108512675B (en) * 2017-02-25 2021-06-15 华为技术有限公司 Network diagnosis method and device, control node and network node
CN109218058B (en) * 2017-07-06 2021-09-14 中国电信股份有限公司 Method and system for acquiring OAM information and computer readable storage medium
CN112804075B (en) * 2019-11-14 2022-10-11 华为技术有限公司 Method, device and system for sending message and receiving message for OAM (operation administration and maintenance)
CN113497758B (en) * 2020-04-03 2023-02-14 华为技术有限公司 Service execution method, device and system
CN115225732A (en) * 2021-04-21 2022-10-21 华为技术有限公司 Operation, maintenance and management (OAM) detection method and device
CN115733767A (en) * 2021-09-01 2023-03-03 华为技术有限公司 Path fault detection method, device, system, network equipment and storage medium

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN102224709A (en) * 2011-04-20 2011-10-19 华为技术有限公司 Method and apparatus of monitoring on ip bearing net performance
CN103580894A (en) * 2012-07-31 2014-02-12 华为技术有限公司 Method, device and system for operation, administration and maintenance (OAM) configuration
CN103716172A (en) * 2012-09-28 2014-04-09 中兴通讯股份有限公司 Multiple protocol label switching-based operation, administration and maintenance (OAM) method and apparatus
CN104052623A (en) * 2014-06-25 2014-09-17 成都广达电子股份有限公司 Message processing method and message processing system in Ethernet passive optical network

Family Cites Families (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN102185780B (en) * 2011-05-12 2015-09-16 中兴通讯股份有限公司 OAM message processing method and device

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN102224709A (en) * 2011-04-20 2011-10-19 华为技术有限公司 Method and apparatus of monitoring on ip bearing net performance
CN103580894A (en) * 2012-07-31 2014-02-12 华为技术有限公司 Method, device and system for operation, administration and maintenance (OAM) configuration
CN103716172A (en) * 2012-09-28 2014-04-09 中兴通讯股份有限公司 Multiple protocol label switching-based operation, administration and maintenance (OAM) method and apparatus
CN104052623A (en) * 2014-06-25 2014-09-17 成都广达电子股份有限公司 Message processing method and message processing system in Ethernet passive optical network

Cited By (40)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US10237379B2 (en) 2013-04-26 2019-03-19 Cisco Technology, Inc. High-efficiency service chaining with agentless service nodes
US10148577B2 (en) 2014-12-11 2018-12-04 Cisco Technology, Inc. Network service header metadata for load balancing
USRE48131E1 (en) 2014-12-11 2020-07-28 Cisco Technology, Inc. Metadata augmentation in a service function chain
US10187306B2 (en) 2016-03-24 2019-01-22 Cisco Technology, Inc. System and method for improved service chaining
US10812378B2 (en) 2016-03-24 2020-10-20 Cisco Technology, Inc. System and method for improved service chaining
US10931793B2 (en) 2016-04-26 2021-02-23 Cisco Technology, Inc. System and method for automated rendering of service chaining
US10419550B2 (en) 2016-07-06 2019-09-17 Cisco Technology, Inc. Automatic service function validation in a virtual network environment
US10218616B2 (en) 2016-07-21 2019-02-26 Cisco Technology, Inc. Link selection for communication with a service function cluster
US10320664B2 (en) 2016-07-21 2019-06-11 Cisco Technology, Inc. Cloud overlay for operations administration and management
EP3273640A1 (en) * 2016-07-21 2018-01-24 Cisco Technology, Inc. Link selection for communication with a service function cluster
US10225270B2 (en) 2016-08-02 2019-03-05 Cisco Technology, Inc. Steering of cloned traffic in a service function chain
US10778551B2 (en) 2016-08-23 2020-09-15 Cisco Technology, Inc. Identifying sources of packet drops in a service function chain environment
US10218593B2 (en) 2016-08-23 2019-02-26 Cisco Technology, Inc. Identifying sources of packet drops in a service function chain environment
US10225187B2 (en) 2017-03-22 2019-03-05 Cisco Technology, Inc. System and method for providing a bit indexed service chain
US10778576B2 (en) 2017-03-22 2020-09-15 Cisco Technology, Inc. System and method for providing a bit indexed service chain
US10257033B2 (en) 2017-04-12 2019-04-09 Cisco Technology, Inc. Virtualized network functions and service chaining in serverless computing infrastructure
US10938677B2 (en) 2017-04-12 2021-03-02 Cisco Technology, Inc. Virtualized network functions and service chaining in serverless computing infrastructure
US10884807B2 (en) 2017-04-12 2021-01-05 Cisco Technology, Inc. Serverless computing and task scheduling
US10333855B2 (en) 2017-04-19 2019-06-25 Cisco Technology, Inc. Latency reduction in service function paths
US11102135B2 (en) 2017-04-19 2021-08-24 Cisco Technology, Inc. Latency reduction in service function paths
US10554689B2 (en) 2017-04-28 2020-02-04 Cisco Technology, Inc. Secure communication session resumption in a service function chain
US11539747B2 (en) 2017-04-28 2022-12-27 Cisco Technology, Inc. Secure communication session resumption in a service function chain
US11196640B2 (en) 2017-06-16 2021-12-07 Cisco Technology, Inc. Releasing and retaining resources for use in a NFV environment
US10735275B2 (en) 2017-06-16 2020-08-04 Cisco Technology, Inc. Releasing and retaining resources for use in a NFV environment
US10798187B2 (en) 2017-06-19 2020-10-06 Cisco Technology, Inc. Secure service chaining
US10397271B2 (en) 2017-07-11 2019-08-27 Cisco Technology, Inc. Distributed denial of service mitigation for web conferencing
US11108814B2 (en) 2017-07-11 2021-08-31 Cisco Technology, Inc. Distributed denial of service mitigation for web conferencing
US10673698B2 (en) 2017-07-21 2020-06-02 Cisco Technology, Inc. Service function chain optimization using live testing
US11115276B2 (en) 2017-07-21 2021-09-07 Cisco Technology, Inc. Service function chain optimization using live testing
US11063856B2 (en) 2017-08-24 2021-07-13 Cisco Technology, Inc. Virtual network function monitoring in a network function virtualization deployment
US10791065B2 (en) 2017-09-19 2020-09-29 Cisco Technology, Inc. Systems and methods for providing container attributes as part of OAM techniques
US11018981B2 (en) 2017-10-13 2021-05-25 Cisco Technology, Inc. System and method for replication container performance and policy validation using real time network traffic
US10541893B2 (en) 2017-10-25 2020-01-21 Cisco Technology, Inc. System and method for obtaining micro-service telemetry data
US11252063B2 (en) 2017-10-25 2022-02-15 Cisco Technology, Inc. System and method for obtaining micro-service telemetry data
US11122008B2 (en) 2018-06-06 2021-09-14 Cisco Technology, Inc. Service chains for inter-cloud traffic
US11799821B2 (en) 2018-06-06 2023-10-24 Cisco Technology, Inc. Service chains for inter-cloud traffic
US10666612B2 (en) 2018-06-06 2020-05-26 Cisco Technology, Inc. Service chains for inter-cloud traffic
CN114143380A (en) * 2022-01-04 2022-03-04 烽火通信科技股份有限公司 Method and system for solving SRv6 tail node power failure scene OAM and service inconsistency
CN114143380B (en) * 2022-01-04 2023-06-09 烽火通信科技股份有限公司 Method and system for solving inconsistent OAM and service of SRv tail node power down scene
CN115766536A (en) * 2022-11-11 2023-03-07 北京百度网讯科技有限公司 Service chain detection system, method and device and electronic equipment

Also Published As

Publication number Publication date
CN105577413B (en) 2019-09-10
CN105577413A (en) 2016-05-11

Similar Documents

Publication Publication Date Title
WO2016058245A1 (en) Processing method and apparatus for operation, administration and maintenance (oam) message
US10972391B2 (en) Full-path validation in segment routing
US20210273866A1 (en) Service Chain Fault Detection Method and Apparatus
EP3332511B1 (en) Method and system for path monitoring in a software-defined networking (sdn) system
US9917745B2 (en) Validation of chained network services
US9497107B1 (en) Seamless path monitoring and rapid fault isolation using bidirectional forwarding detection in a network environment
US8837300B2 (en) Managing trace requests over tunneled links
US10063447B2 (en) Path-ping and ECMP-traceroute for IPV6 overlay virtualized networks
US8976682B2 (en) Connection verification for MPLS label switched paths and pseudowires
JP5992602B2 (en) System and method for using label distribution protocol (LDP) in IPv6 networks
US7746796B2 (en) Directed echo requests and reverse traceroute
JP4840236B2 (en) Network system and node device
US20200396162A1 (en) Service function chain sfc-based communication method, and apparatus
WO2021185208A1 (en) Packet processing method and apparatus, device, and storage medium
WO2015184771A1 (en) Method and node device for operation, administration, and maintenance of service function chaining
WO2018210213A1 (en) Method and device for implementing ioam packaging and storage medium
CN108604997B (en) Method and apparatus for a control plane to configure monitoring of Differentiated Services Coding Points (DSCPs) and Explicit Congestion Notifications (ECNs)
US8971195B2 (en) Querying health of full-meshed forwarding planes
JP6622922B2 (en) Method and apparatus for a data plane for monitoring DSCP (Differentiated Services Code Point) and ECN (Explicit Connection Notification)
WO2015184740A1 (en) Method and device for processing detection hierarchy information
WO2016050177A1 (en) Pmtu determination method, network device and system
US20200336401A1 (en) Round-trip performance measurement in a packet-switched communication network
Bonica et al. Label Switched Path (LSP) Self-Ping
WO2023247996A1 (en) Method and system to mitigate fault in a distributed system
Bonica et al. RFC 7746: Label Switched Path (LSP) Self-Ping

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: 14903921

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 14903921

Country of ref document: EP

Kind code of ref document: A1