Protocol Standardization for

IOT
Web of Things vs. Internet of Things

• The Internet is the term used to identify the massive

interconnection of computer networks around the world.
• It refers to the physical connection of the paths between two
or more computers. 
Web of Things vs. Internet of Things
• The World Wide Web is the general name for accessing the
Internet via HTTP.
• The Internet is the large container, and the web is a part
within the container.
• The key to make the Internet of Things (IoT) takes off is the
Web of Things (WoT) which is the base of the IoT.
• The WoT is the next logical step in this IoT evolution toward
global networks of sensors and actuators, enabling new
applications and providing new opportunities.
• The internet and World Wide Web are not synonymous.
• The internet is the physical computer system that consists of
an international internetwork of networks that link millions
of computers and allow information to be transferred
between any node within the system.
• The World Wide Web is the accessible information available
over the Internet which is in the form of documents,
multimedia or any other standard file format available for
transfer over the Internet.
• The WoT explores the layer on top of connectivity with things
and addresses issues such as fast prototyping, data
integration, and interaction with objects.
• The WoT is a version where things become seamlessly
integrated into the web.
• There are also many other WoT applications around the
world. Some of the WoT applications are listed here.
1.Arduino Japan Geiger Map Nanode
2.The National Weather Study Project AgSphere 
Two Pillars of Web
Two Pillars of Web
Most important pillars of Web of Things are
1.HTTPs and Universe Resource Locator
2.Web browsers, multi tiered architecture and application
servers.
Two Pillars of the Web
• The application server became the foundation that helped
build widely spreading web-based applications.
• An application server acts as a set of components accessible
to the software developer through an API defined by the
middleware itself.
• The application server is based on the three-tiered or multi-
tiered software architecture.
• The protocols (HTML)/HTTP/URL and the software will be the
two pillars which play an important role in building WoT
applications. 
HTTPs Universe Resource Locator

• Hyperlinks plays a major role in the Web of Things. The name itself
includes web that means to connect it we need protocols like HTTPs.
HTTP transfers data between the web server and the browser in the
hypertext format, on the other hand HTTPs transfers data in the
encrypted format.
• Thus, HTTPs prevents our data from hackers from modifying and
reading the data during the transfer between the web server and the
browser. Even if the hackers managed to get the data, they can’t use it
as the data is encrypted.
• HTTPS uses the Secure Socket Layer (SSL) or Transport Layer Security
(TLS) protocols to establish an encrypted link between the web server
and the browser. TLS is the updated version of SSL.
Web browsers, Multi-tiered Architecture, Application
servers

• Everyone uses web browsers, we all know how it works and

what are its uses.
• There are three tiers- one for client, second for application
servers, third for database server.
Three Tier Architecture
• First tier is for client which includes User Interface and
Connectivity. UI is something the companies care about the
most because no matter however good functionalities your
app or site have but if it doesn’t look good, no one is going to
use it.
• UI matters the most as it creates the first impression on the
user. Everyone wants things which works and looks good.
• Connectivity is the main part when it comes to IoT. It means
all internet we got to have a better connectivity among the
devices to provide users a better and seamless experience.
• Second tier stands for application servers. WoT works on
Java-Based application servers.

• This is the logic part of the WoT which includes business

logic and presentation logic.

• This tier makes logical decisions and evaluations and

performs calculations and coordinates the application,
process commands.
• Third tier includes database servers.

• Here all the data is saved and the data access layer provides
a platform(API) to the client that helps them by showing the
possible methods of managing the data independently.
Java-Based application servers
Standards and Specifications of WoT
Web Things (WT) Requirements.

Level 0:
• A Web Thing MUST be a HTTP/1.1 server.
•  A Web Thing MUST have an access via an HTTP or URL.
•  A Web Thing MUST support PUT, GET, POST, and DELETE
HTTP methods.
•  A Web Thing MUST implement HTTPs status code 200, 400,
500.
•  A Web Thing MUST support JSON as base representation.
•  A Web Thing MUST support GET on its source URL.
Level 1:
• Secure connections (HTTPS) SHOULD be used by a Web
Thing.
•  WebSocket Protocol SHOULD be used by a Web Thing.
•  A Web Thing SHOULD support the WoT model.
•  Basic human-readable documentation SHOULD be provided
by a Web Thing.
Level 2:
• The HTTP OPTIONS method for each of its resources MAY be
supported by a Web Thing.
•  A Web Thing MAY provide additional representation tools.
•  A Web Thing MAY offer a HTML-based UI.
•  A Web Thing MAY provide accurate information about the
intended meaning of individual parts of the model.
 IoT Protocol Standardization Efforts
• No holistic approach to implement the IoT has yet been proposed.
Many island solutions do exist (RFID, sensor nets, etc.) .
The key objectives of the IoT-A consortium are as follows:
• Create the architectural foundations of an interoperable Internet of Things as a
key dimension of the larger future Internet.
• Architectural reference model together with an initial set of key building blocks.
• Not reinventing the wheel but federating already existing technologies.
• Demonstrating the applicability in a set of use cases.
• Removing the barriers of deployment and wide-scale acceptance of the IoT by
establishing a strongly involved stakeholder group Federating heterogeneous IoT
technologies into an interoperable IoT fabric.
• The emergency application space for smart objects require scalable and
interoperable communication mechanisms that support future innovation as the
application space grows.
• A smart object is defined by IPSO (Internet Protocol Smart
Object) as
An intelligent (RFID) tag
A Sensor
An actuator
An embedded device or Any combination of the above
features to form a more complex entity.
M2M and WSN Protocol
• A broad horizontal standard is a key requirement for the
M2M protocol to move from its current state of applications
existing in isolated silos based on vertical market or
underlying technology to a truly interconnected IoT.
• There are a number of standardization bodies in the field of
WSNs.
• IEEE - the physical and MAC layers
• IETF – physical and MAC layers or above
SCADA and RFID Protocols
• The Object Linking and Embedding for Process Control (OPC)
Foundation is an industry consortium that creates and
maintains standards for open connectivity of industrial
automation devices and systems.
• The OPC standards specify the communication of industrial
process data, alarms and events, historical data and batch
process data between sensors, instruments, controllers,
software systems, and notification devices.
• The smart cards with contactless interfaces (RFID is a subset)
are becoming increasingly popular for payment and ticketing
applications.
• The standard for contactless smart card communications is
ISO/IEC 14443.
Issues with IoT Standardization 
• Standardization is like a double-edged sword: critical to market
development, but it may threaten innovation and inhibit change when
standards are accepted by the market.
• The following two issues for the IoT standardization and the ICT
standardization in general may never have answers:
• ICT standardization is a highly decentralized activity. How can the
individual activities of the network of extremely heterogeneous
standards-setting bodies be coordinated?
• It will become essential to allow all interested stake-holders to
participate in the standardization process toward the IoT and to voice
their respective requirements and concerns. How can this be achieved?
THANK YOU