IOT-Module 3
IOT-Module 3
Scalable
IP is a common Internet protocol that has been
massively deployed and tested for robust scalability.
IP has scalability as one of its strength.
Manageable and highly secure
Communications infrastructure requires appropriate
management and security capabilities for proper operations
Well known network and security management tools are easily
leveraged with an IP network layer.
Real challenges still exists in securing constrained nodes,
handling legacy OT protocols and scaling operations
IP provides a solid foundation for IoT by allowing secured and
manageable bidirectional data communication capabilities
between all devices in the network
Stable and resilient
IP exists from past 30 years. It has a large and well-
established knowledge base.
It has been used in many critical infrastructures such as
financial and defense networks.
Deployed for many critical services, such as voice and
video
A large number of IT professionals can help in
designing, deploying and operating IP-based solutions
IP addresses the network issues such as naming, time
distribution, traffic prioritization, isolation etc. very
well.
Consumer’s market adoption
IoT consumers access IoT applications and devices through
smart/phones, tablets or PCs (broadband/wireless).
IP is the common protocol that links IoT consumer space to
the accessing devices.
The innovation factor
IP has the increased innovation factor.
It is the underlying protocol for applications ranging from
file transfer and email to the world wide web, e-commerce,
social networking, mobility etc.
From cloud, centralized or distributed architectures, IP data
flow can be developed and implemented according to the
business requirements
Adoption or Adaptation of the IP
Adaptation means application layered
gateways(ALGs) must be implemented to
ensure the translation between non- IP and
IP layers
Hop-by-hop scheduling
A node reserves a path to a destination node multiple
hops away by requesting the allocation of cells in a
schedule at each intermediate node hop in the path.
There are three 6TiSCH forwarding models:
Track Forwarding (TF): Simplest and fastest
A track is a unidirectional path between a source and a
destination.
Track is formed by pairing bundles of receive cells in a
schedule with a bundle of receive cells set to transmit
A frame received within a particular cell or cell bundle is
switched to another cell or cell bundle
Fragment forwarding (FF):
First fragment is routed based on the IPV6 header.
The sub-layer learns the next-hop selection of this first
fragment, which is applied to all subsequent fragments of
that packet
IPV6 Forwarding (6F): This model forwards the traffic
based on its IPV6 routing table
Flow of packets is prioritized by traditional QoS and
RED operations.
RPL: IPV6 Routing Protocol for Low
Power and Lossy Network
RPL specification was published as RFC 6550 by the
RoLL(Routing over Low Power and Lossy Network)
working group
Each node acts as a router and becomes part of a mesh
network
Routing is performed at the IP layer
Each node, when it receives the IPV6 packet
determines the next hop destination based on the
information present in the IPV6 header.
RPL protocol defines two modes:
Storing mode:
All node contains full routing table of the RPL domain.
Every node knows how to directly reach every other node
Non storing mode:
Only the border router of the RPL domain contains the full
routing table.
All other nodes in the domain only maintain their list of
parents.
It saves memory space and CPU.
A node always forwards its packet to border router, which
knows how to ultimately reach the final destination
RPL process involves building a DODAG(Destination
Oriented Directed Acyclic Graph)
It is a DAG rooted to one destination. The destination
is at border router.
Upward routes in RPL are discovered and configured
using DAG Information Object messages(DIO).
Nodes listen to DIOs to handle changes in the
topology that can affect routing.
The information in the DIO messages determines
parents and the best path to DODAG root
Nodes establish downward routes by advertising their
parents set toward DODAG root using a Destination
Advertisement Object(DAO) message.
DAO messages allow nodes to inform their parents of
their presence and reachability from descendants.
Objective Function (OF)
Defines how metrics are used to select routes and
establish a node’s rank.
Rank
Is a approximation of how close a node is to the root
It helps to avoid routing loops and the count-to-infinity
problem.
Nodes can increase their rank if they receive a DIO
message with a larger version number
It can decrease the rank whenever it establishes a lower
cost routes
RPL Headers
`helps in loop detection
Metrics
Expected Transmission Count (ETX): value that tells the
number of transmission a node expects to make to deliver a
packet
Hop count: tracks the number of nodes traversed in a path
Latency: varies depending on power consumption. Paths with
lower latency is preferred.
Link Quality Level: measures the reliability of a link. It
considers the packet error rate caused by factors such as signal
attenuation and interference
Link color: Allows manual influence of routing by choosing the
links
Node state and Attribute: Identifies nodes that
functions as traffic aggregators and nodes that are being
impacted by high workload