1 / 16

BETaaS Architecture Definition: Enabling Things as a Service Implementation

Explore the top-down BETaaS architecture definition and its main features, functionalities, and interaction examples for efficient Things as a Service deployment. Discover the benefits of instance and gateway perspective architectures, component definitions, and conclusions for enhanced platform capabilities.

kizzy
Télécharger la présentation

BETaaS Architecture Definition: Enabling Things as a Service Implementation

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript


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

  2. Outline • BETaaS Architecture Definition • Architecture Definition Steps • Architecture Main Features • BETaaSFunctionalities • BETaaS Architecture • TaaS Reference Architecture • Instance Perspective Architecture • GW Perspective Architecture • Components Definition Example • Interactions Examples • Conclusions

  3. BETaaSArchitecture Definition Top-Down Approach

  4. BETaaSArchitectureFeatures

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

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

  7. InstancePerspectiveArchitecture Service Service Service * TaaS TaaS TaaS Adaptation Adaptation Adaptation

  8. GW Perspective Architecture ServiceLayer TaaSLayer AdaptationLayer AllLayers

  9. Components Definition Example

  10. ComponentsDefinitionExample

  11. Interactions – Join Instance

  12. Interactions – Get Real-time Data

  13. Conclusions • 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 • Simplifycertainoperations and improvenetworkusage • Increasereliability and performance • The architecture is valid for increasing the capabilities of the platform in the future

  14. Thanks for your attention

  15. BETaaS Star Components

More Related