Introduction to IOT/M2M

SIDDHARTH TRIKHA
Senior Research Engineer
C-DOT

oneM2M Training
10/3/2019 1
[C-DOT Confidential]
The next step for the Internet evolution
Internet Internet Internet Internet
Pre-
of of of of
internet
CONTENT SERVICES PEOPLE THINGS

“HUMAN “MACHINE
“SOCIAL
TO “WWW” “WEB 2.0” TO
MEDIA”
HUMAN” MACHINE”

• Fixed & • e-mail • e- • Skype • Identification,

mobile productivity tracking, monitoring,
• Informa • Facebook
telephony metering, …
• tion • e-commerce • YouTube
• SMS •… • Semantically
• Entertainme •… structured and shared
nt data…
•… •…
+ smart + smart + smart + smart + smart
networks IT platforms phones & devices, data &
& services applications objects, ambient
tags context

© ETSI 2014. All rights reserved

10/3/2019 oneM2M Training in TEC [C-DOT Confidential] 3
Standard End to End IoT/M2M Solution
What are the components in an IOT
system ?

IoT technology stack – from IoT devices(sensors, actuators),

gateways to IoT platforms

1. IoT devices(sensors, actuators).

2. The local network (this can include a Gateway, which translates
proprietary communication protocols to Internet Protocol).
3. IoT platforms: Back-end services (enterprise data systems, or PCs
and mobile devices).

Courtsey : www.iotone.com
 IoT Devices:
Sensors & Actuators
• A sensor is a device that detects, measures or indicates any specific
physical quantity such as light, heat, motion, moisture, pressure,
or similar entities, by converting them into any other form which is
mostly, electrical pulses.
• Whereas sensors sense and send, actuators act and activate. The
actuator gets a signal and sets in motion what it needs to set in
motion in order to act upon/within an environment.

10/3/2019 oneM2M Training in TEC [C-DOT Confidential] 6

10/3/2019 oneM2M Training in TEC [C-DOT Confidential] 7
 IoT Gateways
• IoT gateways de facto are used for connectivity aggregation,
encryption and decryption of IoT data (security), the translation of
the various protocols that exist in the overall IoT technology
landscape, the management and onboarding of IoT devices, pre-
processing and aggregation of data and so forth.

10/3/2019 oneM2M Training in TEC [C-DOT Confidential] 8

 IoT Platform
• At a high level, IoT platforms provide a head start in building IoT
systems by providing built-in tools and capabilities to make IoT
easier and cheaper for businesses, developers, and users. An IoT
platform helps facilitate the communication, data flow, device
management, and the functionality of applications.

10/3/2019 oneM2M Training in TEC [C-DOT Confidential] 9

 Broad key Technologies for development of IoT

1. Platformisation based on standards enabling Interoperability,

scalability, modularity.

2. Intelligence- Support of AI and Machine learning

3. Analytics at the edge of Gateway router or mobile network

4. Security: Support for embedded security solutions. Security by

design features (Hardware & software).

5. Low power wireless networks: extended battery life as most of

the devices will be unmanned and charging not possible.

6. High speed and reliable internet at fixed and mobile devices

Technology roadmap for short term, mid term and long term ?
 IoT Working

10/3/2019 oneM2M Training in TEC [C-DOT Confidential] 11

12
 IoT Protocols

10/3/2019 oneM2M Training in TEC [C-DOT Confidential] 13

Constrained Application Protocol (CoAP)

10/3/2019 oneM2M Training in TEC [C-DOT Confidential] 14

 CoAP
• CoAP is an internet utility protocol for constrained gadgets. It is
designed to enable simple, constrained devices to join IoT through
constrained networks having low bandwidth availability (e.g.,
low-power, lossy networks), between devices and general nodes on
the Internet, and between devices on different constrained
networks both joined by an internet.
• CoAP makes use of the UDP protocol for lightweight
implementation. It also uses restful architecture, which is just like
the HTTP protocol.
• A 4-byte fixed header and a compact encoding of options enables
small messages that cause no or little fragmentation on the link
layer.
10/3/2019 oneM2M Training in TEC [C-DOT Confidential] 15
Message Queue Telemetry Transport
Protocol (MQTT)

10/3/2019 oneM2M Training in TEC [C-DOT Confidential] 16

 MQTT
• MQTT protocols paintings on top of TCP to offer easy and dependable
streams of information.
• These IoT protocols include 3 foremost additives: subscriber, publisher,
and broker. The writer generates the information and transmits the facts
to subscribers through the dealer. The dealer guarantees safety by means
of move-checking the authorization of publishers and subscribers.
• When a tool sends a message associated with an exact topic, the message
drives to any customer subscribed to it.
• There are several projects that implement MQTT. Examples are:
• Facebook Messenger. Facebook has used aspects of MQTT in Facebook
Messenger for online chat. However, it is unclear how much of MQTT is
used or for what.

10/3/2019 oneM2M Training in TEC [C-DOT Confidential] 17

 IoT Hardware: Arduino Uno

10/3/2019 oneM2M Training in TEC [C-DOT Confidential] 18

 Arduino Uno
• IoT Hardware components can vary from low-power boards;
single-board processors like the Arduino Uno which are basically
smaller boards that are plugged into mainboards to improve and
increase its functionality by bringing out specific functions or
features (such as GPS, light and heat sensors, or interactive
displays). A programmer specifies a board’s input and output, then
creates a circuit design to illustrate the interaction of these inputs
and outputs.

10/3/2019 oneM2M Training in TEC [C-DOT Confidential] 19

 Raspberry Pi

10/3/2019 oneM2M Training in TEC [C-DOT Confidential] 20

 Raspberry Pi
• Another well-known IoT platform is Raspberry Pi 2, which is a
very affordable and tiny computer that can incorporate an entire
web server. Often called “RasPi,” it has enough processing power
and memory to run Windows 10 on it as well as IoT Core. RasPi
exhibits great processing capabilities, especially when using the
Python programming language.

10/3/2019 oneM2M Training in TEC [C-DOT Confidential] 21

 Potential M2M services
Everything Else you can think of
10

10/3/2019 Orientation Program for RE 2018 22

10/3/2019 oneM2M Training in TEC [C-DOT Confidential] 23
10/3/2019 oneM2M Training in TEC [C-DOT Confidential] 24
IoT and M2M framework
Linked things and digital
Things representations
representations Applications
Applications

Communications Communications
network
network

Blood
pressure
GW Smart phone serving as
A an M2M device
Field area
A network Pulse
Device oximeter
A A
Device
Device Device

Things Smart
bandage
© ETSI 2014. All rights reserved Pedometer
 The issue with IoT interoperability is diversity

oneM2M Training
03-10-2019 [C-DOT Confidential] 26
Current State of IoT Deployments

10/3/2019 oneM2M Training in TEC [C-DOT Confidential] 27

Today each vertical develops the
A global interoperable Standard,
whole technology stack, leading
enables a
to silos and cross vertical
cross-vertical IoT Eco-System
interoperability issues
Supply Chain / Industrial IoT

Automotive / Connected Car

Healthcare / Fittnes

Connected Home
Data presentation
Smart Cities
Utilities

Data Analytics
Data storage
IoT Applications
IoT Service Enablement
Functions
Connectivity

28
 Present Landscape of IoT/M2M Architecture
Pipe (vertical):
1 Application, 1 NW,
1 (or few) type of Device

Business
Application

Business platform

Transport Network (mobile, fixed, Powerline ..)

Gateway

Local N/W

A
A Application Entity Device

C-DOT
03-10-2019 29
Confidential
 Current State of Vertical Centric Siloed Ecosystem
Management Layer Management
App

ITS ITS ITS ITS

Application1 Application2 Application3 Application4 Other Applications
Like
❖ Safety and

❖ Emergency Systems

❖ Car Sharing System

❖ Parking Management
System

❖ Etc. etc.

Car Insurance Maintenance Traffic Police

Manufacturer Provider Provider

oneM2M Training in TEC

03-10-2019 31
[C-DOT Confidential]
 Data Sharing Example
• Cars fitted with various sensors send information to the
manufacturer

• The service provider servicing the car may also need access to some
of the sensor data

• The insurance company providing insurance for the car also needs
information as to how the car is driven and based on this info
charges the premium.

• The on-road assistance company would require the location

information of the car to send appropriate assistance

• The traffic police needs accident information to be able to manage

traffic.

• This information would be useful for the commuters to select

alternate route

oneM2M Training in TEC

03-10-2019 [C-DOT Confidential] 32
 Q. What’s the Solution?

A. Standardisation.

oneM2M Training in TEC

03-10-2019 [C-DOT Confidential] 33
Definitions
• No single industry definition for Internet of Things/M2M
• But broad agreement on following key concepts:
• The Internet of Things is the framework where “Things” have
representations in the Internet. A representation may contain semantically
structured data (e.g., status, capabilities, location, measurements) that can
be shared, processed or acted upon. Sharing of information is governed
according to privacy settings and access rights.
• The "Things" that are represented in the Internet may be active (e.g.,
Zigbee sensor) or passive (e.g., RFID tag).
• The representation of the “Things” to the Internet is enabled by M2M
Technologies

10/3/2019 oneM2M Training in TEC [C-DOT Confidential] 34

 Need For Standardization
• So far the IoT/M2M industry is vertical Centric and the Telecom Network is merely
used as a means for transport.
However, the real value of these IoT ecosystem comes from interoperability and
sharing of Data amongst various divergent applications.
• Standardization is required in order to deliver cost-effective IoT/M2M solutions,
This would enable device, applications and Semantic interoperability and thus
allow this market to take off in its true potential.
• Many component-level standards already exist, addressing various radio interfaces,
different meshed or routed networking choices, or offering a choice of identity
schemes. Each is optimised for a particular application scenario and so there exists a
degree of fragmentation.
Need is to embrace them and not reinvent the wheel.
• Now, efforts are being made by SDOs like OneM2M to bring all these pieces
together, and identify the standardization gaps which exist.
oneM2M Training in TEC
03-10-2019 [C-DOT Confidential] 35
 oneM2M is
A global partnership among Standards Defining Organizations (SDOs) and Industry
Associations :
1. ETSI (European Telecommunications Standards Institute, Europe),
2. TIA (Telecommunication Industries Association, America),
3. TSDSI (Telecommunications Standards Development Society, India),

5. ARIB (Association of Radio Industries and Businesses, Japan),

6. ATIS (Advancing Transformation of the ICT Industry, America),
7. CCSA (China Communications Standards Association, China),
8. TTC (Telecommunications Technology Committee, Japan).
Additional partners contributing to the oneM2M work include:
BBF (Broadband Forum), Continua, GlobalPlatform, HGI (Home Gateway Initiative), the New
Generation M2M Consortium - Japan, and OMA (Open Mobile Alliance).
[C-DOT is also partner Type I (through TSDSI) contributing to the standards]
• In simple terms the main goal to develop technical specifications for an M2M Service Layer
• A software platform to make M2M devices/applications communicate with each other in a secure and efficient
manner

10/3/2019 oneM2M Training in TEC [C-DOT Confidential] 37

 oneM2M Partnership Project

oneM2M Training in TEC

03-10-2019 [C-DOT Confidential] 38
 What is oneM2M?

Global initiative
to drive
• Requirements
IoT interoperability • Architecture
through the covers • API specifications
development and implementation • Security
of standards • Interoperability

Mission Facilitate, implement and promote IoT standardization and

interoperability
Purpose To specify, promote and maintain a Common IoT Services Layer

Deliverables Technical Reports & Technical Specifications

39
 Ongoing Collaborations
• Collaboration is important to reach common understanding, avoid overlap and build interoperable IoT ecosystems globally.

Sharing/Reference
(Liaison, workshop, …)
P2413 MIoT
ref. arch, Certificatio
OHTP n

JTC1
Interworking SCP,
WG10 SmartM2M
OCF

SG20 OSGi/D Endorsement SCEF/CIoT

WG
AL
(adoption) WoT 3
TR-069/ TR-181
DD
AllJoyn S OPC-UA
OMA DM/
LWM2M
HTTP/ CoAP/
(D)TLS/
MQT WebSocket
T
Partnership

Source: Huawei
40
 Benefits
Lower Costs
CAPEX OPEX
– Lower cost of deployment (library – Efficient communications (policy-
of functions) driven and event triggered)
– Programmers can focus on – Sensor data sharing (produce once,
applications (not on underlying consume many times)
communications)
– Transport economics (use best
– Scale economies of horizontal transport network for business
service layer (common functions for
needs)
diverse use-cases)
Simplifies the development of applications

– Common services layer for different verticals and segments eliminates the need for
application-specific platforms

Creates mass-market economies of scale

Accelerates IoT adoption

41
 Ultimate Goal:
IoT cross-domain interoperability

Without oneM2M With oneM2M

• Highly fragmented market with limited vendor-specific
applications
• Reinventing the wheel: Same services developed again and
again
• Each silo contains its own technologies without interop
• End-to-end platform: common service capabilities layer
• Interoperability at the level of communications and data
• Seamless interaction between heterogeneous applications and
devices
 What is Common Service Layer?
❖ It is a software/middleware layer
❖ It sits between applications and underlying communication
networking HW/SW
Application Layer ❖ It rides on top of IP protocol stack
❖ It provides functions that applications across different industry
segments commonly need
❖ It is integrated into devices/gateways/servers and allows
distributed intelligence
❖ It hides complexity of NW usage from apps
Network Layer ❖ It stores and shares data
❖ It supports access control
❖ It notifies applications about events

Enable the industry to develop Standard based Applications which would reduce the development, test and
deployment lifecycles.
By deploying the Standards compliant Common Service Layer Platform, M2M Service Providers can offer wide range
of services developed by the industry.
It can also play a pivotal role in the Smart City Projects by having this platform which would ease the development
efforts of the application providers offering solutions for smart city project.
oneM2M Training in TEC
03-10-2019 [C-DOT Confidential] 43
 The Common Service Functions in oneM2M Architecture

Group
Registration Discovery Security
Management
HTTP(S)
Devices/
Sensors
Application &
Data Management Subscription & Device
CoAP Service
& Repository Notification Management
Management

MQTT Communication
Network Service Service Charging
Management and Location
Exposure & Accounting
Delivery Handling
Applications
in the Cloud
WebSocket
Transaction
Semantics
Management

CSE
03-10-2019 oneM2M Training in TEC 45
[C-DOT Confidential]
 Details of the Common Service Functions (CSFs)
Registration
Discovery
Security
Group Management
Data Management & Repository
Subscription & Notification
Device Management
Application & Service Management
Location
Network Service Exposure
Communication Management and
Delivery Handling
Service Charging & Accounting
Transaction Management
Semantics
03-10-2019
Registers the Applications ( and each instance of the application )with the CSE
Discovery of the resources ( Devices as well as applications) within the CSE
Ensures security of the data as well as communication
Grouping the devices/sensors and taking common action
Managing Storage of Data within CSE
Notifying Applications about Data arrival or Events
Management of Devices TR069, LWM2M, OMA-DM
Management of Applications and Service Subscriptions
Location data management
Choosing optimal network for application & Device Triggering,
When and How often communication should happen
Providing Charging Data (Records for Billing)
Scheduling of a transaction, locking and unlocking of resources targeted by
a transaction
Enable applications to manage semantic information and provide
functionalities based on this information
oneM2M Training in TEC 46
[C-DOT Confidential]
Learn form the modularity of smart Phones -
offer a framework for developers!
Governance:

• Applications access the

Applications Connectivity Layer and built-in
sensors, via API’s provided by the
Operating System

Operating System • Operating System collects

connectivity requests from
applications, buffers messages,
optimizes & controls device’s
network use
Connectivity
• Connectivity Layer provides
device access to the Internet via the
3GPP mobile network, Wi-Fi, etc..
Apply the concept of an Operating System to IoT Devices and Application
Developers
47
 Scope of and purpose of IoT
technology Layers
IoT Field IoT Infrastructure
Device(s)
▪ Measuring of Physical Parameters ▪ UI / Presentation of Device Data
IoT Application ▪ Execution of commands ▪ Data Analytics etc.

▪ Storing of data in case of lack of ▪ Developer API to control:

connectivity ▪ Data Management
▪ Security, Authentication & ▪ Security
Service Layer Authorization ▪ Device Management
▪ Device Management & Firmware ▪ Connectivity Management
update mechanism
▪ Connectivity Management
▪ Developer API
Connectivity Layer ▪ Reliable & efficient data transport ▪ Reliable & efficient data transport

48
oneM2M a Global Partnership Project
to develop the IoT Service Layer
Over 200 member
organizations
in oneM2M

The 8 regional Standards

Development Organizations jointly
develop the oneM2M technical
specifications. oneM2M standards are
then referenced by regional legal and
regulatory bodies

49
 Individual technologies / Protocols used
today
IoT Field Device(s) IoT Infrastructure

IoT Application

Service Layer
Standards

Connectivity Layer
Standards

50
 Bundling of individual service Layer
technologies by oneM2M
IoT Field Device(s) IoT Infrastructure

IoT Application

Service Layer
Standards

Connectivity Layer
Standard

51
Functions provided by oneM2M
IoT Field Device(s) IoT Infrastructure

IoT Application

Application developers can leverage

Common Service Functions (CSF’s) provided by
Service Layer oneM2M
oneM2M Communicati
Group
Common Registration Discovery Security
Management
on
Management
Service Layer
Data Registration Application & Network
Subscription Device
Management Service Service
& Notification Management
& Repository Management Exposure

Service
Transaction
Location Charging & Semantics
Management
Accounting

52
oneM2M Application Developers Interface
IoT Field Device(s) IoT Infrastructure

IoT Application

Developer-Interface

ServiceCommon
oneM2M Layer
Standards
Service Layer

Connectivity
Connectivity Layer
Layer
Standards

IP Communication
53
oneM2M Interfaces with Underlying Transport
Networks
IoT Field Device(s) IoT Infrastructure

IoT Application

ServiceCommon
oneM2M Layer
Standards
Service Layer

Network-Interface
SCEF
Connectivity
Connectivity Layer
Layer
(Service Capability Exposure Function)

Standards
3GPP Network
IP Communication
54
So how does oneM2M
help?

55
oneM2M Breaks Down the Silos
Horizontal
Smart Smart Smart
Emergency
Information Flow
Transportatio Infrastructur
Services n e Smart Smart Smart
Emergency Transportatio Infrastructur …
Services n e

Information Flow
Information Flow
Information Flow

Vertical
Vertical

Vertical

… Service Layer

56
oneM2M is Distributive and Scalable

Flexible
App App App App App App
Deployment
Service
Layer
Options
• IoT Cloud / Enterprise

Service
• IoT Gateway
Layer Service
Layer
• IoT Edge Device
Communication Network(s)
• IoT User Devices
 Where to find more details
http://www.onem2m.org

oneM2M IoT
Device/Clou Appication
d Integrator Developer

For globally certified products refer to: http://www.onem2mcert.com/main/main.php

58
 Summary and conclusion
Developers can leverage from globally specified-, cloud
IoT Application provider independent- API’s, to transfer data-, safely,
developers reliable, battery efficient and secure, -form an IoT device to a
cloud infrastructure
Customers have the freedom of choice, in selecting their
IoT Customers cloud solution provider, IoT device manufacturer and their
application developer for the cloud and device

Connectivity Are able to protect their networks from badly developed IoT
provider applications and use their networks more efficient

oneM2M technology solves common technical problems, in context of IoT

solutions for all stakeholders in the value chain, and allows to focus @ the actual
IoT application
59
 Description of Nodes in OneM2M Architecture

Application Dedicated Node (ADN):

An Application Dedicated Node is a Node that contains at least one Application
Entity and does not contain a Common Services Entity.
Example of physical mapping: an Application Dedicated Node could reside in a
constrained M2M Device.

Application Services Node(ASN):

An Application Service Node is a Node that contains one Common Services Entity
and contains at least one Application Entity.
Example of physical mapping: an Application Service Node could reside in an M2M
Device.

03-10-2019 oneM2M Training in TEC 60

[C-DOT Confidential]
 Description of Nodes in OneM2M Architecture

Middle Node (MN):

A Middle Node is a Node that contains one Common Services Entity and contains
zero or more Application Entities.
Example of physical mapping: a Middle Node could reside in an M2M Gateway.

Infrastructure Node (IN):

An Infrastructure Node is a Node that contains one Common Services Entity and
contains zero or more Application Entities.
Example of physical mapping: an Infrastructure Node could reside in an M2M
Server.

oneM2M Training in TEC

03-10-2019 61
[C-DOT Confidential]
 Conceptual Architecture View
Application Infrastructure
Dedicated Node
Node Middle Node
AE AE
AE
Things: AE Apps
Mca
Sensors, Cloud
Devices Application Mca CSE Services,
Service
BSS
Node CSE
AE
Mca
CSE Gateways Network
AE: Application Entity
CSE: Common Services Entity
NSE: Network Services Entity NSE NSE NSE

Sensor Areas Cloud

62
 Configurations supported by oneM2M Architecture

oneM2M Training in TEC 63

03-10-2019
[C-DOT Confidential]
 Deployment of IoT Applications : the oneM2M way

Smart Parking Smart Street Light Smart Metering Intelligent Transport

IN-CSE (M2MSP-1) IN-CSE (M2MSP-2)

MN MN MN

MN MN
ADN ADN ADN

ADN ADN

MN-Middle Node :oneM2M Gateway Device (Contains CSE and optionally applications)
ADN-Application Dedicated Node :The oneM2M Device that contains applications which interface with sensors/actuators

03-10-2019 oneM2M Training in TEC

65
[C-DOT Confidential]
 oneM2M Timeline

03-10-2019 oneM2M Training in TEC

66
[C-DOT Confidential]
 oneM2M Feature Summary by Release

oneM2M Training in TEC

03-10-2019 [C-DOT Confidential] 67
 Deployment of Standardised M2M/IoT Ecosystem
External world

ISP/TSP
1 Router , Firewall

ISP/TSP Redundant LAN Fabric

2

Application servers Database servers

ISP/TSP Servers for Miscellaneous Functions
3

ISP/TSP
ADN/MN 4
Redundant Fibre Channel SAN Fabric
PAN ISP/TSP
5

Disk Based Backup

Storage
Storage Encryption
Device
Tape library

Application M2M Service

Service Provider Provider DoT

1. M2M Service Provider registers with DoT fulfilling the M2MSP registration Process(Licensed or otherwise!!)
2. Sets up M2M Platform Infrastructure with the common service functions
3. Ties up with one or many TSPs/ISPs for connectivity
4. Application Service Provider(s) approaches M2MSP with their intended application and signs an agreement. The agreement binds
them for application enrolment and registration, Access Control Policies, use of security framework, device management, discovery
and other CSFs besides commercial agreements.
5. The ASPs get the Unique AE-ID, Encryption Keys for their application entities
6. The ASPs set up their IN-AE on their platform of choice(Public or private infrastructure).
7. The ASPs roll out devices & applications in the field
oneM2M Training in TEC
03-10-2019 [C-DOT Confidential] 68
 Strong Implementation Base

oneM2M Training in TEC

03-10-2019 [C-DOT Confidential] 69
03-10-2019 oneM2M Developer Event 70