Modern Wireless Networks

Communication for
Internet of Things
ICEN 574– Spring 2019
Prof. Dola Saha
Viable Options for IoT Communication

2
LPWAN – Design Goals
Ø Long Range (few Km in urban to 10s of Km in rural)
§ Use of sub-1 GHz band (exception: WEIGHTLESS-W, INGENU)
§ Modulation Techniques:
o Narrowband (SigFox, NB-IoT) or
o Spread Spectrum (LoRa)

Ø Ultra low power operation

§ Topology (star over mesh)
§ Duty Cycling (sleep/wake)
§ Lightweight Medium Access Control (ALOHA or TDMA)
§ Offloading complexity from end device
U. Raza, P. Kulkarni and M. Sooriyabandara, "Low Power Wide Area Networks: An Overview," 3
in IEEE Communications Surveys & Tutorials, vol. 19, no. 2, pp. 855-873, Secondquarter 2017.
LPWAN – Design Goals
Ø Low Cost (per hardware cost < $5)
§ Reduction in hardware complexity
§ Minimum infrastructure
§ Using license-free or owned licensed bands
Ø Scalability
§ Diversity techniques
§ Densification
§ Adaptive channel selection and data rate
Ø Quality of Service
4
Proprietary Technologies

5
LPWAN Standards
Ø IEEE:
§ IEEE 802.15.4k: Low Energy, Critical
Infrastructure Monitoring Networks (DSSS
and FSK as two PHY layers)
§ IEEE 802.15.4g: Low-Data-Rate, Wireless,
Smart Metering Utility Networks (three
PHY layers: FSK, OFDMA, and offset
Quaternary Phase Shift Keying (QPSK)
§ IEEE 802.11: Wireless Local Area
Networks (slower OFDM)

6
LPWAN Standards
Ø 3GPP
§ LTE enhancements for Machine Type Communications (eMTC)
§ EC-GSM (Extended Coverage GSM)
§ NB-IoT (narrowband IoT)

7
Technical Specs

8
Low Power Wide-Area Networks (LPWAN)

9
LoRaWAN

10
LoRaWAN
Ø LoRaWAN defines the communication protocol and system
architecture for the network
Ø LoRa physical layer enables the long-range communication
link.

11
Network Architecture
Ø Long range star architecture
Ø Preserves battery power compared to Mesh

12
Network Architecture
Ø Nodes are NOT connected to specific gateway
Ø Data transmitted by a node is received by multiple gateways
Ø Each gateway will forward the received packet to the cloud-
based network server via some backhaul (cellular/Wi-Fi)
Ø The intelligence and complexity is pushed to the network
server
§ Manages the network
§ Filters redundant received packets Handover is not required
§ Performs security checks
§ Schedules acknowledgments through the optimal gateway
§ Performs adaptive data rate
13
Device Classes
Ø The device classes trade off network downlink
communication latency versus battery lifetime.

14
Regional Summary
Ø The ISM band for North America is from 902-
928MHz.
Ø LoRaWAN defines 64, 125kHz uplink channels
from 902.3 to 914.9MHz in 200kHz increments.
Ø There are an additional eight 500KHz uplink
channels in 1.6MHz increments from 903MHz to
914.9MHz.
Ø The eight downlink channels are 500kHz wide
starting from 923.3MHz to 927.5MHz.
Ø The maximum output power in North America is
+30dBm but for most devices +20dBm is sufficient.
Ø Under FCC there are no duty cycle limitations but
there is a 400msec max dwell time per channel.

15
Physical Message Format
Ø Uplink
§ LoRa physical header (PHDR) plus a header CRC (PHDR_CRC)
§ The integrity of the payload is protected by a CRC
§ The PHDR, PHDR_CRC and payload CRC fields are inserted by the
radio transceiver.

Ø Downlink
§ No payload integrity check is done at this level to keep messages as short
as possible with minimum impact on any duty-cycle limitations of the ISM
bands used
16
MAC Message Format
Ø All LoRa uplink and downlink
messages carry a PHY payload
(Payload) starting with a single-
octet MAC header (MHDR),
followed by a MAC payload
(MACPayload), and ending with
a 4-octet message integrity code
(MIC)
Ø Maximum MACPayload size
depends on region

17
MAC Header
Ø Mtype: Message Type
Ø RFU: Reserved for Future Use
Ø Major: Major Version

18
Frame Header
Ø Adaptive Data Rate (ADR) - when this is enabled the network
will be optimized to use the fastest data rate possible.
Ø After ADR_ACK_LIMIT uplinks (ADR_ACK_CNT >=
ADR_ACK_LIMIT) without any downlink response, it sets
the ADR acknowledgment request bit (ADRACKReq)
Ø The network is required to respond with a downlink frame

19
Class B - Beacon

20
Class C: Continuously Listening End Device
Ø The end-devices implanting the Class C option are used for
applications that have sufficient power available and thus do
not need to minimize reception time.
Ø Class C end-devices SHALL NOT implement Class B option.
Ø The end-device SHALL listen on RX2 when it is not either (a)
sending or (b) receiving on RX1, according to Class A
definition.

21
LoRaWAN Network Reference Model
Ø The End-Device is a sensor or an actuator - wirelessly
connected to a LoRaWAN network through Radio Gateways.
Ø The application layer of the End-Device is connected to a
specific Application Server in the cloud. All application layer
payloads of this End-Device are routed to its corresponding
Application Server.

22
LoRaWAN Network Reference Model

23
Radio Gateway
Ø The Radio Gateway forwards all received LoRaWAN radio
packets to the Network Server that is connected through an IP
back-bone.
Ø The Radio Gateway operates entirely at the physical layer. Its
role is simply to decode uplink radio packets from the air and
forward them unprocessed to the Network Server.
Ø For downlinks, it executes transmission requests coming from
the Network Server without any interpretation of the payload.

24
Network Server
Ø The Network Server (NS) terminates the LoRaWAN
MAC layer for the End-Devices connected to the
network. It is the center of the star topology.
Ø Generic features of NS are:
§ End-Device address check, Frame authentication and frame counter
checks, Acknowledgements, Data rate adaptation, Responding to all MAC
layer requests coming from the End-Device, Forwarding uplink application
payloads to the appropriate Application Servers, Queuing of downlink
payloads coming from any Application Server to any End- Device
connected to the network, Forwarding Join-request and Join-accept
messages between the End-Devices and the Join Servers.
25
Network Servers
Ø Serving NS (sNS) controls the MAC layer of the End-Device
Ø Home NS (hNS) is where Device Profile, Service Profile, Routing Profile
and DevEUI of the End-Device are stored.
Ø Forwarding NS (fNS) is the NS managing the Radio Gateways. When sNS
and fNS are separated, they are in a roaming agreement.
Ø The Join Server (JS) manages the Over-the-Air (OTA) End-Device
activation process. There may be several JSs connected to a NS, and a JS
may connect to several NSs.
Ø The JS may be connected to several Application Servers (AS), and an AS
maybe connected to several JSs.

26
LoRa PHY
Ø LoRa is a proprietary spread spectrum modulation scheme that
is derivative of Chirp Spread Spectrum modulation (CSS)
Ø It was developed by Cycleo of Grenoble, France, and acquired
by Semtech in 2012
§ Constant bandwidth
§ Implements a variable data rate
§ utilizes orthogonal spreading factors
§ system designer can trade off between data rate for range or power
Ø LoRa is a PHY layer implementation and is agnostic with to
higher-layer implementations.
§ LoRa can coexist and interoperate with existing network architectures.
27
Spread Spectrum Principles

Ø Each bit in original signal is represented by multiple bits in the transmitted signal
Ø Spreading code spreads signal across a wider frequency band
§ Spread is in direct proportion to number of bits used
Ø One technique combines digital information stream with the spreading code bit
stream using exclusive-OR
28
 DSSS with BPSK
DS spreader
Spread spectrum
Binary data sd(t) signal
Modulator
(BPSK) +1 –1 +1 –1
d(t) s(t) (a) d(t)
data

c(t)
T

Pseudonoise
bit source (b) sd (t)

(a) Transmitter

DS despreader
Spread spectrum +1 +1 –1 –1 +1 –1 +1 +1 +1 –1 +1
(c) c(t)
signal sd(t) Binary data spreading code
Demodulator
(BPSK)
s(t) Tc

c(t)
(d) s(t)

Pseudonoise
bit source

(b) Receiver

29
Characteristics of Chirp pulses
Ø A chirp pulse is a frequency modulated pulse.
§ Its duration is T; within this time the frequency is changing in a monotonic
manner from a lower value to a higher one (“Up-Chirp”) or reverse
(“Down-Chirp”).
§ The difference between these two frequencies is a good approximation for
the bandwidth B of the chirp pulse.
S(f)

f
B

Spectrum of the chirp pulse with Up-Chirp in the time domain

bandwidth B and a roll-off factor of 0.25 (roll-off factor 0.25)
30
CSS Chirps

LoRa Frequency:
https://revspace.nl/DecodingLora

31
Steps for Modulation
Ø Gray Indexing - Adds error tolerance
Ø Data Whitening - Induces randomness
Ø Interleaving - Scrambles bits within frame
Ø Forward Error Correction - Adds parity bits

1) Low power long range transmitter

European Patent EP2763321A1
https://patents.google.com/patent/EP2763321A1/en
2) Matt Knight, “Decoding LoRa, a Wireless Network for the Internet of Things”, RSA
Conference 2017
32
LoRa Localization
Ø Direct Path Energy
Ø TDoA & Phase
Ø Multiple Gateways

33
LoRa Localization

34
SigFox

35
SigFox
Ø Ultra narrow band
Ø Random Access
Ø Cooperative Reception
Ø Small Messages (12-byte payload Uplink, 8 byte
payload downlink)
Ø Bi-directional
Ø Cloud-based Core Network

36
SigFox in comparison to other technologies

37
Ultra narrowband operation in EU

38
Modulation and Encoding

39
Long Range

40
Random Access
Ø Unsynchronized transmission
Ø Random frequency
Ø SIGFOX Base stations permanently listen to the spectrum
Ø 3 replicas of the same frame @ 3 frequencies

41
Cooperative Reception
Ø Message received by 3 Base Stations in average
Ø Spatial diversity decreases collision probability
Ø MIMO like Approach

42
Cloud Based Core Network

43
Cellular IoT

44
3GPP’s Effort
Ø NB-IoT designed to exist in one of three ways:
§ In independently licensed bands.
§ In unused 200 kHz bands that have previously been used for GSM or
CDMA.
§ On LTE base stations that can allocate a resource block to NB-IoT
operations or in their guard bands (where regulations allow it)
Ø LTE-M
§ The advantage of LTE-M over NB-IoT is its higher data rate, mobility, and
voice over the network
§ It requires more bandwidth, is more expensive, and cannot be put into
guard band frequency band for now
45
Bluetooth

46
IEEE 802.15
Ø Wireless Personal Area Networks
§ Short-range communication
§ Low-cost, low-energy to provide long battery life
Ø Several standards have been provided
Ø We focus on 802.15 technologies
§ Other viable WPAN alternatives exist

47
Bluetooth
Ø Universal short-range wireless capability
Ø Uses 2.4-GHz band
Ø Available globally for unlicensed users
Ø Devices within 10 m can share up to 2.1 Mbps or 24 Mbps of
capacity
Ø Supports open-ended list of applications
§ Data, audio, graphics, video
Ø Started as IEEE 802.15.1
§ New standards come from the Bluetooth Special Interest Group (Bluetooth SIG)
o Industry consortium
§ Bluetooth 2.0, 2.1, 3.0, and 4.0
48
Bluetooth Application Areas
Ø Data and voice access points
§ Real-time voice and data transmissions
Ø Cable replacement
§ Eliminates need for numerous cable attachments for connection
Ø Ad hoc networking
§ Device with Bluetooth radio can establish connection with another when in
range

49
Top uses of Bluetooth
Ø Mobile handsets
Ø Voice handsets
Ø Stereo headsets and speakers
Ø PCs and tablets
Ø Human interface devices, such as mice and keyboards
Ø Wireless controllers for video game consoles
Ø Cars
Ø Machine-to-machine applications: credit-card readers,
industrial automation, etc.
50
Bluetooth Standards Documents
Ø Core specifications
§ Details of various layers of Bluetooth protocol architecture
Ø Profile specifications
§ Use of Bluetooth technology to support various applications
Ø Initial Standard
§ 2.1 Basic/Enhanced Data Rate (BR/EDR)
Ø Later standards
§ 3.0 Alternative MAC/PHY (AMP)
§ 4.0 Bluetooth Smart (Bluetooth Low Energy)
51
Bluetooth Protocol Stack
= Core protocols vCard/vCal WAE AT
TCS BIN SDP
= Cable replacement protocol OBEX WAP commands
= Telephony control protocols
UDP/TCP
= Adopted protocols
IP
PPP

Audio RFCOMM Control

Logical Link Control and Adaptation Protocol (L2CAP)

Host-controller interface
Link Manager Protocol (LMP)

Baseband

Bluetooth Radio

AT = Attention sequence (modem prefix) TCS BIN = Telephony control specification - binary
IP = Internet Protocol UDP = User Datagram Protocol
OBEX = Object exchange protocol vCal = Virtual calendar
PPP = Point-to-Point Protocol vCard = Virtual card
RFCOMM = Radio frequency communications WAE = Wireless application environment
SDP = Service discovery protocol WAP = Wireless application protocol
TCP = Transmission control protocol
52
Protocol Architecture
Ø Bluetooth is a layered protocol architecture
§ Core protocols
§ Cable replacement and telephony control protocols
§ Adopted protocols
Ø Core protocols
§ Radio
§ Baseband
§ Link manager protocol (LMP)
§ Logical link control and adaptation protocol (L2CAP)
§ Service discovery protocol (SDP)

53
Protocol Architecture
Ø Cable replacement protocol
§ RFCOMM
Ø Telephony control protocol
§ Telephony control specification – binary (TCS BIN)
Ø Adopted protocols
§ PPP
§ TCP/UDP/IP
§ OBEX
§ WAE/WAP

54
Profiles
Ø Over 40 different profiles are defined in Bluetooth
documents
§ Only subsets of Bluetooth protocols are required
§ Reduces costs of specialized devices
Ø All Bluetooth nodes support the Generic Access Profile
Ø Profiles may depend on other profiles
§ Example: File Transfer Profile
o Transfer of directories, files, documents, images, and streaming media
formats
o Depends on the Generic Object File Exchange, Serial Port, and Generic
Access Profiles.
o Interfaces with L2CAP and RFCOMM protocols

55
Piconets and Scatternets
Ø Piconet
§ Basic unit of Bluetooth networking
§ Master and one to seven slave devices
§ Master determines channel and phase
Ø Scatternet
§ Device in one piconet may exist as master or slave in another piconet
§ Allows many devices to share same area
§ Makes efficient use of bandwidth

56
Master/Slave Relationships
M

M/S S S S

S S S S

57
Wireless Network Configurations

(a) Cellular system (squares represent (b) Conventional ad hoc systems

stationary base stations)

58
(c) Scatternets
Piconet
IDa
IDd IDd

IDa D IDa P

A M

IDe IDe
E sb
IDa
IDb B IDb S IDa
IDc C IDc S

Ø All devices in a piconet hop together

§ To form a piconet: master gives slaves its clock and device ID
o Hopping pattern determined by device ID (48-bit)
o Phase in hopping pattern determined by Clock

Ø Non-piconet devices are in standby

Ø Piconet Addressing
§ Active Member Address (AMA, 3-bits)
§ Parked Member Address (PMA, 8-bits)
59
Radio Specification
Ø Classes of transmitters
§ Class 1: Outputs 100 mW for maximum range
o Power control mandatory
o Provides greatest distance
§ Class 2: Outputs 2.4 mW at maximum
o Power control optional
§ Class 3: Nominal output is 1 mW
o Lowest power

60
Frequency Hopping in Bluetooth
Ø Provides resistance to interference and multipath
effects
Ø Provides a form of multiple access among co-located
devices in different piconets

61
Frequency Hopping
Ø Total bandwidth divided into 1MHz physical channels
Ø FH occurs by jumping from one channel to another in pseudorandom
sequence
Ø Hopping sequence shared with all devices on piconet
Ø Piconet access:
§ Bluetooth devices use time division duplex (TDD)
§ Access technique is TDMA
§ FH-TDD-TDMA

62
Frequency Hopping Example
Frequency

f8 2
Energy
f7 4
5 8 3 7 1 4 6 2 f6 7
f5 1
f4 6
f3 3
f2 8
f1 5

f1 f2 f3 f4 f5 f6 f7 f8 Frequency Time
(a) Channel assignment (b) Channel use

63
Modulation
Ø Gaussian frequency shift keying (GFSK)
§ A type of FSK modulation which uses a Gaussian filter to shape the pulses
before they are modulated.
§ This reduces the spectral bandwidth and out-of-band spectrum, to meet
adjacent-channel power rejection requirements.

64
 Frequency-Hop Time-Division Duplex
f(k) f(k + 1) f(k + 2)

Master
t

Slave
t
625 µs

• The channel is divided into time slots, each 625 µs in length.

• The time slots are numbered according to the Bluetooth clock of the piconet master.
• Hop Rate = 1600 hops per sec
• FH occurs on a pseudorandom sequence
• Hopping sequence is shared among all devices in a piconet
• Different piconets will have different masters and will have different sequence
65
TDD
Ø A TDD scheme is used where master and slave
alternatively transmit.
Ø The master shall start its transmission in even-
numbered time slots only, and the slave shall start its
transmission in odd-numbered time slots only.
Ø The packet start shall be aligned with the slot start.
Ø Packets transmitted by the master or the slave may
extend over up to five time slots.
66
Examples of Multislot Packets
625 µs
f(k) f(k + 1) f (k + 2) f (k + 3) f (k + 4) f(k + 5) f (k + 6)

f (k) f (k + 3) f (k + 4) f (k + 5) f (k + 6)

f(k) f (k + 5) f (k + 6)

67
Physical Links between Master and Slave
Ø Synchronous connection oriented (SCO)
§ Allocates fixed bandwidth between point-to-point connection of master and slave
§ Master maintains link using reserved slots
§ Master can support three simultaneous links
Ø Asynchronous connectionless (ACL)
§ Point-to-multipoint link between master and all slaves
§ Only single ACL link can exist
Ø Extended Synchronous connection oriented (eSCO)
§ Reserves slots just like SCO
§ But these can be asymmetric
§ Retransmissions are supported
68
 Bluetooth Baseband Formats
bits 72 54 0 to 2745
Access Code Header Payload
The preamble is a
(a) Packet format
fixed zero-one pattern
of four symbols used
4 64 4
Pre- Trail-
to facilitate dc
SYNC Word
amble er
compensation. The
(b) Access code format sequence is either
3 4 1 1 1 8 1010 or 0101,
AM_Addr Type Flow ARQN SEQN Header error control (HEC)
depending whether
the LSB of the
(c) Header format (prior to coding)
following sync word
2 1 5 is 1 or 0, respectively.
L_CH Flow Length Single-slot packets

2 1 9 4
Multislot
L_CH Flow Length Undefined
packets
69
(d) Data payload header format
Bluetooth Packet Fields
Ø Access code – used for timing synchronization,
offset compensation, paging, and inquiry
Ø Header – used to identify packet type and carry
protocol control information
Ø Payload – contains user voice or data and payload
header, if present

70
Types of Access Codes
Ø Channel access code (CAC) – identifies a piconet
Ø Device access code (DAC) – used for paging and
subsequent responses
Ø Inquiry access code (IAC) – used for inquiry
purposes

71
Packet Header Fields
Ø AM_ADDR – contains “active mode” address of one of the slaves
Ø Type – identifies type of packet
Ø Flow – 1-bit flow control
Ø ARQN – 1-bit acknowledgment
Ø SEQN – 1-bit sequential numbering schemes
Ø Header error control (HEC) – 8-bit error detection code

72
Payload Format
Ø Payload header
§ L_CH field – identifies logical channel
§ Flow field – used to control flow at L2CAP level
§ Length field – number of bytes of data
Ø Payload body – contains user data
Ø CRC – 16-bit CRC code

73
Error Correction Schemes
Ø 1/3 rate FEC (forward error correction)
§ Used on 18-bit packet header, voice field in HV1 packet
Ø 2/3 rate FEC
§ Used in DM packets, data fields of DV packet, FHS packet and HV2
packet
Ø ARQ
§ Used with DM and DH packets

74
 Bit Processing

Header HEC Generation

Payload Data Whitening Polynomial

CRC Generation

75
ARQ Scheme Elements
Ø Error detection – destination detects errors, discards packets
Ø Positive acknowledgment – destination returns positive
acknowledgment
Ø Retransmission after timeout – source retransmits if packet
unacknowledged
Ø Negative acknowledgment and retransmission – destination returns
negative acknowledgement for packets with errors, source retransmits

76
An Example of Retransmission Operation
f(k + 1) f(k + 2) f(k + 3) f(k + 4) f(k + 5) f(k + 6) f(k + 7) f(k + 8) f(k + 9) f(k + 10) f(k + 11) f(k + 12)

A B B X C
Master t

NAK
ACK

ACK
Failure

NAK
ACK

ACK

ACK
Failure

F G H
Slave 1 t

ACK
Z Z
Slave 2 t

625 µs
77
Logical Channels
Ø Link control (LC)
Ø Link manager (LM)
Ø User asynchronous (UA)
Ø User isochronous (UI)
Ø Use synchronous (US)

78
Link manager
Ø Manages various aspects of the radio link between a
master and a slave
Ø Involves the exchange LMP PDUs (protocol data units)
Ø Procedures defined for LMP are grouped into 24
functional areas, which include
§ Authentication
§ Pairing
§ Encryption
§ Clock offset request
§ Switch master/slave
§ Name request
§ Hold or park or sniff mode
79
Logical link control & adaptation protocol-L2CAP
Ø Provides a link-layer protocol between entities with a number of
services
Ø Relies on lower layer for flow and error control
Ø Makes use of ACL links, does not support SCO links
Ø Provides two alternative services to upper-layer protocols
§ Connection service
§ Connection-mode service

80
L2CAP Logical Channels
Ø Connectionless
§ Supports connectionless service
§ Each channel is unidirectional
§ Used from master to multiple slaves
Ø Connection-oriented
§ Supports connection-oriented service
§ Each channel is bidirectional
Ø Signaling
§ Provides for exchange of signaling messages between L2CAP entities

81
Flow Specification Parameters
Ø Service type
Ø Token rate (bytes/second)
Ø Token bucket size (bytes)
Ø Peak bandwidth (bytes/second)
Ø Latency (microseconds)
Ø Delay variation (microseconds)

82
Token Bucket Scheme
Token rate =
R bytes per second

Bucket size =
B bytes
Current bucket
occupancy

Arriving Departing
data data

83
Bluetooth high speed
Ø Bluetooth 3.0+HS
Ø Up to 24 Mbps
Ø New controller compliant with 2007 version of IEEE
802.11
Ø Known as Alternative MAC/PHY (AMP)
§ Optional capability
Ø Bluetooth radio still used for device discovery,
association, setup, etc.
Ø Allows more power efficient Bluetooth modes to be used,
except when higher data rates are needed
84
Bluetooth smart
Ø Bluetooth 4.0
Ø Also known as Bluetooth Low Energy (BLE)
Ø An intelligent, power-friendly version of Bluetooth
Ø Can run long periods of time on a single battery
§ Or scavenge for energy
Ø Also communicates with other Bluetooth-enabled devices
§ Legacy Bluetooth devices or Bluetooth-enabled smartphones
§ Great feature
Ø Possible successful technology for the Internet of Things
§ For example, health monitoring devices can easily integrate with existing
smartphones
85
Bluetooth smart
Ø Same 2.4 GHz ISM bands as Bluetooth BR/EDR
§ But uses 40 channels spaced 2 MHz apart instead of 79 channels spaced 1
MHz apart
Ø Devices can implement a transmitter, a receiver, or both
Ø Implementation
§ Single-mode Bluetooth Smart functionality
o Reduced cost chips that can be integrated into compact devices.
§ Dual-mode functionality to also have the Bluetooth BR/EDR capability
Ø 10 mW output power
Ø 150 m range in an open field
86
IEEE 802.15
Ø After 802.15.1, work went two directions
Ø 802.15.3
§ Higher data rates than 802.15.1
§ But still low cost, low power compared to 802.11
Ø 802.15.4
§ Very low cost, very low power compared to 802.15.1
Ø Figure 12.9 shows different options
Ø Figure 12.10 shows relative distances and rates
87
IEEE 802.15 Protocol Architecture

Logical link control (LLC)

802.15.1
802.15.3 802.15.4, 802.15.4e
Bluetooth
MAC MAC
MAC

802.15.1 802.15.3c 802.15.3d 802.15.4, 802.15.4a

2.4 GHz 60 GHz 60 GHz 868/915 MHz, 2.4 GHz
1, 2, or 3 1 to 6 100 DSSS: 20, 40, 100, 250 kbps
Mbps Gbps Gbps UWB: 110 kbps to 27 Mbps
24 Mbps HS CSS: 250 kbps, 1 Mbps

88
Wireless Local Networks
100 Gbps 802.15.3d

WPAN

1 to 7 Gbps 802.11ac (Wi-Fi)

802.15.3c
802.11ad (Wi-Fi)

WLAN
Data rate

54 to 600 802.11n (Wi-Fi)

Mbps

802.11g (Wi-Fi)

24 Mbps Bluetooth+HS

802.15.1
1 to 3 Mbps
(Bluetooth) WPAN

20 to 250 802.15.4
kbps (ZigBee)

0 10 n x 100
Indoor range (m) 89
ZigBee Architecture
Application (APL) Layer

Application Framework

Application Application ZigBee Device Object

ZDO Public
•••

Interfaces
Object 240 Object 1 (ZDO)

Endpoint 240 Endpoint 1 Endpoint 0

APSDE-SAP APSDE-SAP APSDE-SAP

ZDO Management Plane

Application Support Sublayer (APS)

APSME-SAP
APS Security APS Message Reflector
Security Management Broker Management
Service NLDE-SAP NLME-SAP
Provider Network (NWK) Layer

NLME-SAP
IEEE 802.15.4
Security Message Routing Network
defined Management Broker Management Management
ZigBee™ Alliance
MLDE-SAP
defined MLME-SAP
Medium Access Control (MAC) Layer
End manufacturer
defined
PLME-SAP
Layer PD-SAP
Physical (PHY) Layer
function
2.4 GHz Radio 868/915 MHz Radio
Layer
interface
90
IEEE 802.15.3
Ø High data rate WPANs
§ Digital cameras, speakers, video, music
Ø Piconet coordinator (PNC)
§ Sends beacons to devices to connect to the network
§ Uses superframes like 802.11
§ QoS based on TDMA
§ Controls time resources but does not exchange data
Ø 802.15.3c
§ Latest standard
§ Uses 60 GHz band, with same benefits as 802.11ad
§ Single-carrier and OFDM PHY modes
91
IEEE 802.15.4
Ø Low data rate, low complexity
§ Competitor to Bluetooth Smart
Ø PHY options in 802.15.4 and 802.15.4a
§ 868/915 MHz for 20, 40, 100, and 250 kbps
§ 2.4 GHz for 250 kbps
§ Ultrawideband (UWB)
o Uses very short pulses with wide bandwidth
ü Low energy density for low interference with others
851 kbps and optionally 110 kbps, 6.81 Mbps, or 27.234 Mbps
o
§ 2.4 GHz chirp spread spectrum for 1 Mbps and optionally 250 kbps
o Sinusoidal signals that change frequency with time

92
IEEE 802.15.4
Ø Many other creative and practical activities
Ø IEEE 802.15.4f – Active Radio Frequency Identification Tags (RFIDs)
§ Attached to an asset or person with a unique identification
§ An Active RFID tag must employ some source of power
Ø IEEE 802.15.4g – Smart Utility Networks (SUN)
§ Facilitates very large scale process control applications such as the utility smart-grid network
Ø IEEE 802.15.4j – Medical Body Area Networks
Ø EEE 802.15.4k – Low Energy Critical Infrastructure Networks (LECIM)
§ To facilitate point to multi-thousands of points communications for critical infrastructure monitoring
devices with multi-year battery life.
Ø IEEE 802.15.4p – Positive Train Control
§ Sensor, control and information transfer applications for rail transit

93
Other IEEE 802.15 standards
Ø 802.15.2 – Coexistence between 802.11 and 802.15
Ø 802.15.5 – Mesh networks
§ Multihop networking
Ø 802.15.6 – Body area networks
Ø 802.15.7 – Visible light communication

94
ZigBee
Ø Extends IEEE 802.15.4 standards
Ø Low data rate, long battery life, secure networking
Ø Data rates 20 to 250 kbps
Ø Operates in ISM bands
§ 868 MHz (Europe), 915 MHz (USA and Australia), 2.4 GHz (worldwide)
Ø Quick wake from sleep
§ 30 ms or less compared to Bluetooth which can be up to 3 sec.
§ ZigBee nodes can sleep most of the time

95
ZigBee
Ø ZigBee complements the IEEE 802.15.4 standard by
adding four main components
§ Network layer provides routing
§ Application support sublayer supports specialized services.
§ ZigBee device objects (ZDOs) are the most significant improvement
o Keep device roles, manage requests to join the network, discover devices,
and manage security.
§ Manufacturer-defined application objects allow customization.

96
ZigBee Architecture
Application (APL) Layer

Application Framework

Application Application ZigBee Device Object

ZDO Public
•••

Interfaces
Object 240 Object 1 (ZDO)

Endpoint 240 Endpoint 1 Endpoint 0

APSDE-SAP APSDE-SAP APSDE-SAP

ZDO Management Plane

Application Support Sublayer (APS)

APSME-SAP
APS Security APS Message Reflector
Security Management Broker Management
Service NLDE-SAP NLME-SAP
Provider Network (NWK) Layer

NLME-SAP
IEEE 802.15.4
Security Message Routing Network
defined Management Broker Management Management
ZigBee™ Alliance
MLDE-SAP
defined MLME-SAP
Medium Access Control (MAC) Layer
End manufacturer
defined
PLME-SAP
Layer PD-SAP
Physical (PHY) Layer
function
2.4 GHz Radio 868/915 MHz Radio
Layer
interface
97
ZigBee
Ø Star, tree, or general mesh network structures
Ø ZigBee Coordinator
§ Creates, controls, and maintains the network
§ Only one coordinator in the network
§ Maintains network information, such as security keys
Ø ZigBee Router
§ Can pass data to other ZigBee devices
Ø ZigBee End Device
§ Only enough functionality to talk to a router or coordinator
§ Cannot relay information
§ Sleeps most of the time
§ Less expensive to manufacture
98
ZigBee Network

a) Star b) Tree

ZigBee Coordinator

ZigBee Router

ZigBee End Device c) Mesh

99
ZigBee alliance
Ø Industry consortium
Ø Maintains and publishes the ZigBee standard
§ ZigBee specifications in 2004
§ ZigBee PRO completed in 2007
o Enhanced ZigBee
o Profile 1 – home and light commercial use
o Profile 2 – more features such as multicasting and higher security

Ø Application profiles
§ Allow vendors to create interoperable products if they implement the same
profile
100
ZigBee application profiles
Ø ZigBee Building Automation (Efficient commercial spaces)
Ø ZigBee Health Care (Health and fitness monitoring)
Ø ZigBee Home Automation (Smart homes)
Ø ZigBee Input Device (Easy-to-use touchpads, mice, keyboards, wands)
Ø ZigBee Light Link (LED lighting control)
Ø ZigBee Network Devices (Assist and expand ZigBee networks)
Ø ZigBee Retail Services (Smarter shopping)
Ø ZigBee Remote Control (Advanced remote controls)
Ø ZigBee Smart Energy 1.1 (Home energy savings)
Ø ZigBee Smart Energy Profile 2 (IP-based home energy management)
Ø ZigBee Telecom Services (Value-added services)

101