0% found this document useful (0 votes)
13 views

Q1. Explain The IOT Architecture and Its Domain. Ans

Uploaded by

avipsa57
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
0% found this document useful (0 votes)
13 views

Q1. Explain The IOT Architecture and Its Domain. Ans

Uploaded by

avipsa57
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 4

Q1. Explain the IOT architecture and its domain.

Ans: The Internet of Things (IoT) architecture refers to the structure that supports the
deployment, opera on, and management of IoT devices, enabling them to communicate
and interact with each other, with centralized systems, and with users. IoT architecture is
typically divided into several layers, each serving a specific func on. Here’s an overview of
the key layers and the domains they encompass:
1. Percep on Layer (Device Layer)
 Func on: This is the physical layer where data is collected from the environment. It
consists of sensors and actuators embedded in various devices.
 Components: Sensors, actuators, RFID tags, cameras, GPS, etc.
 Domain: IoT devices, embedded systems, sensor networks.
2. Network Layer (Connec vity Layer)
 Func on: This layer is responsible for transmi ng the data collected by the
percep on layer to other parts of the architecture. It ensures reliable and secure
data transfer.
 Components: Routers, gateways, network protocols (Wi-Fi, Bluetooth, Zigbee, 4G/5G,
LPWAN, etc.).
 Domain: Networking technologies, communica on protocols, network infrastructure.
3. Edge Compu ng Layer
 Func on: Edge compu ng processes data locally at or near the data source, reducing
latency and the load on centralized systems. It filters and pre-processes data before
sending it to the cloud.

 Components: Edge devices, edge servers, local data centers, fog compu ng nodes.
 Domain: Edge compu ng, fog compu ng, real- me analy cs.

Domains of IoT
1. Industrial IoT (IIoT): Focuses on industrial applica ons like manufacturing, supply
chain management, and asset tracking.
o Example: Smart factories, predic ve maintenance.
2. Smart Homes: Includes IoT applica ons in residen al environments for automa on
and security.
o Example: Smart thermostats, security cameras, smart ligh ng.
3. Healthcare: IoT in healthcare involves remote pa ent monitoring, smart medical
devices, and health data analy cs.
o Example: Wearable health monitors, telemedicine devices.
4. Smart Ci es: IoT applica ons for urban management, including traffic control, waste
management, and energy efficiency.
o Example: Smart streetlights, traffic monitoring systems.
5. Agriculture: IoT enables precision farming, livestock monitoring, and automated
irriga on.
o Example: Soil moisture sensors, GPS-guided tractors.
6. Automo ve: Focuses on connected vehicles, autonomous driving, and fleet
management.
o Example: Connected cars, vehicle-to-everything (V2X) communica on.
7. Retail: Enhances customer experience through personalized services, inventory
management, and smart checkout.
o Example: Smart shelves, automated checkouts.

Q2. Write the key elements of SDN.


Ans: So ware-Defined Networking (SDN) is an approach to network management that
enables dynamic, programma cally efficient network configura on to improve network
performance and monitoring. The key elements of SDN include:

1. Separa on of Control and Data Planes :


- Control Plane : This is the brain of the network, where decisions about where traffic is
sent are made. It is centralized and can be managed by so ware.
- Data Plane : This is responsible for forwarding packets to the selected des na on. It
carries out the instruc ons from the control plane.

2. Centralized Control :
- SDN introduces a centralized controller that has a global view of the network. This
controller manages and configures network devices, like switches and routers, from a central
point.

3. Programmability :
- SDN enables network administrators to programma cally control and automate the
behavior of the network using APIs. This allows for easier management and faster
deployment of applica ons.

4. Open Standards and Protocols :


- SDN leverages open standards like OpenFlow, which is a protocol that allows the SDN
controller to interact with the data plane. This fosters interoperability between devices from
different vendors.

5. Abstrac on :
- SDN abstracts the underlying network infrastructure, enabling easier management by
hiding the complexity of physical devices and network topologies. This abstrac on layer
helps in developing network applica ons and services without worrying about the hardware
details.

6. Network Virtualiza on :
- SDN supports network virtualiza on, which allows for the crea on of mul ple virtual
networks on top of the same physical infrastructure. This is useful for op mizing resources
and crea ng isolated environments.

7. Dynamic Configura on :
- SDN allows for the real- me adjustment of network configura ons in response to
changing demands, such as fluctua ng traffic pa erns or the introduc on of new services.

8. Security and Policy Enforcement :


- SDN centralizes security policies, making it easier to implement and enforce network-
wide security rules. The centralized controller can monitor traffic and apply security policies
across the en re network.

9. Scalability and Flexibility :


- SDN architectures are inherently scalable, allowing networks to grow and adapt to
increased demand without a complete overhaul of the infrastructure. It offers flexibility in
deploying new applica ons and services.

These elements make SDN a powerful tool for modernizing and op mizing network
infrastructures.

Q3. Explain NFV use case with suitable diagram.


Ans: The term “Network Func ons Virtualiza on” (NFV) refers to the use of virtual machines in
place of physical network appliances. There is a requirement for a hypervisor to operate networking
so ware and procedures like load balancing and rou ng by virtual computers. A network func ons
virtualiza on standard was first proposed at the OpenFlow World Congress in 2012 by the European
Telecommunica ons Standards Ins tute (ETSI), a group of service providers that includes AT&T, China
Mobile, BT Group, Deutsche Telekom, and many more.

Need of NFV:
With the help of NFV, it becomes possible to separate communica on services from
specialized hardware like routers and firewalls. This eliminates the need for buying new
hardware and network opera ons can offer new services on demand. With this, it is possible
to deploy network components in a ma er of hours as opposed to months as with
conven onal networking. Furthermore, the virtualized services can run on less expensive
generic servers.
Advantages:
 Lower expenses as it follows Pay as you go which implies companies only pay for
what they require.
 Less equipment as it works on virtual machines rather than actual machines which
leads to fewer appliances, which lowers opera ng expenses as well.
 Scalability of network architecture is quite quick and simple using virtual func ons in
NFV. As a result, it does not call for the purchase of more hardware.
Working:
Usage of so ware by virtual machines enables to carry out the same networking tasks as
conven onal hardware. The so ware handles the task of load balancing, rou ng, and
firewall security. Network engineers can automate the provisioning of the virtual network
and program all of its various components using a hypervisor or so ware-defined
networking controller.

You might also like