Rules-based network service management with on-demand dependency insertion

• US 9,485,159 B1
• Filed: 12/17/2012
• Issued: 11/01/2016
• Est. Priority Date: 12/17/2012
• Status: Active Grant

• Current Assignee: Juniper Networks Incorporated
• Original Assignee: Juniper Networks Incorporated
• Inventors: Sant'Anna, Paulo, Jin, Jian
• Primary Examiner(s): Miah, Razu A
• Application Number:
  US13/717,578
• Time in Patent Office: 1,415 Days
• Field of Search: 709/219
• US Class Current: 1/1
• CPC Class Codes: H04L 41/0636 based on a decision tree analysis
• CPC Class Codes: H04L 41/069 using logs of notifications; Post-processing of notifications
• CPC Class Codes: H04L 43/08 Monitoring or testing based on specific metrics, e.g. QoS, energy consumption or environmental parameters
• CPC Class Codes: H04L 67/06 specially adapted for file transfer, e.g. file transfer protocol [FTP]
• CPC Class Codes: H04L 67/125 involving control of end-device applications over a network
• CPC Class Codes: H04L 69/329 in the application layer [OSI layer 7]
• CPC Class Codes: H04L 9/40 Network security protocols

Abstract

Techniques are described for managing network services deployed in a network using a rules engine with on-demand dependency insertion. A network service manager may use a rules engine to monitor a network service at network devices in order to detect a device-level event, and determine a service-level impact of the detected event based on network service rules and dependencies. The dependencies define links between the device-level event and actions triggered by the device-level event. According to the techniques, a rules engine is configured to detect a device-level event and, in response, insert only those dependencies associated with the detected device-level event into a working memory. Once the device-level event has been cleared, the dependencies related to the device-level event are removed from the working memory. The working memory, therefore, will include only the dependencies needed to determine service-level impacts of currently detected device-level events.

Claims

1. A method comprising:

monitoring, with a rules engine, a network service at one or more network devices in a network to detect a device-level event;

in response to detecting a first device-level event, inserting a first data set of dependencies associated with the first device-level event into a working memory, wherein the first data set of dependencies inserted in the working memory comprises a first subset of a plurality of dependencies for the network service, and wherein the first data set of dependencies defines links between the first device-level event and actions triggered by the first device-level event;

applying, with the rules engine, a set of network service rules to the first data set of dependencies inserted in the working memory to determine a first service-level impact of the detected first device-level event;

in response to detecting a second device-level event, inserting a second data set of dependencies associated with the second device-level event into the working memory, wherein the second data set of dependencies inserted in the working memory comprises a second subset of the plurality of dependencies for the network service; and

applying, with the rules engine, the set of network service rules to the second data set of dependencies inserted in the working memory to determine a second service-level impact of the second device-level event.

2. The method of claim 1, further comprising, upon detecting the first device-level event, querying a service database to retrieve the first data set of dependencies associated with the first device-level event from the plurality of dependencies for the network service.

3. The method of claim 1, wherein inserting the first data set of dependencies associated with the first device-level event comprises:

inserting one or more first-level dependencies directly linked to the first device-level event into the working memory; and

for each of the first-level dependencies, inserting one or more second-level dependencies directly linked to the first-level dependency into the working memory.

4. The method of claim 1, wherein inserting the first data set of dependencies associated with the first device-level event comprises inserting a dependency tree rooted at the device-level event into the working memory, wherein the dependency tree includes levels of dependencies that define the links to actions triggered by the first device-level event.

5. The method of claim 4, wherein applying the set of network service rules to the first data set of dependencies to determine the first service-level impact of the first device-level event comprises applying the set of network service rules to the dependency tree to determine a path along the dependency tree to a service-level action triggered by the first device-level event.

6. The method of claim 1, further comprising generating a notification of the first service-level impact of the first device-level event to a network service application.

7. The method of claim 1, further comprising, when the first device-level event is cleared, removing the first data set of dependencies associated with the first device-level event from the working memory.

8. The method of claim 1, wherein, when the second data set of dependencies includes one or more dependencies from the first data set of dependencies, inserting the second data set of dependencies comprises inserting a subset of the second data set of dependencies into the working memory, wherein the subset includes dependencies for the second device-level event that are not in the first data set of dependencies.

9. The method of claim 1, further comprising, when the first device-level event is cleared, removing one or more dependencies of the first data set of dependencies from the working memory, wherein the removed dependencies are not linked to any other detected device-level events.

10. The method of claim 1, further comprising, when the first device-level event and second device-level event are cleared:

removing one or more dependencies of the first data set of dependencies and the second data set of dependencies from the working memory; and

maintaining at least one dependency of the first data set of dependencies and the second data set of dependencies in the working memory.

11. The method of claim 10, further comprising removing the at least one maintained dependency of the first data set of dependencies and the second data set of dependencies according to one of a time-out mechanism or a first-in, first-out (FIFO) mechanism.

12. The method of claim 1, wherein the first device-level event comprises a connectivity failure between a first network device and a second network device, and wherein the first service-level impact of the first device-level event comprises a failure of the network service in the network.

13. The method of claim 1, further comprising:

upon installation of a network service application in a network service manager, installing the set of network service rules into a rules database of the rules engine; and

provisioning, with the network service application, the network service across the one or more network devices in the network.

14. The method of claim 1, wherein the network service comprises one of a point-to-point service, a point-to-multipoint service, or a mesh service across the one or more network devices.

15. The method of claim 1, wherein the network service comprises one of a virtual private network (VPN) or a virtual local area network (VLAN) across the one or more network devices.

16. A network service manager device for a network comprising:

a working memory; and

a processor configured to execute a rules engine to monitor a network service at one or more network devices in the network to detect a device-level event,

wherein the processor is configured to, in response to detecting a first device-level event, insert a first data set of dependencies associated with the first device-level event into the working memory, wherein the first data set of dependencies inserted in the working memory comprises a first subset of a plurality of dependencies for the network service, and wherein the first data set of dependencies defines links between the first device-level event and actions triggered by the first device-level event,

wherein the processor is configured to apply a set of network service rules to the first data set of dependencies inserted in the working memory to determine a first service-level impact of the detected first device-level event,

wherein the processor is configured to, in response to detecting a second device-level event, insert a second data set of dependencies associated with the second device-level event into the working memory, wherein the second data set of dependencies inserted in the working memory comprises a second subset of the plurality of dependencies for the network service, and

wherein the processor is configured to apply the set of network service rules to the second data set of dependences inserted in the working memory to determine a second service-level impact of the second device-level event.

17. The device of claim 16, wherein the processor is configured to execute the rules engine within a virtual instance.

18. The device of claim 16, further comprising a service database that stores the plurality of dependencies for the network service, wherein, upon detecting the first device-level event, the rules engine queries the service database to retrieve the first data set of dependencies associated with the first device-level event from the plurality of dependencies for the network service.

19. The device of claim 16, wherein the rules engine inserts one or more first-level dependencies directly linked to the first device-level event into the working memory, and, for each of the first-level dependencies, inserts one or more second-level dependencies directly linked to the first-level dependency into the working memory.

20. The device of claim 16, wherein the rules engine inserts a dependency tree rooted at the first device-level event into the working memory, wherein the dependency tree includes levels of dependencies that define the links to actions triggered by the first device-level event.

21. The device of claim 20, wherein the rules engine applies the set of network service rules to the dependency tree to determine a path along the dependency tree to a service-level action triggered by the first device-level event.

22. The device of claim 16, wherein the rules engine generates a notification of the first service-level impact of the first device-level event to a network service application.

23. The device of claim 16, wherein, when the first device-level event is cleared, the rules engine removes the first data set of dependencies for the first device-level event from the working memory.

24. The device of claim 16, wherein, when the second data set of dependencies includes one or more dependencies from the first data set of dependencies, the rules engine inserts a subset of the second data set of dependencies into the working memory, wherein the subset includes dependencies for the second device-level event that are not in the first data set of dependencies.

25. The device of claim 16, wherein, when the first device-level event is cleared, the rules engine removes one or more dependencies of the first data set of dependencies from the working memory, wherein the removed dependencies are not linked to any other detected device-level events.

26. The device of claim 16, wherein, when the first device-level event and second device-level event are cleared, the rules engine removes one or more dependencies of the first data set of dependencies and the second data set of dependencies from the working memory, and maintains at least one dependency of the first data set of dependencies and the second data set of dependencies in the working memory.

27. The device of claim 26, wherein the rules engine removes the at least one maintained dependency of the first data set of dependencies and the second data set of dependencies according to one of a time-out mechanism or a first-in, first-out (FIFO) mechanism.

28. The device of claim 16, wherein the first device-level event comprises a connectivity failure between a first network device and a second network device, and wherein the first service-level impact of the first device-level event comprises a failure of the network service in the network.

29. The device of claim 16, further comprising a rules database that stores the set of network service rules, wherein the processor is configured to execute a network service application to install the set of network service rules in the rules database, and provision the network service across the one or more network devices in the network.

30. The device of claim 16, wherein the network service comprises one of a point-to-point service, a point-to-multipoint service, or a mesh service across the one or more network devices.

31. The device of claim 16, wherein the network service comprises one of a virtual private network (VPN) or a virtual local area network (VLAN) across the one or more network devices.

32. A non-transitory computer-readable medium comprising instructions that when executed cause a processor of a network service manager device to:

monitor a network service at one or more network devices in a network to detect a device-level event;

in response to detecting a first device-level event, insert a first data set of dependencies for the first device-level event into a working memory, wherein the first data set of dependencies inserted in the working memory comprises a first subset of a plurality of dependencies for the network service, and wherein the first data set of dependencies defines links between the first device-level event and actions triggered by the first device-level event;

apply a set of network service rules to the first data set of dependencies inserted in the working memory to determine a first service-level impact of the detected first device-level event;

in response to detecting a second device-level event, insert a second data set of dependencies for the second device-level event into the working memory, wherein the second data set of dependencies inserted in the working memory comprises a second subset of the plurality of dependencies for the network service; and

apply the set of network service rules to the second data set of dependencies inserted in the working memory to determine a second service-level impact of the second device-level event.