Network component management system

• US 20040057454A1
• Filed: 08/15/2003
• Published: 03/25/2004
• Est. Priority Date: 08/25/2000
• Status: Abandoned Application

• Current Assignee: Telstra Corporation Limited (Telstra Group Ltd.)
• Original Assignee: Telstra Corporation Limited (Telstra Group Ltd.)
• Inventors: Hennegan, Rodney George, Mogg, John Brian
• Application Number:
  US10/362,680
• Publication Number:
  US 20040057454A1
• Time in Patent Office: Days
• US Class Current: 370/463
• CPC Class Codes: G06F 9/5027 the resource being a machine, e.g. CPUs, Servers, Terminals
• CPC Class Codes: G06F 9/5072 Grid computing
• CPC Class Codes: H04L 41/0803 Configuration setting

Abstract

A management system (2) for a network of components, including an interface (5) for use in selecting at least one operation to be performed on at least one component of the network (10), and creating a request that the operation be executed, an engine (4) for processing the request and executing at least one operation, and a scheduler (6) for scheduling execution of at least one operation by the engine (4), based on resource constraints of the network (10).

Claims

1. A management system for a network of components, including:

an interface for use in selecting at least one operation to be performed on at least one component of said network, and creating a request that said operation be executed;

an engine for processing said request and executing said at least one operation; and

a scheduler for scheduling execution of said at least one operation by said engine, based on resource constraints of said network.

2. A management system as claimed in claim 1, including a data store having a rule defining said operation.

3. A management system as claimed in claim 2, wherein said engine generates an execution instance for said operation using said rule, in response to said request.

4. A management system as claimed in claim 1, wherein said request includes scheduling information for executing said operation and for use by said scheduler.

5. A management system as claimed in claim 1, including interfaces for communicating with said network components.

6. A management system as claimed in claim 5, wherein the network components include network switches.

7. A management system as claimed in claim 6, wherein the network switches are distributed over an area, such as a city, state, region or country.

8. A management system as claimed in claim 1, including a client server system providing said interface and a real-time system providing said engine, said scheduler and interfaces for said components.

9. A management system as claimed in claim 8, including a data store having a rule defining said operation, and accessible by said client server system and said real-time system.

10. (Amended) A management system as claimed in claim 1, wherein said engine includes a manager to control the state of said request and initiate execution of at least one business rule associated with said request to perform said operation, and an interpreter instance to execute said at least one business rule under the control of said scheduler.

11. A management system as claimed in claim 1, including a rule defining said operation and resource requirements for said operation.

12. A management system as claimed in claim 1, wherein said scheduler schedules execution of said requests by instances of said engine when resources for execution of said instances are available.

13. A management system as claimed in claim 1, including a data store having data representing said resource constraints, and wherein said scheduler is adapted to access said data.

25. A management system as claimed in claim 1, wherein said interfaces include a messaging interface for sending and receiving messages to user interfaces.

26. A management system as claimed in claim 25, wherein said user interfaces are HTTP interfaces.

14. A scheduler for scheduling execution of rule requests by a rules engine, based on resources required by each request and an estimated time that each resource is required.

15. (Amended) A scheduler as claimed in claim 14, wherein the estimated times are defined by said requests.

16. (Amended) A scheduler as claimed in claim 14, wherein said scheduler schedules resources associated with said requests on the basis of time parameters for said resources and time windows for execution of said requests.

17. A scheduler as claimed in claim 14, wherein said scheduler determines scheduling conflicts between said requests.

18. A scheduler as claimed in claim 14, wherein said scheduler monitors said requests to determine estimated completion times and reschedule said request.

27. A management system for a network of components, including:

a rules engine as claimed in claim 19;

and

a scheduler as claimed in any one of claims 14 to 18.

19. A rules engine for executing rules interactively to allow the input and output of variables, and allow users to select from a set of defined inputs.

20. A management system for network components, including:

a rules engine for executing a rule to perform an operation on at least one of said components, and adapted to save an execution state of the engine during execution of a rule and send a notification concerning resuming execution of the rule; and

a scheduler for receiving said notification and causing resumption of execution of said rule at said execution state.

21. A management system for a network of components, including:

a rules engine for executing a rule defining an operation to be performed on at least one of said components, said engine being adapted to detect process exceptions, and in response, save the state of execution of said rule; and

an interface for examining and adjusting said execution state and allowing continued execution of said rule.

22. (Amended) A management system as claimed in claim 21, wherein said interface is adapted to set the execution point of said rule, and to examine and modify variables of said rule.

23. A programming language, stored on computer readable storage medium, for defining business rules, including commands for transmitting and receiving data from network nodes.

24. A programming language as claimed in claim 23, including commands for sending and receiving messages between user interfaces and a network component management system.

28. A management system as claimed in claim 27, further including a programming language as claimed in claim 23 or 24.

29. A component management system, including:

a rules engine for interpreting change requests and executing component change modules to submit changes to respective components; and

a scheduler for controlling the timing of execution of said component change modules.

30. A component management system as claimed in claim 29, including an interface for generating said change requests.

31. (Amended) A management system for a network of components, including:

an engine for processing a request for at least one configuration change for said network; and

a scheduler for scheduling execution of said at least one configuration change by said engine, based on constraints of said network.

32. (New) A management system for a network of components, including:

an engine for processing a request for at least one configuration change for said network, and reconfiguring components of said network to effect said at least one configuration change; and

a scheduler for scheduling processing of said request based on constraints of said request.

33. (New) A management system as claimed in claim 32, wherein said request identifies components of said network that need to be reconfigured to effect said at least one configuration change, and said engine is adapted to reconfigure said components.

34. (New) A management system as claimed in claim 33, wherein said scheduling is based on at least one of:

access constraints to said network components, and constraints on the times that certain configuration changes can be made.

35. (New) A management system as claimed in claim 32, wherein said processing includes processing one-or more rules implementing said request.

36. (New) A management system as claimed in claim 35, wherein said rules include one or more rule dependencies.

37. (New) A management system as claimed in claim 36, wherein said scheduler is adapted to schedule the execution order of said rules on the basis of said dependencies.

38. (New) A management system as claimed in claim 35, wherein said rules include concurrency and exclusivity requirements.

39. (New) A management system as claimed in claim 35, including a user interface component for interacting with said rules.

40. (New) A management system as claimed in claim 32, wherein said request identifies a job module of a library of job modules, and data for said job module.

41. (New) A management system as claimed in claim 40, wherein said data for said job module includes configuration data and scheduling data.

42. (New) A management system as claimed in claim 40, wherein said engine is adapted to identify one or more component job modules for respective network. Received Nov. 1, 2002 components on the basis of said job module and said configuration data, and to execute said component job modules to reconfigure said components.

43. (New) A management system as claimed in claim 42, wherein said engine is adapted to generate one or more time estimates for each component job module, and said scheduler is adapted to schedule execution of said component job modules on the basis of said time estimates.

44. (New) A management system as claimed in claim 42, wherein said scheduling takes into account a settling period following reconfiguring of a component, during which no further reconfiguration of said component is allowed.

45. (New) A management system as claimed in claim 42, wherein said engine is adapted to execute one or more component operation modules corresponding to each component job module, representing respective operations to be performed on the corresponding component.

46. (New) A management system as claimed in claim 32, wherein said reconfiguring includes generating and sending respective component configuration data to each of said components.

47. (New) A management system as claimed in claim 32, including a scheduler interface component for allowing a user to interact with said scheduler to schedule a request.

48. (New) A management system as claimed in claim 32, including an interface for use in selecting said at least one configuration change for said network and creating said request.

49. (New) A management system as claimed in claim 32, wherein said scheduling is based on constraints of said request and other requests.

50. (New) A management system as claimed in claim 35, wherein said rules include a hierarchy of rules.

51. (New) A management system as claimed in claim 32, wherein said components include network switches.

52. (New) A management system as claimed in claim 46, wherein said components include heterogeneous network switches, and said component configuration data for each network switch is generated in a command language supported by the network switch.

53. (New) A management system as claimed in claim 32, wherein said network is a telecommunications network, and said elements include exchange switches.

54. (New) A management system as claimed in claim 32, wherein said engine and said scheduler are part of a real-time system, and the management system further includes a client-server system providing a user interface to said real-time system.

55. (New) A management system as claimed in claim 54, wherein said user interface is an HTTP interface.

56. (New) A management system as claimed in claim 54, wherein said real-time system includes a multi-processor computer system for concurrently executing rules to effect said request.