Multi-tiered control architecture for adaptive optical networks, and methods and apparatus therefor

• US 7,013,084 B2
• Filed: 02/28/2001
• Issued: 03/14/2006
• Est. Priority Date: 02/28/2001
• Status: Expired due to Fees

• Current Assignee: Lambda Optical Systems Corporation
• Original Assignee: Lambda Optical Systems Corporation
• Inventors: Brooks, David M., Chen, Chin J., Mandelberg, I. Michael, Tzathas, Anastasios, Walters, David H., Alvarez, Mario F., Kim, Moon W., Battou, Abdella
• Primary Examiner(s): Sedighian, M. R.
• Application Number:
  US09/795,252
• Publication Number:
  US 20030163555A1
• Time in Patent Office: 1,840 Days
• Field of Search: 398/12, 398/19, 398/45, 398/50, 398/51, 398/54, 398/55, 398/56, 370/254, 370/422, 370/396, 370/398
• US Class Current: 398/45
• CPC Class Codes: G06F 8/65 Updates security arrangements therefor G06F21/57
• CPC Class Codes: H04J 14/0227 Operation, administration, maintenance or provisioning [OAMP] of WDM networks, e.g. media access, routing or wavelength allocation
• CPC Class Codes: H04J 14/0238 Wavelength allocation for communications one-to-many, e.g. multicasting wavelengths
• CPC Class Codes: H04J 14/0241 Wavelength allocation for communications one-to-one, e.g. unicasting wavelengths
• CPC Class Codes: H04J 14/0284 WDM mesh architectures
• CPC Class Codes: H04J 14/0286 WDM hierarchical architectures
• CPC Class Codes: H04J 14/029 Dedicated protection at the optical multiplex section (1+1)
• CPC Class Codes: H04J 14/0291 Shared protection at the optical multiplex section (1:1, n:m)
• CPC Class Codes: H04J 14/0294 Dedicated protection at the optical channel (1+1)
• CPC Class Codes: H04J 14/0295 Shared protection at the optical channel (1:1, n:m)
• CPC Class Codes: H04J 14/0297 Optical equipment protection
• CPC Class Codes: H04L 41/044 comprising hierarchical management structures
• CPC Class Codes: H04L 41/046 comprising network management agents or mobile agents therefor
• CPC Class Codes: H04L 41/0631 using root cause analysis; using analysis of correlation between notifications, alarms or events based on decision criteria, e.g. hierarchy, tree or time analysis
• CPC Class Codes: H04L 41/0659 by isolating or reconfiguring faulty entities
• CPC Class Codes: H04L 41/0681 Configuration of triggering conditions
• CPC Class Codes: H04L 41/0806 for initial configuration or provisioning, e.g. plug-and-play
• CPC Class Codes: H04L 41/0843 based on generic templates
• CPC Class Codes: H04L 41/0856 by backing up or archiving configuration information
• CPC Class Codes: H04L 41/0893 Assignment of logical groups to network elements
• CPC Class Codes: H04L 41/22 : comprising specially adapted graphical user interfaces [GUI]
• CPC Class Codes: H04L 43/00 : Arrangements for monitoring or testing data switching networks
• CPC Class Codes: H04L 43/022 : by sampling
• CPC Class Codes: H04L 43/0811 : by checking connectivity
• CPC Class Codes: H04L 43/0817 : by checking functioning
• CPC Class Codes: H04L 43/0847 : Transmission error
• CPC Class Codes: H04L 43/10 : Active monitoring, e.g. heartbeat, ping or trace-route
• CPC Class Codes: H04L 43/106 : using time related information in packets, e.g. by adding timestamps
• CPC Class Codes: H04L 43/16 : Threshold monitoring
• CPC Class Codes: H04L 67/34 : involving the movement of software or configuration parameters network booting or remote initial program loading [RIPL] G06F9/4416
• CPC Class Codes: H04L 69/329 : in the application layer [OSI layer 7]
• CPC Class Codes: H04L 9/40 : Network security protocols
• CPC Class Codes: H04Q 11/0005 : Switch and router aspects
• CPC Class Codes: H04Q 11/0062 : Network aspects
• CPC Class Codes: H04Q 11/0066 : Provisions for optical burst or packet networks
• CPC Class Codes: H04Q 11/0071 : Provisions for the electrical-optical layer interface
• CPC Class Codes: H04Q 2011/0015 : using splitting combining
• CPC Class Codes: H04Q 2011/0016 : using wavelength multiplexing or demultiplexing
• CPC Class Codes: H04Q 2011/0024 : using space switching
• CPC Class Codes: H04Q 2011/003 : using switches based on microelectro-mechanical systems [MEMS]
• CPC Class Codes: H04Q 2011/0039 : Electrical control
• CPC Class Codes: H04Q 2011/0081 : Fault tolerance; Redundancy; Recovery; Reconfigurability
• CPC Class Codes: H04Q 2011/0083 : Testing; Monitoring

Abstract

A hierarchical and distributed control architecture for managing an optical communications network. The architecture includes a line card manager level for managing individual line cards in an optical switch, a node manager level for managing multiple line cards in an optical switch/node, and a network management system level for managing multiple optical switches/nodes in a network. An event manager at the node manager level enables software components that are running at the node manager to register for and receive events, and to post events. The events may be triggered, e.g., by a change in a status of the switch, or an alarm condition. Control architecture functionalities include signaling, routing, protection switching and network management. Furthermore, the network management function includes a topology manager, a performance manager, a connection manager, a fault detection manager, and a configuration manager.

Claims

1. A multi-tiered control architecture for an optical network having a plurality of optical switches, comprising:

for each optical switch, respective line card managers for managing respective line cards associated therewith, and a node manager for managing the line card managers; and

a centralized network management system for managing the node managers of the optical switches;

wherein, at each optical switch, the node manager includes an event manager for enabling software components running at the node manager to at least one of;

(a) register for, and receive, events, and (b) post events.

2. The control architecture of claim 1, wherein:

the software components comprise a protection/fault manager component that is adapted to register and receive events from the associated event manager related to alarms at the associated optical switch.

3. The control architecture of claim 1, wherein:

the software components comprise a protection/fault manager component that is adapted to post events with the associated event manager related to at least one of;

(a) alarms at the associated optical switch, (b) changes in configuration information at the associated optical switch, and (c) changes in connection information at the associated optical switch.

4. The control architecture of claim 1, wherein:

the software components comprise a signaling component that is adapted to post an event with the associated event manager regarding whether a light path setup attempt was successful.

5. The control architecture of claim 1, wherein:

the software components comprise a database access protocol client that is adapted to interact with a database at the centralized network management system; and

the database access protocol client is adapted to at least one of;

(a) request configuration data regarding the associated optical switch from other ones of the software components via the associated event manager, and (b) provide configuration data regarding the associated optical switch to other ones of the software components via the associated event manager.

6. The control architecture of claim 1, wherein:

the software components comprise a routing component that is adapted to register for and receive change events from the associated event manager regarding a change in at least one of connection and configuration information of the associated optical switch.

7. The control architecture of claim 1, wherein:

the software components comprise an agent component for applications running at the centralized network management system; and

the agent component is adapted to register for and receive change events from the associated event manager regarding at least one of a resource component, a configuration component and a signaling component.

8. The control architecture of claim 1, wherein:

the software components comprise a resource manager component that is adapted to post change events with the associated event manager regarding a change in resource information at the associated optical switch.

9. The control architecture of claim 8, wherein:

the resource information associated with the change event includes a change in at least one of;

(a) wavelengths used at the associated optical switch, and (b) a state of cross-connects at the associated optical switch.

10. The control architecture of claim 1, wherein:

the software components comprise a configuration manager component that is adapted to register for and receive events from the associated event manager designating that a line card has become active.

11. The control architecture of claim 1, wherein:

the software components comprise a configuration manager component that is adapted to post an event at the associated event manager after configuring at least one of the line cards.

12. The control architecture of claim 1, wherein:

the software components comprise a configuration manager component that is adapted to post an event at the associated event manager after sending a request to change a configuration of at least one of the line cards, and receiving an acknowledgement that the request was carried out.

13. The control architecture of claim 1, wherein:

the software components comprise a software version manager component for configuring the associated node manager and line card managers with software.

14. The control architecture of claim 1, wherein:

the line cards associated with each optical switch include at least one of a transport ingress line card, transport egress line card, optical access ingress line card, optical access egress line card, access line interface card, switching fabric line card, optical signaling card, and optical performance monitoring card.

15. The control architecture of claim 1, wherein:

the line card managers push data up to the associated node managers when the data requires attention by the associated node managers.

16. The control architecture of claim 1, wherein:

the node managers push data up to the network management system when the data requires attention by the network management system.

17. The control architecture of claim 1, wherein:

the node managers collect trend data of the line cards from the line card managers; and

the network management system collects trend data of the node managers.

18. The control architecture of claim 1, wherein:

within at least one of the optical switches, the associated node manager and line card managers communicate with one another via a local area network (LAN).

19. The control architecture of claim 1, further comprising:

an interface between the network management system and a client system that is external to the optical network for enabling the client system to request a light path in the optical network.

20. The control architecture of claim 1, further comprising:

an interface for enabling an exchange of management information between the network management system and a client management system that is external to the optical network.

21. The control architecture of claim 1, further comprising:

an interface to an on-screen graphical user interface for providing status data regarding the optical network.

22. The control architecture of claim 21, wherein:

the status data provides information regarding at least one of topology of the optical switches in the optical network, performance of the optical switches, light path connections in the optical network, faults in the optical network, and configuration of the optical switches.

23. The control architecture of claim 1, wherein:

the network management system and node managers support signaling in the optical network.

24. The control architecture of claim 23, wherein:

the signaling is provided for configuring at least one of the optical switches as at least one of;

(a) an add multiplexer, and (b) a drop multiplexer.

25. The control architecture of claim 23, wherein:

the signaling is provided for configuring at least one of the optical switches as a wavelength cross-connect.

26. The control architecture of claim 1, wherein:

the network management system and node managers support protection switching for responding to detected light path interruptions in the optical network.

27. The control architecture of claim 26, wherein:

the protection switching responds to detected light path interruptions at at least one of the optical switches.

28. The control architecture of claim 26, wherein;

the protection switching provides at least one of line protection and path protection.

29. The control architecture of claim 1, wherein:

the network management system and node managers support network management in the optical network.

30. The control architecture of claim 29, wherein:

the network management is implemented using a software component that is executed at the network management system, and agent software components that are executed at the node managers.

31. The control architecture of claim 29, wherein:

the network management includes a topology manager for managing information regarding physical connectivity of switches in the network.

32. The control architecture of claim 31, wherein:

the topology manager is implemented using a software component that is executed at the network management system.

33. The control architecture of claim 29, wherein:

the network management includes a configuration manager for configuring the optical switches.

34. The control architecture of claim 33, wherein:

the optical switches are configurable by the configuration manager as one of;

(a) a wavelength cross-connect and (b) an optical add and/or drop multiplexer.

35. The control architecture of claim 33, wherein:

the configuration manager is implemented using a software component that is executed at the network management system, and software components that are executed at the node managers.

36. The control architecture of claim 29, wherein:

the network management includes a connection manager for managing information regarding light path connectivity within the optical network.

37. The control architecture of claim 36, wherein:

the connection manager is implemented using a software component that is executed at the network management system, and software components that are executed at the node managers.

38. The control architecture of claim 36, wherein:

the connection manager supports creation and removal of end-to-end light path connections in the optical network.

39. The control architecture of claim 29, wherein:

the network management includes a performance manager for providing information regarding performance of the optical switches and/or the optical network.

40. The control architecture of claim 39, wherein:

the performance manager is implemented using a software component that is executed at the network management system, and software components that are executed at the node managers.

41. The control architecture of claim 1, wherein:

the node managers provide real-time software configuring of the associated line card managers.

42. The control architecture of claim 1, wherein:

the node managers receive at least one of monitored parameters and faults from the associated line card managers.

43. The control architecture of claim 42, wherein:

the node managers aggregate the received monitored parameters and/or alarms into a switch-wide view.

44. The control architecture of claim 1, wherein:

the node managers are adapted to remotely download software from the network management system.

45. The control architecture of claim 1, wherein:

the node managers are adapted to distribute software to the associated line card managers.

46. The control architecture of claim 1, wherein:

the line card managers are adapted to execute commands received from the associated node manager.

47. The control architecture of claim 1, wherein:

the line card managers provide digital and/or analog monitoring of the associated line cards.

48. The control architecture of claim 1, wherein:

the line card managers send at least one of monitored parameters and alarms faults to the associated node manager.

49. A multi-tiered control architecture for an optical network having a plurality of optical switches, comprising:

for each optical switch, respective line card manager means for managing respective line cards associated therewith, and a node manager means for managing the line card manager means; and

a centralized network management means for managing the node manager means of the optical switches;

wherein, at each optical switch, the node manager means includes an event manager means for enabling software components running at the node manager means to at least one of;

(a) register for, and receive, events, and (b) post events.

50. A method for providing a multi-tiered control architecture for an optical network having a plurality of optical switches, comprising:

for each optical switch, managing respective line cards using respective line card managers, and managing the line card managers using a node manager;

managing the node managers of the optical switches using a centralized network management system; and

at each optical switch, enabling software components running at the node manager to at least one of;

(a) register for, and receive, events, and (b) post events.