CN105577413A - OAM (Operation, Administration and Management) message processing method and device - Google Patents
OAM (Operation, Administration and Management) message processing method and device Download PDFInfo
- Publication number
- CN105577413A CN105577413A CN201410555236.1A CN201410555236A CN105577413A CN 105577413 A CN105577413 A CN 105577413A CN 201410555236 A CN201410555236 A CN 201410555236A CN 105577413 A CN105577413 A CN 105577413A
- Authority
- CN
- China
- Prior art keywords
- message
- sfcoam
- oam
- service node
- information
- Prior art date
- Legal status (The legal status 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 status listed.)
- Granted
Links
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
- H04L41/34—Signalling channels for network management communication
Abstract
The invention discloses an OAM message processing method and device. The method comprises that A source end service node determines an OAM message which is sent in an SFC (Service Function Chain), the OAM message comprises the load Payload, the head of the OAM message and the head of a service function message, and the OAM message is carried by a predetermined SFC OAM network port number; and the source end service node sends the OAM message carried by the predetermined SFC OAM network port number to a target service node in the SFC for processing. According to the method and device of the invention, the problem that the content of the SFC OAM message as well as the protocol to carry the message cannot be determined in the prior art is solved, the complete SFC OAM message is determined, and the expansibility of SFC OAM is improved.
Description
Technical field
The present invention relates to the communications field, in particular to a kind of Operations, Administration and Maintenance (OperationAdministrationandMaintenance, referred to as OAM) message processing method and device.
Background technology
Since data center network is after Overlay network Development, network edge becomes the separation of virtual network and physical network, and wherein, network edge can be Server or ToR, and may be Gateway.But Overlay technology does not solve all problems, also have a lot of Middleware in data center, as fire compartment wall/load equalizer etc., these equipment all carry out deal with data based on customer service, if passed through these equipment by tunnel, be obviously not all right.
This deployment model of data center, requires that virtual firewall/load equalizer can be disposed arbitrarily in a network, namely has nothing to do with network topology.Such new problem is, how flow can be processed by virtual firewall/load equalizer flexibly? the service processing function such as these virtual firewall/load equalizers, independent of former network topology, are realized by standard server.
In the related, service processing function such as virtual firewall/load equalizer/gateways, be called business function (ServiceFunction, referred to as SF), and flow is through the process of a series of SF, form business function chain (ServiceFunctionChaining, referred to as SFC).Business function chain is the ordered arrangement of a series of abstract business function, and which SFFs of process and/or the sequential combination of which SFs on earth when concrete service traffics forward, SFC does not define.Fig. 1 is the exemplary plot of SFC in correlation technique, and as shown in Figure 1, solid line and dotted line represent two SFC, are sometimes also business chain ServiceChain.Below the framework of SFC is described.
This SFC can be divided into following assembly:
1. business superposition (ServiceOverlay), namely each business function node needs Overlay (superposition) technology of communication;
2. general service control plane (GenericServiceControlPlane, referred to as GSCP), forms the controller of SFC;
3. business categorizing device (ServiceClassifier, referred to as SC), namely needs to flow identification into passerby, then specifically flows, carry out specific SFC process;
4, business function (ServiceFunction, referred to as SF), carries out the assembly of Business Processing to data message;
5. business function transponder (ServiceFunctionForwarder, referred to as SFF), the forwarding between the multiple SFs in inside of responsible same service node.The data message of Overlay encapsulates through the forwarded device NF of service node, after the outer overlay layer of decapsulation, main carry out encapsulating on SFF assembly, decapsulation, renewal business function heading (NetworkServiceHeader, referred to as NSH).Fig. 2 is the message format schematic diagram of business function heading in correlation technique, as shown in Figure 2;
6. forwarded device (NetworkForwarder, referred to as NF), the forwarding between the multiple SFFs in inside of responsible same service node; And the data message of Overlay is encapsulated, decapsulation Overlay layer; Meanwhile, the forwarding between different business node is processed;
7. business function path (ServiceFunctionPath, referred to as SFP), Fig. 3 is the schematic diagram in business function path in correlation technique, as shown in Figure 3, SFP is from grader, through some concrete business function examples in order, the Business Processing path arrived at the destination.In some cases, general service parametric controller GSCP can not know all business function examples of process on the way, such as load sharing scene or business service grade scene etc., now, the description of this business function chain between the path that the orderly srvice instance of abstract business function chain SFC and truly concrete traffic forwarding process is formed, is also referred to as business function path.Article one, business function chain may comprise multiple business function path, and different business function paths corresponds to different strategies.
8. control plane metadata (DataplaneMetadata), this is a large feature, and metadata (Metadata) allows each business function node, can intercourse information, reaches certain Business Processing object.
In sum, network equipment business function and forwarding can be separated by SFC, thus achieve operation independent and the process of business function, promote the forwarding performance of the network equipment.
OAM technology is the network transmission technology for network connectivty detection, fault location, investigation, and when breaking down, can provide the trigger mechanism of pretection switch.It contains, and connectivity of link detects (ConnectivityVerification, referred to as CV) mechanism, Ping is machine-processed and Trace is machine-processed.For different bearer network agreements, all there is corresponding OAM mechanism.Such as, Ethernet has ether OAM agreement, and IP network has IPOAM agreement, and MPLS network has MPLSOAM.
Wherein, IPPing and the IPTraceroute mechanism in IPOAM is based on ICMP agreement.Wherein, IPPing realizes request request and response reply message by the field of the type of expansion ICMP agreement; IPTraceroute realizes the request request message of Traceroute by the ttl value in amendment IPPingrequest message, and the ICMP error message exceeded the time limit by TTL realizes the response reply message of Traceroute; But there is two large problems by ICMP carrying: 1. the agreement relating to two kinds of IP layers is ICMPv4 and ICMPv6 respectively, when expanding SFCOAM, all going expansion to seem slightly loaded down with trivial details from two protocol level; 2.ICMP message is inconvenient to be used for expansion to carry Trace response message.
In addition, LSPPing and LSPTrace of MPLSOAM is machine-processed based on udp protocol, application target port numbers 3503.Because need to consider to dissimilar LSP (such as, IPv4LDPLSP, IPv6LDPLSP, IPv4RSVPLSP, IPv6RSVPLSP, PWLSP etc.) carry out different LSPPing and LSPTrace, conveniently expand, LSPPing and LSPTrace does not use Ping and Traceroute based on ICMP mechanism to expand, but expands based on udp protocol.
Fig. 4 is SFCOAM technological frame schematic diagram in correlation technique, and as shown in Figure 4, the technological frame of SFCOAM is mainly used in the link circuit condition between diagnosis business functional chain or business function.As shown in Figure 5, Fig. 5 is the schematic diagram of SFCOAM message format one in correlation technique to a kind of implementation wherein, and as shown in Figure 5, in business function heading NSH, a reserved field, is OAM message and OAM message type for mark; Another kind of implementation as shown in Figure 6, Fig. 6 is the schematic diagram of SFCOAM message format two in correlation technique, as shown in Figure 6, reserved 1 Bit in business function heading NSH, for mark be OAM message, so to the OAM message of which kind of type, be placed in the message beyond business function heading NSH.But no matter which kind of scheme, all not relating to concrete SFCOAM message content, be carried on earth on what protocol massages, is the expansion of icmp packet, or the expansion of UDP message, or other.
Therefore, in the related, existence cannot determine SFCOAM message content, and what agreement to carry the problem of this message based on.
Summary of the invention
The invention provides a kind of Operations, Administration and Maintenance OAM message processing method and device, SFCOAM message content cannot be determined at least to solve in correlation technique to exist, and what agreement to carry the problem of this message based on.
According to an aspect of the present invention, provide a kind of Operations, Administration and Maintenance OAM message processing method, comprise: source service node determines the OAM message sent on business function chain SFC, wherein, described OAM message comprises: load p ayload, OAM message head, business function heading, wherein, described OAM message adopts predetermined SFCOAM network terminal slogan carrying; The described OAM message be carried on described predetermined SFCOAM network terminal slogan is sent to the object service node process on described SFC by described source service node.
Preferably, described OAM message one of adopts following form at least: Payload, OAM message head, business function heading, and wherein, SFCOAM type is carried in described OAM message head; Payload, OAM message head, business function heading, wherein, SFCOAM type is carried in described business function heading.
Preferably, SFCOAM message based on udp protocol carrying comprises following information one of at least: UDP source port number, for identifying the UDP destination slogan of SFCOAM message port numbers, for identifying the version information of the version number of SFCOAM message, for identifying the type of message information of SFCOAM message, for the response modes information of identification response message, coded message is returned for what identify failure cause, for the frequency information of identification message transmission frequency, for the information of request message stochastic generation, for the information of the time point that identification message sends, for the information of the time point that identification message receives, for TLV to be expanded in request message, or for the TLV of the business function link information that identifies acquisition in response message, for identifying the filling field information of filling field.
Preferably, after the described OAM message be carried on described predetermined SFCOAM network terminal slogan is sent to the object service node process on described SFC, also comprise: when the response modes that described SFCOAM message carries is IPv4/IPv6 User Data Protocol UDP message, receive the IPv4/IPv6UDP message that described object service node does not carry business function heading, wherein, the result to obtaining after described OAM message process is carried in described IPv4/IPv6UDP message; When the response modes that described SFCOAM message carries is SFCOAMUDP message, receive the SFCOAMUDP message that described object service node sends, wherein, described SFCOAMUDP message carries the result to obtaining after described OAM message process.
Preferably, described source service node is one of them service node on business categorizing device or business function chain.
According to a further aspect in the invention, provide a kind of Operations, Administration and Maintenance OAM message processing method, comprise: object service node is received in the OAM message that business function chain SFC sends, wherein, described OAM message comprises: load p ayload, OAM message head, business function heading, wherein, OAM message adopts predetermined SFCOAM network terminal slogan carrying; Described object service node processes the described OAM message received.
Preferably, described OAM message one of adopts following form at least: Payload, OAM message head, business function heading, and wherein, SFCOAM type is carried in described OAM message head; Payload, OAM message head, business function heading, wherein, SFCOAM type is carried in described business function heading.
Preferably, SFCOAM message based on udp protocol carrying comprises following information one of at least: UDP source port number, for identifying the UDP destination slogan of SFCOAM message port numbers, for identifying the version information of the version number of SFCOAM message, for identifying the type of message information of SFCOAM message, for the response modes information of identification response message, coded message is returned for what identify failure cause, for the frequency information of identification message transmission frequency, for the information of request message stochastic generation, for the information of the time point that identification message sends, for the information of the time point that identification message receives, for TLV to be expanded in request message, or for the TLV of the business function link information that identifies acquisition in response message, for identifying the filling field information of filling field.
After described object service node processes the described OAM message received, also comprise: when the response modes that described SFCOAM message carries is IPv4/IPv6 User Data Protocol UDP message, the result after described OAM message process will be sent to the source service node or down hop service node that send described OAM message by the IPv4/IPv6UDP message not carrying business function heading; When the response modes that described SFCOAM message carries is SFCOAMUDP message, the result after described OAM message process will be sent to the source service node or down hop service node that send described OAM message by described SFCOAMUDP message.
Preferably, described object service node is the combination of all the other service nodes on business function chain except described source service node or multiple service node.
According to a further aspect in the invention, provide a kind of Operations, Administration and Maintenance OAM message processing unit, be arranged in source service node, comprise: determination module, for determining the OAM message sent on business function chain SFC, wherein, described OAM message comprises: load p ayload, OAM message head, business function heading, wherein, described OAM message adopts predetermined SFCOAM network terminal slogan carrying; First sending module, for sending to the object service node process on described SFC by the described OAM message be carried on described predetermined SFCOAM network terminal slogan.
Preferably, described OAM message one of adopts following form at least: Payload, OAM message head, business function heading, and wherein, SFCOAM type is carried in described OAM message head; Payload, OAM message head, business function heading, wherein, SFCOAM type is carried in described business function heading.
Preferably, SFCOAM message based on udp protocol carrying comprises following information one of at least: UDP source port number, for identifying the UDP destination slogan of SFCOAM message port numbers, for identifying the version information of the version number of SFCOAM message, for identifying the type of message information of SFCOAM message, for the response modes information of identification response message, coded message is returned for what identify failure cause, for the frequency information of identification message transmission frequency, for the information of request message stochastic generation, for the information of the time point that identification message sends, for the information of the time point that identification message receives, for TLV to be expanded in request message, or for the TLV of the business function link information that identifies acquisition in response message, for identifying the filling field information of filling field.
Preferably, this device also comprises: the first receiver module, when response modes for carrying at described SFCOAM message is IPv4/IPv6 User Data Protocol UDP message, receive the IPv4/IPv6UDP message that described object service node does not carry business function heading, wherein, the result to obtaining after described OAM message process is carried in described IPv4/IPv6UDP message; Second receiver module, when response modes for carrying at described SFCOAM message is SFCOAMUDP message, receive the SFCOAMUDP message that described object service node sends, wherein, described SFCOAMUDP message carries the result to obtaining after described OAM message process.
Preferably, described source service node is one of them service node on business categorizing device or business function chain.
According to also one side of the present invention, provide a kind of Operations, Administration and Maintenance OAM message processing unit, be arranged in object service node, comprise: the 3rd receiver module, for being received in the OAM message that business function chain SFC sends, wherein, described OAM message comprises: load p ayload, OAM message head, business function heading, wherein, OAM message adopts predetermined SFCOAM network terminal slogan carrying; Processing module, for processing the described OAM message received.
Preferably, described OAM message one of adopts following form at least: Payload, OAM message head, business function heading, and wherein, SFCOAM type is carried in described OAM message head; Payload, OAM message head, business function heading, wherein, SFCOAM type is carried in described business function heading.
Preferably, SFCOAM message based on udp protocol carrying comprises following information one of at least: UDP source port number, for identifying the UDP destination slogan of SFCOAM message port numbers, for identifying the version information of the version number of SFCOAM message, for identifying the type of message information of SFCOAM message, for the response modes information of identification response message, coded message is returned for what identify failure cause, for the frequency information of identification message transmission frequency, for the information of request message stochastic generation, for the information of the time point that identification message sends, for the information of the time point that identification message receives, for TLV to be expanded in request message, or for the TLV of the business function link information that identifies acquisition in response message, for identifying the filling field information of filling field.
Preferably, this device also comprises: the second sending module, when response modes for carrying at described SFCOAM message is IPv4/IPv6 User Data Protocol UDP message, the result after described OAM message process will be sent to the source service node or down hop service node that send described OAM message by the IPv4/IPv6UDP message not carrying business function heading; 3rd sending module, when response modes for carrying at described SFCOAM message is SFCOAMUDP message, the result after described OAM message process will be sent to the source service node or down hop service node that send described OAM message by described SFCOAMUDP message.
Preferably, described object service node is the combination of all the other service nodes on business function chain except described source service node or multiple service node.
Pass through the present invention, source service node determines the OAM message sent on business function chain SFC, and wherein, described OAM message comprises: load p ayload, OAM message head, business function heading, wherein, described OAM message adopts predetermined SFCOAM network terminal slogan carrying; The described OAM message be carried on described predetermined SFCOAM network terminal slogan is sent to the object service node process on described SFC by described source service node, solve in correlation technique to exist and cannot determine SFCOAM message content, and what agreement to carry the problem of this message based on, and then reach and determine a kind of complete S FCOAM message, and improve the effect of SFCOAM autgmentability.
Accompanying drawing explanation
Accompanying drawing described herein is used to provide a further understanding of the present invention, and form a application's part, schematic description and description of the present invention, for explaining the present invention, does not form inappropriate limitation of the present invention.In the accompanying drawings:
Fig. 1 is the exemplary plot of SFC in correlation technique;
Fig. 2 is the message format schematic diagram of business function heading in correlation technique;
Fig. 3 is the schematic diagram in business function path in correlation technique;
Fig. 4 is SFCOAM technological frame schematic diagram in correlation technique;
Fig. 5 is the schematic diagram of SFCOAM message format one in correlation technique;
Fig. 6 is the schematic diagram of SFCOAM message format two in correlation technique;
Fig. 7 is the flow chart of the Operations, Administration and Maintenance OAM message processing method one according to the embodiment of the present invention;
Fig. 8 is the flow chart of the Operations, Administration and Maintenance OAM message processing method two according to the embodiment of the present invention;
Fig. 9 is the structured flowchart of the Operations, Administration and Maintenance OAM message processing unit one according to the embodiment of the present invention;
Figure 10 is the preferred structure block diagram of the Operations, Administration and Maintenance OAM message processing unit one according to the embodiment of the present invention;
Figure 11 is the structured flowchart of the Operations, Administration and Maintenance OAM message processing unit two according to the embodiment of the present invention;
Figure 12 is the preferred structure block diagram of the Operations, Administration and Maintenance OAM message processing unit two according to the embodiment of the present invention;
Figure 13 is the message format schematic diagram of the udp protocol carrying SFCOAM message according to the embodiment of the present invention;
Figure 14 be according to the Overlay of embodiment of the present invention encapsulation after based on the complete S FCOAM message format schematic diagram after UDP carrying;
Figure 15 is the message format schematic diagram realizing SFCPing function according to the embodiment of the present invention;
Figure 16 is the schematic diagram realizing SFCTrace function according to the embodiment of the present invention.
Embodiment
Hereinafter also describe the present invention in detail with reference to accompanying drawing in conjunction with the embodiments.It should be noted that, when not conflicting, the embodiment in the application and the feature in embodiment can combine mutually.
Provide a kind of Operations, Administration and Maintenance OAM message processing method in the present embodiment, Fig. 7 is the flow chart of the Operations, Administration and Maintenance OAM message processing method one according to the embodiment of the present invention, and as shown in Figure 7, this flow process comprises the steps:
Step S702, source service node determines the OAM message sent on business function chain SFC, and wherein, OAM message comprises: load p ayload, OAM message head, business function heading, wherein, OAM message adopts predetermined SFCOAM network terminal slogan carrying;
Step S704, the OAM message be carried on predetermined SFCOAM network terminal slogan is sent to the object service node process on SFC by source service node.
Pass through above-mentioned steps, determine a kind of OAM message, predetermined SFCOAM network terminal slogan is adopted to carry this OAM message, and this OAM message determined is sent to object service node, solve in correlation technique to exist and cannot determine SFCOAM message content, and what agreement to carry the problem of this message based on, and then reach and determine a kind of complete S FCOAM message, and improve the effect of SFCOAM autgmentability.
Above-mentioned OAM message can adopt multiple format, such as, one of can adopt following form at least: Payload, OAM message head, business function heading, and wherein, SFCOAM type is carried in OAM message head; Payload, OAM message head, business function heading, wherein, SFCOAM type is carried in business function heading.
It should be noted that, the agreement carrying this SFCOAM message for multiple, can be described for udp protocol below.SFCOAM message based on udp protocol carrying can comprise following information one of at least: UDP source port number, for identifying the UDP destination slogan of SFCOAM message port numbers, for identifying the version information of the version number of SFCOAM message, for identifying the type of message information of SFCOAM message, for the response modes information of identification response message, coded message is returned for what identify failure cause, for the frequency information of identification message transmission frequency, for the information of request message stochastic generation, for the information of the time point that identification message sends, for the information of the time point that identification message receives, for TLV to be expanded in request message, or for the TLV of the business function link information that identifies acquisition in response message, for identifying the filling field information of filling field.
Preferably, after the OAM message be carried on predetermined SFCOAM network terminal slogan being sent to the object service node process on SFC, the response modes that can also carry according to SFCOAM message is different, receives the different response message that source service node sends, illustrates below.
Such as, when the response modes that SFCOAM message carries is IPv4/IPv6 User Data Protocol UDP message, receive the IPv4/IPv6UDP message that object service node does not carry business function heading, wherein, the result to obtaining after OAM message process is carried in IPv4/IPv6UDP message; Again such as, when the response modes that SFCOAM message carries is SFCOAMUDP message, receive the SFCOAMUDP message that object service node sends, wherein, SFCOAMUDP message carries the result to obtaining after OAM message process.And when the response modes that SFCOAM message carries is not for replying, namely do not receive the response message that object service node sends.
It should be noted that, above-mentioned source service node is one of them service node on business categorizing device or business function chain.
In the present embodiment, additionally provide a kind of Operations, Administration and Maintenance OAM message processing method, Fig. 8 is the flow chart of the Operations, Administration and Maintenance OAM message processing method two according to the embodiment of the present invention, and as shown in Figure 8, this flow process comprises the steps:
Step S802, object service node is received in the OAM message that business function chain SFC sends, and wherein, OAM message comprises: load p ayload, OAM message head, business function heading, and wherein, OAM message adopts predetermined SFCOAM network terminal slogan carrying;
Step S804, object service node processes the OAM message received.
Pass through above-mentioned steps, by this OAM message that the SFCOAM network terminal slogan that the employing receiving transmission on SFC is predetermined carries, and this OAM message received is processed, solve in correlation technique to exist and cannot determine SFCOAM message content, and what agreement to carry the problem of this message based on, and then reach and determine a kind of complete S FCOAM message, and improve the effect of SFCOAM autgmentability.
It should be noted that, after this OAM message of the SFCOAM network terminal slogan carrying that the employing that reception SFC sends is predetermined, after carrying out decapsulation to this OAM message, it is SFCOAM message that the port numbers in analytic message finds, processes this OAM message.
Wherein, OAM message can adopt multiple format, such as, one of can adopt following form at least: Payload, OAM message head, business function heading, and wherein, SFCOAM type is carried in OAM message head; Payload, OAM message head, business function heading, wherein, SFCOAM type is carried in business function heading.
Accordingly, this SFCOAM message can be carried on various protocols, is described below to be carried on udp protocol.Such as, SFCOAM message based on the carrying of UPD agreement can comprise following information one of at least: UDP source port number, for identifying the UDP destination slogan of SFCOAM message port numbers, for identifying the version information of the version number of SFCOAM message, for identifying the type of message information of SFCOAM message, for the response modes information of identification response message, coded message is returned for what identify failure cause, for the frequency information of identification message transmission frequency, for the information of request message stochastic generation, for the information of the time point that identification message sends, for the information of the time point that identification message receives, for TLV to be expanded in request message, or for the TLV of the business function link information that identifies acquisition in response message, for identifying the filling field information of filling field.
Preferably, after object service node processes the OAM message received, the response modes that can also carry according to SFCOAM message is different, sends response message, illustrate below to source service node.Such as, when the response modes that SFCOAM message carries is IPv4/IPv6 User Data Protocol UDP message, the source service node or down hop service node that send OAM message will be sent to the result after OAM message process by the IPv4/IPv6UDP message not carrying business function heading; Again such as, when the response modes that SFCOAM message carries is SFCOAMUDP message, the source service node or down hop service node that send OAM message will be sent to the result after OAM message process by SFCOAMUDP message.And and the response modes that SFCOAM message carries for do not reply time, after object service node receives this OAM message, need not response message be sent.
Preferably, object service node is the combination of all the other service nodes on business function chain except source service node or multiple service node.
Additionally provide a kind of Operations, Administration and Maintenance OAM message processing unit in the present embodiment, this device is used for realizing above-described embodiment and preferred implementation, has carried out repeating no more of explanation.As used below, term " module " can realize the software of predetermined function and/or the combination of hardware.Although the device described by following examples preferably realizes with software, hardware, or the realization of the combination of software and hardware also may and conceived.
Fig. 9 is the structured flowchart of the Operations, Administration and Maintenance OAM message processing unit one according to the embodiment of the present invention, and as shown in Figure 9, this device is arranged in source service node, comprising: determination module 92 and the first sending module 94, be described this device below.
Determination module 92, for determining the OAM message sent on business function chain SFC, wherein, OAM message comprises: load p ayload, OAM message head, business function heading, and wherein, OAM message adopts predetermined SFCOAM network terminal slogan carrying; First sending module 94, is connected to above-mentioned determination module 92, for the OAM message be carried on predetermined SFCOAM network terminal slogan being sent to the object service node process on SFC.
Wherein, OAM message can adopt multiple format, such as, one of can adopt following form at least: Payload, OAM message head, business function heading, and wherein, SFCOAM type is carried in OAM message head; Payload, OAM message head, business function heading, wherein, SFCOAM type is carried in business function heading.
Preferably, SFCOAM message based on udp protocol carrying can comprise following information one of at least: UDP source port number, for identifying the UDP destination slogan of SFCOAM message port numbers, for identifying the version information of the version number of SFCOAM message, for identifying the type of message information of SFCOAM message, for the response modes information of identification response message, coded message is returned for what identify failure cause, for the frequency information of identification message transmission frequency, for the information of request message stochastic generation, for the information of the time point that identification message sends, for the information of the time point that identification message receives, for TLV to be expanded in request message, or for the TLV of the business function link information that identifies acquisition in response message, for identifying the filling field information of filling field.
Figure 10 is the preferred structure block diagram of the Operations, Administration and Maintenance OAM message processing unit one according to the embodiment of the present invention, as shown in Figure 10, this device is except comprising all modules shown in Fig. 9, also comprise following one of at least: the first receiver module 102, second receiver module 104, is described this device below.
First receiver module 102, be connected to above-mentioned first sending module 94, when response modes for carrying at SFCOAM message is IPv4/IPv6 User Data Protocol UDP message, receive the IPv4/IPv6UDP message that object service node does not carry business function heading, wherein, the result to obtaining after OAM message process is carried in IPv4/IPv6UDP message; Second receiver module 104, be connected to above-mentioned first sending module 94, when response modes for carrying at SFCOAM message is SFCOAMUDP message, receive the SFCOAMUDP message that object service node sends, wherein, SFCOAMUDP message carries the result to obtaining after OAM message process.
Preferably, source service node is one of them service node on business categorizing device or business function chain.
Figure 11 is the structured flowchart of the Operations, Administration and Maintenance OAM message processing unit two according to the embodiment of the present invention, as shown in figure 11, this device is arranged in object service node, comprising: the 3rd receiver module 112 and processing module 114, be described this device below.
3rd receiver module 112, for being received in the OAM message that business function chain SFC sends, wherein, OAM message comprises: load p ayload, OAM message head, business function heading, and wherein, OAM message adopts predetermined SFCOAM network terminal slogan carrying; Processing module 114, is connected to above-mentioned 3rd receiver module 112, for processing the OAM message received.
Preferably, above-mentioned OAM message one of can adopt following form at least: Payload, OAM message head, business function heading, and wherein, SFCOAM type is carried in OAM message head; Payload, OAM message head, business function heading, wherein, SFCOAM type is carried in business function heading.
Preferably, SFCOAM message based on udp protocol carrying comprises following information one of at least: UDP source port number, for identifying the UDP destination slogan of SFCOAM message port numbers, for identifying the version information of the version number of SFCOAM message, for identifying the type of message information of SFCOAM message, for the response modes information of identification response message, coded message is returned for what identify failure cause, for the frequency information of identification message transmission frequency, for the information of request message stochastic generation, for the information of the time point that identification message sends, for the information of the time point that identification message receives, for TLV to be expanded in request message, or for the TLV of the business function link information that identifies acquisition in response message, for identifying the filling field information of filling field.
Figure 12 is the preferred structure block diagram of the Operations, Administration and Maintenance OAM message processing unit two according to the embodiment of the present invention, as shown in figure 12, this device is except comprising all modules shown in Figure 11, also comprise following one of at least: the second sending module 122, the 3rd sending module 124, be described this device below.
Second sending module 122, be connected to above-mentioned processing module 114, when response modes for carrying at SFCOAM message is IPv4/IPv6 User Data Protocol UDP message, the source service node or down hop service node that send OAM message will be sent to the result after OAM message process by the IPv4/IPv6UDP message not carrying business function heading; 3rd sending module 124, be connected to above-mentioned processing module 114, when response modes for carrying at SFCOAM message is SFCOAMUDP message, the source service node or down hop service node that send OAM message will be sent to the result after OAM message process by SFCOAMUDP message.
Preferably, object service node is the combination of all the other service nodes on business function chain except source service node or multiple service node.
For the problems referred to above in correlation technique, in the present embodiment, a kind of method of bearer service functional chain Operations, Administration and Maintenance message is provided.By defining a new UDP/TCP port numbers, be used for carrying the various message of SFCOAM; Be described for udp protocol for the agreement of carrying below.Figure 13 is the message format schematic diagram of the udp protocol carrying SFCOAM message according to the embodiment of the present invention, as shown in figure 13:
SourcePort: mark UDP source port number;
DestinationPort: mark UDP destination slogan, in the present embodiment, define a new port numbers, is used for carrying SFCOAM message;
The version number of VersionNumber: mark SFCOAM message;
MessageType: mark SFCOAM type of message, mainly contains PingRequest message, PingReply message, connective Request message, connective Reply message etc.;
ReplyMode: the response modes of identification response message, response message by common IPv4/IPv6UDP message response or can send message response by business function path SFP; Etc.;
ReturnCode: carry in response message, mark failure cause (such as, request message mistake, the TLV carrying nonrecognition, business function operation exception etc.); In request message, this field is 0;
Frequency: for periodic SFCOAM message, this field is used for the frequency that identification message sends; For the SFCOAM message (Ping or Trace) initiatively triggered, this field is 0;
Sender ' sHandle: request message stochastic generation; In response message, this field is consistent with request message;
TimestampSent: the time point that identification message sends;
TimestampReceived: the time point that identification message receives;
TLV: for SFCPing or SFCTrace, considers that the information of SFP is included in business function head,
And be carried to final jump service node on the way, therefore in SFCPing or SFCTrace request message, can not carry this field, this field is optional, for subsequent expansion; For in the response message of SFCTrace, this field need by obtain business function link information or business function chain business function relevant information (such as, bandwidth information, resource information, deferred message etc.) respond to the promoter of SFCTrace, therefore need to carry this TLV field, different type corresponds to different information;
Padding: mark fills field, meets the byte requirement of message needs;
Figure 14 be according to the Overlay of embodiment of the present invention encapsulation after based on the complete S FCOAM message format schematic diagram after UDP carrying, as shown in figure 14.
Below in conjunction with accompanying drawing, the embodiment of the present invention is described.
Embodiment 1:
In the present embodiment 1, the business function chain based on the embodiment of SFCPing function comprises: SF1--->SF2--->SF3; Wherein, Overlay network is IP network.
First, operator configures RelayMode for sending response message by business function path, and from Classifier, carries out the Ping request function in this business function path, then from the Ping message format that Classifier sends.Figure 15 is the message format schematic diagram realizing SFCPing function according to the embodiment of the present invention, and as shown in Figure 15, use SFCOAM dedicated port numbers in UDP head, in SFCPing request message, type of message is request message, and response modes as above configures.In the present embodiment, realize Ping function and comprise the steps:
101:Classifier sends the OAM message in Figure 15, and service node 1 is jumped in first of the business function path that E-Packets;
102: service node 1 decapsulation Overlay layer, will carry the message repeating of SFC business function head to SFF1 process, SFF1 judges that this is an OAMPing protocol massages, so be transmitted to the process of SFCOAM protocol module;
103: this SFCOAM protocol module calls the first jumping business function SF1, checks whether it normally runs, and if so, then forwards the packet back to SFF1;
104:SFF1 forwards the packet to service node 1, and service node 1 carries out Overlay encapsulation to this message, forwards this message to down hop service node 2;
105: if check that the first jumping business function SF1 does not normally run, then construct Ping response message, carry business function fault message; And this response message is forwarded meeting to SFF1;
106:SFF1 is by this corresponding message repeating to service node 1, and service node 1 carries out Overlay encapsulation to this message, forwards this message to Classifier;
107: service node 2 receives this message, first decapsulation Overlay layer, will carry the message repeating of SFC business function head to SFF2 process, SFF2 judges that this is an OAM protocol massages, so be transmitted to the process of SFCOAM protocol module;
108: this SFCOAM protocol module calls the second jumping business function SF2, checks whether it normally runs, and if so, then forwards the packet back to SFF2;
109:SFF2 forwards the packet to service node 2, and service node 2 carries out Overlay encapsulation to this message, forwards this message to down hop service node 3;
110: if check that the second jumping business function SF2 does not normally run, then construct Ping response message, carry business function fault message; And this response message is forwarded meeting to SFF2;
111:SFF2 is by this corresponding message repeating to service node 2, and service node 2 carries out Overlay encapsulation to this message, is transmitted to service node 1 along reverse path, and then forwards this message to Classifier;
112: service node 3 receives this message, first decapsulation Overlay layer, to carry the message repeating of SFC business function head to SFF3 process, SFF3 judges that this is an OAM protocol massages and is the final jump in business function path, continues to be transmitted to the process of SFCOAM protocol module;
113: this SFCOAM protocol module calls the 3rd and jumps business function SF3, checks whether it normally runs, if so, then construct Ping response message and this message repeating is returned to SFF3; If not, also construct Ping response message and carry fault business function fault message; And this message repeating is returned to SFF3;
114:SFF3 forwards the packet to service node 3, and service node 3 carries out Overlay encapsulation to this message, is transmitted to service node 2 and service node 1 along reverse path, and then forwards this message to Classifier;
After 115:Classifier receives Ping response message, whether Ping is successful to be shown to operator, if not success, is shown to operator's failure cause.
Specific embodiment 2:
In the present embodiment, the business function chain based on the specific embodiment of SFCTrace function comprises: SF1--->SF2--->SF3, and wherein, Overlay network is IP network.
First, operator configures RelayMode for sending response message by IP path, and from Classifier, carries out Trace (path) request function in this business function path, then from the Trace message format that Classifier sends.Figure 16 is the schematic diagram realizing SFCTrace function according to the embodiment of the present invention, and as shown in Figure 16, wherein, use SFCOAM dedicated port numbers in UDP head, in SFCTrace request message, type of message is request message, and response modes as above configures; The present embodiment comprises the steps:
201:Classifier sends OAM message in Figure 16, and the ttl field arranged in message is 1, and service node 1 is jumped in first of the business function path that E-Packets;
202: service node 1 decapsulation Overlay layer, will carry the message repeating of SFC business function head to SFF1 process, and SFF1 judges that this is an OAMTrace protocol massages and TTL is 1, so be transmitted to the process of SFCOAM protocol module;
203: this SFCOAM protocol module calls the first jumping business function SF1, checks whether it normally runs, and if so, then obtains the business information of SF1, resource information, deferred message etc., is encapsulated in the TLV of response message, forwards the packet back to SFF1; If not, also tectonic response message, carries business function fault message, and forwards the packet back to SFF1;
204:SFF1 forwards the packet to service node 1, and service node 1 carries out Overlay encapsulation to this message, is transmitted to Classifier along IP path;
205:Classifier receives the corresponding message of the first jumping service node, and whether Trace is successful to be shown to operator, if success, shows the information got; Meanwhile, Classifier constructs the SFCTrace message that TTL is 2, and service node 1 is jumped in second of the business function path that E-Packets; If send unsuccessful, display failure cause;
206: service node 1 receives this message, first decapsulation Overlay layer, will carry the message repeating of SFC business function head to SFF1 process, SFF1 judges that this is an OAM protocol massages, so be transmitted to the process of SFCOAM protocol module; Meanwhile, the ttl value in message can be subtracted 1 by SFF1;
207: this SFCOAM protocol module calls the first jumping business function SF1, checks whether it normally runs, and if so, then forwards the packet back to SFF1;
208:SFF1 forwards the packet to service node 1, and service node 1 carries out Overlay encapsulation to this message, forwards this message to down hop service node 2;
209: service node 2 receives this message, first decapsulation Overlay layer, will carry the message repeating of SFC business function head to SFF2 process, and SFF2 judges that this is an OAM protocol massages and be TTL is 1, continues to be transmitted to the process of SFCOAM protocol module;
210: this SFCOAM protocol module calls the second jumping business function SF2, checks whether it normally runs, and if so, then obtains the business information of SF2, resource information, deferred message etc., is encapsulated in the TLV of response message, forwards the packet back to SFF2; If not, also tectonic response message, carries business function fault message, and forwards the packet back to SFF2;
211:SFF2 forwards the packet to service node 2, and service node 2 carries out Overlay encapsulation to this message, is transmitted to Classifier along IP path;
212:Classifier receives the corresponding message of the second jumping service node, and whether Trace is successful to be shown to operator, if success, shows the information got; Meanwhile, Classifier constructs the SFCTrace message that TTL is 3, and service node 1 is jumped in second of the business function path that E-Packets; If send unsuccessful, display failure cause;
213: service node 1 receives this message, first decapsulation Overlay layer, will carry the message repeating of SFC business function head to SFF1 process, SFF1 judges that this is an OAM protocol massages, so be transmitted to the process of SFCOAM protocol module; Meanwhile, the ttl value in message can be subtracted 1 by SFF1;
214: this protocol module calls the first jumping business function SF1, checks whether it normally runs, and if so, then forwards the packet back to SFF1;
215:SFF1 forwards the packet to service node 1, and service node 1 carries out Overlay encapsulation to this message, forwards this message to down hop service node 2;
216: service node 2 receives this message, first decapsulation Overlay layer, will carry the message repeating of SFC business function head to SFF2 process, SFF2 judges that this is an OAM protocol massages, so be transmitted to the process of SFCOAM protocol module; Meanwhile, the ttl value in message can be subtracted 1 by SFF2;
217: this protocol module calls the first jumping business function SF2, checks whether it normally runs, and if so, then forwards the packet back to SFF2;
218:SFF2 forwards the packet to service node 2, and service node 2 carries out Overlay encapsulation to this message, forwards this message to down hop service node 3;
219: service node 3 receives this message, first decapsulation Overlay layer, will carry the message repeating of SFC business function head to SFF3 process, and SFF3 judges that this is an OAM protocol massages and be TTL is 1, continues to be transmitted to the process of SFCOAM protocol module;
220: this protocol module calls the 3rd and jumps business function SF3, checks whether it normally runs, if so, then obtains the business information of SF3, resource information, deferred message etc., be encapsulated in the TLV of response message, forward the packet back to SFF3; If not, also tectonic response message, carries business function fault message, and forwards the packet back to SFF3;
221:SFF3 forwards the packet to service node 3, and service node 3 carries out Overlay encapsulation to this message, is transmitted to Classifier along IP path;
222:Classifier receives the corresponding message that the 3rd jumps service node, and whether Trace is successful to be shown to operator, if success, shows the information got; If send unsuccessful, display failure cause.
Obviously, those skilled in the art should be understood that, above-mentioned of the present invention each module or each step can realize with general calculation element, they can concentrate on single calculation element, or be distributed on network that multiple calculation element forms, alternatively, they can realize with the executable program code of calculation element, thus, they can be stored and be performed by calculation element in the storage device, and in some cases, step shown or described by can performing with the order be different from herein, or they are made into each integrated circuit modules respectively, or the multiple module in them or step are made into single integrated circuit module to realize.Like this, the present invention is not restricted to any specific hardware and software combination.
The foregoing is only the preferred embodiments of the present invention, be not limited to the present invention, for a person skilled in the art, the present invention can have various modifications and variations.Within the spirit and principles in the present invention all, any amendment done, equivalent replacement, improvement etc., all should be included within protection scope of the present invention.
Claims (20)
1. an Operations, Administration and Maintenance OAM message processing method, is characterized in that, comprising:
Source service node determines the OAM message sent on business function chain SFC, wherein, described OAM message comprises: load p ayload, OAM message head, business function heading, and wherein, described OAM message adopts predetermined SFCOAM network terminal slogan carrying;
The described OAM message be carried on described predetermined SFCOAM network terminal slogan is sent to the object service node process on described SFC by described source service node.
2. method according to claim 1, is characterized in that, described OAM message one of adopts following form at least:
Payload, OAM message head, business function heading, wherein, SFCOAM type is carried in described OAM message head;
Payload, OAM message head, business function heading, wherein, SFCOAM type is carried in described business function heading.
3. method according to claim 1, is characterized in that, the SFCOAM message based on udp protocol carrying comprises following information one of at least:
UDP source port number, for identifying the UDP destination slogan of SFCOAM message port numbers, for identifying the version information of the version number of SFCOAM message, for identifying the type of message information of SFCOAM message, for the response modes information of identification response message, coded message is returned for what identify failure cause, for the frequency information of identification message transmission frequency, for the information of request message stochastic generation, for the information of the time point that identification message sends, for the information of the time point that identification message receives, for TLV to be expanded in request message, or for the TLV of the business function link information that identifies acquisition in response message, for identifying the filling field information of filling field.
4. method according to claim 3, is characterized in that, after the described OAM message be carried on described predetermined SFCOAM network terminal slogan is sent to the object service node process on described SFC, also comprises:
When the response modes that described SFCOAM message carries is IPv4/IPv6 User Data Protocol UDP message, receive the IPv4/IPv6UDP message that described object service node does not carry business function heading, wherein, the result to obtaining after described OAM message process is carried in described IPv4/IPv6UDP message;
When the response modes that described SFCOAM message carries is SFCOAMUDP message, receive the SFCOAMUDP message that described object service node sends, wherein, described SFCOAMUDP message carries the result to obtaining after described OAM message process.
5. method according to any one of claim 1 to 4, is characterized in that,
Described source service node is one of them service node on business categorizing device or business function chain.
6. an Operations, Administration and Maintenance OAM message processing method, is characterized in that, comprising:
Object service node is received in the OAM message that business function chain SFC sends, and wherein, described OAM message comprises: load p ayload, OAM message head, business function heading, and wherein, OAM message adopts predetermined SFCOAM network terminal slogan carrying;
Described object service node processes the described OAM message received.
7. method according to claim 6, is characterized in that, described OAM message one of adopts following form at least:
Payload, OAM message head, business function heading, wherein, SFCOAM type is carried in described OAM message head;
Payload, OAM message head, business function heading, wherein, SFCOAM type is carried in described business function heading.
8. method according to claim 6, is characterized in that, the SFCOAM message based on udp protocol carrying comprises following information one of at least:
UDP source port number, for identifying the UDP destination slogan of SFCOAM message port numbers, for identifying the version information of the version number of SFCOAM message, for identifying the type of message information of SFCOAM message, for the response modes information of identification response message, coded message is returned for what identify failure cause, for the frequency information of identification message transmission frequency, for the information of request message stochastic generation, for the information of the time point that identification message sends, for the information of the time point that identification message receives, for TLV to be expanded in request message, or for the TLV of the business function link information that identifies acquisition in response message, for identifying the filling field information of filling field.
9. method according to claim 6, is characterized in that, after described object service node processes the described OAM message received, also comprises:
When the response modes that described SFCOAM message carries is IPv4/IPv6 User Data Protocol UDP message, the result after described OAM message process will be sent to the source service node or down hop service node that send described OAM message by the IPv4/IPv6UDP message not carrying business function heading;
When the response modes that described SFCOAM message carries is SFCOAMUDP message, the result after described OAM message process will be sent to the source service node or down hop service node that send described OAM message by described SFCOAMUDP message.
10. the method according to any one of claim 6 to 9, is characterized in that,
Described object service node is the combination of all the other service nodes on business function chain except described source service node or multiple service node.
11. 1 kinds of Operations, Administration and Maintenance OAM message processing unit, is characterized in that, be arranged in source service node, comprise:
Determination module, for determining the OAM message sent on business function chain SFC, wherein, described OAM message comprises: load p ayload, OAM message head, business function heading, wherein, described OAM message adopts predetermined SFCOAM network terminal slogan carrying;
First sending module, for sending to the object service node process on described SFC by the described OAM message be carried on described predetermined SFCOAM network terminal slogan.
12. devices according to claim 11, is characterized in that, described OAM message one of adopts following form at least:
Payload, OAM message head, business function heading, wherein, SFCOAM type is carried in described OAM message head;
Payload, OAM message head, business function heading, wherein, SFCOAM type is carried in described business function heading.
13. devices according to claim 11, is characterized in that, the SFCOAM message based on udp protocol carrying comprises following information one of at least:
UDP source port number, for identifying the UDP destination slogan of SFCOAM message port numbers, for identifying the version information of the version number of SFCOAM message, for identifying the type of message information of SFCOAM message, for the response modes information of identification response message, coded message is returned for what identify failure cause, for the frequency information of identification message transmission frequency, for the information of request message stochastic generation, for the information of the time point that identification message sends, for the information of the time point that identification message receives, for TLV to be expanded in request message, or for the TLV of the business function link information that identifies acquisition in response message, for identifying the filling field information of filling field.
14. devices according to claim 13, is characterized in that, also comprise:
First receiver module, when response modes for carrying at described SFCOAM message is IPv4/IPv6 User Data Protocol UDP message, receive the IPv4/IPv6UDP message that described object service node does not carry business function heading, wherein, the result to obtaining after described OAM message process is carried in described IPv4/IPv6UDP message;
Second receiver module, when response modes for carrying at described SFCOAM message is SFCOAMUDP message, receive the SFCOAMUDP message that described object service node sends, wherein, described SFCOAMUDP message carries the result to obtaining after described OAM message process.
15., according to claim 11 to the device according to any one of 14, is characterized in that,
Described source service node is one of them service node on business categorizing device or business function chain.
16. 1 kinds of Operations, Administration and Maintenance OAM message processing unit, is characterized in that, be arranged in object service node, comprise:
3rd receiver module, for being received in the OAM message that business function chain SFC sends, wherein, described OAM message comprises: load p ayload, OAM message head, business function heading, and wherein, OAM message adopts predetermined SFCOAM network terminal slogan carrying;
Processing module, for processing the described OAM message received.
17. devices according to claim 16, is characterized in that, described OAM message one of adopts following form at least:
Payload, OAM message head, business function heading, wherein, SFCOAM type is carried in described OAM message head;
Payload, OAM message head, business function heading, wherein, SFCOAM type is carried in described business function heading.
18. devices according to claim 16, is characterized in that, the SFCOAM message based on udp protocol carrying comprises following information one of at least:
UDP source port number, for identifying the UDP destination slogan of SFCOAM message port numbers, for identifying the version information of the version number of SFCOAM message, for identifying the type of message information of SFCOAM message, for the response modes information of identification response message, coded message is returned for what identify failure cause, for the frequency information of identification message transmission frequency, for the information of request message stochastic generation, for the information of the time point that identification message sends, for the information of the time point that identification message receives, for TLV to be expanded in request message, or for the TLV of the business function link information that identifies acquisition in response message, for identifying the filling field information of filling field.
19. devices according to claim 16, is characterized in that, also comprise:
Second sending module, when response modes for carrying at described SFCOAM message is IPv4/IPv6 User Data Protocol UDP message, the result after described OAM message process will be sent to the source service node or down hop service node that send described OAM message by the IPv4/IPv6UDP message not carrying business function heading;
3rd sending module, when response modes for carrying at described SFCOAM message is SFCOAMUDP message, the result after described OAM message process will be sent to the source service node or down hop service node that send described OAM message by described SFCOAMUDP message.
20., according to claim 16 to the device according to any one of 19, is characterized in that,
Described object service node is the combination of all the other service nodes on business function chain except described source service node or multiple service node.
Priority Applications (2)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201410555236.1A CN105577413B (en) | 2014-10-17 | 2014-10-17 | Operations, Administration and Maintenance OAM message processing method and processing device |
| PCT/CN2014/092178 WO2016058245A1 (en) | 2014-10-17 | 2014-11-25 | Processing method and apparatus for operation, administration and maintenance (oam) message |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201410555236.1A CN105577413B (en) | 2014-10-17 | 2014-10-17 | Operations, Administration and Maintenance OAM message processing method and processing device |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN105577413A true CN105577413A (en) | 2016-05-11 |
| CN105577413B CN105577413B (en) | 2019-09-10 |
Family
ID=55746008
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201410555236.1A Expired - Fee Related CN105577413B (en) | 2014-10-17 | 2014-10-17 | Operations, Administration and Maintenance OAM message processing method and processing device |
Country Status (2)
| Country | Link |
|---|---|
| CN (1) | CN105577413B (en) |
| WO (1) | WO2016058245A1 (en) |
Cited By (8)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN108512675A (en) * | 2017-02-25 | 2018-09-07 | 华为技术有限公司 | A kind of method, apparatus of network diagnosis, control node and network node |
| CN109218058A (en) * | 2017-07-06 | 2019-01-15 | 中国电信股份有限公司 | Acquisition methods, system and the computer readable storage medium of OAM Information |
| CN111884934A (en) * | 2016-07-01 | 2020-11-03 | 华为技术有限公司 | Method, device and system for forwarding message in Service Function Chain (SFC) |
| CN112804075A (en) * | 2019-11-14 | 2021-05-14 | 华为技术有限公司 | Method, device and system for sending message and receiving message for OAM (operation administration and maintenance) |
| CN113055289A (en) * | 2016-07-01 | 2021-06-29 | 华为技术有限公司 | Message forwarding method, device and system based on Service Function Chain (SFC) |
| CN113497758A (en) * | 2020-04-03 | 2021-10-12 | 华为技术有限公司 | Service execution method, device and system |
| WO2022222544A1 (en) * | 2021-04-21 | 2022-10-27 | 华为技术有限公司 | Method and apparatus for operation administration and maintenance (oam) detection |
| WO2023030202A1 (en) * | 2021-09-01 | 2023-03-09 | 华为技术有限公司 | Path fault detection method, apparatus and system, network device and storage medium |
Families Citing this family (26)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US9794379B2 (en) | 2013-04-26 | 2017-10-17 | Cisco Technology, Inc. | High-efficiency service chaining with agentless service nodes |
| USRE48131E1 (en) | 2014-12-11 | 2020-07-28 | Cisco Technology, Inc. | Metadata augmentation in a service function chain |
| US9660909B2 (en) | 2014-12-11 | 2017-05-23 | 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 |
| 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 |
| US10225270B2 (en) | 2016-08-02 | 2019-03-05 | Cisco Technology, Inc. | Steering of cloned traffic in a service function chain |
| 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 |
| US10884807B2 (en) | 2017-04-12 | 2021-01-05 | Cisco Technology, Inc. | Serverless computing and task scheduling |
| US10257033B2 (en) | 2017-04-12 | 2019-04-09 | Cisco Technology, Inc. | Virtualized network functions and service chaining in serverless computing infrastructure |
| US10333855B2 (en) | 2017-04-19 | 2019-06-25 | 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 |
| 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 |
| US10673698B2 (en) | 2017-07-21 | 2020-06-02 | 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 |
| US10666612B2 (en) | 2018-06-06 | 2020-05-26 | Cisco Technology, Inc. | Service chains for inter-cloud traffic |
| 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 |
Citations (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN102185780A (en) * | 2011-05-12 | 2011-09-14 | 中兴通讯股份有限公司 | Operation, administration and maintenance (OAM) message processing method and device |
| 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 |
Family Cites Families (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| WO2012142753A1 (en) * | 2011-04-20 | 2012-10-26 | 华为技术有限公司 | Method and device for monitoring ip bearer network performance |
| CN104052623A (en) * | 2014-06-25 | 2014-09-17 | 成都广达电子股份有限公司 | Message processing method and message processing system in Ethernet passive optical network |
-
2014
- 2014-10-17 CN CN201410555236.1A patent/CN105577413B/en not_active Expired - Fee Related
- 2014-11-25 WO PCT/CN2014/092178 patent/WO2016058245A1/en active Application Filing
Patent Citations (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN102185780A (en) * | 2011-05-12 | 2011-09-14 | 中兴通讯股份有限公司 | Operation, administration and maintenance (OAM) message processing method and device |
| 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 |
Non-Patent Citations (1)
| Title |
|---|
| P. QUINN等: "Network Service Heade draft-quinn-sfc-nsh-03.txt", 《NETWORK WORKING GROUP INTERNET-DRAFT》 * |
Cited By (17)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US11516130B2 (en) | 2016-07-01 | 2022-11-29 | Huawei Technologies Co., Ltd. | Service function chaining SFC-based packet forwarding method, apparatus, and system |
| US11895026B2 (en) | 2016-07-01 | 2024-02-06 | Huawei Technologies Co., Ltd. | Service function chaining SFC-based packet forwarding method, apparatus, and system |
| CN111884934A (en) * | 2016-07-01 | 2020-11-03 | 华为技术有限公司 | 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 |
| US11671364B2 (en) | 2016-07-01 | 2023-06-06 | Huawei Technologies Co., Ltd. | Method, apparatus, and system for forwarding packet in service function chaining SFC |
| CN113055289A (en) * | 2016-07-01 | 2021-06-29 | 华为技术有限公司 | Message forwarding method, device and system based on Service Function Chain (SFC) |
| CN113055290A (en) * | 2016-07-01 | 2021-06-29 | 华为技术有限公司 | Message forwarding method, device and system based on Service Function Chain (SFC) |
| CN111884934B (en) * | 2016-07-01 | 2021-07-09 | 华为技术有限公司 | Method, device and system for forwarding message in Service Function Chain (SFC) |
| US11075839B2 (en) | 2016-07-01 | 2021-07-27 | Huawei Technologies Co., Ltd. | Method, apparatus, and system for forwarding packet in service function chaining SFC |
| CN108512675B (en) * | 2017-02-25 | 2021-06-15 | 华为技术有限公司 | Network diagnosis method and device, control node and network node |
| CN108512675A (en) * | 2017-02-25 | 2018-09-07 | 华为技术有限公司 | A kind of method, apparatus of network diagnosis, control node and network node |
| CN109218058A (en) * | 2017-07-06 | 2019-01-15 | 中国电信股份有限公司 | Acquisition methods, system and the computer readable storage medium of OAM Information |
| CN112804075A (en) * | 2019-11-14 | 2021-05-14 | 华为技术有限公司 | Method, device and system for sending message and receiving message for OAM (operation administration and maintenance) |
| CN113497758A (en) * | 2020-04-03 | 2021-10-12 | 华为技术有限公司 | Service execution method, device and system |
| CN113497758B (en) * | 2020-04-03 | 2023-02-14 | 华为技术有限公司 | Service execution method, device and system |
| WO2022222544A1 (en) * | 2021-04-21 | 2022-10-27 | 华为技术有限公司 | Method and apparatus for operation administration and maintenance (oam) detection |
| WO2023030202A1 (en) * | 2021-09-01 | 2023-03-09 | 华为技术有限公司 | Path fault detection method, apparatus and system, network device and storage medium |
Also Published As
| Publication number | Publication date |
|---|---|
| CN105577413B (en) | 2019-09-10 |
| WO2016058245A1 (en) | 2016-04-21 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN105577413A (en) | OAM (Operation, Administration and Management) message processing method and device | |
| CN112165725B (en) | Message processing method and device | |
| CN108737128B (en) | Method and device for realizing in-band operation management maintenance IOAM | |
| US9832130B2 (en) | Data packet routing method and device | |
| US20200396162A1 (en) | Service function chain sfc-based communication method, and apparatus | |
| CN102404197B (en) | Data path processing information included in the pseudowire layer of packets | |
| CN105577416B (en) | Service function chain operation, management and maintenance method and node equipment | |
| CN101595686B (en) | Triggering flow analysis at intermediary devices | |
| CN110535768B (en) | Multicast data transmission method and related equipment | |
| CN107786437B (en) | Message forwarding method and device | |
| CN105515816B (en) | Processing method and device for detecting hierarchical information | |
| CN108566336A (en) | A kind of network path acquisition methods and equipment | |
| WO2016050177A1 (en) | Pmtu determination method, network device and system | |
| US9313090B2 (en) | Tunnel fault detection method and traffic engineering node | |
| CN111130982B (en) | Message forwarding method and device, gateway equipment and readable storage medium | |
| CN106453204B (en) | Method and device for processing data message | |
| CN106789650B (en) | Wide area network acceleration method and device based on IP | |
| CN110224916B (en) | Message processing method and device and message packaging method, device and system | |
| CN103986637B (en) | A kind of error message processing method and tunnel device | |
| CN107666671B (en) | Method and device for detecting wrong connection based on TWAMP | |
| CN111654440B (en) | Intelligent routing method, electronic equipment and storage medium | |
| CN114006854A (en) | Communication method and network equipment | |
| CN101150510B (en) | A method and device for realizing GRE protocol compatible IPinIP protocol | |
| CN111435948A (en) | Method for transmitting message in network and network equipment | |
| CN106656786A (en) | Flow protection method and device |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| C06 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant | ||
| CF01 | Termination of patent right due to non-payment of annual fee |
Granted publication date: 20190910 Termination date: 20201017 |
|
| CF01 | Termination of patent right due to non-payment of annual fee |