DOCSLIB.ORG

Iotivity Demo Networking Laboratory 2/37 Iotivity Target

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
Iotivity Demo Networking Laboratory 2/37 Iotivity Target Sungkyunkwan University IoTivity Presenter: Dzung Tien Nguyen Networking Laboratory, 83345 [email protected] Copyright 2000-2015Networking Networking Laboratory Laboratory 1/00 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 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 The framework IoTivity demo Networking Laboratory 4/37 The stack architecture IoTivity demo Networking Laboratory 5/37 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 http://iot-datamodels.blogspot.kr/ IoTivity demo Networking Laboratory 6/37 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 Resource Discovery IoTivity demo Networking Laboratory 8/37 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 More on IoTivity Current release: 0.9.2, open source Getting started: https://www.iotivity.org/documentation/linux/getting- started Number of joined companies: 50+, including Intel, Samsung, … Still in development phase, not a production-ready product Discussion forum: ► https://jira.iotivity.org/browse/IOT-124 ► View is available ► Registering seems not open IoTivity demo Networking Laboratory 10/37 The virtual machine Ubuntu 14.04 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 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 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 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 InitOICStack config Initialize the configuration mode of the ‘thing’ ► ServiceType: InProc, OutOfProc ► ModeType: Server/Client/Both ► IPAddress: 0.0.0.0 means broadcast ► ClientConnectivityType: port number ► QualityOfService: LowQoS, MidQos, HighQos, NaQos (in OCApi.h) IoTivity demo Networking Laboratory 15/37 [SERVER] Define a resource Member variables Constructor IoTivity demo Networking Laboratory 16/37 [SERVER] Register the resource C++ API ► OCStackResult OC::OCPlatform::registerResource(…); ► OCEntityHandlerResult entityHandler(std::shared_ptr<OCResourceRequest> request) IoTivity demo Networking Laboratory 17/37 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 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 Scheme 1: Simple discovery myClient myServer Register resource findResource() OCResource foundResource() get() GET OCRepresentation onGetCallback() IoTivity demo Networking Laboratory 20/37 [CLIENT] Find Resource FindResource syntax std::ostringstream requestURI; requestURI << OC_RSRVD_WELL_KNOWN_URI << "?rt=core.light"; OCStackResult result = OCPlatform::findResource("", requestURI, CT_DEFAULT, FindCallback); FindResource ‘s Callback 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 [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 [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 Scheme 2: PUT request myput myServer put() entityHandler (requestType == “PUT”) OCResource onPUTCallback() get() GET OCRepresentation onGetCallback() IoTivity demo Networking Laboratory 24/37 [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 Scheme 3: OBSERVE request myput myObserverServer myObserverClient findResource() put() and Observe() - entityHandler(requestType == “PUT”) - notifyObserver() Get server’s state changes IoTivity demo Networking Laboratory 26/37 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 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
Load more

Recommended publications
  • Demystifying Internet of Things Security Successful Iot Device/Edge and Platform Security Deployment — Sunil Cheruvu Anil Kumar Ned Smith David M
    Demystifying Internet of Things Security Successful IoT Device/Edge and Platform Security Deployment — Sunil Cheruvu Anil Kumar Ned Smith David M. Wheeler Demystifying Internet of Things Security Successful IoT Device/Edge and Platform Security Deployment Sunil Cheruvu Anil Kumar Ned Smith David M. Wheeler Demystifying Internet of Things Security: Successful IoT Device/Edge and Platform Security Deployment Sunil Cheruvu Anil Kumar Chandler, AZ, USA Chandler, AZ, USA Ned Smith David M. Wheeler Beaverton, OR, USA Gilbert, AZ, USA ISBN-13 (pbk): 978-1-4842-2895-1 ISBN-13 (electronic): 978-1-4842-2896-8 https://doi.org/10.1007/978-1-4842-2896-8 Copyright © 2020 by The Editor(s) (if applicable) and The Author(s) This work is subject to copyright. All rights are reserved by the Publisher, whether the whole or part of the material is concerned, specifically the rights of translation, reprinting, reuse of illustrations, recitation, broadcasting, reproduction on microfilms or in any other physical way, and transmission or information storage and retrieval, electronic adaptation, computer software, or by similar or dissimilar methodology now known or hereafter developed. Open Access This book is licensed under the terms of the Creative Commons Attribution 4.0 International License (http://creativecommons.org/licenses/by/4.0/), which permits use, sharing, adaptation, distribution and reproduction in any medium or format, as long as you give appropriate credit to the original author(s) and the source, provide a link to the Creative Commons license and indicate if changes were made. The images or other third party material in this book are included in the book’s Creative Commons license, unless indicated otherwise in a credit line to the material.
    [Show full text]
  • Iotivity and Iotivity-Lite • Resources for Getting Started
    Overview of IoTivity Projects Kishen Maloor, Intel June 2018 Agenda • What is IoTivity? • Structure of an OCF implementation • IoTivity and IoTivity-Lite • Resources for getting started 2 What is IoTivity? • Umbrella of projects for building IoT devices • Open-source, reference implementations of OCF specifications • Serve as starting point for developing and certifying OCF products Specifications Vertical Data Models Device Certification Strategy, Marketing Independent governance with coordinated efforts 3 Structure of an OCF implementation User space IoT Applications Outer functional blocks APIs & Language Security Manage on-boarding, Bindings Provisioning Provisioning credentials, Infrastructure Access-control lists OCF Resource Model Resource directory, Device High-level Services Wi-Fi Easy Setup, etc. Stack Security Flows Bridging to other Zigbee, Z-Wave, etc. IP Connectivity ecosystems Kernel space Network Interfaces OS & Kernel 4 IoTivity and IoTivity-Lite • IoTivity • Suitable only for more capable device classes • Runs on Linux, Windows, Android, macOS • Multiple language bindings: C, C++, Java, Node.js • IoTivity-Lite (formerly called IoTivity-Constrained) • Lightweight implementation of OCF specifications • Suitable for all device classes (including few constrained devices) • Runs on Linux, Windows, macOS, and multiple RTOSes • C APIs only 5 IoTivity Directory Structure auto_build.py NOTICE.md auto_build.sh plugins bridging prep.sh build_common README-building-and-running-remote-access-sample.txt cloud README.md CONTRIBUTING.md
    [Show full text]
  • Krawetz, Neal
    Response to DoC NTIA RFC No. 160331306­6306­01 Page 1 of 23 Response to the Department of Commerce National Telecommunications and Information Administration Request for Comment on Internet of Things The Benefits, Challenges, and Potential Roles for the Government in Fostering the Advancement of the Internet of Things RFC No. 160331306‐6306‐01 May 22, 2016 Neal Krawetz, Eric Schultz, Valerie Kaminsky, Bill Tucker, et al. Response to DoC NTIA RFC No. 160331306­6306­01 Page 2 of 23 The Department of Commerce (DoC) National Telecommunications and Information Administration (NTIA) issued a Request for Comments (RFC) in the Federal Register.1 This issuance requested feedback on the current policy and technological landscape related to the Internet of Things (IoT). This document includes responses to the following items: IoT Challenges Software Patches Unsupported Devices Personal Information Recycling and Safe Disposal Disposable Electronics Insecure Design Inherent Vulnerabilities Intentional Backdoors Network and Infrastructure Economic Impact Industry Recommendations Governmental Role Current Government Policies Recommended Government Policies Proposed Role for NTIA Contributors IoT Challenges Issue #1 in the NTIA RFC requested information related to the challenges and opportunities arising from IoT. In particular, how they are similar to existing challenges and what aspects are novel. This topic is further discussed in other issues, including #6 (technological issues), #16 (cybersecurity), and #17 (privacy). The challenges posed by the Internet of Things mirrors today’s existing issues with mobile devices in regards to security, application, and networking. However, the IoT amplifies all of these issues and brings them to a critical level. The IoT is positioned to become invasive and integral to businesses and consumers across America.
    [Show full text]
  • Time-To-Provision Evaluation of Iot Devices Using Automated Zero
    Time-to-Provision Evaluation of IoT Devices Using Automated Zero-Touch Provisioning Ivan Boˇskov∗†, Halil Yetgin∗‡, MatevˇzVuˇcnik∗†, Carolina Fortuna∗, Mihael Mohorˇciˇc∗† ∗Department of Communication Systems, Joˇzef Stefan Institute, SI-1000 Ljubljana, Slovenia. †Joˇzef Stefan International Postgraduate School, Jamova 39, SI-1000 Ljubljana, Slovenia. ‡Department of Electrical and Electronics Engineering, Bitlis Eren University, 13000 Bitlis, Turkey. {ivan.boskov | halil.yetgin | matevz.vucnik | carolina.fortuna | miha.mohorcic}@ijs.si Abstract—The Internet of Things (IoT) is being widely adopted thus to avoid manual provisioning process [3]. Therefore, ZTP in today’s society, interconnecting smart embedded devices that enables accomplishing and providing remote device provision- are being deployed for indoor and outdoor environments, such ing, where even an end-user that does not have the technical as homes, factories and hospitals. Along with the growth in the development and implementation of these IoT devices, their knowledge can simply connect a non-provisioned device to simple and rapid deployment, initial configuration and out- the network [3]. Having reviewed the paucity of the literature of-the-box operational provisioning are becoming prominent and the industry perspectives, the characteristics of a typical challenges to be circumvented. Considering a large number of ZTP can be summarized as follows. heterogeneous devices to be deployed within next generation IoT networks, the amount of time needed for manual provisioning • Ease of Use - provisioning could be performed by anyone of these IoT devices can significantly delay the deployment and even without technical background. manual provisioning may introduce human-induced failures and • Interoperability - ZTP should be independent of vendors. errors. By incorporating zero-touch provisioning (ZTP), multiple • Security - during the provisioning process, credentials heterogeneous devices can be provisioned with less effort and without human intervention.
    [Show full text]
  • Avoid the Silos and Help Build the True Internet of Things
    Avoid the Silos and Help Build the True Internet of Things April 2016 Aaron Vernon, CTO at Higgns [email protected] I N T R O D U C T I O N ● Aaron Vernon, CTO at Higgns ● Previously I was VP Software Engineering at LIFX and CTO at Two Bulls ● Chair of the AllSeen Alliance Common Frameworks Working Group ● I am going to cover the following: ○ The complexities of the current IoT landscape ○ How this affects companies and users ○ The Internet of Silos example ○ How we can work together better Transports W i F i ● Uses the 802.11 standard ● Standard on all mobile devices and routers ● Has become ubiquitous for users ● Great range ● Great bandwidth ● High power consumption ● High cost ● Onboarding experience can be complicated ● Examples: Nest Cam, LIFX, Canary, Honeywell Lyric B L U E T O O T H S M A R T ● Standard on most mobile devices ● Becoming increasingly ubiquitous ● Low bandwidth ● Medium range ● Low power consumption ● Low cost ● Smart Mesh is being worked on ● Examples: Flic, Ilumi, Elgato Eve Z I G B E E ● Uses the 802.15.4 standard ● Low bandwidth ● Low range ● Low power consumption ● Very low cost ● Forms a mesh network ● Typically requires a hub for the radio ● Known to have interop and interference problems ● Examples: Phillips Hue, large amount of sensors and actuators Z W A V E ● Proprietary - chips developed by a single manufacturer ● Uses different frequencies in different countries ● Low bandwidth ● Medium range ● Low power consumption ● Very low cost ● Forms a mesh network ● Better interoperability and less interference
    [Show full text]
  • Comparison of Iot Frameworks for the Smart Home
    Alexander Nimmermark Larsson Erik & Comparison frameworks of IoT for the smart Master’s Thesis Comparison of IoT frameworks for the smart home Alexander Larsson Erik Nimmermark home Series of Master’s theses Department of Electrical and Information Technology LU/LTH-EIT 2016-520 http://www.eit.lth.se Department of Electrical and Information Technology, Faculty of Engineering, LTH, Lund University, 2016. Comparison of IoT frameworks for the smart home Alexander Larsson [email protected] Erik Nimmermark [email protected] Anima AB Västra Varvsgatan 19, Malmö Advisor: Maria Kihl, EIT June 15, 2016 Printed in Sweden E-huset, Lund, 2016 Abstract The smart home landscape is rapidly evolving right now. There is yet to be an industry-wide common standard and several organizations are introducing their own proposed solutions. This has led to fragmentation and the field can appear confusing to interested parties trying to enter the market. There is a need to evaluate the different technologies to discern their distinguishing characteristics. This thesis report provides a comparison between HomeKit and IoTivity based on our proposed evaluation model. The model identifies a set of relevant charac- teristics which are evaluated through operationalization of criteria into composite measurables. Our comparison shows that at this time there is no definite answer to what framework to choose. Developers will have to compromise and make a decision based on the type of product they want to make. The proposed model can readily be used as a tool to evaluate any Internet of Things framework and provide guidance when choosing what technology to use.
    [Show full text]
  • The Pennsylvania State University the Graduate
    THE PENNSYLVANIA STATE UNIVERSITY THE GRADUATE SCHOOL STATE ENDORSEMENT IN THE SMART HOME IOTIVITY FRAMEWORK A Thesis in Computer Science and Engineering by Kirti Jagtap © 2020 Kirti Jagtap Submitted in Partial Fulfillment of the Requirements for the Degree of Master of Science August 2020 The thesis of Kirti Jagtap was reviewed and approved by the following: Trent Jaeger Professor of Computer Science and Engineering Thesis Advisor Mahanth Gowda Assistant Professor of Computer Science and Engineering Chitaranjan Das Distinguished Professor of Computer Science and Engineering Head of the Department of Computer Science and Engineering ii Abstract The increasing use of smart home devices has resulted in the emergence of software frameworks and automation platforms that provide scripts and Application Programming Interface (API) to develop different apps for these smart devices. Open-source platforms such as IoTivity make it easier to develop applications by providing Application Program- ming Interface. As the Internet of Things (IoT) and its applications in various domains have emerged only in the last few decades, the technology is relatively new; the developers are lacking experience and above all the complexity of Smart Home environment result in an increased number of bugs, security loopholes, and safety-critical issues leaving Smart Homes vulnerable to attacks. Since home automation is based on routines and triggers, using third-party applications or user-defined routines and custom automation [26] can lead to an unsafe and inconsistent home environment that is vulnerable to attacks thereby compromising user security and safety. These triggers and routines are dependent on the state of devices and the current home environment.
    [Show full text]
  • Iotivity Tutorial
    Tutorial Prototyping IoT devices on GNU/Linux Embedded Linux Conference #LFELC, Berlin, Germany <2016-10-13> Philippe Coval Samsung Open Source Group / SRUK [email protected] Samsung Open Source Group 1 Hallo Welt! ● Philippe Coval – Software engineer for Samsung OSG ● Belongs to SRUK team, based in Rennes, France ● Ask me for IoTivity support on Tizen platform and others – Interests ● Libre Soft/Hard/ware, Communities, Interoperability – DIY, Embedded, Mobile, Wearables, Automotive... – Find me online ● https://wiki.tizen.org/wiki/User:Pcoval Samsung Open Source Group 2 Newbies, makers, hackers welcome ! ● This “IoT” talk is not about: – Market share, prospects, growth, figures ● Monetize data with cloud, analytics, big data, machine learning – Security, privacy, trust, Skynet, singularity or any concerns – Architectures, services or designs ● Comparison of protocols or implementations ● Tizen the “OS of Everything” (unless if asked) ● It's about quick prototyping for proof of concepts: – Learn by doing from scratch, DIY: software, hardware, electronics – Feedback on previous experimentations from embedded developer – Front door to a project of 435K+ lines of code and ~500 pages of specifications Samsung Open Source Group 3 Agenda ● Prototyping ● Simplest example ● Implementation ● Hardware integration ● Demonstration ● Q&A Samsung Open Source Group 4 Motivations for prototyping ● *NOT* making a mass produced IoT device at 1st shot – Low cost (<10 $), low consumption (mW), high level of security ● Validate concepts with relaxed constraints – In friendly environment (ie: tools, security or connectivity shortcuts) – Validate, show, gather feedback, stress, benchmark, adapt, iterate ● Think of use cases first? – Or experiment with what can technology can provide? Be inspired! ● Topics and Ideas? – Controlling, monitoring, convergence, network of sensors, behaviors, AI..
    [Show full text]
  • Architecture and Features
    IOTIVITY INTRODUCTION Martin Hsu Intel Open Source Technology Center 1 Content may contain references, logos, trade or service marks that are the property of their respective owners. Agenda • Overview • Architecture • Base Layer & APIs • Primitive Services & APIs 2 IoTivity Overview OCF Topologies Supported •An open source software framework implementing OCF Standards •Ensures seamless device-to-device and OCF Client OCF Server device-to-cloud connectivity to address P2P Direct emerging needs of IoT OCF Client OCF Client •Licensed under Apache License Version XMPP/ Cloud 2.0 STUN/ TURN/ICE CoAP over TCP •Available on TIZEN, Android, Arduino, OCF Intermediary Gateway Linux(Ubuntu) Platforms Gateway OCF Servers OCF IoTivity OCF Servers Cloud based (Standards) (Open Source) Remote Access intelligent Services 3 IoTivity – High Level Architecture Rich Device Key Goals Consumer Enterprise Industrial Automotive Health …. APIs Common Solution (C/C++/Java/JS) Established Protocols Service Layer Security & Identity Lite Device Device Low-Power Data Standardized Profiles Management Management Management Sensing/Control Application Interoperability Resource Resource Encapsulation Innovation Opportunities Container Base Layer Necessary connectivity Base Layer Messaging Security Discovery Messaging Security Discovery IoTivity Profiles IoTivity Framework IoTivity Connectivities* 4 IoTivity Base Layer & APIs 5 IoTivity – High Level Architecture Rich Device Key Goals Consumer Enterprise Industrial Automotive Health …. APIs Common Solution (C/C++/Java/JS)
    [Show full text]
  • Iotivity – Connecting Things in Iot
    IoTivity – Connecting Things in IoT Ashok Subash Agenda Overview of IoT, OIC & IoTivity IoT Stack, Topologies & Protocol IoTivity Architecture Programming IoTivity Core APIs Programming IoTivity Service APIs Demo 2 Overview Internet of Things – What is it? The Internet of Things is the network of physical objects that contains embedded technology to communicate and sense or interact with the objects' internal state or the external environment.* Smart Energy Vehicle, Asset, Person, Agriculture Pet Monitoring & Consumption Controlling Security & Surveillance M2M & Wireless Internet of Things Building Sensor Network Management Telemedicine & Wearables & Smart Home Healthcare Things & Cities 4 *Gartner, July 2014 What is making IoT possible? • H/W Miniaturization & Lower BOM Cost • Advancements in Sensor Technology • Low Power Connectivity Technologies • IP as key Interoperability Protocol • Devices ability to run on battery for longer duration (> 5 years) 5 What is hindering IoT? • Non IP based standards technology resulting in limited Interoperability • Proprietary Protocols & Technologies • Licensing issues • Companies creating “Closed Ecosystem” (Zero or limited Interoperability with other Vendor devices) • Low adoption of Open Standards by various Industry Consortiums • Security & Privacy concerns • Dilemma in “Ownership” of Data from variety of IoT devices • Lack of Strong Certification for ensuring Protocol & Application Profile Interoperability Need Standards & Reference Implementation which cater to these issues 6 OIC & IoTivity • Open Interconnect Consortium (OIC) • Founded by Leading Technology Companies including Cisco, GE, Intel,, MediaTek & Samsung • Defines standards for connectivity requirements • Ensures interoperability of billions of Internet of Things (IoT) devices. • IoTivity • An open source software framework implementing OIC Standards • Ensures seamless device-to-device connectivity to address the emerging needs of the Internet of Things.
    [Show full text]
  • Etsi Tr 103 536 V1.1.2 (2019-12)
    ETSI TR 103 536 V1.1.2 (2019-12) TECHNICAL REPORT SmartM2M; Strategic/technical approach on how to achieve interoperability/interworking of existing standardized IoT Platforms 2 ETSI TR 103 536 V1.1.2 (2019-12) Reference RTR/SmartM2M-103536v112 Keywords interoperability, IoT, IoT platforms, oneM2M, SAREF, semantic ETSI 650 Route des Lucioles F-06921 Sophia Antipolis Cedex - FRANCE Tel.: +33 4 92 94 42 00 Fax: +33 4 93 65 47 16 Siret N° 348 623 562 00017 - NAF 742 C Association à but non lucratif enregistrée à la Sous-Préfecture de Grasse (06) N° 7803/88 Important notice The present document can be downloaded from: http://www.etsi.org/standards-search The present document may be made available in electronic versions and/or in print. The content of any electronic and/or print versions of the present document shall not be modified without the prior written authorization of ETSI. In case of any existing or perceived difference in contents between such versions and/or in print, the prevailing version of an ETSI deliverable is the one made publicly available in PDF format at www.etsi.org/deliver. Users of the present document should be aware that the document may be subject to revision or change of status. Information on the current status of this and other ETSI documents is available at https://portal.etsi.org/TB/ETSIDeliverableStatus.aspx If you find errors in the present document, please send your comment to one of the following services: https://portal.etsi.org/People/CommiteeSupportStaff.aspx Copyright Notification No part may be reproduced or utilized in any form or by any means, electronic or mechanical, including photocopying and microfilm except as authorized by written permission of ETSI.
    [Show full text]
  • Apple Homekit
    Avoid the silos and help build the true Internet of Things Introduction ● Aaron Vernon, CTO at Two Bulls ● Been at Two Bulls from the beginning with two stretches away at startups - CTO of Blokify and VP Software Engineering at LIFX ● Member of the AllSeen Alliance Technical Steering Committee ● I am going to cover the following: ○ The complexities of the current IoT landscape ○ How this affects companies and users ○ The Internet of Silos example ○ How we can work together better Transports WiFi ● Uses the 802.11 standard ● Standard on all mobile devices and routers ● Has become ubiquitous for users ● Great range ● Great bandwidth ● High power consumption ● High cost ● Onboarding experience can be complicated ● Examples: Nest Cam, LIFX, Canary, Honeywell Lyric Bluetooth Smart ● Standard on most mobile devices ● Becoming increasingly ubiquitous ● Low bandwidth ● Medium range ● Low power consumption ● Low cost ● Smart Mesh is being worked on ● Examples: Flic, Ilumi, Elgato Eve ZigBee ● Uses the 802.15.4 standard ● Low bandwidth ● Low range ● Low power consumption ● Very low cost ● Forms a mesh network ● Typically requires a hub for the radio ● Known to have interop and interference problems ● Examples: Phillips Hue, large amount of sensors and actuators Z-Wave ● Proprietary - chips developed by a single manufacturer ● Uses different frequencies in different countries ● Low bandwidth ● Medium range ● Low power consumption ● Very low cost ● Forms a mesh network ● Better interoperability and less interference than ZigBee ● Typically requires
    [Show full text]