This document provides an overview of the course "18BME18 INTERNET OF THINGS FOR BIOMEDICAL ENGINEERS". The course aims to discuss IoT concepts, interpret wireless sensor network protocols, illustrate IoT applications in healthcare using tools and embedded systems. The document outlines the various units that will be covered, including IoT and M2M communication models, functional blocks, and protocols. It also compares IoT with M2M and describes software-defined networking.

1. 18BME18 INTERNET OF THINGS
FOR BIOMEDICAL ENGINEERS
Dr.S.K.Manikandan,
Prof./BME

2. 18BME18 INTERNET OF THINGS FOR BIOMEDICAL ENGINEERS
• Course Outcomes: Upon completion of the course, students
will be able to:
– Discuss the concepts of Internet of Things.
– Interpret basic protocols in wireless sensor network.
– Illustrate the need and challenges of IoT.
– Relate IoT applications in Industry domain and analyze their
performance.
– Compute the health care applications through IoT tools and
Embedded systems.

3. UNIT I
UNIT 1 IoT & M2M
• Defining IoT - Characteristics of IoT - Physical
design of IoT - Logical design of IoT - Functional
blocks of IoT - Communication models & APIs -
Machine to Machine - Difference between IoT and
M2M - Software define network.

4. Defining IoT
• It is the way to interconnection with the help of the internet devices that can be
embedded to implement the functionality in everyday objects by enabling them to
send and receive data.
• Applications:
• Agriculture, assets tracking, energy sector, safety and security sector, defence,
embedded applications, education, waste management, healthcare product,
telemedicine, smart city applications, etc.

5. Characteristics of IoT
• Characteristics of the Internet of Things
– Connectivity
– Intelligence and Identity
– Scalability
– Dynamic and Self-Adapting (Complexity)
– Architecture
– Safety
– Self Configuring

6. Connectivity
• Connectivity is an important requirement of the IoT infrastructure.
• Things of IoT should be connected to the IoT infrastructure.
• Anyone, Anywhere, Anytime can connect, this should be guaranteed at all times.
• For example, connection between people through internet devices like mobile
phones ,and other gadgets, also connection between Internet devices such as
routers, gateways, sensors, etc.

7. Intelligence and Identity
• The extraction of knowledge from the generated data is very important.
• For example, a sensor generates data, but that data will only be useful if it is
interpreted properly.
• Each IoT device has a unique identity.
• This identification is helpful in tracking the equipment and at times for querying its
status.

8. Dynamic and Self-Adapting (Complexity)
• IoT devices should dynamically adapt themselves to the changing contexts and
scenarios.
• CCTV camera meant for the surveillance.
• It should be adaptable to work in different conditions and different light situations
(morning, afternoon, night).

9. Scalability
• The number of elements connected to the IoT zone is increasing day by day.
• Capable of handling the massive expansion.
• The data generated as an outcome is enormous, and it should be handled
appropriately.

10. Architecture
• IoT architecture cannot be homogeneous in nature.
• It should be hybrid, supporting different manufacturers ‘ products to function in
the IoT network.
• IoT is not owned by anyone engineering branch.
• IoT is a reality when multiple domains come together.

11. Safety
• There is a danger of the sensitive personal details of the users getting
compromised when all his/her devices are connected to the internet.
• This can cause a loss to the user.
• Data security is the major challenge.
• The equipment involved is huge.
• IoT networks may also be at the risk. Therefore, equipment safety is also critical.

12. Self Configuring
• This is one of the most important characteristics of IoT.
• IoT devices are able to upgrade their software in accordance with requirements
with a minimum of user participation.
• Additionally, they can set up the network, allowing for the addition of new devices
to an already-existing network.

13. Physical design of IoT

14. IoT Protocols

15. • IoT protcols help to establish Communication between IoT Device (Node Device)
and Cloud based Server over the Internet.
• It help to sent commands to IoT Device and received data from an IoT device over
the Internet.
• Link Layer
• Link layer protocols determine how data is physically sent over the network’s
physical layer or medium (Coxial cable or other or radio wave).
• 802.3 – Ethernet : Ethernet is a set of technologies and protocols that are used
primarily in LANs.
• 802.11 – WiFi : IEEE 802.11 is part of the IEEE 802 set of LAN protocols, and
specifies the set of media access control (MAC) and physical layer (PHY) protocols
for implementing wireless local area network (WLAN) Wi-Fi computer
communication in various frequencies, including but not limited to 2.4 GHz, 5 GHz,
and 60 GHz frequency bands.
• 802.16 – Wi-Max : The standard for WiMAX technology is a standard for Wireless
Metropolitan Area Networks (WMANs) that has been developed by working group
number 16 of IEEE 802, specializing in point-to-multipoint broadband wireless
access.

16. • 802.15.4 -LR-WPAN : A collection of standards for Low-rate wireless personal area
network.
• 2G/3G/4G- Mobile Communication : These are different types of
telecommunication generations. IoT devices are based on these standards can
communicate over the celluer networks.
• Network Layer
• Responsible for sending of IP datagrams from the source network to the
destination network. Network layer performs the host addressing and packet
routing.
• IPv4 defines an IP address as a 32-bit number.
• IP (IPv6), using 128 bits for the IP address.
• IPv6 was developed by the Internet Engineering Task Force (IETF) to deal with the
long-anticipated problem of IPv4 address fatigue.
• 6LoWPAN : It is an acronym of IPv6 over Low-Power Wireless Personal Area
Networks. This protocol allows for the smallest devices with limited processing
ability to transmit information wirelessly using an internet protocol.

17. • Transport Layer
• This layer provides functions such as error control, segmentation, flow control and
congestion control. So this layer protocols provide end-to-end message transfer
capability independent of the underlying network.
• TCP : TCP (Transmission Control Protocol) is a standard that defines how to
establish and maintain a network conversation through which application
programs can exchange data.
• UDP : User Datagram Protocol (UDP) is a Transport Layer protocol. UDP is a part of
Internet Protocol suite, referred as UDP/IP suite.
• Unlike TCP, it is unreliable and connectionless protocol. So, there is no need to
establish connection prior to data transfer.

18. • Application Layer
• Application layer protocols define how the applications interface with the lower
layer protocols to send over the network.
• HTTP : Hypertext Transfer Protocol (HTTP) is an application-layer protocol for
transmitting hypermedia documents, such as HTML.
• CoAP : CoAP-Constrained Application Protocol is a specialized Internet Application
Protocol for constrained devices.
• WebSocket : The WebSocket Protocol enables two-way communication between a
client running untrusted code in a controlled environment to a remote host that
has opted-in to communications from that code.
• MQTT : MQTT is a machine-to-machine (M2M)/”Internet of Things” connectivity
protocol. It was designed as an extremely lightweight publish/subscribe messaging
transport and useful for connections with remote locations where a small code
footprint is required and/or network bandwidth is at a premium.
• XMPP : Extensible Messaging and Presence Protocol (XMPP) is a communication
protocol for message-oriented middleware based on XML (Extensible Markup
Language).

19. • DDS : The Data Distribution Service (DDS™) is a middleware protocol and API
standard .
• AMQP : The AMQP IoT protocols consist of a hard and fast of components that
route and save messages within a broker carrier, with a set of policies for wiring
the components together for data-centric connectivity from the Object
Management Group

20. Logical design of IoT
• A logical design for an IoT system is the actual design of how its components
(computers, sensors, and actuators) should be arranged to complete a particular
function.
• It doesn’t go into the depth of describing how each component will be built with
low-level programming specifics.

21. Functional blocks of IoT
• IoT systems include several functional blocks such as Devices, communication,
security, services, and application.
• The functional blocks provide sensing, identification, actuation, management, and
communication capability.
• These functional blocks consist of devices that handle the communication
between the server and the host, enable monitoring control functions, manage
the data transfer, secure the IoT system using authentication and different
functions, and provide an interface for controlling and monitoring various terms.

22. Functional blocks of IoT

24. Communication Models and APIs
• IoTs enable people and things to be connected anytime, in any space, with
anything and anyone, through any network and service.
• Request & Response Model
• Publish-Subscribe Model(Pub-Sub)
• Push-Pull Model
• Exclusive Pair Model

26. • The communication takes place between a client and a server.
• Whenever required, the client will request information from the server. This
request is usually in the encoded format.
• So in this model, basically a client sends requests to the server and the server
responds to the requests. That is why it is called as Request-Response model.
• After receiving the request from the client, the server decides how to respond,
fetches the data from the database and its resource representation, prepares a
response and ultimately sends the response to the client.
• Request-Response model is a stateless model. Each request-response pair is
independent of others.
• Example is HTTP. HTTP operates as a query-response protocol between a client and
a server.
• A web browser can be the client, and an application on a computer that supports a
website can be the server. The client(browser) submits an HTTP request to the
server and the server will return a response back to the client.

28. • Publisher, Broker and Consumer Let us see the roles of each of these 3 entities.
• Publishers, send the data to the topics that are managed by the broker. They are
the source of data.
• The Man in the Middle, the Broker, has the responsibility to accept the data sent
by the publisher and deliver that data to the consumers.
• What is the task of the Consumers? Consumers will subscribe to the broker-
managed topics.
• Publishers aren't aware of who the consumers are.
• Once the data is published on a topic, the broker sends this message to all
consumers who have subscribed to the specific topic. It works a bit like YouTube.
When you subscribe to a channel and tap the Bell icon, you'll get notifications if
the YouTube channel posts a video.

30. • Here too, we have 3 entities:- Publisher, Queues and Consumers.
• Push-Pull is a communication model where data producers push data into queues
and consumers pull data out of queues.
• What are Queues? They are used to separate out single producer-consumer
communication.
• At times, there might be some mismatch in the push-pull rates.
• Queues act as a buffer which helps in situations when there is a mismatch
between the rate at which the producers push data and the rate at which the
consumer pull data.

32. • What is Stateless and Stateful Protocols?
• Stateless Protocol
• It is a network model in which the client sends a request to the server and the
server in return sends a response back according to the current state just like the
Request-Response model.
• The server is not obliged to keep the session information or the status of each
communication partner for multiple requests.
• They are very easy to implement on the Internet.
• Stateless protocols work better when the crash occurs because no state needs to
be restored, a failed server can simply reboot after a crash.
• Examples:- HTTP (Hypertext Transfer Protocol), UDP (User Datagram
Protocol), DNS (Domain Name System).

33. • Stateful Protocol
• In this protocol, suppose a client sends a request to the server and the server
doesn't respond, then the client resends a request to the server.
• Stateful protocols are logically heavy to implement on the Internet.
• Stateful Protocol does not work better at the time of the crash because stateful
servers must retain information about the state and session details of internal
states.
• Examples:- FTP (File Transfer Protocol), Telnet.

34. APIs (Application Programming Interface)
• API Application In IoT.
• Application Programming Interface (API) is an interfacing software platform that
allows the exchange of any information or data and supports the interaction
among different applications or any such intermediaries.
• What are APIs?
• An API is an interface used by programs to access an application.
• It enables a program to send commands to another program and receive replies
from the app.
• IoT APIs are the interface points between an IoT device and the Internet and/or
other network components.

35. • There are four principal types of API commonly used in web-based applications:
Public, Partner, Private and Composite.
• Public APIs. A public API is open and available for use by any outside developer or
business. An enterprise that cultivates a business strategy that involves sharing its
applications and data with other businesses will develop and offer a public API.
• Partner APIs. A partner API, only available to specifically selected and authorized
outside developers or API consumers, is a means to facilitate business-to-business
activities. For example, if a business wants to selectively share its customer data
with outside CRM firms, a partner API can connect the internal customer data
system with those external parties -- no other API use is permitted.
• Internal APIs. An internal (or private) API is intended only for use within the
enterprise to connect systems and data within the business. For example, an
internal API may connect an organization's payroll and HR systems.

36. • Composite APIs. Composite APIs generally combine two or more APIs to craft a
sequence of related or interdependent operations. Composite APIs can be
beneficial to address complex or tightly-related API behaviors, and can sometimes
improve speed and performance over individual APIs.

37. Machine to Machine
• This is commonly known as Machine to machine communication.
• It is a concept where two or more than two machines communicate with each
other without human interaction using a wired or wireless mechanism.
• M2M is an technology that helps the devices to connect between devices without
using internet.
• M2M communications offer several applications such as security, tracking and
tracing, manufacturing and facility management.
• M2M is also named as Machine Type Communication (MTC) in 3GPP ( 3rd
Generation Partnership Project).
• M2M is communication could carried over mobile networks, for ex- GSM-GPRS.
• In M2M communication, the role of mobile networks is largely confined to server
as a transport networks.
• M2M is only subset of IoT .

38. Difference between IoT and M2M
Basis of IoT M2M
Abbreviation Internet of Things Machine to Machine
Intelligence
Devices have objects that are
responsible for decision making
Some degree of intelligence is
observed in this.
Connection type used
The connection is via Network and
using various communication types.
The connection is a point to point
Communication protocol used
Internet protocols are used such
as HTTP, FTP, and Telnet.
Traditional protocols and
communication technology techniques
are used
Data Sharing
Data is shared between other
applications that are used to improve
the end-user experience.
Data is shared with only the
communicating parties.
Internet
Internet connection is required for
communication
Devices are not dependent on the
Internet.

39. Type of Communication It supports cloud communication
It supports point-to-point
communication.
Computer System Involves the usage of both Hardware and Software. Mostly hardware-based technology
Scope A large number of devices yet scope is large. Limited Scope for devices.
Business Type used
Business 2 Business(B2B) and Business 2
Consumer(B2C)
Business 2 Business (B2B)
Centric Information and service centric Communication and device centric.
Components
Devices/sensors, connectivity, data processing, user
interface
Device, area networks, gateway,
Application server.
Examples Smart wearables, Big Data and Cloud, etc. Sensors, Data and Information, etc.

40. Software define network
• Software-Defined Networking (SDN) is an approach to networking that uses
software-based controllers or application programming interfaces (APIs) to
communicate with underlying hardware infrastructure and direct traffic on a
network.
• This model differs from that of traditional networks, which use dedicated
hardware devices (i.e., routers and switches) to control network traffic. SDN can
create and control a virtual network – or control a traditional hardware – via
software.
• network virtualization allows organizations to segment different virtual networks
within a single physical network, or to connect devices on different physical
networks to create a single virtual network, software-defined networking enables
a new way of controlling the routing of data packets through a centralized server.

41. Why Software-Defined Networking is
important?
• Increased control with greater speed and flexibility
• Customizable network infrastructure
• Robust security

42. • How does Software-Defined Networking (SDN) work?
• In SDN (like anything virtualized), the software is decoupled from the hardware.
• SDN moves the control plane that determines where to send traffic to software,
and leaves the data plane that actually forwards the traffic in the hardware.
• This allows network administrators who use software-defined networking to
program and control the entire network via a single plane instead of on a device by
device basis.

43. • There are three parts to a typical SDN architecture, which may be located in
different physical locations:
• Applications, which communicate resource requests or information about the
network as a whole
• Controllers, which use the information from applications to decide how to route a
data packet
• Networking devices, which receive information from the controller about where
to move the data

44. • Benefits of Software-Defined Networking
• Many of today’s services and applications, especially when they involve the cloud,
could not function without SDN.
• SDN allows data to move easily between distributed locations, which is critical for
cloud applications.
• SDN supports moving workloads around a network quickly.
• dividing a virtual network into sections, using a technique called network functions
virtualization (NFV).
• Finally, because of the speed and flexibility offered by SDN, it is able to support
emerging trends and technologies such as edge computing and the Internet of
Things, which require transferring data quickly and easily between remote sites.

45. • How is SDN different from Traditional Networking?
• SDN is software-based, while traditional networking is hardware-based.
• The control plane is software-based, SDN is much more flexible than traditional
networking.
• It allows administrators to control the network, change configuration settings,
provision resources, and increase network capacity—all from a centralized user
interface, without adding more hardware.

46. • What are the different models of SDN?
• Open SDN
• SDN by APIs
• SDN Overlay Model
• Hybrid SDN