requirements, building
blocks, IoT
architecture layers,,
M2M – Machine to
Machine architecture,
Web of Things,
physical layer, MAC
layer, 6LoWPAN
security aspects in IoT.
6LoWPAN
• 6LoWPAN is IPv6 over Low-Power Wireless Personal Area
Networks.
• •It optimizes IPv6 packet transmission in low power and
lossynetwork (LLN) such as IEEE 802.15.4.
• •Operates at 2 frequencies:
• •2400–2483.5 MHz (worldwide)
• •902–929 MHz (North America)
• •It uses 802.15.4 standard in unslottedCSMA/CA mode.
6LoWPAN
• Low‐power Wireless Personal Area Networks over IPv6.
• Allows for the smallest devices with limited processing
ability to transmit information wirelessly using an Internet
protocol.
• Allows low‐power devices to connect to the Internet.
• Created by the Internet Engineering Task Force (IETF) ‐
RFC5933 and RFC 4919.
6LoWPAN
• Allows IEEE 802.15.4 radios to carry 128‐bit addresses of
• Internet Protocol version 6 (IPv6).
• Header compression and address translation techniques
allow the IEEE 802.15.4 radios to access the Internet.
• IPv6 packets compressed and reformatted to fit the IEEE
802.15.4 packet format.
• Uses include IoT, Smart grid, and M2M applications.
M2M – Machine to Machine
architecture
M2M – Machine to Machine
architecture
M2M – Machine to Machine
architecture
M2M – Machine to Machine
architecture
M2M – Machine to Machine
architecture
M2M – Machine to Machine
architecture
M2M – Machine to Machine
architecture
M2M – Machine to Machine
architecture
Web of Things
• IoT has evolved with various and exclusive
designs, making it challenging to connect
different device
• can also result in vendor lock-in
• Web of Things (WoT) aims to resolve these
issues by standardizing the IoT.
Future Web of Things
• adopted and promoted by organizations like
Mozilla, Siemens, and the World Wide Web
Consortium (W3C)
• have established interest groups to define the
standards that should govern the (WoT)
• Web Thing Model represents a standardized
way to provide information on a virtual or
physical device, known as a Thing
IoT Vs WoT
• IoT solves just the network layer between
devices (example of a highway)
• IoT itself cannot help guide information to its
destination or coordinate
• WoT can be thought of as the application layer
(establish the rules of the road)
• WoT is not an alternative or competitor to IoT;
instead, it tries to enhance IoT.
IoT Vs WoT
• establish well-defined paths for data to travel
and ensure that it is compatible with its source
and destination
• WoT enables devices to connect over the web
using mainstream technologies and
standards (HTML 5.0 and Javascript)
• WoT paradigms promote RESTful API designs
WoT Architecture
• architectural standards is spearheaded by the
W3C,
• W3C’s standardization of WoT is based on
several building blocks.
• Includes-
• Thing Description,
• Binding Templates,
• Scripting API,
• Security and Privacy Guidelines.
WoT Architecture
The WoT Thing Description :
•is the basis upon which IoT devices (“Things”) can
fit into WoT.
•The Thing Description defines the metadata and
interfaces that a Thing should provide.
WoT Architecture
• Protocol Bindings refer to the protocols over
which IoT devices communicate.
• The W3C attempts to establish, Binding
Templates.
• These Binding Templates allow unique Thing
Descriptions to be modeled after and interact
with different established protocols for
communication.
WoT Architecture
• WoT Scripting API provides a common
programming language for implementing
Thing connectivity over IoT.
• This API is in the form of a JSON API.
• A device doesn’t need to use the Scripting
API to be part of the WoT, but it is convenient to
simplify application portability across platforms.
WoT Architecture
• Security and Privacy Guidelines are the most
important aspect of WoT.
• Much like the Internet itself does not define
any specific safety guidelines for applications,
neither does the Internet of Things.
• W3C has laid out the Security and Privacy
Guidelines for developers to implement
standard safety practices in Internet-connected
devices
WoT Thing Description (TD)
• is a standardized, machine-readable metadata
representation format (Instances)
• is instance-specific and is the default external,
textual (Web) representation of a Thing
• to discover and interpret the capabilities of
a Thing (through semantic annotations)
• to adapt to different implementations (e.g.,
different protocols or data structures)
WoT Thing Description (TD)
WoT Thing Model (TM)
• a logical description of the interface and
possible interaction with Thing's Properties,
Actions, and Events
• TM can be used to describe common
capabilities that are available for a set of
Things (Class of Instances)
• does not contain any instance-specific
information
WoT Thing Model (TM)
• also be used when complete information for an
instance is not available or is not necessary.
• is used to define the basic information model of
a Thing to address such kind of scenarios.
• can be seen as a template for Thing
Descriptions (TD)
WoT Thing Model (TM)
WoT Thing Model (TM) Provides
• onboarding and management of multiple Thing
models, e.g., by a cloud service.
• simulation of devices/Things that have not yet
been developed.
• developing common applications across
devices from different manufacturers that share a
common Thing model.
• combining multiple models into a Thing.
• implementation support of a concrete Thing.
WoT Links
• represent relationships between things, between
things and thing models, and between thing models
• Does not only apply to hierarchical Things, but also to
relations between Things and other resources
• Link relation types express how Things relate (a switch
controlling a light)
• Web linking among Things makes the WoT navigable,
for both humans and machines
• One example of this is an HTTP server running on an
embedded device with sensors and actuators
interfacing the physical entity
WoT Links
WoT Intermediaries
• Intermediaries are remedy in a scenario where
local networks are not reachable from the
Internet
• Has TD points to the WoT Interface provided by
the Intermediary
• act as proxies for Things
• also augment existing Things with additional
capabilities or compose a new Thing (Virtual
Thing)
WoT Intermediaries
• Affordance refers to the perceived and actual
properties of the thing, that determine just how
the thing could possibly be used
• An example for this is a door with a handle
(door can be opened - how the door can be opened
- knob suggests twisting - lever handle suggests
pressing down)
WoT - Binding Templates
• IoT uses a variety of protocols (no single
protocol is appropriate in all contexts)
• challenge for the WoT is to enable interactions
with the plethora of different IoT platforms (e.g.,
OMA LWM2M (Open Mobile Alliance Lightweight
Machine-to-Machine), OPC UA ( Open Platform
Communications United Architecture), oneM2M)
WoT - Binding Templates
• Binding Templates address the aspect that an
application client can use the TD to extract the
specific metadata of the protocols
• metadata can be passed to a network
implementation interface to establish
interaction
• include three kinds of bindings: Protocol
bindings, Payload format bindings, and
Platform bindings
Binding Templates
WoT - Binding Templates
Protocol bindings
•uses the term transport protocol for the
underlying, standardized application-layer
protocol without application-specific options or
Sub-protocol mechanisms
•URI scheme will be in the form of an Interaction
Affordance
•associated protocol endpoint URI contains the
information required to identify the transport
protocol
WoT - Binding Templates
Payload format bindings
•Representation formats used for exchanging
data can differ between protocols, IoT Platforms
and standards.
Platform bindings
•IoT Platforms and standards often introduce
specific modifications at the application layer such
as platform-specific HTTP header fields or CoAP
options.
WoT – Scripting API
• an optional "convenience" building block of W3C
WoT that eases IoT application development by
providing an ECMA Script-based API
[ECMAScript] similar to the Web browser APIs
• Enables implementing device logic by
reusable scripts executed in a runtime system
for IoT applications.
• defines the structure and algorithms of the
programming interface that allows scripts to
discover, consume, and expose WoT TD
WoT – Security and Privacy
Guidelines
• Security is supported by certain explicit features,
such as support for Public Security Metadata in
TDs and by separation of concerns in the
design of the WoT Scripting API
• each building block also includes a discussion
of particular security and privacy considerations