APIs : The Bridge to IoT

The Presentation inside:

Slide 0

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

Slide 1


Slide 2

Trip to Sri Lanka 3

Slide 3

Connect everything to anything. 4

Slide 4


Slide 5

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

Slide 6

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

Slide 7

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

Slide 8

Aggregated view 9

Slide 9

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

Slide 10

{API}s to avoid isolation. 11

Slide 11

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

Slide 12

{API}s to enable the device functionality. 13

Slide 13

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

Slide 14


Slide 15

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

Slide 16

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

Slide 17

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

Slide 18

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

Slide 19

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

Slide 20

Analytics 21

Slide 21

* Mediation/ Routing Device Gateway App Authorization Manager Analytics 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 {API} {API} {API} {API} {API}

Slide 22

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

Slide 23

* Event Queue Mediation/ Routing Device Gateway App Authorization Manager Analytics 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}

Slide 24

* Event Queue Mediation/ Routing Device Gateway App Authorization Manager Analytics 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 Pattern #7 {API} {API} {API} {API} {API} {API} {API} {API}

Slide 25

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

Slide 26

Reference architecture 27

Slide 27

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

Slide 28

How SenseBot works 29

Slide 29

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

Slide 30

Device cloud 31

Slide 31

Hackathon in London 32

Slide 32

IoT reference architecture 33

Slide 33

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

Slide 34

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

Slide 35

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