Phase I - Study


Title

  • SEBA - SDN Enabled Broadband Access


Objective

  • SDN-Enabled Broadband Access (SEBA) is an Exemplar Platform being built by the ONF and CORD community.


Concepts


  • SEBA is a lightweight platform based on a variant of R-CORD. It supports a multitude of virtualized access technologies at the edge of the carrier network, including PON, G.Fast, and eventually DOCSIS and more. SEBA supports both residential access and wireless backhaul and is optimized such that traffic can run ‘fastpath’ straight through to the backbone without requiring VNF processing on a server.
  • Is integrated with Kubernetes, prepared for use in high speed and operationalized with FCAPS and OSS Integration.
  • This project intends to anticipate a big trend that is to bring the features of SDN to access broadband.


Features


  • Integration with:
    • VOLTHA (Virtual OLT Hardware Abstraction): An open source project to create a hardware abstraction for broadband access equipment. It supports the principle of multi-vendor, disaggregated, “any broadband access as a service” for the Central Office. VOLTHA currently provides a common, vendor agnostic, GPON control and management system, for a set of white-box and vendor-specific PON hardware devices. With the upcoming introduction of access Technology Profiles, VOLTHA will support other access technologies like EPON, NG-PON2 and G.Fast as well. On its northbound interface, VOLTHA abstracts the PON network to appear as a programmable Ethernet switch to an SDN controller. On its southbound side, VOLTHA communicates with PON hardware devices using vendor-specific protocols through OLT and ONU adapters.
    • ONOS: The only SDN controller platform that supports the transition from legacy “brown field” networks to SDN “green field” networks. This enables exciting new capabilities, and disruptive deployment and operational cost points for network operators. ONOS is the only open source controller providing:
      • Scalability
      • High performance
      • Resiliency
      • Legacy device support
      • Next-generation device support
    • TRELLIS: Is the leading open-source SDN based, multi-purpose L2/L3 spine-leaf switching fabric for data-center (DC) networking. Leveraging the ONOS Controller, Trellis creates a non-blocking fabric for data centers using white box switching hardware and open source software. Unlike traditional networking approaches, the fabric itself does not run a control protocol (such as BGP, OSPF or RSTP). Instead, all the intelligence is moved into applications running on the clustered ONOS controller. In this way the fabric switches can be simplified, the entire fabric can be optimized by leveraging a holistic view of all activity, and new features and functionality can be deployed without upgrading the switches.


Oriented Study


Write here, the study plane and the references.


Phase II - Teaching


Content

  • GPON - GigaBit Passive Optical Networks
  • SDN - Software Defined Networking


Presentation


Metodology


Describe the metodologies.


Phase III - Example of Business Case


Benefits to the owner



Benefits to the user


Drivers



Business Models

Business Case

    Descrever um exemplo de negócio que permita avaliar a solução comercialmente


Lei do Bem


  • Projeto possui algum elemento tecnologicamente novo ou inovador?
Elemento tecnologicamente novo ou inovador pode ser entendimento como o avanço tecnológico pretendido pelo projeto, ou a hipótese que está sendo testada


  • Projeto possui barreira ou desafio tecnológico superável?
Barreira ou desafio tecnológico superável pode ser entendido como aquilo que dificulta o atingimento do avanço tecnológico pretendido, ou dificulta a comprovação da hipótese


  • Projeto utiliza metodologia/método para superação da barreira ou desafio tecnológico?
Metodologia/método para superação da barreira ou desafio tecnológico pode ser entendido como aqueles atividades que foram realizadas para superação da barreira ou do desafio tecnológico existente no projeto


  • Projeto é desenvolvido em parceira com alguma instituição acadêmica, ICT ou startup?
Se sim, o desenvolvimento tecnológico é executado por associado ou por alguma empresa terceira? qual o nome da empresa? 
Anexar cópia do contrato


Phase IV - Prototype oriented to the business


Scope


To install, configure, learn and to aplly techniques to implement the SEBA platform


Product Backlog


Describe the requisites


Limitations




PoC


Proof of Concept


Technical Details


  • The SEBA project delivers a set of software components specified in the high-level architecture, including but not necessarily limited to NEM/Edge Cloud Orchestrator, SDN controller, Access Node (AN) driver, Aggregation & Service Edge (ASG) driver.
  • The hardware from vendors may also include embedded software for controlling, monitoring and abstracting low level functions of the hardware, including BIOS, firmware, board support drivers and board management controllers (BMCs).

SEBA Service Layer

  • BNG
    • The BNG (Broadband Network Gateway) is a key component in fixed broadband access networks. It resides at the demarcation point between the access network (usually based on L2 tunnels) and the routed IP/MPLS network. The BNG provides per-subscriber services and is the highest-tier network element that has the full per-subscriber context. Beyond this point, traffic can be correlated to a subscriber using the IP address, but the complete view is gone. The functional requirements on BNG types are described by the Broadband Forum (BBF, TR-178 and related documents). The core functions of a BNG at the access side and towards the core, but not

limited to, are:

      • Aggregation of L2 access tunnels / VLANs / MPLS PWs
      • Termination of network attachment (PPPoE or IPoE tunnels), authentication, (dynamic) policy enforcement, AAA client
      • Tunnel switching and termination (e.g., L2TP LAC)
      • Traffic filtering and shaping
      • Lawful interception
      • Anti-Spoofing
      • Split horizon rules
      • Per-subscriber OAM (e.g. using keepalives)
      • Accounting
    • The BNG also acts as a router as it is part of the IP core network of the service provider. This covers, amongst others, the following functions:
      • Routing protocols (IGPs, EGPs)
      • MPLS control and user planes
    • The BNG directly interfaces with Policy control systems and AAA services.
    • In SEBA, there are multiple ways to deal with the required BNG functionality:
      • a) Serve an external BNG. In this case, SEBA acts as smart aggregation network
      • b) Embed the BNG as part of the POD, either as PNF or VNF
      • c) Decompose the BNG into Service Edge (SE) and Router and deploy as PNF or VNF with the PNF possibly being embedded in the AN or ASG. While the first two options basically represent state-of-the art thinking and keep existing centralized functionality in closed systems, option
      • c) goes beyond.
  • Network Edge Mediator (NEM)
    • The Network Edge Mediator (NEM) serves as the mediation layer between the edge/access system and the service provider backend and global automation frameworks. NEM will provide the interfaces and components to support FCAPS functionalities required by the service provider for managing the access network components and broadband service subscribers the SEBA POD is designed to offer and support. A variety of operator OSS/BSS and global orchestration frameworks can be integrated northbound for specific deployment needs.

Functionalities:






Schedule


Historic



Researchers

  • Ana Paula Fernandes
  • Aymen Ghannouchi
  • Bruno Rodrigues Rabelo Resende
  • Luiz Cláudio Theodoro
  • Raoni Exaltação Masson
  • Willian Santos Silva