Module 2 questions in the PDF are:
1. What is M2M communication? Explain end to end M2M system architecture with neat diagram.
2. What is M2M gateway? With neat diagram explain block diagram of M2M gateway.
3. Difference between: i) M2M and IoT ii) SDN and NFV.
4. Explain SDN with neat diagram of conventional network architecture with its limitations.
5. Explain SDN architecture with its control plane and data plane with neat diagram (twist may
ask: Explain SDN layers with neat diagram).
6. Explain NFV architecture and its key elements and use cases with neat diagram.
Extra for score:
7. Explain the need for IoT system management and discuss limitations of SNMP.
8. Explain NETCONF protocol architecture and YANG data modeling language and explain IoT system management
using NETCONF-YANG with neat diagram.
Machine-to-Machine (M2M) Communication
Definition
Machine-to-Machine (M2M) communication refers to the direct communication between machines or devices for
the purpose of remote monitoring, control, and data exchange without human intervention.
End-to-End M2M System Architecture
1. M2M Area Network (Local Network)
This is the local network of machines/devices, also called M2M nodes.
Characteristics:
Devices have sensors, actuators, and communication modules
Use short-range, usually non-IP protocols
Operate in a limited geographical area
Collects data from physical environment
Performs local monitoring and control
Common protocols used:
ZigBee
Bluetooth
Modbus
2. Communication Network (Wide Area Network)
The communication network connects different M2M area networks over long distances.
characteristics:
Uses IP-based networks such as the Internet
Enables remote access and global connectivity
Bridges geographically distributed M2M systems
Note: Since local M2M devices are non-IP, they cannot directly communicate with IP networks.
3. M2M Gateway
To solve the non-IP to IP communication problem, an M2M gateway is used.
Functions of M2M Gateway:
Acts as a bridge/translator between non-IP and IP networks
Converts local protocol messages into IP-based messages
4. Application Domain
The application domain is where the collected M2M data is processed, stored, and used.
Functions:
Data visualization
Monitoring and reporting
Control and automation
Business analytics
Examples of applications:
Smart homes
Industrial automation
Smart electricity systems
Remote monitoring and service management
Role of M2M Gateways and Communication between Non-IP and IP-based Networks
In M2M systems, local devices often use non-IP communication protocols such as ZigBee, Bluetooth, or Modbus,
whereas wide-area communication uses IP-based networks like the Internet. Since non-IP devices cannot directly
communicate with IP networks, an M2M gateway is used to bridge this gap.
Role of M2M Gateway
4+4+D
1. Protocol Translation – Converts non-IP protocols into IP-based protocols.
2. Data Aggregation – Collects data from multiple M2M nodes.
3. Device Visibility – Makes non-IP devices accessible over IP networks.
4. Security Support – Provides basic security and access control.
Communication between Non-IP Devices and IP-based Networks
Step-by-Step Communication Process
Local Communication (Non-IP) M2M devices (nodes) communicate with each other using short-range, non-IP
protocols such as ZigBee, Bluetooth, or Modbus within the M2M area network.
1. Gateway Interaction All local devices send their data to the M2M gateway using their native
non-IP protocols.
2. Protocol Translation at Gateway The gateway translates non-IP messages into IP-based
messages (e.g., TCP/IP, HTTP, MQTT).
3. IP Network Communication Translated data is transmitted over IP-based networks such as the
Internet to remote servers or applications.
4. Reverse Communication Control commands from applications are sent back through the
gateway, translated into non-IP format, and delivered to local devices.
🖧 Software Defined Networking (SDN)
Definition: Software Defined Networking (SDN) is a new approach to designing computer networks in which the
control logic of the network is separated from the data forwarding hardware. In SDN, the network is divided into
two distinct planes: control plane and data plane.
Traditional Network Architecture
In conventional networks, both the control plane and the data plane are implemented inside the same hardware
devices such as routers and switches. This makes the devices:
Complex
Difficult to manage
Less scalable
SDN Architecture
In SDN, the control plane is decoupled from the data plane and is placed in a centralized controller, while the data
plane remains in the forwarding devices.
1. Control Plane (6 Points)
Responsible for decision making
Decides how and where data packets should move
Implemented in a centralized SDN controller
Maintains a global view of the network
Uses software and programmable APIs
Can dynamically add, update, or delete flow rules
2. Data Plane (5 Points)
Responsible for actual packet forwarding
Implemented in simple network devices (switches/routers)
Executes forwarding rules received from the SDN controller
Uses standard packet-forwarding hardware
Does not implement complex control logic
Key Elements of SDN Architecture
1. Centralized Network Controller
Central point of control for the entire network
Simplifies configuration, management, and provisioning
Enables faster innovation using software
2. Programmable Open APIs
Allow communication between:
o Network applications
o SDN controller
3. Standard Communication Interface (OpenFlow)
OpenFlow is the southbound interface between controller and switches
Uses flow-based forwarding
A flow is a rule that says: “If traffic looks like this, do this.”
Flows can be: Static or Dynamic
OpenFlow switch components:
o Flow tables
o Group table
o OpenFlow channel to controller