Embedded controller architecture for a modular optical network, and methods and apparatus therefor

• US 20020165962A1
• Filed: 02/28/2001
• Published: 11/07/2002
• Est. Priority Date: 02/28/2001
• Status: Abandoned Application

• Current Assignee: Lambda Optical Systems Corporation
• Original Assignee: Lambda Optical Systems Corporation
• Inventors: Amoroso, Michael S., Tzathas, Anastasios, Alvarez, Mario F., Battou, Abdella, Garrick, Richard J., Liu, Gyi-Hong, Shung, Wu-Shi
• Application Number:
  US09/795,534
• Publication Number:
  US 20020165962A1
• Time in Patent Office: Days
• US Class Current: 709/226
• 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 Line Card Manager (LCM) architecture for use at an optical switch in an optical communications network. A LCM with a dedicated processor is provided for different line cards at the switch. The LCM includes a first interface, such as a connector to the line card, for receiving monitored parameters from the line card, and a processor that executes software for determining when an event such as a fault should be set, e.g., when a monitored parameter is out of range. The LCM has a second interface to a local area network at the switch for reporting the event to a Node Manager, which manages the LCM. The LCM is preferably a removable plug-in module of the line card to allow easy upgrades and maintenance. The LCM includes generic software for managing different types of line cards.

Claims

1. A management architecture for use at an optical switch in an optical network, comprising:

a line card manager at the optical switch for managing an associated line card at the optical switch;

said line card manager comprising;

(a) a first interface for receiving monitored parameter values from the line card;

(b) processing resources for setting an event regarding the line card when criteria for setting the event is met by the monitored parameter values; and

(c) a second interface for communicating the event to a node manager at the optical switch that manages the line card manager.

2. The architecture of claim 1, wherein:

the event comprises a fault regarding the line card.

3. The architecture of claim 1, wherein:

the monitored parameter values comprise at least one of digital and analog parameter values.

4. The architecture of claim 1, wherein:

the line card manager is adapted to communicate the monitored parameter values to the node manager via the second interface.

5. The architecture of claim 1, wherein:

the processing resources are adapted to execute commands received from the node manager via the second interface.

6. The architecture of claim 1, wherein:

the second interface comprises an interface to a local area network at the optical switch that allows the line card manager to communicate with the node manager.

7. The architecture of claim 6, wherein:

the local area network uses a shared medium.

8. The architecture of claim 1, further comprising:

non-volatile memory resources at the line card manager for storing software that is executable by the processing resources for use in managing the line card.

9. The architecture of claim 8, wherein:

the line card is managed by the stored software at the line card manager without requiring software to be downloaded from the Node Manager.

10. The architecture of claim 8, wherein:

the software is loaded from the non-volatile memory resources to the processing resources upon initialization of the line card manager.

11. The architecture of claim 1, further comprising:

non-volatile memory resources at the line card manager for storing a current version and a backup version of software that is executable by the processing resources for use in managing the line card.

12. The architecture of claim 1, further comprising:

a status register at the line card manager for receiving the monitored parameter values from the line card via the first interface.

13. The architecture of claim 1, wherein:

the line card comprises 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 performance monitoring line card, and optical signaling line card.

14. The architecture of claim 1, wherein:

the processing resources comprise a microprocessor for setting the event.

15. The architecture of claim 1, wherein:

the line card manager is provided as a removable plug-in module of the line card.

16. The architecture of claim 1, wherein:

the processing resources are provided with software by the node manager via the second interface; and

the software is executable by the processing resources for use in managing the line card.

17. The architecture of claim 1, further comprising:

memory resources at the line card manager for storing the monitored parameter values.

18. The architecture of claim 1, wherein:

the line card manager is provided with a threshold level by the node manager via the second interface for setting the event when the monitored parameter values cross the threshold level.

19. The architecture of claim 1, wherein:

the processing resources are adapted to apply control signals to the line card via the first interface.

20. The architecture of claim 19, wherein:

the control signals comprise at least one of digital and analog control signals.

21. The architecture of claim 19, further comprising:

a control register at the line card manager for applying the control signals to the line card.

22. The architecture of claim 1, further comprising:

at least one additional line card manager for managing a respective line card at the optical switch;

said additional line card manager comprising;

(a) a first interface for receiving respective monitored parameter values from the respective line card;

(b) processing resources for setting a respective event regarding the respective line card when criteria for setting the respective event is met by the respective monitored parameter values; and

(c) a second interface for communicating the respective event to the node manager at the optical switch;

wherein the node manager manages each of the line card managers.

23. The architecture of claim 22, wherein:

each line card manager provides local control of its respective line card.

24. The architecture of claim 22, wherein:

the respective line card managers communicate via their respective second interfaces with the node manager via a common local area network.

26. The architecture of claim 25, further comprising:

at least one additional line card manager means for managing an associated line card at the optical switch;

said additional line card manager means comprising;

(a) means for receiving respective monitored parameter values from the respective line card;

(b) means for setting a respective event regarding the respective line card when criteria for setting the respective event is met by the respective monitored parameter values; and

(c) means for communicating the respective event to the node manager at the optical switch;

wherein the node manager manages each of the respective line card manager means.

28. The method of claim 27, further comprising:

pushing data regarding the line card from the line card manager up to the node manager when the data requires attention by the node manager.

29. The method of claim 27, wherein:

the event is set when the monitored parameter values cross a threshold level.

30. The method of claim 27, further comprising:

receiving, at the line card manager, a line card identifier from the line card for use in identifying a type of the line card.

31. The method of claim 30, further comprising:

providing the line card manager with software for managing a plurality of different types of line cards; and

using a portion of the software for controlling the associated line card according to the received line card identifier.

32. The method of claim 30, wherein:

the type comprises 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 performance monitoring line card, and optical signaling line card.

33. The method of claim 27, further comprising:

multi-tasking, at the line card manager, multiple sense-and-control processes for the line card.

34. The method of claim 33, wherein:

each of the processes involves at least one of monitoring and controlling a corresponding function of the line card.

35. The method of claim 27, further comprising:

receiving, at at least one additional line card manager, respective monitored parameter values from respective associated line cards;

setting an event regarding the respective line card when criteria for setting the event is met by the respective monitored parameter values; and

communicating the event to the node manager;

wherein the node manager manages each of the respective line card managers.

25. A management architecture for use at an optical switch in an optical network, comprising:

line card manager means at the optical switch for managing an associated line card at the optical switch;

said line card manager means comprising;

(a) means for receiving monitored parameter values from the line card;

(b) means for setting an event regarding the line card when criteria for setting the event is met by the monitored parameter values; and

(c) means for communicating the event to a node manager at the optical switch that manages the line card manager means.

27. A method for managing an optical switch in an optical network, comprising:

receiving, at a line card manager at the optical switch, monitored parameter values from an associated line card at the optical switch;

setting an event regarding the line card when criteria for setting the event is met by the monitored parameter values; and

communicating the event to a node manager at the optical switch that manages the line card manager.