WO2015184740A1 - 检测层次信息的处理方法及装置 - Google Patents

检测层次信息的处理方法及装置 Download PDF

Info

Publication number
WO2015184740A1
WO2015184740A1 PCT/CN2014/092070 CN2014092070W WO2015184740A1 WO 2015184740 A1 WO2015184740 A1 WO 2015184740A1 CN 2014092070 W CN2014092070 W CN 2014092070W WO 2015184740 A1 WO2015184740 A1 WO 2015184740A1
Authority
WO
WIPO (PCT)
Prior art keywords
service
sfc oam
information
sfc
oam detection
Prior art date
Application number
PCT/CN2014/092070
Other languages
English (en)
French (fr)
Inventor
王翠
孟伟
Original Assignee
中兴通讯股份有限公司
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 中兴通讯股份有限公司 filed Critical 中兴通讯股份有限公司
Publication of WO2015184740A1 publication Critical patent/WO2015184740A1/zh

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L43/00—Arrangements for monitoring or testing data switching networks

Definitions

  • the present invention relates to the field of communications, and in particular to a method and apparatus for processing hierarchical information.
  • Service Function Chaining is a network technology currently being researched and standardized. Since the development of the data center network to the overlay network, the network edge has become the demarcation point between the virtual network and the physical network, where the network edge may be a server or a top-of-rack (ToR) switch, and possibly a gateway ( Gateway).
  • ToR top-of-rack
  • Gateway Gateway
  • Overlay technology can't solve all the problems. There are still a lot of middleware in the data center, such as firewall/load balancer. These devices are all processed based on user services. If you tunnel through these devices, obviously It won't work.
  • This deployment model of the data center requires that the virtual firewall/load balancer can be deployed arbitrarily in the network, that is, independent of the network topology; the drawback is that if the traffic can be flexibly processed through the virtual firewall/load balancer, then New middleware such as virtual firewalls/load balancers will be created. These virtual firewalls/load balancers are deployed at the edge of the network and can be implemented by standard servers.
  • a service function such as a virtual firewall/load balancer/gateway is called a service function, and after a series of service functions are processed, a service function chaining, that is, a service function chain, is formed.
  • the SFC framework in the related art can be basically divided into the following components:
  • Service Overlay that is, Overlay technology that each network edge node needs to communicate
  • the Generic Service Control Plane is the controller that forms the Service Function Chaining.
  • Service Classification that is, need to perform flow identification, and then perform specific Service Function Chaining processing on a specific flow
  • Service function (referred to as SF), a component that performs business processing on data packets;
  • Service Function Forwarder which is transmitted between nodes of the service function chain, and encapsulates a layer of service function headers outside the data frame.
  • Service Header referred to as NSH. This header is parsed, encapsulated, and decapsulated by the service function forwarder component on the service function node.
  • the format of the packet header of the service function is shown in Figure 1.
  • Network Forwarder which is responsible for forwarding between multiple SFFs of the same service node and encapsulating and decapsulating the Overlay layer of data packets of the Overlay. It can also handle different service nodes. Forwarding
  • FIG. 2 is a schematic diagram of a service function path according to the related art.
  • the SFP is a service processing path that starts from the classifier and then passes through several service function instances to finally reach the destination.
  • the General Service Control Platform GSCP
  • the abstract service function chain SFC and real specific traffic are located.
  • a description of such a service function chain between paths formed by forwarded ordered service instances also referred to as a service function path.
  • a service function chain may include multiple service function paths, and different service function paths correspond to different policies.
  • Control plane metadata (Dataplane Metadata), which is a major feature, Metadata allows each business function node to exchange information with each other to achieve specific business processing purposes.
  • SFC is a technology that separates network device service functions from forwarding. It implements independent operation and processing of service functions and improves the forwarding performance of network devices.
  • the Operation, Administration, and Maintenance (OAM) technology is a network transmission protocol for network connectivity detection, fault location, and troubleshooting. It also provides a trigger mechanism for protection switching when a fault occurs. Connectivity Verification (CV) mechanism, Ping mechanism, and Trace mechanism. For different bearer network protocols, there is a corresponding OAM mechanism. For example, there is an Ethernet OAM protocol in the Ethernet, an IP OAM protocol exists in the IP network, and MPLS OAM exists in the MPLS network.
  • FIG. 3 is a schematic diagram of a technical framework of an SFC OAM according to the related art. As shown in Figure 3, the core idea is to diagnose the link status between business function chains or business functions.
  • 4 is a schematic diagram of an SFC OAM message format according to the related art. As shown in FIG. 4, a field may be reserved in the service function packet header NSH to identify the OAM packet and the OAM packet type.
  • FIG. 5 is a schematic diagram of another SFC OAM message format according to the related art. As shown in FIG. 5, a bit (Bit) may be reserved in the service function packet header NSH to identify an OAM packet, and a type of OAM packet may be set in the service function report.
  • the level problem of SFC OAM cannot be solved, that is, whether it is the connectivity between the service nodes experienced by the diagnostic service function chain or the service function forwarder on the service node experienced by the service function chain.
  • the embodiment of the invention provides a method and a device for processing hierarchical information, so as to at least solve the problem that the existing SFC OAM technology cannot flexibly define and manage its OAM detection level.
  • a processing method of detecting hierarchical information is provided.
  • the method for processing the detection level information includes: the source service node determines the service function chain (SFC) operation, management and maintenance (OAM) detection level information, and encapsulates the SFC OAM detection level information in the SFC OAM detection report.
  • SFC service function chain
  • OAM management and maintenance
  • the SFC OAM detection level information is used to indicate SFC OAM detection between peer entities belonging to the same level in different service nodes; the source service node sends an SFC OAM detection message to the destination service node.
  • the determining, by the source service node, the SFC OAM detection level information comprises: the source service node acquiring the currently selected multiple SFC OAM detection levels; and the source service node selecting at least one of the multiple SFC OAM detection levels. Detection level.
  • the plurality of SFC OAM detection levels comprise at least one of: an SFC OAM detection level between different service nodes experienced by the service function chain; and an SFC between the service function forwarders SFF on different service nodes experienced by the service function chain OAM detection level; SFC OAM detection level between service functions SF managed by SFF on different service nodes experienced by the service function chain.
  • the SFC OAM detection hierarchy information is encapsulated in a specific bit of the service function header NSH or the SFC OAM detection hierarchy information is encapsulated in other headers except the NSH.
  • the source service node is a service classifier or one of the service nodes on the service function chain.
  • the destination service node is a combination of the other service node or the plurality of service nodes except the source service node on the service function chain.
  • the SFC OAM detection packet includes one of the following types: a connectivity detection packet, a ping packet, and a trace packet.
  • the processing method for detecting the hierarchical information includes: the destination service node receives the service function chain SFC operation, management, and maintenance OAM detection packet from the source service node, where the SFC OAM detection packet carries SFC OAM detection level information, SFC OAM detection level information is used to indicate that SFC OAM detection is performed between peer entities belonging to the same level in different service nodes; the destination service node resolves SFC OAM detection level information from SFCOAM detection packets. And determining the SFC OAM response message to be fed back according to the SFC OAM detection level information.
  • the destination service node determines, according to the SFC OAM detection level information, that the SFC OAM response message includes one of the following: when the SFC OAM detection level information is the SFC OAM detection level between different service nodes experienced by the service function chain, the destination end
  • the service node directly processes the SFC OAM detection packet, and after the SFCOAM detection packet is processed, the information carried in the SFC OAM response packet includes at least one of the following: the node information of the destination service node, and the destination service node.
  • the connectivity information and the path information of the destination service node when the SFC OAM detection level information is the SFC OAM detection level between the service function forwarders SFF on different service nodes experienced by the service function chain, the destination service node will be SFC OAM
  • the detection message is forwarded to the SFF to process the SFC OAM message, and after the SFC processes the SFC OAM message, the information carried in the SFC OAM response message includes at least one of the following: connectivity information of the SFF of the destination service node. , SFF path information, SFF service level agreement information; when SFC OAM detects hierarchical information for the business function chain experience
  • the SFC OAM detection packet is forwarded to the SFF after the SFC OAM detection packet is sent to the SFF.
  • the SFF and the SF detect the SFC OAM.
  • the information carried in the SFC OAM response packet includes at least one of the following: the service function information of the SF under the SFF management of the destination service node, the connectivity information of the SF, the path information of the SF, and the service of the SF. Level agreement information.
  • a processing apparatus for detecting hierarchical information is provided.
  • the processing device for detecting the hierarchical information includes: a determining module, configured to determine the service function chain SFC operation, manage and maintain the OAM detection level information, and encapsulate the SFC OAM detection level information in the SFC OAM detection message,
  • the SFC OAM detection level information is used to indicate that the SFC OAM detection is performed between the peer entities belonging to the same level in different service nodes, and the sending module is configured to send the SFC OAM detection message to the destination service node.
  • the determining module comprises: an obtaining unit configured to acquire a plurality of currently selected multiple SFC OAM detection levels; and a selecting unit configured to select one of the SFC OAM detection levels from the plurality of SFC OAM detection levels.
  • the plurality of SFC OAM detection levels comprise at least one of: an SFC OAM detection level between different service nodes experienced by the service function chain; and an SFC between the service function forwarders SFF on different service nodes experienced by the service function chain OAM detection level; SFC OAM detection level between service functions SF managed by SFF on different service nodes experienced by the service function chain.
  • the SFC OAM detection hierarchy information is encapsulated in a specific bit of the service function header NSH or the SFC OAM detection hierarchy information is encapsulated in other headers except the NSH.
  • the source service node is a service classifier or one of the service nodes on the service function chain.
  • the destination service node is a combination of the other service node or the plurality of service nodes except the source service node on the service function chain.
  • the SFC OAM detection packet includes one of the following types: a connectivity detection packet, a ping packet, and a trace packet.
  • another processing apparatus for detecting hierarchical information is provided.
  • the processing device for detecting the hierarchical information includes: a receiving module, configured to receive a service function chain SFC operation, management, and maintenance OAM detection message from the source service node, where the SFC OAM detection message carries SFC OAM detection level information is used to indicate SFC OAM detection between peer entities belonging to the same level in different service nodes.
  • the processing module is configured to parse SFC OAM from SFC OAM detection packets. The level information is detected, and the SFC OAM response message to be fed back is determined according to the SFC OAM detection level information.
  • the processing module is configured to directly process the SFC OAM detection message when the SFC OAM detection level information is the SFC OAM detection level between different service nodes experienced by the service function chain, and after processing the SFC OAM detection message,
  • the information carried in the SFC OAM response packet includes at least one of the following: node information of the destination service node, connectivity information of the destination service node, and path information of the destination service node; or, when the SFC OAM detects the layer information
  • the SFC OAM detection packet is forwarded to the SFF to process the SFCOAM packet, and the SFC OAM packet is processed by the SFF after the SFC OAM detection layer is sent to the SFF OAM packet.
  • the information carried in the SFC OAM response packet includes at least one of the following: connectivity information of the SFF of the destination service node, path information of the SFF, and service level agreement information of the SFF; or, when the SFC OAM detects the layer information as a service
  • the SFC OAM detection packet is forwarded to the SFC OAM detection layer between the service functions SF managed by different SFFs in the function chain. After the SFF process, the SFF is forwarded to the SF for processing. After the SFF and the SF process the SFC OAM detection packet, the information carried in the SFC OAM response packet includes at least one of the following: the SFF of the destination service node.
  • the source service node determines the service function chain SFC operation, manages, and maintains the OAM detection level information, and encapsulates the SFC OAM detection level information in the SFC OAM detection message, where the SFC OAM detects the hierarchical information.
  • SFC OAM detection is performed between peer entities that belong to the same level in different service nodes.
  • the source service node sends SFC OAM detection packets to the destination service node, which solves the problem that the existing SFC OAM technology cannot be flexibly defined and managed.
  • the problem of its OAM detection level enables flexible definition and management of OAM detection levels.
  • FIG. 1 is a schematic diagram of a format of a service function packet header packet according to the related art
  • FIG. 2 is a schematic diagram of a service function path according to the related art
  • FIG. 3 is a schematic diagram of a technical framework of an SFC OAM according to the related art
  • FIG. 5 is a schematic diagram of another SFC OAM message format according to the related art.
  • FIG. 6 is a flowchart of a method of processing detection level information according to an embodiment of the present invention.
  • FIG. 7 is a schematic diagram of an overall architecture of an SFC according to a preferred embodiment of the present invention.
  • FIG. 8 is a schematic diagram of a format of an SFC OAM packet carrying SFC OAM detection hierarchy information according to a preferred embodiment of the present invention.
  • FIG. 9 is a schematic diagram of another SFC OAM packet format carrying SFC OAM detection level information according to a preferred embodiment of the present invention.
  • FIG. 10 is a flowchart of another processing method for detecting hierarchical information according to an embodiment of the present invention.
  • FIG. 11 is a schematic diagram of a connectivity detection mechanism between service nodes based on level one according to a preferred embodiment of the present invention.
  • FIG. 12 is a schematic diagram of a Ping mechanism between service nodes based on level two according to a preferred embodiment of the present invention.
  • FIG. 13 is a schematic diagram of a Trace mechanism of a Layer 3 based service function path according to a preferred embodiment of the present invention.
  • FIG. 14 is a structural block diagram of a processing apparatus for detecting hierarchical information according to an embodiment of the present invention.
  • FIG. 15 is a block diagram showing the structure of another processing apparatus for detecting hierarchical information according to an embodiment of the present invention.
  • FIG. 6 is a flowchart of a processing method of detecting hierarchical information according to an embodiment of the present invention. As shown in FIG. 6, the method may include the following processing steps:
  • Step S602 The source service node determines the SFC OAM detection level information, and encapsulates the SFC OAM detection level information in the SFC OAM detection message, where the SFC OAM detection level information is used to indicate that the pair belongs to the same level in different service nodes. Perform SFC OAM detection between entities;
  • Step S604 The source service node sends an SFC OAM detection packet to the destination service node.
  • the SFC OAM technology provided in the related art cannot flexibly define and manage its OAM detection hierarchy.
  • the hierarchical relationship between different service nodes, or the hierarchical relationship between service function forwarders of different service nodes, or the service function under the management of the service function of different service nodes The hierarchical relationship is encapsulated in the SFC OAM detection message and notified to the destination service node. This solves the problem that the existing SFC OAM technology cannot flexibly define and manage its OAM detection level, thereby enabling flexible definition and management of OAM detection levels.
  • the source service node determines that the SFC OAM detection level information may include the following operations:
  • Step S1 The source service node acquires multiple SFC OAM detection levels that are currently selected
  • Step S2 The source service node selects at least one of the SFC OAM detection levels from the plurality of SFC OAM detection levels.
  • the foregoing multiple SFC OAM detection levels may include at least one of the following:
  • FIG. 7 is a schematic diagram of an overall architecture of an SFC in accordance with a preferred embodiment of the present invention. As shown in Figure 7, there are three SFC OAM levels in the overall SFC architecture:
  • Level 1 between different business nodes experienced by the business function chain
  • Level 2 between the service function forwarders SFF on different service nodes experienced by the service function chain;
  • the SFC OAM source service node in the service function chain can select an SFC OAM detection layer from the above three SFC OAM layers, and then encapsulate the information in the SFC OAM packet. Send to the destination service node.
  • the SFC OAM detection level information may be encapsulated in a specific bit of the service function header NSH or the SFC OAM detection level information may also be encapsulated in other headers except the NSH.
  • FIG. 8 is a schematic diagram of a format of an SFC OAM packet carrying SFC OAM detection hierarchy information according to a preferred embodiment of the present invention.
  • the SFC OAM detection layer information may use dedicated bits, and the dedicated bits may be located in the service function packet header NSH.
  • FIG. 9 is a schematic diagram of another SFC OAM packet format carrying SFC OAM detection hierarchy information according to a preferred embodiment of the present invention. As shown in FIG. 9, the SFC OAM detection level information may also be located in a packet header other than the service function packet header NSH.
  • the source service node may be a service classifier or one of the service nodes on the service function chain.
  • the destination service node may be a service node or a combination of multiple service nodes except the source service node.
  • the foregoing SFC OAM detection message may include, but is not limited to, one of the following types:
  • Type I Connectivity Verification (CV) message
  • FIG. 10 is a flowchart of another processing method for detecting hierarchical information according to an embodiment of the present invention. As shown in FIG. 10, the method may include the following processing steps:
  • Step S1002 The destination service node receives the SFC OAM detection packet from the source service node, where the SFC OAM detection packet carries the SFC OAM detection hierarchy information, and the SFC OAM detection hierarchy information is used to indicate that it is in different service nodes. SFC OAM detection between peer entities belonging to the same level;
  • Step S1004 The destination service node parses the SFC OAM detection level information from the SFC OAM detection message, and determines the SFC OAM response message to be fed back according to the SFC OAM detection level information.
  • the destination service node determines, according to the SFC OAM detection level information, that the SFCOAM response message may include one of the following:
  • the destination service node directly processes the SFC OAM detection message, and after the SFC OAM detection message is processed,
  • the information carried in the SFC OAM response packet includes at least one of the following: node information of the destination service node, connectivity information of the destination service node, and path information of the destination service node;
  • the destination service node forwards the SFC OAM detection message to the SFF processing SFC OAM.
  • the information carried in the SFC OAM response packet includes at least one of the following: connectivity information of the SFF of the destination service node, path information of the SFF, and service of the SFF. Level agreement information;
  • the destination service node forwards the SFC OAM detection message to the SFF, and then forwards the information.
  • the SF is processed until the SFF and the SF process the SFC OAM detection packet, and the information carried in the SFC OAM response packet includes at least one of the following: the service function information of the SF under the SFF management of the destination service node. , SF connectivity information, SF path information, and SF service level agreement information.
  • the destination service node parses the detection hierarchy field from the SFC OAM detection message. If the field identifies the level 1, the SFC OAM response message carrying at least one of the node information, the connectivity information, and the path information of the service node is returned; if the field identifies the level 2, the service is returned.
  • SLA service level agreement
  • FIG. 11 is a schematic diagram of a connectivity detection mechanism between service nodes based on level one, in accordance with a preferred embodiment of the present invention. As shown in FIG. 11, the process may include the following steps:
  • Step 1 The source service node 1 constructs a connectivity check packet carrying the SFC OAM of the SFC OAM detection hierarchy field, and encapsulates the connectivity detection packet in the Overlay layer and forwards the connectivity detection packet to the next hop service along the service function chain.
  • Node 2 wherein the detection level field value carried in the connectivity detection packet is 1, that is, based on connectivity detection between service nodes;
  • Step 2 The service node 2 receives the connectivity detection packet, and parses the SFC OAM detection hierarchy field from the connectivity detection packet, and finds that it is based on the layer one; and at the same time, it finds that its operation is normal, then the service node 2
  • the SFC OAM packet carrying the SFC OAM detection hierarchy field is re-encapsulated in the Overlay layer, and then the connectivity detection packet is forwarded to the next hop service node 3 along the service function chain;
  • Step 3 The service node 3 receives the connectivity detection packet, and parses the SFC OAM detection hierarchy field from the connectivity detection packet, and finds that it is based on the layer one; Then, the SFC OAM connectivity detection response message carrying the connectivity information is generated and encapsulated in the Overlay layer, and then the connectivity detection response message is forwarded hop by hop along the service function chain to the source service node 1.
  • FIG. 12 is a schematic diagram of a Ping mechanism between service nodes based on Level 2, in accordance with a preferred embodiment of the present invention. As shown in FIG. 12, the method may include the following steps:
  • Step 1 The source service node 1 constructs a ping packet carrying the SFC OAM of the SFC OAM detection level field, and encapsulates the ping packet in the Overlay layer, and then forwards the ping packet to the next hop service node along the service function chain. 2, wherein the carrying detection level field value is 2, that is, the connectivity detection between the forwarders based on the service function;
  • Step 2 The service node 2 receives the ping packet, and parses the SFC OAM detection hierarchy field from the ping packet, and finds that it is based on the layer 2, and then forwards the SFC encapsulated packet to the service function forwarder experienced by the service function chain.
  • SFF SFC OAM detection hierarchy field
  • Step 3 The SFF detects whether the SFCOAM message is normal or not. If the SFF OAM packet carrying the SFC OAM detection level field is encapsulated in the Overlay layer, the service node 2 forwards the SFCOAM message to the next service chain.
  • Step 4 The service node 3 receives the SFC OAM packet, and parses the SFCOAM detection hierarchy field from the SFC OAM packet, and finds that it is based on the layer 2, and then forwards the SFC encapsulated packet to the service experienced by the service function chain.
  • Function repeater SFF Function repeater
  • Step 5 The service node 3 finds that it is the destination service node. After the local SFF is running normally, it generates an SFC OAM ping response packet and encapsulates it in the Overlay layer, and then forwards it hop by hop along the service function chain. The response message is sent to the source service node 1.
  • FIG. 13 is a schematic diagram of a Trace mechanism based on a Layer 3 service function path in accordance with a preferred embodiment of the present invention. As shown in FIG. 13, the method may include the following steps:
  • Step 1 The source service classifier constructs a TTL value of 1, and encapsulates the SFC OAM trace message carrying the SFC OAM detection level field in the Overlay layer, and forwards the Trace message to the next hop service node along the service function chain. 1, wherein the detected detection level field value is 3, that is, the connectivity detection between the service functions SF managed by the service function forwarder;
  • Step 2 The service node 1 receives the trace packet, and parses the SFC OAM detection hierarchy field from the trace packet, and finds that it is based on the layer 3, and then forwards the SFC encapsulated packet to the service function experienced by the service function chain.
  • Transponder SFF Transponder SFF
  • Step 3 The SFF forwards the SFC encapsulated packet to the SF specified by the service function path, and obtains at least one of the following information: the service function information, the function processing time information, the bandwidth information, and the resource information of the SF, and is encapsulated in the SFC OAM Trace.
  • the response message In the response message;
  • Step 4 The service node 1 performs Overlay encapsulation on the response message of the SFC OAM Trace, and forwards the response packet to the Service Classifier.
  • Step 5 The source service classifier constructs a TTL value of 2, and encapsulates the trace message of the SFC OAM carrying the SFC OAM detection level field in the Overlay layer, and then forwards the Trace message to the next hop service along the service function chain.
  • Step 6 The service node 1 re-overlays the Overlay, and then forwards the packet to the service node 2;
  • Step 7 The service node 2 receives the above-mentioned Overlay-encapsulated packet, and parses the SFC OAM detection hierarchy field from the packet, and finds that it is based on the level three, and then forwards the SFC encapsulated packet to the service function chain.
  • Business function forwarder SFF
  • Step 8 The SFF forwards the SFC encapsulated packet to the SF specified by the service function path, and obtains at least one of the following information: service function information, function processing time information, bandwidth information, and resource information of the SF, and is encapsulated in the SFC OAM Trace.
  • service function information e.g., service function information, function processing time information, bandwidth information, and resource information of the SF.
  • Step 9 The service node 2 performs Overlay encapsulation on the response message of the SFC OAM Trace, and forwards the response packet to the Service Classifier hop by hop;
  • Step 10 The source service classifier constructs a TTL value of 3, and encapsulates the SFC OAM trace message carrying the SFC OAM detection level field in the Overlay layer, and forwards the Trace message to the next hop service node along the service function chain. 1;
  • Step 11 The service node 1 receives the Trace message, re-overlays the Overlay, and then forwards the packet encapsulated by the Overlay to the service node 2;
  • Step 12 The service node 2 receives the Trace message, re-overlays the Overlay, and then forwards the packet encapsulated by the Overlay to the service node 3;
  • Step 13 The service node 3 receives the packet encapsulated by the Overlay, and parses the SFC OAM detection hierarchy field from the packet, and finds that it is based on the layer 3, and then forwards the SFC encapsulated packet to the service function chain.
  • Business function forwarder SFF
  • Step 14 The SFF forwards the SFC encapsulated packet to the SF specified by the service function path, and obtains at least one of the following information: service function information, function processing time information, bandwidth information, and resource information of the SF, and then encapsulated in the SFC OAM Trace.
  • service function information e.g., service function information
  • function processing time information e.g., bandwidth information
  • resource information e.g., resource information of the SFC OAM Trace.
  • Step 15 The service node 3 performs Overlay encapsulation on the response message of the SFC OAM Trace, and forwards the response packet to the Service Classifier hop by hop.
  • FIG. 14 is a block diagram showing the structure of a processing apparatus for detecting hierarchical information according to an embodiment of the present invention.
  • the processing device for detecting hierarchical information may include: a determining module 10 configured to determine a service function chain SFC operation, manage and maintain OAM detection hierarchy information, and encapsulate the SFC OAM detection hierarchy information in SFC OAM
  • the SFC OAM detection level information is used to indicate that the SFC OAM detection is performed between the peer entities belonging to the same level in different service nodes; and the sending module 20 is configured to send the SFC OAM to the destination service node. Detect the message.
  • the device shown in FIG. 14 solves the problem that the existing SFC OAM technology cannot flexibly define and manage its OAM detection hierarchy, thereby enabling flexible definition and management of the OAM detection hierarchy.
  • the determining module 10 may include: an acquiring unit (not shown) configured to acquire a plurality of currently selected multiple SFC OAM detection levels; a selecting unit (not shown) configured to be from a plurality of SFC OAMs Select one of the SFC OAM detection levels in the detection hierarchy.
  • the foregoing multiple SFC OAM detection levels may include at least one of the following:
  • the SFC OAM detection level information may be encapsulated in a specific bit of the service function header NSH or the SFC OAM detection level information may also be encapsulated in other headers except the NSH.
  • the source service node may be a service classifier or one of the service nodes on the service function chain.
  • the destination service node may be a service node or a combination of multiple service nodes except the source service node.
  • the foregoing SFC OAM detection message may include, but is not limited to, one of the following types:
  • Type I Connectivity Verification (CV) message
  • FIG. 15 is a block diagram showing the structure of another processing apparatus for detecting hierarchical information according to an embodiment of the present invention.
  • the processing device for detecting the hierarchical information may include: a receiving module 30, configured to receive an SFC OAM detection packet from the source service node, where the SFC OAM detection packet carries the SFC OAM detection layer The information, the SFC OAM detection level information is used to indicate that the SFC OAM detection is performed between the peer entities belonging to the same level in different service nodes, and the processing module 40 is configured to parse the SFC OAM detection level information from the SFC OAM detection message. The SFC OAM response message to be fed back is determined according to the SFC OAM detection level information.
  • the processing module 40 is configured to directly process the SFC OAM detection message and detect the SFC OAM when the SFC OAM detection level information is the SFC OAM detection level between different service nodes experienced by the service function chain.
  • the information carried in the SFC OAM response packet includes at least one of the following: the node information of the destination service node, the connectivity information of the destination service node, and the path information of the destination service node; or
  • the SFC OAM detection level information is the SFC OAM detection level between the service function forwarders SFFs on the service nodes that are experienced by the service function chain
  • the SFC OAM detection message is forwarded to the SFF to process the SFC OAM message, and is in the SFF pair.
  • the information carried in the SFC OAM response packet includes at least one of the following: the connectivity information of the SFF of the destination service node, the path information of the SFF, and the service level agreement information of the SFF; or
  • the SFC OAM detection level information is the SFC OAM detection level between the service functions SF managed by different SFFs in the service function chain
  • the SFC OAM detection message is forwarded to the SFF processing, and then forwarded to the SF for processing until SFF
  • the information carried in the SFC OAM response packet includes at least one of the following: the service function information of the SF under the SFF management of the destination service node, and the connectivity information of the SF. Path information of SF, service level agreement information of SF.
  • modules or steps of the present invention described above can be implemented by a general-purpose computing device that can be centralized on a single computing device or distributed across a network of multiple computing devices. Alternatively, they may be implemented by program code executable by the computing device such that they may be stored in the storage device by the computing device and, in some cases, may be different from the order herein.
  • the steps shown or described are performed, or they are separately fabricated into individual integrated circuit modules, or a plurality of modules or steps thereof are fabricated as a single integrated circuit module.
  • the invention is not limited to any specific combination of hardware and software.
  • the processing method and apparatus for detecting hierarchical information provided by the embodiments of the present invention have the following beneficial effects: by hierarchical relationship between different service nodes, or hierarchical relationship between service function repeaters of different service nodes.
  • the hierarchical relationship between the service functions managed by the service function of the different service nodes is encapsulated in the SFC OAM detection message and notified to the destination service node, thereby enabling flexible definition and management of the OAM detection hierarchy.

Landscapes

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

Abstract

本发明公开了一种检测层次信息的处理方法及装置，在上述方法中，源端业务节点确定SFC OAM检测层次信息，并将SFC OAM检测层次信息封装在SFC OAM检测报文中，其中，SFC OAM检测层次信息用于表明在不同业务节点中属于同一层级的对等实体之间进行SFC OAM检测；源端业务节点向目的端业务节点发送SFC OAM检测报文。根据本发明提供的技术方案，进而能够实现灵活定义并管理OAM检测层次。

Description

检测层次信息的处理方法及装置 技术领域
本发明涉及通信领域，具体而言，涉及一种检测层次信息的处理方法及装置。
背景技术
业务功能链(Service Function Chaining，简称为SFC)是目前正在研究和标准化的一种网络技术。自从数据中心网络向叠加(Overlay)网络发展以后，网络边缘成为了虚拟网络与物理网络的分界点，其中，网络边缘可能为服务器(Server)或者架顶式(ToR)交换机，以及可能为网关(Gateway)。然而Overlay技术无法解决所有问题，在数据中心内还是存在很多中间件(Middleware)，例如：防火墙/负载均衡器等，这些设备都是基于用户业务来处理的，如果通过隧道而穿越这些设备，显然是不行的。
数据中心的这种部署模型，要求虚拟防火墙/负载均衡器可以在网络中任意部署，也就是与网络拓扑无关；其缺陷在于：如果将流量能够灵活地通过虚拟防火墙/负载均衡器进行处理，那么将会产生虚拟防火墙/负载均衡器等新型中间件，这些虚拟防火墙/负载均衡器部署在网络的边缘，可以由标准服务器来实现。
相关技术中将虚拟防火墙/负载均衡器/网关等业务处理功能称为业务功能(Service Function)，而流量经过一系列的Service Function的处理，便会形成Service Function Chaining，即业务功能链。
目前，相关技术中的SFC框架基本可以分为如下组件：
1.业务叠加(Service Overlay)，即各个网络边缘节点需要通信的Overlay技术；
2.通用业务控制平面(Generic Service Control Plane，简称为GSCP)，即为形成Service Function Chaining的控制器；
3.业务分类器(Service Classification)，即需要进行流识别，然后对特定的流进行特定的Service Function Chaining处理；
4.业务功能(Service Function，简称为SF)，对数据报文进行业务处理的的组件；
5.业务功能转发器(Service Function Forwarder，简称为SFF)，数据报文在业务功能链的各个节点之间传递，会在数据帧以外封装一层业务功能报文头(Network  Service Header，简称为NSH)。这个报文头会被业务功能节点上的业务功能转发器组件进行解析、封装和解封装。上述业务功能报文头报文格式具体如图1所示。
6.网络转发器(Network Forwarder，简称为NF)，负责同一业务节点的内部多个SFFs之间的转发以及对Overlay的数据报文进行封装、解封装Overlay层；同时还能够处理不同业务节点之间的转发；
7.业务功能路径(service function path，简称为SFP)，图2是根据相关技术的业务功能路径的示意图。如图2所示，SFP是从分类器开始，再经过若干业务功能实例，最终达到目的地的一条业务处理路径。在某些情况下，通用业务控制平台(GSCP)无法知晓沿途经过的所有业务功能实例，例如：负荷分担场景或者业务服务等级场景等，此时，位于抽象的业务功能链SFC和真实具体的流量转发经过的有序业务实例构成的路径之间的这种业务功能链的描述，也称之为业务功能路径。一条业务功能链可能包括多个业务功能路径，不同的业务功能路径对应于不同的策略。
8.控制平面元数据(Dataplane Metadata)，其为一大特点，元数据(Metadata)允许各个业务功能节点能够互相交换信息，从而达到特定业务处理目的。
综上而述，SFC是一项将网络设备业务功能和转发分离开来的技术，其实现了业务功能的独立运算和处理，提升了网络设备的转发性能。
操作、管理和维护(Operation，Administration and Maintenance，简称为OAM)技术是针对网络连通性检测、故障定位、排查的网络传输协议以及在出现故障的时能够提供保护倒换的触发机制，其包含了链路连通性检测(Connectivity Verification，简称为CV)机制、Ping机制以及Trace机制。对于不同的承载网协议，均有相应的OAM机制。例如：在以太网中存在以太OAM协议，在IP网络中存在IP OAM协议，在MPLS网络中存在MPLS OAM。
目前，正在讨论SFC OAM技术的技术框架和实现细节。图3是根据相关技术的SFC OAM的技术框架示意图。如图3所示，其核心思想在于诊断业务功能链或者业务功能之间的链路状况。图4是根据相关技术的一种SFC OAM报文格式的示意图。如图4所示，可以在业务功能报文头NSH中预留一个字段，用于标识是OAM报文以及OAM报文类型。图5是根据相关技术的另一种SFC OAM报文格式的示意图。如图5所示，可以在业务功能报文头NSH中预留1个比特(Bit)，用于标识是OAM报文，而至于是哪种类型的OAM报文，则可以设置在业务功能报文头NSH以外的报文中。但是无论哪种方案，都无法解决SFC OAM的层次问题，即究竟是诊断业务功能链经历的业务节点之间的连通性还是业务功能链经历的业务节点上的业务功能转发器 (SFF)之间的连通性、抑或是业务功能链经历的业务功能转发器(SFF)所管理的SF之间的连通性。
综上所述，现有的SFC OAM技术无法灵活定义、管理其OAM检测层次。
发明内容
本发明实施例提供了一种检测层次信息的处理方法及装置，以至少解决现有的SFC OAM技术无法灵活定义、管理其OAM检测层次的问题。
根据本发明的一个方面，提供了一种检测层次信息的处理方法。
根据本发明实施例的检测层次信息的处理方法包括：源端业务节点确定业务功能链(SFC)操作、管理和维护(OAM)检测层次信息，并将SFC OAM检测层次信息封装在SFC OAM检测报文中，其中，SFC OAM检测层次信息用于表明在不同业务节点中属于同一层级的对等实体之间进行SFC OAM检测；源端业务节点向目的端业务节点发送SFC OAM检测报文。
优选地，源端业务节点确定SFC OAM检测层次信息包括：源端业务节点获取当前备选的多种SFC OAM检测层次；源端业务节点从多种SFC OAM检测层次中选取其中至少一种SFC OAM检测层次。
优选地，多种SFC OAM检测层次包括以下至少之一：业务功能链经历的不同业务节点之间的SFC OAM检测层次；业务功能链经历的不同业务节点上的业务功能转发器SFF之间的SFC OAM检测层次；业务功能链经历的不同业务节点上的SFF分别管理的业务功能SF之间的SFC OAM检测层次。
优选地，SFC OAM检测层次信息封装在业务功能报文头NSH的特定比特位中或者SFC OAM检测层次信息封装在除NSH之外的其余报文头中。
优选地，源端业务节点为业务分类器或者业务功能链上的其中一个业务节点。
优选地，目的端业务节点为业务功能链上除源端业务节点之外的其余一个业务节点或多个业务节点的组合。
优选地，SFC OAM检测报文包括以下类型之一：连通性检测报文、Ping报文、Trace报文。
根据本发明的另一方面，提供了另一种检测层次信息的处理方法。
根据本发明实施例的检测层次信息的处理方法包括：目的端业务节点接收来自于源端业务节点的业务功能链SFC操作、管理和维护OAM检测报文，其中，SFC OAM检测报文中携带有SFC OAM检测层次信息，SFC OAM检测层次信息用于表明在不同业务节点中属于同一层级的对等实体之间进行SFC OAM检测；目的端业务节点从SFCOAM检测报文中解析出SFC OAM检测层次信息，并根据SFC OAM检测层次信息确定待反馈的SFC OAM应答报文。
优选地，目的端业务节点根据SFC OAM检测层次信息确定SFC OAM应答报文包括以下之一：当SFC OAM检测层次信息为业务功能链经历的不同业务节点之间的SFC OAM检测层次时，目的端业务节点直接处理SFC OAM检测报文，并在对SFCOAM检测报文处理完毕后，在SFC OAM应答报文中携带的信息包括以下至少之一：目的端业务节点的节点信息、目的端业务节点的连通性信息、目的端业务节点的路径信息；当SFC OAM检测层次信息为业务功能链经历的不同业务节点上的业务功能转发器SFF之间的SFC OAM检测层次时，目的端业务节点将SFC OAM检测报文转发给SFF处理SFC OAM报文，并在SFF对SFC OAM报文处理完毕后，在SFC OAM应答报文中携带的信息包括以下至少之一：目的端业务节点的SFF的连通性信息、SFF的路径信息、SFF的业务等级协议信息；当SFC OAM检测层次信息为业务功能链经历的不同SFF分别管理的业务功能SF之间的SFC OAM检测层次时，目的端业务节点将SFC OAM检测报文转发给SFF处理后，再转发给SF进行处理，直至SFF和SF对SFC OAM检测报文均处理完毕后，在SFC OAM应答报文中携带的信息包括以下至少之一：目的端业务节点的SFF管理下的SF的业务功能信息、SF的连通性信息、SF的路径信息、SF的业务等级协议信息。
根据本发明的又一方面，提供了一种检测层次信息的处理装置。
根据本发明实施例的检测层次信息的处理装置包括：确定模块，设置为确定业务功能链SFC操作、管理和维护OAM检测层次信息，并将SFC OAM检测层次信息封装在SFC OAM检测报文中，其中，SFC OAM检测层次信息用于表明在不同业务节点中属于同一层级的对等实体之间进行SFC OAM检测；发送模块，设置为向目的端业务节点发送SFC OAM检测报文。
优选地，确定模块包括：获取单元，设置为获取当前备选的多种SFC OAM检测层次；选取单元，设置为从多种SFC OAM检测层次中选取其中一种SFC OAM检测层次。
优选地，多种SFC OAM检测层次包括以下至少之一：业务功能链经历的不同业务节点之间的SFC OAM检测层次；业务功能链经历的不同业务节点上的业务功能转发器SFF之间的SFC OAM检测层次；业务功能链经历的不同业务节点上的SFF分别管理的业务功能SF之间的SFC OAM检测层次。
优选地，SFC OAM检测层次信息封装在业务功能报文头NSH的特定比特位中或者SFC OAM检测层次信息封装在除NSH之外的其余报文头中。
优选地，源端业务节点为业务分类器或者业务功能链上的其中一个业务节点。
优选地，目的端业务节点为业务功能链上除源端业务节点之外的其余一个业务节点或多个业务节点的组合。
优选地，SFC OAM检测报文包括以下类型之一：连通性检测报文、Ping报文、Trace报文。
根据本发明的另一方面，提供了另一种检测层次信息的处理装置。
根据本发明实施例的检测层次信息的处理装置包括：接收模块，设置为接收来自于源端业务节点的业务功能链SFC操作、管理和维护OAM检测报文，其中，SFC OAM检测报文中携带有SFC OAM检测层次信息，SFC OAM检测层次信息用于表明在不同业务节点中属于同一层级的对等实体之间进行SFC OAM检测；处理模块，设置为从SFC OAM检测报文中解析出SFC OAM检测层次信息，并根据SFC OAM检测层次信息确定待反馈的SFC OAM应答报文。
优选地，处理模块设置为当SFC OAM检测层次信息为业务功能链经历的不同业务节点之间的SFC OAM检测层次时，直接处理SFC OAM检测报文，并在对SFC OAM检测报文处理完毕后，在SFC OAM应答报文中携带的信息包括以下至少之一：目的端业务节点的节点信息、目的端业务节点的连通性信息、目的端业务节点的路径信息；或者，当SFC OAM检测层次信息为业务功能链经历的不同业务节点上的业务功能转发器SFF之间的SFC OAM检测层次时，将SFC OAM检测报文转发给SFF处理SFCOAM报文，并在SFF对SFC OAM报文处理完毕后，在SFC OAM应答报文中携带的信息包括以下至少之一：目的端业务节点的SFF的连通性信息、SFF的路径信息、SFF的业务等级协议信息；或者，当SFC OAM检测层次信息为业务功能链经历的不同SFF分别管理的业务功能SF之间的SFC OAM检测层次时，将SFC OAM检测报文转发给SFF处理后，再转发给SF进行处理，直至SFF和SF对SFC OAM检测报文均处理完毕后，在SFC OAM应答报文中携带的信息包括以下至少之一：目的端业务节点的SFF 管理下的SF的业务功能信息、SF的连通性信息、SF的路径信息、SF的业务等级协议信息。
通过本发明实施例，采用源端业务节点确定业务功能链SFC操作、管理和维护OAM检测层次信息，并将SFC OAM检测层次信息封装在SFC OAM检测报文中，其中，SFC OAM检测层次信息用于表明在不同业务节点中属于同一层级的对等实体之间进行SFC OAM检测；源端业务节点向目的端业务节点发送SFC OAM检测报文，解决了现有的SFC OAM技术无法灵活定义、管理其OAM检测层次的问题，进而能够实现灵活定义并管理OAM检测层次。
附图说明
此处所说明的附图用来提供对本发明的进一步理解，构成本申请的一部分，本发明的示意性实施例及其说明用于解释本发明，并不构成对本发明的不当限定。在附图中：
图1是根据相关技术的业务功能报文头报文格式示意图；
图2是根据相关技术的业务功能路径的示意图；
图3是根据相关技术的SFC OAM的技术框架示意图；
图4是根据相关技术的一种SFC OAM报文格式的示意图；
图5是根据相关技术的另一种SFC OAM报文格式的示意图；
图6是根据本发明实施例的检测层次信息的处理方法的流程图；
图7是根据本发明优选实施例的SFC整体架构示意图；
图8是根据本发明优选实施例的一种携带SFC OAM检测层次信息的SFC OAM报文格式示意图；
图9是根据本发明优选实施例的另一种携带SFC OAM检测层次信息的SFC OAM报文格式示意图；
图10是根据本发明实施例的另一种检测层次信息的处理方法的流程图；
图11是根据本发明优选实施例的基于层次一的业务节点之间的连通性检测机制的示意图；
图12是根据本发明优选实施例的基于层次二的业务节点之间的Ping机制的示意图；
图13是根据本发明优选实施例的基于层次三的业务功能路径的Trace机制的示意图；
图14是根据本发明实施例的检测层次信息的处理装置的结构框图；
图15是根据本发明实施例的另一种检测层次信息的处理装置的结构框图。
具体实施方式
下文中将参考附图并结合实施例来详细说明本发明。需要说明的是，在不冲突的情况下，本申请中的实施例及实施例中的特征可以相互组合。
图6是根据本发明实施例的检测层次信息的处理方法的流程图。如图6所示，该方法可以包括以下处理步骤：
步骤S602：源端业务节点确定SFC OAM检测层次信息，并将SFC OAM检测层次信息封装在SFC OAM检测报文中，其中，SFC OAM检测层次信息用于表明在不同业务节点中属于同一层级的对等实体之间进行SFC OAM检测；
步骤S604：源端业务节点向目的端业务节点发送SFC OAM检测报文。
相关技术中所提供的SFC OAM技术无法灵活定义、管理其OAM检测层次。采用如图1所示的方法，将不同业务节点之间的层次关系、或者不同业务节点的业务功能转发器之间的层次关系，抑或是不同业务节点的业务功能转发器管理下的业务功能之间的层次关系封装在SFC OAM检测报文中并告知目的端业务节点。由此解决了现有的SFC OAM技术无法灵活定义、管理其OAM检测层次的问题，进而能够实现灵活定义并管理OAM检测层次。
优选地，在步骤S602中，源端业务节点确定SFC OAM检测层次信息可以包括以下操作：
步骤S1：源端业务节点获取当前备选的多种SFC OAM检测层次；
步骤S2：源端业务节点从多种SFC OAM检测层次中选取其中至少一种SFC OAM检测层次。
优选地，上述多种SFC OAM检测层次可以包括以下至少之一：
(1)业务功能链经历的不同业务节点之间的SFC OAM检测层次；
(2)业务功能链经历的不同业务节点上的业务功能转发器SFF之间的SFC OAM检测层次；
(3)业务功能链经历的不同SFF分别管理的业务功能SF之间的SFC OAM检测层次。
在优选实施例中，图7是根据本发明优选实施例的SFC整体架构示意图。如图7所示，在该SFC整体架构中存在以下三种SFC OAM层次：
层次1：业务功能链经历的不同业务节点之间；
层次2：业务功能链经历的不同业务节点上的业务功能转发器SFF之间；
层次3：业务功能链经历的不同业务功能转发器SFF管理的SF之间；
当业务功能链上发起SFC OAM检测时，业务功能链中的SFC OAM源端业务节点可以从上述三种SFC OAM层次中任意选择一种SFC OAM检测层次，然后封装在SFC OAM报文中，继而发送到目的端业务节点。
优选地，上述SFC OAM检测层次信息可以封装在业务功能报文头NSH的特定比特位中或者上述SFC OAM检测层次信息还可以封装在除NSH之外的其余报文头中。
在优选实施例中，图8是根据本发明优选实施例的一种携带SFC OAM检测层次信息的SFC OAM报文格式示意图。如图8所示，上述SFC OAM检测层次信息可以使用专用的bits，该专用bits可以位于业务功能报文头NSH中。图9是根据本发明优选实施例的另一种携带SFC OAM检测层次信息的SFC OAM报文格式示意图。如图9所示，上述SFC OAM检测层次信息也可以位于业务功能报文头NSH以外的报文头中。
在优选实施过程中，上述源端业务节点可以为业务分类器或者业务功能链上的其中一个业务节点。
在优选实施过程中，上述目的端业务节点可以为业务功能链上除源端业务节点之外的其余一个业务节点或多个业务节点的组合。
在优选实施过程中，上述SFC OAM检测报文可以包括但不限于以下类型之一：
类型一、连通性检测(Connectivity Verification，简称为CV)报文；
类型二、Ping报文；
类型三、Trace报文。
图10是根据本发明实施例的另一种检测层次信息的处理方法的流程图。如图10所示，该方法可以包括以下处理步骤：
步骤S1002：目的端业务节点接收来自于源端业务节点的SFC OAM检测报文，其中，SFC OAM检测报文中携带有SFC OAM检测层次信息，SFC OAM检测层次信息用于表明在不同业务节点中属于同一层级的对等实体之间进行SFC OAM检测；
步骤S1004：目的端业务节点从SFC OAM检测报文中解析出SFC OAM检测层次信息，并根据SFC OAM检测层次信息确定待反馈的SFC OAM应答报文。
优选地，在步骤S1004中，目的端业务节点根据SFC OAM检测层次信息确定SFCOAM应答报文可以包括以下之一：
(1)当SFC OAM检测层次信息为业务功能链经历的不同业务节点之间的SFCOAM检测层次时，目的端业务节点直接处理SFC OAM检测报文，并在对SFC OAM检测报文处理完毕后，在SFC OAM应答报文中携带的信息包括以下至少之一：目的端业务节点的节点信息、目的端业务节点的连通性信息、目的端业务节点的路径信息；
(2)当SFC OAM检测层次信息为业务功能链经历的不同业务节点上的业务功能转发器SFF之间的SFC OAM检测层次时，目的端业务节点将SFC OAM检测报文转发给SFF处理SFC OAM报文，并在SFF对SFC OAM报文处理完毕后，在SFC OAM应答报文中携带的信息包括以下至少之一：目的端业务节点的SFF的连通性信息、SFF的路径信息、SFF的业务等级协议信息；
(3)当SFC OAM检测层次信息为业务功能链经历的不同SFF分别管理的业务功能SF之间的SFC OAM检测层次时，目的端业务节点将SFC OAM检测报文转发给SFF处理后，再转发给SF进行处理，直至SFF和SF对SFC OAM检测报文均处理完毕后，在SFC OAM应答报文中携带的信息包括以下至少之一：目的端业务节点的SFF管理下的SF的业务功能信息、SF的连通性信息、SF的路径信息、SF的业务等级协议信息。
在优选实施例中，目的端业务节点在接收到携带有SFC OAM检测层次的SFCOAM检测报文之后，从SFC OAM检测报文中解析出检测层次字段。如果该字段标识层次1，则仅返回携带有该业务节点的节点信息、连通性信息以及路径信息中至少一种信息的SFC OAM应答报文；如果该字段标识层次2，则返回携带有该业务节点的业务转发器的连通性信息以及路径信息中至少一种信息的SFC OAM应答报文；如果该字段标识层次3，则返回携带有该业务节点的业务转发器管理的业务功能的业务功能信息、连通性信息、路径信息以及业务等级协议(Service Level Agreement，简称为SLA)信息中至少一种信息的SFC OAM应答报文。
下面将结合图11至图13中所示的优选实施方式对上述优选实施过程作进一步的描述。
优选实施例一
图11是根据本发明优选实施例的基于层次一的业务节点之间的连通性检测机制的示意图。如图11所示，该流程可以包括以下步骤：
步骤一、源端业务节点1构造携带有SFC OAM检测层次字段的SFC OAM的连通性检测报文，将其封装于Overlay层并沿着业务功能链将连通性检测报文转发至下一跳业务节点2，其中，该连通性检测报文中携带的检测层次字段值为1，即基于业务节点之间的连通性检测；
步骤二、业务节点2接收到上述连通性检测报文，并从该连通性检测报文中解析出SFC OAM检测层次字段，发现其基于层次一；同时，发现自身运行正常，则该业务节点2将携带有SFC OAM检测层次字段的SFC OAM报文重新将其封装于Overlay层，再沿着业务功能链将连通性检测报文转发至下一跳业务节点3；
步骤三、业务节点3接收到上述连通性检测报文，并从该连通性检测报文中解析出SFC OAM检测层次字段，发现其基于层次一；同时，发现自身运行正常且为目的端业务节点，则生成携带有连通性信息的SFC OAM连通性检测应答报文，并将其封装于Overlay层，然后再沿着业务功能链逐跳转发连通性检测应答报文至源端业务节点1。
优选实施例二
图12是根据本发明优选实施例的基于层次二的业务节点之间的Ping机制的示意图。如图12所示，该方法可以包括以下步骤：
步骤一、源端业务节点1构造携带有SFC OAM检测层次字段的SFC OAM的Ping报文，并将其封装于Overlay层，然后再沿着业务功能链将Ping报文转发到下一跳业务节点2，其中，携带检测层次字段值为2，即基于业务功能转发器之间的连通性检测；
步骤二、业务节点2接收到Ping报文，并从Ping报文中解析出SFC OAM检测层次字段，发现其为基于层次二，然后，转发SFC封装报文到业务功能链经历的业务功能转发器SFF；
步骤三、上述SFF检测自身是否运行正常；如果正常，则该业务节点2将携带有SFC OAM检测层次字段的SFC OAM报文封装于Overlay层，并沿着业务功能链将SFCOAM报文转发到下一跳业务节点3；
步骤四、业务节点3接收到SFC OAM报文，并从SFC OAM报文中解析出SFCOAM检测层次字段，发现其为基于层次二，然后，再将SFC封装报文转发到业务功能链经历的业务功能转发器SFF；
步骤五、业务节点3发现自身已经是目的端业务节点，在发现本地SFF运行正常后，生成SFC OAM Ping应答报文，并将其封装于Overlay层，然后再沿着业务功能链逐跳转发上述应答报文到源端业务节点1。
优选实施例三
图13是根据本发明优选实施例的基于层次三的业务功能路径的Trace机制的示意图。如图13所示，该方法可以包括以下步骤：
步骤一、源端Service Classifier构造TTL值为1，将携带有SFC OAM检测层次字段的SFC OAM的Trace报文封装于Overlay层，并沿着业务功能链将Trace报文转发到下一跳业务节点1，其中，携带的检测层次字段值为3，即基于业务功能转发器管理的业务功能SF之间的连通性检测；
步骤二、业务节点1接收到Trace报文，从该Trace报文中解析出SFC OAM检测层次字段，发现其为基于层次三，然后，再将SFC封装报文转发到业务功能链经历的业务功能转发器SFF；
步骤三、SFF将该SFC封装报文转发到该业务功能路径指定的SF，获取以下信息至少之一：SF的业务功能信息、功能处理时间信息、带宽信息、资源信息，并封装在SFC OAM Trace的应答报文中；
步骤四、业务节点1对上述SFC OAM Trace的应答报文进行Overlay封装，并转发应答报文到Service Classifier上；
步骤五、源端Service Classifier构造TTL值为2，并将携带有SFC OAM检测层次字段的SFC OAM的Trace报文封装于Overlay层，然后再沿着业务功能链转发Trace报文到下一跳业务节点1；
步骤六、业务节点1重新进行Overlay封装，然后转发该报文到业务节点2；
步骤七、业务节点2接收到上述经过Overlay封装的报文，并从该报文中解析出SFC OAM检测层次字段，发现其基于层次三，然后，再将SFC封装报文转发到业务功能链经历的业务功能转发器SFF；
步骤八、SFF转发该SFC封装报文到该业务功能路径指定的SF，获取以下信息至少之一：SF的业务功能信息、功能处理时间信息、带宽信息、资源信息，并封装在SFC OAM Trace的应答报文中；
步骤九、业务节点2对上述SFC OAM Trace的应答报文进行Overlay封装，逐跳转发应答报文到Service Classifier上；
步骤十、源端Service Classifier构造TTL值为3，将携带有SFC OAM检测层次字段的SFC OAM的Trace报文封装于Overlay层，并沿着业务功能链将Trace报文转发到下一跳业务节点1；
步骤十一、业务节点1接收到该Trace报文，重新进行Overlay封装，然后再转发经过Overlay封装的报文到业务节点2；
步骤十二、业务节点2接收到该Trace报文，重新进行Overlay封装，然后再转发经过Overlay封装的报文到业务节点3；
步骤十三、业务节点3接收到经过Overlay封装的报文，并从上述报文中解析出SFC OAM检测层次字段，发现其基于层次三，然后，再将SFC封装报文转发到业务功能链经历的业务功能转发器SFF；
步骤十四、SFF转发该SFC封装报文到该业务功能路径指定的SF，获取以下信息至少之一：SF的业务功能信息、功能处理时间信息、带宽信息、资源信息，然后封装在SFC OAM Trace的应答报文中；
步骤十五、业务节点3对上述SFC OAM Trace的应答报文进行Overlay封装，逐跳转发应答报文到Service Classifier上。
图14是根据本发明实施例的检测层次信息的处理装置的结构框图。如图14所示，该检测层次信息的处理装置可以包括：确定模块10，设置为确定业务功能链SFC操作、管理和维护OAM检测层次信息，并将所述SFC OAM检测层次信息封装在SFC OAM检测报文中，其中，SFC OAM检测层次信息用于表明在不同业务节点中属于同一层级的对等实体之间进行SFC OAM检测；发送模块20，设置为向目的端业务节点发送所述SFC OAM检测报文。
采用如图14所示的装置，解决了现有的SFC OAM技术无法灵活定义、管理其OAM检测层次的问题，进而能够实现灵活定义并管理OAM检测层次。
优选地，确定模块10可以包括：获取单元(图中未示出)，设置为获取当前备选的多种SFC OAM检测层次；选取单元(图中未示出)，设置为从多种SFC OAM检测层次中选取其中一种SFC OAM检测层次。
优选地，上述多种SFC OAM检测层次可以包括以下至少之一：
(1)业务功能链经历的不同业务节点之间的SFC OAM检测层次；
(2)业务功能链经历的不同业务节点上的业务功能转发器SFF之间的SFC OAM检测层次；
(3)业务功能链经历的不同SFF分别管理的业务功能SF之间的SFC OAM检测层次。
优选地，上述SFC OAM检测层次信息可以封装在业务功能报文头NSH的特定比特位中或者上述SFC OAM检测层次信息还可以封装在除NSH之外的其余报文头中。
在优选实施过程中，上述源端业务节点可以为业务分类器或者业务功能链上的其中一个业务节点。
在优选实施过程中，上述目的端业务节点可以为业务功能链上除源端业务节点之外的其余一个业务节点或多个业务节点的组合。
在优选实施过程中，上述SFC OAM检测报文可以包括但不限于以下类型之一：
类型一、连通性检测(Connectivity Verification，简称为CV)报文；
类型二、Ping报文；
类型三、Trace报文。
图15是根据本发明实施例的另一种检测层次信息的处理装置的结构框图。如图15所示，该检测层次信息的处理装置可以包括：接收模块30，设置为接收来自于源端业务节点的SFC OAM检测报文，其中，SFC OAM检测报文中携带有SFC OAM检测层次信息，SFC OAM检测层次信息用于表明在不同业务节点中属于同一层级的对等实体之间进行SFC OAM检测；处理模块40，设置为从SFC OAM检测报文中解析出SFC OAM检测层次信息，并根据SFC OAM检测层次信息确定待反馈的SFC OAM应答报文。
在优选实施过程中，处理模块40，设置为当SFC OAM检测层次信息为业务功能链经历的不同业务节点之间的SFC OAM检测层次时，直接处理SFC OAM检测报文，并在对SFC OAM检测报文处理完毕后，在SFC OAM应答报文中携带的信息包括以下至少之一：目的端业务节点的节点信息、目的端业务节点的连通性信息、目的端业务节点的路径信息；或者，
当SFC OAM检测层次信息为业务功能链经历的不同业务节点上的业务功能转发器SFF之间的SFC OAM检测层次时，将SFC OAM检测报文转发给SFF处理SFC OAM报文，并在SFF对SFC OAM报文处理完毕后，在SFC OAM应答报文中携带的信息包括以下至少之一：目的端业务节点的SFF的连通性信息、SFF的路径信息、SFF的业务等级协议信息；或者，
当SFC OAM检测层次信息为业务功能链经历的不同SFF分别管理的业务功能SF之间的SFC OAM检测层次时，将SFC OAM检测报文转发给SFF处理后，再转发给SF进行处理，直至SFF和SF对SFC OAM检测报文均处理完毕后，在SFC OAM应答报文中携带的信息包括以下至少之一：目的端业务节点的SFF管理下的SF的业务功能信息、SF的连通性信息、SF的路径信息、SF的业务等级协议信息。
从以上的描述中，可以看出，上述实施例实现了如下技术效果(需要说明的是这些效果是某些优选实施例可以达到的效果)：采用本发明实施例所提供的技术方案，通过将不同业务节点之间的层次关系、或者不同业务节点的业务功能转发器之间的层次关系，抑或是不同业务节点的业务功能转发器管理下的业务功能之间的层次关系封装在SFC OAM检测报文中并告知目的端业务节点，进而能够实现灵活定义并管理OAM检测层次。
显然，本领域的技术人员应该明白，上述的本发明的各模块或各步骤可以用通用的计算装置来实现，它们可以集中在单个的计算装置上，或者分布在多个计算装置所组成的网络上，可选地，它们可以用计算装置可执行的程序代码来实现，从而，可以将它们存储在存储装置中由计算装置来执行，并且在某些情况下，可以以不同于此处的顺序执行所示出或描述的步骤，或者将它们分别制作成各个集成电路模块，或者将它们中的多个模块或步骤制作成单个集成电路模块来实现。这样，本发明不限制于任何特定的硬件和软件结合。
以上所述仅为本发明的优选实施例而已，并不用于限制本发明，对于本领域的技术人员来说，本发明可以有各种更改和变化。凡在本发明的精神和原则之内，所作的任何修改、等同替换、改进等，均应包含在本发明的保护范围之内。
工业实用性
如上所述，本发明实施例提供的一种检测层次信息的处理方法及装置具有以下有益效果：通过将不同业务节点之间的层次关系、或者不同业务节点的业务功能转发器之间的层次关系，抑或是不同业务节点的业务功能转发器管理下的业务功能之间的层次关系封装在SFC OAM检测报文中并告知目的端业务节点，进而能够实现灵活定义并管理OAM检测层次。

Claims (18)

  1. 一种检测层次信息的处理方法，包括：
    源端业务节点确定业务功能链SFC操作、管理和维护OAM检测层次信息，并将所述SFC OAM检测层次信息封装在SFC OAM检测报文中，其中，所述SFC OAM检测层次信息用于表明在不同业务节点中属于同一层级的对等实体之间进行SFC OAM检测；
    所述源端业务节点向目的端业务节点发送所述SFC OAM检测报文。
  2. 根据权利要求1所述的方法，其中，所述源端业务节点确定所述SFC OAM检测层次信息包括：
    所述源端业务节点获取当前备选的多种SFC OAM检测层次；
    所述源端业务节点从所述多种SFC OAM检测层次中选取其中至少一种SFC OAM检测层次。
  3. 根据权利要求2所述的方法，其中，所述多种SFC OAM检测层次包括以下至少之一：
    业务功能链经历的不同业务节点之间的SFC OAM检测层次；
    所述业务功能链经历的不同业务节点上的业务功能转发器SFF之间的SFC OAM检测层次；
    所述业务功能链经历的不同业务节点上的SFF分别管理的业务功能SF之间的SFC OAM检测层次。
  4. 根据权利要求1所述的方法，其中，所述SFC OAM检测层次信息封装在业务功能报文头NSH的特定比特位中或者所述SFC OAM检测层次信息封装在除所述NSH之外的其余报文头中。
  5. 根据权利要求1至4中任一项所述的方法，其中，所述源端业务节点为业务分类器或者业务功能链上的其中一个业务节点。
  6. 根据权利要求1至4中任一项所述的方法，其中，所述目的端业务节点为业务功能链上除所述源端业务节点之外的其余一个业务节点或多个业务节点的组合。
  7. 根据权利要求1至4中任一项所述的方法，其中，所述SFC OAM检测报文包括以下类型之一：连通性检测报文、Ping报文、Trace报文。
  8. 一种检测层次信息的处理方法，包括：
    目的端业务节点接收来自于源端业务节点的业务功能链SFC操作、管理和维护OAM检测报文，其中，所述SFC OAM检测报文中携带有SFC OAM检测层次信息，所述SFC OAM检测层次信息用于表明在不同业务节点中属于同一层级的对等实体之间进行SFC OAM检测；
    所述目的端业务节点从所述SFC OAM检测报文中解析出SFC OAM检测层次信息，并根据所述SFC OAM检测层次信息确定待反馈的SFC OAM应答报文。
  9. 根据权利要求8所述的方法，其中，所述目的端业务节点根据所述SFC OAM检测层次信息确定所述SFC OAM应答报文包括以下之一：
    当所述SFC OAM检测层次信息为业务功能链经历的不同业务节点之间的SFC OAM检测层次时，所述目的端业务节点直接处理所述SFC OAM检测报文，并在对所述SFC OAM检测报文处理完毕后，在所述SFC OAM应答报文中携带的信息包括以下至少之一：所述目的端业务节点的节点信息、所述目的端业务节点的连通性信息、所述目的端业务节点的路径信息；
    当所述SFC OAM检测层次信息为所述业务功能链经历的不同业务节点上的业务功能转发器SFF之间的SFC OAM检测层次时，所述目的端业务节点将所述SFC OAM检测报文转发给业务功能转发器SFF处理所述SFC OAM报文，并在所述SFF对所述SFC OAM报文处理完毕后，在所述SFC OAM应答报文中携带的信息包括以下至少之一：所述目的端业务节点的SFF的连通性信息、所述SFF的路径信息、所述SFF的业务等级协议信息；
    当所述SFC OAM检测层次信息为所述业务功能链经历的不同SFF分别管理的业务功能SF之间的SFC OAM检测层次时，所述目的端业务节点将所述SFC OAM检测报文转发给所述业务功能转发器SFF处理后，再转发给业务功能SF处理，处理完毕后，在所述SFC OAM应答报文中携带的信息包括以下至少之一：所述目的端业务节点的SFF管理下的SF的业务功能信息、所述SF的连通性信息、所述SF的路径信息、所述SF的业务等级协议信息。
  10. 一种检测层次信息的处理装置，包括：
    确定模块，设置为确定业务功能链SFC操作、管理和维护OAM检测层次信息，并将所述SFC OAM检测层次信息封装在SFC OAM检测报文中，其中，所述SFC OAM检测层次信息用于表明在不同业务节点中属于同一层级的对等实体之间进行SFC OAM检测；
    发送模块，设置为向目的端业务节点发送所述SFC OAM检测报文。
  11. 根据权利要求10所述的装置，其中，所述确定模块包括：
    获取单元，设置为获取当前备选的多种SFC OAM检测层次；
    选取单元，设置为从所述多种SFC OAM检测层次中选取其中一种SFC OAM检测层次。
  12. 根据权利要求11所述的装置，其中，所述多种SFC OAM检测层次包括以下至少之一：
    业务功能链经历的不同业务节点之间的SFC OAM检测层次；
    所述业务功能链经历的不同业务节点上的业务功能转发器SFF之间的SFC OAM检测层次；
    所述业务功能链经历的不同业务节点上的SFF分别管理的业务功能SF之间的SFC OAM检测层次。
  13. 根据权利要求10所述的装置，其中，所述SFC OAM检测层次信息封装在业务功能报文头NSH的特定比特位中或者所述SFC OAM检测层次信息封装在除所述NSH之外的其余报文头中。
  14. 根据权利要求10至13中任一项所述的装置，其中，所述源端业务节点为业务分类器或者业务功能链上的其中一个业务节点。
  15. 根据权利要求10至13中任一项所述的装置，其中，所述目的端业务节点为业务功能链上除所述源端业务节点之外的其余一个业务节点或多个业务节点的组合。
  16. 根据权利要求10至13中任一项所述的装置，其中，所述SFC OAM检测报文包括以下类型之一：连通性检测报文、Ping报文、Trace报文。
  17. 一种检测层次信息的处理装置，包括：
    接收模块，设置为接收来自于源端业务节点的业务功能链SFC操作、管理和维护OAM检测报文，其中，所述SFC OAM检测报文中携带有SFC OAM检测层次信息，所述SFC OAM检测层次信息用于表明在不同业务节点中属于同一层级的对等实体之间进行SFC OAM检测；
    处理模块，设置为从所述SFC OAM检测报文中解析出SFC OAM检测层次信息，并根据所述SFC OAM检测层次信息确定待反馈的SFC OAM应答报文。
  18. 根据权利要求17所述的装置，其中，所述处理模块设置为当所述SFC OAM检测层次信息为业务功能链经历的不同业务节点之间的SFC OAM检测层次时，直接处理所述SFC OAM检测报文，并在对所述SFC OAM检测报文处理完毕后，在所述SFC OAM应答报文中携带的信息包括以下至少之一：所述目的端业务节点的节点信息、所述目的端业务节点的连通性信息、所述目的端业务节点的路径信息；或者，当所述SFC OAM检测层次信息为所述业务功能链经历的不同业务节点上的业务功能转发器SFF之间的SFC OAM检测层次时，将所述SFC OAM检测报文转发给所述SFF处理所述SFC OAM报文，并在所述SFF对所述SFC OAM报文处理完毕后，在所述SFC OAM应答报文中携带的信息包括以下至少之一：所述目的端业务节点的SFF的连通性信息、所述SFF的路径信息、所述SFF的业务等级协议信息；或者，当所述SFC OAM检测层次信息为所述业务功能链经历的不同SFF分别管理的业务功能SF之间的SFC OAM检测层次时，将所述SFC OAM检测报文转发给所述SFF处理后，再转发给所述SF进行处理，直至所述SFF和所述SF对所述SFC OAM检测报文均处理完毕后，在所述SFC OAM应答报文中携带的信息包括以下至少之一：所述目的端业务节点的SFF管理下的SF的业务功能信息、所述SF的连通性信息、所述SF的路径信息、所述SF的业务等级协议信息。
PCT/CN2014/092070 2014-10-20 2014-11-24 检测层次信息的处理方法及装置 WO2015184740A1 (zh)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201410559786.0A CN105515816B (zh) 2014-10-20 2014-10-20 检测层次信息的处理方法及装置
CN201410559786.0 2014-10-20

Publications (1)

Publication Number Publication Date
WO2015184740A1 true WO2015184740A1 (zh) 2015-12-10

Family

ID=54766011

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2014/092070 WO2015184740A1 (zh) 2014-10-20 2014-11-24 检测层次信息的处理方法及装置

Country Status (2)

Country Link
CN (1) CN105515816B (zh)
WO (1) WO2015184740A1 (zh)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2019196585A1 (zh) * 2018-04-08 2019-10-17 华为技术有限公司 监测业务质量的方法和装置

Families Citing this family (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN108574582B (zh) * 2017-03-07 2022-05-13 中兴通讯股份有限公司 一种故障检测方法和装置
CN109120657B (zh) * 2017-06-23 2022-08-16 中兴通讯股份有限公司 一种业务配置方法和节点
CN109218058B (zh) * 2017-07-06 2021-09-14 中国电信股份有限公司 Oam信息的获取方法、系统及计算机可读存储介质
CN110557343A (zh) * 2018-05-31 2019-12-10 中国电信股份有限公司 Sfc业务数据转发方法以及sfc网络系统
CN110493052B (zh) * 2019-08-22 2022-08-05 北京交大思诺科技股份有限公司 一种兼容不同通信协议的安全计算机平台通信架构

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101425928A (zh) * 2008-11-29 2009-05-06 中兴通讯股份有限公司 维护实体组层次的处理方法及装置
CN102185711A (zh) * 2011-04-26 2011-09-14 中兴通讯股份有限公司 一种检测混合网络中链路故障的方法及设备
WO2013155696A1 (en) * 2012-04-20 2013-10-24 Telefonaktiebolaget L M Ericsson (Publ) Method to do fast traffic switchover based on server layer status
JP5480189B2 (ja) * 2011-03-28 2014-04-23 エヌ・ティ・ティ・コミュニケーションズ株式会社 ネットワーク監視装置、ネットワーク試験方法、パス情報管理方法、及びプログラム

Family Cites Families (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US8593973B2 (en) * 2010-03-09 2013-11-26 Juniper Networks, Inc. Communicating network path and status information in multi-homed networks
KR101820308B1 (ko) * 2010-09-15 2018-01-19 삼성전자주식회사 디지털 방송 송신기, 디지털 방송 수신기 및 그들의 스트림 처리 방법
WO2011143940A1 (zh) * 2011-01-14 2011-11-24 华为技术有限公司 一种数据转发方法和路由器

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101425928A (zh) * 2008-11-29 2009-05-06 中兴通讯股份有限公司 维护实体组层次的处理方法及装置
JP5480189B2 (ja) * 2011-03-28 2014-04-23 エヌ・ティ・ティ・コミュニケーションズ株式会社 ネットワーク監視装置、ネットワーク試験方法、パス情報管理方法、及びプログラム
CN102185711A (zh) * 2011-04-26 2011-09-14 中兴通讯股份有限公司 一种检测混合网络中链路故障的方法及设备
WO2013155696A1 (en) * 2012-04-20 2013-10-24 Telefonaktiebolaget L M Ericsson (Publ) Method to do fast traffic switchover based on server layer status

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
HALPERN, J.; ET AL.: "Service Function Chaining (SFC) Architecture Draft-merged-sfc-architecture-02", 22 August 2014 (2014-08-22), pages 1 - 26, XP015101310, Retrieved from the Internet <URL:https://tools.ietf.org/html/draft-merged-sfc-architecture-02> *

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2019196585A1 (zh) * 2018-04-08 2019-10-17 华为技术有限公司 监测业务质量的方法和装置

Also Published As

Publication number Publication date
CN105515816A (zh) 2016-04-20
CN105515816B (zh) 2019-12-31

Similar Documents

Publication Publication Date Title
WO2016058245A1 (zh) 操作、管理和维护oam报文处理方法及装置
CN111886833B (zh) 重定向控制信道消息的方法和用于实现该方法的设备
WO2021170092A1 (zh) 报文处理方法、装置、网络设备及存储介质
CN111953604B (zh) 一种为业务流提供业务服务的方法和装置
US9917745B2 (en) Validation of chained network services
WO2015184740A1 (zh) 检测层次信息的处理方法及装置
US20200396162A1 (en) Service function chain sfc-based communication method, and apparatus
US9819586B2 (en) Network-based ethernet switching packet switch, network, and method
WO2021185208A1 (zh) 报文处理方法、装置、设备及存储介质
US10999121B2 (en) Service OAM virtualization
WO2018210213A1 (zh) 一种实现ioam封装的方法及装置、存储介质
CN105577416B (zh) 一种业务功能链操作、管理和维护方法及节点设备
CN111245715B (zh) 报文传输方法和系统
US10862735B2 (en) Method and apparatus for implementing operation, administration, and maintenance function
US10623278B2 (en) Reactive mechanism for in-situ operation, administration, and maintenance traffic
US10680910B2 (en) Virtualized proactive services
KR20140117993A (ko) 링크 장애 추적을 위한 mpls-tp 네트워크 및 방법
WO2015184868A1 (zh) 一种服务层信号失效检测装置及方法
CN108111423B (zh) 流量传输管理方法、装置及网络分路设备
CN106161065B (zh) 路径的保护倒换处理方法、装置、系统及转发设备
KR101802037B1 (ko) Ｓｄｎ 환경에서 서비스 기능 체이닝을 위한 ｏａｍ 메시지 전송 방법 및 시스템
CN111435948A (zh) 一种在网络中传输报文的方法及网络设备
CN104378245A (zh) 在l2vpn架构的ac口上实现oam的方法及装置
CN115842696A (zh) 通信方法、装置和计算机可读存储介质
WO2023247996A1 (en) Method and system to mitigate fault in a distributed system

Legal Events

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

Ref document number: 14893707

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 14893707

Country of ref document: EP

Kind code of ref document: A1