Abstract: A system may receive a first user input that identifies an optical route in an optical network, may receive a second user input that identifies a direction with which to display the optical route, and may provide, based on the first user input and the second user input, a user interface. The user interface may display optical links associated with the optical route, and may display network entities associated with the optical route. The user interface may display a source entity, where the source entity identifies a source of an optical transmission carried by an optical link, and may display a destination entity, where the destination entity identifies a destination for the optical transmission. The interface may also display an optical power with which the optical transmission is transmitted from the source entity, and may display an optical power with which the optical transmission is received at the destination entity.

Abstract: A system may receive user input that identifies network entities in an optical network. The system may provide a user interface that displays a representation of the network entities and of optical link types configured to carry optical signals among the network entities. The system may receive user input that identifies a particular optical link type, and may display a representation of optical links, of the particular optical link type, that are associated with the network entities. The system may also display an indication of an allocation status of the optical links. The system may receive user input that identifies an available optical link to be allocated for an optical transmission, and may provide, to the network entities and based on the user input, information that identifies the available optical link to permit the available optical link to be allocated for the optical transmission between the network entities.

Abstract: A system may receive a first user input that identifies an optical route in an optical network, may receive a second user input that identifies a direction with which to display the optical route, and may provide, based on the first user input and the second user input, a user interface. The user interface may display optical links associated with the optical route, and may display network entities associated with the optical route. The user interface may display a source entity, where the source entity identifies a source of an optical transmission carried by an optical link, and may display a destination entity, where the destination entity identifies a destination for the optical transmission. The user interface may also display a power adjustment made to the optical transmission at the source entity or the destination entity.

Abstract: A system may receive first user input that identifies an optical route in an optical network, may receive a second user input that identifies a view type, and may provide, based on the first user input and the second user input, a user interface. The user interface may display, based on the identified view type, a representation of components associated with the optical route, a representation of ports on each of the components, a representation of a first parameter associated with each port, and a representation of an optical link associated with the optical route, where the representation of the optical link identifies a port on each of the components that connects the optical link to each of the components.

Abstract: A system may receive a user input that identifies an optical route in an optical network, and may provide a user interface based on the user input. The user interface may display a representation of network entities associated with the optical route, may display a representation of components of the network entities associated with the optical route, and may display a representation of optical links that connect two of the components. The user interface may also display a representation of connection points associated with the components, where each of the connection points identifies a connection between one of the optical links and one of the components, and may display an element that provides an indication of whether an optical transmission, transmitted via one of the optical links, is added, dropped, or routed via the network entity.

Abstract: A system may receive a user input that identifies an optical route in an optical network, and may receive a user input that identifies a view type, where the view type includes a data channel view or a control channel view. The system may provide, based on the user input, a user interface that displays a representation of network entities associated with the optical route, a representation of an amplification capability associated with a network entity, a representation of a first parameter associated with the network entity, where the representation of the first parameter is based on the user input, a representation of optical links that connect the network entities, where the optical links indicate an optical transmission direction between two network entities, and a representation of a second parameter associated with an optical link, where the representation of the second parameter is based on the user input.

Abstract: A network including nodes configured to provide auto-discovery and those that do not are provided in a network. The nodes that do not provide auto-discovery may be provided as end points or terminating nodes in the network. A path or circuit identifier is entered into a database at those nodes and communicated to a network management system. The network management system compares the path identifiers, and, if the two match, the network management system designates the nodes associated with the path identifiers as terminating nodes. A path through the network connecting these nodes can then be determined and monitored. In addition, fiber connection information may further be stored at each node and communicated to the network management system, such that links along the path can also be identified by the network management system. Thus, path determination and monitoring in a network including non-auto-discovering nodes can thus be obtained.

Abstract: A network including nodes configured to provide auto-discovery and those that do not are provided in a network. The nodes that do not provide auto-discovery may be provided as end points or terminating nodes in the network. A path or circuit identifier is entered into a database at those nodes and communicated to a network management system. The network management system compares the path identifiers, and, if the two match, the network management system designates the nodes associated with the path identifiers as terminating nodes. A path through the network connecting these nodes can then be determined and monitored. In addition, fiber connection information may further be stored at each node and communicated to the network management system, such that links along the path can also be identified by the network management system. Thus, path determination and monitoring in a network including non-auto-discovering nodes can thus be obtained.

Abstract: A network element management system which can exploit the customized interface features of a variety of versions of a variety of complex system products from a variety of manufacturers. This is done by maintaining a meta-model, which is not itself a model until instantiated, of the possible known product configurations to be interfaced to. Once the meta-model is instantiated, it provides configuration parameters which the interface program uses to build a correct configuration for the management and/or monitoring interface. This is particularly advantageous in the preferred embodiment of a telecommunications network element management system, but also has potential applicability to other large “supersystem” applications.

Abstract: A network element management system which can exploit the customized interface features of a variety of versions of a variety of complex system products from a variety of manufacturers. This is done by maintaining a meta-model, which is not itself a model until instantiated, of the possible known product configurations to be interfaced to. Once the meta-model is instantiated, it provides configuration parameters which the interface program uses to build a correct configuration for the management and/or monitoring interface. This is particularly advantageous in the preferred embodiment of a telecommunications network element management system, but also has potential applicability to other large “supersystem” applications.

Abstract: A network element management system which automatically configures itself, when an operator enters a component identifier, for optimal full-featured management of the identified component. This is preferably done by an autodiscovery process, and not by any mere lookup.

Abstract: A network element management system which automatically configures itself, when an operator enters a component identifier, for optimal full-featured management of the identified component. This is preferably done by an autodiscovery process, and not by any mere lookup.