Diese Präsentation wurde erfolgreich gemeldet.
Die SlideShare-Präsentation wird heruntergeladen. ×

IoT and WoT (Internet of Things and Web of Things)

Anzeige
Anzeige
Anzeige
Anzeige
Anzeige
Anzeige
Anzeige
Anzeige
Anzeige
Anzeige
Nächste SlideShare
Wot
Wot
Wird geladen in …3
×

Hier ansehen

1 von 28 Anzeige

IoT and WoT (Internet of Things and Web of Things)

Herunterladen, um offline zu lesen

Talk on 1st WebAppsCamp. It's a short review between IoT and WoT. In this slide, I'd like to talk about why we need to think about Web of Thing in IoT era.

Talk on 1st WebAppsCamp. It's a short review between IoT and WoT. In this slide, I'd like to talk about why we need to think about Web of Thing in IoT era.

Anzeige
Anzeige

Weitere Verwandte Inhalte

Diashows für Sie (20)

Andere mochten auch (20)

Anzeige

Ähnlich wie IoT and WoT (Internet of Things and Web of Things) (20)

Weitere von Jonathan Jeon (20)

Anzeige

Aktuellste (20)

IoT and WoT (Internet of Things and Web of Things)

  1. 1. IoT and WoT (Internet of Thing & Web of Things) Jonghong Jeon ETRI, PEC Email: hollobit@etri.re.kr Blog: http://mobile2.tistory.com http://twitter.com/hollobit http://www.etri.re.kr
  2. 2. The era of Source: http://www.theconnectivist.com/2014/05/infographic-the-growth-of-the-internet-of-things/
  3. 3. 3 Change – Internet Remix
  4. 4. 4 Changes - Connected Things More things are connecting to the Internet than people — Cisco’s Internet Business Solutions Group (IBSG) predicts some 25 billion devices will be connected by 2015, and 50 billion by 2020
  5. 5. 5 Changes – Emerging Open Source Hardware
  6. 6. 6 M2M & IoT
  7. 7. 7 Too many Players https://www.cbinsights.com/blog/tech-periodic-table/
  8. 8. 8 Too Many Connection Technology
  9. 9. 9 Hello, Ciao, Grüetzi…  IoT needs standards  Too many standards means no standard  Big companies grouped in consortiums  Communication protocols must meet low-bandwidth requirements  Interoperability at server level is not always the best solution Soure: http://www.slideshare.net/paolopat/internet-of-things-my-washing-machine-on-internet
  10. 10. 10 different visions on ‘‘Internet of Things” Source: Luigi Atzori, “The Internet of Things: A survey”, October 2010
  11. 11. Consideration 1: Back to Basic
  12. 12. 12 Is coming “Age of IoT” ? Really ?
  13. 13. 13 Is coming “Age of IoT” ? Really ? Source: http://designswarm.com/blog/2014/02/the-past-10-years-of-the-internet-of-things/
  14. 14. 14 Don’t forget the Value and Usability Source: https://twitter.com/cnetnews/status/243783603807461376
  15. 15. 15 야심찬 신제품이 시장서 실패하는 이유 “기업은 소비자들이 신제품의 새로운 효용에 매료될 것이라고 생각하지만 실 제로 소비자들은 가격이 적절한지, 기존 소비 습관을 바꿀만한 것인지, 사회적 행동의 변화를 가져올만한 것인지 등 심리적 요인에 영향을 받는다. 이 때문에 소비자의 구매를 유도하기 위해서는 다각도로 소비자 심리에 접근해야 한다.” http://magazine.hankyung.com/apps/news?popup=1&nkey=2013112800939000381&mode=print_view
  16. 16. 16 야심찬 신제품이 시장서 실패하는 이유 “기업은 소비자들이 신제품의 새로운 효용에 매료될 것이라고 생각하지만 실 제로 소비자들은 가격이 적절한지, 기존 소비 습관을 바꿀만한 것인지, 사회적 행동의 변화를 가져올만한 것인지 등 심리적 요인에 영향을 받는다. 이 때문에 소비자의 구매를 유도하기 위해서는 다각도로 소비자 심리에 접근해야 한다.” http://magazine.hankyung.com/apps/news?popup=1&nkey=2013112800939000381&mode=print_view
  17. 17. 17 Back to Basic – Service History
  18. 18. 18 Back to Basic – Internet Users
  19. 19. 19 IoT Scenario Source: OIC
  20. 20. Consideration 2: Next Web Application ?
  21. 21. 21 Evolution of World Wide Web
  22. 22. 22 But , Web Technology for Small Connected Things ? Half of connected devices will be small IoT devices (how we can bring those devices into the web ecosystem) We need to consider these small devices
  23. 23. 23 Characteristics of Small Connected Thing  Connectivity  Locally, Globally  Wired, Wireless  Controllability  One way, Two way  Immediately, …  Interactivity  Interaction ability – screen, sound, light …  Limitations  Low Computing power  Device capability  Non-screen
  24. 24. 24 Traditional Web Architecture Web Resources URI/IRI RESTful Web Connectivity Presentation purpose (for human interaction)
  25. 25. 25 Simple WoT Architecture Web Resources RESTful Small device Small device What kind of request ? What kind of response ? Do we need to use HTML/CSS markup ? which kind of web client do we need ? Web Connectivity Control purpose (for automatize interaction) Client/Server Client/Server
  26. 26. 26 Web Architecture for Non-screen Devices Absence of Presentation Layer
  27. 27. 27 Conclusions
  28. 28. 28 JongHong Jeon (hollobit@etri.re.kr) +82-42-860-5333 http://facebook.com/jonathan.jeon http://twitter.com/hollobit

×