Middleware Layer. The same principle of anonymous data handling as was explained for the hardware components is also applied in this layer. Additionally, every XXXXX instance has its own auto generated ID that identifies each instance within multiple Miraculous-Life clients. The XXXXX instance is associated with a specific user at the database level. A separate security mechanism is additionally in place, which is the security framework within the Java Virtual Machine (JVM) itself and an extension provided by the OSGi framework. This security measurement is a general aspect of every Java based program and has therefore no specific impact on the overall security and privacy aspect of the Miraculous-Life system. For this reason, it is not further explained in this document, but for the enthusiastic reader we want to refer to the official OSGi specification for further details [24]. Alongside the XXXXX framework, the Database also resides in this SOA Layer. Only authorized users have access to the Database, and only a subset of those has permissions to actually view the contents of the database tables. The system users (elderly and caregiver) don’t have direct access to the database, but can only interact and make use of it via the services and strictly defined API’s. Furthermore, it was agreed on not encrypting the whole database, as this is quite resources intensive, but instead encrypting the data channel when querying for specific data sets. This ensures that the raw and sensitive data is transferred on a secure channel and cannot be sniffed by 3rd parties.
Middleware Layer. RMW layer is composed of an abstract API (RMW) and its implementation (RMW implementation). This layer provides basic middleware functionality: publish/subscribe, services (request-reply) and serialisation of message types. The upper layers use this middleware API on the micro-ROS library stack. This API abstraction allows hiding implementation and vendor specific details to the user. This abstract API has a default implementation using eProsima’s XRCE protocol implementa- tion, Micro XRCE-DDS. This implementation resides on the rmw_implementation layer. This rmw_implementation layer is responsible for providing discovery as well as inter-process communi- cation optimisation avoiding unnecessary wire interactions. The middleware API provided by RMW layer to the upper layers should be similar to the one produced by its analogous to ROS2.
