Quickly find a path in a complex network

Features

API designed to quickly find paths in a hierarchical network with constraints

API
Offered as a JSON REST server providing the features below.

Build a hierarchical network
A network is made of nodes and links. To help build a network and guarantee its consistency, it is based on a configurable meta-network. A hierarchical network is split in different layers. Each node can be a network in the layer below.

Quickly find paths
A powerful algorithm finds the best paths in a given layer according to various constraints.

Apply various constraints

• Source, intermediate and destination nodes of a flow
• Availability / unavailability / capacity of nodes
• Exclude nodes or node types, ...

Submit a flow
The propagation of a signal, a wave or any kind of data in a network with constraints requires a path.

Broadcasting

NetFlowManager (NFM) API provides also a powerful generic solution for broadcasting automatic planification, it allows to:

• Build a structured hierarchical network of all your broadcasting resources
• Find the best paths of a transmission between a start node and an end node according to various constraints

Here is a small example to illustrate what NFM API can offer.

A hierarchical network is built with 2 layers:

• A layer, named “MACRO”, which gives an overview of the network
• A layer, named “PHYSICAL”, which contains all the equipment or physical resources needed to propagate the signal

Here is the meta-network described at MACRO layer and detailed at PHYSICAL layer:

• A broadcast center (BC) that contains an internal network:
• Matrix to exchange the signal between all its inputs and output nodes
• Fiber input/outputs ports
• Uplinks towards satellite, downlinks from satellite
• Input/output terrestrial circuit ports
• A satellite that contains:
• Transponders
• Fiber network

Terrestrial circuits are represented by links between broadcast centers.

The MACRO network is then built and based on the MACRO meta-network. It contains:

• Broadcast centers are identified by city codes:
• GENEVA
• MADRID
• ...

• 2 satellites are defined:
• USSAT (American)
• EUSAT (European)

• A fiber network named FIBERNET

Once this network is built, NFM API can find an optimized path, for example between WASHINGTON node and ROMA node, much more quickly than a human can.
The found path of the signal starts from WASHINGTON, is then injected into the fiber network and goes out into MADRID. From MADRID, there is an uplink towards EUSAT and then a downlink towards GENEVA. The signal arrives in ROMA using a terrestrial link from GENEVA.

The path can also be calculated in the PHYSICAL layer. It is then possible to book all the resources included in the found path.

This example is very simple, but much more complex networks can be built with NetFlowManager, in which you can quickly find paths of transmissions.
Contact us to have a live demo of this powerful tool !