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.

Abstract: An optical transport switching system having an all-optical switch that can be selectively configured to provide cross-connection and add/drop multiplexing functions. Optical circuit cards are provided in a chassis/bay, and connected by an optical backplane. The circuit cards may include access line interface cards, optical access ingress cards, transport ingress cards, transport egress cards, and optical access egress cards. An optical switching fabric provides selective optical coupling between the cards. The all-optical switch can be used in an optical network that allows external/access networks to access the optical network, including access networks that use Gigabit Ethernet or SONET signaling. Wavelength conversion is provided for non-compliant wavelengths of the access networks. A local area network enables control and monitoring of the cards by a local node manager.

Abstract: An optical switch architecture in an optical communications network. The imminent removal of a line card from a slot at the optical switch is detected to inform an associated software process/manager that manages the line card that it is going to be removed. The movement of a locking mechanism that locks the line card in its slot triggers a message to a Node Manager that the line card is about to be removed. The software process knows that it will not be able to communicate with the line card, such as to request data or transmit commands. Moreover, the software process knows to not set an alarm for a malfunctioning line card since it will not receive any responses from the removed line card. The software process also maintains information related to the line card during its removal for use when the line card is subsequently re-installed.