Brief overview of the key architectural concepts within webinos Presented by Christian Furhop of the Fraunhofer Institute

1. Architecture
Architecture Technical Overview 1

2. Personal Zone
Basic concepts already exist:
• In a local network, devices often trust each other
implicitly (UPnP/DLNA is quite explicitly based on this)
• Discovery can be achieved with multicast
• Devices that are registered to the same owner often
share the same applications / rights / profiles / settings
(Kindle, Android, iPad/iPod/iPhone)
Architecture Technical Overview 2

3. Personal Zone
defines Personal Zones:
 Devices belong to Personal Zones
 Discovery is 'local' with a Personal Zones
 Discovery requests originating from outside the Personal
Zone are mediated
 Devices outside the Personal Zones are firewalled
 The Personal Zone does not need to match the physical
network
– mobile phones can be included
(which are typically not in the same network as home
electronics)
– the Personal Zone can include non-IP devices (Bluetooth,
ZigBee)
 Devices authenticate themselves to the Personal Zone
(and vice versa)
Architecture Technical Overview 3

4. Webinos Architecture
 PZH - Personal Zone Hub  PZP - Personal Zone Proxy
– Resides on Server – Resides locally on the – TLS – Transport Layer
– Logical Entity: 1 PZH per device Security
user – Present on every webinos  Secure/Certified
– Each PZH server can host device connection between
multiple PZH’s webinos components
Peter: PZH John: PZH
(Personal Zone Hub)  TLS (Personal Zone Hub)
Security Policy Security Policy
Server / PZH Server / PZH
(Logical Entity) (Logical Entity)
 TLS
 TLS
Peter’s Personal Zone John’s Personal Zone
Peter: PZP Peter: PZP
Peter: PZP
Peter: PZP Peter: PZP
John: PZP
(Personal Zone Proxy) (Personal Zone Proxy)
Security Policy Security Policy
Devices Devices
4

5. Personal Zone Hub
Central to a Personal Zone is the Personal Zone Hub (PZH)
The main task of the PZH are:
 User authentication service
 Session creation for messages and synchronization
 Single-sign on point for web services
 Host for webinos web services
 Master repository for context data
 Central repository of policy rules
 Policy enforcement point for remote communication
Architecture Technical Overview 5

6. Personal Zone Proxy
Every device is associated with a Personal Zone Proxy
(PZP)
 Routes all 'Internet' messages to PZH
 Routes 'local' messages to other PZPs
 Can perform PZP to PZP communication for optimisation
reasons
 The PZP acts as a stand-in when devices are
temporarily not connected to the Internet
 Performs functions of PZH when PZH is not accessible
 PZP is stores various information (context information,
event messages) until next sync with PZH is possible
 PZP is responsible for discovery of local bearers
(Bluetooth, ZigBee, NFC)
Architecture Technical Overview 6

7. Device Integration
JSON
Binding
Messaging
Device 1
JSON-RPC
Device 2 Packages
JSON
Binding
Architecture Technical Overview 7

8. webinos Device/PZP
Architecture
PZH
TLS
Browser/ Widget
Web Runtime PZP Session Manager
Context Manager TLS Authenticatio HTTPS
Policy Manager
n
Certificate Manager Key Storage
WebSocket User Data Device
Sync Manager
Messaging Manager
RPC Error recovery Routing Messaging queue
webinos API
RPC Handler/Manager Discovery Manager
APIs
APIs
APIs
APIs
APIs
Native Discovery
Mechanisms
Native Device OS
8 Drivers