Tizen/Artik IoT Practice Part 5 IoTivity Simple Server and Simple Client

Transcription

1 1 Tizen/Artik IoT Practice Part 5 IoTivity Simple Server and Simple Client Sungkyunkwan University

2 IoTivity Resource 2 In IoTivity, an entity(e.g. Sensor, Actuator) is being handled as a resource(ocf Resource Model). Each resource contains resource and device types, CRUDN Operations, URI information Users can access the Resource via URI and RESTful interface

3 IoTivity Simple Server & Client 3 Simple IoTivity Server & Client Make a simple server (Service Provider [e.g. sensors, actuators]) and simple client (e.g. Android Application) using IoTivity base API(CRUDN). OCF Server In IoTivity network topology, OCF Server handles the CRUDN requests E.g Temperature Sensors, Lights, Humidity Sensors, Air conditional etc.. OCF Client In IoTivity network topology, OCF Client typically finds resources and sends CRUDN requests Android, Linux, Tizen, Windows, etc..

4 RESTful Resource Model RESTful API Http request interface such as GET, PUT, POST, DELETE Using RESTful API, users can control the OCF server device in remote 4 RESTful API CRUDN

5 Simple Client & Server Scenario 5 Using IoTivity base API set, make a simple server (Temperature, Humidity sensors) and Android simple client App Temperature Sensor URi : /a/temperature Type : core.temperature CRUDN API : RUND Source Repository :

6 Resource Class Resource class contains basic operation of IoTivity & CRUDN virtual functions (interface set) IoTivity/resource/examples/IoTivity_Sample_Server/resource.h File <User Define Virtual Function> put : Set the data sent from the cline get : Get the data requested from the Client SensorValueRead : Sensor Acquisition Read Thread ChangeResourceRepresentation : Observe Thread Logic User-defined Virtual Interface 6 <Common Interface Function> Resource Creation Logic : Resource Creation and Registering the URI resource EntityHandler Logic : Request Handling Parsing Logic Common Interface for Entity Handler

7 Resource Class Implementation Common IoTivity Resource API Resource Creation, Resource Handler (CRUDN Request Parser) 7 IoTivity/resource/examples/IoTivity_Sample_Server/resourceImpl.cpp File Initialization Uri & Resource Type Registering CRUDN API Parsing Handler Callback Resource Registering Request Parsing Logic Resource Creation Function CRUDN API Handler Unit

8 Entity Handler - CRUDN Request Handler Entity handler refers to the CRUDN request parsing callback function GET : get the sensor data, then send data with response to the clients PUT : receive the status value (e.g. Turn On, Off) from the client, and set the status Observe : Periodically, observer thread publishing the sensor data to registered clients GET Observe 8 Put Delete

9 Server (Thing Device) Interface E.g., Light, Humidity, Temp 9 URI, Resource Type < Get Logic > Things Meta-Data <Temperature Things> IoTivity/resource/examples/IoTivity_Sample_Server/simple_server_temp.h /.cpp File

10 Server (Thing Device) Interface (2/2) 10 Get the data from the Representation Notify the current message to observers <Sensor Logic> Sensor Thread Creation <Put Logic> <Observation Logic>

11 Simple Client (Android) IoTivityWrapper.java 11 Listener Callback Operation

12 findresource() - Resource Find Logic 12 Platform Configuration Found resource info <Find Resource Listener Callback> Find Resource API

13 GET & PUT Function 13 <PUT Function> <GET Function> <Observe Function> <GET Listener Callback>

14 Client Resource Description 14 To get the value from Representation for GET, OBSERVE To set the value to Representation for PUT

15 IoTivity Communication Demo 1 /a/temp - PUT Status ON 2 /a/humidity - PUT Status ON 3 4 /a/temp - Get /a/humidity - Get Temperature Humidity