8. Three Keys
Anyone can do it
Simple to setup
No special knowledge
required
9.
10. Workshop basic goals
Create concrete solutions
Using off the shelf materials
Where anything is remote controllable
via sensors or a mobile phone
11. Three design rules
Easy to install
Easy to expand / extend
Up and running in minutes
12. Means and Materials
Microphones
(Web) cams
Paper & Printers
Mobile phones
Online web services
RoomWare Web Applications
13. Fields
1. Online: Web applications
2. Mobile: RoomWare applications
3. Local: User input via sensors
4. Server: Extending the RoomWare
server
5. Conceptual: Use cases for RoomWare
use
14. 1: Online
1. Identity Broker
2. Visualization of social data
(Flikr, Twitter, .. in Flash / HTML)
3. QR-code reader (Flash)
4. Connection to RoomWare Server
15. 2: Mobile
1. Augmented (web) browser
1. QR-code reader
2. Direct call to RW service
2. QR-code / RoomWare handshake
3. RoomWare Remote control
16. 3: Local (input / sensors)
1. Scratch input
2. Sensors
3. Camera: gestures / fiducials / QR / AR
17. 4: RW Server
1. Installer
2. Bridges
3. Communication / interaction via
Sockets
4. Definition / description of interfaces
5. Config panel
21. A quick flip through
presentation
Basic concepts of RoomWare
22. Basic concepts
Record the moment
Enrich the present *
Connect to others
Connect to your environment
Re-live the past
Discover the future
Basic concepts of RoomWare
46. Identity Brokers
Profile Identity
<XML>
IN Social OUT <identity></identity>
Identifier <identity></identity>
Profile </XML>
Access
Location
Grant
Connect to others
47. Proximity
You Proximity levels
Close Around the Around the block
corner
Connect to your environment
127. RW Server
Identification (inter)action
Data Source
ID Broker Web App
RoomWare Server
Bridge A ID Bridge B
Adapter
ID Reader
Sensors Devices
Enabling the room
144. Identity Brokers
Profile Identity
<XML>
IN Social OUT <identity></identity>
Identifier <identity></identity>
Profile </XML>
Access
Location
Grant
Connecting to others
148. Basic setup
• Identity Broker
• RoomWare Server
• ID Readers (RFID, BT, QR-code)
• (Web) Applications
• Sensors and Devices
• Bridges
The framework
149. Identification (inter)action
Data Source
ID Broker Web App
RoomWare Server
Bridge A ID Bridge B
ID Reader Sensors Devices
The framework
150. Identification (inter)action
Data Source
ID Broker Web App
Pointer to
RoomWare Server
Bridge A ID Bridge B
Adapter
ID Reader
Sensors Devices
The framework
151. Identity Reader
• Is used to identify people in a location
• Can be any device: BlueTooth, RFID, ...
• Can be software: Biometric Face
recognition, QR codes
• Can be [one] to [one] (RFID, QR code)
• Can be [one] to [many] (BlueTooth)
The framework
152. Identity Broker
• Is an external service
• Can be any provider
• Is called by the RoomWare Server
• Translates an abstract number to one
or more (online) identities
The framework
153. Basic ID Broker setup
Profile
[one] [one]
[many] [many]
<XML>
IN OUT <identity></identity>
Identifier Identity
<identity></identity>
</XML>
- QR code - Flickr
- RFID card - Twitter
- BlueTooth ID - FaceBook
- BlueTooth MAC address - LinkedIn
- ... - ...
Identity Broker
154. Protecting Identities
• Basis: distrust + roles (professional/private)
• User defines which social identities are
public (visible for anyone)
• Per location the user sets access grants to
specific social identities
• Each set of grants can be put in a social
profile
Identity Broker
155. Using QR codes
QR-code
• Each of your social profiles can be
represented by a unique QR-code
• Each of these QR-codes is a key
• By showing the QR-code, the user creates
a connection between a social profile and a
location
Identity Broker
156. Using specific identifiers
• Social profiles can also be connected to
specific Identifiers (RFID card, BlueTooth
device, QR-code)
Identity Broker
157. ID Broker: access grant
[many]
Profile [one] Identity
[one] [many]
[many] [many]
<XML>
IN [many] Social OUT <identity></identity>
Identifier <identity></identity>
[many]
Profile </XML>
[one]
[many]
[one] Access
Location [many]
Grant
Identity Broker
159. (Web) Applications
• Run outside RoomWare Server
• Uses external Web Services to create
(data) visualizations related to present
people
• RoomWare Server has pointer to App
• RoomWare server acts as a bridge for
the app to interact with the space
The framework
160. Adapters
• Are pieces of software to communicate
with RoomWare and Sensors and Devices
• Plugs into RoomWare via XML stream or
using Sockets
The framework
163. Bridges
• Pass information from A to B
• Have a limited intelligence
• Have no awareness of what is sent
• Connect (Web) Applictions to Readers,
Sensors and Devices
The framework
164. Identification (inter)action
Data Source
ID Broker Web App
RoomWare Server
Bridge A ID Bridge B
Adapter
ID Reader
Sensors Devices
The framework
165. Conclusion
• RoomWare aggregates Identities and passes
these to (Web) Applications
• Communication is directly between Web
Applications and Devices
• RoomWare Server functions as a bridge
The framework
174. Parts
• Remote calls to RoomWare server
• Webinterface in Flash / Ajax / HTML
• Communication via HTTP POST /
Sockets
• Security via handshake / pairing
The web interface
175. Local Web
User ID
ID Reader
ID Broker
RW Server Identities
Web App
The web interface
176. Local Web App Web Client
RW Conn
Event
User actions
handler
RW Server
Data Retr.
Visualization
Send
Instructions Room
Sensors
Adapter
Devices
The web interface
180. Basic assumptions #1
• RFID / BlueTooth: Preferred Identifiers
• QR-code = easy to copy = “unsafe”
• QR-code = identifier = easy to produce
Authentication process
181. ID Broker + QR-code
Create ID Broker
account
Account ID
Identity
Print out
Authentication process
182. RFID / BlueTooth
• Using QR-code to link RFID / BT to my
Identity
Authentication process
183. Register RFID | BT
ID Reader Handler
√ Registered
1 QR-code QR + RFID
Application
reader QR + BTID
X Unregistered 3.
2.a RFID Register
Reader
RoomWare
Server
2.b BlueTooth ID Broker
Reader
RFID / BlueTooth
184. Register Process
ID Reader Application
√ Registered
1 Read Show identity
QR-code based on QR-code
X Unregistered
2 Read [xxID] “Please confirm”
?
Feedback “Register [xxID]
3 ID Broker failed | success”
RFID / BlueTooth
185. Use RFID | BT
ID Reader Handler
√ Registered
1.a QR-code Application 3: visualiza-
reader tions
√ Registered
1.b RFID
ID Broker
Reader
RoomWare
Server
1.c BlueTooth
Reader 2: Social
Identities
RFID / BlueTooth
186. Possible Scenarios
• Single ID Broker: I register once. Every
venue will recognize me
• Multiple ID Brokers: At each new
venue I do basic registration process. My
[xxID] will be locally stored & linked to
specific broker
• Central IDB Switch: All RW Servers
call Central IDB Switch. Stored is
[xxID] + link to “Personal ID Broker”
RFID / BlueTooth
222. Ambient
Service
Basic Setup
“Open ID” Online
DataCloud
connector services
Server Server
reciever reciever
item ID
You item ID
Feed back
Web from venue
connection