In touch with smart devices (droidcon)

In Touch with Smart Devices
The future is connected.

Masanori Fujita
Zühlke Engineering GmbH

Slide 1
March 2012

Masanori Fujita

© Zühlke 2012

What about Android@Home?

• Android@Home announced at
Google I/O in May 2011
• Vision: “think of your entire
home as an accessory”
– Control lighting
– Collect sensor data
– Play media

• new wireless protocol to
communicate with accessories
• so far, no updates on this

In Touch with Smart Devices | Masanori Fujita March 2012 Slide 2 © Zühlke 2012

• Lighting
• Heating system
• Washing Machine
• Dish washer
• Weather sensors
• Door bell
• Audio & Video

Supported interfaces types

GSM/3G

USB WiFi

NFC Bluetooth


Traditional Roles

Accessory

Master Device

Accessory

• PCs • Input Devices
• Mass Storage
• Printer
• Camera
• MP3 Players
• Smartphones


New Roles

Accessory

Master Device

Accessory

• PCs • Input Devices
• Smartphones • Mass Storage
• Printer
• Camera
• MP3 Players
• Smartphones


USB Host Mode

• USB host is required to provide
500mA current
• USB On-the-Go is used to act as
limited USB host
• USB Host Mode is optional
Accessory

Accessory


Open Accessory
Development Kit

USB Host USB Slave

Android
Phone

Dev. Machine

ADK Initialization Process

Wait for Android Request USB
device to connect device descriptor

Accessory
Power On Android device
connected
Request
accessory support
Android Device

Send
no OEM’s vendor
and product ID

Wait for accessory
to connect

Power On Device in accessory mode?
Send
yes Google’s vendor
and product ID


Android: Many form-factors

Samsung Galaxy S II

HTC Velocity 4G

Motorola Pro+


USB Support in Android

Oct-11
4.0

Feb-11 May-11 Jul-11
3.0 3.1 3.2
Oct 09 Jan 10 May 10 Dec-10
2.0 2.1 2.2 2.3
Sep-08 Feb-09 Apr 09 Sep-09
1.0 1.1 1.5 1.6

Sep 2008 Mar 2012

ADK (since 3.1 + 2.3.4)
USB Host Mode (since 3.1)


• Reliable and high speed
connection
• Easy handling for user and
developer
• Power supply and form-
factors might be an issue for
accessory designers

Which Bluetooth profiles does your phone
support?

SPP HDP

DUN

SIM

HID
FAX
HFP

OPP
OPP
HSP


The built-in Bluetooth Stack

Android API Socket
(android.bluetooth.*)

Serial Port Profile (SPP)
Virtual serial port
Service Discovery
RFCOMM Protocol

L2CAP

Link Manager Layer
Bluetooth
Baseband
Controller
Radio Layer


What the API offers…

• Scan for devices
• Listen for incoming RFCOMM connections
• Establish RFCOMM connections
• Communicate with HFP, HSP, HDP, A2DP devices
• Implement new Bluetooth profiles


Not all profiles use RFCOMM
Example: HID

Human Interface Device Profile

Service Discovery
Protocol

L2CAP

Link Manager Layer
Bluetooth
Baseband
Controller
Radio Layer


You should only rely on serial
communication, unless…

• you can implement a profile in Java that solely builds
upon RFCOMM and SDP.
• you have a defined set of target devices
– accessing the native BT driver
– create native extensions
– add profiles to API
– compile custom ROM

• Google defines other profiles to be mandatory for
Android devices and offer them as API


• Supported by most devices
• Handling might be tricky for
user
• Only serial communication is
guaranteed

Reading and writing tags

• Support for different
types of tags
– NFC Forum Type 1-4
– Mifare *

• API features
– Reacting on tag
discovery
– Reading and writing
passive tag with serial
NDEF messages passive number, deployment
– Sector level I/O access
date, date of last
inspection etc.
active

Card emulation
providing live status
information, allow
device settings


Beaming to and from your smart device

• Android Beam™ is technically an NDEF push
in peer-to-peer mode
– Google’s own NDEF Push Protocol (NPP)
– NFC Forum’s new Simple NDEF Exchange Protocol (SNEP)

• No bi-directional data exchange using lower layers

active

Realtime status
information, allow
device settings


Android as a Card

• Card emulation is not exposed in Android API
• Would add many valuable scenarios
• Also consider discussion around secure elements
– in a SIM card
– embedded in a chip
– on stickers


• Future Android devices will
probably have support for
NFC
• Easy handling for user and
developer
• Need to find workaround for
missing card emulation
mode

What is the best way to connect to your
devices and accessories?

Which UX do you desire?

?
What about security?
How does the
device’s environment
look like?

Can you define the
How much data will
deployment targets?
you produce?


TCP / UDP
over WiFi and Mobile Network

Home Automation made easy
powered by ELV

ELV pluggable sensors and actors


powered by ELV


UART


Introducing Arduino

• Open Source prototyping board
• ATmega328 @ 16 MHz
• 14 digital and 6 analog I/O pins
• USB
• UART
• I2C
• SPI
• Many many shields


powered by ELV + Arduino + Android


3G
Internet

DSL

WiFi
UART

Ethernet


Udp.begin(localPort);
server.begin();

Serial.begin(9600);
while(timeStatus() == timeNotSet) {
unsigned long t = getNtpTime();
if (t > 0) {
setTime(t);
}
}
setSyncProvider(getNtpTime);
setSyncInterval(60);

}

bool event_1_triggered = false;
bool event_2_triggered = false;

void loop()
{
time_t t = now();

for(int i = 0; i < EVENT_COUNT; i = i + 1) {
// check whether On-Event was not fired and On-Time has been
reached
if (!triggered_events[i*2] && hour(t) == time_table[i*FIELDS] &&
minute(t) == time_table[i*FIELDS+1]) {
fs20.send_cmd(time_table[i*FIELDS+4], CMD_ON, 0xFF);
triggered_events[i*2] = true;
triggered_events[i*2+1] = false;
}
// check whether Off-Event was not fired and Off-Time has been
reached
if (!triggered_events[i*2+1] && hour(t) == time_table[i*FIELDS+2]
&& minute(t) == time_table[i*FIELDS+3]) {
fs20.send_cmd(time_table[i*FIELDS+4], CMD_OFF, 0xFF);
triggered_events[i*2] = false;
triggered_events[i*2+1] = true;
}
}

// wait for a new client:
Client client = server.available();

// when the client sends the first byte, say hello:
if (client) {
if (client.connected() && client.available()) {
// read the bytes incoming from the client:
char c1 = client.read();
fs20.send_cmd(c1, c2, c3);
}
}

SMA Solar Inverter

Bluetooth

Stiebel-Eltron Heating System

RS232

Build upon small and open
components

 Thermometer
 Accelerometer
 External Sensors
 WiFi
 Twitter
 Email
 Text Messaging

We can make it happen.
Today.

Masanori Fujita

mfu@zuehlke.com
@matterlobby

In touch with smart devices (droidcon)

Empfohlen

Empfohlen

Weitere ähnliche Inhalte

Andere mochten auch

Andere mochten auch (7)

Ähnlich wie In touch with smart devices (droidcon)

Ähnlich wie In touch with smart devices (droidcon) (20)

Mehr von Droidcon Berlin

Mehr von Droidcon Berlin (20)

Kürzlich hochgeladen

Kürzlich hochgeladen (20)

In touch with smart devices (droidcon)