UNIT 1

IOT ARCHITECTURE AND PROTOCOLS

PRUDHVI KIRAN P
Assistant Professor, CSE - IoT Dept.
R. V. R. & J. C. College of Engineering
UNIT - 1 [ 12 Periods ]
IoT Network Architecture and Design: Drivers behind New Network Architectures, The
OneM2M IoT Standardized Architecture, The IoT World Forum (IoTWF) Standardized
Architecture, A Simplified IoT Architecture - The Core IoT Functional Stack, IoT Data
Management and Compute Stack.
IoT Connectivity Technologies (PART 1):
1. Introduction
2. IEEE 802.15.4 - Overview, Architecture, Topology, Addressing Modes and Packet
Structure, Security, 802.15 standards
3. Zigbee - Overview, Protocol Stack, PHY and MAC Layer, Addressing Modes and Packet
Structure, Topology, Security
4. Z-Wave - Overview, Protocol Stack, Addressing, Topology and Routing.

SUBJECT CODE - CO 224

CLASS DETAILS - IoT IV SEM - MARCH 2023
FACULTY DETAILS - PRUDHVI KIRAN P, Asst. Prof., CSE (IoT), RVR&JC College of Engineering
QUESTION BANK - UNIT 1 [Assignment Questions - 2, 6, 9]
1. Explain briefly about popular IoT connectivity technologies. What are the Drivers behind IOT
network Architecture?
2. Discuss about the OneM2M IoT Standardized Architecture with relevant block diagram.
3. Discuss about the IoT World Forum (IoTWF) Standardized Architecture with relevant block
diagram.
4. Discuss about the Simplified IoT Architecture with relevant block diagram.
5. Discuss about Core IOT functional stack in relevance with IoT Data Management and Compute
Stack with relevant block diagram.
6. Discuss about various aspects of IEEE 802.15.4 protocol and draw Protocol Stack and Packet
Structure of IEEE 802.15.4 (MAC, PHY).
7. Discuss about various aspects of Zigbee. Draw and explain the Protocol Stack and Packet
Structure of Zigbee.
8. Discuss about various aspects of Z-Wave. Draw and explain the protocol stack of Z-Wave.
9. Discuss about the working topologies of IEEE 802.15.4, Zigbee and Z-Wave. Mention five IoT
applications separately for those three protocols.
END
1.1.1 Drivers behind New Network Architectures
To implement any networking concept, designing and understanding the network architecture is of
utmost importance. Traditional computing network architectures are meant for reliable and
continuous support of business applications such as email, web, databases, etc. and on the other
hand, new network architectures like IoT is all about the data generated by sensors and how that
data is used; the essence of these network architectures thus involves how the data is transported,
collected, analysed, and ultimately acted upon.
Below are the drivers behind the new network architectures, driving the design process and leveling
the path to the efficient IoT networks; These drivers are discussed in contrast with traditional IT
architectures for better understanding:
1. Scalability
 The scale of a typical IT network ranges in several thousand devices like printers, mobile wireless
devices, laptops, servers, etc.
 But when a scale of a network goes from a few thousand endpoints to a few millions the IT
engineers lack a required skills to design a network that is intended to support millions of
routable IP endpoints.
2. Security
 Protecting corporate data from intrusion and theft is one of the main functions of the IT
network architectures.
 Security in IoT network architectures require consistent mechanisms of authentication,
encryption, and intrusion prevention techniques and be able to identify and authenticate all
entities involved in the IoT service(i.e., gateways, endpoint devices, home networks, roaming
networks, service platforms).
3. Constrained Devices and Networks
 If an IT network has performance constraints, the solution is simple: Upgrade to a faster
network; i.e. if too many devices in network are impacting performance, we can simply scale
network as much as we need and this may be expensive.
 IoT network performance varies from traditional, as most IoT sensors are constrained for a
single job, and they are typically small and inexpensive. This means they often have limited
power, CPU, and memory, and they transmit only when there is something important.
4. Data
 In general IT infrastructure, they don’t really care much about the unstructured chatty data
generated by devices on the network.
 However, in IoT the data is like gold, as it is what enables businesses to deliver new IoT services
that enhance the customer experience, reduce cost, and deliver new revenue opportunities.
Although most IoT-generated data is unstructured, the insights it provides through analytics can
revolutionize processes and create new business models.
5. Legacy Device Support
 Supporting legacy devices in an IT organization is not usually a big problem. If someone’s
computer or operating system is outdated, they simply upgrades. If someone is using a mobile
device with an outdated Wi-Fi standard, such as 802.11b or 802.11g, we can simply deny them
access to the wireless network, and will be forced to upgrade.
 In IoT systems, end devices are likely to be on the network for a very long time, sometimes
decades. As new IoT networks are deployed, they need to support the older devices already
present on the network. Here in the case of IoT networks, it does not want to upgrade just so it
can have a better network.

The network architecture of IoT depends upon its functionality and

implementation in different sectors. Still, there is a basic process
flow based on which IoT network is built; and above are the drivers
for that network.
1.1.2 The oneM2M IoT Standardized Architecture
The challenges and requirements of IoT systems have driven a whole new discipline of network
architecture. In the past several years, many architectural standards and frameworks have emerged
to address the challenge of designing massive-scale IoT networks. Two of the best-known
architectures;
 oneM2M IoT Standardized Architecture
 IoT World Forum (IoTWF) Standardized Architecture
OneM2M IoT Standardized Architecture
 In effort to standardize the rapidly growing field of machine to machine (M2M) communications,
the European telecommunications Standards Institute (ETSI) created the M2M Technical
committee in 2008. The goal of this committee was to create a common architecture that would
help accelerate the adoption of M2M applications and devices. Over the time, the scope has
expanded to include the Internet of Things.
 Recognizing this need, in 2012 ETSI and 13 other founding members launched one M2M as a
global initiative designed to promote efficient M2M communication systems and IoT.
 The one M2M architecture divides IoT functions into three major domains: the application layer,
the services layer and the network layer.
 THE ONEM2M IOT STANDARDIZED ARCHITECTURE

APPLICATIONS LAYER SERVICES LAYER NETWORK LAYER

 While this architecture may seem simple and somewhat generic at first glance, it is very rich and
promotes interoperability through IT-friendly APIs and supports a wide range of IoT
technologies.
Applications Layer:
 Here the major attention is given to connectivity between devices and their applications, using
application-layer protocols and attempts to standardize API definitions for interaction with
business intelligence (BI) systems.
 Applications tend to be industry specific and have their own sets of data models and thus they
are shown as vertical entities.
Services Layer:
 This layer is shown as a horizontal framework across the vertical industry applications. At this
layer, horizontal modules include the physical network that the IoT applications run on, the
underlying management protocols, and the hardware.
 This conceptual layer adds APIs and middleware supporting third party services and applications.
Network Layer:
 This is the communication domain for the IoT devices and endpoints. It includes the devices
themselves and the communication network that links them. Embodiments of this
communication infrastructure includes wireless mesh technologies such as IEEE 802.15.4, and
wireless point-to-multipoint systems, such as IEEE 801.11. Also included are wired device
connections, such as IEEE 1901 power line communications.
Common services layer, which can be readily embedded in field devices to allow
communication with application servers. One of the greatest challenges in
designing an IoT architecture is dealing with the heterogeneity of devices,
software, and access methods.
UNDERSTANDING ONE M2M ARCHITECTURE WITH GIF IMAGE
1.1.3 The IoT World Forum (IoTWF) Standardized Architecture
 In 2014 the IoTWF architectural committee COLLABORATION & PROCESSES
(led by Cisco, IBM, Rockwell Automation, 7 (Involving people & business processes)
and others) published a seven layer IoT APPLICATION
architectural reference model. Each of the 6 (Reporting analysis control)
seven layers is broken down into specific
DATA ABSTRACTION
functions, and security encompasses the 5 (Aggregation & access)
entire model.
DATA ACCUMULATION
 According to an official press release by 4 (Storage)
Cisco forum host, the architecture aims to
EDGE (FOG) COMPUTING
help educate IT departments and 3 (Data element analysis and transformation)
developers on deployment of IoT projects,
and accelerate the adoption of IoT. CONNECTIVITY
2 (Communication & Processing units)
About Layers
PHYSICAL DEVICES & CONTROLLERS
Layer 1 - Physical Devices 1 ('Things' in IoT)
 Including the various endpoint devices and
IOT WORLD FORUM (IOTWF)
sensors that send and receive information.
STANDARDIZED ARCHITECTURE
 The size of these “things” can range from almost microscopic sensors to giant machines in a
factory.
 Their primary function is generating data and being capable of being queried and/or controlled
over a network.
Layer 2 - Connectivity
 The focus is on connectivity. The most important function of this IoT layer is the reliable and
timely transmission of data. Few functions include, communication between Layer 1 devices,
switching and routing, translation between protocols, network level security.
Layer 3 - EDGE/FOG
 Edge computing is often referred to as the “fog” layer. At this layer, the emphasis is on data
reduction and converting network data flows into information that is ready for storage and
processing by higher layers.
 One of the basic principles of this reference model is that information processing is initiated as
early and as close to the edge of the network as possible, this will be done by fog/edge
computing in Layer 3.
 Functions include, Evaluate and reformat data for processing at higher levels, Filter data to
reduce traffic in higher level processing.
Layer 4 - Data Accumulation
 Captures data and stores it so it usable by applications when necessary. Converts event-based
data to query based processing.
Layer 5 - Data Abstraction
 Reconciles multiple data formats and ensures consistent semantics from various sources.
Confirms that the data set is complete and consolidates data into one place or multiple data
stores.
Layer 6 - Application
 Interprets data using software applications. Applications may monitor, control and provide
reports based on the analysis of the data.
Layer 7 - Collaboration
 Consumes and shares the application information. This layer can change business processes and
delivers benefits of IoT.
The bottom of the stack is generally in the domain of IoT (Layer 1 to Layer 4), this includes sensors
and the data generated here is event based real-time data. The top of the stack (Layer 4 to Layer 7)
is in the IT area and includes things like the servers, databases and applications, the date generated
here is query based ‘data in rest’.
Using this reference model, we are able to achieve the following:
 Decompose the IoT problem into smaller parts.
 Identify different technologies at each layer and how they relate to one another.
 Define a system in which different parts can be provided by different vendors.
 Have a process of defining interfaces that leads to interoperability.
 Define a tiered security model that is enforced at the transition points between levels.
1.1.4 A Simplified IoT Architecture - The Core IoT Functional Stack, IoT Data Management
and Compute Stack
 Simplified IoT Architecture is an IoT framework that highlights the fundamental building blocks
that are common to most IoT systems. Simplified IoT Architecture also intended to help you in
designing an IoT network.
 A Simplified IoT Architecture is presented as two parallel stacks; Core IoT Functional Stack and
IoT Data Management and Compute Stack.
Note that, Data Management and Compute Stack is aligned with each of the three layers of the Core
IoT Functional Stack. The three data management layers are the edge layer (data management
within the sensors themselves), the fog layer (data management in the gateways and transit
network), and the cloud layer (data management in the cloud or central data centre). An expanded
view of the Simplified IoT architecture is presented below:
THE CORE IOT FUNCTIONAL STACK
 Three layers presented in Core IoT Functional Stack represents the most foundational building
blocks of IoT architecture.
Layer 1: Things: Sensors and Actuators Layer
 This layer represents the "things" in IoT. Things are actuators and sensors, the smart objects,
embedded with software, and other technologies for the purpose of connecting and exchanging
data with other devices and systems. Architectural classification of this "things" could be done on
basis of;
• Battery-powered or power-connected
• Mobile or static
• Low or high reporting frequency
• Simple or rich data (quantity of data exchanged at each report cycle)
• Report range (distance at which the gateway is located)
• Object density per cell
Layer 2: Communications Network Layer
 Smart objects are not self contained, they need to communicate with an external system. In most
of the cases, this communication uses a wireless technology. This layer has four sublayers:
1. Access Network Sublayer
2. Gateways and backhaul network sublayer
3. Network transport sublayer
4. IoT network management sublayer
1. Access Network Sublayer
 There is a direct relationship between the IoT network technology (for connectivity between
things) we choose and the type of connectivity and topology this chosen technology allows.
 Each network technology was designed with a certain number of use cases in mind, like what to
connect, where to connect, how much data to transport at what interval and over what distance.
Common network groups represented by Access network Sublayer are as follows;
 PAN (personal area network): Scale of a few meters. This is the personal space around a person.
A common wireless technology for this scale is Bluetooth.
 HAN (home area network): Scale of a few tens of meters. At this scale, common wireless
technologies for IoT include ZigBee and Bluetooth Low Energy
 NAN (neighbourhood area network): Scale of a few hundreds of meters. The term NAN is often
used to refer to a group of house units from which data is collected.
 FAN (field area network): Scale of several tens of meters to several hundred meters. FAN typically
refers to an outdoor area larger than a single group of house units.
 LAN (local area network): Scale of up to 100 m. This term is very common in networking, and it
is therefore also commonly used in the IoT space where standard networking technologies
(such as Ethernet or IEEE 802.11) are used.
Common topologies represented by Access network Sublayer are as follows;

STAR TOPOLOGY CLUSTERED STAR TOPOLOGY MESH TOPOLOGY

In Star topology, the nodes are connected to the central hub in which the information travel from
the central hub to all the nodes (node to node), this can be also seen as Point-to-Point topology.
In Mesh topology, all devices in the network are interconnected. In a mesh topology, data can be
transmitted from node to node directly, by routing.
2. Gateways and backhaul network sublayer
 Gateway acts as a medium to open up connections between the cloud and objects (sensors &
actuators) in Internet of Things (IoT). With the help of gateways, it is possible to establish device-
to-device or device-to-cloud communication. A gateway can be a typical hardware device or
software program. It enables a connection between the sensor network and the Internet along
with enabling IoT communication.
 Backhaul network in IoT is defined as the wire/wireless link that connect the Internet network
with the smaller subnetworks towards the edge (Objects/Things of IoT). Backhaul enables users
to access the internet by accessing the subnetwork. Backhaul increase the expanse of network
coverage.
3. Network transport sublayer
 This layer focuses on end-to-end communication and provides features such as reliability,
congestion avoidance, and guaranteeing that packets will be delivered in the same order that
they were sent.
4. IoT Network management sublayer
 This layer looks after the total applications, tools and processes used to provision, operate,
maintain, administer and secure network infrastructure of IoT. The overarching role of network
management is ensuring network resources are made available to users efficiently, effectively
and quickly.
 There exists many protocols like CoAP (Constrained Application Protocol), MQTT (Message
Queuing Telemetry Transport) to look after the network management.
Layer 3: Applications Layer
 Application layer is designed as the top layer in the three-layer IoT architecture. The application
layer accepts the network-level data from the second layer and utilizes the data to deliver
desired services or operations for user applications. The application layer act as an interface
between end-user and IoT, the user can utilize the data and manage the device through the
application layer. This layer in core IoT functional stack is represented through two sublayers;
1. Vertical Specified Apps
2. Analytics
1. Vertical Specified Apps
This represents that, the applications in application layer are vertical specific, like SCADA and MDM.
• SCADA - supervisory control and data acquisition, a category of software applications for
controlling industrial processes, which is the gathering of data in real time from remote locations
in order to control equipment and conditions.
• MDM - Mobile Device Management is any software that allows IT to automate, control, and
secure administrative policies on laptops, smartphones, tablets, or any other device connected
to an organization's network.
2. Analytics
 Analytics is a general term that describes processing information to make sense of collected data.
In the world of IoT, Data analytics processes the data collected by smart objects and combines it
to provide an intelligent view related to the IoT system. In a more complex case, temperature,
pressure, wind, humidity, and light levels collected from thousands of sensors may be combined
and then processed to determine the likelihood of a storm and its possible path.
IOT DATA MANAGEMENT AND COMPUTE STACK
 The massive scale of IoT networks is fundamentally driving the demand of new network
architectures. As per the projections by Cisco nearly 50 billion devices are connected to the IoT
networks by the year 2020. In fact, the data generated by these IoT devices is one of the single
biggest challenges in building an IoT system.
 Data Management and Compute Stack is represented by three layers and these three layers are
aligned with each of the three layers of the Core IoT Functional Stack.
Layer 1: Edge Computing Layer
 In Edge computing, information processing is located close to the edge (where things produce
that information) rather than sending the data back to a datacenter or cloud for processing.
 Edge computing is also sometimes called “mist” computing. Together, IoT and edge computing
are a powerful way to rapidly analyze data in real-time.
Layer 2: Fog Computing Layer
 Fog computing is a computing architecture in which a series of nodes receives data from IoT
devices in real time. These nodes perform real-time processing of the data that they receive, with
millisecond response time. The nodes periodically send analytical summary information to the
cloud. Fog computing brings computation and data storage closer to the network edge, but not
as closer as the edge computing.
Layer 3: Cloud Computing Layer
 IoT uses cloud computing services
to collect and process data from IoT
devices, and to manage the devices
remotely. Developers can use IoT
cloud computing on-demand and
users can also scale the cloud
service according to their needs.
Cloud computing servs the
application layer of core IoT
functional stack.
The Simplified IoT architectural stack is
nothing else than a range of
technologies, standards and tools,
which lead from the simple connection
of objects to the applications that use
these connected things, the data they
gather and communicate and the
different steps needed to power them.
1.2.1 IoT Connectivity Technologies - Introduction
 Understand that for the IoT devices to work correctly there needs to be robust connectivity
between the IoT devices and the servers to which they are relaying the information.
 Finding the best
connectivity technology LOCAL AREA
LAN NETWORK <= 45
METERS WAN
WIDE AREA
NETWORK
<=1000
KILO METERS
for a given IoT project

SATELLITE
always involves
negotiating a balance
between three <= 45
PERSONAL AREA
fundamental connectivity PAN NETWORK METERS

parameters:
a) Range/Distance Covered
b) Bandwidth - Speed LPWAN LOW POWER WIDE
AREA NETWORK
FEW THOUSANDS
KILO METERS

c) Power consumption
Technologies that are widely
used in IoT now-a-days, are
mentioned in the figure;
IOT CONNECTIVITY TECHNOLOGIES - DEPLOYMENT RANGE
1.2.2 IEEE 802.15.4 - Overview
 IEEE 802.15.4 (LR-WPAN) is a technical standard which defines the operation of wireless personal
area network which focuses on low data rate but very long battery life and very low complexity.
It specifies the physical layer (PHY) and media access control layer (MAC) layers for LR-WPANs,
and is maintained by the IEEE 802.15 working group, which defined the standard in 2003.
 It is the basis for the Zigbee, ISA100.11a, Wireless HART, Thread and few other specifications,
each of which further extends their standard by developing the upper layers which are not
defined in IEEE 802.15.4.
 IEEE standard 802.15.4 intends to offer the fundamental lower network layers of a type of
wireless personal area network (WPAN) which focuses on low-cost, low-speed ubiquitous
communication between devices. It can be contrasted with other approaches, such as Wi-Fi,
which offer more bandwidth and requires more power. The basic framework conceives a 10-
meter communications range with line-of-sight at a transfer rate of 250 kbit/s.
 Networks based on IEEE 802.15.4 can be developed in a star, peer-to-peer, or mesh topology.
Mesh can connect large number of devices, where devices doesn't have to communicate directly
to a gateway, but just forward its message to the next closest device.
IEEE 802.15.4 - Key Features
 Real-Time Suitability by reservation of Guaranteed Time Slots (GTS), I.e. One or more slots of time
reserved for a particular node for it’s operation.
 Collision Avoidance through CSMA/CA - Carrier-sense multiple access with collision avoidance, it
is a protocol for carrier transmission in 802.11 networks. It was developed to minimize the
potential of a collision occurring when two or more stations send their signals over a data link
layer. CSMA requires each station to first check the state of the medium before initiating a
transmission. This helps to avert potential collisions by listening to the broadcasting nodes and
then informing devices to transmit when the channel is free.
 Integrated support for Secure Communications, ensuring Data Confidentiality, Data Integrity,
Data Authentication, Data Freshness. It also offers Power Management functions such as link
speed/quality and energy detection.
 Support for time and data rate sensitive applications because of its ability to operate either as
CSMA/CA or TDMA (Time Division Multiple Access) access modes. The TDMA mode of operation is
supported via the GTS feature of the standard.
 IEEE 802.15.4 supported devices may use one of three possible frequency bands for operation
868/915/2450 MHz
IEEE 802.15.4 - Architecture
IEEE 802.15.4 PHY
 The PHY provides two services: the PHY Data
Service and PHY Management Service interfacing to
the physical layer management entity (PLME).
 The PHY data service enables the transmission and
reception of PHY protocol data units (PPDUs) across
the physical radio channel.
 The PHY management services are activation and
deactivation of the radio transceiver, energy
detection (ED), link quality indication (LQI), channel
selection, clear channel assessment (CCA) and
transmitting as well as receiving packets across the
physical medium.
 To maintain a common simple interface with MAC,
both PHY data service and management service
share a single packet structure.
IEEE 802.15.4 MAC
 The purpose of the IEEE 802.15.4 MAC layer is to provide an interface between the physical layer
(PHY) and the application layer. The as IEEE 802.15.4 does not specify an application layer, this is
generally an application system such as Zigbee. The IEEE 802.15.4 MAC provides the interface to
the application layer using two elements:
 The MAC provides two services: the MAC Data Service and MAC Management Service
interfacing to the MAC layer management entity (MLME).
 The MAC data service enables the transmission and reception of MAC protocol data units
(MPDUs) across the media access control (MAC) entities.
 The MAC management services are scheduling and routing of data packets, Beaconing for devices
that operate as controllers in a network, associate and dissociate PANs with the help of devices,
safety of the device and make sure of Consistent communication between MAC devices.
UPPER LAYERS
 No upper/higher-level layers and interoperability sublayers are defined in the standard. Other
specifications, such as Zigbee and many more, build upper layers of their own making IEEE
802.15.4 as their base layer.
LLC & SSCS
 logical link control (LLC) and service specific convergence sub-layer (SSCS) are used to
communicate with all upper layers. LLC controls the synchronization, flow control, and error-
checking functions of the Upper Layers. SSCS is an intermediate layer of a layer model, which is
responsible for the converted traffic. SSCS is service-dependent and provides secured data
transmission.
IEEE 802.15.4 - Security
 the MAC sublayer of IEEE 802.15.4 offers facilities which can be harnessed by upper layers to
achieve the desired level of 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.
 Furthermore, MAC computes freshness checks between successive receptions to ensure that
presumably old frames, or data which is no longer considered valid, does not transcend to higher
layers.

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.
IEEE 802.15.4 - Packet Structure

MAC Packet
Frame Control Field - It is 2 bytes long field which defines type of frame, i.e., management(00),
control(01) or data(10). Data Sequence Number - Following each packet transmission, the firmware
increments the sequence number field by 1. This maintains the data order. Address Information -
Source and Destination address information. Payload - Transmission data unit. Frame Check Sequence
- Error-detecting code added to a frame.
PHY Packet
Preamble Sequence - Provides synchronization between a client and a base station. Each packet is
preceded by a sequence of alternate 1s and 0s to allow the receiving system to synchronize its local
clock with that of the transmitter. Start of frame Delimiter - Iindicates that it is followed by the real
data. Frame Length - Data Frame size. MPDU - MAC Frame/Header.
IEEE 802.15.4 - Addressing Modes
IEEE 802.15.4 address frame will be configured as one of below mentioned three different
addressing modes; that is included in the frame.
1. No address: For example, both addresses are missing from ACK frames as Mobile node senses
the medium for ACK when it wants to. Another scenario is for data and command frames, only
one, either source or destination address field can be omitted - if the source address is omitted,
it means the PAN coordinator sent the frame; if the destination address is missing, it means it
should be received by the PAN coordinator.
2. Long address: 8 Byte EUI-64 address assigned to it during manufacturing. This address is unique
between all devices that supports this address format. This is usually called the long address.
3. Short address: Each device can configure a 2 Byte short address. This should be unique within
the PAN. However, a network layer can also configure a short address to devices, usually during a
join process.
IEEE 802.15.4 - Supporting Topology
In a peer-to-peer topology, it is In a mesh topology, each node Star topology is a type of
not typically feasible for each in a peer-to-peer network also network topology in which
node to be directly connected functions as a router. This every device in the network is
to each other node, so instead routing layer allows you to individually connected to a
they connect to some subset of directly address nodes to which central node, known as the
nodes. Information can be you are not directly connected, switch or hub. If two nodes
published to the network in a because intermediate nodes want to communicate with each
broadcast fashion, where it will pass the message along other, node have to contact
eventually becomes available to until it reaches the target node. central node and central node
everyone, but it is not possible The message is only passed to then transfers the message to
to directly address nodes in the the next, so the data is not intended receiver node.
network to which you are not broadcast to the entire network
directly connected. like peer-to-peer.
IEEE 802.15 Standards
IEEE 802.15.4 - APPLICATIONS IN IoT
 The IEEE 802.15. 4 standard specifies the MAC and PHY layers of Low-Rate Wireless Personal Area
Networks (LR-WPANs). The IEEE 802.15. 4 MAC and PHY layers provide the basis of other higher-
layer standards, such as ZigBee, WirelessHart, 6LoWPAN and MiWi.
1.2.3 Zigbee - Overview
 ZigBee is a technological standard created
for Control and Sensor Networks.
 ZigBee works in close proximity
environment (i.e., personal area networks)
such as for home automation, medical
device data collection, and other low-
power low-bandwidth needs, designed for
small scale projects which need wireless
connection.
 ZigBee is Created in 2006 by the ZigBee
Alliance in which, Philips, Motorola, Intel,
HP are the members of this alliance.
 ZigBee is Based on the IEEE 802.15.4
Standard. ZigBee supports low power
consumption, allowing batteries to
essentially last for ever.
ZigBee - Characteristics
 Low power consumption with battery life ranging from months to years.
 High density of nodes per network.
 Low cost.
 Simple implementation.
 Low data rate.
 Reliable data.
 Adequate security features.
 Small packet devices.
ZigBee - Applications
 The ZigBee is used in set top boxes and remote controls.
 It is used in safety and surveillance system, fire alarms, pressure sensors, meter reading monitors,
health and environmental monitors for live monitoring.
 It is used for automation and control such as home, factory, warehouse and building.
 It is used for situational awareness and precision asset location like military actions, firefighters
operations, real time tracking of inventory.
 It is used for entertainment such as learning games and interactive toys.
 It is used in medical data collection.
ZigBee - Device Types
There are three different ZigBee device types that operate on the layers in any self-organizing
application network;
1. Zigbee Coordinator node(ZCN) REDUCED FUNCTION DEVICE
2. Full Function Device(FFD)
3. Reduced Function Device(RFD)
1. Zigbee Coordinator node (ZCN)
 It is the root of network tree and a bridge to other network.
Able to store information about the network. Only one ZCN for
a network. It act as a repository for other security keys.
2. Full Function Device (FFD) FULL FUNCTION DEVICE

 An intermediatory router transmitting data from other devices.

Less memory and Cheaper than ZCN. Can operate on all
topologies. Also act as a coordinator some times.
3. Reduced Function Device (RFD)
 Device capable of talking in the network. It cannot relay data
from other devices. Less memory and Cheaper than FFD. It ZIGBEE COORDINATOR NODE
talks only to the n/w coordinator.
ZigBee - Protocol Stack
IEEE 802.15.4 PHY LAYER
APPLICATION CUSTOMER
 The PHY provides two services: the PHY Data
Service and PHY Management Service
interfacing to the physical layer management
API
entity (PLME). SECURITY
 The PHY data service enables the transmission 32 -/64-/128- bit
and reception of PHY protocol data units Encryption ZIGBEE ALLIANCE
(PPDUs) across the physical radio channel.
 The PHY management services are activation NETWORK
and deactivation of the radio transceiver, Star/Mesh/Cluster-Tree
energy detection (ED), link quality indication
(LQI), channel selection, clear channel
MAC
assessment (CCA) and transmitting as well as
receiving packets across the physical medium. IEEE 802.15.4
 To maintain a common simple interface with PHY
MAC, both PHY data service and management 868 MHz/915 MHz/2.4 GHz
service share a single packet structure.
IEEE 802.15.4 MAC LAYER
 The purpose of the IEEE 802.15.4 MAC layer is to provide an interface between the physical layer
(PHY) and the application layer. The IEEE 802.15.4 MAC provides the interface to the application
layer using two elements:
 The MAC provides two services: the MAC Data Service and MAC Management Service interfacing
to the MAC layer management entity (MLME).
 The MAC data service enables the transmission and reception of MAC protocol data units
(MPDUs) across the media access control (MAC) entities.
 The MAC management services are scheduling and routing of data packets, Beaconing for
devices that operate as controllers in a network, associate and dissociate PANs with the help of
devices, safety of the device and make sure of Consistent communication between MAC devices.
NETWORK LAYER
 This layer ensures correct operation of the IEEE 802.15.4 MAC sub-layer and provides an
appropriate service interface to the Application layer. It interfaces with application layer via NLDE
and NLME.
 The NWK layer is responsible for the processing steps needed to securely transmit outgoing
frames and securely receive incoming frames; coordinating the supporting network topologies.
SECURITY LAYER
 Zigbee assumes an “open trust” model. The protocol stack layers trust each other. The layer that
originates a frame is responsible for its security. Zigbee is considered to be a secure wireless
communication protocol, with security architecture built in accordance with IEEE 802.15.4
standard. Zigbee supports, 32,64 & 128 bit encryption standards for security.
API & APPLICATION LAYER
 The ZigBee application layer is called application framework (AF). The AF supports multiple
applications and demultiplexes incoming data between the registered applications.
 The Application Framework depends on the vendor who has chosen for specific applications to
interact with Zigbee protocol. This represents how end points are implemented, how data
requests and data confirmation is executed for that particular vendor.
 An application programming interface (API) is a way for two or more computer programs to
communicate with each other. It is a type of software interface, offering a service to other pieces
of software. API acts as interface between application layer and lower layers of Zigbee protocol
stack.
ZigBee - Packet Structure
PHY Packet SENDER'S
Preamble Sequence - Provides MESSAGE
synchronization between a client and a base
station. Each packet is preceded by a
sequence of alternate 1s and 0s to allow the
receiving system to synchronize its local clock
with that of the transmitter. Start of frame
Delimiter - Iindicates that it is followed by the
real data. Frame Length - Data Frame size.
MPDU - MAC Frame/Header. Frame Payload -
Content of upper layer (MAC Data Frame).

MAC Data frame

Frame Control Field - It is 2 bytes long field
which defines type of frame,
i.e., management(00),
control(01) or data(10).
Data Sequence Number - Following each packet transmission, the firmware increments the
sequence number field by 1. This maintains the data order. Address Information - Source and
Destination address information. Payload - Content of upper layer (Network Layer Frame). Frame
Check Sequence - Error-detecting code added to a frame.
Network Layer frame
Frame Control Field - It is 2 bytes long field which defines type of frame, i.e., management(00),
control(01) or data(10). Destination Address - Destination address information. Source Address -
Source address information. Radius - Broadcast range radius. Sequence Number - Sequence number
of frames sent. Frame Payload - Content of upper layer (Application Layer Frame).
Application Layer frame
Frame Control Field - It is 2 bytes long field which defines type of frame, i.e., management(00),
control(01) or data(10). Destination Endpoint - Destination address information. Cluster ID - Source
address information. Profile ID - Broadcast range radius. Source Endpoint - Sequence number of
frames sent. Frame Payload - Users Message.
ZigBee - Network Topology

STAR
TOPOLOGY
MESH
TOPOLOGY

CLUSTERED STAR Zigbee Coordinator node(ZCN)

TOPOLOGY Full Function Device (FFD)
Reduced Function Device (RFD)
ZigBee - Addressing Modes
All Zigbee devices have two different addresses, a 64-bit and a 16-bit address. This section
describes the characteristics of each.
64-bit device addresses
The 64-bit address is a device address which is unique to each physical device. It is sometimes also
called the MAC address or extended address and is assigned during the manufacturing process. The
first three bytes of the 64-bit address is a Organizationally Unique Identifier (OUI) assigned to the
manufacturer by the IEEE. The OUI of XBee devices is 0x0013A2.
16-bit device addresses
A device receives a 16-bit address when it joins a Zigbee network. For this reason, the 16-bit address
is also called the network address. The 16-bit address of 0x0000 is reserved for the coordinator. All
other devices receive a randomly generated address from the router or coordinator device that
allows the join. The 16-bit address can change under certain conditions:
Address Conflict
An address conflict is detected where two devices are found to have the same 16-bit address. If a
device leaves the network and later joins (it can receive a different address).
 All Zigbee transmissions are sent using the source and destination 16-bit addresses. The routing
tables on Zigbee devices also use 16-bit addresses to determine how to route data packets
through the network. However, since the 16-bit address is not static, it is not a reliable way to
identify a device.
 To solve this problem, the 64-bit destination address is often included in data transmissions to
guarantee data is delivered to the correct destination. The Zigbee stack can discover the 64-bit
address, if unknown, before transmitting data to a remote.
Application Layer Addressing
Zigbee devices support multiple application profiles, cluster IDs, and endpoints. API mode provides a
simple yet powerful interface that easily sends data to any profile ID, cluster ID and endpoint
combination on any device in a Zigbee network.
ZigBee - Security
Centralized Security Network Only Zigbee coordinators/trust centres can initiate
centralized networks. Nodes join, receive the network
key and establish a unique trust centre link key. Nodes
communicate with each other only through the
coordinator. This security pattern in seen in Zigbee star
topology.
Zigbee assumes an “open trust” model. The protocol
stack layers trust each other. The layer that originates
a frame is responsible for its security.

Distributed Security Network

No central node/trust centre. Routers are able to initiate
distributed networks. Nodes join and receive the network
key. This security pattern in seen in Zigbee mesh topology.
Zigbee is considered to be a secure wireless communication
protocol, with security architecture built in accordance with
IEEE 802.15.4 standard.
ZigBee- APPLICATIONS IN IoT
 Home automation.
 Wireless sensor networks.
 Industrial control systems.
 Embedded sensing.
 Medical data collection.
 Smoke and intruder warning.
 Building automation.
 Remote wireless microphone configuration.
1.2.4 Z-Wave - Overview
 Z-Wave is a wireless communication protocol used primarily in smart home networks, allowing
smart devices to connect and exchange control commands and data with each other.
 With two-way communication through mesh networking and message acknowledgment, the Z-
Wave protocol brings low-cost wireless connectivity to home automation, offering a lower-
power alternative to Wi-Fi and a longer-range alternative to Bluetooth.
 A Z-Wave network consists of internet of things (IoT) devices and a primary controller, also
known as a smart home hub, which is the only device in a Z-Wave network that is usually
connected to the internet. When a Z-Wave hub receives a command from a smart home
application on a user's smartphone, tablet or computer, it routes the command to its destination
device across networks of up to 232 devices - including the hub.
 The Z-Wave protocol operates on the low-frequency 908.42 band in the U.S. and the 868.42
MHz band in Europe. Though interference with other home electronics, such as cordless
phones, is possible, the protocol avoids interference with the 2.4 GHz band where Wi-Fi and
Bluetooth operate.
 Z-Wave offers transmission rates of small data packets using throughput rates of 9.6 kbps, 40
kbps or 100 kbps. The Z-Wave PHY and MAC layers are based on the ITU-T G.9959 global radio
standard, and the protocol uses GFSK modulation and Manchester encoding.
 Communication between devices ranges from 98 to 328 feet; the 500 Series has a range of 130
feet and the 700 Series 328 feet. Because walls and other dense building materials limit the range,
the general deployment best practice is to place Z-Wave devices 50 feet or fewer apart for
maximum signal strength.
 In regards to battery life, some 700 Series Z-Wave devices can last up to 10 years on a coin cell
battery, while many other battery-powered devices last a year or longer. All Z-Wave technology is
backward-compatible, i.e. they can work with old devices too.
 The Z-Wave Alliance, a consortium of industry leaders, manufacturers and integrators aimed at
developing and expanding Z-Wave applications and capabilities, was founded in 2005.
Z-Wave - Protocol Stack
 Z-wave protocol stack consists of 5 layers; PHY layer, MAC layer, Transport APPLICATION
Zwave specific cmds.
layer, network layer and application layer. The security layer is not defined app specific cmds.
in z-wave open protocol specifications and hence it is implementation
specific. Following are the major functions of these protocol layers; NETWORK
1. Physical layer takes care of modulation and RF channel assignment as well Frame Routing,
Topology Scan,
preamble addition at the transmitter and synchronization at the receiver Routing Table Update
using preamble. Based on the ITU-T G.9959 global radio standard.
2. MAC layer takes care of HomeID and NodeID, controls the medium TRANSPORT
between nodes based on collision avoidance algorithm and backoff Retransmission, ACK,
Checksum
algorithm. Based on the ITU-T G.9959 global radio standard.
3. Transport layer takes care of transmission and reception of frames, takes MAC
care of retransmission, ACK frame transmission and insertion of checksum. ITU-T G.9959 Global
Radio Standards
4. Network layer takes care of frame routing, topology scan and routing table
updates. PHY
5. Application layer takes care of control of payloads in the frames received ITU-T G.9959 Global
Radio Standards
or to be transmitted.
Z-Wave - Topology
 Z-Wave Mesh topology includes the controller and other slave devices. The controller acts as a
gateway in between devices and network.
 In few cases there will be also a secondary Controller on the mesh for assistance to the Primary
controller. The transport layer of the Z-Wave stack manages the frame transport from one node to
another.
Z-Wave - Addressing
 Z-Wave Mesh topology includes the single Primary Controller and four slaves and one enhanced
slave. The bridge controller acts as a gateway to a WiFi network.
 A Portable Controller and Secondary Controller also sits on the mesh for assistance to the Primary
Controller. The routing layer of the Z-Wave stack manages the frame transport from one node to
another.
 The Z-Wave protocol uses a 32 bit identifier to address the devices it controls. i.e. if a device
needs to be controlled by a microcontroller then every device controlled by that microcontroller is
assigned a common Home ID. Once the device is added to the network the device looks for other
devices and adds them to the same network.
 When devices are being added to the network through devices that have already been added the
device in turn return assigns the same Home ID but a different Node ID. The node ID is a 8 bit
identifier.
 A device can be spotted by a microcontroller only if the Home ID on the microcontroller is same as
the one on the device. Hence the path to be chosen by the microcontroller to send a signal is
through devices which have the same Home ID only.
 When two different networks are present they know each other are present but they are not
interoperable.
Z-Wave - APPLICATIONS IN IoT
 Smart Hubs
Smart hubs are the central controlling unit of every smart home application. Wide range of appliances,
devices, power plugs, locking units, security systems, access control units, routers, sensors and voice
enabled applications can be connected and configured using smart hubs.
 Smart Lighting
Light intensity can be wirelessly controlled and configured using a mobile phone app which can be
accessed from anywhere.
 Security and Alarm
Z-wave provides smart solutions for Indoor and outdoor security, monitoring systems and alarms.
Temperature and smoke detectors will continuously monitor and trigger alarms when the measured
level exceeds set threshold value.
 Water management
Accurate water and flood sensors are used in water management and smart city systems. Smart
sensors will monitor water level round the clock and triggers once the level exceeds.
 Smart USB
Smart USB will convert any personal computer running Z-wave software to a smart hub for home
automation applications.
Z-Wave vs ZigBee
 Z-Wave and Zigbee are two of the biggest names in smart home communication protocols. Both
use short-range, low-power radio signals and mesh network technologies, and both are secured
using AES. However, there are some notable differences. Z-Wave operates on the low-frequency
908.42 band while the Zigbee protocol operates at 2.4 GHz. While the higher frequency allows
Zigbee to transmit more data and faster too, 40-250 kbps while Z-Wave support 9.6 to 100 kbps.
 A Zigbee network, which doesn't have a maximum number of allowed hops, can support more
than 65,000 devices, while a Z-Wave network, limited to four hops, supports a maximum of 232
devices.
 Many smart home hubs today, including Samsung SmartThings and Wink Hub, support both
standards, allowing Zigbee and Z-Wave devices to communicate with each other, so there is no
need to choose one over the other.

END OF UNIT 1