Infinera Corporation

Fujitsu Corporation

Dharmendra Naik

Kiran Kumar Dintakurthi

Lam Dinh Hoang

Vasudha N Bhaskara

Jagadeesh Virupaksha Huliyar

Rajasekar Venkatesan

Gilbert Levesque

Kasi Viswanadham Pydi

Kamalakannan Govindarajan

Steven Joseph Hand

Biao Lu

Vasudha Bhaskara

Salim Galou

Abhijeet D Deore

Gilbert Lévesque

Yatindra Chugh

Bryce Edwards

Konstantin Saunichev

Prashaanth Ragupathy

Sudhanshu Verma

Venkata Ramarao Garikapati

Mandar A Shinde

Avaneesh C Arora

Syed F Haq

Manish Chandra

Rick Zaeh

Praveen Kumar Pal

Madhav Kothapalli

A network element is herein disclosed. The network element comprises an embedded device having one or more property affecting a function of the embedded device; a computing system having a processor and a memory, the memory being a non-transitory computer-readable medium storing a performance monitoring domain agent, a performance monitoring collector daemon, and a performance monitoring logger. The performance monitoring collector daemon is processor-executable code that when executed by the processor causes the processor to communicate with the embedded device and collect one or more performance information of the embedded device based on the one or more property. The performance monitoring domain agent is processor-executable code that when executed by the processor causes the processor to: retrieve the performance information from the performance monitoring collector daemon; format the performance information into a formatted data based on a metrics metadata file; and transmit the formatted data to the performance monitoring logger.

Observability without changing the target

A network element is herein disclosed. The network element comprises an embedded device having one or more property affecting a function of the embedded device and one or more status; a first computing system having a first processor and a first memory, the first memory being a first non-transitory computer-readable medium storing a device microservice and a hardware entity microservice, the hardware entity microservice in communication with the embedded device; a second computing system having a second processor and a second memory, the second memory being a second non-transitory computer-readable medium storing a core framework microservice; and a communication device in communication with the first computing system and the second computing system.

Streaming and config for event driven microservice architecture for embedded services

A computer-readable medium storing instructions that, when executed by one or more processors, cause the one or more processors to: receive a setup request for an optical path between a source entity of network entities in an optical network and a destination entity of the network entities, identify a first channel and a second channel having one or more contiguous first span with an allocation status of available and being configurable to provide the optical path between the source entity and the destination entity; analyze network configuration data indicative of the first channel and the second channel with a fragmentation heuristic to generate an allocation recommendation recommending the first channel to be allocated to the optical path; and provide the allocation recommendation identifying the first channel for allocation to the optical path.

Optical bandwidth manager

In the disclosed method, a current state of a network device indicative of no license key being associated with a network device is stored in a license database. Information indicative of a master state of the network device is received, via an input port, including at least one license key associated with the network device. The current state of the network device is updated to include the at least one license key associated with the network device, and the updated current state is stored in the license database.

License management system

A centralized network administrator may automatically provision an Ethernet circuit between network elements by storing and managing circuit data (managed objects) in one of the network elements (master node) and synchronizing the circuit data among the network nodes in the Ethernet circuit path. In addition, multiple network administrators may provision multiple Ethernet circuits using the overlapping network elements by managing access to the circuit data in the Master node.

Systems and methods for provisioning ethernet services

A network device may receive an activation instruction. The network device may provide network resources. The activation instruction may request the network device to activate a particular network resource that is deactivated. The activation instruction may be associated with a license that identifies the particular network resource and identifies a resource request of a user. The network device may configure, based on the activation instruction, a component of the network device to activate the particular network resource. The component, after being configured to activate the particular network resource, may allow data flows, received by the network device, to be provided towards a destination device using the particular network resource. The network device may receive a data flow and provide, by the component of the network device, the data flow towards the destination device using the particular network resource.

Dynamic activation of pre-deployed network resources

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.

A license management system comprises at least one processor capable of executing processor-executable code coupled with a non-transitory processor-readable medium storing a master license database and processor-executable code for causing the processor to: (a) store a master state of a network device indicative of at least one license key associated with the network device in the master license database; (b) access information indicative of a license key request for the network device subsequent to the storing of the master state, the license key request including a current state of the network device; (c) compare the master state of the network device with the current state of the network device; and (d) in response to the master state differing from the current state of the network device, generate an error message and store the error message in non-transitory processor-readable medium.

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.

Digital link viewer

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.

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.

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.

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.

Network management system

A network management system includes a network management server and one or more clients initiating network management messages between the server and network elements. The server parses the network management messages and communicates each message to client consoles having filtering criteria satisfied by the contents of the message.

Filtering network management messages

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.

Growing community of inventors

San Jose, CA, United States of America

Dharmendra Naik