Teraflow SDN

TeraFlow OS is one of the first open-source, micro-service based, cloud-native and carrier-grade SDN controller capable of integrating with current NFV and MEC frameworks as well as to provide revolutionary features for both flow management (service layer), and network equipment integration (infrastructure layer), while incorporating ML-based security and PDL-based forensic evidence for multi-tenancy.

The source code of the first version of the TeraFlow OS SDN Controller is publicly availably for download and installation at the GitLab repository under Apache2 license:

TeraFlow OS SDN Controller

  • The Problem
    Current solutions consist of monolithic software core that can synchronize with other deployed SDN controllers through specific protocols.
  • Ambition
    Implementing a clear path to introduce the TeraFlow OS SDN deployments into operators’ networks
  • Innovation
    TeraFlow OS is one of the first of a new type of secured cloud-native SDN controllers that will radically advance the State-of-the-Art in software-defined network.
  • Why TeraFlow?
    TeraFlow OS follows a cloud-native architecture with stateless micro-services which interact with each other to fulfil network management tasks
  • Our approach
    TeraFlow OS promotes open competition and innovation in two key market segments: transport network devices and network applications
  • Technology
    TeraFlow OS uses open and standard APIs enabling transport network abstraction and vendor-agnostic programmability

TeraFlow proposes a new Transport SDN architecture enabling an open environment for network applications and devices using full standard interfaces with container-based services which are deployed as microservices and managed on elastic infrastructure through agile DevOps processes and continuous delivery workflows.

  • Load Balancing
    Allows the distribution of flow and slice requests among the micro-services component replicas.
  • Cybersecurity
    Provides AI/ML-based mechanisms to detect network intrusions and harmful connections while delivering countermeasures to security incidents.
  • Autoscaling
    Directs the autonomous replication of micro-services to support a high number of incoming requests.
  • Self-healing
    Monitors micro-services and per-flow status to apply healing mechanisms from a control and data plane perspective.
  • Inter-domain smart connectivity services
    Allows the interaction of a TeraFlow OS instance with peer ones managing different network domains.
  • Slice Manager
    Uses the Network Slice Controller to realise a transport network slice, using physical and virtual network resources provided by underlying network controllers, managing both optical and packet resource domains.
  • Service
    Implementing a clear path to introduce the TeraFlow OS SDN deployments into operators’ networks
  • Traffic Engineering
    Responsible for setting up and optimising Segment Routing paths in the infrastructure which are exposed by the Device component considering the constraints and available resources.
  • Distributed Ledger
    Provides a distributed ledger to record, query and process relevant data for network management and detection of compromised edge devices. Also, records slice requests in the blockchain.
  • Compute Integration
    Responsible for providing connectivity to external systems, such as NFV domains, by exporting a REST-API-based NorthBound Interface (NBI). Also translates external requests to be managed by the TeraFlow OS components.
  • Policy
    Translates high-level policy rules to the actual configuration in an automatic manner to either physical or virtual devices.
  • Context
    Stores the configurations and attributes of the different network elements managed by the TeraFlow OS, such as contexts, topologies, devices, links and services created.
  • Device
    Handles the interaction with underlying network equipment with an API, enabling developers to implement new drivers to integrate them into the TeraFlow OS.
  • Monitoring
    Monitors the different metrics or KPIs configured for the network devices and services, records the monitoring data associated with these KPIs, and provides a medium for other components to access the collected data.
  • Automation
    With zero-touch interventions nor local configuration, adds and updates a physical or virtual device, SDN controllers or management tools to the network, while ensuring that the correct certificates, software, configuration parameters and pipeline definition are installed.