Architecture

Architecture Technical Overview

1

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

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

Webinos Architecture

4

TLS

TLS

PZH - Personal Zone Hub – Resides on Server– Logical Entity: 1 PZH per user– Each PZH server can host multiple

PZH’s

PZP - Personal Zone Proxy – Resides locally on the device

– Present on every webinos device

– TLS – Transport Layer Security Secure/Certified connection

between webinos components

Devices Devices

Peter’s Personal Zone John’s Personal Zone

TLS

Server / PZH (Logical Entity)

Server / PZH (Logical Entity)

Personal Zone HubCentral 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

Personal Zone ProxyEvery 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

Device Integration

Architecture Technical Overview

7

JSO

N

Binding

JSO

NBinding

Mes

sagi

ng

Device 2

Device 1JSON-RPCPackages

webinos Device/PZP Architecture

8

PZH

Native Device OS

webinos API

PZPBrowser/ WidgetWeb Runtime

Messaging Manager

Discovery Manager

Context Manager

TLS

Session Manager

Native Discovery Mechanisms

Drivers

Routing

User Data Device

TLS Authentication

HTTPS

WebSocket Certificate Manager Key Storage

RPC Handler/Manager

Messaging queueError recovery

APIs

APIs

APIs

APIs

APIs

RPC

Policy Manager

Sync Manager