SAMI Ecosystem & APIs Overview

© 2014 Samsung Developer Conference. All rights reserved. www.samsungdevcon.com
SAMI
Ecosystem & APIs
Jerome Dubreuil – Dan Serfaty

2
Brief history
• About us
– Past lives in startups and big companies
– Early fans of cloud technologies and platforms connecting devices
• About SAMI
– Started 2013
– Clean slate, no legacy
– Focus on developer and ecosystem from day 1
– Mindset of a startup, strength and maturity of the enterprise

3
Why?

Everything is data

5
A new paradigm

6
A new paradigm
• Digitalize and abstract the physical world
• Any device, any data
• No silo, unlimited data fusion

7
A new paradigm
• Fully open
• Any device can connect, send + receive data
• Any application can access user data
• Full privacy control

8
Data Driven Development

9
You focus on the device
and the applications

10
SAMI takes care of the data

A very simple use case

12
App
• Live monitoring
• Historical Graphs
A very simple use case
Use case: multiple sensors in a house
65,60,600
67,80,650
72,62,630
65,62,602
{
“temp”:65,
“noise”: 60,
“co2”: 600
}
Format: CSV,
every minute
Temp: 65°F,
Noise: 60db
CO2: 600 ppm
Bedroom Room 1
Kitchen
Living Room
Bedroom Room 2
}

13
The developer experience
Create a
Device Type
Create an
application
developer.samsungsami.io

Devices
Connecting devices to SAMI

15
What’s a device in SAMI?
• A device is any registered node that can send and receive data using
the SAMI platform

16
What’s a device type?
• A device type describes a class of devices and the data it is sending
• A device type has a Manifest that:
– Describes the data coming in
– Processes incoming data in real-time
– Normalizes data for SAMI

17
Creating a Device Type and a Manifest

18
Creating a Device Type and a Manifest
• Before submitting, develop your Manifest locally in an IDE using tools
available on the developer portal:
– Manifest SDK (download)
– Documentation, samples, tutorial

19
The Manifest
• Transforms any input data into normalized output data
• Output data are fields (can be nested):
– Name
– Type (bool, integer, long, floats, double, string, collections)
– Unit (allows some level of conversion)
• Today, full power of a Groovy script, with approval
• Tomorrow: simplified version, no approval

20
The Manifest
import com.samsung.sami.manifest.Manifest
import com.samsung.sami.manifest.fields.*
import static com.samsung.sami.manifest.fields.StandardFields.*
import javax.measure.unit.NonSI
public class MyDeviceManifest implements Manifest {
public final static FieldDescriptor TEMP_INTEGER = TEMPERATURE.alias(Integer.class)
public final static FieldDescriptor NOISE = new FieldDescriptor("noise", NonSI.DECIBEL, Integer.class);
public final static FieldDescriptor CO2 = new FieldDescriptor("co2", StandardUnits.PARTS_PER_MILLION, Integer.class);
@Override
List<Field> normalize(String input) {
def fields = []
def values = input.split(",")
def tempInF = values[0].asType(Integer.class)
def noise = values[1].asType(Integer.class)
def co2 = values[2].asType(Integer.class)
fields.add(new Field(TEMP_INTEGER, NonSI.FAHRENHEIT, tempInF))
fields.add(new Field(NOISE, noise))
fields.add(new Field(CO2, co2))
return fields
}
@Override
List<FieldDescriptor> getFieldDescriptors() {
return [TEMP_INTEGER, NOISE, CO2]
}
}

21
Testing your Manifest

22
Testing your Manifest
> java -jar sami-manifest-sdk-1.7.jar -m MyDeviceManifest.groovy -d myDeviceData.csv
==============================================================================
Manifest File: MyDeviceManifest.groovy
Modified On: 10/31/2014 11:02:52
==============================================================================
Manifest FieldDescriptors:
co2 FieldDescriptor[name: co2, normalizedUnit: ppm, valueClass: class java.lang.Integer]
temp FieldDescriptor[name: temp, normalizedUnit: ℃, valueClass: class java.lang.Integer]
noise FieldDescriptor[name: noise, normalizedUnit: dB, valueClass: class java.lang.Integer]
==============================================================================
Results after running manifest on provided data file:
Field[name: temp, field descriptor: FieldDescriptor[name: temp, normalizedUnit: ℃, valueClass:
class java.lang.Integer], unit: °F, value: 18]
Field[name: noise, field descriptor: FieldDescriptor[name: noise, normalizedUnit: dB,
valueClass: class java.lang.Integer], unit: dB, value: 62]
Field[name: co2, field descriptor: FieldDescriptor[name: co2, normalizedUnit: ppm, valueClass:
class java.lang.Integer], unit: ppm, value: 602]
==============================================================================

23
Creating devices
• Through an application using the API
• Through the User Portal

24
How does the device send data?
• Today, 2 protocols: REST, WebSocket
• Tomorrow: any protocol (XMPP, MQTT, …)
• Sample curl call to post a message:
curl -X POST "https://api.samsungsami.io/v1.1/messages" -H "Content-type: application/json" -
d '{"sdid": "281c2bb26a604ed0b4655d446614d9f4", "data": "65,62,602" }' -H "Authorization:
bearer dc7c5016161f419b85e95ca6e7791198”
• Simulator

25
Visualize live and historical data

Applications
Creating value with SAMI

27
Our use case

28
Creating applications

29
How does an application use the SAMI API?
• Oauth 2
• Login is through Samsung Account
• All endpoints need an access token

30
• More details coming in next session about SDKs, samples and tools
• We are showing here examples based on the raw API

31
> java -jar tyrus-client-cli-1.7.jar
"wss://api.samsungsami.io/v1.1/live?userId=6dbf2c80612f11e498030800200c9a
66&Authorization=bearer+dc7c5016161f419b85e95ca6e7791198”
# Connecting to
wss://api.samsungsami.io/v1.1/live?userId=6dbf2c80612f11e498030800200c9a6
6&Authorization=bearer+dc7c5016161f419b85e95ca6e7791198...
# Connected in session 6fbe6f34-a20a-4d4b-bc7d-86420a48dbde
# text-message: {"type":"ping", "ts":1414781476400}
# text-message:
{"mid":"1f1c0dd43e134b6d96fa23a01a6db91e","data":{"temp":18,"noise":62,"c
o2":602},"ts":1414781536866,"sdtid":"dt7c4f60efdc244ea1ac4b247620a38a4b",
"cts":1414781536866,"uid":"2","mv":1,"sdid":"ea064adf013b45ae8ed7b72bf40f
0d49"}
# text-message:
{"mid":"0b424e4ccec247dc8b994895a66d885c","data":{"temp":18,"noise":62,"c
o2":602},"ts":1414781538573,"sdtid":"dt7c4f60efdc244ea1ac4b247620a38a4b",
"cts":1414781538573,"uid":"2","mv":1,"sdid":"ea064adf013b45ae8ed7b72bf40f
0d49"}
Code sample 1: Websocket

32
> curl
"https://api.samsungsami.io/v1.1/messages?sdid=ea064adf013b45ae8ed7b72bf40f0d49&startDate=141469396400
0&endDate=1414780365000" -H "Authorization: bearer dc7c5016161f419b85e95ca6e7791198"
…
"data":[
{
"mid":"6b29828281ff49dba2feb639e13d6bfa",
"data":{
"temp":18,
"noise":62,
"co2":602
},
"ts":1414780059836,
"sdtid":"dt7c4f60efdc244ea1ac4b247620a38a4b",
"cts":1414780059836,
"uid":"6dbf2c80612f11e498030800200c9a66",
"mv":1,
"sdid":"ea064adf013b45ae8ed7b72bf40f0d49"
},
…
Code sample 2: REST /messages

33
Examples of available APIs
• User
– Profile
• Devices
– CRUD devices, CRUD tokens
• Device Types
– Device Type Information, Manifest Versions, Manifest Properties
• Messages
– post, read, aggregates, export

Real life example
Bloom Technologies
Julien Penders
http://www.bloom-life.com

35
Meet Bloom

36
A powerful yet simple wearable to track
contractions. Building on SAMI.
Connect
With your body and get
new insight
Track
Clinically relevant
information
Share
With your partner or doctor.
Unlock new clinical discovery.

37
Bloom Manifest
Device
Bloom
Device type
Bloom contraction monitor
Bloom Alpha HR monitor
Bloom Alpha Motion sensor
Manifests
BloomIUPManifest
BloomHeartRateManifest
BloomAccelerometerManifest
Example of manifest: BloomIUPManifest
public class BloomIUPManifest implements Manifest {
// Custom FieldDesc
static final SESSION_ID = new FieldDescriptor("session_id", Integer.class)
static final IUP_HORIZONTAL = new FieldDescriptor("iup_horizontal", Float.class)
static final IUP_VERTICAL = new FieldDescriptor("iup_vertical", Float.class)
// boolean signals, true when contraction is active
static final CONTRACTION_VERTICAL = new FieldDescriptor("contraction_vertical",
Boolean.class)
static final CONTRACTION_HORIZONTAL = new FieldDescriptor("contraction_horizontal",
Boolean.class)
@Override
List<Field> normalize(String input)
{
...
}
@Override
List<FieldDescriptor> getFieldDescriptors() {
return [IUP_VERTICAL, IUP_HORIZONTAL, CONTRACTION_VERTICAL,
CONTRACTION_HORIZONTAL,SESSION_ID]
}
}

38
Real-time data streaming and visualization in SAMI
SAMI
Contraction signal
Contraction features
maternal HR
Contraction signal
Contraction features
maternal HR
Phone motion
sensor
message.data =@{
@"iup_vertical": @([dataPoint.iup_vertical floatValue]),
@"iup_horizontal": @([dataPoint.iup_horizontal floatValue]),
@"contraction_vertical": @([dataPoint.contraction_vertical boolValue]),
@"contraction_horizontal": @([dataPoint.contraction_horizontal boolValue]),
@"session_id": @([dataPoint.sessionId integerValue])
};

39
Retrieving and visualizing data from SAMI
SAMI
Recording
session
NSString* filter = [NSString
stringWithFormat:@"session_id:%d",[sessionToRead.identifi
er integerValue]];
SAMIDLog(@"filter %@",filter);
[api2 getNormalizedMessagesWithCompletionBlock:nil
sdid:deviceAlphaIUP._id mid:nil fieldPresence:nil
filter:filter offset:nil count:nil startDate:@(start)
endDate:@(stop) order:nil
completionHandler:^(SamiNormalizedMessagesEnvelope
*output, NSError *error) {
//SAMIDLog(@"output.data %@",output.data);
NSArray * messages = output.data;
SAMIDLog(@"got %d points [session id
%d]",[messages count],[sessionToRead.identifier
integerValue]);
}];

40
Demo

Conclusion

42
What’s next – Building applications
Personal
security
Business
Processes
Data
Analysis
Machine
learning
Coaching
modules
User
Interfaces
Wellness
Programs
People Devices Services

43
What’s next – Getting started
• Get started guide, Hello World, tutorials, API reference
• Tools
– Live console to discover the API
– Manifest SDK
– Device simulator
– API SDKs and sample applications (Java/Android, iOS, Python, Ruby,
Javascript, Tizen, PHP, …)
– User portal (manage devices, visualize data)
• Attend the SAMI SDK session
developer.samsungsami.io

44
It’s a journey
Not a destination

45
Beta

46
We’re hiring

47
Q&A
and THANK YOU for your time.
Dan Serfaty - linkedin.com/in/danserfaty
Jerome Dubreuil - linkedin.com/in/jeromedubreuil

Backup

49
Additional notes
• An application can understand what data “is” by looking at the
Manifest
• Why Groovy: simple, popular scripting language and JVM based
• Why a program: as flexible as possible, no constraint on input data
• Once the Manifest is in the platform, can create new devices in a
private way

SAMI Ecosystem & APIs Overview

Recommended

Recommended

More Related Content

Similar to SAMI Ecosystem & APIs Overview

Similar to SAMI Ecosystem & APIs Overview (20)

Recently uploaded

Recently uploaded (20)

SAMI Ecosystem & APIs Overview

Editor's Notes