The main objectives of WP2 are to define a resilient architecture and to develop a range of middleware solutions (i.e. algorithms, protocols, services) for resilience to be applied in the design of highly available, reliable and trustworthy networking solutions. This deliverable presents the HIDENETS resilient architecture (final version), which extends and refines the preliminary version presented in Deliverable D2.1.1. The deliverable builds on results from WP1, the definition of a set of applications and use cases, and provides a perspective of the middleware services that are considered fundamental to address the dependability requirements of those applications. During the course of the project, the set of considered services has slightly changed with respect to the preliminary proposal, reflecting the experience and feedback obtained from other activities within the project. The deliverable presents the software architecture of a HIDENETS node, in which the several services are organized according to a number of factors like their purpose, their function within the communication stack or their criticality/specificity for resilience. A fundamental characteristic of the HIDENETS architecture is that it is a hybrid architecture, which allows differentiating between two classes of services, a class including timeliness and trustworthiness oracles, and a class of so called complex resilience services. In this deliverable we explain the motivation for using such hybrid architecture, the benefits that it may bring for achieving improved dependability and the impact on the feasibility of practical systems exhibiting such hybrid nature. The deliverable provides descriptions for all the services considered in the HIDENETS node software architecture. However, in the case of communication related services, these are short descriptions, which are included for the sake of completeness. The remaining descriptions, for the considered oracle and complex resilience services, provide all the details and include lessons learnt relative to the design and interface specification, in addition to information already provided in the preliminary version of the deliverable. While the communication related services are being developed in the scope of WP3, the remaining services are the focus of the work being carried on in the scope of tasks 2.2 and 2.3 of WP2. The deliverable also considers high-level interfacing aspects, by providing a discussion about the possibility of using existing Service Availability Forum standard interfaces within HIDENETS, in particular discussing possibly necessary extensions to those interfaces in order to accommodate specific HIDENETS services suited for ad-hoc domains. To conclude, the deliverable takes two of the example applications considered in HIDENETS to illustrate the use of the proposed architecture and HIDENETS services. The section discusses dependability aspects, explaining the purpose and relevance of each involved service to improve the resilience, availability and performance of the example applications.

Dissemination Level PU Public X PP Restricted to other programme participants (including the Commission Services) RE Restricted to a group specified by the consortium (including the Commission Services) CO Confidential, only for members of the consortium (including the Commission Services) Abstract: This document provides the starting point for the development of dependability solutions in the HIDENETS project with the following contents: (1) A conceptual framework is defined that contains the relevant terminology, threats and general requirements. This framework is a HIDENETS relevant subset of existing state-of-the-art views in the scientific dependability community. Furthermore, the dependability framework contains a first list of relevant functionalities in the communication and middleware level, which will act as input for the architectural discussions in HIDENETS work packages (WPs) 2 and 3. (2) A set of 17 applications with HIDENETS relevance is identified and their corresponding dependability requirements are derived. These applications belong mostly to the class of car-to-car and car-to-infrastructure services and have been selected due to their different types of dependability needs. (3) The applications have been grouped in six HIDENETS use cases, each consisting of a set of applications. The use cases will be the basis for the development of the dependability solutions in all other WPs. Together with a description of each use-case, application-specific architectural aspects are identified and corresponding failure modes and challenges are listed. (4) The business impact of dependability solutions for these use cases is analysed. (5) A preliminary definition of a HIDENETS reference model is provided, which contains high-level architectural assumptions. This HIDENETS reference model will be further developed in the course of the HIDENETS projects in close cooperation with the other WPs, which is the reason why the preliminary version also contains a collection of potential contributions from other WPs that shall be developed and investigated in the course of the HIDENETS project. In summary, the identified use-cases and their requirements clearly show the large number of dependability related challenges. First steps towards technical solutions have been made in this report in the preliminary reference model, whereas the other work-packages have started in the meanwhile to develop such solutions further based on 'middleware technology' (WP2), 'communication protocols' (WP3), 'quantitative analysis methodology' (WP4), and 'design and testing methodology' (WP5). Infotainment and work with highly mobile terminals use case – Alternative technologies 67 5.3.2.2 Infotainment and work with highly mobile terminals use case – costs and benefits .. [39] …

Dissemination Level PU Public X PP Restricted to other programme participants (including the Commission Services) RE Restricted to a group specified by the consortium (including the Commission Services) CO Confidential, only for members of the consortium (including the Commission Services) Abstract: Resilient topologies and routing are among the important topics that were addressed within the HIDENETS project and have been the focus of task 1 of Work Package 3 'Resilient Communication'. This document provides the results of the work in this area. The document has the following content: (1) The HIDENETS network architecture is described, introducing the relevant terminology and the use cases that are of specific interest for this task. (2) The HIDENETS node software architecture is described. This architecture is developed jointly within the Work Packages 2 and 3. The focus here is on the blocks that have specific relevance for resilient topologies and routing and that has been handled within this task. (3) Resilience is about managing failures and implementing mechanisms that make the system resilient and robust despite possible occurrences of failures. We have therefore analyzed possible faults, errors and failures, and their consequences with respect to the HIDENETS scenarios. The result of this fault analysis is presented. The focus has been on timing faults and value faults and the causes of such faults. We classify the faults that are most relevant for the communication layer and give the motivation for addressing these faults by developing the methods further described in this deliverable (see below). This is done with emphasis on the methods ability to enhance the resilience and dependability of the network. (4) Finally these more specific research topics that have been addressed in this task by extensive theoretical studies are described and the results are presented. This is divided into the areas 'multi-channel multi-radio architecture', 'resilience in stand-alone ad-hoc networks' and 'resilience in accessing infrastructure networks'. Using multiple frequency channels improves communication level properties, especially capacity. Using multiple radios per node also allows for using multiple channels without any synchronisation between nodes. Multiple radios can also be used for increased redundancy both in ad-hoc networks and in access to infrastructure (multihoming). Resilience in stand-alone ad-hoc networks aims at making the network more resilient by increasing the redundancy and decreasing the signalling / broadcasting overhead. This will improve the connectivity and reduce the probability of contention. Resilience in accessing the infrastructure aims at increasing the …