From the Internet of Things to the Web of Things: Lesson from other SDOs

1. From the Internet of Things to the Web of Things: Lesson from other SDOs Gyu Myoung Lee (gmlee@etri.re.kr) Tokyo, Japan 24~26 November 2010

2. Contents • From the IoT and the WoT • Basic concept of the Internet of Things • Features and applications • Towards the Web of Things • Standardization activities of other SDOs • ETSI • 3GPP • IETF • IEEE • Others • Lesson • Discussion for Roles of ITU-T SG13

3. Ubiquitous Computing Ubiquitous Connectivity The Internet-of-Things Introduction – 1 + (Mark Weiser, Xerox Parc) = (ITU) Ambient Intelligence Related technologies: • Item identification (“tagging things”) • Sensors and WSNs (“feeling things”) • Embedded systems (“thinking things”) • Nanotechnology (“shrinking things”) • … Tangible Media Bridging the gap between the physical and virtual world

4. Introduction – 2 • In 2009: Mobile Internet is a fact. • over 25% of the world’s population – about 2 Billion people – are using the Internet • over 60% of the world’s population – about 5 Billion people – are mobile subscribers (Source: ITU) • In 2015: Personal mobile transactions & location-tracked ‘Things’ pervade our lives. • 1 Billion mobile wallets account for 90% of mobile transactions for goods & services • 100s of Billions of RFID-tagged objects, at approximately 5 cents per tag (Source: www.idtechex.com) • In 2020: Our surroundings become personal, interactive and smart. • active connections account for 25% of the tagged market • 0.1% of consumers know what is installed in their home • Already now the Internet-of-Things potentially entails 50-70 Billion ‘machines’ • In 2020: 250 embedded wireless devices/user, this 500 Billion (Source: EC, TNO)

5. The Internet of Things • The networked interconnection of everyday objects • Reliable • Secure • Scalable • Interoperable • Consistent • Pervasive • Efficient • Coherent • Role for network – Integrate all kinds of objects

6. Connected devices

8. From the IoT to the WoT Each Physical entity can be part of the Web. Physical entities are marked in the real-world and become a part of the virtual world. The integration of the physical world with the Web offers unique opportunities to enable ubiquitous computing applications.

9. Web enabled objects User-created Web-of-Things Applications Web’s easy application creation IoT’s abundance of connected smart objects Web of Things • Delivering web content • Capacity to query and process data streams • Publishing content • Capacity to send data through APIs • Triggering other objects • Capacity to interoperate and share data • Adapting their behavior • Capacity to interpret data steams

10. Web of Things • From Wikipedia, the free encyclopedia • The Web of Things is a vision inspired from the Internet of Things where everyday devices and objects, i.e. objects that contain an Embedded devices or computer, are connected by fully integrating them to the Web. Examples of smart devices and objects are Wireless Sensor Networks, Ambient devices, household appliances, etc. • Unlike in the many systems that exist for the Internet of things, the Web of Things is about re-using the Web standards to connect the quickly expending eco-system of Embedded devices built into everyday smart objects. Well-accepted and understood standards and blueprints (such as URI, HTTP, REST, RSS, etc.) are used to access the functionality of the smart objects.

11. Web of Things 1.0, 2.0 & 3.0 – 1 WoT1.0 Collection of Things rather than a “Web” of Things. Abundance of dedicated standards. IP is no standard (yet ?) for interaction with Things. M2M versus entertainment & media.

12. Web of Things 1.0, 2.0 & 3.0 – 2 Users & communities engage in creating content & applications. WoT2.0 WoT1.0 How to search or discover Things ? Can Web2.0 be applied to user resources ? Things are constrained devices: what about resource mgt., access control, policies, distributed execution, … ? Can existing Mashup frameworks be applied to a mix of Things and online Services ? HTTP HTTP Web2.0 for Things (RESTful HTTP over IP) RESTful API

13. Web of Things 1.0, 2.0 & 3.0 – 3 WoT2.0 WoT1.0 WoT3.0 Users & communities engage in creating content & applications. Support for discovering, searching, and composing Things and Services. Semantic framework (with user defined semantics) allowsto articulate and define applications in terms of proper (& personal) concepts. Aggregation, Abstraction & Resource management. IP & REST full interfaces Search Composition Catalog Recipes Wizards HTTP HTTP Collaborative Semantics Aggregation Resource Mgt. Abstraction

14. Swarm-of-Nodes Web3.0 Web-of-Things Internet-of-Things Ubiquitous Computing Network of Objects Ambient Intelligence M2M “Programming” the Web of Things Web2.0’s Easy Application Creation Internet-of-Things’ Abundance of Connected Smart Objects 14

15. Standardization activities of other SDOs

16. ETSI • TC M2M opens in January 2009 • Term of Reference • to collect and specify M2M requirements from relevant stakeholders; • to develop and maintain an end-to-end overall high level architecture for M2M; • to identify gaps where existing standards do not fulfil the requirements and provide specifications and standards to fill these gaps, where existing standards bodies or groups are unable to do so; • to provide the ETSI main centre of expertise in the area of M2M; • to co-ordinate ETSI’s M2M activity with that of other standardization groups and fora.

17. “Connecting Things” cluster Machine-to-Machine eHealth Wireless Factory Cloud Computing RFID Connected Consumer Smart Metering Smart City

18. TR 102 732: eHealth TR 102 897:City automation TR 102 898: Automotive TR 102 692:Smart Metering TR 102 857: Connected consumer TS 102 689 :M2M Service Requirements TS 102 690 :M2M Functional Architecture TR 102 725:M2M Definitions Work Methodology, a stepwise approach Use Case Technical Reports Stage 3 TSs

19. High-level system architecture

20. ETSI M2M high level system view

21. Key Elements of M2M Architecture • M2M Device • A device that runs application(s) using M2M capabilities and network domain functions. • An M2M Device is either connected straight to an Access Network or interfaced to M2M Gateways via an M2M Area Network. • M2M Area Network • A M2M Area Network provides connectivity between M2M Devices and M2M Gateways. Examples of M2M Area Networks include: Personal Area Network technologies such as IEEE 802.15, SRD, UWB, Zigbee, Bluetooth, etc or local networks such as PLC, M-BUS, Wireless M-BUS. • M2M Gateways • Equipments using M2M Capabilities to ensure M2M Devices interworking and interconnection to the Network and Application Domain. • The M2M Gateway may also run M2M applications.

22. Key Elements of M2M Architecture • M2M Core • Composed of Core Networks and Service Capabilities • Service Capabilities • Provide functions that are shared by different applications. Expose functionalities through a set of open interfaces. • Use Core Network functionalities and simplify and optimize applications development and deployment whilst hiding network specificities to applications. • Examples include: Data Storage and Aggregation, Unicast and Multicast message delivery, etc. • M2M Applications (Server) • Applications that run the service logic and use Service Capabilities accessible via open interfaces.

23. Capabilities • Capabilities under development • Generic Message delivery (GM) • Reachability, Addressing and Device Application Repository (RADAR) • Network and Communication Service Selection (NCSS) • M2M Device and M2M Gateway Management (MDGM) • Security Capability (SC) • History and Data Retention (HDR) • Transaction Management (TM) Capability • Compensation and billing

24. 3GPP • M2M in 3GPP – the reason • Interoperable Solution • Endure Interoperability • Product Innovation • Encourages innovation through R&D • New Markets • Expands markets • Standards Solution • Reduces cost • Regulatory Requirements • Satisfies essential regulatory requirement

25. 3GPP • MTC : Machine Type Communication • MTCu : provides MTC devices access to the 3GPP network for the transport of user traffic • MTCi : the reference point for MTC server to connect the 3GPP network via 3GPP bearer service • MTCsms : the reference point for MTC server to connect the 3GPP network via 3GPP SMS Architecture

26. 3GPP Communication scenario with MTC Devices communicating with MTC Server. MTC Server is located in the operator domain. MTC Devices communicating directly with each other without intermediate MTC Server Communication scenario with MTC Devices communicating with MTC Server. MTC Server is located outside the operator domain. Scenarios

27. 3GPP • Features • Low Mobility • Time Controlled • Time Tolerant • Packet Switched (PS) only • Online small Data Transmissions • MTC Monitoring • Offline Indication • Jamming Indication • Priority Alarm Message (PAM) • Extra Low Power Consumption • Secure Connection • Location Specific Trigger • Group based MTC Features

28. 3GPP • Issues • Access Agnostic • Data format of M2M applications • Naming, Address and routing • Alternative addressing solution based on IP addresses should be studies • Service levels and QoS • New QoS profiles needs to be defined • Security, authentication, data integrity, privacy • Security association shall be maintained between “machines” • Interconnect and interworking • Inter-communication via RATs

29. 3GPP • Documents • TR 22.868, Study on Facilitating Machine to Machine Communication in 3GPP Systems • TR 33.812, Remote Management of USIM applications on M2M • TS 22.368, Network Improvements for M2M and M2H type • Communications Rel. 10

30. IRTF IoT • 1st meeting (77th IETF) • Identifies several items to be discussed in the future • Make a discussion group • iot-irtf-discussion@googlegroups.com • 2nd meeting (78th IETF) • Initiate a new work for PS document and charter • 3rd meeting (79th IETF) • Discuss the initial PS document and a draft charter • Preliminary work to create a new research group on the IoT in the IRTF • To identify various issues for IoT • To select candidate topics for future work (Scoping) • To determine To-Do-List for next meeting • Next steps

31. Concept and scope • IoT • Definition • Things • Scope • Classification and characteristics of objects • Size, Mobility, Power, Connectivity, Automation, Physical/logical, Network protocol, etc • Purpose/applications • Body area network, Smart Grid, Building networks, Vehicles (inter and intra), RFID/Asset-tracking, Manufacturing, Environmental sensors. Revealing/sharing information

32. Features of IoT • Overall aspects • Order(s) of magnitude bigger than the Internet, No computers or humans at endpoint, Inherently mobile, disconnected, unattended • Applications/services aspects • Networking aspects • Link/physical layer aspects • Smart/connected objects aspects • Smart environment aspects (home/office/building, etc)

33. Problem statement – 1 • Identifier for objects and services • Various kinds of identifier with different identification codes according to objects and their services. • Object naming • The end points of current Internet are hosts  Naming services for objects • Security/privacy/authority • The diversification of the Internet with new types of devices and heterogeneous networks  ID management for things • Presence (of people; of devices) • Geographic location (self identification of location) • Discovery/search • Tracking of mobile object

34. Problem statement – 2 • Data processing /computing • Information model (data store, retrieval, transfer, etc) • Policy/preferences • Heterogeneous networking interfaces (IP and non-IP, etc) • Interworking model with proxy (gateway) • Global connectivity (IPv6) • End-to-end communications • Scalability • Universal interoperability • Autonomics (self-configuring, intelligence for control) • Remote control and management/maintenance of objects • Power/energy storage • Coordination among many objects • Full-function device (FFD), Reduced Function Devices (RFD), etc • Web Services

35. Relationship with other WGs 6LoWPAN (IPv6 header compression) ROLL (IPv6 routing for low power/lossy networks) Core (Constrained RESTful Environments, former 6LoWApp (Low power applications) BoF) RRG (Routing research group) HIPRG (Host identity protocol research group) Light Weight IP Protocol Design BoF

36. IoT – Building Network definition “Devices that people interact with in daily life” By definition, have IP connectivity People experience – can touch, pick up, hear, smell, get light from, get heat from, see through, go through, … Need standard interfaces to people Concepts embodied in devices need to be derived from what is in people’s heads

37. Draft Charter • Mission • To develop a new architectural framework in order to solve problems and propose solutions • Work items • Framework and problem statement • Understanding of IoT in the viewpoint of IETF (Clear scope of IoT work) • Requirements • Design goals • Architecture for IoT • Naming and addressing to support IoT • Solution spaces • ONS (object naming service) • Protocols for device control

38. Next step • Formal BoF at the next IETF meeting • Cutoff date for BOF proposal requests (Jan. 31, 2011) • Update PS document • Develop draft charter

39. IEEE PES (Personal Environment Services) • IEEE P802.15 Working Group for Wireless Personal Area Networks (WPANs) • Purpose • As the mature stage of ubiquitous environment, it becomes possible to make surroundings to be realized electrically, and to control them by ones’ desire. • PES services are based on • automatically construct personal environment by controlling surrounding electric machines, using pre-defined and self growing personal preference information, and service server.

40. Conceptual diagram of PES

41. Necessity of PES • Intelligent configuration for convenient & comfort human living environment • As a person moves to new position, the environment surrounding the one is supposed to be changed. • Then the one should resign the one’s unique environment or should newly set it up, whenever the one moves. • For energy saving • Minimum operation of electric machine • For security • Using checkpoints, find the one’s moving track

42. Reference model of PES

43. Scope of PES Ubiquitous Service Network Wireless/wireline comm. network Electric/electronic machine Human Context- awareness Sensors Main coverage of ubiquitous service entities

44. Other activities NFC Forum (www.nfc-forum.org) “…advance the use of Near Field Communication technology by developing specifications, ensuring interoperability among devices and services, and educating the market about NFC technology.” TouchaTag (www.touchatag.com) • B2B Mobile Payment, loyalty, vouchers • B2C DiY Internet-of-Things EPC-Global (www.epcglobalinc.org) “…development of industry-driven standards for the Electronic Product Code™ (EPC) to support the use of RFID in today’s fast-moving, information rich, trading networks.” CASAGRAS (www.rfidglobal.eu) “…propose an approach using Object Identifiers and Unique Item Identifier (UII) concepts and namespace resolver to accommodate legacy coding schemes for identification.” • Considering a range of standards, including those from ISO, IEC and EPCglobal6. • Supports a value proposition that exploits a defined infrastructure and provides scope for commercial venture – federated services and applications. And many, many more …

45. Other activities IPSO Alliance - Internet Protocol for Smart Objects • 50+ members (Atmel, Bosch, Cisco, EDF (Électricité de France), Ericsson, Freescale, Google, SAP, Sun Microsystems, Texas Instruments, …) Objectives • IP as the solution for access and communication for Smart Objects. • Promote the use of IP in Smart Objects (white papers, case studies, updates on standards progress (IETF, etc)…. • Understand industries and markets where IP Smart Objects can have a role. • Organize interoperability tests. • Support IETF and other standards development organizations in standardizing IP for Smart Objects. • www.ipso-alliance.org

46. Other activities Pachube (“patch-bay”: generalized data brokerage) "Tag and share real time sensor data from objects, devices, buildings and environments around the world. The key aim is to facilitate interaction between remote environments, both physical and virtual." • Extended Environments Markup Language (EEML) to realize “dynamic, responsive and conversant environments”.

47. Lesson from other SDOs • Most of relevant SDOs are developing related standards for the IoT. • Different approaches depending their specialized areas • ITU-T SG13 • We already started this work. • However, there is no consensus for on-going issues within SG13. • Through gap analysis, let’s find right directions for future standardization

48. Discussion for Roles of ITU-T SG13 • Key items for future standardization in ITU-T SG13 • Many related on-going working items in SG13 • UbiNet, USN, MOC, O2O, WoT, etc • New items • Consolidated architecture, capabilities, mechanisms • Directions for future standardization • Enhancement of NGN vs. Future Network • Synergic approach with all experts • Collaborating this work with all related questions within SG13

49. Collaboration

50. Thank you www.tta.or.kr