Unit 2

Fundamental IoT
Mechanism & Key Technologies

Prof. Rajashree Sutrawe

raj.sutrawe2k19@gmail.com
1
Unit-2 Content

• Identification of IoT Objects and Services

• Structural Aspects of the IoT
• Environment Characteristics
• Traffic Characteristics
• Scalability
• Interoperability
• Security and Privacy
• Open Architecture
• Key IoT Technologies
• Device Intelligence
• Communication Capabilities
• Mobility Support. 2
Identification of IoT Object and
Services
• Identification codes can be classified as
• (i) object IDs (OIDs)
• (ii) communication IDs.
• Examples
• radio frequency identification (RFID)/electronic product code (EPC), content
ID,
1

• telephone number, and uniform resource identifier (URI)/uniform

resource locator (URL);
• media access control (MAC) address,
network layer/IP address, and
session/protocol ID.

3
Identification of IoT Object and
Services
• All objects to have a permanent unique identifier, an OID.
• All end-point network locations and/or intermediary-point network
locations to have a durable, unique network address (NAdr) using
IPv6
• When objects that have enough intelligence to run a communications
protocol stack (so that they can communicate), are placed on a
network, these objects can be tagged with a NAdr.

4
Identification of IoT Object and
Services
• Every object then has a tuple (OID, NAdr) that is always unique,
although the second entry (NAdr) of the tuple may change with time,
location, or situation.
• In a stationary, non-variable, or mostly static environment, assigns
the OID to be identical to the NAdr where the object is expected to
attach to the network; that is, the object tuple (NAdr, NAdr).
• In case the object moved, the OID could then be refreshed to the address of the new
location; that is, the object tuple (NAdr’, NAdr’).
• In general trend toward object mobility, giving rise to a dynamic
environment; hence, to retain maximal flexibility, it is best to
separate, in principle, the OID from the NAdr

5
Identification of IoT Object and
Services
• Identification scheme is that it affords global uniqueness.
• It is useful to have mechanisms for hierarchical grouping to deal with
large populations.
• The feature of IPv6 address provides such hierarchical grouping. For a number of
applications, there is a need to map/bind IP addresses (communications IDs)
with other relevant OIDs.
• Modern layered communication architectures also require addressing
and processing capabilities at several layers,
• For example, at the Data Link Layer, at the Network Layer, at the Transport
(Protocol ID), and at the session/application layer.
• Some argue that different identification schemes are required for
different applications.
• For example, the information related to things such as books, medicine, and
clothes may not require global identification because revocation lists are
required

6
Identification of IoT Object and
Services
• An EPC (electronic product code) is a number assigned to an RFID tag
representative of an actual EPC.
• Each number is encoded with a header, identifying the particular EPC version
used for coding the entire EPC number.
• An EPC manager number is defined, allowing individual companies or
organizations to be uniquely identified; an object class number is present,
identifying objects used within this organization, such as product types EPC
uses a numerical system for product identification, but its capabilities are much
greater.
• An EPC is actually a number that can be associated with specific product
information, such as date of manufacture and origin and destination of
shipment. This provides significant advantages for businesses and consumers.
• The EPC is stored on an RFID tag, which transmits data when prompted by a
signal emitted by a special reader.
• Note that EPC and RFID are not interchangeable

7
Identification of IoT Object and
Services
• OID may be replaced by object naming
• Domain name system (DNS) is a mechanism for Internet-based naming
• In the IoT context, the advantages of identifying information by name, not
by node address.
• DNS is used to map the “human-friendly” host names of computers to their
corresponding “machinefriendly” IP addresses. E.g. www.google.com
• Object name service (ONS) will also be important in the IoT to map the
“thing-friendly” names of object which may belong to heterogeneous name
spaces (e.g., EPC, uCode, and any other self-defined code) on different
networks (e.g., TCP/IP network) into their corresponding “machine-friendly”
addresses or other related information of another TCP/IP network.
• This naming system can used for set of systems as object name should
disclose its identity.

8
Identification of IoT Object and
Services
• For some applications, especially where there is a need for simple end-
user visibility of a small set of objects (i.e., where the objects are few
and discretely identifiable a home’s thermostat, a home’s refrigerator, a
home’s lighting system, a pet of the owner), the object may be identified
through Web Services (WSs).
• WSs provide standard infrastructure for data exchange between two
different distributed applications.
• Lightweight WS protocols for the representational state transfer (REST)
interface may be useful in this context.
• REST is a software architecture for distributed systems to implement
WSs. REST is good compared to simple object access protocol (SOAP)
and web services description language (WSDL) due to its relative
simplicity.

9
Identification of IoT Object and
Services
• IoT objects and IoT applications (e.g., grid control, home control, traffic
control, and medical monitoring), security and privacy in
communications and services become absolutely critical.
• Strong authentication, encryption while transmitting, and also
encryptions for data at rest is ideal; however, the computational
requirements for encryption can be significant.
• At the central/authenticating site, rapid authentication support is
desirable; otherwise objects would not be able to authenticate in large-
population environments.

10
Identification of IoT Object and
Services
• Tracking the object using GPS is costly{to know exact physical location}
• Cellular services may be also too expensive
• Tracking movable individual objects and group objects is also different.
• Different tracking methods required.
• But worst when tracking more than one object.
• Solution - Myriad sensors on a cruise ship or gateway controller in
Medical Body area n/w – (MBAN) in this relative position is used
• There is a need to maintain ubiquitous(present or found everywhere)
and seamless(smooth) communication while tracking the location of
objects.

11
Identification of IoT Object and
Services
• Capabilities for scalability are important in order to be able to support an
IoT environment where there is a large population that is highly
distributed.
• Locator/identifier separation.
• Basic idea behind the separation is that the Internet architecture
combines two functions, routing locators (where one is attached to the
network) and identifiers (where one is located), in one number space:
the IP address.
• Proponents of the separation architecture postulate that splitting these
functions apart will yield several advantages, including improved
scalability for the routing system.
• The separation aims to decouple locators and identifiers, thus allowing
for efficient aggregation of the routing locator space and providing
persistent identifiers in the identifier space.
• The protocol called locator/ID separation protocol (LISP)

12
Identification of IoT Object and
Services
• LISP aims for an incrementally deployable protocol.
• The LISP WG (Working Group) frame that include
• (i) an architecture description
• (ii) deployment models,
• (iii) a description of the impacts of LISP, (iv) LISP security threats and
solutions,
• (v) allocation of end-point identifier (EID) space, (vi) alternate mapping
system designs
• (vii) data models for management of LISP.

13
 Structural Aspects of IoT

• IoT structure consists of several different devices and

sensors. Quantity of these components in a single system is.
limited by factors, such as a number of input and output.
channels for a device, Internet or electrical power network
limit
Basically, there are three IoT architecture layers:
• 1. The client side (IoT Device Layer)
• 2. Operators on the server side (IoT Getaway Layer)
• 3. A pathway for connecting clients and operators (IoT
Platform Layer)
Structural Aspects of the IoT

• Structural Issue related to

• Environment Characteristics
• Traffic Characteristics
• Scalability
• Interoperability
• Security and Privacy
• Open Architecture

16
Structural Aspects of the IoT
Environment Characteristics
• Most (but certainly not all) IoT/machine-to-machine (M2M) nodes
have design constraints:
• Low power (with the requirement that they will run potentially for years on
batteries)
• Low cost (total device cost in single-digit dollars or triple digit rupee)
• Significantly more devices than in a LAN environment
• Severely limited code and RAM space (e.g., generally desirable to fit the
required code—MAC, IP, and anything else needed to execute the embedded
application—in, for example, 32K of flash memory, using 8-bit
microprocessors)
• Unobtrusive but very different user interface for configuration (e.g., using
gestures or interactions involving the physical world)
• Requirement for simple wireless communication technology. In particular, the
IEEE 802.15.4 standard is very promising for the lower (physical and link)
layers

17
Structural Aspects of the IoT
Environment Characteristics

18
Structural Aspects of the IoT
Environment Characteristics

19
Structural Aspects of the IoT
Traffic Characteristics
• The characteristics of IoT/M2M communication is different from
other types of networks or applications.
• For example, cellular mobile networks are designed for human
communication and communication is connection centric; it entails
interactive communication like
• between humans (voice, video), or data communication involving humans (web
browsing, file downloads, and so on).
• It follows that cellular mobile networks are optimized for traffic characteristics of
human-based communication and applications.
• But in IoT, M2M the expectation is that there are many devices, there
will be long idle intervals, transmission entails small messages, there
may be relaxed delay requirements, and device energy efficiency is
paramount.

20
Structural Aspects of the IoT
Traffic Characteristics

21
Structural Aspects of the IoT
Traffic Characteristics

Real World Example 22

Structural Aspects of the IoT
Scalability
• The application and its a desire over time for the service decides the
Scalability.
• When contemplating expansion, one wants to be able to build on
previously deployed technology (systems, protocols), without having
to scrap the system and start from scratch.
• The efficiency of a larger system should be better than the efficiency
of a smaller system.
• This is what is meant by scalability.
• The goal is to make sure that capabilities such as addressing,
communication, and service discovery, among others, are delivered
efficiently in both small and large scale.

23
Structural Aspects of the IoT
Interoperability
• Applications, technology suppliers, and stakeholders, it is desirable to
develop and/or re-use a core set of common standards.
• To the degree possible, existing standards may prove advantageous
to a rapid and cost-effective deployment of the technology.

24
Structural Aspects of the IoT
Security and Privacy
• IoT relates to electric power distribution, goods distribution,
transport and traffic management, e-health, and other key
applications, as noted earlier
• It is critical to maintain system-wide confidentiality, identity integrity,
and trustworthiness.

25
Structural Aspects of the IoT
Open Architecture
• The goal is to support a wide range of applications using a common
infrastructure, preferably based on a service-oriented architecture
(SOA) over an open service platform, and utilizing overly networks
(these being logical networks defined on top of a physical
infrastructure)

26
Key IoT Technologies
• List of Technologies are:
• Device Intelligence
• Communication Capabilities
• Mobility Support
• Device Power
• Sensor Technology
• RFID Technology
• Satellite Technology

• Note: Red color marked points not for syllabus

27
Key IoT Technologies
Device Intelligence
• Device Intelligence
• In order for the IoT to become a reality,
• Objects should be able to intelligently sense and interact with the
environment
• Possibly store some passive or acquired data
• Communicate with the world around them
• Object-to-gateway device communication or even direct object-to-object
communication is desirable

28
Key IoT Technologies
Device Intelligence
• These intelligent capabilities are necessary to support ubiquitous
networking to provide seamlessly interconnection between humans
and objects
• Some have called this mode of communication Any Services, Any Time, Any
Where, Any Devices, and Any Networks (also known as “5-Any”)

29
Key IoT Technologies
Communication Capabilities
• It is highly desirable for objects to support ubiquitous end-to-end
communications
• To achieve ubiquitous connectivity for human-to-object & object-to-
object communications, networking capabilities will need to be
implemented in the objects (“things”)
• IP is considered to be key capability for IoT objects
• Self-configuring capabilities, especially how an IoT device can
establish its connectivity automatically without human intervention,
are also of interest
• IPv6 auto-configuration & multihoming features are useful,
particularly scope-based IPv6 addressing features

30
Key IoT Technologies
Mobility Support
• Another consideration related to tracking and mobility support of
mobile object
• Mobility-enabled architectures & protocols are required
• Some objects move independently, while others will move as one of
group
• Therefore, according to the moving feature, different tracking
methods are required.
• It is important to provide ubiquitous and seamless communication
among objects while tracking the location of objects.
• Mobile IPv6 (MIPv6) offers several capabilities that can address this
requirement.

31
Key IoT Technologies
Device Power
• Related to the powering of the “thing”
• Especially for mobile devices or devices that do not have intrinsic
power
• M2M/IoT applications are always constrained by following factors:
• Devices have ultra-low-power capabilities
• Devices must be of low cost
• Devices must have small physical size & light in weight

32
Key IoT Technologies
Device Power
• The following factors that must be • Environmental conditions
considered in selecting the most • Temperature
suitable battery for a particular • Pressure
application : • Humidity
• Operating voltage level • Vibration
• Load current and profile • Shock
• Pressure
• Duty cycle—continuous or
intermittent • Safety and reliability
• Service life • Shelf life
• Physical requirement • Maintenance and replacement
• Size • Environmental impact and
• Shape recycling capability
• Weight
• Cost
33
Key IoT Technologies
Sensor Technology
• A sensor network is an infrastructure comprising sensing (measuring),
computing, communication, data collection, monitoring, surveillance,
and medical telemetry.
• Sensor network technology, specifically, with embedded networked
sensing, ships, aircrafts, and buildings can “self-detect” structural faults
(e.g., fatigue-induced cracks).
• Earthquake-oriented sensors in buildings can locate potential survivors
and can help assess structural damage; tsunami-alerting sensors can
certainly prove useful for nations with extensive coastlines.
• Sensors also find extensive applicability in battlefield for reconnaissance
and surveillance

34
Key IoT Technologies
Sensor Technology

35
Key IoT Technologies
Sensor Technology

36
Key IoT Technologies
Sensor Technology

37
Key IoT Technologies
RFID Technology
• RFIDs are electronic devices associated with objects (“things”) that
transmit their identity (usually a serial number) via radio links.
• RFID tags are devices that typically have a read-only chip that stores a
unique number but has no processing capability.
• RFID and barcode facilitate the global supply chain and impact all
subsystems within that overall process, including material requirement
planning (MRP), just in time (JIT), electronic data interchange (EDI), and
electronic commerce (EC).

38
Key IoT Technologies
RFID Technology

39
Key IoT Technologies
RFID Technology

40
Key IoT Technologies
RFID Technology- Basic Concept

41
Key IoT Technologies
RFID Technology
• Contactless smart cards (SCs) are more sophisticated than RFID tags
• RFID tags are typically less expensive than SCs.
• When an RFID tag or contactless SC passes within a defined range, a reader
generates electromagnetic waves; the tag’s integrated antenna receives the
signal and activates the chip in the tag/SC, and a wireless communications
channel is set up between the reader and the tag enabling the transfer of
pertinent data.

42
Key IoT Technologies
RFID Technology
• There are a number of standards for RFIDs. Some of the key ones
include the following:
• The ISO 14443
• operating frequency of 13.56 MHz that embed a CPU; power consumption is about
10mW; data throughput is about 100 Kbps and the maximum working distance (from
the reader) is around 10 cm.
• The ISO 15693
• operating at 13.56 MHz frequency, but it enables working distances as high as 1 m, with
a data throughput of a few Kbps.
• The ISO 18000
• with frequency such as 135 KHz, 13.56 MHz, 2.45 GHz, 5.8 GHz, 860–960 MHz, and 433
MHz.
• The ISO 18000–6 standard uses the 860–960MHz range and is the basis for the Class-1
Generation-2 UHF RFID, introduced by the EPCglobal Consortium.

43
Key IoT Technologies
RFID Technology
• Typically, EPC codes used for active RFIDs or IP addresses are
transmitted in clear form
• Provide strong privacy for the IoT.
• The host identity protocol (HIP) with this protocol, active RFIDs do not expose
their identity in clear text, but protect the identity value (e.g., an EPC) using
cryptographic procedures.

44
Key IoT Technologies
RFID Technology
• An RFID system is logically comprising several layers, as follows:
• the tag layer,
• the air interface (also called media interface) layer,
• the reader layer;
• Tag (device) layer:
• Architecture and EPCglobal Gen2 tag finite state machine
• Media interface layer:
• Frequency bands, antennas, read range, modulation, encoding, data rates
• Reader layer:
• Architecture, antenna configurations, Gen2 sessions, Gen2

45
Key IoT Technologies
RFID Technology- standards in the EPCglobal
environment

46
Key IoT Technologies
RFID Technology- standards in the EPCglobal
environment
• An interface is the UHF Class-1 Gen-2 tag air interface, which
specifies a radio-frequency communications protocol by which an
RFID tag and an RFID reader device may interact.
• A component is an RFID tag that is the product of a specific tag
manufacturer.
• An EPC Network Service is the ONS, which provides a logically
centralized registry through which an EPC may be associated with
information services.

47
Key IoT Technologies
Satellite Technology
• Ability to support mobility in all geographical environments (including
Antarctica)
• Global reach
• Offers interesting commercial possibilities

48