SDA - Software Defined Access

Phase I - Study

Title

• SDA - Software Defined Access ou SDAN

Objectives

Describe what you intend with this research

Concepts

• SDA provides automated end-to-end segmentation to separate user, device and application traffic without redesigning the network. SD-Access automates user access policy so organizations can make sure the right policies are established for any user or device with any application across the network. This is accomplished with a single network fabric across LAN and WLAN which creates a consistent user experience anywhere without compromising on security
• There are many challenges today in managing the network because of manual configuration and fragmented tool offerings. Manual operations are slow and error-prone and these issues will be exacerbated due to the constantly changing environment with more users, devices and applications.
• With the growth of users and different devices types coming into the network, it is more complex to configure user credentials and maintain a consistent policy across the network. If your policy is not consistent, there is the added complexity of maintaining separate policies between wired and wireless. As users move around the network, it also becomes difficult to locate users and troubleshoot issues. The bottom line is that the networks of today do not address today’s network needs.
• There are three models for a software-defined access network (SDAN), which can apply to any access technology. Unlike traditional SDN, the control and configuration of physical layer parameters also are an integral aspect of a SDAN.
• The first model of a SDAN uses software to centrally control and manage lines connected to the access hardware. Control functions include the optimization of the physical layer configuration of the broadband connection, for example changing parameters such as data rates, coding schemes and power levels to ensure a reliable connection that meets all service requirements.
• Management functions include network diagnostics and analytics that drive maintenance operations and marketing campaigns. Such functions can include line diagnostics used by technicians for isolating and correcting problems in the outside plant, and targeted recommendations for service upsell based on line qualification and past usage records.
• Centralizing these functions enables the use of advanced analysis and resource allocation algorithms implemented in standard servers instead of relying on the more limited and inflexible functionality available in access hardware. Most importantly, this model allows for homogeneous, vendor-agnostic management of the access hardware, and does not require hardware changes since it relies on existing management interfaces.
• The second model of an SDAN uses software to manage virtualized access networks. The return on investment in new access infrastructure (e.g. FTTN, FTTH) is improved when the infrastructure can be shared among multiple, competing service providers. The physical network is partitioned into virtual networks corresponding to the customers of each of the retail providers.
• Software maps the physical access hardware (e.g. DSL access multiplexers or optical network terminals) to virtual hardware. The virtual hardware can be controlled and managed by the service providers (or virtual network operators), while providing for determinacy in the operation and performance of the underlying physical network. This model greatly improves the virtual network operator’s information about and control over the access network, almost as though the operator owns its own hardware. As opposed to the use of Bit-stream Access (Layer 2) unbundling, this model lets the virtual network operator design its own competitive service products and make real-time changes on the network.
• The third model of an SDAN uses software to manage virtualized access network technologies that extend beyond the access segment to the home network and to the end-devices. Examples of such technologies include Wi-Fi network traffic management and speed-boost capabilities by using multiple fixed or wireless links. A virtual network operator may offload traffic from a customer’s mobile device to a Wi-Fi access point connected to a fixed access line within its control. Or it can deliver a boosted service to a customer by combining traffic streams from the Wi-Fi access point of the customer, and from the Wi-Fi access point of a second customer in the vicinity of the first customer. Virtual centralized control of such technologies requires coordination of multiple network elements that can include access hardware, home networks, end-devices and edge routers.

Features

• In the SDN/NFV archtecture, the access has a special focus due to the possibility of operational improvements.
• Currently, there are two main development groups:
  • Open Broadband - Broadband Access Abstraction do BBF
  • SDN Enabled Broadband Access da ONF (Open Network Functions)
• The OB-BAA has more more traditional sellers and the SEBA had already well successful tests.

• BroadBand Access Abstraction (OB-BAA)
  • Study groups focused to the development of opensource frameworks for the SDN/NFV applications in access networks:
  • Framework test Software available for download
  • TIM, Huawai and Nokia had already tested interop in this application
• SEBA/VOLTHA Project
  • ONFs study group focused in the opensource development of SDN/NFV applications in network access.
  • Test software available for download had already showed interop between many sellers
  • AT&T tests with virtual OLT (whitebox) of Edgecore
• https://www.opencompute.org/products?query=switch&page=1

Driven Study

1. Study of SDN - Software Defined-Networks
2. Study of NFV - Network Functions Virtualization
3. Study of GPON - GigaBit Passive Optical Networks and evolution
4. Implementation of OpenStack
5. Study of SDA - Software Defined Access
6. Stydy about project SEBA/VOLTHA da ONF. Implementation of framework in lab.
   1. https://www.opennetworking.org/seba/
   2. https://www.opennetworking.org/voltha/
7. Environment evaluation
8. Participation in the BroadBand Access Abstraction (OB-BAA)

Correlated Works

• ETArch Pilot
  • 3.1 Básico
  • 3.3 SDN
  • 3.4 NFV
  • 3.6 Redes Metro
  • 3.8 Controladores
• 6.1. Evolução: Artigos
  • 12-FIA Book 2011 - Meeting Services
  • 19-WPEIF-2014
  • 22-AICT-2014

Phase II - Teaching

Contents

Desenvolva um conteúdo que possa transmitir o conhecimento adquirido para outros
Crie um material (Wiki, PDF, PPT, ...) que possa ser armazenado e facilmente atualizável

Presentation

Apresente ao grupo (reunião, EAD, Blog, ...)
Publique aqui

Methodology

Descrevas as metodologias usadas. Alguns exemplos:

Estratégia de Job Rotation
Estudos básicos para conhecimento do potencial
Estudos básicos para entendimento sobre o problema
Estudos para dar base aos pesquisadores
Benchmarking com empresas estrangeiras 
Aceleradoras de empresas
Adoção de novas tecnologias
Utilização da proposta de soluções Open-source
Priorização no desenvolvimento interno
Foco na não dependência de fornecedores
Prática de formação dos talentos necessários 

Fase III - Exemplo de Caso de Negócio

Benefícios para quem for oferecer esta solução

    Descrever em tópicos os benefícios que uma pessoa ou uma empresa podem obter: ganhos, receitas, novos negócios, novos produtos, novas parcerias

Benefícios para o usuário

    Descrever em tópicos os benefícios para os usuários desta solução.
    Pode se inspirar no Canvas.

Direcionadores chave para esta iniciativa

    Descrever em tópicos o que esta iniciativa pode proporcionar

Possíveis modelos de negócios

    Descrever em tópicos os possíveis modelos de negócios

Business Case

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

Barreiras encontradas

    Aponte aqui quais foram os principais obstáculos encontrados para o desenvolvimento desta solução

Fase IV - Protótipo orientado ao Negócio

Escopo

Explique o escopo deste protótipo

Limitações

Informe sobre as limitações técnicas, comerciais, operacionais, recursos, etc.

PoC

Desenvolva um PoC (Proof of Concept)

Detalhamento Técnico

Descreva especificamente os aspectos técnicos desta pesquisa

Pesquisadores

• Bruno Rodrigues Rabelo Resende