CN105577413B - Operations, Administration and Maintenance OAM message processing method and processing device - Google Patents
Operations, Administration and Maintenance OAM message processing method and processing device Download PDFInfo
- Publication number
- CN105577413B CN105577413B CN201410555236.1A CN201410555236A CN105577413B CN 105577413 B CN105577413 B CN 105577413B CN 201410555236 A CN201410555236 A CN 201410555236A CN 105577413 B CN105577413 B CN 105577413B
- Authority
- CN
- China
- Prior art keywords
- message
- oam
- sfc
- information
- service node
- 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.)
- Expired - Fee Related
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
Landscapes
- Engineering & Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Data Exchanges In Wide-Area Networks (AREA)
Abstract
The invention discloses a kind of Operations, Administration and Maintenance OAM message processing method and processing devices, wherein, this method comprises: source service node determines the OAM message for sending on business function chain SFC, wherein, OAM message includes: load p ayload, OAM message head, business function heading, wherein, OAM message is carried using scheduled SFC OAM network port number；The OAM message being carried on scheduled SFC OAM network port number is sent to the processing of the purpose service node on SFC by source service node, through the invention, SFC OAM message content can not be determined by solving presence in the related technology, and the problem of what agreement the message is carried based on, and then reaches and a kind of complete S FC OAM message has been determined, and improved the effect of SFC OAM scalability.
Description
Technical field
The present invention relates to the communications fields, in particular to a kind of Operations, Administration and Maintenance (Operation
Administration and Maintenance, referred to as OAM) message processing method and device.
Background technique
Since data center network is to after Overlay network Development, network edge becomes virtual network and Physical Network
The separation of network, wherein network edge can be Server or ToR, and may be Gateway.However Overlay technology
There is no all problems are solved, also many Middleware, such as firewall/load balancer in data center, these are set
It is standby to be all based on customer service to handle data, if passing through these equipment by tunnel, it is clear that be not all right.
This deployment model of data center, it is desirable that virtual firewall/load balancer can be disposed arbitrarily in a network,
It is namely unrelated with network topology.New problem in this way is, how flow can flexibly be passed through virtual firewall/load balancing
Is device handled? the service processing functions such as these virtual firewall/load balancers are taken independently of former network topology by standard
Device be engaged in realize.
In the related art, service processing functions, referred to as business function such as virtual firewall/load balancer/gateways
(Service Function, referred to as SF), and flow passes through the processing of a series of SF, forms business function chain (Service
Function Chaining, referred to as SFC).Business function chain is a series of ordered arrangement of abstract business functions, specifically
The sequential combination of which SFFs and/or which SFs that service traffics are passed through on earth when forwarding, SFC are not defined.Fig. 1 is phase
The exemplary diagram of SFC in the technology of pass is also business chain Service as shown in Figure 1, solid line and dotted line indicate two SFC sometimes
Chain.The frame of SFC is illustrated below.
The SFC can be divided into such as lower component:
1. business is superimposed (Service Overlay), i.e., the Overlay (superposition) that each business function node needs to communicate
Technology；
2. general service controls plane (Generic Service Control Plane, referred to as GSCP), SFC is formed
Controller；
3. business classifier (Service Classifier, referred to as SC) needs to flow identification into passerby, then specific
Stream, carry out specific SFC processing；
4, business function (Service Function, referred to as SF) carries out the component of business processing to data message；
5. business function transponder (Service Function Forwarder, referred to as SFF), is responsible for same business section
Forwarding between the multiple SFs in inside of point.The data message of Overlay is by the forwarded device NF encapsulation of service node, solution
After outer layer overlay layers of encapsulation, mainly it is packaged, decapsulates on SFF component, updating business function heading (Network
Service Header, referred to as NSH).Fig. 2 is the message format schematic diagram of business function heading in the related technology, such as Fig. 2
It is shown；
6. forwarded device (Network Forwarder, referred to as NF), the inside for being responsible for same service node is multiple
Forwarding between SFFs；And the data message of Overlay is packaged, decapsulates Overlay layers；Meanwhile it handling different
Forwarding between service node；
Business function path 7. (Service Function Path, referred to as SFP), Fig. 3 is business function in the related technology
Can path schematic diagram, as shown in figure 3, SFP be since classifier, by several orderly specific business function examples,
The business processing path to arrive at the destination.In some cases, general service control platform GSCP can not know on the way
All business function examples passed through, such as load sharing scene or business service grade scene etc., at this point, being located at abstract
This business function between path that the orderly srvice instance that business function chain SFC and true specific flow forwarding are passed through is constituted
The description of energy chain, also referred to as business function path.One business function chain may include multiple business function paths, different
Business function path corresponds to different strategies.
8. controlling plane metadata (Dataplane Metadata), this is a big feature, and metadata (Metadata) permits
Perhaps each business function node, can intercourse information, reach certain business processing purpose.
In conclusion SFC can separate network equipment business function and forwarding, to realize business function
Operation independent and processing promote the forwarding performance of the network equipment.
OAM technology is the network transmission technology for network connectivty detection, fault location, investigation, and is broken down
When, it is capable of providing the trigger mechanism of pretection switch.It contains connectivity of link detection (Connectivity
Verification, referred to as CV) mechanism, Ping mechanism and Trace mechanism.For different carrying fidonetFidos, there is phase
The OAM mechanism answered.For example, Ethernet has ether OAM agreement, IP network has IP OAM agreement, and MPLS network has MPLS OAM.
Wherein, IP Ping and IP the Traceroute mechanism in IP OAM is based on ICMP agreement.Wherein, IP
Ping realizes request request and response reply message by the field of the type of extension ICMP agreement；IP Traceroute
The request request message of Traceroute is realized by the ttl value in modification IP Ping request message, it is super by TTL
The ICMP error message of phase realizes the response reply message of Traceroute；But by ICMP carrying, there are two large problems: 1.
It is related to two kinds IP layers of agreement, is that ICMPv4 and ICMPv6 go to expand when extending SFC OAM from two protocol levels respectively
Exhibition seems slightly cumbersome；2.ICMP message is inconvenient to be used to extend to carry Trace response message.
In addition, LSP Ping and LSP the Trace mechanism of MPLS OAM is to use destination slogan based on udp protocol
3503.Since it is desired that considering to different types of LSP (for example, IPv4 LDP LSP, IPv6LDP LSP, IPv4 RSVP
LSP, IPv6 RSVP LSP, PW LSP etc.) different LSP Ping and LSP Trace is carried out, it extends for convenience, LSP
Ping and LSP Trace does not use Ping and Traceroute extension based on ICMP mechanism, but is carried out based on udp protocol
Extension.
Fig. 4 is SFC OAM technological frame schematic diagram in the related technology, as shown in figure 4, the technological frame of SFC OAM is main
For diagnosing the link circuit condition between business function chain or business function.One such implementation is as shown in figure 5, Fig. 5
It is the schematic diagram of SFC OAM message format one in the related technology, as shown in figure 5, reserving one in business function heading NSH
Field is OAM message and OAM message type for identifying；Another implementation is as shown in fig. 6, Fig. 6 is in the related technology
The schematic diagram of SFC OAM message format two, as shown in fig. 6,1 Bit is reserved in business function heading NSH, for identifying
It is OAM message, until then which type of OAM message, is placed in the message other than business function heading NSH.But no matter
Which kind of scheme is all not involved with specific SFC OAM message content, is carried on what protocol massages on earth, is ICMP
The extension of message or the extension of UDP message or other.
Therefore, in the related art, SFC OAM message content can not be determined by existing, and should based on what agreement carrying
The problem of message.
Summary of the invention
The present invention provides a kind of Operations, Administration and Maintenance OAM message processing method and processing devices, at least to solve related skill
The problem of in art in the presence of that can not determine SFC OAM message content, and what agreement to carry the message based on.
According to an aspect of the invention, there is provided a kind of Operations, Administration and Maintenance OAM message processing method, comprising: source
Service node is held to determine the OAM message for sending on business function chain SFC, wherein the OAM message includes: load
Payload, OAM message head, business function heading, wherein the OAM message uses scheduled SFC OAM network port number
Carrying；The OAM message being carried on the scheduled SFC OAM network port number is sent to by the source service node
Purpose service node processing on the SFC.
Preferably, the OAM message is using at least one following format: Payload, OAM message head, business function message
Head, wherein SFC OAM type is carried in the OAM message head；Payload, OAM message head, business function heading,
In, SFC OAM type is carried in the business function heading.
The SFC OAM message for being preferably based on udp protocol carrying includes at least one following information: UDP source port number,
The version of version number for identifying the UDP destination slogan of SFC OAM message port numbers, for identifying SFC OAM message is believed
Breath, the type of message information for identifying SFC OAM message, the response modes information for identifying response message, for identifying
The return encoded information of failure cause for identification message sends the frequency information of frequency, generates at random for request message
Information, for identification message send time point information, for identification message received time point information, for request report
TLV to be extended in text, or the business function link information for identifying acquisition in response message TLV, for identify fill out
Fill the filling field information of field.
Preferably, the OAM message being carried on the scheduled SFC OAM network port number is sent to it is described
On SFC purpose service node processing after, further includes: the SFC OAM message carry response modes be IPv4/IPv6
When User Data Protocol UDP message, the IPv4/IPv6 that the purpose service node does not carry business function heading is received
UDP message, wherein carried in the IPv4/IPv6 UDP message to the processing result obtained after OAM message processing；
When the response modes that the SFC OAM message carries are SFC OAM UDP message, receive the purpose service node and send
SFC OAM UDP message, wherein the SFC OAM UDP message is carried to the processing that obtains after OAM message processing
As a result.
Preferably, the source service node is one of business section on business classifier or business function chain
Point.
According to another aspect of the present invention, a kind of Operations, Administration and Maintenance OAM message processing method is provided, comprising: mesh
Service node receive the OAM message that sends on business function chain SFC, wherein the OAM message includes: load
Payload, OAM message head, business function heading, wherein OAM message is carried using scheduled SFC OAM network port number；
The purpose service node handles the received OAM message.
Preferably, the OAM message is using at least one following format: Payload, OAM message head, business function message
Head, wherein SFC OAM type is carried in the OAM message head；Payload, OAM message head, business function heading,
In, SFC OAM type is carried in the business function heading.
The SFC OAM message for being preferably based on udp protocol carrying includes at least one following information: UDP source port number,
The version of version number for identifying the UDP destination slogan of SFC OAM message port numbers, for identifying SFC OAM message is believed
Breath, the type of message information for identifying SFC OAM message, the response modes information for identifying response message, for identifying
The return encoded information of failure cause for identification message sends the frequency information of frequency, generates at random for request message
Information, for identification message send time point information, for identification message received time point information, for request report
TLV to be extended in text, or the business function link information for identifying acquisition in response message TLV, for identify fill out
Fill the filling field information of field.
After the purpose service node handles the received OAM message, further includes: in the SFC
When the response modes that OAM message carries are IPv4/IPv6 User Data Protocol UDP message, by not carrying business function message
The IPv4/IPv6 UDP message of head is by the OAM message, treated that processing result is sent to sends the source of the OAM message
Hold service node or next-hop service node；It is SFC OAM UDP message in the response modes that the SFC OAM message carries
When, by the way that the SFC OAM UDP message will treated that processing result is sent to sends the OAM and report to the OAM message
The source service node or next-hop service node of text.
Preferably, the purpose service node is remaining one in addition to the source service node on business function chain
The combination of service node or multiple service nodes.
According to another aspect of the present invention, a kind of Operations, Administration and Maintenance OAM message processing unit is provided, source is located at
It holds in service node, comprising: determining module, for determining the OAM message for sending on business function chain SFC, wherein institute
Stating OAM message includes: load p ayload, OAM message head, business function heading, wherein the OAM message is using scheduled
The carrying of SFC OAM network port number；First sending module, for the scheduled SFC OAM network port number will to be carried on
The OAM message be sent to the purpose service node on the SFC processing.
Preferably, the OAM message is using at least one following format: Payload, OAM message head, business function message
Head, wherein SFC OAM type is carried in the OAM message head；Payload, OAM message head, business function heading,
In, SFC OAM type is carried in the business function heading.
The SFC OAM message for being preferably based on udp protocol carrying includes at least one following information: UDP source port number,
The version of version number for identifying the UDP destination slogan of SFC OAM message port numbers, for identifying SFC OAM message is believed
Breath, the type of message information for identifying SFC OAM message, the response modes information for identifying response message, for identifying
The return encoded information of failure cause for identification message sends the frequency information of frequency, generates at random for request message
Information, for identification message send time point information, for identification message received time point information, for request report
TLV to be extended in text, or the business function link information for identifying acquisition in response message TLV, for identify fill out
Fill the filling field information of field.
Preferably, device further include: the first receiving module, the response modes for being carried in the SFC OAM message
When for IPv4/IPv6 User Data Protocol UDP message, receives the purpose service node and do not carry business function heading
IPv4/IPv6 UDP message, wherein carry in the IPv4/IPv6 UDP message and to be obtained to after OAM message processing
Processing result；Second receiving module, when the response modes for carrying in the SFC OAM message are SFC OAM UDP message,
Receive the SFC OAM UDP message that the purpose service node is sent, wherein the SFC OAM UDP message carries pair
The processing result obtained after the OAM message processing.
Preferably, the source service node is one of business section on business classifier or business function chain
Point.
It is according to the present invention also on the one hand to provide a kind of Operations, Administration and Maintenance OAM message processing unit, it is located at mesh
Service node in, comprising: third receiving module, for receiving the OAM message sent on business function chain SFC, wherein institute
Stating OAM message includes: load p ayload, OAM message head, business function heading, wherein OAM message uses scheduled SFC
The carrying of OAM network port number；Processing module, for handling the received OAM message.
Preferably, the OAM message is using at least one following format: Payload, OAM message head, business function message
Head, wherein SFC OAM type is carried in the OAM message head；Payload, OAM message head, business function heading,
In, SFC OAM type is carried in the business function heading.
The SFC OAM message for being preferably based on udp protocol carrying includes at least one following information: UDP source port number,
The version of version number for identifying the UDP destination slogan of SFC OAM message port numbers, for identifying SFC OAM message is believed
Breath, the type of message information for identifying SFC OAM message, the response modes information for identifying response message, for identifying
The return encoded information of failure cause for identification message sends the frequency information of frequency, generates at random for request message
Information, for identification message send time point information, for identification message received time point information, for request report
TLV to be extended in text, or the business function link information for identifying acquisition in response message TLV, for identify fill out
Fill the filling field information of field.
Preferably, device further include: the second sending module, the response modes for being carried in the SFC OAM message
When for IPv4/IPv6 User Data Protocol UDP message, by the IPv4/IPv6 UDP message for not carrying business function heading
By to the OAM message, treated that processing result is sent to sends the source service node or next-hop of the OAM message
Service node；Third sending module, when the response modes for carrying in the SFC OAM message are SFC OAM UDP message,
By the way that the SFC OAM UDP message will treated that processing result is sent to sends the OAM message to the OAM message
Source service node or next-hop service node.
Preferably, the purpose service node is remaining one in addition to the source service node on business function chain
The combination of service node or multiple service nodes.
Through the invention, source service node determines the OAM message for sending on business function chain SFC, wherein institute
Stating OAM message includes: load p ayload, OAM message head, business function heading, wherein the OAM message is using scheduled
The carrying of SFC OAM network port number；The source service node will be carried on the scheduled SFC OAM network port number
The OAM message is sent to the processing of the purpose service node on the SFC, and SFC can not be determined by solving presence in the related technology
OAM message content, and the problem of what agreement to carry the message based on, and then reached and a kind of complete S FC OAM has been determined
Message, and improve the effect of SFC OAM scalability.
Detailed description of the invention
The drawings described herein are used to provide a further understanding of the present invention, constitutes part of this application, this hair
Bright illustrative embodiments and their description are used to explain the present invention, and are not constituted improper limitations of the present invention.In the accompanying drawings:
Fig. 1 is the exemplary diagram of SFC in the related technology；
Fig. 2 is the message format schematic diagram of business function heading in the related technology；
Fig. 3 is the schematic diagram in business function path in the related technology；
Fig. 4 is SFC OAM technological frame schematic diagram in the related technology；
Fig. 5 is the schematic diagram of SFC OAM message format one in the related technology；
Fig. 6 is the schematic diagram of SFC OAM message format two in the related technology；
Fig. 7 is the flow chart of Operations, Administration and Maintenance OAM message processing method one according to an embodiment of the present invention；
Fig. 8 is the flow chart of Operations, Administration and Maintenance OAM message processing method two according to an embodiment of the present invention；
Fig. 9 is the structural block diagram of Operations, Administration and Maintenance OAM message processing unit one according to an embodiment of the present invention；
Figure 10 is the preferred structure frame of Operations, Administration and Maintenance OAM message processing unit one according to an embodiment of the present invention
Figure；
Figure 11 is the structural block diagram of Operations, Administration and Maintenance OAM message processing unit two according to an embodiment of the present invention；
Figure 12 is the preferred structure frame of Operations, Administration and Maintenance OAM message processing unit two according to an embodiment of the present invention
Figure；
Figure 13 is the message format schematic diagram of udp protocol carrying SFC OAM message according to an embodiment of the present invention；
Figure 14 is after Overlay according to an embodiment of the present invention is encapsulated based on the complete S FC OAM message after UDP carrying
Form schematic diagram；
Figure 15 is the message format schematic diagram according to an embodiment of the present invention for realizing SFC Ping function；
Figure 16 is the schematic diagram according to an embodiment of the present invention for realizing SFC Trace function.
Specific embodiment
Hereinafter, the present invention will be described in detail with reference to the accompanying drawings and in combination with Examples.It should be noted that not conflicting
In the case of, the features in the embodiments and the embodiments of the present application can be combined with each other.
A kind of Operations, Administration and Maintenance OAM message processing method is provided in the present embodiment, and Fig. 7 is according to the present invention
The flow chart of the Operations, Administration and Maintenance OAM message processing method one of embodiment, as shown in fig. 7, the process includes following step
It is rapid:
Step S702, source service node determine the OAM message for sending on business function chain SFC, wherein OAM
Message includes: load p ayload, OAM message head, business function heading, wherein OAM message uses scheduled SFC OAM net
The carrying of network port numbers；
The OAM message being carried on scheduled SFC OAM network port number is sent to by step S704, source service node
Purpose service node processing on SFC.
Through the above steps, it determines a kind of OAM message, OAM report is carried using scheduled SFC OAM network port number
Text, and the determining OAM message is sent to purpose service node, SFC OAM can not be determined by solving presence in the related technology
Message content, and the problem of what agreement to carry the message based on, and then reached and a kind of complete S FC OAM report has been determined
Text, and improve the effect of SFC OAM scalability.
Above-mentioned OAM message can use multiple format, for example, can be using at least one following format: Payload, OAM
Heading, business function heading, wherein SFC OAM type is carried in OAM message head；Payload, OAM message head, industry
Business function heading, wherein SFC OAM type is carried in business function heading.
It should be noted that carrying the agreement of the SFC OAM message can carry out by taking udp protocol as an example below to be a variety of
Explanation.SFC OAM message based on udp protocol carrying may include at least one following information: UDP source port number, for marking
Know the UDP destination slogan of SFC OAM message port numbers, the version information of version number for identifying SFC OAM message, be used for
Identify the type of message information of SFC OAM message, the response modes information for identifying response message, for identifying failure cause
Return encoded information, for identification message send the frequency information of frequency, the information generated at random for request message, be used for
Identification message send time point information, for identification message received time point information, in request message wait expand
The TLV of exhibition, or business function link information for identifying acquisition in response message TLV, for identifying filling field
Fill field information.
Preferably, in the purpose being sent to the OAM message being carried on scheduled SFC OAM network port number on SFC
After service node processing, the response modes that can also be carried according to SFC OAM message are different, receive source service node hair
The different response messages sent, are exemplified below.
For example, being received when the response modes that SFC OAM message carries are IPv4/IPv6 User Data Protocol UDP message
The IPv4/IPv6 UDP message of business function heading is not carried to purpose service node, wherein IPv4/IPv6 UDP message
In carry to the processing result that obtains after OAM message processing；In another example being SFC in the response modes that SFC OAM message carries
When OAM UDP message, the SFC OAM UDP message of purpose service node transmission is received, wherein SFC OAM UDP message is taken
With the processing result obtained after handling OAM message.And when the response modes that SFC OAM message carries are not reply, i.e.,
The response message of purpose service node transmission is not received.
It should be noted that above-mentioned source service node is one of industry on business classifier or business function chain
Business node.
In the present embodiment, a kind of Operations, Administration and Maintenance OAM message processing method is additionally provided, Fig. 8 is according to this hair
The flow chart of the Operations, Administration and Maintenance OAM message processing method two of bright embodiment, as shown in figure 8, the process includes following step
It is rapid:
Step S802, purpose service node receive the OAM message sent on business function chain SFC, wherein OAM message
It include: load p ayload, OAM message head, business function heading, wherein OAM message uses scheduled SFC OAM network-side
Slogan carrying；
Step S804, purpose service node handle received OAM message.
Through the above steps, by receiving being somebody's turn to do using the carrying of scheduled SFC OAM network port number sent on SFC
OAM message, and the received OAM message is handled, solving presence in the related technology can not determine in SFC OAM message
The problem of holding, and what agreement the message carried based on, and then reached and a kind of complete S FC OAM message has been determined, and
Improve the effect of SFC OAM scalability.
It should be noted that the OAM carried using scheduled SFC OAM network port number sent on receiving SFC
After message, after decapsulating to the OAM message, the port numbers in analytic message are the discovery that SFC OAM message, report to the OAM
Text is handled.
Wherein, OAM message can use multiple format, for example, can be using at least one following format: Payload,
OAM message head, business function heading, wherein SFC OAM type is carried in OAM message head；Payload, OAM message head,
Business function heading, wherein SFC OAM type is carried in business function heading.
Accordingly, which can be carried on various protocols, be illustrated below with being carried on udp protocol.Example
Such as, the SFC OAM message based on the carrying of UPD agreement may include at least one following information: UDP source port number, for identifying
The UDP destination slogan of SFC OAM message port numbers, the version information of version number for identifying SFC OAM message, for marking
Know the type of message information of SFC OAM message, the response modes information for identifying response message, for identifying failure cause
It returns to encoded information, send the frequency information of frequency, the information generated at random for request message for identification message, for marking
Know message send time point information, for identification message received time point information, in request message wait extend
TLV, or business function link information for identifying acquisition in response message TLV, fill out for identifying filling field
Fill field information.
Preferably, it after purpose service node handles received OAM message, can also be reported according to SFC OAM
The response modes that text carries are different, and Xiang Yuanduan service node sends response message, are exemplified below.For example, being reported in SFC OAM
When the response modes that text carries are IPv4/IPv6 User Data Protocol UDP message, by not carrying business function heading
IPv4/IPv6 UDP message by OAM message treated processing result is sent to send OAM message source service node or
Person's next-hop service node；In another example passing through when the response modes that SFC OAM message carries are SFC OAM UDP message
SFC OAM UDP message by OAM message treated processing result is sent to send OAM message source service node or
Next-hop service node.And the response modes carried and SFC OAM message are when not replying, purpose service node receives this
After OAM message, do not have to send response message.
Preferably, purpose service node is remaining service node on business function chain in addition to source service node
Or the combination of multiple service nodes.
Additionally provide a kind of Operations, Administration and Maintenance OAM message processing unit in the present embodiment, the device for realizing
Above-described embodiment and preferred embodiment, the descriptions that have already been made will not be repeated.As used below, term " module " can
To realize the combination of the software and/or hardware of predetermined function.Although device described in following embodiment is preferably come with software
It realizes, but the realization of the combination of hardware or software and hardware is also that may and be contemplated.
Fig. 9 is the structural block diagram of Operations, Administration and Maintenance OAM message processing unit one according to an embodiment of the present invention, such as
Shown in Fig. 9, which is located in source service node, comprising: determining module 92 and the first sending module 94, below to the device
It is illustrated.
Determining module 92, for determining the OAM message for sending on business function chain SFC, wherein OAM message packet
It includes: load p ayload, OAM message head, business function heading, wherein OAM message uses the scheduled SFC OAM network port
Number carrying；First sending module 94 is connected to above-mentioned determining module 92, for that will be carried on the scheduled SFC OAM network port
OAM message on number is sent to the processing of the purpose service node on SFC.
Wherein, OAM message can use multiple format, for example, can be using at least one following format: Payload,
OAM message head, business function heading, wherein SFC OAM type is carried in OAM message head；Payload, OAM message head,
Business function heading, wherein SFC OAM type is carried in business function heading.
The SFC OAM message for being preferably based on udp protocol carrying may include at least one following information: UDP source port
Number, the UDP destination slogan for identifying SFC OAM message port numbers, the version of the version number for identifying SFC OAM message
Information, the type of message information for identifying SFC OAM message, the response modes information for identifying response message, for marking
Know the return encoded information of failure cause, sends the frequency information of frequency for identification message, generated at random for request message
Information, for identification message send time point information, for the information at identification message received time point, for requesting
TLV to be extended in message, or the business function link information for identifying acquisition in response message TLV, for identifying
Fill the filling field information of field.
Figure 10 is the preferred structure frame of Operations, Administration and Maintenance OAM message processing unit one according to an embodiment of the present invention
Figure, as shown in Figure 10, the device further include at least one of: the first receiving module in addition to including all modules shown in Fig. 9
102, the second receiving module 104 is below illustrated the device.
First receiving module 102 is connected to above-mentioned first sending module 94, the response for carrying in SFC OAM message
When mode is IPv4/IPv6 User Data Protocol UDP message, receives purpose service node and do not carry business function heading
IPv4/IPv6 UDP message, wherein carried in IPv4/IPv6 UDP message to the processing knot obtained after OAM message processing
Fruit；Second receiving module 104, is connected to above-mentioned first sending module 94, and the response modes for carrying in SFC OAM message are
When SFC OAM UDP message, the SFC OAM UDP message of purpose service node transmission is received, wherein SFC OAM UDP report
Text is carried to the processing result obtained after OAM message processing.
Preferably, source service node is one of service node on business classifier or business function chain.
Figure 11 is the structural block diagram of Operations, Administration and Maintenance OAM message processing unit two according to an embodiment of the present invention, such as
Shown in Figure 11, which is located in purpose service node, comprising: third receiving module 112 and processing module 114, below to this
Device is illustrated.
Third receiving module 112, for receiving the OAM message sent on business function chain SFC, wherein OAM message packet
It includes: load p ayload, OAM message head, business function heading, wherein OAM message uses the scheduled SFC OAM network port
Number carrying；Processing module 114 is connected to above-mentioned third receiving module 112, for handling received OAM message.
Preferably, above-mentioned OAM message can be using at least one following format: Payload, OAM message head, business function
Heading, wherein SFC OAM type is carried in OAM message head；Payload, OAM message head, business function heading,
In, SFC OAM type is carried in business function heading.
The SFC OAM message for being preferably based on udp protocol carrying includes at least one following information: UDP source port number,
The version of version number for identifying the UDP destination slogan of SFC OAM message port numbers, for identifying SFC OAM message is believed
Breath, the type of message information for identifying SFC OAM message, the response modes information for identifying response message, for identifying
The return encoded information of failure cause for identification message sends the frequency information of frequency, generates at random for request message
Information, for identification message send time point information, for identification message received time point information, for request report
TLV to be extended in text, or the business function link information for identifying acquisition in response message TLV, for identify fill out
Fill the filling field information of field.
Figure 12 is the preferred structure frame of Operations, Administration and Maintenance OAM message processing unit two according to an embodiment of the present invention
Figure, as shown in figure 12, the device further include at least one of in addition to including all modules shown in Figure 11: second sends mould
Block 122, third sending module 124, are below illustrated the device.
Second sending module 122 is connected to above-mentioned processing module 114, the response modes for carrying in SFC OAM message
When for IPv4/IPv6 User Data Protocol UDP message, by the IPv4/IPv6 UDP message for not carrying business function heading
By to OAM message, treated that processing result is sent to sends the source service node or next-hop service node of OAM message；
Third sending module 124 is connected to above-mentioned processing module 114, and the response modes for carrying in SFC OAM message are SFC
When OAM UDP message, by the way that SFC OAM UDP message will treated that processing result is sent to transmission OAM message to OAM message
Source service node or next-hop service node.
Preferably, purpose service node is remaining service node on business function chain in addition to source service node
Or the combination of multiple service nodes.
In view of the above problems in the related art, in the present embodiment, a kind of operation of bearer service function chain, pipe are provided
The method of reason and maintenance packet.By defining a new UDP/TCP port numbers, for carrying the various message of SFC OAM；With
Under by the agreement of carrying be udp protocol for be illustrated.Figure 13 is udp protocol carrying SFC according to an embodiment of the present invention
The message format schematic diagram of OAM message, as shown in figure 13:
Source Port: mark UDP source port number；
Destination Port: mark UDP destination slogan defines a new port numbers in the present embodiment, uses
To carry SFC OAM message；
Version Number: the version number of mark SFC OAM message；
Message Type: mark SFC OAM message type mainly has Ping Request message, Ping Reply report
Text, connectivity Request message, connectivity Reply message etc.；
Reply Mode: identifying the response modes of response message, and response message can be reported by common IPv4/IPv6UDP
Literary response sends message response by business function path SFP；Etc.；
Return Code: carrying in response message, and mark failure cause is (for example, request message mistake, carrying nonrecognition
TLV, business function be operating abnormally etc.)；The field is 0 in request message；
Frequency: for periodic SFC OAM message, which is used for the frequency that identification message is sent；For master
The SFC OAM message (Ping or Trace) of dynamic triggering, the field are 0；
Sender ' s Handle: request message generates at random；The field is consistent with request message in response message；
Timestamp Sent: the time point that identification message is sent；
Timestamp Received: identification message received time point；
TLV: for SFC Ping or SFC Trace, it is contemplated that the information of SFP is included in business function head,
And it is carried to final jump service node on the way, therefore in SFC Ping or SFC Trace request message, it can not
The field is carried, the field is optional, is used for subsequent expansion；For in the response message of SFC Trace, field needs be will acquire
Business function link information or business function chain business function relevant information (for example, bandwidth information, resource information, prolonging
Slow information etc.) promoter of SFC Trace is responded to, therefore need to carry the TLV field, different type corresponds to different letters
Breath；
Padding: mark filling field meets the byte requirement of message needs；
Figure 14 is after Overlay according to an embodiment of the present invention is encapsulated based on the complete S FC OAM message after UDP carrying
Form schematic diagram, as shown in figure 14.
The embodiment of the present invention is described below in conjunction with attached drawing.
Embodiment 1:
In the present embodiment 1, the business function chain of the embodiment based on SFC Ping function include: SF1--- > SF2--- >
SF3；Wherein, Overlay network is IP network.
Firstly, operator configure Relay Mode be by business function path send response message, and from
Classifier starts to carry out the Ping request function in the business function path, then the Ping message lattice issued from Classifier
Formula.Figure 15 is the message format schematic diagram according to an embodiment of the present invention for realizing SFC Ping function, as shown in Figure 15, UDP
It is SFC OAM dedicated port numbers used in head, type of message is request message in SFC Ping request message, and response modes are such as
Upper configuration.In the present embodiment, realize that Ping function includes the following steps:
101:Classifier sends the OAM message in Figure 15, E-Packets to the first jump business in business function path
Node 1；
102: service node 1 decapsulates Overlay layers, and the message for carrying SFC business function head is transmitted at SFF1
Reason, SFF1 judge that this is an OAM Ping protocol massages, are then transmitted to the processing of SFC OAM protocol module；
103: the SFC OAM protocol module calls first to jump business function SF1, checks it whether normal operation, if so,
It then forwards the packet back to SFF1；
104:SFF1 forwards the message to service node 1, and service node 1 carries out Overlay encapsulation to the message, and forwarding should
Message is to next-hop service node 2；
105: if checking that the first jump business function SF1 is not operated normally, constructing Ping response message, carry business
Functional fault information；And it can be to SFF1 by response message forwarding；
The corresponding message is transmitted to service node 1 by 106:SFF1, and service node 1 carries out Overlay encapsulation to the message,
Forward the message to Classifier；
107: service node 2 receives the message, first decapsulates Overlay layers, will carry the report of SFC business function head
Text is transmitted to SFF2 processing, and SFF2 judges that this is an OAM protocol massages, is then transmitted to the processing of SFC OAM protocol module；
108: the SFC OAM protocol module calls second to jump business function SF2, checks it whether normal operation, if so,
It then forwards the packet back to SFF2；
109:SFF2 forwards the message to service node 2, and service node 2 carries out Overlay encapsulation to the message, and forwarding should
Message is to next-hop service node 3；
110: if checking that the second jump business function SF2 is not operated normally, constructing Ping response message, carry business
Functional fault information；And it can be to SFF2 by response message forwarding；
The corresponding message is transmitted to service node 2 by 111:SFF2, and service node 2 carries out Overlay encapsulation to the message,
It is transmitted to service node 1 along reversed path, then forwards the message to Classifier again；
112: service node 3 receives the message, first decapsulates Overlay layers, will carry the report of SFC business function head
Text be transmitted to SFF3 processing, SFF3 judge this be an OAM protocol massages and be business function path final jump, continue turn
Issue the processing of SFC OAM protocol module；
113: the SFC OAM protocol module calls third to jump business function SF3, checks it whether normal operation, if so,
It then constructs Ping response message and forwards the message back to SFF3；If it is not, also construction Ping response message carries failure
Business function fault message；And the message is forwarded back to SFF3；
114:SFF3 forwards the message to service node 3, and service node 3 carries out Overlay encapsulation to the message, along anti-
To path be transmitted to service node 2 and service node 1, then forward the message to Classifier again；
After 115:Classifier receives Ping response message, be shown to operator whether Ping success, if not at
Function is shown to operator's failure cause.
Specific embodiment 2:
In the present embodiment, the business function chain of the specific embodiment based on SFC Trace function include: SF1--- >
SF2--- > SF3, wherein Overlay network is IP network.
Firstly, operator configures Relay Mode to send response message by the path IP, and since Classifier
Trace (path) request function in the business function path is carried out, then the Trace message format issued from Classifier.Figure
16 be the schematic diagram according to an embodiment of the present invention for realizing SFC Trace function, as shown in Figure 16, wherein use in UDP
Be SFC OAM dedicated port numbers, type of message is request message in SFC Trace request message, and response modes as above configure；
The present embodiment includes the following steps:
201:Classifier sends OAM message in Figure 16, and the ttl field being arranged in message is 1, E-Packets to business
The first of feature path jumps service node 1；
202: service node 1 decapsulates Overlay layers, and the message for carrying SFC business function head is transmitted at SFF1
Reason, SFF1 judge that this be an OAM Trace protocol massages and TTL is 1, is then transmitted to SFC OAM protocol module and handles；
203: the SFC OAM protocol module calls first to jump business function SF1, checks it whether normal operation, if so,
Then obtain the business information of SF1, resource information, delay information etc., be encapsulated in the TLV of response message, forward the packet back to
SFF1；If it is not, also constructing response message, business function fault message is carried, and forward the packet back to SFF1；
204:SFF1 forwards the message to service node 1, and service node 1 carries out Overlay encapsulation to the message, along IP
Path is transmitted to Classifier；
205:Classifier receives the corresponding message of the first jump service node, and being shown to operator, whether Trace is successful,
If it is successful, the information that display is got；Meanwhile Classifier construction TTL be 2 SFC Trace message, E-Packet to
The second of business function path jumps service node 1；It sends if it fails, display failure cause；
206: service node 1 receives the message, first decapsulates Overlay layers, will carry the report of SFC business function head
Text is transmitted to SFF1 processing, and SFF1 judges that this is an OAM protocol massages, is then transmitted to the processing of SFC OAM protocol module；Together
When, the ttl value in message can be subtracted 1 by SFF1；
207: the SFC OAM protocol module calls first to jump business function SF1, checks it whether normal operation, if so,
It then forwards the packet back to SFF1；
208:SFF1 forwards the message to service node 1, and service node 1 carries out Overlay encapsulation to the message, and forwarding should
Message is to next-hop service node 2；
209: service node 2 receives the message, first decapsulates Overlay layers, will carry the report of SFC business function head
Text is transmitted to SFF2 processing, and SFF2 judges that this is an OAM protocol massages and is TTL for 1, continues to be transmitted to SFC OAM agreement
Resume module；
210: the SFC OAM protocol module calls second to jump business function SF2, checks it whether normal operation, if so,
Then obtain the business information of SF2, resource information, delay information etc., be encapsulated in the TLV of response message, forward the packet back to
SFF2；If it is not, also constructing response message, business function fault message is carried, and forward the packet back to SFF2；
211:SFF2 forwards the message to service node 2, and service node 2 carries out Overlay encapsulation to the message, along IP
Path is transmitted to Classifier；
212:Classifier receives the corresponding message of the second jump service node, and being shown to operator, whether Trace is successful,
If it is successful, the information that display is got；Meanwhile Classifier construction TTL be 3 SFC Trace message, E-Packet to
The second of business function path jumps service node 1；It sends if it fails, display failure cause；
213: service node 1 receives the message, first decapsulates Overlay layers, will carry the report of SFC business function head
Text is transmitted to SFF1 processing, and SFF1 judges that this is an OAM protocol massages, is then transmitted to the processing of SFC OAM protocol module；Together
When, the ttl value in message can be subtracted 1 by SFF1；
214: the protocol module calls first to jump business function SF1, checks it whether normal operation, if it is, will report
Text forwarding is back to SFF1；
215:SFF1 forwards the message to service node 1, and service node 1 carries out Overlay encapsulation to the message, and forwarding should
Message is to next-hop service node 2；
216: service node 2 receives the message, first decapsulates Overlay layers, will carry the report of SFC business function head
Text is transmitted to SFF2 processing, and SFF2 judges that this is an OAM protocol massages, is then transmitted to the processing of SFC OAM protocol module；Together
When, the ttl value in message can be subtracted 1 by SFF2；
217: the protocol module calls first to jump business function SF2, checks it whether normal operation, if it is, will report
Text forwarding is back to SFF2；
218:SFF2 forwards the message to service node 2, and service node 2 carries out Overlay encapsulation to the message, and forwarding should
Message is to next-hop service node 3；
219: service node 3 receives the message, first decapsulates Overlay layers, will carry the report of SFC business function head
Text is transmitted to SFF3 processing, and SFF3 judges that this is an OAM protocol massages and is TTL for 1, continues to be transmitted to SFC OAM agreement
Resume module；
220: the protocol module calls third to jump business function SF3, checks it whether normal operation, if it is, obtaining
Business information, resource information, delay information of SF3 etc., are encapsulated in the TLV of response message, forward the packet back to SFF3；Such as
Fruit is not also to construct response message, carries business function fault message, and forward the packet back to SFF3；
221:SFF3 forwards the message to service node 3, and service node 3 carries out Overlay encapsulation to the message, along IP
Path is transmitted to Classifier；
222:Classifier receives the corresponding message that third jumps service node, and being shown to operator, whether Trace is successful,
If it is successful, the information that display is got；It sends if it fails, display failure cause.
Obviously, those skilled in the art should be understood that each module of the above invention or each step can be with general
Computing device realize that they can be concentrated on a single computing device, or be distributed in multiple computing devices and formed
Network on, optionally, they can be realized with the program code that computing device can perform, it is thus possible to which they are stored
It is performed by computing device in the storage device, and in some cases, it can be to be different from shown in sequence execution herein
Out or description the step of, perhaps they are fabricated to each integrated circuit modules or by them multiple modules or
Step is fabricated to single integrated circuit module to realize.In this way, the present invention is not limited to any specific hardware and softwares to combine.
The foregoing is only a preferred embodiment of the present invention, is not intended to restrict the invention, for the skill of this field
For art personnel, the invention may be variously modified and varied.All within the spirits and principles of the present invention, made any to repair
Change, equivalent replacement, improvement etc., should all be included in the protection scope of the present invention.
Claims (20)
1. a kind of Operations, Administration and Maintenance OAM message processing method characterized by comprising
Source service node determines OAM message for sending on business function chain SFC, wherein the OAM message include with
It is at least one lower: load p ayload, OAM message head, business function heading, wherein the OAM message uses scheduled SFC
The carrying of OAM network port number；
The OAM message being carried on the scheduled SFC OAM network port number is sent to by the source service node
Purpose service node processing on the SFC.
2. the method according to claim 1, wherein the OAM message is using at least one following format:
Payload, OAM message head, business function heading, wherein SFC OAM type is carried in the OAM message head；
Payload, OAM message head, business function heading, wherein SFC OAM type is carried on the business function heading
In.
3. the method according to claim 1, wherein the SFC OAM message based on udp protocol carrying includes following
At least one information:
UDP source port number, the UDP destination slogan for identifying SFC OAM message port numbers, for identifying SFC OAM message
Version number version information, the type of message information for identifying SFC OAM message, the response mould for identifying response message
Formula information, the return encoded information for identifying failure cause send the frequency information of frequency for identification message, for requesting
Information that message generates at random, the information at the time point sent for identification message, for identification message received time point
Information, for TLV to be extended in request message, or business function link information for identifying acquisition in response message
TLV, the filling field information for identifying filling field.
4. according to the method described in claim 3, it is characterized in that, the scheduled SFC OAM network port will be carried on
The OAM message on number is sent to after the processing of the purpose service node on the SFC, further includes:
When the response modes that the SFC OAM message carries are IPv4/IPv6 User Data Protocol UDP message, institute is received
State the IPv4/IPv6 UDP message that purpose service node does not carry business function heading, wherein the IPv4/IPv6 UDP
It is carried in message to the processing result obtained after OAM message processing；
When the response modes that the SFC OAM message carries are SFC OAM UDP message, the purpose service node is received
The SFC OAM UDP message of transmission, wherein the SFC OAM UDP message is carried to be obtained to after OAM message processing
Processing result.
5. method according to claim 1 to 4, which is characterized in that
The source service node is one of service node on business classifier or business function chain.
6. a kind of Operations, Administration and Maintenance OAM message processing method characterized by comprising
Purpose service node receives the OAM message that sends on business function chain SFC, wherein the OAM message include with down toward
It is one of few: load p ayload, OAM message head, business function heading, wherein OAM message uses scheduled SFC OAM network
Port numbers carrying；
The purpose service node handles the received OAM message.
7. according to the method described in claim 6, it is characterized in that, the OAM message is using at least one following format:
Payload, OAM message head, business function heading, wherein SFC OAM type is carried in the OAM message head；
Payload, OAM message head, business function heading, wherein SFC OAM type is carried on the business function heading
In.
8. according to the method described in claim 6, it is characterized in that, the SFC OAM message based on udp protocol carrying includes following
At least one information:
UDP source port number, the UDP destination slogan for identifying SFC OAM message port numbers, for identifying SFC OAM message
Version number version information, the type of message information for identifying SFC OAM message, the response mould for identifying response message
Formula information, the return encoded information for identifying failure cause send the frequency information of frequency for identification message, for requesting
Information that message generates at random, the information at the time point sent for identification message, for identification message received time point
Information, for TLV to be extended in request message, or business function link information for identifying acquisition in response message
TLV, the filling field information for identifying filling field.
9. according to the method described in claim 6, it is characterized in that, being reported in the purpose service node to the received OAM
After text is handled, further includes:
When the response modes that the SFC OAM message carries are IPv4/IPv6 User Data Protocol UDP message, by not taking
IPv4/IPv6 UDP message with business function heading will treated that processing result is sent to transmission to the OAM message
The source service node or next-hop service node of the OAM message；
When the response modes that the SFC OAM message carries are SFC OAM UDP message, reported by the SFC OAM UDP
Text is by the OAM message, treated that processing result is sent to sends the source service node of the OAM message or next
Jump service node.
10. according to the method described in claim 9, it is characterized in that,
The purpose service node be on business function chain remaining service node in addition to the source service node or
The combination of multiple service nodes.
11. a kind of Operations, Administration and Maintenance OAM message processing unit, which is characterized in that be located in source service node, comprising:
Determining module, for determining OAM message for sending on business function chain SFC, wherein the OAM message includes
At least one of: load p ayload, OAM message head, business function heading, wherein the OAM message is using scheduled
The carrying of SFC OAM network port number；
First sending module, for the OAM message being carried on the scheduled SFC OAM network port number to be sent to
Purpose service node processing on the SFC.
12. device according to claim 11, which is characterized in that the OAM message is using at least one following format:
Payload, OAM message head, business function heading, wherein SFC OAM type is carried in the OAM message head；
Payload, OAM message head, business function heading, wherein SFC OAM type is carried on the business function heading
In.
13. device according to claim 11, which is characterized in that based on udp protocol carrying SFC OAM message include with
At least one lower information:
UDP source port number, the UDP destination slogan for identifying SFC OAM message port numbers, for identifying SFC OAM message
Version number version information, the type of message information for identifying SFC OAM message, the response mould for identifying response message
Formula information, the return encoded information for identifying failure cause send the frequency information of frequency for identification message, for requesting
Information that message generates at random, the information at the time point sent for identification message, for identification message received time point
Information, for TLV to be extended in request message, or business function link information for identifying acquisition in response message
TLV, the filling field information for identifying filling field.
14. device according to claim 13, which is characterized in that further include:
First receiving module, the response modes for carrying in the SFC OAM message are IPv4/IPv6 User Data Protocol
When UDP message, the IPv4/IPv6 UDP message that the purpose service node does not carry business function heading is received, wherein
It is carried in the IPv4/IPv6 UDP message to the processing result obtained after OAM message processing；
Second receiving module receives when the response modes for carrying in the SFC OAM message are SFC OAM UDP message
The SFC OAM UDP message sent to the purpose service node, wherein the SFC OAM UDP message is carried to described
The processing result obtained after OAM message processing.
15. device described in any one of 1 to 14 according to claim 1, which is characterized in that
The source service node is one of service node on business classifier or business function chain.
16. a kind of Operations, Administration and Maintenance OAM message processing unit, which is characterized in that be located in purpose service node, comprising:
Third receiving module, for receiving the OAM message sent on business function chain SFC, wherein the OAM message includes
At least one of: load p ayload, OAM message head, business function heading, wherein OAM message uses scheduled SFC
The carrying of OAM network port number；
Processing module, for handling the received OAM message.
17. device according to claim 16, which is characterized in that the OAM message is using at least one following format:
Payload, OAM message head, business function heading, wherein SFC OAM type is carried in the OAM message head；
Payload, OAM message head, business function heading, wherein SFC OAM type is carried on the business function heading
In.
18. device according to claim 16, which is characterized in that based on udp protocol carrying SFC OAM message include with
At least one lower information:
UDP source port number, the UDP destination slogan for identifying SFC OAM message port numbers, for identifying SFC OAM message
Version number version information, the type of message information for identifying SFC OAM message, the response mould for identifying response message
Formula information, the return encoded information for identifying failure cause send the frequency information of frequency for identification message, for requesting
Information that message generates at random, the information at the time point sent for identification message, for identification message received time point
Information, for TLV to be extended in request message, or business function link information for identifying acquisition in response message
TLV, the filling field information for identifying filling field.
19. device according to claim 16, which is characterized in that further include:
Second sending module, the response modes for carrying in the SFC OAM message are IPv4/IPv6 User Data Protocol
When UDP message, by do not carry business function heading IPv4/IPv6 UDP message will treated to the OAM message
Processing result is sent to the source service node or next-hop service node for sending the OAM message；
Third sending module passes through when the response modes for carrying in the SFC OAM message are SFC OAM UDP message
The SFC OAM UDP message is by the OAM message, treated that processing result is sent to sends the source of the OAM message
Service node or next-hop service node.
20. device according to claim 19, which is characterized in that
The purpose service node be on business function chain remaining service node in addition to the source service node or
The combination of multiple service nodes.
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 CN105577413A (en) | 2016-05-11 |
| CN105577413B true 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) |
Families Citing this family (34)
| 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 |
| CN111884933B (en) * | 2016-07-01 | 2021-07-09 | 华为技术有限公司 | Method, device and system for forwarding message in Service Function Chain (SFC) |
| WO2018000443A1 (en) * | 2016-07-01 | 2018-01-04 | 华为技术有限公司 | Service function chaining (sfc)-based packet forwarding method, device and system |
| US10419550B2 (en) | 2016-07-06 | 2019-09-17 | Cisco Technology, Inc. | Automatic service function validation in a virtual network environment |
| US10320664B2 (en) | 2016-07-21 | 2019-06-11 | Cisco Technology, Inc. | Cloud overlay for operations administration and management |
| US10218616B2 (en) * | 2016-07-21 | 2019-02-26 | 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 |
| US10218593B2 (en) | 2016-08-23 | 2019-02-26 | Cisco Technology, Inc. | Identifying sources of packet drops in a service function chain environment |
| CN108512675B (en) * | 2017-02-25 | 2021-06-15 | 华为技术有限公司 | Network diagnosis method and device, control node and network node |
| US10225187B2 (en) | 2017-03-22 | 2019-03-05 | 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 |
| 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 |
| 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 |
| CN109218058B (en) * | 2017-07-06 | 2021-09-14 | 中国电信股份有限公司 | Method and system for acquiring OAM information and computer readable storage medium |
| 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 |
| 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 |
| CN114143380B (en) * | 2022-01-04 | 2023-06-09 | 烽火通信科技股份有限公司 | Method and system for solving inconsistent OAM and service of SRv tail node power down scene |
| CN115766536B (en) * | 2022-11-11 | 2024-08-27 | 北京百度网讯科技有限公司 | 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 |
|---|
| Network Service Heade draft-quinn-sfc-nsh-03.txt;P. Quinn等;《Network Working Group Internet-Draft》;https://tools.ietf.org/html/draft-quinn-sfc-nsh-03;20140703;全文 |
Also Published As
| Publication number | Publication date |
|---|---|
| WO2016058245A1 (en) | 2016-04-21 |
| CN105577413A (en) | 2016-05-11 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN105577413B (en) | Operations, Administration and Maintenance OAM message processing method and processing device | |
| US10742488B2 (en) | Detecting link faults in network paths that include link aggregation groups (LAGs) | |
| CN111953604B (en) | Method and device for providing business service for business flow | |
| EP3346661B1 (en) | Path detection method and device | |
| US9497107B1 (en) | Seamless path monitoring and rapid fault isolation using bidirectional forwarding detection in a network environment | |
| JP4840236B2 (en) | Network system and node device | |
| US8797886B1 (en) | Verification of network paths using two or more connectivity protocols | |
| CN105577416B (en) | Service function chain operation, management and maintenance method and node equipment | |
| US8117301B2 (en) | Determining connectivity status for unnumbered interfaces of a target network device | |
| CN105515816B (en) | Processing method and device for detecting hierarchical information | |
| CN107248941A (en) | A kind of method and apparatus in detection path | |
| CN107465565A (en) | Link test method and apparatus and system | |
| CN104378249B (en) | Detection method, device, system, controller and the gateway of data link | |
| EP3245768B1 (en) | Bidirectional forwarding detection over network virtualization using generic routing encapsulation | |
| CN103746881B (en) | Neighbor state detection method and device in EVI networks | |
| US10623278B2 (en) | Reactive mechanism for in-situ operation, administration, and maintenance traffic | |
| CN108667709B (en) | Message forwarding method and device | |
| CN101490661A (en) | Methods and apparatus for providing optimal identification and processing of layer 3 control channels | |
| CN110943879B (en) | Network performance monitoring using proactive measurement protocol and relay mechanisms | |
| US8971195B2 (en) | Querying health of full-meshed forwarding planes | |
| EP3203685A1 (en) | Method and apparatus for implementing operations, administration and maintenance function | |
| Xhonneux et al. | Flexible failure detection and fast reroute using eBPF and SRv6 | |
| KR20230041727A (en) | Tunnel BFD session establishment method and apparatus | |
| CN110380966A (en) | A kind of method and its relevant device finding forward-path | |
| EP3065364B1 (en) | Synchronization method and apparatus for interface parameters |
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 | ||
| CF01 | Termination of patent right due to non-payment of annual fee |
Granted publication date: 20190910 Termination date: 20201017 |