During the last weeks the work on WP2 (SDN-microSENSE Architecture, Pilot Preparation and Security & Privacy Requirements) has progressed considerably, culminating in the delivery of Deliverable D2.3, which describes the SDN-microSENSE platform specifications and the architecture. Intensive meetings have been held among the partners involved in order to clarify and progress on the definition of the different functional components of the SDN-microSENSE architecture and its operation. This deliverable is classified as “confidential”, so its content cannot be disseminated outside the consortium. In addition to the architecture specifications, the deliverable explains the architecture itself through 4 different views:
- Structural view, which presents the different functional blocks in the architecture, as well as the main interfaces among them.
- Behavioral view, which describes how the different functional blocks in the Structural View interact with each other.
- Deployment view, which shows how the Structural View can be implemented in practice by means of specific components.
- Topological view, describing where the different components of the architecture can be placed in the Electrical Power and Energy Systems (EPES) infrastructure.
As the project name suggests, the presented architecture is largely based on the SDN technology. In this regard, the document also explains how the different components of the SDN-microSENSE architecture are mapped into to the overall SDN architecture as it is defined from the Open Networking Foundation, describing the working of the different architectural components associated to the four SDN layers: Application, Controller, Data and Management. The overall objective is, of course, to provide enhanced security and resilience to the EPES, focusing on two action areas: the power-grid itself (i.e., the electrical infrastructure) and the data networks associated to this electrical infrastructure. In particular, the architecture makes it possible to deal with security threats (e.g. cyber-attacks) or other unforeseen events that may affect the power supply (e.g. natural phenomena or human error).
This deliverable is based on the functional and non-functional requirements defined in the previous Deliverable D2.2, and in turn, is intended to serve as the basis for the next Deliverable D2.4, where the practical implementation through the different pilots defined in the project will be introduced.