Building the Environment forthe Things as a Service

GWS 2014 - AalborgFco. Javier Nieto (ATOS)

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

• Conclusions

Outline

3

BETaaS Architecture Definition

Identify Functionalities

Identify Main Components

Define APIs

Detail Components and Interactions

Top-Down Approach

4

BETaaS Architecture Features

Use Several Inputs

Conceptual ModelRequirementsCapabilities

Keep Layered Model

Service Layer ComponentsTaaS Layer Components

Adaptation Layer Components

Enable Modularity

Different GWs configurationDifferent GWs capabilities

Agile & Reliable

Operation

P2P based organizationLimit centralized operations

5

BETaaS Platform FunctionalitiesServices and App.

Management

Resources Management &

Discovery

Things Access Adaptation

Big Data Management

Context Management

Security Services QoS Services

Dependability

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 M2Madaptation layer

CoAPadaptation layer

…Adaptation layer

TaaS local agent

BETaaS GW 2 BETaaS GW 3

BETaaS instance

TaaS local agent TaaS local agent

TaaS local agentBETaaS BETaaS BETaaS

TaaS

PHY

laye

rLo

gica

l lay

erSe

rice

laye

r

7

Instance Perspective Architecture

ServiceTaaS

Adaptation

ServiceTaaS

AdaptationService

TaaSAdaptation

*

8

GW Perspective Architecture

Service LayerTaaS LayerAdaptation LayerAll Layers

9

Components Definition Example

10

Components Definition Example

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– 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

Thanks for your attention

16

BETaaS Star Components