Protocol Standardization For Iot: Unit-Ii
Protocol Standardization For Iot: Unit-Ii
Protocol Standardization For Iot: Unit-Ii
IOT PROTOCOLS: Protocol Standardization for IoT – Efforts – M2M and WSN Protocols –
SCADA and RFID Protocols – Issues with IoT Standardization – Unified Data Standards –
Protocols – IEEE802.15.4–BACNet Protocol– Modbus – KNX – Zigbee– Network layer – APS
layer – Security
—----------------------------------------------------------------------------------------------------------------------------
IoT communication protocols are modes of communication that protect and ensure optimum
security to the data being exchanged between connected devices.
The IoT devices are typically connected to the Internet via an IP (Internet Protocol) network.
However, devices such as Bluetooth and RFID allow IoT devices to connect locally. In these
cases, there’s a difference in power, range, and memory used. Connection through IP networks
are comparatively complex, requiring increased memory and power from the IoT devices while
the range is not a problem. On the other hand, non-IP networks demand comparatively less
power and memory but have a range limitation.
As far as the IoT communication protocols or technologies are concerned, a mix of both IP and
non-IP networks can be considered depending on usage.
Types of IoT ProtocolsTypes of IoT Protocols: IoT protocols and standards can be broadly
classified into two separate categories.
1. IoT Network Protocols: IoT network protocols are used to connect devices over the
network. These are the set of communication protocols typically used over the Internet.
Using IoT network protocols, end-to-end data communication within the scope of the
network is allowed. Following are the various IoT Network protocols:
● HTTP (HyperText Transfer Protocol): HyperText Transfer Protocol is the best
example of IoT network protocol. This protocol has formed the foundation of data
communication over the web. It is the most common protocol that is used for IoT
devices when there is a lot of data to be published. However, the HTTP protocol
is not preferred because of its cost, battery-life, energy saving, and more
constraints.
Additive manufacturing/3D printing is one of the use cases of the HTTP protocol.
It enables computers to connect 3D printers in the network and print
three-dimensional objects and pre-determined process prototypes.
● LoRaWan (Long Range Wide Area Network): It is a long-range low power
protocol that provides signal detection below the noise level. LoRaWan connects
battery operated things wirelessly to the Internet in either private or global
networks. This communication protocol is mainly used by smart cities, where there
are millions of devices that function with less power and memory. Smart street
lighting is the practical use case of LoRaWan IoT protocol. The street lights can be
connected to a LoRa gateway using this protocol. The gateway, in turn, connects to
the cloud application that controls the intensity of light bulbs automatically based
on the ambient lighting, which helps in reducing the power consumption during
day-times.
● Bluetooth: Bluetooth is one of the most widely used protocols for short-range
communication. It is a standard IoT protocol for wireless data transmission. This
communication protocol is secure and perfect for short-range, low-power,
low-cost, and wireless transmission between electronic devices. BLE (Bluetooth
Low Energy) is a low-energy version of Bluetooth protocol that reduces the power
consumption and plays an important role in connecting IoT devices. Bluetooth
protocol is mostly used in smart wearables, smartphones, and other mobile
devices, where small fragments of data can be exchanged without high power and
memory. Offering ease of usage, Bluetooth tops the list of IoT device connectivity
protocols.
● ZigBee: ZigBee is an IoT protocol that allows smart objects to work together. It is
commonly used in home automation. More famous for industrial settings, ZigBee
is used with apps that support low-rate data transfer between short distances.
Street lighting and electric meters in urban areas, which provides low power
consumption, use the ZigBee communication protocol. It is also used with
security systems and in smart homes.
2. IoT Data Protocols: IoT data protocols are used to connect low power IoT devices.
These protocols provide point-to-point communication with the hardware at the user side
without any Internet connection. Connectivity in IoT data protocols is through a wired or
a cellular network. Some of the IoT data protocols are:
● Message Queue Telemetry Transport (MQTT): One of the most preferred
protocols for IoT devices, MQTT collects data from various electronic devices
and supports remote device monitoring. It is a subscribe/publish protocol that runs
over Transmission Control Protocol (TCP), which means it supports event-driven
message exchange through wireless networks. MQTT is mainly used in devices
which are economical and requires less power and memory. For instance, fire
detectors, car sensors, smart watches, and apps for text-based messaging.
● Constrained Application Protocol (CoAP): CoAP is an internet-utility protocol
for restricted gadgets. Using this protocol, the client can send a request to the
server and the server can send back the response to the client in HTTP. For
light-weight implementation, it makes use of UDP (User Datagram Protocol) and
reduces space usage. The protocol uses binary data format EXL (Efficient XML
Interchanges). CoAP protocol is used mainly in automation, mobiles, and
microcontrollers. The protocol sends a request to the application endpoints such
as appliances at homes and sends back the response of services and resources in
the application.
● Advanced Message Queuing Protocol (AMQP): AMQP is a software layer
protocol for message-oriented middleware environment that provides routing and
queuing. It is used for reliable point-to-point connection and supports the
seamless and secure exchange of data between the connected devices and the
cloud. AMQP consists of three separate components namely Exchange, Message
Queue, and Binding. All these three components ensure a secure and successful
exchange and storage of messages. It also helps in establishing the relationship of
one message with the other. AMQP protocol is mainly used in the banking
industry. Whenever a message is sent by a server, the protocol tracks the message
until each message is delivered to the intended users/destinations without failure.
● Machine-to-Machine (M2M) Communication Protocol: It is an open industry
protocol built to provide remote application management of IoT devices. M2M
communication protocols are cost-effective and use public networks. It creates an
environment where two machines communicate and exchange data. This protocol
supports the self-monitoring of machines and allows the systems to adapt
according to the changing environment. M2M communication protocols are used
for smart homes, automated vehicle authentication, vending machines, and ATM
machines.
● Extensible Messaging and Presence Protocol (XMPP): The XMPP is uniquely
designed. It uses a push mechanism to exchange messages in real-time. XMPP is
flexible and can integrate with the changes seamlessly. Developed using open
XML (Extensible Markup Language), XMPP works as a presence indicator
showing the availability status of the servers or devices transmitting or receiving
messages. Other than the instant messaging apps such as Google Talk and
WhatsApp, XMPP is also used in online gaming, news websites, and Voice over
Internet Protocol (VoIP).
● Platform: This part includes the form and design of the products (UI/UX), analytics tools
used to deal with the massive volume of data streaming from all products in a secure way,
and scalability which means that wide adoption of protocols like IPv6 in all vertical and
horizontal markets is needed.
● Business Model: The bottom line is a big motivation for starting, investing in, and
operating any business; without a sound and solid business model for IoT we will have
another bubble , this model must satisfy all the requirements for all kinds of e-commerce;
vertical markets, horizontal markets and consumer markets. But this category is always a
victim of regulatory and legal scrutiny.
● Killer Applications: In this category there are three functions needed to have killer
applications: control "things", collect "data", and analyze "data". IoT needs killer
applications to drive the business model using a unified platform.
● Security: IoT encompasses everything from wireless communications, sensors,
Radio-Frequency Identification (RFID) to Machine-to-Machine (M2M). However, the
IoT industry is still unregulated, which has led to wider security and privacy implications.
The ease with which IoT devices can be hacked, packet data sniffed and unsecured
firmware can be modified, is alarming. Attacks are heterogeneous in nature and can occur
at every layer of IoT’s protocol stack. We need to have regulation, robust security
mechanisms and stricter controls over authentication of devices that are connected to the
Internet
● Governance: Effective governance within the IoT industry is an important consideration.
Due to IoT’s entry into almost every industry, malicious back-door passage led by
vulnerable devices may not be immediately apparent, but it opens up new avenues of
cyber attack on a much larger scale. Governance on an international level, such as rules,
processes, procedures, audits, accountability and coherence are also currently
non-existent in the IoT domain, due to the absence of general legislation in the IoT
industry. Such levels of legislation at an industry, national and international level can be
extremely helpful in aiding the organisations with improved efficiency and reliability of
systems, as well as reduce the possibility of future errors. The involvement of
heterogeneous technologies and the broad range of services used to support IoT, an
effective governance plan is harder to achieve, but not impossible.
● Connectivity: Connecting billions of devices or things is a major challenge. Connectivity
impacts the scale of business, profit margin, and societal impact of the operation. Though
cloud-based deployments rule the IoT world, edge-based deployments are picking up due
to (i) low latency, (ii) ease of deployment, (iii) better security and privacy, and (iv) high
data aggregation.
● Interoperability: The IoT is growing in various directions, and different technologies are
playing different roles. Today, Wireless Fidelity (WiFi), Zigbee, Long-Term Evolution
(LTE), LTE Advanced (LTE-A), Low-Power Wide Area Network (LPWAN), Bluetooth,
etc., are some of the major communication technologies rule the IoT world. Seamless
connectivity with different devices operating in different technologies is a major
challenge. Interoperation at higher layers of the network protocol stack involving
semantics, and domain-specific operations is another challenge.
● IoT analytics: The basic nature of the IoT is to obtain and to act on information.
Therefore, IoT analytics play a major role. For practical deployment, placing the
analytics platform in the IoT architecture is the major issue. Since information is
generated or gathered at the devices and is communicated to the cloud with/without the
support of edge, decision has to be taken such that parts of the analytics platform have to
be deployed in appropriate places of the framework, i.e. whether at edge/fog or at the
cloud. Factors such as delay, regulatory issues, cost, scale and ease of operation, etc., play
significant roles on this.
● Security and privacy: It has been observed that IoT deployments are prone to security
and privacy issues at device, edge, and cloud platform level. Therefore, security and
privacy of the data, device, application, and the server are to be considered while
deciding appropriate deployment architecture. Instead of considering security and privacy
as afterthoughts of deployment, today, these are the prime concerns for any kind of
deployment.
● Business or return on investment (RoI): Deployment decision can impact the vertical,
horizontal, and consumer markets of IoT industry while struggling with the regulatory
and legal aspects of the society. Based on the deployment usage and client base, IoT can
be divided into (i) consumer IoT, which impacts the mass (like wellness, education, etc.)
and the governance in the society; (ii) industrial IoT, which governs the communication
framework of Industry 3.0 or Industry 4.0 scenarios; and (iii) commercial IoT, which
includes retail and warehouse inventory controls, device tracking, health services, and so
on.
● Societal: Societal challenges also play a major role in IoT deployment as IoT has to
satisfy the customer, developer, and regulator needs of the society. This includes the
mode of usage, the energy consumption, environmental impact, societal impact, etc.
M2M: Machine-to-Machine Communications
M2M technology may be present in offices, shopping malls, houses, and many other places. A
common example of a machine to machine is controlling electrical devices like fans and bulbs
using Bluetooth from the smartphone. Here, the smartphone and electrical devices are the two
interacting devices with each other.
● IoT is a subset of M2M technology. In IoT, the communication between two machines
without human instruction, making it a part of the M2M communication system.
● The point-to-point communication of M2M is the main difference between M2M and IoT
technology. Meanwhile, an IoT system usually locates its devices within a global cloud
network that facilitates larger-scale automation and more advanced applications.
● Another key difference between IoT and M2M is scalability. IoT is designed to be highly
scalable because devices may also be included in the network and integrated into existing
networks with minimal issues. In contrast, maintaining and setting up M2M networks
could also be more labor-intensive, as new point-to-point connections must be built for
each system.
1. MQTT (Message Queuing Telemetry Transport) protocol: MQTT stands for Message
Queuing Telemetry Transport. MQTT is a machine to machine internet of things
connectivity protocol. It is an extremely lightweight and publish-subscribe messaging
transport protocol. This protocol is useful for the connection with the remote location
where the bandwidth is a premium. These characteristics make it useful in various
situations, including a constant environment such as for communication machine to
machine and internet of things contexts. It is a publish and subscribe system where we
can publish and receive the messages as a client. It makes it easy for communication
between multiple devices. It is a simple messaging protocol designed for the constrained
devices and with low bandwidth, so it's a perfect solution for the internet of things
applications.
Characteristics of MQTT
The MQTT has some unique features which are hardly found in other protocols. Some of the
features of an MQTT are given below:
MQTT Architecture
To understand the MQTT architecture, we first look at the components of the MQTT.
● Message: The message is the data that is carried out by the protocol across the network for the
application. When the message is transmitted over the network, then the message contains the
following parameters:
❖ Payload data
❖ Quality of Service (QoS)
❖ Collection of Properties
❖ Topic Name
● Client: In MQTT, the subscriber and publisher are the two roles of a client. The clients
subscribe to the topics to publish and receive messages. In simple words, we can say that if any
program or device uses an MQTT, then that device is referred to as a client. A device is a client
if it opens the network connection to the server, publishes messages that other clients want to
see, subscribes to the messages that it is interested in receiving, unsubscribes to the messages
that it is not interested in receiving, and closes the network connection to the server. In MQTT,
the client performs two operations:
❖ Publish: When the client sends the data to the server, then we call this operation as a
publish.
❖ Subscribe: When the client receives the data from the server, then we call this operation
a subscription.
● Server: The device or a program that allows the client to publish the messages and subscribe to
the messages. A server accepts the network connection from the client, accepts the messages
from the client, processes the subscribe and unsubscribe requests, forwards the application
messages to the client, and closes the network connection from the client.
● TOPIC: The label provided to the message is checked against the subscription known by the
server as TOPIC.
Suppose a device has a temperature sensor and wants to send the rating to the server or the
broker. If the phone or desktop application wishes to receive this temperature value on the other
side, then there will be two things that happened. The publisher first defines the topic; for
example, the temperature then publishes the message, i.e., the temperature's value. After
publishing the message, the phone or the desktop application on the other side will subscribe to
the topic, i.e., temperature and then receive the published message, i.e., the value of the
temperature. The server or the broker's role is to deliver the published message to the phone or
the desktop application.
CoAP is a customary client-server IoT protocol. It enables clients to make requests for web
transfers as per the need of the hour. On the other hand, it also lets supporting servers to respond
to arriving requests. In summary, devices’ nodes in the IoT ecosystem are enabled to interact
over through CoAP only.
CoAP and HTTP follow the same working procedure. However, CoAP attains its functionality
via asynchronous transactions (using UDP). It utilizes the POST, GET, PUT, and DELETE calls.
The WWW and the constraints ecosystem are the 2 foundational elements of the CoAP protocol
architecture. Here, the server monitors and helps in communication happening using CoAP and
HTTP while proxy devices bridge the existing gap for these 2 ecosystem, making the
communication smoother.
CoAP allows HTTP clients (also called CoAP clients here) to talk or exchange data/information
with each other within resource constraints.
While one tries to understand this architecture, gaining acquaintances with some key terms is
crucial:
3. OMA LWM2M : Lightweight M2M is an open protocol from the Open Mobile Alliance
(OMA) that is designed for addressing the needs of mobile low-power devices with very
little compute power. LWM2M is being adopted widely by telecom operators and is
emerging as the standard protocol for device management and service enablement.
Use of LWM2M
As the use of Internet of Things continues to grow so will the need to manage and use
remote sensors and devices in areas with intermittent connectivity and situated far from
power connections. LWM2M provides a standardized way to manage these devices and
send telemetry data drawn in by the sensors quickly and cost effectively to the cloud.
LWM2M has been designed to reduce power and data usage for low-power devices,
which are limited in processing power and bandwidth. The protocol is ideal when people
or devices are a long way from power and need to use battery-powered local devices,
have a SIM card and no power cord.
So sensors and devices can be managed centrally and viewed remotely, LWM2M defines
a common language for the communication between devices and IoT platforms. With
LWM2M, metadata (which describes the data) needed to understand the capabilities of a
given device and interpret the data sent by the device is stored in a central repository in
the cloud. This allows devices to minimize the transmission of data, so that only key data
is sent. Saving bandwidth in particular for remote devices accelerates transmission, as
well as reduces communication costs.
Example uses include tracking shipper containers, cargo railways, farming where sensors
monitor and optimize irrigation fertilization, smart cities, and water and energy metering.
LWM2M is also used across telecommunications, the automotive industry, security
devices, by utilities companies and in manufacturing.
Benefits of LWM2M
The Cumulocity IoT platform natively supports LWM2M as an IoT device management
and service enablement protocol.
1. Self-service, plug and play:You can connect any LWM2M server and device without
coding. Direct integration with LWM2M devices is quick and easy with our
plug-and-play integration.
2. Remote management: Even though your devices are in hard-to-reach locations you need
to be able to update the firmware and be aware of any issues. With its native integration,
Cumulocity IoT provides firmware updates and monitoring capabilities out of the box
and enables you to troubleshoot devices remotely.
3. Easy-to-use interface to map with the Cumulocity IoT data model: Cumulocity IoT’s
device management allows you to define which data you want to receive from the device
and at which frequency. Additionally, you can integrate data from the device into your
IoT application’s domain model, allowing you to treat an LWM2M device in the same
way as any other device connected to your Cumulocity IoT tenant.
WSNs: Wireless Sensor Networks
IoT configurations often involve sensors, which can be connected by wireless networks. Such
sensor networks are termed “Wireless Sensor Networks” or WSNs. A WSN comprises spatially
distributed autonomous devices equipped with sensors, connected through a wireless network to
some type of gateway. The sensors typically monitor physical or environmental conditions. The
gateway communicates with another set of devices that can act on the information from the
sensors. Application examples include patient monitoring; environmental monitoring of air,
water, and soil; structural monitoring for buildings and bridges; industrial machine monitoring;
and process monitoring. The wireless network could be WiFi or Bluetooth, and the protocol one
of the three listed above.
The boundaries between these networks are not clearly drawn, and in practice they overlap
considerably. Figure 1 shows the relationship schematically:
WSN Protocols:
1. WIFI: WiFi stands for Wireless Fidelity. WiFiIt is based on the IEEE 802.11 family of
standards and is primarily a local area networking (LAN) technology designed to provide
in-building broadband coverage. Current WiFi systems support a peak physical-layer data
rate of 54 Mbps and typically provide indoor coverage over a distance of 100 feet.
WiFi has become the de facto standard for last mile broadband connectivity in homes,
offices, and public hotspot locations. Systems can typically provide a coverage range of
only about 1,000 feet from the access point.
WiFi offers remarkably higher peak data rates than do 3G systems, primarily since it
operates over a larger 20 MHz bandwidth, but WiFiWiFi systems are not designed to
support high-speed mobility. One significant advantage of WiFi over WiMAX and 3G is
its wide availability of terminal devices. A vast majority of laptops shipped today have a
built-in WiFi interface. WiFi interfaces are now also being built into a variety of devices,
including personal data assistants (PDAs), cordless phones, cellular phones, cameras, and
media players.
3. Zigbee:
ZigBee is a Personal Area Network task group with low rate task group 4. It is a technology of
home networking. ZigBee is a technological standard created for controlling and sensing the
network. As we know that ZigBee is the Personal Area Network of task group 4 so it is based on
IEEE 802.15.4 and is created by Zigbee Alliance.
IEEE 802.15.4 supports star and peer-to-peer topologies. The ZigBee specification supports star
and two kinds of peer-to-peer topologies, mesh and cluster tree. ZigBee-compliant devices are
sometimes specified as supporting point-to-point and point-to-multipoint topologies.
Types of ZigBee Devices:
● Zigbee Coordinator Device: It communicates with routers. This device is used for
connecting the devices.
● Zigbee Router: It is used for passing the data between devices.
● Zigbee End Device: It is the device that is going to be controlled.
Advantages of Zigbee:
Designed for low power consumption.
Provides network security and application support services operating on the top of IEEE.
Zigbee makes possible completely networks homes where all devices are able to communicate
and be
Use in smart home
Easy implementation
Adequate security features.
Low cost: Zigbee chips and modules are relatively inexpensive, which makes it a cost-effective
solution for IoT applications.
Mesh networking: Zigbee uses a mesh network topology, which allows for devices to
communicate with each other without the need for a central hub or router. This makes it ideal for
use in smart home applications where devices need to communicate with each other and with a
central control hub.
Reliability: Zigbee protocol is designed to be highly reliable, with robust mechanisms in place to
ensure that data is delivered reliably even in adverse conditions.
Disadvantages of Zigbee :
Limited range: Zigbee has a relatively short range compared to other wireless communications
protocols, which can make it less suitable for certain types of applications or for use in large
buildings.
Limited data rate: Zigbee is designed for low-data-rate applications, which can make it less
suitable for applications that require high-speed data transfer.
Interoperability: Zigbee is not as widely adopted as other IoT protocols, which can make it
difficult to find devices that are compatible with each other.
Security: Zigbee’s security features are not as robust as other IoT protocols, making it more
vulnerable to hacking and other security threats.
Zigbee Network Topologies:
Star Topology (ZigBee Smart Energy): Consists of a coordinator and several end devices, end
devices communicate only with the coordinator.
Mesh Topology (Self Healing Process): Mesh topology consists of one coordinator, several
routers, and end devices.
Tree Topology: In this topology, the network consists of a central node which is a coordinator,
several routers, and end devices. the function of the router is to extend the network coverage.
Architecture of Zigbee:
Zigbee architecture is a combination of 6 layers.
Application Layer
Application Interface Layer
Security Layer
Network Layer
Medium Access Control Layer
Physical Layer
● Physical layer: The lowest two layers i.e the physical and the MAC (Medium Access
Control) Layer are defined by the IEEE 802.15.4 specifications. The Physical layer is
closest to the hardware and directly controls and communicates with the Zigbee radio.
The physical layer translates the data packets in the over-the-air bits for transmission and
vice-versa during the reception.
● Medium Access Control layer (MAC layer): The layer is responsible for the interface
between the physical and network layer. The MAC layer is also responsible for providing
PAN ID and also network discovery through beacon requests.
● Network layer: This layer acts as an interface between the MAC layer and the application
layer. It is responsible for mesh networking.
● Application layer: The application layer in the Zigbee stack is the highest protocol layer
and it consists of the application support sub-layer and Zigbee device object. It contains
manufacturer-defined applications.
● Channel Access: Contention Based Method (Carrier-Sense Multiple Access With
Collision Avoidance Mechanism) Contention Free Method (Coordinator dedicates a
specific time slot to each device (Guaranteed Time Slot (GTS)))
Zigbee Applications:
● Home Automation
● Medical Data Collection
● Industrial Control Systems
● meter reading system
● light control system
● Commercial
● Government Markets Worldwide
● Home Networking
The DNP3 protocol is a polled protocol. When the master station connects to a remote, an
integrity poll is performed. Integrity polls are important for DNP3 addressing. This is
because they return all buffered values for a data point and include the current value of
the point as well.
RFID
Kinds of RFID :
There are many kinds of RFID, each with different properties, but perhaps the most fascinating
aspect of RFID technology is that most RFID tags have neither an electric plug nor a battery.
Instead, all of the energy needed to operate them is supplied in the form of radio waves by RFID
readers. This technology is called passive RFID to distinguish it from the(less common) active
RFID in which there is a power source on the tag.
UHF RHID ( Ultra-High Frequency RFID ). It is used on shipping pallets and some driver’s
licenses. Readers send signals in the 902-928 MHz band. Tags communicate at distances of
several meters by changing the way they reflect the reader signals; the reader is able to pick up
these reflections. This way of operating is called backscatter.
There are also other forms of RFID using other frequencies, such as LF RFID(Low-Frequency
RFID), which was developed before HF RFID and used for animal tracking
1. Passive RFID – Passive RFID tags does not have thier own power source. It uses
power from the reader. In this device, RF tags are not attached by a power supply and
passive RF tag stored their power. When it is emitted from active antennas and the RF
tag are used specific frequency like 125-134MHZ as low frequency, 13.56MHZ as a
high frequency and 856MHZ to 960MHZ as ultra-high frequency.
2. Active RFID – In this device, RF tags are attached by a power supply that emits a
signal and there is an antenna which receives the data. means, active tag uses a power
source like battery. It has it’s own power source, does not require power from
source/reader.
An antenna is an device which converts power into radio waves which are used for
communication between reader and tag. RFID readers retrieve the information from RFID tag
which detects the tag and reads or writes the data into the tag. It may include one processor,
package, storage and transmitter and receiver unit.
Every RFID system consists of three components: a scanning antenna, a transceiver and a
transponder. When the scanning antenna and transceiver are combined, they are referred to as an
RFID reader or interrogator. There are two types of RFID readers — fixed readers and mobile
readers. The RFID reader is a network-connected device that can be portable or permanently
attached. It uses radio waves to transmit signals that activate the tag. Once activated, the tag
sends a wave back to the antenna, where it is translated into data.
The transponder is in the RFID tag itself. The read range for RFID tags varies based on factors
including the type of tag, type of reader, RFID frequency and interference in the surrounding
environment or from other RFID tags and readers. Tags that have a stronger power source also
have a longer read range.
Features of RFID :
Application of RFID :
Advantages of RFID :
● It provides data access and real-time information without taking to much time.
● RFID tags follow the instruction and store a large amount of information.
● The RFID system is non-line of sight nature of the technology.
● It improves the Efficiency, traceability of production.
● In RFID hundred of tags read in a short time.
Disadvantages of RFID :
RFID tags from different manufacturers can be read using a common reader according to this
standard. Besides, transponder size is not specified in the standard, so it can be designed in a
variety of shapes to suit different animals, such as glass tubes, earmarks, or collars.
ISO/IEC14443 protocol is divided into two types: TypeA & TypeB, both operating at 13.56 MHz
(RFID HF). They are close-reading protocols. Label read-write distance is 0~10cm. The main
difference between A and B lies in their modulation, coding schemes, and anti-collision methods.
ISO/IEC 14443A
Strong anti-interference ability but poor power stability, mainly used in the field of
transportation, urban construction access cards, bus cards, and small stored value consumption
cards, with a high market share.
ISO/IEC 14443B
Good stability, high security, but relatively vulnerable to external environment interference.
Because the encryption coefficient is relatively high, it is more suitable for CPU card, generally
used for ID card, passport, bank card, etc.
It is compatible with ISO 18000-3 and allows long-distance communication. The maximum
reading distance is 100mm, and the application is more flexible. It widely used in production
automation, medical management, jewelry inventory, asset management, parking management
and product anti-counterfeiting, access control, asset management, logistics & supply chain,
library management, etc.
ISO 18000-6C (EPC Gen2) protocol is the most widely used protocol in medium and
long-distance. Tags under the EPC Gen2 protocol can be read and written repeatedly, and have a
good confidentiality performance.
IEEE802.15.4
IEEE 802.15.4 is a low-cost, low-data-rate wireless access technology for devices that are
operated or work on batteries. This describes how low-rate wireless personal area networks
(LR-WPANs) function.
802.15.4e for industrial applications and 802.15.4g for the smart utility networks (SUN). The
802.15.4e improves the old standard by introducing mechanisms such as time slotted access,
multichannel communication and channel hopping.
1. Low Energy (LE): This mechanism is intended for applications that can trade latency for
energy efficiency. It allows a node to operate with a very low duty cycle.
2. Information Elements (IE) It is an extensible mechanism to exchange information at the MAC
sublayer.
3. Enhanced Beacons (EB): Enhanced Beacons are an extension of the 802.15.4 beacon frames
and provide a greater flexibility. They allow to create application-specific frames.
4. Multipurpose Frame: This mechanism provides a flexible frame format that can address a
number of MAC operations. It is based on IEs.
5. MAC Performance Metric: It is a mechanism to provide appropriate feedback on the channel
quality to the networking and upper layers, so that appropriate decision can be taken.
6. Fast Association (FastA) The 802.15.4 association procedure introduces a significant delay in
order to save energy. For time-critical application latency has priority over energy efficiency.
3. Low Latency Deterministic Network (LLDN): Designed for single-hop and single channel
networks
4. Radio Frequency Identification Blink (BLINK): It is intended for application domains such as
item/people identification, location and tracking.
Properties:
1. Standardization and alliances: It specifies low-data-rate PHY and MAC layer requirements
for wireless personal area networks (WPAN).
IEEE 802.15. Protocol Stacks include:
● ZigBee: ZigBee is a Personal Area Network task group with a low rate task group 4.
It is a technology of home networking. ZigBee is a technological standard created for
controlling and sensing the network. As we know that ZigBee is the Personal Area
network of task group 4 so it is based on IEEE 802.15.4 and is created by Zigbee
Alliance.
● 6LoWPAN: The 6LoWPAN system is used for a variety of applications including
wireless sensor networks. This form of wireless sensor network sends data as packets
and uses IPv6 – providing the basis for the name – IPv6 over Low power Wireless
Personal Area Networks.
● ZigBee IP: Zigbee is a standards-based wireless technology that was developed for
low-cost and low-power wireless machine-to-machine (M2M) and internet of things
(IoT) networks.
● ISA100.11a: It is a mesh network that provides secure wireless communication to
process control.
● Wireless HART: It is also a wireless sensor network technology, that makes use of
time-synchronized and self-organizing architecture.
● Thread: Thread is an IPv6-based networking protocol for low-power Internet of
Things devices in IEEE 802.15. 4-2006 wireless mesh network. Thread is
independent.
2. Physical Layer: This standard enables a wide range of PHY options in ISM bands, ranging
from 2.4 GHz to sub-GHz frequencies. IEEE 802.15.4 enables data transmission speeds of 20
kilobits per second, 40 kilobits per second, 100 kilobits per second, and 250 kilobits per second.
The fundamental structure assumes a 10-meter range and a data rate of 250 kilobits per second.
To further reduce power usage, even lower data rates are possible. IEEE 802.15.4 regulates the
RF transceiver and channel selection, and even some energy and signal management features, at
the physical layer. Based on the frequency range and data performance needed, there are now six
PHYs specified. Four of them employ frequency hopping techniques known as Direct Sequence
Spread Spectrum (DSSS). Both PHY data service and management service share a single packet
structure so that they can maintain a common simple interface with MAC.
3. MAC layer: The MAC layer provides links to the PHY channel by determining that devices
in the same region will share the assigned frequencies. The scheduling and routing of data
packets are also managed at this layer. The 802.15.4 MAC layer is responsible for a number of
functions like:
● frame of data
● Frame for a beacon
● Frame of acknowledgement
● Frame for MAC commands
4. Topology: Networks based on IEEE 802.15.4 can be developed in a star, peer-to-peer, or mesh
topology. Mesh networks connect a large number of nodes. This enables nodes that would
otherwise be out of range to interact with each other to use intermediate nodes to relay data.
5. Security: For data security, the IEEE 802.15.4 standard employs the Advanced Encryption
Standard (AES) with a 128-bit key length as the basic encryption technique. Activating such
security measures for 802.15.4 significantly alters the frame format and uses a few of the
payloads. The very first phase in activating AES encryption is to use the Security Enabled field
in the Frame Control part of the 802.15.4 header. For safety, this field is a single bit which is
assigned to 1. When this bit is set, by taking certain bytes from its Payload field, a field known as
the Auxiliary Security Header is formed following the Source Address field.
6. Competitive Technologies: The IEEE 802.15.4 PHY and MAC layers serve as a basis for a
variety of networking profiles that operate in different IoT access scenarios. DASH7 is a
competing radio technology with distinct PHY and MAC layers.
● cheap cost
● long battery life,
● Quick installation
● simple
● extensible protocol stack