WP26 - Reference Architecture / Reference Implementations
|WP Title:||Reference Architecture / Reference Implementations|
|Contributors:||ISEP, VIF, AIT, AVL, CISC, CIT, EAB, TECNALIA, HH, HIOA, INDRA, ITI, JIG.ES, JKU, Klas Telecom, KTH, Wolffia, qplox, SICS, SMARTIO, TU Delft, VTT, TELENOR ASA, UiO, VEMCO SP ZOO|
This work package is in charge of the design of a reference architecture of the secure wireless infrastructure solution to be enforced by the SCOTT communication bubble. These architecture design activities are associated with technology and protocol evaluation, interface description, vulnerability identification/mitigation, middleware design as well as entity and attack modelling. Part of the tasks related to the reference architecture design include distributed cloud integration, autonomous operation, synchronisation of applications supported by different bubbles (cross-domain bubble synchronisation), and multi-metric security and privacy assessment of architecture components. Interface and protocol evaluation are also correlated with standardisation activities that will allow all technology developments across use cases to achieve interoperability, backwards compatibility and efficient integration with the state of the art wireless communication technologies. Standardisation activities will attempt to impact different standardization bodies related to secure wireless short range communications based on the Bubble concept. The proposed architecture will allow for explicit interoperability between different industrial use cases with different underlying standards, security and quality of service requirements. This is in line with the vision of future smart cities and fully connected digital societies. In the end, the objective is to provide reference guidelines for the development or secure wireless architectures with enhanced interoperability, dependability, cross-domain infrastructure reusability and application development. The main objectives of this WP are as follows:
- 1. Review the underlying technologies for each use case individual requirements and architectural patterns to achieve the objective of secure wireless confined transmission inside the bubble.
- 2. Design the infrastructure and the proper hierarchical arrangement of entities and functionalities to enforce interoperable and secure wireless solutions in industrial applications.
- 3. Identify the standardized interfaces relevant to enforce security, dependable and interoperable solutions
- 4. Design the middleware mechanisms needed between different industrial domains with different quality of service, security, and semantic requirements.
- 5. Identify vulnerabilities of the system from the perspective of architecture design and the relevant entities. Based on these results propose countermeasures that minimize risks and threats to the system at different levels of the architecture..
- 6. Provide the different perspectives or views of the architecture that will support the main requirements of the different use cases.
- 7. Include in the architecture infrastructure design a multi-metric security and privacy labelling used in the SHIELD project
- 8. Enable the use of advance applications such as distributed cloud integration, reconfigurability, adaptability, continuous (uninterrupted operation), autonomous operation, and synchronisation of near real time applications.
- 9. Enable the use of heterogeneous transmission technologies including satellite, vehicle to vehicle, vehicle to infrastructure, etc.
- 10. Ensure the design of scalable, dependable, architectural models and implementations*
Partners in WP26
SCOTT-NO contact: Boning Feng
HiOA (5 PM) will contribute with requirements for configuration architectures, starting from the home bubble and extending towards other domains.
Wolffia (4 PM) will contribute with requirements for configuration architectures, starting from the home bubble and extending towards other domains.
SmartIO (2 PM) will contribute to Task 8 Multi level security metrics and privacy labelling for architecture definition
Telenor (4 PM) will contribute with requirements for configuration architectures, starting from the home bubble and extending towards other domains.
UiO (6 PM) will contribute for distributed access control, distributed logic and measurable security to the reference architecture and also address compatibility with the FiWare platform. UiO will also drive standardization activities for the ‘privacy labelling’ developed in WP22.