Connected Car … Connected Aeroplane … Connected light bulb…. IoT has become a necessity in every business vertical. A few decades ago enterprises were keen on internal connectivity before attending to external connectivity. But, today it has changed, to connecting anything to everything. Connecting anything to everything requires additional precautionary measures to be taken in areas such as security and governance. In addition to this, delivery channels of IoT (devices/sensors) are required to connect with existing backend systems and service platforms to pull and push events. Therefore, IoT architecture requires an unified manner of handling this situation. APIs, enable extensibility of business operations in internal, external and partner networks. The capability of APIs is such that it can be used to bridge the new IoT world and SOA, EDA, also legacy systems that exists in the enterprises. During this session Asanka Abeysinghe vice president of Solutions Architecture at WSO2 will discuss the relation between APIs and IoT as well as how APIs can be used as a bridge between IoT and other technology domains. Asanka will explain the reference architecture and describe use-cases around the same, while using WSO2 enterprise middleware and cloud platform as the toolset for implementation. This keynote talk was presented at APIdays San Francisco held 17-18 June, 2015.

1. APIs : The Bridge to IoT
Asanka Abeysinghe
Vice President, Solutions Architecture - WSO2,Inc

2. 2

3. Trip to Sri Lanka
3

4. Connect everything to
anything.
4

5. 5

6. Connecting the new/old world
6
Picture Credit : Flicker – Sam Valadi

7. Smart basketball
7
Picture Credit : http://www.94fifty.eu/

8. Nike running app
8
Picture Credit : https://secure-nikeplus.nike.com/plus/running/home

9. Aggregated view
9

10. Anatomy of a device : isolated
- Piece of hardware
- Built for a purpose
- Capable for a limited functionality
- Control interface
- Input/output
- Consumes power
10

11. {API}s to avoid isolation.
11

12. Anatomy of a device : functional
- Functional capabilities (actuators)
- Administration capabilities (management)
- Monitoring capabilities (sensor data)
12

13. {API}s to enable the
device functionality.
13

14. {API}s at the edge
14
Inside device itself
Closer to the device

15. {API}s and devices
15
TO FROM
FUNCTIONAL
SYSTEM

16. Modeling device as an {API}
- HTTP API
- Temperature sensor
- http://{ip}/{locationid}/sensors/temperature -GET
- Motor
-
http://{ip}/{locationid}/actuators/motor1/rotate/{
turns}/{direction} -POST
- http://{ip}/{locationid}/actuators/motor1/status -
GET
16

17. *
App
End User
Device
Device has full API
Management capabilities.
Pattern #1
{API}

18. *
Authorization
Manager
App
End User
Device
Device uses an
authorization server to
authorize access.
Pattern #2
{API}
{API}

19. *
Device
Gateway
App
End User
Authorization
Manager
Device
Having a Device gateway
in front of the device.
Pattern #3
{API}
{API}
{API}

20. *
Device
Gateway
App
End User
Authorization
Manager
Analytics
Device
Device gateway
publishes events to an
external (scalable) event
processing engine.
Pattern #4
{API}
{API}
{API}
{API}

21. Analytics
21

22. *
Mediation/
Routing
Device
Gateway
App
End User
Authorization
Manager
Analytics
Device
Having mediation &
routing capabilities help
to transform the
messages going back
and forth from the
device.
Routing helps to select
the correct device.
Pattern #5
Device
{API}
{API}
{API} {API}
{API}

23. {API}s and Mediation as
the protocol to connect
with the ecosystem.
E.g. Systems of
record/engagement/automation
23

24. *
Event Queue
Mediation/
Routing
Device
Gateway
App
End User
Authorization
Manager
Analytics
Device
Devices could be busy/
unavailable.
Having a Queue helps to
guarantee message
delivery to/from device.
(pub/sub api)
Pattern #6
{API}
{API}
{API}
{API}
{API}
{API}

25. *
Event Queue
Mediation/
Routing
Device
Gateway
App
End User
Authorization
Manager
Analytics
Device
Some devices are not
built with sufficient
processing capabilities.
They could be low
powered ones.
A Device hub will help
such devices connect to
the rest of the world.
Device Hub
Device
DeviceDevice
Pattern #7
{API}
{API}
{API}
{API}
{API}
{API}
{API}{API}

26. *
Event Queue
Mediation/
Routing
Device
Gateway
App
End User
Authorization
Manager
Statistics
Processing
Device
Device Management
helps a large number of
devices (common
policies,etc) to be
managed centrally.
Device Hub
Device
DeviceDevice
Device
Management
Pattern #8
{API}
{API}
{API}
{API}
{API}
{API}
{API}

27. Reference architecture
27

28. SenseBot
28
A robotic car, built around the Arduino Uno and WSO2 Platform.

29. How SenseBot works
29

30. SenseBot APIs
/controller/{direction} - POST
/sensordata/ldrstats – POST
/sensordata/motionStats – POST
/sensordata/sonarStats – POST
/sensordata/tempreatureStats – POST
/sensordata/humidityStats - POST
30

31. Device cloud
31

32. Hackathon in London
32

33. IoT reference architecture
33

34. Enterprise middleware and cloud
platform from systems of record to
systems of engagement
( data to consumer )

35. Summary
35
- Integrate the IoT and the IT world
- Developer productivity & go to market
- Events management
- QoS
- Security
- Scalability
- Reliability
- Device management & governance
- Be prepared to adapt to the future
{API}s

36. 36
b : http://asanka.abeysinghe.org
t : @asankama
e : asankaa AT wso2.com
w : http://wso2.com