Internet-of-Things (IoT)

Khondaker A. Mamun, PhD.

Director, AIMS Lab
Professor, CSE,UIU

Acknowledgement
University of Notre Dame
Course Overview
Lecture Lab
Fundamentals of IoT, basic Basic Python programming, meet
Week 1 concepts, applications your Raspberry Pi

Smart objects, user interfaces, Sensor programming, control

Week 2 sensing, actuation loops, digital/analog I/O

Fundamentals of computer and Wi-Fi and Bluetooth networks,

Week 3 wireless networks network measurements

Sensor networks, mesh ZigBee, WPANs, WBANs, routing,

Week 4 networks, routing, WPANs network measurements

Processing, IoT cloud, analytics, IoT cloud integration, sensor

Week 5 visualization fusion, analytics, visualization

IoT ecosystem, security, privacy, Final project

Week 6 ethics, trends, case studies
Review Munich
• IBM speaker
– INTELLIGENT IoT (collaboration, conversational
interfaces, slow/focused introduction of technology)
• Samsung speaker
– In-memory analysis; “imprecise computation“
• Uppsala speaker
– Inter-network interaction; co-locality of networks
• USC speaker
– IoT marketplace; sharing of data
Review Munich
• Vint Cerf (Google)
– Reliability, safety, security, privacy, interoperability,
autonomy, …
• Panel
– Closed vs. open approach
• Data:Lab Munich
– Connected vehicles; data science; quantum
computing; natural language processing
– SDK (Software Development Kit), API (Application
Programming Interface)
Review Munich
• Prof. Barker
– SWAG
– Circuit-switched vs. packet-switched
– Packet drop (routers)
– Real-time focus
– System on a chip (SoC)
– State machines
– Virtual memory
– RPC (remote procedure call)
– IPv4 vs. IPv6
– Object-oriented vs. predictability
– 6LowPan
Computer Network Terminology
• Network: group of computers and associated devices
that are connected by communication facilities
• Wide Area Network (WAN): world-wide (Internet)
• Metropolitan Area Network (MAN): city-scale
• Local Area Network (LAN): laboratory/office-scale
(Ethernet)
– WLAN: wireless LAN (Wi-Fi)
– WPAN: wireless personal area network (Bluetooth)
– WBAN: wireless body area network
Network Topologies
Network Protocols
• Protocols are the building blocks of a network
architecture
• Formal standards and policies enabling
communication
• IEEE (Institute of Electrical and Electronics
Engineers): standardization
– Example: Project 802
• 802.3: Ethernet
• 802.11: WLAN
• 802.15: WPAN
Communication
• Who initiates communication?
• Order of communication?
• How long can I talk?
• How loud can I speak?
• Do I have to say something specific at beginning
or end?
• Do I have to add meta information?
• What do I do if I get interrupted?
• What do I do if I was not understood?
Protocols

Hi
TCP connection
request
Hi
TCP connection
Got the response
time?
2:00 Get http://www.awl.com/kurose-ross

time <file>
Client/Server Model
• Client: “active” (initiates communication)
• Server: “passive” (listens and responds)
Client/Server Model Examples
• HTTP (Hypertext Transfer Protocol)
• SMTP (Simple Mail Transfer Protocol)
• SSH (Secure Shell)
• DNS (Domain Name System)
• NFS/AFS (Network/Andrew File System)
Network Protocols (“Protocol Stack”)
Application Application
Layer Layer

Presentation Presentation
Layer Layer

Session Session
Layer Layer

Transport Transport
Layer Communication Network Layer

Network Network Network Network

Layer Layer Layer Layer

Data Link Data Link Data Link Data Link

Layer Layer Layer Layer

Physical Physical Physical Physical

Layer Layer Layer Layer
Copyright ©2000 The McGraw Hill Companies

Figure 2.6
Network Protocols (Headers/Trailers)
Application A Application B
data
Application Application
Layer data ah Layer

Presentation Presentation
Layer data ph Layer

Session Session
Layer data sh Layer

Transport Transport
Layer data th Layer

Network Network
Layer data nh Layer

Data Link Data Link

Layer dt data dh Layer

Physical Physical
Layer bits Layer
Why A Layered Design?
• An explicit structure for dealing with a
complex system
• Simplifies the design process
• Modularity of layers eases maintenance
and updating of system components
• Accommodates incremental changes
Open System Interconnection (OSI)
Physical Layer (Layer 1)
• Physical/electrical characteristics
• Cable type, length, connectors, voltage levels, signal
durations, ...
• Binary data (bits) as electrical or optical signals
• Frequencies (wireless)
Wireless Characteristics
• VLF = Very Low Frequency UHF = Ultra High Frequency
• LF = Low Frequency SHF = Super High Frequency
• MF = Medium Frequency EHF = Extra High Frequency
• HF = High Frequency UV = Ultraviolet Light
• VHF = Very High Frequency

• Frequency and wave length

–  = c/f
– wave length , speed of light c  3x108m/s, frequency f

1 Mm 10 km 100 m 1m 10 mm 100 m 1 m
300 Hz 30 kHz 3 MHz 300 MHz 30 GHz 3 THz 300 THz

VLF LF MF HF VHF UHF SHF EHF infrared visible light UV

Frequencies for Mobile Communication

• Low Frequencies:
– low data rates
– travel long distances
– follow Earth’s surface
– penetrate objects and water (submarine
communication)
• High Frequencies:
– high data rates
– short distances
– straight lines
– cannot penetrate objects (“Line of Sight” or LOS)
Other Propagation Effects
• Shadowing
• Reflection at large obstacles
• Refraction depending on the density of a medium
• Scattering at small obstacles
• Diffraction at edges

shadowing reflection refraction scattering diffraction

Real World Examples
Multipath Propagation
• Signal can take many different paths between sender
and receiver due to reflection, scattering, diffraction

Delay Spread
multipath
LOS pulses pulses

signal at sender
signal at receiver
Digital Modulation
• Amplitude Shift Keying (ASK): 1 0 1

– very simple
– low bandwidth requirements t
– very susceptible to interference
1 0 1
• Frequency Shift Keying (FSK):
– needs larger bandwidth
t

1 0 1

• Phase Shift Keying (PSK):

– more complex t
– robust against interference
Data Link Layer (Layer 2)
• Defines when/how medium will be accessed for
transmission
• Units typically called “frames”; error detection/correction;
divided into sublayers, including: MAC = Medium Access
Control (MAC address 6f:00:2b:23:1f:32)
• Cell phone example:
Example: Ethernet (802.3)
• Most popular LAN technology, uses bus
architecture
• Easy to install, inexpensive
• Data is broken into packets
Example: Ethernet
• Medium Access Control (MAC) protocol
• CSMA/CD Protocol
– Carrier Sense
– Multiple Access
– Collision Detection

AA BB CC

collision
Example: Ethernet
Don’t
Don’t
transmit
transmit

AA BB CC

Can
Can collisions
collisions still
still occur?
occur?

• “Sense” (listen) carrier (“is anyone else talking right

now?”)
• If “busy”: wait; if “idle”: transmit
• CD: Keep listening while transmitting
– If collision detected: retry at a later time
Example: Wi-Fi (802.11)
• Most popular wireless LAN architecture

Access point
Wi-Fi router
Base station
Hotspot
Example: Wi-Fi (802.11)
• CSMA/CA Protocol
– Carrier Sense
– Multiple Access
– Collision Avoidance
• Channel reservations:
– Transmitter sends request-to-send (RTS)
– Receiver sends clear-to-send (CTS)
• Advantages:
– Nodes hearing RTS and/or CTS keep quiet
– If collision, only small RTS or CTS packets are lost
Network Layer (Layer 3)
• Dominant protocol: IP = Internet Protocol
• Addressing and routing (sender & receiver IP address)
• Uses 32 bit hierarchical address space with location
information embedded in the structure

Network ID Host ID

4 bytes

• IPv4 address is usually expressed in dotted-decimal

notation, e.g.:
128.100.11.56
IPv4
IPv6
• IPv6 addresses are 128 bits long
• 16 bytes of IPv6 address are represented as a group of hexadecimal digits,
separated by colons, e.g.:
2000:fdb8:0000:0000:0001:00ab:853c:39a1
• Shorthand – leave out groups of zeros and leading zeros:
2000:fdb8:::1:ab:853c:39a1
Network Protocols (“Protocol Stack”)
Application Application
Layer Layer

Presentation Presentation
Layer Layer

Session Session
Layer Layer

Transport Transport
Layer Communication Network Layer

Network Network Network Network

Layer Layer Layer Layer

Data Link Data Link Data Link Data Link

Layer Layer Layer Layer

Physical Physical Physical Physical

Layer Layer Layer Layer
Copyright ©2000 The McGraw Hill Companies

Figure 2.6
Routers
• Form backbone of the Internet
• Use IP layer to identify source and destination of packets
• Look up routing tables that determines “next hop”

Destination Next Hop

147.39.21.X 131.19.18.121
89.44.X.X 131.19.22.119
203.21.X.X 137.18.47.48
Transport Layer (Layer 4)
• UDP (User Datagram Protocol)

UDP Header Data

• Adds more addressing: “ports”

– IP address tell you which computer
– Ports tell you which application on that computer
– Example: a web server “listens” to requests on port 80
– Web browser: http://www.google.com:80 = http://216.58.216.100:80
• “:80": optional

– Unreliable!
• Packets can get lost; packets can arrive out of order
Transport Layer
• TCP (Transmission Control Protocol)
• Reliable protocol!
• Adds ports (just like UDP), but also provides:
– In-order delivery of packets (using sequence numbers)
– Reliable delivery: using acknowledgment (ACK) packets

Packet
ACK

– Flow control & congestion control:

• Allows receiver to slow down sender
• Allows “network” to slow down sender
UDP vs TCP
• TCP:
– typical choice of most applications
– do not want to lose data, out-of-order arrival, etc.
– email, web traffic, financial transactions, etc.

• UDP:
– can be “faster”
• no flow/congestion control “slowing down” traffic
• no retransmissions
• good for “real-time” traffic
– out-of-order arrival: can also “reorder” at application level
– loss of data: can be acceptable
• missing frames in video/audio stream
Upper Layers (Layers 5-7)
• Session Layer
– Management of “sessions”
• Presentation Layer
– Data translation, formatting, encryption, compression
• Application Layer
– Interface between user applications and lower network services
Example: Web Servers

Request
HTTP HTTP
client server
Response
Example: Web Servers
HTTP HTTP
client server

Ephemeral Port 80
Port # GET 80, #

TCP TCP

#, 80 STATUS
 Example: Web Servers
HTTP Request

Header contains source TCP

and destination port
numbers Header

Header contains source

and destination IP IP
addresses; transport
Header
protocol type

Header contains
source and Frame
destination physical Ethernet Check
addresses; network Header Sequence
protocol type
BREAK