1. Building the Environment for the Things as a Service GWS 2014 - Aalborg Fco. Javier Nieto (ATOS)

2. 2 BETaaS Architecture Definition – Architecture Definition Steps – Architecture Main Features – BETaaS Functionalities BETaaS Architecture – TaaS Reference Architecture – Instance Perspective Architecture – GW Perspective Architecture – Components Definition Example – Interactions Examples ConclusionsOutline

3. 3 BETaaS Architecture Definition Identify Functionalities Identify Main Components Define APIs Detail Components and Interactions Top-Down Approach

4. 4 BETaaS Architecture Features Use Several Inputs Conceptual Model Requirements Capabilities Keep Layered Model Service Layer Components TaaS Layer Components Adaptation Layer Components Enable Modularity Different GWs configuration Different GWs capabilities Agile & Reliable Operation P2P based organization Limit centralized operations

5. 5 BETaaS Platform Functionalities Services and App. Management Resources Management & Discovery Things Access Adaptation Big Data Management Context Management Security ServicesQoS Services Dependability

6. 6 One TaaS (distributed) instance per BETaaS instance One Adaptation Layer instance per BETaaS gateway TaaS Reference Architecture BETaaS GW 1 M2M implementation (ETSI M2M) M2M implementation (CoAP) M2M implementation (…) ETSI M2M adaptation layer CoAP adaptation layer … Adaptation layer TaaS local agent BETaaS GW 2BETaaS GW 3 BETaaS instance TaaS local agent BETaaS TaaS PHY layer Logical layer Serice layer

7. 7 Instance Perspective Architecture Service TaaS Adaptation Service TaaS Adaptation Service TaaS Adaptation *

8. 8 GW Perspective Architecture Service Layer TaaS Layer Adaptation Layer All Layers

9. 9 Components Definition Example

10. 10 Components Definition Example

11. 11 Interactions – Join Instance

12. 12 Interactions – Get Real-time Data

13. 13Conclusions The architecture has been useful for implementing the components, even using OSGi Layers differentiation is still clear and it enables flexibility and evolution  Adopt several M2M frameworks From the BETaaS Instance perspective, we can use a mix of Star and P2P architecture  Distributed & Centralized approach – Simplify certain operations and improve network usage – Increase reliability and performance The architecture is valid for increasing the capabilities of the platform in the future

14. 14

15. Thanks for your attention

16. 16 BETaaS Star Components