Node management architecture with customized line card handlers for a modular optical network, and methods and apparatus therefor

• US 20030091267A1
• Filed: 05/14/2002
• Published: 05/15/2003
• Est. Priority Date: 02/28/2001
• Status: Abandoned Application

• Current Assignee: Firstwave Secure Intelligent Optical Networks Inc.
• Original Assignee: Firstwave Secure Intelligent Optical Networks Inc.
• Inventors: Garrick, Richard J., Sung, Wu-Shi, Chen, Chin J., Alvarez, Mario F., Battou, Abdella, Liu, Gyi-Hong
• Application Number:
  US10/145,967
• Publication Number:
  US 20030091267A1
• Time in Patent Office: Days
• US Class Current: 385/16
• CPC Class Codes: H04Q 11/0005 Switch and router aspects
• 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/0039 Electrical control
• CPC Class Codes: H04Q 2011/0081 Fault tolerance; Redundancy; Recovery; Reconfigurability
• CPC Class Codes: H04Q 2011/0083 Testing; Monitoring

Abstract

A node management architecture for use at an optical switch/node in an optical communications network. A software task is provided for managing each line card according to a type of the line card. The architecture may identify the line card type, and assign a corresponding software task to manage it. To avoid delays, unassigned software tasks may be created ahead of time for managing line cards that are later installed at the optical switch. Furthermore, different types of software tasks are provided for managing corresponding different types of line cards, while software tasks that manage the same type of line card may be organized as an array of the same type. Moreover, the software tasks may act as an intermediary between the line card managers and other software processes at the node manager, such as a database manager, alarms manager, or optical cross-connect manager.

Claims

1. A node manager software architecture at an optical switch in an optical network, comprising:

a node configuration manager that creates a plurality of software tasks, each of which is capable of managing a line card and at least one of which manages an associated line card that is installed at the optical switch;

wherein the software tasks have a functionality that is customized according to a type of the associated line card.

2. The architecture of claim 1, wherein:

the software tasks whose associated line cards are of a common type have a common functionality.

3. The architecture of claim 1, wherein:

the line cards are managed by respective line card managers at the optical switch; and

each of the software tasks manages its associated line card via the respective line card manager.

4. The architecture of claim 1, wherein:

the node configuration manager creates at least one additional, unassigned software task, for each of the line card types;

wherein each of the unassigned software tasks maintains readiness to manage an associated type of line card upon installation thereof at the optical switch.

5. The architecture of claim 1, wherein:

the node configuration manager assigns the software tasks to manage their associated line cards according to identifiers of the associated line cards.

6. The architecture of claim 5, wherein:

the identifiers identify the respective type of the respective associated line card.

7. The architecture of claim 5, wherein:

the identifiers distinguish the line cards from one another.

8. The architecture of claim 5, wherein:

the identifiers uniquely identify the line cards.

9. The architecture of claim 5, wherein:

the identifiers are provided to the node configuration manager based on data stored at the respective line cards.

10. The architecture of claim 9, wherein:

the data are stored in respective non-volatile memories of the line cards.

11. The architecture of claim 5, wherein:

the line cards are managed by respective line card managers at the optical switch; and

the identifiers are provided to the node configuration manager via the respective line card managers.

12. The architecture of claim 1, wherein:

the line cards are managed by respective line card managers at the optical switch; and

the software tasks provide configuration data to the respective line card managers for use in managing the associated line cards.

13. The architecture of claim 12, wherein:

the configuration data includes threshold levels for parameters of the line cards that are monitored by the respective line card managers.

14. The architecture of claim 12, wherein:

the configuration data includes mask data for filtering parameters of the line cards that are monitored by the respective line card managers.

15. The architecture of claim 12, wherein:

the respective line card managers of respective ones of the line cards that are of a common type are configured with common configuration data.

16. The architecture of claim 1, wherein:

the software tasks run separately from one another.

17. The architecture of claim 1, wherein:

the software tasks receive and process monitored parameters of the associated line cards.

18. The architecture of claim 1, wherein:

the software tasks aggregate data from the associated line cards for use by at least one of;

a database manager, an alarms manager, and an optical cross-connect manager at the node manager.

19. The architecture of claim 1, wherein:

the software tasks provide commands to the associated line cards from at least one of;

a database manager, an alarms manager, and an optical cross-connect manager at the node manager.

20. The architecture of claim 1, wherein:

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

21. The architecture of claim 1, wherein:

at least a particular one of the line cards continues to be managed by its associated software task after the particular line card is uninstalled from the optical switch and subsequently reinstalled at the optical switch.

22. The architecture of claim 1, wherein:

at least a particular one of the line cards continues to be managed by its associated software task after the particular line card is uninstalled from a particular line card receiving location at the optical switch and subsequently reinstalled at a different line card receiving location at the optical switch.

23. A node manager software architecture at an optical switch in an optical network, comprising:

means for creating a plurality of software tasks, each of which manages an associated line card that is installed at the optical switch;

wherein the software tasks have a functionality that is customized according to a type of the associated line card.

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

creating a plurality of software tasks, each of which is capable of managing a line card; and

managing, by at least one of the plurality of software tasks, an associated line card that is installed at the optical switch;

wherein the software tasks have a functionality that is customized according to a type of the associated line card.

25. A node manager system at an optical switch in an optical network, comprising:

a node configuration manager sub-system that creates a plurality of tasks, each of which is capable of managing a line card and at least one of which manages an associated line card that is installed at the optical switch;

wherein the tasks have a functionality that is customized according to a type of the associated line card.

26. A computer program product comprising a computer usable medium having computer readable code embodied therein, the computer program product comprising:

computer readable program code devices configured to cause a computer to create a plurality of tasks, each of which is capable of managing a line card at an optical switch in an optical network, and at least one of which manages an associated line card that is installed at the optical switch;

wherein the tasks have a functionality that is customized according to a type of the associated line card.

27. A data processing system having a memory, comprising:

a node manager sub-system for creating a plurality of tasks, each of which is capable of managing a line card at an optical switch in an optical network, and at least one of which manages an associated line card that is installed at the optical switch;

wherein the tasks have a functionality that is customized according to a type of the associated line card.