IoTivity. Sungkyunkwan University. Presenter: Dzung Tien Nguyen Networking Laboratory,

Transcription

1 Sungkyunkwan University IoTivity Presenter: Dzung Tien Nguyen Networking Laboratory, Copyright Networking Laboratory 1/00

2 Current issues Incompatibility of platforms: Manufacturers are providing a large number of IoT devices. Those devices could be based on Linux, Android, Adruino, ios, etc. To let them work together requires a hub/controller to interpret (or translate ) the data, commands. Difficulty in cooperation between industries (smart home, automotive, industrial automation, healthcare etc.) IoTivity demo Networking Laboratory 2/37

3 IoTivity target To provide a common open source framework for Discovery and Connectivity. In addition to that, Device management and Data management are mentioned as services To ensure interoperability among products and services, regardless of maker and across multiple industries, e.g. Consumer, Enterprise, Industrial, etc. The interaction might be made between WIFI, Bluetooth, Zigbee, Z-wave devices and so forth To provide the common code bases/apis to accelerate innovation, besides the open standard and specifications Supporting Linux (compiled), Android (Compiled), Tizen, Adruino, Yocto, ios, Windows (unsuccessful) IoTivity demo Networking Laboratory 3/37

4 The framework IoTivity demo Networking Laboratory 4/37

5 The stack architecture IoTivity demo Networking Laboratory 5/37

6 Protocol: CoAP Is Constrained Application Protocol for constrained resource environment Is a simple and compact binary mapping of REST Provides asynchronous notifications, publish-subscribe, resource discovery Work in CLIENT/SERVER context Each entity can be both CLIENT/SERVER at the same time IoTivity is using CoAP IoTivity demo Networking Laboratory 6/37

7 More about CoAP Most IoT systems use UDP. However, since UDP is neither stable nor reliable, it needs to combine with another application protocol to improve the stability CoAP stands for Constrained Application Protocol, is a client-server application layer protocol designed for resource-constrained devices (i.e. low power, small, need to control remotely) CoAP is like HTTP (document transfer protocol), but with multicast, low overhead and simplicity. CoAP can easily be translated to HTTP. CoAP is built on top of UDP (not TCP) and supports the scalable web services IoTivity demo Networking Laboratory 7/37

8 Resource Discovery IoTivity demo Networking Laboratory 8/37

9 CoAP: observation CoAP extends the HTTP request model with the ability to observe a resource. When the observe flag is set on a CoAP GET request, the server may continue to reply after the initial document has been transferred. This allows servers to stream state changes to clients as they occur. Either end may cancel the observation. Example of a resource: a light controller, a garage door opener Resources might be organized in a hierarchical manner (tree form) E.g. /fridge/ Light1 Light2 Fan Sensor1 Sensor2 IoTivity demo Networking Laboratory 9/37

10 More on IoTivity Current release: 0.9.2, open source Getting started: Number of joined companies: 50+, including Intel, Samsung, Still in development phase, not a production-ready product Discussion forum: View is available Registering seems not open IoTivity demo Networking Laboratory 10/37

11 The virtual machine Ubuntu Username/passwd: mc2015/123 Gcc4.9 Eclipse with Android SDK v.19 / 20 / 21 (required); Android NDK, Gradle Dependencies: python2.7, scons Jre Boost, IoTivity demo Networking Laboratory 11/37

12 Build the framework Source code inside the VM is prebuilt with the following options: scons TARGET_OS=linux TARGET_ARCH=x86 TARGET_TRANSPORT=IP scons TARGET_OS=android TARGET_ARCH=armeabi TARGET_TRANSPORT=IP To add more source file (e.g. to folder resource/examples) and recompile: Inside the folder, modify Sconscript From root directory execute: scons resource/examples IoTivity demo Networking Laboratory 12/37

13 Before getting started Generating the doxygen doxygen g iotdoc vim iotdoc RECURSIVE=YES CREATE_SUBDIRS=YES GENERATE_LATEX=NO doxygen iotdoc IoTivity demo Networking Laboratory 13/37

14 Client/Server basis Server Init the configuration Register resource Entity handlers for handling request (GET/PUT/POST/OBSERVE) Client Client configuration Functions for PUT/GET/POST/OBSERVE and its callbacks IoTivity demo Networking Laboratory 14/37

15 InitOICStack config Initialize the configuration mode of the thing ServiceType: InProc, OutOfProc ModeType: Server/Client/Both IPAddress: means broadcast ClientConnectivityType: port number QualityOfService: LowQoS, MidQos, HighQos, NaQos (in OCApi.h) IoTivity demo Networking Laboratory 15/37

16 [SERVER] Define a resource Member variables Constructor IoTivity demo Networking Laboratory 16/37

17 [SERVER] Register the resource C++ API OCStackResult OC::OCPlatform::registerResource( ); OCEntityHandlerResult entityhandler(std::shared_ptr<ocresourcerequest> request) IoTivity demo Networking Laboratory 17/37

18 Application calls the library function On finishing the task, the library function trigger the associated callback at the same tier with the call IoTivity demo Networking Laboratory 18/37

19 Find Resource On the findresource(), the get() request is sent out (multicast) to all the vicinity IoT devices Each device processes the query and responds if it satisfies the request filter Parameters: "oic/res?rt=core.light" including URI path ( /oc/core ) and URI query ( rt=core.light ) /oic/res is the OIC Virtual resources supported by every OIC device (octypes.h) IoTivity demo Networking Laboratory 19/37

20 Scheme 1: Simple discovery myclient myserver findresource() Register resource OCResource foundresource() get() GET OCRepresentation ongetcallback() IoTivity demo Networking Laboratory 20/37

21 [CLIENT] Find Resource FindResource syntax std::ostringstream requesturi; requesturi << OC_RSRVD_WELL_KNOWN_URI << "?rt=core.light"; OCStackResult result = OCPlatform::findResource("", CT_DEFAULT, FindCallback); FindResource s Callback requesturi, void founddevice(std::shared_ptr<ocresource> resource){ if(resource){ std::cout << "Got one" << resource->host() << resource->uri() << std::endl; } } //host() return string coap://<m_devaddr.addr>:<m_devaddr.port> //source: OCResource.cpp IoTivity demo Networking Laboratory 21/37

22 [Client] Get Trigger GET request OCStackResult result = resource->get(getmap, g); if(oc_stack_ok!= result) { std::cout << "Get resource error!" << std::endl; } Process ongetcallback void ongetcallback(const HeaderOptions& ho, const OCRepresentation& rep, const int ecode){ if (ecode == OC_STACK_OK){ std::cout << "GET request was successful" << std::endl; std::cout << "\tpower value: " << rep.getvaluetostring("power") << std::endl; }else{ std::cout << "Error in GET callback" << std::endl; } } IoTivity demo Networking Laboratory 22/37

23 [SERVER] OnGetRequest On receiving GET request, the resource server get() its representation and sendresponse back to the requester using OCPlatform API if (requesttype == "GET") { std::cout << "\treceived GET request\n"; presponse->setresourcerepresentation(lightresource::get()); if(oc_stack_ok == OC::OCPlatform::sendResponse(pResponse)) { ehresult = OC_EH_OK; } } IoTivity demo Networking Laboratory 23/37

24 Scheme 2: PUT request myput myserver put() OCResource onputcallback() entityhandler (requesttype == PUT ) get() GET OCRepresentation ongetcallback() IoTivity demo Networking Laboratory 24/37

25 [CLIENT] PUT PUT is to send the next state to the resource Send the new desired state of type OCRepresentation to the resource //do the PUT OCRepresentation reptoput; reptoput.seturi("/a/light"); for (auto i = 0; i < 10; i++){ if (i%2 == 0) reptoput.setvalue("power", std::string("off")); else reptoput.setvalue("power", std::string("on")); put(myclient::lightresources, reptoput); sleep(3); } IoTivity demo Networking Laboratory 25/37

26 Scheme 3: OBSERVE request put() myput myobserverserver - entityhandler(requesttype == PUT ) - notifyobserver() myobserverclient findresource() and Observe() Get server s state change IoTivity demo Networking Laboratory 26/37

27 Usecase: send other In IoTivity, devices are in CLIENT/SERVER modes, and the connections are of type Client-Server The available messages are GET/PUT/POST/OBSERVE Look at the signature of those functions: OCStackResult OCResource::get(const QueryParamsMap &, GetCallback attributehandler) OCStackResult OCResource::put(const OCRepresentation & representation, const QueryParamsMap & queryparametersmap, PutCallback attributehandler) OCStackResult OCResource::post(const OCRepresentation & representation, const QueryParamsMap & queryparametersmap, PostCallback attributehandler) OCStackResult OCResource::observe(ObserveType observetype, const QueryParamsMap & queryparametersmap, ObserveCallback observehandler) In OCApi.h: typedef map::<string, string> QueryParamsMap; IoTivity demo Networking Laboratory 27/37

28 Back to OnGetCallback With OCRepresentation which will be sent back to the client, we can carry any data with user-defined field name In the example, power is the field name void ongetcallback(const HeaderOptions& ho, const OCRepresentation& rep, const int ecode){ if (ecode == OC_STACK_OK){ } std::cout << "\tpower value: " << rep.getvaluetostring("power") << std::endl; } else{ std::cout << "Error in GET callback" << std::endl; } IoTivity demo Networking Laboratory 28/37

29 Scheme 4: user-defined GET myquery Client myquery Server get() IoTivity demo Networking Laboratory 29/37

30 To be modified Add extra info to GET message QueryParamsMap getmap; getmap["energylevel"] = "100"; getmap["ip"] = myclient::myip4address; Add energy level to resource s representation l_rep.setenergy("energylevel", l_energy); IoTivity demo Networking Laboratory 30/37

31 Extract info From server side: calling API to get the queryparams of type std::map<string, string> std::string requesttype = request->getrequesttype(); std::map<std::string, std::string> queryparams = request->getqueryparameters(); auto requestrepresentation = request->getresourcerepresentation(); for(auto it = queryparams.cbegin(); it!= queryparams.cend(); it++) { std::cout << it->first << " : " << it->second << std::endl; // it->first = Text energylevel // it->second = the actual value } Client: Ocrepresentation.getValueToString( energylevel ) IoTivity demo Networking Laboratory 31/37

32 Approach to the project Creation of an array for storing resources in the vicinity Requesting residual energy from neighbors, selecting the highest (e.g. using GET) Utilizing the PUT message to send data to an end point Defining new field in the OCRepresentation (e.g. mode = aggregation / put ) On the server side: if (requesttype == "PUT") { recvmsg = request->getresourcerepresentation(); if (recvmsg.getvaluetostring("mode") == "aggregation") { //do something here } } Making your aggregation algorithms (e.g. taking average of all the Temperature received) and then sending to the sink IoTivity demo Networking Laboratory 32/37

33 Sungkyunkwan University Things-manager Extra example Copyright Networking Networking Laboratory 33/00

34 Guideline link Follow this link: _1 Path for android SDK: Iotivity/extlibs/android/sdk/android-sdk/ Path for android NDK: Iotivity/extlibs/android/ndk/android-ndk/ Link for installing android plugin for eclipse: IoTivity demo Networking Laboratory 34/37

35 Topology Context: All the devices connect to the Access point Light resources <mcl1> and <mcl2> registered Android clients interacts with the resources: PUT, OBSERVE Scheduled PUT IoTivity demo Networking Laboratory 35/37

36 IoTivity demo Networking Laboratory 36/37

37 IoTivity demo Networking Laboratory 37/37