A device may be configured to determine a current state of each of multiple operator network devices that provide a service via an operator network. The device may determine an allowable event at an operator network device based on the current state of the operator network device and model information that models behavior of the operator network device for the service. The device may monitor events at the operator network devices during a session. The device may detect that an allowable event for the operator network device does not occur during the session. The device may determine that a fault occurred at the operator network device during the session based on the allowable event not being detected at the operator network device. The device may provide fault information that indicates the fault occurred at the operator network device.
Legal claims defining the scope of protection. Each claim is shown in both the original legal language and a plain English translation.
1. A device, comprising: one or more processors to: determine a current state of each of a plurality of operator network devices that provide a Quality of Service (QoS) based service via an operator network, the current state being associated with a session between the operator network and a client device, determine at least one allowable event at a particular operator network device, of the plurality of operator network devices, based on a current state of the particular operator network device and based on model information, the model information indicating allowed behavior of the particular operator network device for the QoS based service; monitor events at the plurality of operator network devices during the session; detect, based on monitoring the events, that an allowable event, of the at least one allowable event, does not occur at the particular operator network device before a timeout time expires, the timeout time indicating an amount of time for the allowable event to occur before a fault is triggered, and the timeout time being based on a QoS level of the session; determine that the fault occurred at the particular operator network device during the session based on the allowable event not being detected at the particular operator network device before the timeout time expires; and provide fault information that indicates the fault occurred at the particular operator network device.
A device monitors network devices providing a Quality of Service (QoS) based service. It determines the current state of each network device in a session between the network and a client. Based on this state and a model of allowed behavior for that device, it identifies acceptable events. The device watches for these events. If an expected event doesn't occur within a timeout period specific to the QoS level of the session, the device flags a fault on that network device and provides fault information. The timeout value specifies how long to wait for an expected event before assuming a fault.
2. The device of claim 1 , where the at least one allowable event includes at least one of receiving a first packet or sending a second packet.
The fault detection device, as described previously, considers the receipt of a packet or the sending of a packet as an allowable event that it monitors. Specifically, the device determines faults by monitoring whether a particular network device either receives a packet or sends a packet within the allotted timeout. The failure of either of these events to occur would indicate a fault.
3. The device of claim 1 , where the one or more processors, when monitoring the events, are to: monitor the events in real time.
The fault detection device, as described previously, monitors the network device events in real-time. This means that the device is actively and immediately tracking events occurring on the network devices, rather than processing logs or historical data.
4. The device of claim 1 , where the one or more processors are further to: detect that an unallowable event occurs; and where the one or more processors, when determining that the fault occurred, are further to: determine that the fault occurred based on the unallowable event occurring instead of the allowable event.
The fault detection device, as described previously, also detects "unallowable" events. If an unallowable event occurs instead of an allowable event, the device determines that a fault has occurred. This provides an alternative method for determining faults, where the presence of unexpected behavior indicates a problem.
5. The device of claim 1 , where the one or more processors are further to: cause a corrective action, based on the fault, to be performed, the corrective action causing a problem that caused the fault to be corrected.
The fault detection device, as described previously, automatically initiates a corrective action to resolve the underlying problem causing the fault. The corrective action is designed to fix the issue that triggered the fault detection, automatically attempting to resolve the problem.
6. The device of claim 1 , where the timeout time is separate for different QoS levels.
The fault detection device, as described previously, uses different timeout periods for different QoS levels. This ensures that fault detection is sensitive to the specific requirements of each QoS level, with more stringent timeouts for high-priority services and more relaxed timeouts for lower-priority ones.
7. The device of claim 1 , where the timeout time is one of multiple timeout times associated with the current state.
The fault detection device, as described previously, uses a timeout period selected from a set of multiple timeout periods associated with each possible state of a network device. This allows the timeout to be contextually chosen based on the current operational state of the operator device.
8. A computer-readable medium storing instructions, the instructions comprising: one or more instructions that, when executed by one or more processors, cause the one or more processors to: determine a current state of a client device and one or more operator network devices that provide a Quality of Service (QoS) based service via an operator network, the current state being associated with a session between the operator network and the client device; determine at least one allowable event at a particular operator network device, of the one or more operator network devices based on model information, the model information indicating allowed behavior of the particular operator network device for the QoS based service; monitor events at the one or more operator network devices during the session; detect, based on monitoring the events, that an allowable event, of the at least one allowable event, does not occur at the particular operator network device before a timeout time expires, the timeout time indicating an amount of time for the allowable event to occur before a fault is triggered, and the timeout time being based on a QoS level of the session; determine that the fault occurred at the particular operator network device during the session based on the allowable event not being detected at the particular operator network device before the timeout time expires; and provide fault information that indicates the fault occurred at the particular operator network device.
A computer-readable medium contains instructions that, when executed, cause a processor to monitor network devices providing a Quality of Service (QoS) based service. The instructions cause the processor to determine the current state of each network device and the client device, in a session. Based on the device's state and a model of allowed behavior, the system determines acceptable events. The system watches for these events. If an expected event doesn't occur within a timeout period specific to the QoS level, the system flags a fault and provides fault information.
9. The computer-readable medium of claim 8 , where the at least one allowable event includes at least one of receiving a first packet or sending a second packet.
The computer-readable medium, as described previously, considers the receipt of a packet or the sending of a packet as an allowable event that it monitors. Specifically, the instructions cause the processor to determine faults by monitoring whether a particular network device either receives a packet or sends a packet within the allotted timeout, and the failure of either to occur would indicate a fault.
10. The computer-readable medium of claim 8 , where the one or more instructions, that cause the one or more processors to monitor the events, cause the one or more processors to: monitor the events in near real time.
The computer-readable medium, as described previously, causes the processor to monitor the network device events in near real-time. This means that the system actively and almost immediately tracks events occurring on the network devices, rather than processing logs or historical data.
11. The computer-readable medium of claim 8 , where the one or more instructions, when executed by the one or more processors, are further to: detect that an unallowable event occurs; and where the one or more instructions, that cause the one or more processors to determine that the fault occurred, are further to: determine that the fault occurred based on the unallowable event occurring instead of the allowable event.
The computer-readable medium, as described previously, also detects "unallowable" events. If an unallowable event occurs instead of an allowable event, the instructions cause the processor to determine that a fault has occurred. This provides an alternative method for determining faults, where the presence of unexpected behavior indicates a problem.
12. The computer-readable medium of claim 8 , where the one or more instructions, executed by the one or more processors, further cause the one or more processors to: perform a corrective action based on the fault, the corrective action causing a problem that caused the fault to be corrected.
The computer-readable medium, as described previously, contains instructions that cause the processor to automatically initiate a corrective action to resolve the underlying problem causing the fault. The corrective action is designed to fix the issue that triggered the fault detection, automatically attempting to resolve the problem.
13. The computer-readable medium of claim 8 , where the timeout time is one of multiple timeout times associated with the current state.
The computer-readable medium, as described previously, specifies that the timeout period is one of multiple timeout periods associated with each state of the network device. This allows the specific timeout value to be determined based on the particular state of the network device.
14. A method comprising: determining, by a device, a current state of each of a plurality of operator network devices that provide a service via an operator network, the current state being associated with a session between the operator network and a client device; determining, by the device, at least one allowable event at a particular operator network device, of the plurality of operator network devices, based on a current state of the particular operator network device and based on model information, the model information indicating allowed behavior of the particular operator network device for the service; monitoring, by the device, events at the plurality of operator network devices during the session; detecting, by the device and based on monitoring the events, that an allowable event, of the at least one allowable event, does not occur at the particular operator network device before a timeout time expires, the timeout time indicating an amount of time for the allowable event to occur before a fault is triggered, and the timeout time being based on a Quality of Service (QoS) level of the session; determining, by the device, that the fault occurred at the particular operator network device during the session based on the allowable event not being detected at the particular operator network device before the timeout time expires; and providing, by the device, fault information that indicates the fault occurred at the particular operator network device.
A method involves monitoring network devices providing a service. The method determines the current state of each network device in a session. Based on this state and a model of allowed behavior, it identifies acceptable events. The method watches for these events. If an expected event doesn't occur within a timeout period specific to the QoS level, a fault is flagged on that network device, and fault information is provided.
15. The method of claim 14 , where the at least one allowable event includes at least one of receiving a first packet or sending a second packet.
The fault detection method, as described previously, considers the receipt of a packet or the sending of a packet as an allowable event that it monitors. Specifically, the method determines faults by monitoring whether a particular network device either receives a packet or sends a packet within the allotted timeout. The failure of either of these events to occur would indicate a fault.
16. The method of claim 14 , where monitoring the events comprises: monitoring the events in real time based on a packet tracer.
The fault detection method, as described previously, monitors the network device events in real-time using a packet tracer. This means the method employs a tool that captures and analyzes network packets in real-time to immediately track events occuring on the network devices.
17. The method of claim 14 , further comprising: detecting that an unallowable event occurs; and where determining that the fault occurred further comprises: determining that the fault occurred based on the unallowable event occurring instead of the allowable event.
The fault detection method, as described previously, also detects "unallowable" events. If an unallowable event occurs instead of an allowable event, the method determines that a fault has occurred. This provides an alternative method for determining faults, where the presence of unexpected behavior indicates a problem.
18. The method of claim 14 , further comprising: causing, by the device, a corrective action to be performed based on the fault, the correction action causing a problem that caused the fault to be corrected.
The fault detection method, as described previously, automatically initiates a corrective action to resolve the underlying problem causing the fault. The corrective action is designed to fix the issue that triggered the fault detection, automatically attempting to resolve the problem.
19. The method of claim 14 , where the timeout time is separate for different QoS levels.
The fault detection method, as described previously, uses different timeout periods for different QoS levels. This ensures that fault detection is sensitive to the specific requirements of each QoS level, with more stringent timeouts for high-priority services and more relaxed timeouts for lower-priority ones.
20. The method of claim 14 , where the timeout time is one of multiple timeout times associated with the current state.
The fault detection method, as described previously, uses a timeout period selected from a set of multiple timeout periods associated with each possible state of a network device. This allows the timeout to be contextually chosen based on the current operational state of the operator device.
Cooperative Patent Classification codes for this invention. Click any code to explore related patents in that topic.
September 8, 2014
August 1, 2017
Browse 5M+ US patents with plain-English claim translations and AI-generated analysis.