WO2018050122A1 - 防止故障处理延迟 - Google Patents

防止故障处理延迟 Download PDF

Info

Publication number
WO2018050122A1
WO2018050122A1 PCT/CN2017/102222 CN2017102222W WO2018050122A1 WO 2018050122 A1 WO2018050122 A1 WO 2018050122A1 CN 2017102222 W CN2017102222 W CN 2017102222W WO 2018050122 A1 WO2018050122 A1 WO 2018050122A1
Authority
WO
WIPO (PCT)
Prior art keywords
queue
equivalence class
time window
identifier
bfd session
Prior art date
Application number
PCT/CN2017/102222
Other languages
English (en)
French (fr)
Inventor
郭道荣
Original Assignee
新华三技术有限公司
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 新华三技术有限公司 filed Critical 新华三技术有限公司
Priority to US16/334,318 priority Critical patent/US11206176B2/en
Priority to JP2019515274A priority patent/JP6727424B2/ja
Priority to EP17850323.1A priority patent/EP3499801B1/en
Publication of WO2018050122A1 publication Critical patent/WO2018050122A1/zh

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/06—Management of faults, events, alarms or notifications
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L45/00—Routing or path finding of packets in data switching networks
    • H04L45/28—Routing or path finding of packets in data switching networks using route fault recovery
    • 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/06—Management of faults, events, alarms or notifications
    • H04L41/0631—Management of faults, events, alarms or notifications using root cause analysis; using analysis of correlation between notifications, alarms or events based on decision criteria, e.g. hierarchy, tree or time analysis
    • H04L41/064—Management of faults, events, alarms or notifications using root cause analysis; using analysis of correlation between notifications, alarms or events based on decision criteria, e.g. hierarchy, tree or time analysis involving time analysis
    • 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/06—Management of faults, events, alarms or notifications
    • H04L41/0681—Configuration of triggering conditions
    • 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/06—Management of faults, events, alarms or notifications
    • H04L41/0686—Additional information in the notification, e.g. enhancement of specific meta-data
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L43/00—Arrangements for monitoring or testing data switching networks
    • H04L43/08—Monitoring or testing based on specific metrics, e.g. QoS, energy consumption or environmental parameters
    • H04L43/0805—Monitoring or testing based on specific metrics, e.g. QoS, energy consumption or environmental parameters by checking availability
    • H04L43/0811—Monitoring or testing based on specific metrics, e.g. QoS, energy consumption or environmental parameters by checking availability by checking connectivity
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L43/00—Arrangements for monitoring or testing data switching networks
    • H04L43/08—Monitoring or testing based on specific metrics, e.g. QoS, energy consumption or environmental parameters
    • H04L43/0805—Monitoring or testing based on specific metrics, e.g. QoS, energy consumption or environmental parameters by checking availability
    • H04L43/0817—Monitoring or testing based on specific metrics, e.g. QoS, energy consumption or environmental parameters by checking availability by checking functioning
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L43/00—Arrangements for monitoring or testing data switching networks
    • H04L43/16—Threshold monitoring
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L47/00—Traffic control in data switching networks
    • H04L47/50—Queue scheduling
    • H04L47/56—Queue scheduling implementing delay-aware scheduling
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L47/00—Traffic control in data switching networks
    • H04L47/50—Queue scheduling
    • H04L47/62—Queue scheduling characterised by scheduling criteria
    • H04L47/625—Queue scheduling characterised by scheduling criteria for service slots or service orders
    • H04L47/6275—Queue scheduling characterised by scheduling criteria for service slots or service orders based on priority
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00—Network arrangements or protocols for supporting network services or applications
    • H04L67/14—Session management
    • H04L67/146—Markers for unambiguous identification of a particular session, e.g. session cookie or URL-encoding
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L45/00—Routing or path finding of packets in data switching networks
    • H04L45/68—Pseudowire emulation, e.g. IETF WG PWE3
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L47/00—Traffic control in data switching networks
    • H04L47/10—Flow control; Congestion control
    • H04L47/30—Flow control; Congestion control in combination with information about buffer occupancy at either end or at transit nodes

Definitions

  • BFD Bidirectional Forwarding Detection
  • Figure 1 is a flow chart of a method provided by the present disclosure
  • FIG. 2 is a structural diagram of an equivalence class set table provided by the present disclosure
  • FIG. 3 is a structural diagram of an equivalence class time window queue provided by the present disclosure.
  • FIG. 4 is a structural diagram of another equivalence class time window queue provided by the present disclosure.
  • FIG. 5 is a block diagram of an internal BFD system provided by the present disclosure.
  • Figure 6 is a flow chart of an embodiment of the present disclosure.
  • Figure 7 is a flow chart of another embodiment provided by the present disclosure.
  • Figure 8 is a schematic structural view of a device provided by the present disclosure.
  • FIG. 9 is a schematic diagram showing the hardware structure of the apparatus shown in FIG. 8 provided by the present disclosure.
  • the same public network path such as a public network tunnel
  • the pseudowire (PW) is used as an example, and different PWs are associated with different BFD sessions.
  • a BFD session is responsible for detecting whether its associated PW is faulty.
  • a common detection mode is as follows: The device periodically sends a BFD control packet to the peer device. If no N packets are sent continuously, the device considers that the associated PW is faulty and reports the Down event to the BFD driver. The BFD driver processes the received Down event.
  • the results detected by the BFD session carried by the public network path are inconsistent, and some BFD sessions are detected. Its associated PW is normal, and some BFD sessions detect that their associated PW is Down. In this inconsistency, BFD session detection misjudgment occurs, delaying the reporting of Down events, and eventually the fault is delayed.
  • the method provided by the present disclosure can prevent the delay of the Down event in the scenario of the public network path from being gradually disconnected, thereby preventing the fault processing delay caused by the delayed reporting of the Down event, and enhancing the performance of the BFD detection mechanism to adapt to the public network path to gradually disconnect the scenario.
  • FIG. 1 is a flowchart of a method provided by the present disclosure. As shown in Figure 1, the process can include the following steps:
  • Step 101 Receive a BFD session event.
  • the BFD session event is an event that is detected by a BFD session on its associated path (such as a PW), and carries at least a BFD session identifier and an event type identifier.
  • the event type identifier is specifically described below, and will not be described here.
  • Step 102 Obtain an equivalence class set identifier from a basic information entry matching the BFD session identifier carried in the BFD session event, where the equivalence class set identifier indicates an equivalence class set to which the BFD session corresponding to the BFD session identifier belongs.
  • each BFD session has a matching basic information entry.
  • the basic information of the BFD session is established in the initial stage of the BFD session.
  • the basic information items will be described below, and will not be described here.
  • the set of equivalence classes to which the BFD session belongs is determined according to the public network path that carries the BFD session.
  • different BFD sessions carried by the same public network path belong to the same set of equivalence classes.
  • the structure of the set of equivalence classes is described below. I won't go into details here.
  • Step 103 When the event type identifier carried in the BFD session event indicates a Down event, step 104 is performed.
  • Step 104 Add a queue element corresponding to the BFD session identifier to the equivalence class time window queue corresponding to the equivalence class set identifier, and determine whether the number of queue elements in the equivalence class time window queue is in a set time window. The set threshold is reached, and if so, the Down event is reported for each BFD session in the set of equivalence classes.
  • an equivalence class set corresponds to an equivalence class time window queue.
  • the Equivalent Class Time Window Queue is used to record the BFD session that reports the Down event.
  • the Equivalent Class Time Window Queue records the BFD session that reports the Down event.
  • the structure of the equivalence class time window queue the following will focus on the description, which will not be described here.
  • step 104 adding a queue element corresponding to the BFD session identifier to the equivalence class time window queue corresponding to the equivalence class set identifier includes:
  • the queue element corresponding to the BFD session identifier is added as the first queue element of the equivalence class time window queue to the equivalence class time window queue, and the timestamp of the added queue element is the current system. time;
  • the queue element corresponding to the BFD session identifier is added to the last queue element in the queue of the equivalence class time window, and the timestamp of the added queue element is the current system time.
  • the first queue element in the equivalence class time window queue is dynamically changed, and the dynamic change is specifically:
  • the BFD session is logically independent of each other.
  • the public network path is likely to fail.
  • the present disclosure reports the Down event to the BFD session in the Down state in a set event window, so that the Down event of the public network can be reported in the morning.
  • the first queue element in the queue of the equivalence class time window can be deleted. That is, the deleted queue element is not in the queue element of the equivalence class time window queue In the same time window, it is not possible to report the Down event to the Down BFD session in a set time window. It can be seen that the first queue element in the queue of the equivalence class time window is deleted over time. When the first queue element in the queue of the equivalence class time window is deleted, the first one is deleted. The second queue element after the queue element naturally becomes the first queue element.
  • the equivalence class time window queue can set a corresponding counter, which is used to count the number of queue elements in the equivalence class time window queue.
  • the counter corresponding to the equivalence class time window queue can be updated accordingly. For example, to add a queue element to the equivalence class time window queue, the counter is incremented by one.
  • the present disclosure reports the corresponding Down event for each BFD session in the set of equivalence classes. This prevents the delay of the Down event in the scenario where the public network path is gradually disconnected. This prevents the fault processing delay caused by the delayed reporting of the Down event.
  • the BFD detection mechanism is adapted to the performance of the public network path to disconnect the scene. Defects detected by the BFD mechanism under signal degradation.
  • Basic information table consists of basic information items. The basic information entry matches the BFD session.
  • Sid BFD session ID. Each BFD session has a unique identifier.
  • Valid The valid identifier of the entry. When the Valid is 1, for example, the basic information entry is valid. Otherwise, when the Valid is 0, the basic information entry is invalid.
  • 3) Status The status of the BFD session, which may include operation (UP), failure (Down), initialization (Init), etc.;
  • Class ID The identifier of the set of equivalence classes to which the BFD session belongs. All BFD sessions that are carried on the same public network path are classified into the same set of equivalence classes.
  • Table 1 shows an example of a basic information table.
  • the basic information table matching the BFD session identifier carried in the BFD session event in the basic information table is as follows:
  • the BFD session ID carried in the BFD session is used as the keyword.
  • the basic information table is used to search for the basic information of the keyword.
  • the basic information of the BFD session is matched with the BFD session ID of the BFD session. Information item.
  • Equivalence class collection table consists of a collection of equivalence classes. Initially, there is no equivalence class set element in each equivalence class set in the equivalence class collection table.
  • the identifier of the BFD session in the UP state is formed into a corresponding equivalence class set element and added to the equivalence class set to which the BFD session belongs.
  • the BFD session ID of the Down state is used as the key, and the equivalence class set element corresponding to the keyword is deleted from the equivalence class set to which the BFD session belongs.
  • the identifier of the deleted BFD session is used as a key, and the equivalence class set element corresponding to the keyword is deleted from the equivalence class set to which the BFD session belongs.
  • the identifier of the BFD session associated with the deleted PW is used as a key, and the equivalence class set element corresponding to the keyword is deleted from the equivalence class set to which the BFD session belongs.
  • the equivalence class set table may be a two-dimensional linked list.
  • each two-dimensional linked list item represents a set of equivalence classes, and each two-dimensional linked list item is mainly composed of a header and a corresponding equivalence class set element.
  • the header consists of the following three parts:
  • NextClass points to the next set of equivalence classes
  • ClassID the identifier of the equivalence class
  • HeadPtr points to the first equivalence class set element in the two-dimensional linked list item
  • the equivalence class collection element consists of the following three parts:
  • Sid BFD session ID. Each BFD session has an identifier. You can find the corresponding data information through this ID.
  • Prev points to the previous equivalence class set element. For the first equivalence class set element, Prev points to the header;
  • Fig. 2 exemplifies the structure of an equivalence class set table.
  • the equivalence class collection table stores the identifier of the BFD session in the UP state, and the number of queue elements in the queue of the equivalence class time window reaches within the set time window.
  • a threshold is set, a Down event is reported for each BFD session in the equivalence class set.
  • the equivalent time window queue is used to record the BFD session that reports the Down event. Based on this, when the BFD session with the Down event is added to the queue of the equivalent time window, if the BFD session is added, It is also recorded in the equivalence class set table.
  • the newly added BFD session may be further deleted from the corresponding equivalence class set.
  • the identifier corresponds to the equivalence class collection element.
  • a corresponding counter can be set for the set of equivalence classes, and the counter is used to count the number of BFD session identifiers in the set of equivalence classes.
  • Equivalence class time window queue list consists of an equivalence class time window queue.
  • the structure of the equivalence class time window queue list is similar to the structure of the equivalence class set.
  • the equivalence class time window team list is preferably a two-dimensional linked list.
  • each two-dimensional linked list item represents an equivalence class time window queue, and each two-dimensional linked list item is mainly composed of a header and a queue element.
  • the header consists of the following three parts:
  • NextQue points to the next equivalence class time window queue
  • ClassID the identifier of the equivalence class
  • HeadPtr the first queue element pointing to this two-dimensional linked list item
  • the queue element consists of the following three parts:
  • Prev points to the previous queue element.
  • Prev points to the header
  • the equivalence class time window queue in the equivalence class time window queue list has no queue elements, as shown in Figure 3.
  • the present disclosure provides a BFD detection structure to prevent a failure processing delay caused by delay reporting of a Down event.
  • the general BFD monitoring structure includes: a switching chip located at the hardware layer (FIG. 5 takes FIRMWARE/FPGA as an example) 501 and switching hardware 502, a driving layer BFD driving module 511, and a switching platform driving module 512, and a platform.
  • the present disclosure adds a processing module 503 between the driver layer and the hardware layer.
  • the newly added processing module 503 is connected between the BFD driver module 511 of the driver layer and the switch chip 501 of the hardware layer, as shown in FIG. 5.
  • the processing module 503 of the present disclosure may be in the form of software or hardware.
  • the processing module 503 can be configured in the driver layer, but does not change the core process of the original processing BFD session, and at the same time ensures that the execution of the original modules of each layer is not affected.
  • it can be integrated, for example, in an FPGA or integrated into one core of a multi-core CPU.
  • FIG. 6 is a flowchart of an embodiment provided by the present disclosure. The flow of this embodiment is performed by the processing module shown in FIG. As shown in FIG. 6, the process may include the following steps:
  • step 601 the firmware event is monitored.
  • the hardware layer of the BFD is implemented by the switch chip FIRMWARE/FPGA. Therefore, as an example, the BFD session event is taken as an example of the Firmware event.
  • the firmware event may be triggered by the BFD session becoming the UP state, or may be triggered by the BFD session becoming the Down state, and so on, which will be specifically described below.
  • the Firmware event carries at least the BFD session identifier and the event type identifier.
  • the firmware event is triggered by the BFD session being in the Up state.
  • the BFD session ID carried in the Firmware event is the ID of the BFD session in the UP state.
  • the type identifier is the identifier of the UP event.
  • the BFD session identifier carried in the Firmware event is recorded as Sid1 in this embodiment.
  • Step 602 Parse the Sid1 carried by the Firmware event when the Firmware event is detected.
  • step 603 a basic information entry (named as basic information entry 1) matching the Sid1 is found in the basic information table.
  • step 604 is performed.
  • the basic information entry matching the Sid1 in the basic information table is specifically: the Sid is found as the key in the basic information table, and the basic information of the keyword is found in the basic information table.
  • the information item is the basic information table item that the Sid1 matches.
  • the firmware event is reported to the BFD driver module, and the BFD driver module performs corresponding processing according to the event type identifier carried in the firmware event. Let me repeat.
  • step 604 the event type matching the event type identifier carried in the firmware event is found in the feature table, and when the session state in the basic information table item 1 is UP, the process shown in FIG. 7 is executed. 605.
  • session state in the basic information table item described above further includes Init or the like, in the present disclosure, only the case where the session state is UP or Down is described in detail, and other cases are not described in detail.
  • a feature table is used to store user customization information, and includes the following feature table items:
  • MaxSessions The maximum number of sessions supported by the network side edge device (PE: Provider Edge), such as support for 512 BFD sessions.
  • PE Provider Edge
  • Admin Down Event Admin (Down) event, with the corresponding event type identifier (recorded as the first ID); when the user actively deletes the BFD session, it means the Admin Down event (Event);
  • BFD Down Event BFD Down event, with the corresponding event type identifier (marked as the second identifier);
  • the BFD session that reports the Down event in this time window is considered to be a Down event at the same time; as described below, it will not be described here;
  • the threshold is set: that is, the set threshold in the above step 104.
  • Table 2 exemplifies the feature table.
  • step 604 is specifically: if the event type identifier carried by the firmware event is the first identifier, such as 0, it is determined that the event type of the firmware event is Admin Down Event; if the event type identifier carried by the firmware is If the identifier is 2, the event type identifier carried by the firmware event is matched to the event type. If the event type identifier of the firmware is 3, for example, 3, the event type identifier carried by the firmware event is matched. The event type is UP Event.
  • "set time window size" and “set threshold” can be configured by the user according to the actual situation. For example, when the sending interval of the BFD session is 10 ms and the number of consecutive monitoring times is 3, the set time window may be 2 ms, and the set threshold may be 3.
  • Step 605 When the event type matched in step 604 is UP Event, Sid1 is formed into a corresponding equivalence class set element and placed in the equivalence class set corresponding to the equivalence class set identifier in the basic information table item 1.
  • Sid1 is formed into a corresponding equivalence class set element and placed in the equivalence class set corresponding to the equivalence class set identifier in the basic information table item 1: specifically: The two-dimensional linked list entry containing the keyword is found in the two-dimensional linked list (the two-dimensional linked list corresponding to the equivalence class set) by using the equivalence class set identifier in the basic information table item 1 as a key, and the found one is found in the two-dimensional linked list (the two-dimensional linked list corresponding to the equivalence class set).
  • An equivalence class set element corresponding to Sid1 is added to the equivalence class set corresponding to the two-dimensional linked list item.
  • the equivalence class set element corresponding to Sid1 is specifically constructed according to the structure of the equivalence class set element as described above.
  • the event type matched in step 604 can also be Down Event and Admin Down Event.
  • this step 605 when the event type matched in step 604 is found to be Down Event or Admin Down Event, the current mode is directly
  • the above-mentioned firmware event is reported to the BFD driver module, and the BFD driver module performs corresponding processing according to the event type identifier carried in the firmware event, which is not described here.
  • FIG. 7 is a flowchart of another embodiment provided by the present disclosure. As described above, the flow is executed when it is determined in the above step 604 that the session state in the basic information table item 1 is UP.
  • the process may include:
  • step 701 it is determined that the event type matched in step 604 is Down Event or Admin Down Event. If the event is Down Event, step 702 is executed.
  • This step 701 is performed when the session state in the basic information table item 1 is UP.
  • the event type that is matched in the foregoing step 704 is an event type other than the Down Event and the Admin Down Event, such as an UP Event, and the above-mentioned Firmware event is reported to the BFD driving module, and the BFD driving module is based on the BFD driving module.
  • the event type identifier carried in the firmware event is processed accordingly, and is not mentioned here.
  • step 702 the session state in the basic information entry 1 is updated to be Down. Then step 703 is performed.
  • Step 703 Find a corresponding equivalent time window queue (recorded as queue 1) according to the equivalence class set identifier in the basic information table item 1.
  • step 703 is specifically: using the equivalence class set identifier in the basic information table item 1 as a keyword in the two-dimensional linked list (the equivalent of the equivalence class time window queue list) In the dimension list, a two-dimensional linked list entry containing the keyword is found in the header, and the found two-dimensional linked list entry is recorded as the queue 1 above.
  • step 704 it is determined whether the queue 1 is empty. If yes, step 705 is performed, and if no, step 706 is performed.
  • step 705 the queue element corresponding to the Sid1 is added to the queue 1 as the first queue element of the queue 1, and the timestamp of the added queue element is the current system time. Then step 709 is performed.
  • step 705 is specifically: forming Sid1 into a corresponding queue element according to the structure of the queue element in the equivalence class time window queue, and adding to queue 1 (that is, the above Step 703 finds the two-dimensional linked list item).
  • the queue element added at this point is the first queue element in queue 1.
  • Step 706 Calculate the difference between the current system time and the timestamp of the first queue element in the queue 1, and compare the calculation result with the set time window size in the local feature table. If the former is greater than the latter, step 707 is performed, if the former is smaller than Or equal to the latter, step 708 is performed.
  • step 707 the first queue element in the queue 1 is deleted, and the queue element corresponding to the Sid1 is added to the last queue element in the queue 1.
  • the timestamp of the added queue element is the current system time. End the current process.
  • step 708 the queue element corresponding to Sid1 is added to the last queue element in queue 1, and the timestamp of the added queue element is the current system time. Then step 709 is performed.
  • step 709 it is determined whether the number of the queue elements in the queue 1 reaches the set threshold in the feature table, and if so, the Down event is reported in each BFD session in the equivalence class set corresponding to the basic information set item 1 And clear all the queue elements in queue 1 and clear all the equivalence class set elements in the equivalence class set corresponding to the basic information table item 1 equal price class set identifier.
  • the queue class corresponds to the equivalence class corresponding to the media class class identifier of the basic information class 1
  • All the equivalence class set elements in the set have no meaning, so in order to save the storage resources, as an embodiment, this step 709 clears the equivalent of all the queue elements in the queue 1 and the clear basic information table item 1 parity class set identifier. All equivalence class collection elements in a collection of classes.
  • the above-mentioned firmware event can be reported to the BFD driver module, and the BFD driver module performs corresponding processing according to the event type identifier carried in the firmware event, and details are not described herein again.
  • the reporting of the Down event for each BFD session in the set of equivalence classes also means reporting the Down event of each BFD session in the equivalence class set to the BFD driver module.
  • the BFD driver module processes the Down event according to the Down event. Narration.
  • Step 710 Update the session state in the basic information entry 1 to Down, and report the monitored firmware event to the BFD driver module. End the current process.
  • the BFD driver module After receiving the Firmware event, the BFD driver module processes the fault according to the Firmware event, which is not mentioned here.
  • the following scenario is adopted: 64 BFD sessions are carried on the same public network path, the detection period of the BFD session is 10 ms, and three detection packets need to be sent in the detection period.
  • the Down event reporting delay is more than 128ms, which is much longer than the telecom request packet delay of 50ms. After the method provided by the present disclosure, the Down event reporting delay is less than 30ms, which greatly shortens the Down event reporting delay.
  • FIG. 8 is a structural diagram of a device provided by the present disclosure. As shown in Figure 8, the device includes:
  • the receiving unit 801 is configured to receive a BFD session event, where the BFD session event carries a BFD session identifier and an event type identifier.
  • the obtaining unit 802 is configured to obtain an equivalence class set identifier from the basic information entry that matches the BFD session identifier, where the equivalence class set identifier indicates an equivalence class set to which the BFD session corresponding to the BFD session identifier belongs.
  • the BFD session carried by the same public network path belongs to the same set of equivalence classes;
  • the control unit 803 is configured to: when the event type identifier indicates a Down event, add a queue element corresponding to the BFD session identifier to an equivalence class time window queue corresponding to the equivalence class set identifier, and determine the equivalent Whether the number of queue elements in the time-type window queue reaches a set threshold within a set time window, and if so, reports a Down event for each BFD session in the corresponding equivalence class set of the equivalence class set identifier.
  • control unit 803 further deletes the equivalence class set element corresponding to the BFD session identifier from the corresponding equivalence class set of the equivalence class set identifier.
  • control unit 803 adds the queue element corresponding to the BFD session identifier to the equivalence class time window queue corresponding to the equivalence class set identifier, including:
  • the queue element corresponding to the BFD session identifier is added as the first queue element of the equivalence class time window queue to the equivalence class time window queue, and the timestamp of the added queue element is the current system. time;
  • the queue element corresponding to the BFD session identifier is added to the last queue element in the queue of the equivalence class time window, and the timestamp of the added queue element is the current system time.
  • control unit 803 adds a queue element corresponding to the BFD session identifier to the last queue element in the queue of the equivalence class time window, including:
  • the reporting, by the control unit 803, the Down event for each BFD session in the set of equivalence classes further includes:
  • the event type identifier indicates that the UP event is initiated
  • the session state in the basic information entry that matches the BFD session identifier is Down
  • the BFD session identifier is corresponding to the BFD session identifier.
  • An equivalence class set element is added to the equivalence class set corresponding to the equivalence class binding identifier;
  • the event type identifier indicates an Admin Down event
  • the session state in the basic information entry matching the BFD session identifier is UP
  • the corresponding equivalence class set is identified from the equivalence class set identifier.
  • the equivalence class set element corresponding to the BFD session identifier is deleted, and the BFD session event is reported. So far, the structural description of the apparatus shown in Fig. 8 is completed.
  • FIG. 9 is a schematic structural diagram of hardware of the apparatus shown in FIG. 8 according to the present disclosure.
  • the apparatus includes a processor 901, and a machine readable storage medium 902 that stores machine executable instructions.
  • Processor 901 and machine readable storage medium 902 can communicate via system bus 903. And, by reading and executing machine executable instructions in machine readable storage medium 902, processor 901 can perform the methods described above.
  • the hardware structure can also include a power supply component 904 configured to perform power management of the switching device, a wired or wireless network interface 905 configured to connect the device to the network, and an input and output (I) /O) interface 906.
  • the machine-readable storage medium 902 referred to herein can be any electronic, magnetic, optical, or other physical storage device that can contain or store information such as executable instructions, data, and the like.
  • the machine-readable storage medium may be: RAM (Radom Access Memory), volatile memory, non-volatile memory, flash memory, storage drive (such as a hard disk drive), solid state drive, any type of storage disk. (such as a disc, dvd, etc.), or a similar storage medium, or a combination thereof.
  • the machine readable storage medium 902 is configured to store program instructions run by the receiving unit 801, program instructions run by the obtaining unit 802, and program instructions run by the control unit 803;
  • the processor 901 is configured to execute program instructions executed by the receiving unit 801, program instructions for executing the operation of the obtaining unit 802, and program instructions for executing the operation of the control unit 803.
  • the processor 901 implements the method as described above by executing program instructions executed by the respective units as described above.
  • a processing apparatus including:
  • a machine-readable storage medium storing machine-executable instructions, wherein by executing machine-executable instructions in the machine-readable storage medium, the processor is caused to:
  • BFD bidirectional forwarding detection
  • the processor is further caused to:
  • the processor is further caused by:
  • the queue element corresponding to the BFD session identifier is added as the first queue element of the equivalence class time window queue to the equivalence class time window queue, and the timestamp of the added queue element is the current system. time;
  • the queue element corresponding to the BFD session identifier is added to the last queue element in the queue of the equivalence class time window, and the timestamp of the added queue element is the current system time.
  • the processor is further caused by:
  • the queue element corresponding to the BFD session identifier is added to the last queue element in the queue of the equivalence class time window.
  • the processor After reporting a Down event for each BFD session in the set of equivalence classes corresponding to the equivalence class set identifier, the processor is further caused to:
  • the processor is also caused to:
  • the equivalence class set element corresponding to the BFD session identifier is added to the equivalence class set corresponding to the equivalence class set identifier;
  • the session state in the basic information entry that matches the BFD session identifier is UP, the equivalence class set element corresponding to the BFD session identifier is deleted from the equivalence class set corresponding to the equivalence class set identifier, and The BFD session event is reported.
  • the device embodiment since it basically corresponds to the method embodiment, reference may be made to the partial description of the method embodiment.
  • the device embodiments described above are merely illustrative, wherein the units described as separate components may or may not be physically separate, and the components displayed as units may or may not be physical units, ie may be located A place, or it can be distributed to multiple network units. Some or all of the modules may be selected according to actual needs to achieve the purpose of the solution of the embodiment. Those of ordinary skill in the art can understand and implement without any creative effort.

Landscapes

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

Abstract

本公开提供了防止故障处理延迟的方法及装置。本公开中，当等价类时间窗口队列中的队列元素的数量在设定时间窗口内达到设定阈值(记为N)时，也就意味着同一等价类集合中有N个BFD会话检测到Down事件，智能推断出承载该N个BFD会话的公网路径故障，为便于上层及时处理故障，减少数据流丢失，本公开可针对N个BFD会话所属的等价类集合中每一BFD会话上报对应的Down事件。

Description

防止故障处理延迟
相关申请的交叉引用
本专利申请要求于2016年9月19日提交的、申请号为201610830946.x、发明名称为“防止故障处理延迟的方法和装置”的中国专利申请的优先权，该申请的全文以引用的方式并入本文中。
背景技术
双向转发检测(BFD:Bidirectional Forwarding Detection)是一个通用的、标准化的、与介质无关和协议无关的快速故障检测机制，用于检测IP网络中链路的连通状况，保证设备之间能够快速检测到通信故障，以便能够及时采取措施，保证业务持续运行。BFD可以为各种上层协议如路由协议、MPLS等快速检测两台设备间双向转发链路的故障。BFD能够实现毫秒级故障检测。
附图说明
图1为本公开提供的方法流程图；
图2为本公开提供的等价类集合表的结构图；
图3为本公开提供的等价类时间窗口队列的结构图；
图4为本公开提供的另一等价类时间窗口队列的结构图；
图5为本公开提供的BFD内部系统框图；
图6为本公开提供的一实施例流程图；
图7为本公开提供的另一实施例流程图；
图8为本公开提供的装置结构示意图；
图9为本公开提供的图8所示装置的硬件结构示意图。
具体实施方式
下面将结合本公开实施例中的附图，对本公开实施例中的技术方案进行清楚、完整地描述，显然，所描述的实施例仅仅是本公开一部分实施例，而不是全部的实施例。基于本公开中的实施例，本领域普通技术人员在没有做出创造性劳动前提下所获得的所有其他实施例，都属于本公开保护的范围。
在应用中，同一条公网路径比如公网隧道可虚拟化出不同路径，以伪线(PW)为例，而不同PW关联不同BFD会话。BFD会话负责检测其关联的PW是否故障。常见的检测方式为：设备周期性地向对端设备发送BFD控制报文，当连续发送N个报文均没有收到对端回应，则认为其相关联的PW故障，向BFD驱动上报Down事件，BFD驱动根据收到的Down事件进行处理。
但是，在公网路径的网络信号衰减直至断开的场景(简称公网路径逐步断开场景)中，该公网路径承载的各个BFD会话检测到的结果是不一致的，有的BFD会话检测到其相关联的PW正常，而有的BFD会话检测到其相关联的PW断开(Down)。这种不一致中会出现BFD会话检测误判，延迟了Down事件上报，最终会导致故障被延迟处理。
本公开提供的方法能够避免公网路径逐步断开场景中Down事件延迟上报，进而防止因为Down事件延迟上报而导致的故障处理延迟，增强BFD检测机制适应于公网路径逐步断开场景的性能。
下面对本公开提供的方法进行描述：
参见图1，图1为本公开提供的方法流程图。如图1所示，该流程可包括以下步骤:
步骤101，接收BFD会话事件。
作为一个实施例，这里的BFD会话事件举例为BFD会话对其相关联的路径(比如PW等)检测到的事件，至少携带BFD会话标识、事件类型标识。事件类型标识具体在下文描述，这里暂不赘述。
步骤102，从BFD会话事件携带的BFD会话标识匹配的基本信息表项中获取等价类集合标识，所述等价类集合标识表示BFD会话标识对应的BFD会话所属的等价类集合。
在本公开中，每一BFD会话都有一个匹配的基本信息表项。其中，BFD会话匹配的基本信息表项建立在BFD会话创建初期。下文会重点描述基本信息表项，这里暂不赘述。
在本公开中，BFD会话所属的等价类集合是根据承载BFD会话的公网路径确定的。优选地，同一公网路径承载的不同BFD会话同属一个等价类集合。下文会描述等价类集合的结构， 这里暂不赘述。
步骤103，当BFD会话事件携带的事件类型标识表示Down事件时，执行步骤104。
步骤104，将BFD会话标识对应的队列元素添加至所述等价类集合标识对应的等价类时间窗口队列，判断所述等价类时间窗口队列中的队列元素的数量是否在设定时间窗口内达到设定阈值，如果是，针对所述等价类集合中每一BFD会话上报Down事件。
在本公开中，一个等价类集合对应一个等价类时间窗口队列。等价类时间窗口队列用于记录上报Down事件的BFD会话，换言之，等价类时间窗口队列记录的是上报了Down事件的BFD会话。至于等价类时间窗口队列的结构，下文会重点描述，这里暂不赘述。
作为一个实施例，步骤104中，将BFD会话标识对应的队列元素添加至所述等价类集合标识对应的等价类时间窗口队列包括：
判断所述等价类时间窗口队列是否为空，
如果是，将所述BFD会话标识对应的队列元素作为所述等价类时间窗口队列的第一个队列元素添加至所述等价类时间窗口队列中，添加的队列元素的时间戳为当前系统时间；
如果否，将所述BFD会话标识对应的队列元素添加至所述等价类时间窗口队列中最后一个队列元素的后面，添加的队列元素的时间戳为当前系统时间。
在本公开中，等价类时间窗口队列中的第一个队列元素是动态变化的，该动态变化具体为：
在将BFD会话标识作为队列元素添加至所述等价类时间窗口队列中最后一个队列元素的后面之前，计算当前系统时间与所述等价类时间窗口队列中第一个队列元素的时间戳之差，在计算结果大于设定时间窗口大小时，删除所述等价类时间窗口队列中第一个队列元素。
由于BFD会话在逻辑上是相互独立的，当在足够小的一段时间内，同一等价类窗口队列中有多个BFD会话Down时，公网路径极有可能出现故障。在此情况下，本公开通过将在一个设定事件窗口内变为Down状态的BFD会话上报Down事件，从而可以尽早上报公网的Down事件。
若第一个队列元素与当前上报的Down事件的队列元素的时间间隔很长，即不在同一个时间窗口，则此时将第一个队列元素保留在等价类时间窗口队列中也无法作为准确判断公网路径异常的依据。因此，当计算结果大于设定时间窗口大小时，可删除等价类时间窗口队列中第一个队列元素。也就是，被删除的队列元素与等价类时间窗口队列中其他队列元素不在 同一个时间窗口，无法实现将在一个设定时间窗口内Down的BFD会话上报Down事件的目的。可以看出，等价类时间窗口队列中的第一个队列元素随着时间变化会被删除，当等价类时间窗口队列中的第一个队列元素被删除时，原先在被删除的第一个队列元素后面的第二个队列元素就自然成为第一个队列元素了。
在获取等价类时间窗口队列中队列元素的数量时，等价类时间窗口队列可以设置相应的计数器，该计数器用于统计在等价类时间窗口队列中队列元素的数量。当接收到BFD会话Down事件，将BFD会话标识添加至等价类时间窗口队列时，可以相应的更新与该等价类时间窗口队列对应的计数器。举例来说，向等价类时间窗口队列中添加一个队列元素，则计数器加一。
至此，完成图1所示的流程。通过图1所示流程可以看出，当等价类时间窗口队列中的队列元素的数量在设定时间窗口内达到设定阈值(记为N)时，也就意味着在预设时间内同一等价类集合中有N个BFD会话分别检测到Down事件。基于此，可推断出该等价类集合对应的公网路径(实质是承载等价类集合中各BFD会话的同一公网路径)故障。为便于上层及时处理故障，减少数据流丢失，如步骤104的描述，本公开针对等价类集合中每一BFD会话上报对应的Down事件。这避免了公网路径逐步断开场景中Down事件延迟上报，进而防止了因为Down事件延迟上报而导致的故障处理延迟，增强BFD检测机制适应于公网路径逐步断开场景的性能，有效弥补了信号劣化下BFD机制检测的缺陷。
下面对本公开涉及的几个表项进行描述：
基本信息表：由基本信息表项组成。基本信息表项与BFD会话匹配。
BFD会话匹配的基本信息表项主要包含：
1)Sid：BFD会话标识，每一个BFD会话有唯一的标识；
2)Valid：表项有效标识，当Valid为比如1时，表示此基本信息表项有效，反之，当Valid为比如0时，表示此基本信息表项无效；
3)Status：BFD会话的状态，其可包含运行(UP)、故障(Down)、初始化(Init)等；
4)Class ID：BFD会话所属等价类集合的标识。等价类集合按照公网路径划分，承载在同一公网路径的所有BFD会话被划分为属于同一等价类集合。
表1举例示出了基本信息表。
Sid Valid Status ClassID
0 1 Up 1
1 1 NotUp N
2 1 NotUp 1
... ... ... ...
509 1 Up N
510 1 Up 1
511 0 Up -
表1
基于这里描述的基本信息表项的结构，则上述步骤102中在基本信息表中找到与BFD会话事件携带的BFD会话标识匹配的基本信息表项具体为：
以BFD会话事件携带的BFD会话标识为关键字，在基本信息表中查找Sid为该关键字的基本信息表项，将找到的基本信息表项作为与BFD会话事件携带的BFD会话标识匹配的基本信息表项。
等价类集合表：由等价类集合组成。初始，等价类集合表中各等价类集合内没有等价类集合元素。
当BFD会话变为UP状态时，则将该UP状态的BFD会话的标识构成一个对应的等价类集合元素并加入该BFD会话所属的等价类集合；
当BFD会话变为Down状态时，则以该Down状态的BFD会话的标识为关键字，从该BFD会话所属的等价类集合中删除该关键字对应的等价类集合元素；
当删除BFD会话时，则以该被删除的BFD会话的标识为关键字，从该BFD会话所属的等价类集合中删除该关键字对应的等价类集合元素；
当删除BFD会话关联的PW时，则将该被删除的PW关联的BFD会话的标识为关键字，从该BFD会话所属的等价类集合中删除该关键字对应的等价类集合元素。
作为一个实施例，等价类集合表可为一个二维链表。在二维链表中，每一二维链表项代表一个等价类集合，每一二维链表项主要由表头和对应的等价类集合元素组成。
表头由以下三部分组成：
NextClass：指向下一个等价类集合；
ClassID：等价类集合标识；
HeadPtr：指向本二维链表项中的第一个等价类集合元素；
等价类集合元素由以下三部分组成：
Sid：BFD会话标识，每一个BFD会话有一个标识，通过这个标识可以找到相应的数据信息；
Prev：指向前一个等价类集合元素，对于第一个等价类集合元素，Prev指向表头；
Next：指向下一个等价类集合元素，对于最后一个等价类集合元素，Next为空。
图2举例示出了等价类集合表的结构。如上描述的等价类集合表，则可以看出，等价类集合表存放的是UP状态的BFD会话的标识，当等价类时间窗口队列中的队列元素的数量在设定时间窗口内达到设定阈值时，会针对等价类集合中每一BFD会话上报Down事件。而如上描述，等价类时间窗口队列用于记录上报Down事件的BFD会话，基于此，当等价类时间窗口队列中新增加上报了Down事件的BFD会话时，如果该增加的BFD会话此时还记录在等价类集合表，则为避免针对同一BFD会话重复上报Down事件，需要从等价类集合中删除该BFD会话。基于此，上述步骤104中在等价类时间窗口队列中的队列元素的数量在设定时间窗口内达到设定阈值时，还可进一步从相应的等价类集合中删除该新增加的BFD会话的标识对应的等价类集合元素。相应的，可以为等价类集合设置相应的计数器，该计数器用于统计等价类集合中BFD会话标识的数量。
等价类时间窗口队列表：由等价类时间窗口队列组成。等价类时间窗口队列表的结构类似等价类集合的结构。
在本公开中，等价类时间窗口队列表优选为一个二维链表。二维链表中，每一二维链表项代表一个等价类时间窗口队列，每一二维链表项主要由表头和队列元素组成。
表头由以下三部分组成：
NextQue：指向下一个等价类时间窗口队列；
ClassID：等价类集合标识；
HeadPtr：指向本二维链表项的第一个队列元素；
队列元素由以下三部分组成：
Sid：BFD会话标识；
Prev：指向前一个队列元素，第一个队列元素时，Prev指向表头；
Next：指向下一个队列元素，最后一个队列元素时，Next为空。
初始，等价类时间窗口队列表中各等价类时间窗口队列没有队列元素，具体如图3所示。
而当有BFD会话变为Down状态时，可将该Down状态的BFD会话的标识构成一个对应的队列元素加入至对应的等价类时间窗口队列中。图4示出了BFD会话变为Down状态时某时刻的等价类时间窗口队列状态。
基于上面描述的各表项，下面通过一个实施例对图1所示流程进行描述：
作为一个实施例，在本公开中，为防止因为Down事件延迟上报而导致的故障处理延迟，本公开提供了一种BFD检测结构。如图5所示，一般的BFD监测结构包括：位于硬件层的交换芯片(图5以FIRMWARE/FPGA为例)501和交换硬件502，驱动层的BFD驱动模块511和交换平台驱动模块512，平台软件内核中的BFD内核态模块521和MPLS内核态模块522，平台软件用户态中的BFD用户态模块531和MPLS用户态模块532，以及路由协议族540。本公开在驱动层和硬件层之间新增加处理模块503，该新增加的处理模块503连接在驱动层的BFD驱动模块511和硬件层的交换芯片501、之间，具体如图5所示。需要说明的是，本公开的处理模块503可以为软件形式也可以为硬件形式。当为软件形式时，该处理模块503可以被配置在驱动层，但并不改变原有处理BFD会话的核心流程，并同时保证不影响各层原有模块的执行。当为硬件形式时，可以例如集成在FPGA中或者集成在多核CPU的一个核中。
参见图6，图6为本公开提供的一实施例流程图。该实施例流程是由图5所示的处理模块执行。如图6所示，该流程可包括以下步骤：
步骤601，监听Firmware事件。
图5以BFD的硬件层由交换芯片FIRMWARE/FPGA实现为例，因此，作为一个实施例，这里以BFD会话事件为Firmware事件为例。
在本实施例中，该Firmware事件可能是因为BFD会话变为UP状态触发的，也可能是因为BFD会话变为Down状态触发的，等等，下文会具体描述。在本公开中，Firmware事件至少携带了BFD会话标识、事件类型标识。比如，Firmware事件是因为BFD会话变为UP状态触发的，则Firmware事件携带的BFD会话标识就为该UP状态的BFD会话的标识，事件 类型标识为UP事件(Event)的标识。
为便于描述，在本实施例中将Firmware事件携带的BFD会话标识记为Sid1。
步骤602，当监听到Firmware事件时，解析Firmware事件携带的Sid1。
步骤603，在基本信息表中找到Sid1匹配的基本信息表项(记为基本信息表项1)，当匹配出的基本信息表项1中的Valid为有效值时，执行步骤604。
基于上面描述的基本信息表项的结构，本步骤603中，在基本信息表中找到Sid1匹配的基本信息表项具体为：以Sid1为关键字在基本信息表中找到Sid为该关键字的基本信息表项，找到的基本信息表项为Sid1匹配的基本信息表项。
作为一个实施例，当匹配出的基本信息表项1中的Valid为无效值时，将Firmware事件上报给BFD驱动模块，由BFD驱动模块依据Firmware事件携带的事件类型标识进行相应的处理，这里不再赘述。
步骤604，在特征表中找到Firmware事件携带的事件类型标识匹配的事件类型，并在基本信息表项1中的会话状态为UP时，执行如图7所示的流程，为Down时，执行步骤605。
虽然如上描述的基本信息表项中的会话状态还包含Init等，但在本公开中，仅对会话状态为UP、Down时进行详细描述，其他情况不作详细描述。
在本公开中，特征表，用于存放用户定制信息，包含以下几个特征表项：
MaxSessions：网络侧边缘设备(PE：Provider Edge)支持的最大会话数，比如支持512个BFD会话。
Admin Down Event：管理(Admin)Down事件，具有对应的事件类型标识(记为第一标识)；当用户主动删除BFD会话时，意味着Admin Down事件(Event)；
Down Event：BFD Down事件，具有对应的事件类型标识(记为第二标识)；
UP Event：BFD会话UP事件，具有对应的事件类型标识(记为第三标识)；
设定时间窗口大小：在这个时间窗口内上报Down事件的BFD会话，认定为是同时报Down事件的；下文会描述到，这里暂不赘述；
设定阈值：即上述步骤104中的设定阈值。表2举例示出了特征表。
Name Value 备注
MaxSessions 512  
Admin Down Event 0 第一标识
Down Event 2 第二标识
UP Event 3 第三标识
设定时间窗口大小    
设定阈值    
表2
基于上面描述的特征表，则步骤604具体为：假如Firmware事件携带的事件类型标识为第一标识比如0，则确定该Firmware事件的事件类型为Admin Down Event；假如Firmware携带的事件类型标识为第二标识比如2，则确定Firmware事件携带的事件类型标识匹配的事件类型为Down事件(Event)；假如Firmware携带的事件类型标识为第三标识比如3，则确定Firmware事件携带的事件类型标识匹配的事件类型为UP Event。在表2中，“设定时间窗口大小”和“设定阈值”可以由用户根据实际情况进行配置。例如，在BFD会话的发包间隔为10ms、连续监测次数为3次的情况下，该设定时间窗口大小可以为2ms，设定阈值可以为3。
步骤605，在步骤604匹配出的事件类型为UP Event时，将Sid1构成一个对应的等价类集合元素并放入基本信息表项1中的等价类集合标识对应的等价类集合中。
基于上面描述的等价类集合的结构，步骤605中将Sid1构成一个对应的等价类集合元素并放入基本信息表项1中的等价类集合标识对应的等价类集合中具体为：以基本信息表项1中的等价类集合标识为关键字，在二维链表(等价类集合对应的二维链表)中找到表头包含该关键字的二维链表项，向该找到的二维链表项对应的等价类集合中添加Sid1对应的等价类集合元素。Sid1对应的等价类集合元素具体是按照如上描述的等价类集合元素的结构构成的。
如上描述，步骤604匹配出的事件类型还可为Down Event、Admin Down Event，在本步骤605中，当发现步骤604匹配出的事件类型为Down Event、或者Admin Down Event，则按照现有方式直接上报上述的Firmware事件给BFD驱动模块，由BFD驱动模块依据Firmware事件携带的事件类型标识进行相应的处理，这里不再赘述。
至此，完成图6所示的流程。
参见图7，图7为本公开提供的另一实施例流程图。如上描述，该流程是在上述步骤604确定出基本信息表项1中的会话状态为UP时执行的。
如图7所示，该流程可包括：
步骤701，判断步骤604匹配出的事件类型为Down Event还是为Admin Down Event，为Down Event时，执行步骤702，为Admin Down Event时，执行步骤710。
本步骤701是在基本信息表项1中的会话状态为UP时执行的。
在本实施例中，对于上述步骤704匹配出的事件类型为除Down Event、Admin Down Event之外的其他事件类型比如UP Event，则将上述的Firmware事件上报给BFD驱动模块，由BFD驱动模块依据Firmware事件携带的事件类型标识进行相应的处理，这里不再赘述。
步骤702，更新基本信息表项1中的会话状态为Down。之后执行步骤703。
步骤703，依据基本信息表项1中的等价类集合标识找到对应的等价时间窗口队列(记为队列1)。
基于上面描述的等价类时间窗口队列的结构，则步骤703具体为：以基本信息表项1中的等价类集合标识为关键字在二维链表(等价类时间窗口队列表对应的二维链表)中找到表头包含该关键字的二维链表项，该找到的二维链表项记为上述的队列1。
步骤704，判断队列1是否为空，如果是，执行步骤705，如果否，执行步骤706。
这里的判断队列1是否为空实质是：判断队列1中是否不存在队列元素，如果队列1不存在队列元素，则确定队列1为空，否则，确定队列1不为空。
步骤705，将Sid1对应的队列元素作为队列1的第一个队列元素添加至队列1中，添加的队列元素的时间戳为当前系统时间。之后执行步骤709。
基于上面描述的等价类时间窗口队列的结构，则步骤705具体为：按照等价类时间窗口队列中队列元素的结构将Sid1构成一个对应的队列元素，并添加至队列1中(也即上述步骤703找到的二维链表项中)。此时该添加的队列元素是该队列1中的第一个队列元素。
步骤706，计算当前系统时间与队列1中第一个队列元素的时间戳之差，比较计算结果与本地特征表中设定时间窗口大小，如果前者大于后者，则执行步骤707，如果前者小于或等于后者，则执行步骤708。
步骤707，删除队列1中的第一个队列元素，将Sid1对应的队列元素添加至队列1中最后一个队列元素的后面，添加的队列元素的时间戳为当前系统时间。结束当前流程。
在本实施例中，当删除队列1中的第一个队列元素后，队列1中的其他队列元素则依次向被删除的第一个队列元素所在的位置移动，最终，队列1中原有的第二个队列元素作为第一个队列元素，依次类推。步骤708，将Sid1对应的队列元素添加至队列1中最后一个队列元素的后面，添加的队列元素的时间戳为当前系统时间。之后执行步骤709。
步骤709，判断队列1中的队列元素的数量是否达到特征表中的设定阈值，如果是，针对基本信息表项1中等价类集合标识对应的等价类集合中每一BFD会话上报Down事件，并清空队列1中所有队列元素和清空基本信息表项1中等价类集合标识对应的等价类集合中所有等价类集合元素。
当针对基本信息表项1中等价类集合标识对应的等价类集合中每一BFD会话上报Down事件后，队列1中所有队列元素和基本信息表项1中等价类集合标识对应的等价类集合中所有等价类集合元素就没有意义了，所以为节省存储资源，作为一个实施例，本步骤709清空队列1中所有队列元素和清空基本信息表项1中等价类集合标识对应的等价类集合中所有等价类集合元素。
作为一个实施例，当步骤709的判断结果为否时，则可将上述的Firmware事件上报给BFD驱动模块，由BFD驱动模块依据Firmware事件携带的事件类型标识进行相应的处理，这里不再赘述。
这里的针对等价类集合中每一BFD会话上报Down事件，也意味着将等价类集合中每一BFD会话Down事件上报给BFD驱动模块，由BFD驱动模块依据Down事件进行处理，这里不再赘述。
步骤710，更新基本信息表项1中的会话状态为Down，并可将上述监听到的Firmware事件上报给BFD驱动模块。结束当前流程。
BFD驱动模块接收到Firmware事件后，依据Firmware事件进行处理，这里不再赘述。
至此，完成图7所示的流程。
基于上述流程，则应用于以下场景：同一公网路径上承载有64个BFD会话，BFD会话的检测周期为10ms，检测周期内需要发送3次检测报文，则采用现有方案，经验证，Down事件上报时延超过128ms，远超过电信要求丢包时延50ms以内，而采用本公开提供的方法后，经验证，Down事件上报时延在30ms以内，大大缩短了Down事件上报时延。
以上对本公开提供的方法进行了描述。
下面对本公开提供的装置进行描述：
参见图8，图8为本公开提供的装置结构图。如图8所示，该装置包括：
接收单元801，用于接收BFD会话事件，所述BFD会话事件携带BFD会话标识、事件类型标识；
获取单元802，用于从所述BFD会话标识匹配的基本信息表项中获取等价类集合标识，所述等价类集合标识表示所述BFD会话标识对应的BFD会话所属的等价类集合，其中，同一公网路径承载的BFD会话同属一个等价类集合；
控制单元803，用于当所述事件类型标识表示Down事件时，将所述BFD会话标识对应的队列元素添加至所述等价类集合标识对应的等价类时间窗口队列，判断所述等价类时间窗口队列中的队列元素的数量是否在设定时间窗口内达到设定阈值，如果是，针对所述等价类集合标识对应的等价类集合中每一BFD会话上报Down事件。
在一个示例中，所述控制单元803进一步从所述等价类集合标识对应的等价类集合中删除所述BFD会话标识对应的等价类集合元素。
在一个示例中，所述控制单元803将所述BFD会话标识对应的队列元素添加至所述等价类集合标识对应的等价类时间窗口队列包括：
判断所述等价类时间窗口队列是否为空，
如果是，将所述BFD会话标识对应的队列元素作为所述等价类时间窗口队列的第一个队列元素添加至所述等价类时间窗口队列中，添加的队列元素的时间戳为当前系统时间；
如果否，将所述BFD会话标识对应的队列元素添加至所述等价类时间窗口队列中最后一个队列元素的后面，添加的队列元素的时间戳为当前系统时间。
在一个示例中，所述控制单元803将所述BFD会话标识对应的队列元素添加至所述等价类时间窗口队列中最后一个队列元素的后面，包括：
计算当前系统时间与所述等价类时间窗口队列中第一个队列元素的时间戳之差，在所述计算的差大于设定时间窗口大小时，删除所述等价类时间窗口队列中第一个队列元素，并将所述BFD会话标识对应的队列元素添加至所述等价类时间窗口队列中最后一个队列元素的后面。
在一个示例中，所述控制单元803针对等价类集合中每一BFD会话上报Down事件进一步包括：
清空所述等价类集合中的等价类集合元素；
清空所述等价类时间窗口队列中的队列元素。
在一个示例中，所述控制单元803进一步在所述事件类型标识表示启动UP事件时，若所述BFD会话标识匹配的基本信息表项中的会话状态为Down，则将所述BFD会话标识对应的等价类集合元素添加至所述等价类结合标识对应的等价类集合中；以及，
在所述事件类型标识表示管理(Admin)Down事件时，若所述BFD会话标识匹配的基本信息表项中的会话状态为UP，则从所述等价类集合标识对应的等价类集合中删除所述BFD会话标识对应的等价类集合元素，并将所述BFD会话事件上报。至此，完成图8所示装置的结构描述。
其中，装置中各单元执行过程可以参照方法部分的实施例，在此不再赘述。
对应地，本公开还提供了图8所示装置的一种实施方式。参见图9，图9为本公开提供的图8所示装置的硬件结构示意图。该装置包含：处理器901、存储有机器可执行指令的机器可读存储介质902。处理器901与机器可读存储介质902可经由系统总线903通信。并且，通过读取并执行机器可读存储介质902中的机器可执行指令，处理器901可执行上文描述的方法。如图9所示，该硬件结构还可以包括一个电源组件904被配置为执行该交换设备的电源管理，一个有线或无线网络接口905被配置为将该装置连接到网络，和一个输入输出(I/O)接口906。
本文中提到的机器可读存储介质902可以是任何电子、磁性、光学或其它物理存储装置，可以包含或存储信息，如可执行指令、数据，等等。例如，机器可读存储介质可以是：RAM(Radom Access Memory，随机存取存储器)、易失存储器、非易失性存储器、闪存、存储驱动器(如硬盘驱动器)、固态硬盘、任何类型的存储盘(如光盘、dvd等)，或者类似的存储介质，或者它们的组合。
所述机器可读存储介质902，用于存放接收单元801运行的程序指令、获取单元802运行的程序指令、控制单元803运行的程序指令；
处理器901，用于执行接收单元801运行的程序指令、用于执行获取单元802运行的程序指令、用于执行控制单元803运行的程序指令。其中，处理器901通过执行如上各个单元所运行的程序指令，来实现如上所述的方法。
至此，完成图9所示的硬件结构描述。
根据本公开的示例，提供一种处理装置，包括：
处理器；以及
存储有机器可执行指令的机器可读存储介质，其中，通过执行所述机器可读存储介质中的机器可执行指令，所述处理器被使得：
接收双向转发检测(BFD)会话事件，所述BFD会话事件携带BFD会话标识、事件类型标识；
从所述BFD会话标识匹配的基本信息表项中获取等价类集合标识，所述等价类集合标识表示所述BFD会话标识对应的BFD会话所属的等价类集合，其中，同一公网路径承载的BFD会话同属一个等价类集合；
当所述事件类型标识表示Down事件时，
将所述BFD会话标识对应的队列元素添加至所述等价类集合的标识对应的等价类时间窗口队列，
判断所述等价类时间窗口队列中的队列元素的数量是否在设定时间窗口内达到设定阈值，如果是，针对所述等价类集合标识对应的等价类集合中每一BFD会话上报Down事件。
在所述等价类时间窗口队列中的队列元素的数量在设定时间窗口内达到设定阈值时，所述处理器还被使得：
从所述等价类集合标识对应的等价类集合中删除所述BFD会话标识对应的等价类集合元素。
在将所述BFD会话标识对应的队列元素添加至所述等价类集合标识对应的等价类时间窗口队列时，所述处理器还被使得：
判断所述等价类时间窗口队列是否为空，
如果是，将所述BFD会话标识对应的队列元素作为所述等价类时间窗口队列的第一个队列元素添加至所述等价类时间窗口队列中，添加的队列元素的时间戳为当前系统时间；
如果否，将所述BFD会话标识对应的队列元素添加至所述等价类时间窗口队列中最后一个队列元素的后面，添加的队列元素的时间戳为当前系统时间。
其中，在将所述BFD会话标识对应的队列元素添加至所述等价类时间窗口队列中最后一个队列元素的后面时，所述处理器还被使得：
计算当前系统时间与所述等价类时间窗口队列中第一个队列元素的时间戳之差，
在所述计算的差大于设定时间窗口大小时，删除所述等价类时间窗口队列中第一个队列元素，并
所述BFD会话标识对应的队列元素添加至所述等价类时间窗口队列中最后一个队列元素的后面。
在针对所述等价类集合标识对应的等价类集合中每一BFD会话上报Down事件后，所述处理器还被使得：
清空所述等价类集合中的等价类集合元素；
清空所述等价类时间窗口队列中的队列元素。
所述处理器还被使得：
当所述事件类型标识表示启动(UP)事件时，
若所述BFD会话标识匹配的基本信息表项中的会话状态为Down，则将所述BFD会话标识对应的等价类集合元素添加至所述等价类集合标识对应的等价类集合中；
当所述事件类型标识表示管理(Admin)Down事件时，
若所述BFD会话标识匹配的基本信息表项中的会话状态为UP，则从所述等价类集合标识对应的等价类集合中删除所述BFD会话标识对应的等价类集合元素，并将所述BFD会话事件上报。
对于装置实施例而言，由于其基本对应于方法实施例，所以相关之处参见方法实施例的部分说明即可。以上所描述的装置实施例仅仅是示意性的，其中所述作为分离部件说明的单元可以是或者也可以不是物理上分开的，作为单元显示的部件可以是或者也可以不是物理单元，即可以位于一个地方，或者也可以分布到多个网络单元上。可以根据实际的需要选择其中的部分或者全部模块来实现本实施例方案的目的。本领域普通技术人员在不付出创造性劳动的情况下，即可以理解并实施。
需要说明的是，在本文中，诸如第一和第二等之类的关系术语仅仅用来将一个实体或者操作与另一个实体或操作区分开来，而不一定要求或者暗示这些实体或操作之间存在任何这种实际的关系或者顺序。术语“包括”、“包含”或者其任何其他变体意在涵盖非排他性的包含，从而使得包括一系列要素的过程、方法、物品或者设备不仅包括那些要素，而且还包括没有明确列出的其他要素，或者是还包括为这种过程、方法、物品或者设备所固有的要素。 在没有更多限制的情况下，由语句“包括一个……”限定的要素，并不排除在包括所述要素的过程、方法、物品或者设备中还存在另外的相同要素。
以上对本公开实施例所提供的方法和装置进行了详细介绍，本文中应用了具体个例对本公开的原理及实施方式进行了阐述，以上实施例的说明只是用于帮助理解本公开的方法及其核心思想；同时，对于本领域的一般技术人员，依据本公开的思想，在具体实施方式及应用范围上均会有改变之处，综上所述，本说明书内容不应理解为对本公开的限制。

Claims (12)

  1. 一种防止故障处理延迟的方法，包括：
    处理器接收双向转发检测(BFD)会话事件，所述BFD会话事件携带BFD会话标识、事件类型标识；
    所述处理器从所述BFD会话标识匹配的基本信息表项中获取等价类集合标识，所述等价类集合标识表示所述BFD会话标识对应的BFD会话所属的等价类集合，其中，同一公网路径承载的BFD会话同属一个等价类集合；
    当所述事件类型标识表示Down事件时，
    所述处理器将所述BFD会话标识对应的队列元素添加至所述等价类集合标识对应的等价类时间窗口队列，
    所述处理器判断所述等价类时间窗口队列中的队列元素的数量是否在设定时间窗口内达到设定阈值，如果是，针对所述等价类集合标识对应的等价类集合中每一BFD会话上报Down事件。
  2. 根据权利要求1所述的方法，当所述等价类时间窗口队列中的队列元素的数量在设定时间窗口内达到设定阈值时，该方法进一步包括：
    所述处理器从所述等价类集合标识对应的等价类集合中删除所述BFD会话标识对应的等价类集合元素。
  3. 根据权利要求1所述的方法，其中，将所述BFD会话标识对应的队列元素添加至所述等价类集合标识对应的等价类时间窗口队列包括：
    所述处理器判断所述等价类时间窗口队列是否为空，
    如果所述等价类时间窗口队列为空，所述处理器将所述BFD会话标识对应的队列元素作为所述等价类时间窗口队列的第一个队列元素添加至所述等价类时间窗口队列中，添加的队列元素的时间戳为当前系统时间；
    如果所述等价类时间窗口队列不为空，所述处理器将所述BFD会话标识对应的队列元素添加至所述等价类时间窗口队列中最后一个队列元素的后面，添加的队列元素的时间戳为当前系统时间。
  4. 根据权利要求3所述的方法，其中，将所述BFD会话标识对应的队列元素添加至所述等价类时间窗口队列中最后一个队列元素的后面，包括：
    所述处理器计算当前系统时间与所述等价类时间窗口队列中第一个队列元素的时间戳之差，
    在所述计算的差大于设定时间窗口大小时，所述处理器删除所述等价类时间窗口队列中第一个队列元素，并
    所述处理器将所述BFD会话标识对应的队列元素添加至所述等价类时间窗口队列中最后一个队列元素的后面。
  5. 根据权利要求1所述的方法，其中，所述方法进一步包括：针对所述等价类集合标识对应的等价类集合中每一BFD会话上报Down事件后，
    所述处理器清空所述等价类集合中的等价类集合元素；
    所述处理器清空所述等价类时间窗口队列中的队列元素。
  6. 根据权利要求1所述的方法，还包括：
    当所述事件类型标识表示启动(UP)事件时，
    若所述BFD会话标识匹配的基本信息表项中的会话状态为Down，则所述处理器将所述BFD会话标识对应的等价类集合元素添加至所述等价类集合标识对应的等价类集合中；
    当所述事件类型标识表示管理(Admin)Down事件时，
    若所述BFD会话标识匹配的基本信息表项中的会话状态为UP，则所述处理器从所述等价类集合标识对应的等价类集合中删除所述BFD会话标识对应的等价类集合元素，并
    所述处理器将所述BFD会话事件上报。
  7. 一种处理装置，包括：
    处理器；以及
    存储有机器可执行指令的机器可读存储介质，其中，通过执行所述机器可读存储介质中的机器可执行指令，所述处理器被使得：
    接收双向转发检测(BFD)会话事件，所述BFD会话事件携带BFD会话标识、事件类型标识；
    从所述BFD会话标识匹配的基本信息表项中获取等价类集合标识，所述等价类集合标识表示所述BFD会话标识对应的BFD会话所属的等价类集合，其中，同一公网路径承载的BFD会话同属一个等价类集合；
    当所述事件类型标识表示Down事件时，
    将所述BFD会话标识对应的队列元素添加至所述等价类集合标识对应的等价类时间窗口队列，
    判断所述等价类时间窗口队列中的队列元素的数量是否在设定时间窗口内达到设定阈值，如果是，针对所述等价类集合标识对应的等价类集合中中每一BFD会话上报Down事 件。
  8. 根据权利要求7所述的装置，在所述等价类时间窗口队列中的队列元素的数量在设定时间窗口内达到设定阈值时，所述处理器还被使得：
    从所述等价类集合标识对应的等价类集合中删除所述BFD会话标识对应的等价类集合元素。
  9. 根据权利要求7所述的装置，其中，在将所述BFD会话标识对应的队列元素添加至所述等价类集合标识对应的等价类时间窗口队列时，所述处理器还被使得：
    判断所述等价类时间窗口队列是否为空，
    如果所述等价类时间窗口队列为空，将所述BFD会话标识对应的队列元素作为所述等价类时间窗口队列的第一个队列元素添加至所述等价类时间窗口队列中，添加的队列元素的时间戳为当前系统时间；
    如果所述等价类时间窗口队列不为空，将所述BFD会话标识对应的队列元素添加至所述等价类时间窗口队列中最后一个队列元素的后面，添加的队列元素的时间戳为当前系统时间。
  10. 根据权利要求9所述的装置，其中，在将所述BFD会话标识对应的队列元素添加至所述等价类时间窗口队列中最后一个队列元素的后面时，所述处理器被使得：
    计算当前系统时间与所述等价类时间窗口队列中第一个队列元素的时间戳之差，
    在所述计算的差大于设定时间窗口大小时，删除所述等价类时间窗口队列中第一个队列元素，并
    将所述BFD会话标识对应的队列元素添加至所述等价类时间窗口队列中最后一个队列元素的后面。
  11. 根据权利要求7所述的装置，所述处理器还被使得：在针对所述等价类集合标识对应的等价类集合中每一BFD会话上报Down事件后，
    清空所述等价类集合中的等价类集合元素；
    清空所述等价类时间窗口队列中的队列元素。
  12. 根据权利要求7所述的装置，所述处理器还被使得：
    当所述事件类型标识表示启动(UP)事件时，
    若所述BFD会话标识匹配的基本信息表项中的会话状态为Down，则将所述BFD会话标识对应的等价类集合元素添加至所述等价类集合标识对应的等价类集合中；
    当所述事件类型标识表示管理(Admin)Down事件时，
    若所述BFD会话标识匹配的基本信息表项中的会话状态为UP，则从所述等价类集 合标识对应的等价类集合中删除所述BFD会话标识对应的等价类集合元素，并将所述BFD会话事件上报。
PCT/CN2017/102222 2016-09-19 2017-09-19 防止故障处理延迟 WO2018050122A1 (zh)

Priority Applications (3)

Application Number Priority Date Filing Date Title
US16/334,318 US11206176B2 (en) 2016-09-19 2017-09-19 Preventing failure processing delay
JP2019515274A JP6727424B2 (ja) 2016-09-19 2017-09-19 障害処理遅延防止
EP17850323.1A EP3499801B1 (en) 2016-09-19 2017-09-19 Preventing failure processing delay

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201610830946.XA CN107846292B (zh) 2016-09-19 2016-09-19 防止故障处理延迟的方法和装置
CN201610830946.X 2016-09-19

Publications (1)

Publication Number Publication Date
WO2018050122A1 true WO2018050122A1 (zh) 2018-03-22

Family

ID=61619324

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2017/102222 WO2018050122A1 (zh) 2016-09-19 2017-09-19 防止故障处理延迟

Country Status (5)

Country Link
US (1) US11206176B2 (zh)
EP (1) EP3499801B1 (zh)
JP (1) JP6727424B2 (zh)
CN (1) CN107846292B (zh)
WO (1) WO2018050122A1 (zh)

Families Citing this family (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN111294358B (zh) * 2020-02-21 2021-08-31 苏州盛科通信股份有限公司 报文的处理方法及装置

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101247270A (zh) * 2008-03-19 2008-08-20 中兴通讯股份有限公司 一种实现双向转发检测的系统及方法
CN101848223A (zh) * 2010-05-25 2010-09-29 中兴通讯股份有限公司 基于网络处理器实现快速报文双向转发检测的方法和装置
CN102347855A (zh) * 2011-07-21 2012-02-08 福建星网锐捷网络有限公司 双向转发检测实现方法、装置及网络设备
CN104821957A (zh) * 2015-04-16 2015-08-05 瑞斯康达科技发展股份有限公司 一种bfd状态机的实现方法、装置及系统

Family Cites Families (35)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US4999613A (en) 1987-04-21 1991-03-12 Guardian Technologies, Inc. Remote confinement system
US6373846B1 (en) * 1996-03-07 2002-04-16 Lsi Logic Corporation Single chip networking device with enhanced memory access co-processor
US6535512B1 (en) * 1996-03-07 2003-03-18 Lsi Logic Corporation ATM communication system interconnect/termination unit
JP2002033767A (ja) 2000-07-18 2002-01-31 Fujitsu Ltd ネットワーク管理システム
JP4398113B2 (ja) 2001-05-23 2010-01-13 富士通株式会社 レイヤ型ネットワークの管理システム
US8289839B2 (en) 2007-07-05 2012-10-16 Cisco Technology, Inc. Scaling BFD sessions for neighbors using physical / sub-interface relationships
US7961601B2 (en) * 2007-08-16 2011-06-14 Ericsson Ab Lesser disruptive open shortest path first handling of bidirectional forwarding detection state changes
CN101132320B (zh) * 2007-09-18 2010-06-16 华为技术有限公司 检测接口故障的方法及网络节点设备
CN101459594B (zh) * 2007-12-14 2011-04-13 华为技术有限公司 Bfd报文的发送方法、链路故障的探测方法及装置
US7921219B2 (en) * 2008-08-19 2011-04-05 Cisco Technology, Inc. Maintaining protocol adjacency state with forwarding failure
CN101447900A (zh) 2008-12-15 2009-06-03 华为技术有限公司 一种建立双向转发检测的方法、系统及设备
US8886762B2 (en) * 2009-09-17 2014-11-11 Adobe Systems Incorporated Stream duration management
EP2572473B1 (en) * 2010-05-19 2014-02-26 Telefonaktiebolaget L M Ericsson (PUBL) Methods and apparatus for use in an openflow network
US8885484B2 (en) 2011-07-25 2014-11-11 Alcatel Lucent Bootstrapping fault detection sessions over a P2MP tunnel
US8832417B2 (en) * 2011-09-07 2014-09-09 Qualcomm Incorporated Program flow control for multiple divergent SIMD threads using a minimum resume counter
CN102571601B (zh) * 2012-02-13 2018-05-15 中兴通讯股份有限公司 一种保证双向转发检测可靠性的方法及标记交换路径设备
CN102801614B (zh) * 2012-07-17 2016-04-27 杭州华三通信技术有限公司 一种等价路由的收敛方法和网络设备
US8953460B1 (en) * 2012-12-31 2015-02-10 Juniper Networks, Inc. Network liveliness detection using session-external communications
GB201302984D0 (en) * 2013-02-20 2013-04-03 Nominet Uk A method of, and apparatus for, monitoring traffic in a communications network
US10097372B2 (en) * 2014-01-09 2018-10-09 Ciena Corporation Method for resource optimized network virtualization overlay transport in virtualized data center environments
CN105099805B (zh) 2014-05-16 2019-05-07 新华三技术有限公司 一种双向转发检测方法及系统
US9509599B2 (en) * 2014-08-04 2016-11-29 Telefonaktiebolaget L M Ericsson (Publ) Self-bootstrapping BFD session over MPLS LSP
JP2016048850A (ja) 2014-08-27 2016-04-07 富士通株式会社 パケット転送装置、パケット転送システム、及びパケット転送方法
CN105490867A (zh) * 2014-10-09 2016-04-13 中兴通讯股份有限公司 一种双向转发检测的控制方法及装置
CN104506546B (zh) * 2014-12-30 2018-06-15 新华三技术有限公司 一种聚合链路的双向转发检测方法和装置
CN107078924B (zh) * 2014-12-31 2020-02-14 华为技术有限公司 对聚合链路进行双向转发检测的方法、设备和系统
US9774524B2 (en) * 2015-02-17 2017-09-26 Telefonaktiebolaget L M Ericsson (Publ) Method and apparatus for fast reroute, control plane and forwarding plane synchronization
US9674071B2 (en) * 2015-02-20 2017-06-06 Telefonaktiebolaget Lm Ericsson (Publ) High-precision packet train generation
US9680694B1 (en) * 2015-03-05 2017-06-13 Juniper Networks, Inc. Overload functionality in overlay networks using fault detection protocols
US10210058B1 (en) * 2015-03-31 2019-02-19 Juniper Networks, Inc. Application aware inter-chassis redundancy
US9985883B2 (en) * 2016-02-26 2018-05-29 128 Technology, Inc. Name-based routing system and method
US10257061B2 (en) * 2016-05-31 2019-04-09 128 Technology, Inc. Detecting source network address translation in a communication system
US10200264B2 (en) * 2016-05-31 2019-02-05 128 Technology, Inc. Link status monitoring based on packet loss detection
US11032197B2 (en) * 2016-09-15 2021-06-08 Cisco Technology, Inc. Reroute detection in segment routing data plane
CN107846356B (zh) 2016-09-19 2020-02-11 新华三技术有限公司 主备伪线pw快速切换方法和装置

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101247270A (zh) * 2008-03-19 2008-08-20 中兴通讯股份有限公司 一种实现双向转发检测的系统及方法
CN101848223A (zh) * 2010-05-25 2010-09-29 中兴通讯股份有限公司 基于网络处理器实现快速报文双向转发检测的方法和装置
CN102347855A (zh) * 2011-07-21 2012-02-08 福建星网锐捷网络有限公司 双向转发检测实现方法、装置及网络设备
CN104821957A (zh) * 2015-04-16 2015-08-05 瑞斯康达科技发展股份有限公司 一种bfd状态机的实现方法、装置及系统

Non-Patent Citations (1)

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

Also Published As

Publication number Publication date
EP3499801A4 (en) 2019-06-19
JP6727424B2 (ja) 2020-07-22
CN107846292B (zh) 2020-12-04
JP2019530339A (ja) 2019-10-17
US11206176B2 (en) 2021-12-21
EP3499801A1 (en) 2019-06-19
EP3499801B1 (en) 2021-04-28
US20190207808A1 (en) 2019-07-04
CN107846292A (zh) 2018-03-27

Similar Documents

Publication Publication Date Title
US11196654B2 (en) System for aggregating statistics associated with interfaces
US10911335B1 (en) Anomaly detection on groups of flows
US11743135B2 (en) Presenting data regarding grouped flows
US11176157B2 (en) Using keys to aggregate flows at appliance
US11140090B2 (en) Analyzing flow group attributes using configuration tags
US11188570B2 (en) Using keys to aggregate flow attributes at host
US7995483B1 (en) Simultaneously testing connectivity to multiple remote maintenance endpoints of the same maintenance association
US10708184B2 (en) Switching primary/backup pseudowire
WO2018094616A1 (zh) 监测虚拟网络的方法、设备和虚拟网络系统
US8356093B2 (en) Apparatus and system for estimating network configuration
US20150103642A1 (en) Diagnosing connectivity in a network
WO2019057007A1 (zh) 一种通信连接检测方法及装置
CN110730125B (zh) 一种报文转发方法、装置、双活系统及通信设备
WO2018145560A1 (zh) 链路故障诊断方法及装置
WO2012062102A1 (zh) 一种检测组播转发树上两点间连通性的方法、系统和装置
WO2018010616A1 (zh) 基于链路层的网络管理
US8670299B1 (en) Enhanced service status detection and fault isolation within layer two networks
WO2018050122A1 (zh) 防止故障处理延迟
US9043274B1 (en) Updating local database and central database
US9432275B2 (en) Transmission monitoring method and device
US7894459B2 (en) Determining availability of a network service
JP6488600B2 (ja) 情報処理システム、プログラム及び情報処理装置
WO2020135445A1 (zh) 对路由震荡的定位
WO2014040409A1 (zh) 路由管理的方法和节点
JP5600629B2 (ja) 通信網監視装置

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

Country of ref document: EP

Kind code of ref document: A1

ENP Entry into the national phase

Ref document number: 2019515274

Country of ref document: JP

Kind code of ref document: A

NENP Non-entry into the national phase

Ref country code: DE

ENP Entry into the national phase

Ref document number: 2017850323

Country of ref document: EP

Effective date: 20190312