University of Computer Studies, Mandalay
CHAPTER 2
IoT and M2M
Dr. May Phyo Ko
Lecturer
Faculty of Computer Systems and Technologies
CST-M-6021: Internet of Things
Outline
2.1 M2M
2.2 Differences and Similarities between M2M and IoT
2.3 SDN and NFV for IoT
2
ㅡ
4
2.1 M2M Communication
➢ Interaction between two or more entities (machines) on a network.
✓ to exchange information and perform actions.
➢ Machines talk to each other to reduce human intervention and automate processes.
➢ Colloquially known as internet of Things (IoT).
➢ M2M devices comprise of sensors, communication links, Radio frequency
identification (RIFD) & software to interpret data.
3
ㅡ
4
M2M Applications and Examples
4
ㅡ
4
Key Features of M2M
➢ Key features of M2M technology include:
➢ Low power consumption, in an effort to improve the system's ability to effectively
service M2M applications.
➢ A Network operator that provides packet-switched service
➢ Monitoring abilities that provide functionality to detect events.
➢ Time tolerance, meaning data transfers can be delayed.
5
ㅡ
4
Key Features of M2M
➢ Time control, meaning data can only be sent or received at specific predetermined
periods.
➢ Location specific triggers that alert or wake up devices when they enter particular
areas.
➢ The ability to continually send and receive small amounts of data.
6
ㅡ
4
2.2 Differences and Similarities between M2M and IoT
7
ㅡ
4
Type of Communication Model
➢ Request & Response Model
➢ Publisher-Subscriber Model
➢ Push-Pull Model
➢ Exclusive Pair
8
ㅡ
4
2.3 SDN and NFV for IoT
Type of Communication Model
➢ Request & Response Model
➢ Publisher-Subscriber Model
➢ Push-Pull Model
➢ Exclusive Pair
9
ㅡ
4
Request & Response Model
➢ This model follows a client-server architecture.
➢ The client, when required, requests the information from the server. This request is
usually in the encoded format.
➢ This model is stateless since the data between the requests is not retained and each
request is independently handled.
10
ㅡ
4
Request & Response Model (Cond’t)
➢ The server Categories the request, and fetches the data from the database and its
resource representation. This data is converted to response and is transferred in an
encoded format to the client. The client, in turn, receives the response.
➢ On the other hand — In Request-Response communication model client sends a
request to the server and the server responds to the request. When the server
receives the request it decides how to respond, fetches the data retrieves resources,
and prepares the response, and sends it to the client.
11
ㅡ
4
Request & Response Model
12
ㅡ
4
Publisher-Subscriber Model
➢ This model comprises three entities: Publishers, Brokers, and Consumers.
➢ Publishers are the source of data. It sends the data to the topic which are managed by the
broker. They are not aware of consumers.
➢ Consumers subscribe to the topics which are managed by the broker.
➢ Hence, Brokers responsibility is to accept data from publishers and send it to the
appropriate consumers. The broker only has the information regarding the consumer to
which a particular topic belongs to which the publisher is unaware of.
13
ㅡ
4
Publisher-Subscriber Model
14
ㅡ
4
Push-Pull Model
➢ The push-pull model constitutes data publishers, data consumers, and data queues.
➢ Publishers and Consumers are not aware of each other.
➢ Publishers publish the message/data and push it into the queue. The consumers, present on
the other side, pull the data out of the queue. Thus, the queue acts as the buffer for the
message when the difference occurs in the rate of push or pull of data on the side of a
publisher and consumer.
➢ Queues help in decoupling the messaging between the producer and consumer. Queues also
act as a buffer which helps in situations where there is a mismatch between the rate at which
the producers push the data and consumers pull the data.
15
ㅡ
4
Push-Pull Model
16
ㅡ
4
Exclusive Pair
➢ Exclusive Pair is the bi-directional model, including full-duplex communication
among client and server. The connection is constant and remains open till the client
sends a request to close the connection.
➢ The Server has the record of all the connections which has been opened.
➢ This is a state-full connection model and the server is aware of all open
connections.
➢ WebSocket based communication API is fully based on this model.
17
ㅡ
4
Exclusive Pair
18
ㅡ
4
In IoT, there are 2 communication APIs-
➢ REST Based Communication APIs
➢ Web Socket Based Communication APIs
19
ㅡ
4
REST Based Communication API:
➢ REpresentational State Transfer (REST) 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 APIs follow the request-response communication model.
➢ The REST architectural constraints apply to the components, connectors, and data
elements, within a distributed hypermedia system.
20
ㅡ
4
Web Socket Based Communication APIs:
➢ Web Socket APIs allow bi-directional, full-duplex communication between clients and servers.
➢ It follows the exclusive pair communication model.
➢ This Communication API does not require a new connection to be set up for each message to be
sent between clients and servers.
➢ Once the connection is set up the messages can be sent and received continuously without any
interruption.
➢ WebSocket APIs are suitable for IoT Applications with low latency or high throughput
requirements.
21
ㅡ
4
Similarities Between REST API and WebSocket API:
➢ Both REST API and WebSocket API are used to build APIs for web applications.
➢ Both REST API and WebSocket API are standardized interfaces that enable communication
between the server and client.
➢ Both REST API and WebSocket API can be customized to suit the specific needs of a particular
application or system.
➢ Both REST API and WebSocket API can be secured using various authentication and encryption
methods.
22
ㅡ
4
Difference between Rest API and Web Socket API :
[Link] REST API WEB SOCKET API
1 It is Stateless protocol. It will not store the data. It is Stateful protocol. It will store the data.
2 It is Uni-directional. Only either server or client will It is Bi-directional. Messages can be received
communicate. or sent by both server or client.
3 It is Request-response model. It is Full duplex model.
4 HTTP request contains headers like head section, title It is suitable for real-time applications. It
section. does not have any overhead.
5 New TCP connection will be set up for each HTTP Only Single TCP connection.
request.
6 Both horizontal and vertical scaling (we can add many Only vertical scaling (we can add resources
resources and number of users both horizontally and only vertically).
vertically).
23
ㅡ
4
Difference between Rest API and Web Socket API :
[Link] REST API WEB SOCKET API
7 It depends upon the HTTP methods to retrieve the It depends upon the IP address and port
data.. number to retrieve the data
8 It is slower than web socket regarding the web socket transmits messages very fastly
transmission of messages. than REST API.
9 It does not need memory or buffers to store the data. It requires memory and buffers to store the
data.
24
ㅡ
4
AMQP
➢ AMQP is an acronym used for the Advanced Message Queuing
Protocol.
➢ It is a protocol that is used for communication between
applications.
➢ It is a lightweight, protocol which supports the applications for
transfer of data.
➢ This protocol is used for its scalability and modularity with the
technologies.
25
ㅡ
4
NB-IoT Introduction
➢ Narrowband IoT (also known as NB-IoT or LTE-M2) is a proposed LPWAN technology.
➢ NBIoT is a Low Power Wide Area Network (LPWAN) radio technology standard that has been
developed to enable a wide range of devices and services to be connected using cellular
telecommunications bands.
➢ NB-IoT technology can be deployed “in-Band, Guard-Band, Standalone.
➢ It is also suitable for the re-farming of GSM spectrum.
26
ㅡ
4
NB-IoT Introduction
➢ NB-IoT focuses specifically on indoor coverage, low cost, long battery life, and enabling a
large number of connected devices.
➢ Other 3GPP IoT technologies include eMTC (enhanced Machine-Type Communication) and
EC-GSM-IoT.
27
ㅡ
4
Features of NB IoT
➢ Low device cost/complexity: <$5 per module
➢ Extended coverage: 164 dB MCL,20 dB better compared to GPRS
➢ Long battery life: >10 years
➢ Capacity: 40 devices per household, 55k devices per cell
➢ Uplink report latency: <10 seconds
28
ㅡ
4
What is LoRa?
• The LoRa Alliance describes LoRaWAN as, "a Low Power, Wide Area (LPWA) networking
protocol designed to wirelessly connect battery operated ‘things’ to the internet in regional,
national or global networks, and targets key Internet of Things (IoT) requirements such as bi-
directional communication, end-to-end security, mobility and localization services.".
29
ㅡ
4
LoRaWAN
➢ The LoRaWAN protocol is a Low Power Wide Area Networking (LPWAN) communication
protocol that functions on LoRa.
➢ The LoRaWAN specification is open so anyone can set up and operate a LoRa network.
➢ LoRa is a wireless radio frequency technology that operates in a license-free radio frequency
spectrum.
➢ LoRa is a physical layer protocol that uses spread spectrum modulation and supports long-range
communication at the cost of a narrow bandwidth.
➢ It uses a narrow band waveform with a central frequency to send data, which makes it robust to
interference.
30
ㅡ
4
Zigbee
➢ Zigbee is a standards-based wireless technology developed to enable low-cost, low-
power wireless machine-to-machine (M2M) and internet of things (IoT) networks.
➢ Zigbee is for low-data rate, low-power applications and is an open standard.
➢ This, theoretically, enables the mixing of implementations from different manufacturers,
but in practice, Zigbee products have been extended and customized by vendors and,
thus, plagued by interoperability issues.
➢ In contrast to Wi-Fi networks used to connect endpoints to high-speed networks, Zigbee
supports much lower data rates and uses a mesh networking protocol to avoid hub
devices and create a self-healing architecture.
31
ㅡ
4
References
32
ㅡ
4