September 2016
Jonathan Jeon (hollobit@etri.re.kr)
ETRI
1. Web As Interface
¤ RESTful, Data-JSON/XML …
2. Web As Integration
¤ Semantic Integration, Web Services, Linked Data …
3. Web As Internet Services
¤ Open Web API, Search/Commerce, Contents, Payment …
4. Web As Application Platform
¤ HTML5/Javascript, Device APIs, Offline …
5. Web As Protocol
¤ HTTP/2, WebSocket, SSE, XHR, WebRTC, WebPush …
6. Web As Identifier
¤ URI/IRI, URL …
7. Web As User Interaction
¤ O2O, Physical Web, Web Bluetooth …
8. Web As Universal Client
¤ Browser …
¢For setup, control & management
¢For own application
¤Must install all of them
¢Platform dependent
¢Too many apps
Too many
Apps …
CAN WE FIND ANOTHER METHOD ?
>0.2B
8B
¢ Original RESTful client & navigator
¢ No installation
¢ Platform independent
¤Can use any devices
¢ Just need a Browser
¢ For basic functionality
¤Setup
¤check
¤control
¤management
There are hundreds of browsers for Android.
¢ Basic functionality
¤ Browsing UX & UI – bookmarking, subscription, user preference …
¤ On boarding & Setup
¤ Web Bluetooth & Physical Web, Web NFC …
¤ Protocol support
¤ CoAP, HTTP
¤ Local Access & Control
¤ Thing browsing – View, navigation and bookmark
¤ Thing resource control – immediate / scheduled
¤ Virtual thing access
¤ Management
¤ Setup, Security management
¤ View & Monitoring
¤ Dash board, notification/alert management
¤ Group Management
¤ Group control, group management, grouping, zone management
¤ Cloud integration – Control, Manage, Monitoring …
¢We need to find the way how web browser can act as an
universal IoT client
¤Required new functionality
¤Required implementation
Web Browser as Universal client for IoT

Web Browser as Universal client for IoT

  • 1.
    September 2016 Jonathan Jeon(hollobit@etri.re.kr) ETRI
  • 2.
    1. Web AsInterface ¤ RESTful, Data-JSON/XML … 2. Web As Integration ¤ Semantic Integration, Web Services, Linked Data … 3. Web As Internet Services ¤ Open Web API, Search/Commerce, Contents, Payment … 4. Web As Application Platform ¤ HTML5/Javascript, Device APIs, Offline … 5. Web As Protocol ¤ HTTP/2, WebSocket, SSE, XHR, WebRTC, WebPush … 6. Web As Identifier ¤ URI/IRI, URL … 7. Web As User Interaction ¤ O2O, Physical Web, Web Bluetooth … 8. Web As Universal Client ¤ Browser …
  • 4.
    ¢For setup, control& management ¢For own application ¤Must install all of them ¢Platform dependent ¢Too many apps Too many Apps …
  • 6.
    CAN WE FINDANOTHER METHOD ?
  • 7.
  • 8.
  • 9.
    ¢ Original RESTfulclient & navigator ¢ No installation ¢ Platform independent ¤Can use any devices ¢ Just need a Browser ¢ For basic functionality ¤Setup ¤check ¤control ¤management
  • 10.
    There are hundredsof browsers for Android.
  • 12.
    ¢ Basic functionality ¤Browsing UX & UI – bookmarking, subscription, user preference … ¤ On boarding & Setup ¤ Web Bluetooth & Physical Web, Web NFC … ¤ Protocol support ¤ CoAP, HTTP ¤ Local Access & Control ¤ Thing browsing – View, navigation and bookmark ¤ Thing resource control – immediate / scheduled ¤ Virtual thing access ¤ Management ¤ Setup, Security management ¤ View & Monitoring ¤ Dash board, notification/alert management ¤ Group Management ¤ Group control, group management, grouping, zone management ¤ Cloud integration – Control, Manage, Monitoring …
  • 13.
    ¢We need tofind the way how web browser can act as an universal IoT client ¤Required new functionality ¤Required implementation