REST and CoRE, TCP, UDP, 6 LoWPAN,

CoAP, MQTT
Constrained RESTful Environment
• IoT and M2M devices communicate within themselves with a LAN.
Each node sends 10s of data.
• The gateway received 100s of data from many end devices. In the
communication framework, the gateway enables communication of
the devices over a REST software architecture.
• Constrained devices- data is Limited in size
• ROLL networks- a wireless network with a low power transceiver.
Devices usually are in sleep mode
• ROLL- Routing over a network of Low power and Data Loss.
REST
• The Representational State Transfer (REST) architectural style [REST] is a
set of guidelines and best practices for building distributed hypermedia
systems.
• At its core is a set of constraints, which when fulfilled enable desirable
properties for distributed software systems such as scalability and
modifiability.
• When REST principles are applied to the design of a system, the result is
often called RESTful and in particular an API following these principles is
called a RESTful API.
• Since RESTful APIs are often simple and lightweight, they are a good fit
for various IoT applications.
REST Terminologies
• Cache: A local store of response messages and the subsystem that controls storage,
retrieval, and deletion of messages in it.
• Client: A node that sends requests to servers and receives responses. In RESTful IoT
systems it’s common for nodes to have more than one role (e.g., both server and
client).
• Client State: The state kept by a client between requests. This typically includes the
currently processed representation, the set of active requests, the history of
requests, bookmarks (URIs stored for later retrieval), and application-specific state
(e.g., local variables).
• Content Negotiation: The practice of determining the “best” representation for a
client when examining the current state of a resource. The most common forms of
content negotiation are Proactive Content Negotiation and Reactive Content
Negotiation.
• Form: A hypermedia control that enables a client to change the state of a resource
or to construct a query locally.
REST Terminologies
• Forward Proxy: An intermediary that is selected by a client, usually via local
configuration rules, and that can be tasked to make requests on behalf of the client.
This may be useful, for example, when the client lacks the capability to make the
request itself or to service the response from a cache in order to reduce response
time, network bandwidth, and energy consumption.
• Gateway: A reverse proxy that provides an interface to a non-RESTful system such as
legacy systems or alternative technologies such as Bluetooth ATT/GATT.
• Hypermedia Control: A component, such as a link or a form, embedded in a
representation that identifies a resource for future hypermedia interactions. If the
client engages in an interaction with the identified resource, the result may be a
change to resource state and/or client state.
• Idempotent Method: A method where multiple identical requests with that method
lead to the same visible resource state as a single such request.
• Link: A hypermedia control that enables a client to navigate between resources and
thereby change the client state.
REST Terminologies
• Link Relation Type: An identifier that describes how the link target resource
relates to the current resource (Ref [RFC5988]).
• Media Type: A string such as “text/html” or “application/json” that is used to
label representations so that it is known how the representation should be
interpreted and how it is encoded.
• Method: An operation associated with a resource. Common methods include
GET, PUT, POST, and DELETE
• Origin Server: A server that is the definitive source for representations of its
resources and the ultimate recipient of any request that intends to modify its
resources. In contrast, intermediaries (such as proxies caching a representation)
can assume the role of a server, but are not the source for representations as
these are acquired from the origin server.
REST Terminologies
• Proactive Content Negotiation: A content negotiation mechanism where the server selects
a representation based on the expressed preference of the client.
• Reactive Content Negotiation: A content negotiation mechanism where the client selects a
representation from a list of available representations. The list may, for example, be
included by a server in an initial response. If the user agent is not satisfied by the initial
response representation, it can request one or more of the alternative representations,
selected based on metadata (e.g., available media types) included in the response.
• Representation: A serialization that represents the current or intended state of a resource
and that can be transferred between clients and servers. REST requires representations to
be self-describing, meaning that there must be metadata that allows peers to understand
which representation format is used. Depending on the protocol needs and capabilities,
there can be additional metadata that is transmitted along with the representation.
• Representation Format: A set of rules for serializing resource state. On the Web, the most
prevalent representation format is HTML. Other common formats include plain text and
formats based on JSON [RFC7159], XML, or RDF. Within IoT systems, often compact
formats based on JSON, CBOR [RFC7049], and EXI [W3C.REC-exi-20110310] are used.
REST Terminologies
• Resource: An item of interest identified by a URI. Anything that can be
named can be a resource. A resource often encapsulates a piece of state
in a system. Typical resources in an IoT system can be, e.g., a sensor, the
current value of a sensor, the location of a device, or the current state of
an actuator.
• Resource State: A model of a resource’s possible states that is
represented in a supported representation type, typically a media type.
Resources can change state because of REST interactions with them, or
they can change state for reasons outside of the REST model.
• Resource Type: An identifier that annotates the application-semantics of
a resource
REST Terminologies
• Reverse Proxy: An intermediary that appears as a server towards the
client but satisfies the requests by forwarding them to the actual server
(possibly via one or more other intermediaries). A reverse proxy is often
used to encapsulate legacy services, to improve server performance
through caching, and to enable load balancing across multiple machines.
• Safe Method: A method that does not result in any state change on the
origin server when applied to a resource.
• Server: A node that listens for requests, performs the requested
operation and sends responses back to the clients.
• Uniform Resource Identifier (URI): A global identifier for resources
Architecture
Architecture
 URI

A URI is a sequence of characters that matches the syntax defined in [RFC3986].

It consists of a hierarchical sequence of five components: scheme, authority, path, query, and fragment
(from most significant to least significant).
• A scheme creates a namespace for resources and defines how the following components identify a resource within
that namespace.
• The authority identifies an entity that governs part of the namespace, such as the server “www.example.org” in the
“http” scheme.
• A host name (e.g., a fully qualified domain name) or an IP address, potentially followed by a transport layer port
number, are usually used in the authority component for the “http” and “coap” schemes.
• The path and query contain data to identify a resource within the scope of the URI’s scheme and naming authority.
• fragment allows to refer to some portion of the resource, such as a Record in a SenML Pack. However, fragments are
processed only at client side and not sent on the wire
6 Low PAN
Introduction
• Ubiquitous computing, where computers interact with each other
• Currently, two main approaches, namely, the proxy-based and the
sensor stack-based are used to connect WSNs to IP networks.
• In the proxy-based approach, the sink node serves as the gateway between the
sensor node and Internet.
• In the stack-based approach, the IP protocol is implemented in each node to
allow data exchange inside the sensor network. It also enables connectivity with
other IP based networks. decisions on behalf of the user, needs to be IP enabled.
• In order to gain the benefits of Internet and to confront the limitations
of WSN, the protocols developed for Integration of WSN over Internet
need to be light weight.
Features
• 6LoWPAN (Jonathan Hui et al., 2009) is an upcoming technology that allows
connectivity among nodes with limited power by importing IPv6
capabilities into the low-power nodes.
• 6LoWPAN adopts the physical (PHY) and Media Access Control (MAC) layer
protocols defined in IEEE 802.15.4 standard as its lower layer protocols.
• The IPv6 protocol is used as the network layer protocol in 6LoWPAN. Since
the IPv6 network layer's Maximum Transmission Unit (MTU) is not
compatible with the MAC layer of IEEE 802.15.4, an adaptation layer is
introduced between the network and MAC layers.
• It performs fragmentation, reassembling, IPv6 header compression, and
addressing mechanism to enable compatibility
Features
• 6LoWPAN standards enable the efficient use
of IPv6 over low power, low rate wireless
networks on simple embedded nodes
through an adaptation layer and
optimisation of related protocols.
• The Maximum frame size of LOWPAN packet
is 128 octets as specified by IEEE 802.15.4
while the frame size of IPv6 is 1280 octets.
• In order to alleviate incompatibility,
6LoWPAN working group has suggested an
additional adaptation layer between MAC
layer and the network layer.
Physical Layer
• To enable the efficient transmission of payload, header compression is mandatory. Also
fragmentation and reassembling of packets and layer-two forwarding is required. Thus,
the adaptation layer introduced between the MAC and Network layer.
• 6LoWPAN PHY layer provides two services namely the PHY data service and PHY
management service.
• Both the service interfaces with Physical Layer Management Entity (PLME) Service
Access Point (SAP) known as the PLME-SAP (Zach Shelby et al., 2009).
• The key function of PHY data services is to provide transmission and reception of data
packets between MAC and PHY through the physical radio channel.
• The PHY management service interface, offers access to every layer management
function and maintains a database of information on related personal area networks.
• It is based on IEEE 802.15.4 standard which operates at the frequency of 2400 –
2483.5MHz offering a data rate of 250 kbps. The protocol data unit is IEEE 802.15.4
compliant with a maximum payload of 127 bytes.
Data Link and adaptation Layers
• The Data Link layer provides services to enable reliable, single-hop communication
links between 6LoWPAN nodes. The MAC Protocol Data Unit (PDU) is IEEE 802.15.4
compliant which operates in non beacon-enabled mode. In non-beacon - enabled
networks, data frames (including those carrying IPv6 packets) are transmitted via the
contention-based channel access method such as un-slotted CSMA/CA.
• The adaptation layer is the main component of 6LoWPAN.
• The major function of this layer is the TCP/IP header compression.
The IEEE 802.15.4 frame has a maximum packet size of 128 bytes, whereas IPv6 header size is 40
bytes, User Datagram Protocol (UDP) and Internet Control Message Protocol (ICMP) header sizes
are both 4 bytes, fragmentation header adds another 5 bytes overhead. However, without
compression, it is not possible to transmit any payload effectively.
• A second major function of the adaptation layer is to handle packet fragmentation and
reassembling.
IEEE 802.15.4 has a maximum frame size of 128 bytes, while IPv6 requires a maximum
transmission unit (MTU) of 1280 bytes. This mismatch is handled in the adaptation layer.
• The next major function of the adaptation layer is routing
6 Low Pan for WSN
• The 6LoWPAN network layer provides the internetworking capability to sensor nodes.
The main considerations of this layer are addressing, mapping and routing protocols.
• It addresses IPv6 requirement and provides appropriate security services.
• It also supports routing and network management with SNMP (Simple Network
Management Protocol).
• In 6LoWPAN, being based on the process of packet forwarding, the routing is
classified into two schemes such as mesh-under and route-over.
• In Mesh-Under, The decision of routing occurs in 6LoWPAN adaptation layer.
• In Route-over, the decision is executed in 6LoWPAN network layer.
In route-over scheme, each link layer hop is an IP hop and each node acts as IP router. The packet
is forwarded hop by hop from source to destination between these links. The payload packet is
encapsulated with IP header. Later, IP packet is fragmented and is sent to the next hop node
based on routing table information. when the adaptation layer in the next hop receives all the
fragments successfully, it creates an IP packet from fragments and forwards it to the network
layer. Further, the network layer sends the packet to the upper layer (transport layer), conditional
to the desired destination being reached. Otherwise, it forwards the packet to the next hop node
according to the routing table information. Whenever fragment loss is encountered, all fragments
are retransmitted to one hop distance.
Architecture
Challenges
• IP Connectivity: The need for IP connectivity within a LoWPAN is realised by
connecting the sensor nodes to other IP-based networks or to embedded
devices. As nodes in the 6LoWPAN network increase, the necessity for
network auto configuration and statelessness is highly required which can
be achieved through IPv6 as it offers 2128 bits of address.
• Limited Packet Size: Applications developed using 6LoWPANs should
support only small packets as devised by IEEE 802.15.4. Hence routing
protocols need to be designed in a manner as specified by the IEEE
802.15.4 frame. Whenever the packet size exceeds 127 bytes, it may pose
challenges for low end 6LoWPAN nodes, as they do not have enough RAM
or storage to accommodate 1280 sized packet.
Challenges
• Limited Configuration and Management: Nodes within the LoWPAN can be deployed in
large numbers. Also these LoWPAN devices posses limited input and display capabilities.
Also the location of some of these devices are hard to access. However, protocols used in
LoWPANs should have minimal configuration, be easy to bootstrap, and enable the
network to self heal given the inherent unreliable characteristic of these nodes. The size
constraints of the link layer protocol should also be considered. Network management
should have little overhead, yet be powerful enough to control dense deployment of
nodes in the network.
• Service Discovery and Security consideration: 6LoWPANs require service discovery
network protocol to discover, control and maintain services provided by nodes. New
protocols must be designed to enable such features in the nodes.
• 6LoWPAN networks poses certain challenges such as the failure of node due to lack of
power, physical damage or environmental interference leading to rerouting or re-
organisation of the network.
TCP/UDP
 The Transport Layer

GOAL: The Transport Layer provides logical communication between application

processes running on different hosts.

Transport protocols run in the end systems (end-to-end)

• The sending side breaks application messages into segments and passes them
down to the Network layer
• The receiving side reassembles the segments into messages and passes them up
to the Application layer

NOTE:
• The Network Layer provides logical communication between hosts.
• The Transport Layer provides logical communication between processes.
 Transport Layer Protocols

Two Transport Protocols are available for Applications to use on the Internet:
1. UDP
2. TCP

UDP (User Datagram Protocol)

Provides: Unreliable, unordered delivery of segments.

TCP (Transmission Control Protocol)

Provides: Reliable, in-order delivery of segments.

TCP includes:
• Connection set-up (3-way handshake)
• Flow Control
• Congestion Control

NOTE: Neither protocol provides:

• Delay guarantees
• Bandwidth guarantees
 UDP (User Datagram Protocol)

UDP is:
• A “no frills,” “bare bones” Internet Transport protocol
• Provides “best effort” service
UDP segments may be:
 lost
 delivered out of order to application
• Connectionless
UDP:
 has no handshaking between UDP sender, receiver
 each UDP segment handled independently of others
 UDP (User Datagram Protocol) (cont’d)

Since UDP provides so few services, why is there a UDP?

1. UDP has no connection establishment =>

• So it has lower delay
• It is simple (no connection state is need at sender, receiver)
• It has a small segment header
2. UDP has no congestion control =>
• UDP can blast away as fast as desired

Uses of UDP:

• It is often used for streaming multimedia apps, because UDP is:

 loss tolerant
 rate sensitive
• UDP is also used in:
 DNS
 SNMP
 TCP (Transmission Control Protocol)

TCP characteristics:
• point-to-point connections
 one sender, one receiver
• full duplex data:
 bi-directional data flow in same connection
• reliable, in-order byte steam transmission
 with no “message boundaries” between bytes
• pipelined transmission
 multiple segments are sent at the same time
 Maximum segments sent simultaneously = TCP congestion/flow
control window size
 send & receive buffers at sender and receiver
• connection-oriented:
 handshaking occurs between the sender, receiver before data
exchange
• Uses flow control:
 The sender will not overwhelm receiver’s buffer
 TCP (Transmission Control Protocol) (cont’d)

Conceptual View

Figure from Kurose & Ross, Networking: A Top Down Approach

 TCP (Transmission Control Protocol) (cont’d)

TCP creates reliable data service on top of IP’s (Layer 3’s) unreliable delivery service.

To make transmission reliable, TCP uses:

• pipelined transmission of segments
• send & receive buffers at sender and receiver
• ACKs (Acknowledgement) messages sent when segments are received
correctly
• A retransmission timer
 The time will expire if an ACK is not received during the specified time
• Retransmissions of segments occur whenever the timer expires.

NOTE: We are skipping the “messy” details of Reliable data transmission!

 TCP (Transmission Control Protocol) (cont’d)

Important: When an Application sends a message down the protocol stack, it selects
whether TCP or UDP should be used for the transmission:
 IoT Communication Models

•Request –Response
•Publish-Subscribe
•Push-Pull
•Exclusive Pair
 Request Response
Communication Model

SERVER
Receives Req
from
CLIENT
Client,processes
Sends Req,looksup/ RESOURCES
Request to Fetches
Server resources,
Prepares
response and
sends response
to client
Publish-Subscribe Communication Model
Push-Pull Communication Model
Exclusive Pair Communication Model
 IoT Communication API’s

• REST-based Communication APIs.

• WebSocket-based Communication APIs

REST(Representational State Transfer)is a set of architectural principles

by which you can design web services and web APIs that focus on a
system’s resources and how resource states are addressed and
transferred.
 REST-based Communication APIs.

• REST APIs follow the Request-Response communication.

• REST architectural constraints:
Client-server
Stateless
Cache-able
Layered System
Uniform Interface
Code on Demand
Communication with REST APIs
Request Response Model used by REST
HTTP request methods and actions
 Points to Note

• RESTfull web service is a webAPI implemented using HTTP and REST

principles.
• RESTfull web service is a collection of resources which are
represented by URIs.
• RESTfull web API has a base URI(e.g.http://example.com/api/tasks/).
• Client sends request to these URIs using the HTTP methods
• RESTfull web service can support various internet media types(JSON)
 WebSocket-based
Communication APIs
• WebSocket APIs allow bi-directional ,full duplex communication
between clients and servers.
• Follows Exclusive pair communication model.
• Unlike request-response APIs such as REST, the
WebSocket APIs allow full duplex communication and do not require a
new connection to be setup for each message to be sent.
Application
layer
protocols
Constrained request response
CoAp
APPLICATION LAYER(CONTD.)
MQTT (MESSAGE QUEUE
TELEMETRY TRANSPORT)
Zigbee
WPAN Technologies for IoT/M2M
• The following network topologies are applicable to personal low-power
radio networks:
• Broadcast: environment where a message is sent from a device in the hope that it
is received by a receiver within range. The broadcaster does not receive signals;
• Mesh: environment where a message can be relayed from one point in a network
to any other by hopping through multiple nodes;
• Star: environment where a central device can communicate with a number of
connected devices;
• Scanning: environment where a scanning device is constantly in receive mode,
waiting to pick up a signal from anything transmitting within range;
• Point-to-point: in this mode, a one-to-one connection exists, where only two
devices are connected over the communication path.

50
WPAN Technologies for IoT/M2M
• Zigbee/IEEE 802.15.4
• Bluetooth and its Low-Energy Profile
• NFC
• RFID

51
WPAN Technologies for IoT/M2M
Zigbee/IEEE 802.15.4
• The commercialization of consumer-based IoT services requires the introduction of
wireless, low-power, battery-powered sensors and actuators in people’s premises.
• ZigBee’s focus aimed at the “little devices” (things, objects) like light switches,
thermostats, electricity meters, remote controls (RCs), as well as more complex
sensor devices found in the healthcare, commercial building, and industrial
automation sectors.
• To avoid multiple separate consumer networks, a PHY/MAC-agnostic solution is
needed upon which IP standards and other well-known higher-layer protocols can
run with little changes.
• ZigBee is one such open standard, as discussed below. ZigBee IP (ZIP) is an example
where Zigbee systems operate in an IP context.
• Here we focus more on the wireless lower-layer aspects of Zigbee and not the IP part.

52
WPAN Technologies for IoT/M2M
Zigbee/IEEE 802.15.4
• ZigBee utilizes the globally available, license-free 2.4 GHz industrial,
scientific, and medical (ISM) frequency band to provide low data rate
wireless applications
• IEEE 802.15.4, wireless links can operate in three unlicensed
frequency bands, namely the 858 MHz band, the 902-to-928 MHz
band, and the 2.4 GHz band
• IEEE 802.15.4 defines a robust radio PHY (physical) layer and MAC
(medium access control) layer, while ZigBee defines the network,
security, and application framework for an IEEE 802.15.4-based
system.

53
WPAN Technologies for IoT/M2M
Zigbee/IEEE 802.15.4
• ZigBee networks support star, mesh, and cluster-tree topologies.
• These capabilities enable a network to have over 65,000 devices on a single
wireless network.
• ZigBee offers low-latency communication between devices without the
need for the initial network synchronization delays as required by
Bluetooth.
• ZigBee can create robust self-forming, self-healing wireless mesh networks.
The ZigBee mesh network connects sensors and controllers without being
restricted by distance or range limitations;
• ZigBee mesh networks allow all participating devices to communicate with
one another and act as repeaters transferring data between devices.
54
WPAN Technologies for IoT/M2M
Zigbee/IEEE 802.15.4
• ZigBee is available as two feature sets,
• ZigBee PRO and ZigBee.
• Both feature sets define how the ZigBee mesh networks operate.

• ZigBee PRO, the most widely used and optimized for low-power
consumption and to support large networks with thousands of devices.
• The ZigBee Alliance announced an expanded set of features for the ZigBee
protocol.
• This new stack profile is universally referred to as ZigBee PRO and for the most
part defines specific stack settings and makes mandatory many of the features.
• ZigBee PRO also used in some new application like automatic meter
reading, commercial building automation, and home automation.
55
WPAN Technologies for IoT/M2M
Zigbee/IEEE 802.15.4
• ZigBee PRO features implement support for larger networks,
• for example stochastic addressing to assign addresses using probability analysis to
simplify network formation.
• ZigBee PRO implements a technique known as frequency agility (not hopping):
• a network node is able to scan for clear spectrum (with a choice of 16 available
channels) and communicate its findings back to the ZigBee coordinator so that a new
channel can be used across the network.
• ZigBee PRO networks have the ability to aggregate routes through the use of
“many-to-one” routing;
• this allows each device to share the same routing path reducing broadcast and
network traffic and greatly improves the efficiency and stability of the network routing
table.

56
WPAN Technologies for IoT/M2M
Zigbee/IEEE 802.15.4
• The ZigBee 802.15.4 spec defines a maximum packet size of 128
octets;
• this packet size is optimal for short control messages, but there may be
instances where the network needs to send larger messages;
• therefore, ZigBee PRO now has the means to automatically fragment and reassemble a message at a
receiving node relieving the host application of this overhead.

• The ZigBee Alliance is a global ecosystem of 400+ companies in the

M2M/IoT space developing standards and producing products for use
in commercial building automation, consumer electronics, health care
and fitness, home automation, energy management, retail
management, and wireless telecommunications.

57
WPAN Technologies for IoT/M2M
Zigbee/IEEE 802.15.4
• LR-WPANs (Low-Rate Wireless Personal Area Networks) applications require a
low-cost, small-size, highly reliable technology which offers long battery life,
measured in months or even years, and automatic or semiautomatic
installation.
• ZigBee is a low-power wireless specification that introduces mesh networking
to the low-power wireless space and is targeted toward applications such as
smart meters, home automation, and RC units. ZigBee technology provides
reasonably efficient low-power connectivity and ability to connect a large
number of devices into a single network.
• Some studies have shown that for the home, two wireless PHY layer
communications technologies that best meet the overall
• performance and cost requirements are Wi-Fi (802.11/n) and ZigBee (802.15.4).
58
WPAN Technologies for IoT/M2M
Zigbee/IEEE 802.15.4
• Disadvantages:
• ZigBee’s relative complexity (as seen in the protocol stack) and the
apparent fact that the power consumption of ZigBee devices is higher
than the consumption of some alternatives (e.g., BLE) tend to make
ZigBee not always the most ideal solution for unmaintained devices
that need to operate for extensive periods of time from a limited
power source;
• hence, while many home applications make ideal use of ZigBee, other
IoT/M2M applications can also be supported by other approaches.

59
WPAN Technologies for IoT/M2M
Zigbee/IEEE 802.15.4
• ZigBee makes use of the physical radio specified by IEEE 802.15.4; it
adds logical network capabilities, and security and application
software.

60
WPAN Technologies for IoT/M2M
Zigbee/IEEE 802.15.4
• The PHY layer of the reference model specifies the network interface
components, parameters, and operation.
• The PHY layer includes a variety of features, such as
• receiver energy detection (RED),
• link quality indicator (LQI),
• clear channel assessment (CCA).
• The PHY layer is also including low-duty cycle operations, strict power
management, and low transmission overhead.
• IEEE 802.15.4 defines several addressing modes:
• it allows the use of either IEEE 64-bit extended addresses or 16-bit addresses
unique within the PAN.
61
WPAN Technologies for IoT/M2M
Zigbee/IEEE 802.15.4
• MAC layer handles network association and disassociation.
• It also regulates access to the medium; this is achieved through two
modes of operation:
• beaconing
• nonbeaconing.
• The beaconing mode is specified for environments where control and data forwarding is achieved
by an always active device.
• The nonbeaconing mode specifies the use of unslotted, non persistent CSMA-based MAC protocol.

62
WPAN Technologies for IoT/M2M
Zigbee/IEEE 802.15.4
• The network layer provides the functionality required to support
network routing capabilities, configuration and device discovery,
association and disassociation, topology management, MAC layer
management, and routing and security management.
• Three network topologies, namely star, mesh, and cluster tree, are
supported.

63
WPAN Technologies for IoT/M2M
Zigbee/IEEE 802.15.4
• The security layer leverages the basic security services specified by
the IEEE 802.15.4 security model to provide support for infrastructure
security and application data security.

64
WPAN Technologies for IoT/M2M
Zigbee/IEEE 802.15.4
• The application layer consists of the application support sublayer
(APS), the ZigBee device object (ZDO), and the manufacturer-defined
application objects.
• The responsibilities of the APS sublayer include maintaining tables for binding
devices together, based on their services and their needs, and forwarding
messages between bound devices.

65
WPAN Technologies for IoT/M2M
Zigbee/IEEE 802.15.4
• ZigBee is not a frequency-hopping technology; therefore, it requires careful planning
during deployment in order to ensure that there are no interfering signals in the vicinity.
• The design of the PHY layer is driven by the need for low-cost, power-effective PHY layer
for cost-sensitive, low data rate monitoring and control applications.
• Under IEEE 802.15.4, wireless links can operate in three unlicensed frequency bands,
namely in the 858 MHz band, in the 902-to-928 MHz band, and in the 2.4 GHz band.
• Based on these frequency bands, the IEEE 802.15.4 standard defines three physical
media:
• Direct sequence spread spectrum (DSSS) using binary phase shift keying (BPSK), operating in the
868 MHz at a data rate of 20 Kbps;
• DSSS using BPSK, operating in the 915 MHz at a data rate of 40 Kbps
• DSSS using offset quadrature phase shift keying (O-QPSK), operating in the 2.4 GHz at a data rate
of 140 Kbps.

66
WPAN Technologies for IoT/M2M
Zigbee/IEEE 802.15.4
• In order to accommodate the MAC protocol, the IEEE 802.15.4 standard
distinguishes devices based on their hardware complexity and
capability.
• The standard defines two classes of physical devices, namely:
• a full function device (FFD)
• a reduced function device (RFD).
• These device types differ in their use and how much of the standard they implement.

• An FFD is equipped with the adequate resources and memory capacity

to handle all the functionalities and features specified by the standard.
• An RFD is a simple device that carries a reduced set of functionalities,
for lower cost and complexity.
67
WPAN Technologies for IoT/M2M
Zigbee/IEEE 802.15.4
• Based on these physical device types, ZigBee defines a variety of logical device types.
There are three categories of logical devices:
• Network coordinator: An FFD device responsible for network establishment and
control. The coordinator is responsible for choosing key parameters of the network
configuration and for starting the network. It also stores information about the
network and acts as the repository for security keys.
• Router: An FFD device that supports the data routing functionality, including acting as
an intermediate device to link different components of the network and forwarding
message between remote devices across multihop paths. A router can communicate
with other routers and end devices.
• End Devices: An RFD device that contains (just) enough functionality to communicate
with its parent node, namely the network coordinator or a router. An end device does
not have the capability to relay data messages to other end devices.
68
WPAN Technologies for IoT/M2M
Zigbee/IEEE 802.15.4
• A PAN coordinator is the designated principal controller of the WPAN. Every
network has exactly one PAN coordinator, selected from within all the
coordinators of the network. A coordinator is a network device configured to
support network functionalities and additional responsibilities, including:
• Managing a list of all associated network devices;
• Exchanging data frames with network devices and peer coordinator;
• Allocating 16-bit short addresses to network devices. The short addresses, assigned
on-demand, are used by the associated devices in lieu of the 64-bit addresses for
subsequent communications with the coordinator;
• Generating, on a periodic basis, beacon frames. These frames are used to announce
the PAN identifier, the list of outstanding frames, and other network and device
parameters.

69
WPAN Technologies for IoT/M2M
Zigbee/IEEE 802.15.4
• Based on these logical device types, a ZigBee WPAN can be organized
into one of three possible topologies, namely a star, a mesh (peer-to-
peer), or a cluster tree.

70
WPAN Technologies for IoT/M2M
Zigbee/IEEE 802.15.4
• The star network topology supports a single coordinator, with up to
65,536 devices. In this topology configuration, one of the FFD-type
devices assumes the role of network coordinator. All other devices act
as end devices. The selected coordinator is responsible for initiating and
maintaining the end devices on the network. Upon initiation, the end
devices can only communicate with the coordinator.
• The mesh configuration allows path formation from any source device
to any destination device, using tree- and table-driven routing
algorithms.
• Cluster-tree networks enable a peer–peer network to be formed with a
minimum of routing overhead, using multihop routing.
71
WPAN Technologies for IoT/M2M
Zigbee/IEEE 802.15.4
• The ZDO (ZigBee device object) represents a predefined base class of
functionality upon which all applications are written.
• The ZDO creates an abstraction so that the developer can focus on
writing application-specific code rather than dealing with the low-
level details.
• The ZDO provides an interface between the application objects, the
profile (e.g., the ZigBee Health Care), and the APS.
• The ZDO is responsible for initializing the APS, the network layer, and
the security service provider.

72
WPAN Technologies for IoT/M2M
Zigbee/IEEE 802.15.4
• ZigBee is designed for low-to-very-low-duty cycle static and dynamic
environments with many active nodes;
• Bluetooth, is designed for high QoS, variety of duty cycles, and
moderate data rates in networks with limited active nodes.

73
Bluetooth
WPAN Technologies for IoT/M2M
Bluetooth and its Low-Energy Profile- Overview

• Bluetooth is a WPAN technology based on IEEE

802.15.1
• Bluetooth was initially developed by Ericsson; in the
late 1990s, the Bluetooth Special Interest Group (SIG)
made their specifications publicly available.
• Soon thereafter, the IEEE 802.15 Group took the
Bluetooth work and developed a vendor-independent
standard.

75
WPAN Technologies for IoT/M2M
Bluetooth and its Low-Energy Profile- Overview
• Bluetooth is a short-range data exchange communication protocol
widely used in cellular phones, smartphones, tablets, and PDAs (has a
range of about 10 m, or a maximum of 100 m with power boost).
• Bluetooth is designed for a small variety of tasks, such as
synchronization, voice headsets, cell-modem calls, and mouse and
keyboard input.
• The Bluetooth specification defines a low-power, low-cost technology
that provides a standardized platform for eliminating cables between
mobile devices and facilitating connections between products.

76
WPAN Technologies for IoT/M2M
Bluetooth and its Low-Energy Profile- Overview
• Bluetooth operates in the 2.4-GHz ISM band and has a bandwidth of
approximately 1–3 Mbps.
• While the cost of Bluetooth equipment is significantly lower than the
cost of WLAN, the transmission range of 10 m or less and the data
transfer rate 12 Mbps or less (in Version 2.0 of the standard) are often
considered a drawback.

77
WPAN Technologies for IoT/M2M
Bluetooth and its Low-Energy Profile- Overview

78
WPAN Technologies for IoT/M2M
Bluetooth and its Low-Energy Profile- Overview
• The sublayers of IEEE 802.15 are as follows:
• (i) RF layer;
• (ii) baseband layer;
• (iii) the link manager (an MAC-level protocol);
• (iv) the logical link control and adaptation protocol (L2CAP) (also an MAC-level
protocol).

79
WPAN Technologies for IoT/M2M
Bluetooth and its Low-Energy Profile- Overview
• RF layer: The air interface is based on antenna power range starting from 0 dBm up
to 20 dBm, 2.4 GHz band, and the link range from 0.1 to 10 m.
• Baseband layer: The baseband layer establishes the Bluetooth piconet. The piconet is
formed when two Bluetooth devices connect. In a piconet, one device acts as the
master and the other devices act as slaves.
• Link manager: The link manager establishes the link between Bluetooth devices.
Additional functions include security, negotiation of Baseband packet sizes, power
mode and duty cycle control of the Bluetooth device, and the connection states of a
Bluetooth device in a piconet.
• L2CAP: This sublayer provides the upper-layer protocols with connectionless and
connection-oriented services. The services provided by this layer include protocol
multiplexing capability, segmentation and reassembly of packets, and group
abstractions.
80
WPAN Technologies for IoT/M2M
Bluetooth and its Low-Energy Profile- Overview
• BLE is an alternative to the “power management” features as part of
the standard Bluetooth protocols.
• BLE is aimed at very low-power applications running off a coin cell:
• it is capable of reporting data from a sensor for up to a year from a small
button battery without recharging.
• data rate and radio range are lower,
• the low-power and long battery life make it suitable for short-range
monitoring applications in medicine.
• BLE sensor devices are typically required to operate for many years without
needing a new battery;

81
WPAN Technologies for IoT/M2M
Bluetooth and its Low-Energy Profile- Overview
• Current chip designs allow for two types of implementation—
• dual mode and single mode.
• In a single-mode implementation, the BLE protocol stack is implemented solely.
• In a dual-mode implementation, BLE functionality is integrated into an existing Classic Bluetooth
controller.
• Most new Bluetooth chipsets from leading Bluetooth silicon manufacturers
are expected to support Bluetooth and the new BLE functionality

82
WPAN Technologies for IoT/M2M
Bluetooth and its Low-Energy Profile- Overview

83
WPAN Technologies for IoT/M2M
Bluetooth and its Low-Energy Profile- Details
• Bluetooth radios use a spread spectrum, frequency-hopping, full-
duplex signal.
• While point-to-point connections are supported, the specification
allows up to seven simultaneous connections to be established and
maintained by a single radio.
• AFH (adaptive frequency hopping) available with newer versions
allows for better graceful coexistence with IEEE 802.11 WLAN
systems.
• The signal hops among 79 frequencies at 1 MHz intervals to give an
acceptable degree of interference immunity between multiple Bluetooth
devices and between a Bluetooth device and a WLAN device
84
WPAN Technologies for IoT/M2M
Bluetooth and its Low-Energy Profile- Details
• A Bluetooth device playing the role of “master” can communicate with
up to seven devices playing the role of “slave” (these groups of up to
eight devices are called piconets).
• At any given instant in time, data can be transferred between the
master and one slave; but the master switches rapidly from slave to
slave in a round-robin fashion. (Simultaneous transmission from the
master to multiple slaves is possible, but not used much in practice.)
• The Bluetooth specification also allows connecting two or more piconets
together to form a scatternet, with some devices acting as a bridge by
simultaneously playing the master role in one piconet and the slave role
in another piconet.
85