ZooNet

Participação Empresa

• Disponibilizar um ambiente real com a participação de profissionais engajados para validar não apenas a funcionalidade mas também a aceitação do usuário e a viabilidade econômica
  • Torna-se mais desafiador e caro para os pesquisadores construirem em seus próprios laboratórios virtuais, sistemas para a FI e soluções de rede que tem se ampliado e diversificado cada vez mais.

• Os parceiros como ANSP e ALGAR poderão disponibilizar suas infraestruturas em regime controlado para implantar e testar os protótipos desenvolvidos ao longo do projeto.
  • ZooNet tem a intenção de acompanhar a iniciativa do FIRE para extender os testes além da rede fechada.
  • O projeto Fed4FIRE fornece uma facilidade de experimentação federada que suporta um amplo conjunto de comunidade de experimentadores cobindo todas as camadas da infraestrutura Internet para plataforma de serviços e aplicações.

Work package 1: Project management and financial control – Leader: EPUSP

• Algar Telecom => No responsibility.

Work package 2: Requirements and validation – Leader: EPUSP

• Role of the ALGAR involved in the WP:
  • as a commercial network operator will participate in all tasks to identify infrastructure development requirements to host the proposed applications/services complying with the governance bounded SLA criteria

• Requisitos e validação
• Algar: 8 pessoas-mês
• Objetivos: The purpose of WP2 is to generate guidelines for such the FI solutions generated in the project from an end-user perspective. For structuring the work we use the model labelled “Stakeholder Coordination Model” (SCM) developed by the Copenhagen Business School (CBS). It has three levels that acknowledge the multi-level organisational nature of stakeholder governance and SLA structure.
• Especificos:
  • 1) Setup an end-users board.
  • 2) Promote the coordination of stakeholders both represented and not in the project including members of the technical community, policy makers and end-users community.
  • 3) Identify along the use cases possible needs that can be satisfied with ICT support.
  • 4) Define governance guidelines for traffic data gathering and analysis.
  • 5) From the end users and network & service providers perspectives define the SLA criteria to be translated into technical requirements and fulfilled by the providers.
  • 6) Specify the applications and services to be prototyped in the project to validate the short term new FI solutions developed in the project.
  • 7) Validate from the point of view of the end-user’s needs satisfaction the new FI solutions developed in the project.
• Responsabilidade Algar:
  • Colaborar na definição de casos de uso, linhas de governança, SLAs e protótipos

Task 2.1. Stakeholders board setup and end-users needs identification

• EPUSP, UFABC, ANSP, ALGAR
• Leader: EPUSP
• Duration: M2 - M3
• Colaborar na construção do SCM Top Level com os seguintes resultados:
  • 1) Narrative of Business (broadly understood) scenario.
  • 2) Categorisation of use cases.
• Método: Business Model Canvas

• A proposta considera tecnologias heterogêneas para a Internet incluindo Ethernet-based switched, IP routed e transporte óptico.
• Em adição, redes de acesso sem e com fio e redes de sensores sem fio são considerados.
• Dois casos de uso serão usados como zonas físicas de : Setor Agrifood and Smart cities
• A função deles será gerar os dados dos objetos conectados à Internet
• Os fluxos de dados constroem os fluxos de tráfego que serão transporão a rede e ṕoderão ser entregeus para Data Centres em nuvem para processamentos e a informação resultante transpõe novamente a rede para retornar à zona física de origem e podem atual sobre os objetos e/ou sobre o ambiente onde eles estavam imersos.

• Parte da rede pertence à ALGAR e ANSP, onde as unidades de monitoramento de tráfego da rede será instalados para reunir tráfego de dados e habilitar uma análise compreensiva.
• A Análise de tráfego é objeto do WP3.

• A estrutura proposta também estará habilitada na realização de testes de stress.
• Neste caso, tráfego especial com características específicas será gerado para provar os limites da rede.
• Isto permitirá executar identificação experimental dos limites da Internet para o cenário de objetos conectados à Intennet.
• Teste de stress são objetos do WP6.

Task 2.2. Mapping user requirements and needs into IoT-based solutions

• EPUSP, UFABC, ANSP, ALGAR
• Leader: EPUSP
• Duration: M3 - M18
• Colaborar na construção do SCM Top Level com os seguintes resultados:
• Set of activities:
  • (i) compare similar solutions and ask users and other stakeholders why they use them, how satisfied they are with them with regard to functionality, quality, security and privacy, and ask them what features they miss
  • (ii) study how interoperable these solutions are
  • (iii) assess safety and privacy issues in connection with the solutions;
  • (iv) ask the stakeholders what unsolved problems they have (with agrifood and smart city living) and which new solutions they are looking for / missing.

Task 2.3. Elaborating Service Level Agreements and technical specifications

• EPUSP, UFABC, ANSP, ALGAR
• Leader: ANSP
• Duration: M14 - M26
• This task is about developing the SCM Technical Level and the objective is:
  • to transform these critical descriptions into generic descriptions of essential requirements for FI solutions and translated into Service Level Agreements (SLAs). We will use a non-technical descriptive language

Task 2.4. Specification of use cases applications

• EPUSP, UFABC, ANSP, ALGAR
• Leader: UFABC;
• Duration: M11 - M17
• The goal of this task is to specify the use cases applications that will be developed in the project
  • Along the use case specification this task will provide the network architecture requirements particularly to allow for distributed, lightweight learning mechanisms throughout the network.

Task 2.5. Monitoring and validation

• EPUSP, UFABC, ANSP, ALGAR
• Leader: UFABC;
• Duration: M4 - M36
• The objective of this task is to perform a continuous monitoring of the activities developed in WP3, WP4 and WP6 to ensure that the governance guidelines, the SLA criteria and the end-users identified needs are being adequately observed ** Along the use case specification this task will provide the network architecture requirements particularly to allow for distributed, lightweight learning mechanisms throughout the network.
  • Such monitoring will be made periodically by means of webminars

Work package 3: Traffic analysis – Leader: ANSP

• Role of the ALGAR involved in the WP:
  • Will utilize its existing suite of traffic measurement and analysis tools, and those developed in T3.1 to observe the traffic mix and behaviour of baseline existing traffic and compare it to the behaviour of traffic generated in T3.5. In T3.2, measurements would be done on Algar’s existing production network, utilising various access technologies and platforms, to determine their impact on various types of generated flows.

• Requirements and validation
• Algar: 18 Person-months
• Objectives: The main objective of WP3 is to design and develop innovative methods for collecting and analysing the traffic exchanged by a diverse range of heterogeneous Future Internet (FI) services and devices, including Internet-connected objects under the Internet of Things paradigm (IoT). A detailed analysis of the IoT traffic will allow the project to understand the main characteristics and particularities of the FI traffic, learn how objects and applications communicate among them, and how their traffic differs from that of the traditional Internet.
• Functions and information extracted from the FI monitoring units,

WP3 will specifically focus on the following:

• • 1) traffic classification (i.e., identification of IoT applications and protocols from the collected traffic)
  • 2) detection of flow dimensions (e.g., elephant, mouse, tortoise, dragonfly, cheetah, snail, etc.)
  • 3) end-point detection and classification (e.g., type of objects, sensors, etc.)
  • 4) traffic matrix estimation (e.g., traffic between different operators as estimated from a limited number of vantage points)
  • 5) measurement of Key Performance Indicators for QoS/QoE (e.g., delay, jitter, packet loss, etc.).

Task 3.1. Design and deployment of FI monitoring units

• EPUSP, UFABC, ANSP, ALGAR, TAL
• Leader: ANSP;
• Duration: M1-M18
• This task will deal with the design and development of FI monitoring units to be deployed in both the end points (e.g., objects and sensors) and the communication devices of the provider and transport networks (e.g., routers and switches)

Task 3.2. Traffic identification and classification

• EPUSP, UFABC, ANSP, ALGAR, TAL
• Leader: EPUSP
• Duration: M6-M36
• The proposed techniques will focus on different dimensions:
  • (1) IoT applications and protocols
  • (2) flow types
  • (3) end points
  • (4) traffic matrices

Task 3.3. Measurement of Key Performance Indicators

• EPUSP, UFABC, ANSP, ALGAR, TAL
• Leader: ANSP;
• Duration: M14-M30
• The goal of this task is to develop traffic modelling and forecasting techniques that enable the implementation of FI traffic generators in Task 3.5 and that can guide dynamic resources assignment techniques that will be proposed in WP5 as means to guarantee the SLAs fulfilment.
  • (1) IoT applications and protocols
  • (2) flow types
  • (3) end points
  • (4) traffic matrices

Task 3.4. Traffic modelling and forecasting

• EPUSP, UFABC
• Leader: EPUSP
• Duration: M12-M24
• The goal of this task is to develop traffic modelling and forecasting techniques that enable the implementation of FI traffic generators in Task 3.5 and that can guide dynamic resources assignment techniques that will be proposed in WP5 as means to guarantee the SLAs fulfilment.

Task 3.5. Traffic generation

• EPUSP, UFABC
• Leader: UFABC
• Duration: M18-M30
• The objective of this task is to develop a realistic IoT traffic generator based on the information and traffic models provided by Tasks 3.2 and 3.4 respectively

Work package 4: Short term evolution towards the FI – Leader: UFABC

• Role of the partners involved in the WP:
  • ANSP and ALGAR as network operator partners of ZooNE T -BR will monitor the FI evolution and participate in tasks T4.4, 4.5 and 4.6 that will involve the deployment of solutions in a real infrastructure.

• Requirements and validation
• Algar: 8 Person-months
• Objectives:The general objective of this work Package is to develop a number of technological results that respond to current and upcoming challenges for the Internet Architecture.
• Four sub-objectives:
  • (1) Security and Privacy: any evolution of the current Internet Architecture must develop sound security policies, and must respect privacies of all users to prevent mission creep. The advent of IoT connecting a huge number of small devices to the Internet, will bring novel security threats, which will be very hard to tackle because of the specific nature limited resources of those devices that may endanger security patches.
  • (2) Service Level Agreement: while the Internet was built over a very simple but efficient paradigm, best-effort, future application and services will need to adhere to much more stringent SLA contracts. Inclusion of hard-real time or critical services, for instance, must go beyond current architectures to be implemented safely and efficiently. ZooNE T -BR will develop technologies that will represent a significant step forward in this respect.
  • (3) Network and Transport Protocols: current protocols may be ill-suited for novel services, which may be enabled only by a much higher efficiency on the current infrastructure. ZooNE T -BR will study such developments in order to provide viable solutions for an evolution for the current Internet Architecture.
  • (4) Network Robustness: as more and more services will be based on Internet connectivity, the coming future blackouts can result in much higher loss than today’s ones. Therefore, there’s the stringent need to embed resilience into the design of any sustainable Future Internet Architecture. ZooNE T -BR will work towards this goal by developing proof-of-concepts that will shift current status towards a robust and resilient architecture.

Task 4.1. Future Internet Architecture Evolution Monitor

• ANSP, ALGAR
• Leader: ANSP
• Duration: M2-M36
• This task intends to fine tune the technological solutions developed by the different tasks in WP4. This task will receive as input the work done in WP2 and WP3, and will develop a strategy to address the different challenges that must be resolved in the short-term, prioritising and making sure that the developments will respond to real users needs and will harmonically work together towards a common vision of Future Internet Architecture.

Task 4.2. Session layer security development

• UFABC, ABC
• Leader: UFABC;
• Duration: M2-M36
• This task will provide major contributions to Objective 4.1 and Objective 4.3. Currently, end-to-end application security contexts are tightly coupled with the underlying communication context

This presents at least three major issues:

• • (1) the current security scheme is not flexible - when the underlying communication context changes, which can be easily the case in Future Internet scenarios, including IoT applications, the application security context must adapt to the different situation and respond to it
  • (2) the overhead associated with such coupling is prohibitively expensive over constrained networks such as sensor or cellular networks
  • (3) any attack on the communication context has a direct effect on the application security.

Task 4.3. Infrastructure-less networking

• UFABC, ABC
• No responsibility

Task 4.4. High speed anonymous networks development

• EPUSP, UFABC, ALGAR, ABC
• Leader: UFABC
• Duration: M18-M36
• This task tackles all the work-package objectives. In this task we will address current data transfer limitation in the TOR network.
• We plan to build an experimental (not open to public usage) MIX-net and running the HIxP protocol suite on top of it.

Task 4.5. Packet/Stream aggregator

• UFABC, ANSP, ABC
• No responsibility

Task 4.6. Packet Normalisation

• UFABC, ANSP, ALGAR, ABC
• Leader: UFABC
• Duration: M2-M36
• This task answers to security and privacy , network and transport protocols, and network robustness objectives. In this task we will develop a tool to be deployed on routers allowing packet normalisation beyond classical scrubbing.