1. An Architecture For
Collaborative Business Items
ARCS 2007
March 14, 2007
Zurich Till Riedel*, Christian Decker*,
Switzerland Phillip Scholl*, Albert Krohn*,
Michael Beigl**
*TecO, University of Karlsruhe
**IBR, Universität Braunschweig

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
ARCS 2007/ An Architecture for Collaborative Business Items / Till Riedel / 2

3. Outline
I.Virtual and real world coupling
II.Design Criteria
III.CoBIs SOA/Middleware
IV.Real world experiences
ARCS 2007/ An Architecture for Collaborative Business Items / Till Riedel / 3

4. Bridging the Gap
Virtual World
CRUD
PC
Real World
ARCS 2007/ An Architecture for Collaborative Business Items / Till Riedel / 4

5. RFID
Virtual World
CRUD RFID
Real World
ARCS 2007/ An Architecture for Collaborative Business Items / Till Riedel / 5

6. Wireless Sensor Networks
Virtual World
CRUD WSN
Real World
ARCS 2007/ An Architecture for Collaborative Business Items / Till Riedel / 6

7. Collaborative Business Items
Virtual World
Real World
ARCS 2007/ An Architecture for Collaborative Business Items / Till Riedel / 7

8. 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
ARCS 2007/ An Architecture for Collaborative Business Items / Till Riedel / 8

9. Design Descissions
Business Logic Backend
Task
Sensor Network Relocated
Task
Collaborative Business
Items
Business Logic implemented in using specific technologies
Cannot change
Web Services, Corba, JINI, ...
Sensor Networks also have their own optimized protocols
Don‘t want to change
Ressource constraints
ARCS 2007/ An Architecture for Collaborative Business Items / Till Riedel / 9

10. 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 Management
 Reconfigure and deploy Logic
 Discover Functionality in the network
 Monitor Services
ARCS 2007/ An Architecture for Collaborative Business Items / Till Riedel / 10

11. CoBIs Services
Business Logic Backend
Task
Relocated
Sensor Network Service
Task
Service
Service Collaborative Business
Items
Service Oriented
Move away from a node centric view
Abstract from sensor node platforms
Make functionality independent of technology
ARCS 2007/ An Architecture for Collaborative Business Items / Till Riedel / 11

12. BACKEND The CoBIs Gateway Architecture
Business Application
WS
SOA Gateway
WS WS
WS
Service Proxy Factory Service
COBIs Gateway Architecture
Proxy WS
Proxy
UPnP Service UPnP
Proxy
UPnP
Platform Gateway
UPnP UPnP
Service Particle µNode Service Sindrion
Sindrion Service
Service
Proxy Proxy Factory Proxy Factory Proxy Proxy Factory
Proxy Factory Proxy
Proxy
ConCom µNodes Network Protokol Sindrion
UPnP
FRONTEND
Particle Network µNode Network Sindrion Network
ARCS 2007/ An Architecture for Collaborative Business Items / Till Riedel / 12

13. RPC Transformation
Transforming RPC into sensor node messages
Client C UPnP Service Proxy S'
Transformation
Routing
Service performed by the network
Needs additional specifaction (XMLbinary transformation)
ARCS 2007/ An Architecture for Collaborative Business Items / Till Riedel / 13

14. Service Transformation
Particle Message Format
t h
pe eng e
ty l d at
ACL 5 5 4 3 2 1
RPC Transformation Template
(
(
(
ARCS 2007/ An Architecture for Collaborative Business Items / Till Riedel / 14

15. Augmenting Service Description
ARCS 2007/ An Architecture for Collaborative Business Items / Till Riedel / 15

16. Lifecycle Management
CoBIs platform UPnP
ProxyDevice A_1
Node 1 Gateway
Service A *
*
Service A
* *
*
ProxyDevice Info_1
Lifecycle
*
*
Service B Info
* *
* *
ProxyDevice B_1 *
* Injector
*
* Service B *
*
*
*
Info
GatewayDevice
* Lifecycle
* *
*
Deployment
* *
*
ARCS 2007/ An Architecture for Collaborative Business Items / Till Riedel / 16

17. Discovery
A B C D
C_xxx
hello
hello
ping
instantiate
Gateway ?_*
Service A Service B Service C Service D
deploy
ARCS 2007/ An Architecture for Collaborative Business Items / Till Riedel / 17

18. Implementation of Particle UpnP Gateway
GatewayDevice «interface»
UPnpGateway
+ actionPerformed() DeviceFactory
creates + addActionListener()
Timer TemplateExpiration
UPnP stack
creates
pComponents
PacketMultiplexer
ParticleFactory Device
*
DefaultTemplate ParticlePacketSender
1 listen
Service
«interface»
ParticleTemplate «interface»
DeviceTemplate + addActionListener() ActionListener
+ match()
+ parse(pck : ParticlePacket) : boolean
+ packet(obj : Object) listen
TupleTemplate StateVariable
StateVariableChanger
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. )
ARCS 2007/ An Architecture for Collaborative Business Items / Till Riedel / 18

19. Hazardous Goods - Real world trial
 1st trial: Summer 2006
 Storage area @ BP Chemical Plant
 SAP Backend System
Incompatible Goods
Storage Limits
Environmental Monitoring
ARCS 2007/ An Architecture for Collaborative Business Items / Till Riedel / 19

20. Sensor Nodes
 Accommodates the Particle communication board
 Integration and accommodation of sensors
 Actuators for provision of in-situ alerts
 Closed and robust package
IR Location Technology
Particle Computer
(Communication, Processing)
Sensors and actuators Power Supply (AAA,
ARCS 2007/ An Architecture for Collaborative Business Items / Till Riedel / 20 lifetime ~ 1 month)

21. Network setup
20
ARCS 2007/ An Architecture for Collaborative Business Items / Till Riedel / 21

22. Basic responsiveness tests
8
0
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
ARCS 2007/ An Architecture for Collaborative Business Items / Till Riedel / 22

23. Message Load
450
Event delivery rate for prototype:
400
450 events per minute
350
300
suboptimal GENA implementation
250
problems w/ TCP setup times
200
transformation overhead neglectable
150
100
50
0
ARCS 2007/ An Architecture for Collaborative Business Items / Till Riedel / 23

24. 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%
70
60
50
40
30
20
10
7,51 7,51
0
02:00
05:00
07:00
07:30
08:00
10:00
11:00
12:30
13:00
14:00
15:30
16:00
19:00
21:30
22:00
23:30
00:00
00:30
01:00
01:30
02:30
03:00
03:30
04:00
04:30
05:30
06:00
06:30
08:30
09:00
09:30
10:30
11:30
12:00
13:30
14:30
15:00
16:30
17:00
17:30
18:00
18:30
19:30
20:00
20:30
21:00
22:30
23:00
#Alerts #SensorData Average
ARCS 2007/ An Architecture for Collaborative Business Items / Till Riedel / 24

25. Conclusion
Service abstraction applies well to sensor node functionality
Services provided collaboratively by sensor networks
Services Discovery Messaging technology
Interface Descriptions Deployment
 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
ARCS 2007/ An Architecture for Collaborative Business Items / Till Riedel / 25

26. Questions?
See also: www.cobis-online.de
ARCS 2007/ An Architecture for Collaborative Business Items / Till Riedel / 26