Architecture for Collaborative Business Items

An Architecture For Collaborative Business Items

ARCS 2007March 14, 2007ZurichSwitzerland

Till Riedel*, Christian Decker*, Phillip Scholl*, Albert Krohn*, Michael Beigl***TecO, University of Karlsruhe**IBR, Universität Braunschweig

ARCS 2007/ An Architecture for Collaborative Business Items / Till Riedel / 2

Real World Interfaces

Business Logic describes the real world processes in a virtual representation

Interfaces needed to couple real and virtual world

Aim: integrate WSN into business logic

Problems: Consistency Scalability Manageability

Solution: integrate business logic into WSN

Approach: offering service interfaces to WSN functionality


Outline

I.Virtual and real world coupling

II.Design Criteria

III.CoBIs SOA/Middleware

IV.Real world experiences


Bridging the Gap

Virtual World

CRUD

PC

Real World


RFID

Virtual World

RFID

Real World

CRUD


Wireless Sensor Networks

Virtual World

WSN

Real World

CRUD


Collaborative Business Items

Virtual World

Real World


Example: Hazardous Goods

SAP Environment Health and Safety (EH&S)

Storage Regulations Incompatibility Absolute volume limit Temperature / Environmental constraints

Requires continuous monitoring

Local action without backend system

Push logic to the item

Communicate to Backend system alarms

Storage Business Logic deployed to sensor network


Design Descissions

Business Logic implemented in using specific technologiesCannot changeWeb Services, Corba, JINI, ...

Sensor Networks also have their own optimized protocolsDon‘t want to changeRessource constraints

Task

Relocated Task


Business Logic Backend

Sensor Network


Design Criteria

Service interfaces Standardization Integration into ERP systems Portability Typing Documentation

Addressing Proprietary routing and MAC protocols Hide details from client Semantic addressing (item,location vs. ID)

Lifecycle ManagementReconfigure and deploy LogicDiscover Functionality in the networkMonitor Services


CoBIs Services

Service Oriented

Move away from a node centric view

Abstract from sensor node platforms

Make functionality independent of technology

Task

Relocated Task


Business Logic Backend

Sensor Network

Service

Service

Service


The CoBIs Gateway Architecture

Sindrion

Business ApplicationWS

BA

CK

END

SOA

Gat

eway

Plat

form

Gat

eway

FRO

NTE

ND

WS

ServiceProxyUPnP

ConCom

Particle Network

UPnPServiceProxy

WSProxy Factory

ParticleProxy Factory

CO

BIs

Gat

eway

Arc

hite

ctur

e

µNodes Network Protokol

µNode Network

µNodeProxy Factory

Sindrion Network

SindrionProxy Factory

SindrionProxy Factory

WS

ServiceProxyUPnP

WSServiceProxyUPnP

ServiceProxy

ServiceProxy

UPnPServiceProxy

UPnP


RPC Transformation

Transforming RPC into sensor node messages

Service performed by the network

Needs additional specifaction (XMLbinary transformation)

Client C Service Proxy S'UPnPTransformation

Routing


Service Transformation

ACL 5 5 4 3 2 1

type

length

date

((

(

Particle Message Format

RPC Transformation Template


Augmenting Service Description


Lifecycle Management

CoBIs platform

Node 1

Service A

Gateway

Service B

Injector

ProxyDevice A_1

Service A

ProxyDevice B_1

Lifecycle

Service B

Lifecycle

ProxyDevice Info_1

Info

UPnP

InfoGatewayDevice

Deployment

* *

*

*

*

*

*

*

*

*

*

*

*

*

* *

* *

* *

*

*

*

*

*

*


Discovery

Gateway

Ahe

llo

Bpi

ng

hello

C

C_x

xx

D

Service A Service B Service C Service D

?_*

depl

oy

inst

antia

te


Implementation of Particle UpnP Gateway

modularized filter system / UPnP* stack

portable architecture

Java* prototype(* Java is a trademark of Sun Microsystems, UPnP is a trademark of the UPnP Implementers Corporation. )

UPnpGateway GatewayDevice+ actionPerformed()

«interface»DeviceFactory

+ addActionListener()

ParticleFactory

pComponentsPacketMultiplexer

DeviceTemplate

TupleTemplate

«interface»ParticleTemplate

+ addActionListener()+ match()+ parse(pck : ParticlePacket) : boolean+ packet(obj : Object)

DefaultTemplate

UPnP stack

Service

Device

StateVariable

«interface»ActionListener

StateVariableChanger

ParticlePacketSender

TemplateExpirationTimer

creates

*

1 listen

listen

creates


Hazardous Goods - Real world trial

1st trial: Summer 2006 Storage area @ BP Chemical Plant SAP Backend System

Incompatible GoodsStorage LimitsEnvironmental Monitoring


Sensor Nodes

Accommodates the Particle communication board

Integration and accommodation of sensors

Actuators for provision of in-situ alerts

Closed and robust package

Particle Computer (Communication, Processing)

Sensors and actuators Power Supply (AAA, lifetime ~ 1 month)

IR Location Technology


Network setup

20


Basic responsiveness tests

0

8

13:38:56 13:39:39 13:40:22 13:41:05 13:41:48 13:42:32 13:43:15 13:43:58 13:44:41

Particle node 1 Particle node 2 Particle node 3


Message Load

0

50

100

150

200

250

300

350

400

450 Event delivery rate for prototype:

450 events per minute

suboptimal GENA implementation

problems w/ TCP setup times

transformation overhead neglectable


Second Trial December 2006

Number of Messages at the Back-End Total: ~ 162’000 Trial 1:560’000 Average: 7 / minute (normal state) Trial 1: 20

30 / minute (alerted state) Trial 1: 100 Peak: 210 / minute Trial 1: 450

Filtering at Gateway reduced number of messages by ~60%

7,517,51

0

10

20

30

40

50

60

70

00

:00

00

:30

01

:00

01

:30

02

:00

02

:30

03

:00

03

:30

04

:00

04

:30

05

:00

05

:30

06

:00

06

:30

07

:00

07

:30

08

:00

08

:30

09

:00

09

:30

10

:00

10

:30

11

:00

11

:30

12

:00

12

:30

13

:00

13

:30

14

:00

14

:30

15

:00

15

:30

16

:00

16

:30

17

:00

17

:30

18

:00

18

:30

19

:00

19

:30

20

:00

20

:30

21

:00

21

:30

22

:00

22

:30

23

:00

23

:30

#Alerts #SensorData Average


ConclusionService abstraction applies well to sensor node functionality

Services provided collaboratively by sensor networks

Services

Middleware layer provides standardized SOA interface to business logic

Integrated 3 different WSN platform w/ SAP Backend systems

High portability due to message level abstraction

Both backend and frontend unchanged

DiscoveryInterface Descriptions

Messaging technologyDeployment


Questions?See also: www.cobis-online.de