IoT Protocol Standardization

Contents

1. IOT and WOT

2. INVENTION OF HTML
3. THE APPLICATION SERVER
4. 2 PILLARS OF THE WEB
5. WHY STANDARDISATION
6. IPSO AND ALL IP
7. M2M AND WSN PROTOCOL
8. SENSOR DATA
9. SCADA AND RFID PROTOCOLS
10. OPC
11. ISSUES WITH IOT STANDARDISATION
IOT AND WOT

 The Internet of Things (IoT) describes the network of physical objects—“things”—that

are embedded with sensors, software, and other technologies for the purpose of connecting
and exchanging data with other devices and systems over the internet.
 The Web of Things explores the layer on top of connectivity with things and addresses
issues such as fast prototyping, data integration, and interaction with objects
Some of the WoT applications are-
• Arduino
• Japan
• Geiger Map
INVENTION OF HTML
 

 The invention of HTML/HTTP/URL on top of TCP/IP-based Internet started the Internet

revolution
 However, it was not until the killer application—Netscape web browser surfaces that the
Internet revolution, symbolized by the World Wide Web, really took off..
 
 THE APPLICATION SERVER
 

 An application server is a server that hosts 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 as shown is the figure or multitier
software architecture.
2 PILLARS of the Web
 
 The two pillars for web applications and the Internet revolution
• The protocols
• The software
Working Group
WHY STANDARDISATION

Internet of Things aims to connect various things around us to the Internet with the use of
smart sensors and actuators.
IoT devices have limited resources in terms of power, processing capabilities, bandwidth etc.
but the existing set of protocols were not designed for such constraints.
The current status of IoT standardization as follows:
◾ Fragmented architectures, no coherent unifying concepts, solutions exist only for
application silos.
◾ No holistic approach to implement the IoT has yet been proposed.
◾ Many island solutions do exist (RFID, sensor nets, etc.).
◾ Little cross-sector reuse of technology and exchange of knowledge.
IPSO AND ALL IP

 IPSO (Internet Protocol for Smart Objects) is an alliance aiming to form an open group of
companies to market and educate about how to use IP for IoT smart objects based on an
all-IP holistic approach.
 The emerging application space for smart objects requires scalable and interoperable
communication mechanisms that support future innovation as the application space grows.
 IP has proven itself a long-lived, stable, and highly scalable communication technology
that supports a wide range of applications, devices, and underlying communication
technologies.
 The IP stack is open, lightweight, versatile, ubiquitous, scalable, manageable, stable, and
end-to-end. It can run on tiny, battery-operated embedded devices.
 IP therefore has all the qualities to make the Internet of Things a reality, connecting
billions of communicating devices.
M2M and WSN Protocols

 The high-level M2M architecture from MSTF does include fixed and other no cellular
wireless networks, which means it’s a generic, holistic IoT architecture even though it is
called M2M architecture.
 Despite all of the positives, efforts to incorporate existing SCADA standards such as OPC,
ISA-95, and RFID EPCIS, ONS, and others are not seen yet.
 Although it is a more comprehensive approach than the 3GPP’s MTC(Machine type
communication) .
 SENSOR DATA

 Sensor data is the output of a device that detects and responds to some type of input from
the physical environment. 
 the ability to access and use the same sensors in multiple application domains, to share
sensor data, and to maximize the full value of sensor networks and data is severely
hindered by a lack of interoperability.
SCADA AND RFID PROTOCOLS

 It stands for Supervisory Control and Data Acquisition. It’s one of the IoT pillars to
represent the whole industrial automation arena.
 In recent years, network-based industrial automation has greatly evolved with the use of
intelligent electronic devices (IEDs), or IoT devices in our terms.
 In substations and power stations the processing is now distributed, and functions that used
to be done at the control center can now be done by the IED, that is, M2M between
devices.
 Despite the fact that many functions can be moved to the IED, utilities still need a master
station, the IoT platform, for the operation of the power system.
 OPC
 OPC, which stands for Object Linking and Embedding (OLE) for Process Control, is the
original name for a standard specification developed in 1996 by an industrial automation
industry task force.

 OPC has achieved great success in many application areas, most of them closely related to
or part of IoT applications. However, OPC’s success story is accompanied by some
caveats.
 For example, standard OPC DA (data access) is based on Microsoft’s COM and DCOM
technology and is consequently restricted to the Windows operating system.
ISSUES WITH IOT STANDARDISATION

It should be noted that not everything about standardization is positive. 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.
 Different consortia, forums and alliances have been doing standardization in their own
limited scope . For example, 3GPP covers only cellular wireless networks while
EPCglobal’s middleware covers only RFID events
 Even though some of the IoT standard organizations have cooperation and interaction, it is
limited and not open enough.
 The following two issues for the IoT standardization in particular 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 stakeholders to participate in the
standardization process toward the IoT and to voice their respective requirements and
concerns. How can this be achieved?
 The only, or at least better, possible solution to address these chaotic situations is to try to
standardize the omnipresent middleware and the XML-based data representation from
across-industry organizations such as World Wide Web, Consortium (W3C), Organization
for the Advancement of Structured Information Standards (OASIS), and others.
THANKYOU !