ZooNet

Participação Empresa

• Coordenador: José Roberto Amazonas - EPUSP

• 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.

• ALGAR is a commercial telecom operator and will provide the infrastructure to perform the stress test and to develop and deploy the short term FI solutions prototypes and use cases applications.
• It will contribute decisively to WP3 and WP6.

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.

Work package 5: Long term path towards the FI – Leader: EPUSP

• Role of the partners involved in the WP:
  • ALGAR will participate in T5.2, 5.3, 5.4 providing the following specific contributions: new FI routing protocols management proposal (T5.2); fulfilment of SLA requirements by means of specific assignment techniques; evaluation and validation related to SLA fulfilment in the FI (T5.4); and active participation to FI workshops (T5.5).

• Requirements and validation
• Algar: 20 Person-months
• Objectives: The general objective of this WP is to identify the most promising evolutionary and revolutionary paths towards a FI architecture based on ongoing IoT efforts.
  • This WP will develop the ZooNE T -BR vision of FI architecture, components and mechanisms to deal with future applications when several kind of different traffic have to share the same medium.
  • A challenging proposition is to identify an approach that will allow not only to handle the diverse range of traffic types of today but, also, to that of applications to come.

• Set of targets, which arise directly from the outcomes of WP3 (traffic analysis):
  • (i) identify the limitations of the current Internet, with particular emphasis on its limited ability to deal with IoT traffic
  • (ii) identify long-term requirements for the Future Internet Architecture, with particular attention to the newly emerging traffic types and to the ability to deal with the future applications that are not yet in sight
  • (iii) develop an IoT-compatible Internet model to enable realistic network simulations and comparison of technological choices related to network and transport protocols, SLA fulfilment, network robustness, mobility, privacy, trust and security
  • (iv) evaluate the most prominent FI architectures currently in development and exert an influence to adequately distil the ZooNE T -BR approach in the forms of specific recommendations (including standardisations bodies) and guidelines towards a common FI architecture
  • (v) promote the development of proof of concept solutions to selected problems, particularly in extreme IoT scenarios (high-density, high-interference, low energy availability).

Task 5.1. Identification of current Internet’s limitation and the FI requirements based on obtained traffic data

• EPUSP, ANSP
• No responsibility

Task 5.2. Assessment of known proposed FI architectures and its suitability for overcoming the traffic challenges.

• UFABC, ALGAR
• Leader: UFABC
  • Duration: M2-M18
• The work will also identify the main building blocks of FI architectures starting from the exhaustively surveyed FI architectures and the requirements defined by the traffic analysis; the path to the proposed architecture will be built upon the identification of the blocks of current FI proposals that also support the requirements of the IoT traffic.

Task 5.3. Architecture design (blocks) recommendations for the FI architecture

• EPUSP, UFABC, ANSP, ALGAR
• Leader: EPUSP;
  • Duration: M7-M24
• A set of recommendations for a compliant FI architecture will be proposed as well as the path to follow in order to enable its swift-footed implementation

Task 5.4. Initial steps on evaluation and validation

• EPUSP, UFABC, ANSP, ALGAR
• Leader: UFABC;;
  • Duration: M12-M30
• A collection of methods, procedures and rules (including the implementation) will be defined in order to assess the essential problems in the design of the FI, including the metrics and KPIs that will be specified allowing to evaluate the degree of accomplishment of the WP objectives.
• The first sub-task is the definition of a road-map for the evaluation and validation defined work.
• Three major points of view are considered:
  • (1) A scalability and performance analysis will be addressed in order to evaluate and validate the selected use cases by identifying the basic blocks or functions which may impose scalability restrictions. Once critical basic functions are identified, a first scalability analysis will be carried out for some of them in order to assess their impact in the real FI, and designing a complete evaluation plan to be implemented in the future.
  • (2) Evaluation and validation related to SLA fulfilment in the FI. This analysis will mainly perform an adjustment of the SLA guarantees taking into account the defined KPIs in the chosen use cases. Similarly, a first analysis of the SLA degree of accomplishment based on the defined metrics will be carried out. The output of the analysis will show the comparison between the obtained results in the proposed FI architecture and the accomplishment of the SLA in the current Internet architecture.
  • (3) Evaluation and validation related to network robustness in the FI. Robustness metrics were partially proposed in the past using graph theory.

Task 5.5. Research workshops

• EPUSP, UFABC, ANSP, ALGAR
• Leader: ANSP
  • Duration: M6-M36
• During this task, three research workshops will be organised.

Work package 6: Stress test and prototype deployment – Leader: ANSP

• Role of the partners involved in the WP:
  • ANSP and ALGAR are the infrastructure providers and will participate in all tasks but T6.2. They will perform all practical deployments and characterisations.

ANSP will lead the whole WP, T6.1 and 6.3.

• Requirements and validation
• Algar: 20 Person-months
• Main Objectives:
  • (1) implementing the monitoring units to enable traffic data gathering, and forwarding it to WP3 where shall be measured and analysed to determine its behaviour and profile which will be used as baseline for later testing
  • (2) performing the stress-tests to identify the current Internet limitations when submitted to its legacy traffic added to IoT generated traffic, and forward the results to WP3, WP4 nd WP5; (3) deploy and stress test the specified short term FI solutions prototypes, and provide feedback to WP4
  • (4) develop, deploy and test the use case applications specified in WP2 that will be used to validated the short term FI solutions proposed in WP4 in terms of security and privacy, scalability, network robustness and SLA fulfilment.

Task 6.1. Definition of the testing methodology

• ANSP, ALGAR
• Leader: ANSP
• Duration: M2 - M6
• In this task a detailed testing methodology will be established, defining for the various flow types the parameters to be measured before and after the deployment of the short term FI solutions developed in WP4. The results from both set of measurements will be compared.
  • The measurements will be assembled from existing and new monitoring systems to be installed on the ANSP’s and ALGAR’s networks.

Task 6.2. Creation of “IoT prototype entities” and deployment of short term FI prototypes

• EPUSP, PER
• Leader: EPUSP
• Duration: M3 - M30
• In this task three kinds of “IoT prototype entities” will be created:
  • (1) “IoT endpoint entity”
  • (2) “IoT proxy entity”
  • (3) “IoT application entity”.

Task 6.3. Feeding the measurement points

• EPUSP, ANSP, ALGAR, PER
• Leader: ANSP;
• Duration: M4 - M8
• This task will provide the connection of the “IoT prototype entities” to the adequate points of the ANSP’s and ALGAR’s infrastructure
  • The “IoT endpoint entities” will be connected to mobile and access networks, will have different capacities offered to them and will use symmetrical and asymmetrical links
  • The “IoT proxy entities” will be connected to the network core, preferably between the transport and the network layers.
  • The “IoT application entities” will be deployed on several datacentre environments (physical and virtual), located within different AS networks

Task 6.4. Traffic measurements

• UFABC, ANSP, ALGAR
• Leader: UFABC
• Duration: M3 - M36
• In this task the practical traffic measurements will be carried out. The task extends practically during the whole duration of the project with different degrees of activity.
• After a period of lower activity the measurements will restart to evaluate the short term FI solutions developed in the WP4 and
  • deployed on the ANSP’s and ALGAR’s infrastructure submitted to the traffic of use cases applications specified in WP2 and developed in this WP.

Task 6.5. Determination of the [access, transport, core] network impact

• UFABC, ANSP, ALGAR
• Leader: UFABC
• Duration: M12 - M33
• In this task it will be evaluated the impact of the network impact on the traffic flows considering in detail the access, transport and core network technologies characteristics.
  • Access network:
    • This sub-task will explore from mobile access networks of various generations up to various fixed network solutions
    • It will observe the impact of inherent delay and symmetric/asymmetric characteristics of the access transmission medium, both in flows between IoT entities and from IoT entities to the cloud-based (Internet-based) data processing and storage systems.
    • It will determine whether QoS mechanisms in the access network and their application to certain user traffic flows can impact their performance
    • It will also determine if there are effects of various THP and QCI classification schemes in 3G and 4G networks to see if changing this classification could improve the overall

performance of the traffic flows of interest.

• • Transport network:
    • It will include applying QoS policies to endpoint entities generated traffic opposed to today’s typical best-effort classification of Internet user traffic.
    • It will observe the traffic behaviour after the implementation of short term FI solutions developed in WP4 and determine the improvements that can be achieved and differentiate

such improvements between the aggregated and endpoints traffic.

• • Core network:
    • It will be monitored the communication between “IoT entities prototypes” located in different segments of Internet, encompassing a wide range of physical and ASPath distances
    • It will pay attention to the transfer of massive data transfer between datacentres in the cloud.

Task 6.6. Identification of IPv4 and IPv6 implementations performances differences

• EPUSP, UFABC, ANSP, ALGAR
• Leader: EPUSP
• Duration: M15 - M33
• in this task we will investigate the difference in performance, scalability and security between NAT-ed endpoints in IPv6 and publicly visible endpoints in IPv4 implementations.

Work package 7: Dissemination, impact creation and exploitation – Leader: UFABC

• Role of the partners involved in the WP:
  • ALGAR is a commercial network operator and will lead the training activities in T7.2. It will also have an active role in T7.1, 7.3 and 7.6.

• Requirements and validation
• Algar: 9 Person-months
• Main Objectives:
  • The general objective of this work Package is to organise in a coherent way the activities leading to maximise impact for the overall project. To achieve this goal, this WP will have six sub-objectives:
    • High level scientific results
    • Academic results
    • Contribution to Standards
    • Creation of an active Future Internet Expert Group
    • Development of a sustainable update and upgrade plan
    • Wide dissemination of results

Task 7.1. Market & (Socio-)Technical Analysis

• EPUSP, ANSP, ALGAR
• Leader: EPUSP;
• Duration: M1-M48
• This task will monitor the current market trends related to Future Internet technologies, collecting and analysing specific market-oriented information that could be used as feedback in specification and implementation activities.
• This task will also drive the exploitation strategy of the project.
  • will take care of elaborating an economical and social analysis for a sustainable deployment plan for future developments of internet-related technologies.

Task 7.2. Training & Technology Transfer

• UFABC, ANSP, ALGAR
• Leader: ALGAR
• Duration: M1-M48
• Internal training:
  • Aimed at employees of the project partners, with no direct involvement in the project but interested in adopting, exploiting and taking up the project results, either from the technological or from the marketing points of view. Internal training will be short (max. 1 day) and organised at the partners’ locations. These actions will take place starting from the 2nd year.
• External training:
  • Involve 3rd party entities with the clear goal of foster the adoption of ZooNE T -BR developments and approach and develop new solutions based on our project’s results. These events will be possibly co-located with existing events (such as fairs and expos) and project events. The specific content of the various events will be defined according to the expected audience, and in general the format will consist of a first informative session (1/2 day, targeting managers and decision makers) and an associated in-depth or ”hands-on” continuation for more technical topics. These events will mainly take place during the second half of ZooNE T -BR when we will be able to provide significant results. Lecture materials will be collected and placed in a specific

section of the web site, available to the general public.

Task 7.3. Large Scale dissemination

• EPUSP, UFABC, ANSP, ALGAR
• Leader: UFABC;
• Duration: M1-M48
• This task will develop a strategy to provide the largest possible dissemination to the project results, considering the budget limitations.
  • Will also be in charge of the writing and editing of the book.

Task 7.4. High level scientific publications

• EPUSP, UFABC
• Leader: UFABC
• Duration: M1-M48
• The purpose of this task is to organise the writing of high-level scientific papers. Most WP will have an output of high scientific value, and papers will be written targeting journals and tier-1 conferences.

Task 7.5. Open Source Software Release

• UFABC
• Leader: UFABC
• Duration: M1-M48
• The

purpose of this task is to organise the proper release of these software advances, publishing it in different portals, preparing different releases and engaging a wide community to use them.

Task 7.6. Contribution to Standard

• ANSP, ALGAR
• Leader: ANSP
• Duration: M1-M48
• This task aims at increasing ZooNE T -BR impact through the development of international collaboration aiming at initiating industrial standardisation activities; it will support existing standardisation bodies, such as IETF, ITU-T and ETSI, to integrate innovative concepts and solutions developed within ZooNE T -BR in existing working, study and focus groups and. Standardisation will enable easier integration and seamless communication between the various systems and sectors that ZooNE T -BR will interact with.

Task 7.7. Future Internet Expert Group creatio

• EPUSP, UFABC, ANSP
• Leader: EPUSP
• Duration: M1-M48
• this task will have the objective of the operations in organising meetings, follow-ups, and contacting the most relevant institutions not only in Europe but also in different parts of the world.