JCE e CONNECT

Subject Code: 18EC741

Lecture 1.4

Chapter 2
 Text & Reference Books
Text Books:
• 1. Raj Kamal, ”Internet of Things-Architecture and design
principles”, McGraw Hill Education.
• 2. Holger Karl & Andreas Willig, "Protocols And Architectures for
Wireless Sensor Networks", John Wiley, 2005.
Reference Books:
• 1. Feng Zhao & Leonidas J. Guibas, “Wireless Sensor Networks- An
Information Processing Approach", Elsevier, 2007.
• 2. Kazem Sohraby, Daniel Minoli, & Taieb Znati, “Wireless Sensor
Networks- Technology, Protocols, And Applications”, John Wiley,
2007.
• 3. Anna Hac, “Wireless Sensor Network Designs”, John Wiley, 2003.

Krupa Rasane 18EC741 3

 Chapter 2
• IoT/M2M SYSTEMS, LAYERS AND DESIGNS
STANDARDISATION
– 2.2.1 Modified OSI Model for the IoT/M2M
Systems (1.3)
• 2.4.1 Data Management and Consolidation
Gateway(1.4)

Krupa Rasane 18EC741 4

 2.4.1 Data Management and
Consolidation Gateway
• Gateway includes the provisions for one or more
of the following functions: transcoding and data
management.
• Following are data management and
consolidation functions:
● Transcoding
● Privacy, security
● Integration
● Compaction and fusion

Krupa Rasane 18EC741 5

 Transcoding
• Transcoding means data adaptation, conversion and change of protocol, format or
code using software.
• The gateway renders the web response and messages in formats and
representations required and acceptable at an IoT device.
• Similarly, the IoT device requests are adapted, converted and changed into
required formats acceptable at the server by the transcoding software.
• For example, use of transcoding enables the message request characters to be in
ASCII format at the device and in Unicode at the server.
• It also enables the use of XML format database at the device, while the server has
a DB2, Oracle or any other database.
• Transcoding involves formats, data and code conversion from one end to another
when the multimedia data is transferred from a server to the mobile TV, Internet
TV, VoIP phone or smartphone as the client devices.
• Transcoding applications also involve filtering, compression or decompression.
• A transcoding proxy can execute itself on the client system or the application
server.
• A transcoding proxy has conversion, computational and analysing capabilities,
while a gateway has conversion and computational capabilities only.

Krupa Rasane 18EC741 6

 Privacy
• Data such as patient medical data, data for supplying goods in a company from and to
different locations, and changes in inventories, may need privacy and protection from
conscious or unconscious transfer to untrustworthy destinations using the Internet.
• Privacy is an aspect of data management and must be remembered while designing an
application. The design should ensure privacy by ensuring that the data at the receiving end
is considered anonymous from an individual or company.
Following are the components of the privacy model:
● Devices and applications identity-management
● Authentication
● Authorisation
● Trust
● Reputation
• A suitable encryption of identification of data source enforces privacy. Device ID
management provides for privacy.
• The analysed decrypted data is an input to application, service or process. IoT or M2M data
have to be for the beneficiary individual person or company only.
• When data is transfered from one point to another, it should be ensured that the stakeholder
in future may not misuse the device end data or the application data.
• These static and dynamic relationships are components which depend on trust and
reputation.
Krupa Rasane 18EC741 7
 Secure Data Access
• Access to data needs to be secure.
• The design ensures the authentication of a request for data
and authorisation for accessing a response or service.
• It may also include auditing of requests and accesses of the
responses for accountability in future.
• Example 2.4 described how a layer provides the
confidentiality and authorisation using AES-128 and CCM.
• End-to-end security is another aspect while implies using a
security protocol at each layer, physical, logical link and
transport layers during communication at both ends in a
network.

Krupa Rasane 18EC741 8

 Data Gathering and Enrichment
• IoT/M2M applications involve actions such as data-gathering (acquisition),
validation, storage, processing, reminiscence (retention) and analysis.
• Data gathering refers to data acquisition from the devices/devices network.
• Four modes of gathering data are:
1. Polling refers to the data sought from a device by addressing the device; for
example, waste container filling information in a waste management system
2. Event-based gathering refers to the data sought from the device on an event; for
example, when the device reaches near an access point or a card reaches near
the card reader or an initial data exchange for the setup of peer-to-peer or
master-slave connection of BT device using NFC
3. Scheduled interval refers to the data sought from a device at select intervals; for
example, data for ambient light condition in Internet of streetlights
4. Continuous monitoring refers to the data sought from a device continuously; for
example, data for traffic presence in a particular street ambient light condition in
Internet of streetlights
Data enrichment refers to adding value, security and usability of the data.nalysis.

Krupa Rasane 18EC741 9

 Data Dissemination
• Consider the following three steps for data enrichment before the
data disseminates to the network as aggregation, compaction and
fusion.
• Aggregation refers to the process of joining together present and
previously received data frames after removing redundant or
duplicate data.
• Compaction means making information short without changing the
meaning or context; for example, transmitting only the incremental
data so that the information sent is short.
• Fusion means formatting the information received in parts through
various data frames and several types of data (or data from several
sources), removing redundancy in the received data and presenting
the formatted information created from the information parts.
• Data fusion is used in cases when the individual records are not
required and/or are not retrievable later.

Krupa Rasane 18EC741 10

 Energy Dissipation in Data
Dissemination
• Energy consumption for data dissemination is an important
consideration in many devices in WPANs and in wireless sensor
nodes (WSNs).
• This is due to limited battery life.
• Energy is consumed when performing computations and
transmissions. Higher the data rate, the greater will be the energy
consumed.
• Higher is RF used, the greater will be the energy consumed. Higher
the gathering interval, the lower will be the energy consumed.
• Energy efficient computations can be done by using concepts of
data aggregation, compaction and fusion.
• Lesser the data bytes communication, greater the acquisition
intervals, and lower the data rate for data transfer, lesser the
energy dissipation.

Krupa Rasane 18EC741 11

 Data Source and Data Destination
• ID: Each device and each device resource is
assigned an ID for specifying the data of
source and a separate ID for data destination.
• Address: Header fields add the destination
address (for example, 48-bit MAC address at
Link layer, 32-bit IPv4 address at IP network
and 128-bit IPv6 address at IPv6 network) and
may also add the port (for example, port 80
for HTTP application).

Krupa Rasane 18EC741 12

 Data Characteristics, Formats and
Structures
• Data characteristics can be in terms of temporal data (dependent on the
time), spatial data (dependent on location), real-time data (generated
continuously and acquired continuously at the same pace), real-world
data (from physical world for example, traffic or streetlight, ambient
condition), proprietary data (copy right data reserved for distribution to
authorised enterprises) and big data (unstructured voluminous data).
• Data received from the devices, formats before transmission onto
Internet.
• The format can be in XML, JSON and TLV.
• A file can be MIME type for Internet. Structure implies the ways for
arranging the data bytes in sequences with size limit = PDU for a layer.

Krupa Rasane 18EC741 13

 2.4.2 Device-management Gateway
• Device Management (DM) means provisioning for the device ID or address which
is distinct from other resources, device activating, configuring (managing device
parameters and settings), registering, deregistering, attaching and detaching.
• Device management also means accepting subscription for its resources.
• Device fault management means course of actions and guidelines to be followed in
case if a fault develops in the device.
• Open Mobile Alliance (OMA)-DM and several standards are used for device
management.
• OMA-DM model suggests the use of a DM server which interacts with devices
through a gateway in case of IoT/M2M applications.
• A DM server is a server for assigning the device ID or address, activating,
configuring (managing device parameters and settings), subscribing to device
services or opting out of device services and configuring device modes.
• A device instead of a DM server, communicates to a gateway in case of low-power
loss environment.

Krupa Rasane 18EC741 14

 2.4.2 Device-management Gateway
Gateway functions for device management are:
• Does forwarding function when the DM server
and device can interact without reformatting
or structuring
• Does protocol conversion when the device
and DM server use distinct protocols
• Does proxy function in case an intermediate
pre-fetch is required in a lossy environment or
network environment needs.
Krupa Rasane 18EC741 15
Krupa Rasane 18EC741 16
Krupa Rasane 18EC741 17