Introduction IOT/M2M

Introduction to IOT/M2M
SIDDHARTH TRIKHA
Senior Research Engineer
C-DOT
10/3/2019
oneM2M Training
[C-DOT Confidential]
1

The next step for the Internet evolution
© ETSI 2014. All rights reserved
Pre-
internet
Internet
of
CONTENT
Internet
of
SERVICES
Internet
of
PEOPLE
+ smart
networks
+ smart
IT platforms
& services
+ smart
phones &
applications
+ smart
devices,
objects,
tags
“SOCIAL
MEDIA”
“WEB 2.0”“WWW”
“HUMAN
TO
HUMAN”
• Fixed &
mobile
telephony
• SMS
• e-mail
• Informa
• tion
• Entertainme
nt
• …
• e-
productivity
• e-commerce
• …
• Skype
• Facebook
• YouTube
• …
• Identification,
tracking, monitoring,
metering, …
• Semantically
structured and shared
data…
• …
“MACHINE
TO
MACHINE”
+ smart
data &
ambient
context
Internet
of
THINGS

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.

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.

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.

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

IoT Protocols

Constrained Application Protocol (CoAP)

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.

Message Queue Telemetry Transport
Protocol (MQTT)

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.

IoT Hardware: Arduino Uno

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.

Raspberry Pi

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.

Potential M2M services
10/3/2019 Orientation Program for RE 2018 22
10
Everything Else you can think of

IoT and M2M framework
© ETSI 2014. All rights reserved
Communications
network
Field area
network
Applications
A
Device
A
Device
A
Device
GW
A
Device
Things
Things
representations
Blood
pressure
Pulse
oximeter
Pedometer
Smart
bandage
Smart phone serving as
an M2M device
Communications
network
Applications
Linked things and digital
representations

The issue with IoT interoperability is diversity
2603-10-2019
oneM2M Training

Current State of IoT Deployments

Today each vertical develops the
whole technology stack, leading
to silos and cross vertical
interoperability issues
ConnectedHome
Automotive/ConnectedCar
SmartCities
Utilities
SupplyChain/IndustrialIoT
Healthcare/Fittnes
Connectivity
IoT Service Enablement
Functions
IoT Applications
Data storage
Data Analytics
Data presentation
A global interoperable Standard,
enables a
cross-vertical IoT Eco-System
28

Present Landscape of IoT/M2M Architecture
03-10-2019
C-DOT
Confidential
29
A
Pipe (vertical):
1 Application, 1 NW,
1 (or few) type of Device
Local N/W
Business
Application
Device
Transport Network (mobile, fixed, Powerline ..)
Gateway
Business platform
A
Application Entity

Other Applications
Like
❖ Safety and
❖ Emergency Systems
❖ Car Sharing System
❖ Parking Management
System
❖ Etc. etc.
03-10-2019 31
Management Layer Management
App
ITS
Application3
Maintenance
Provider
ITS
Application4
Traffic Police
ITS
Application1
Car
Manufacturer
ITS
Application2
Insurance
Provider
Current State of Vertical Centric Siloed Ecosystem
oneM2M Training in TEC

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
03-10-2019 32

Q. What’s the Solution?
A. Standardisation.
03-10-2019 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

Need For Standardization
03-10-2019
• 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.
35

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
oneM2M is

oneM2M Partnership Project
03-10-2019 38

• Requirements
• Architecture
• API specifications
• Security
• Interoperability
covers
What is oneM2M?
Global initiative
to drive
IoT interoperability
through the
development and implementation
of standards
Facilitate, implement and promote IoT standardization and
interoperability
Mission
To specify, promote and maintain a Common IoT Services LayerPurpose
Technical Reports & Technical SpecificationsDeliverables
39

Ongoing Collaborations
40
MQT
T
OMA DM/
LWM2M
HTTP/ CoAP/
(D)TLS/
WebSocket
TR-069/ TR-181
DD
S
P2413
JTC1
WG10
SG20
MIoT
SCP,
SmartM2M
Certificatio
n
ref. arch,
OHTP
WG
3
OPC-UA
WoT
SCEF/CIoT
AllJoyn
OCF
OSGi/D
AL
• Collaboration is important to reach common understanding, avoid overlap and build interoperable IoT ecosystems globally.
Source: Huawei
Sharing/Reference
(Liaison, workshop, …)
Interworking
Endorsement
(adoption)
Partnership

Benefits
Lower Costs
Simplifies the development of applications
CAPEX
– Lower cost of deployment (library
of functions)
– Programmers can focus on
applications (not on underlying
communications)
– Scale economies of horizontal
service layer (common functions for
diverse use-cases)
OPEX
– Efficient communications (policy-
driven and event triggered)
– Sensor data sharing (produce once,
consume many times)
– Transport economics (use best
transport network for business
needs)
– Common services layer for different verticals and segments eliminates the need for
application-specific platforms
Accelerates IoT adoption
Creates mass-market economies of scale
41

Ultimate Goal:
IoT cross-domain interoperability
• 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
Without oneM2M With oneM2M

What is Common Service Layer?
03-10-2019
❖ It is a software/middleware layer
❖ It sits between applications and underlying communication
networking HW/SW
❖ 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
❖ It stores and shares data
❖ It supports access control
❖ It notifies applications about events
Network Layer
Application Layer
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.
43

The Common Service Functions in oneM2M Architecture
Registration SecurityDiscovery
Group
Management
Data Management
& Repository
Application &
Service
Management
Device
Management
Subscription &
Notification
Communication
Management and
Delivery Handling
Service Charging
& Accounting
Location
Network Service
Exposure
CSE
HTTP(S)
CoAP
MQTT
WebSocket
Devices/
Sensors
Applications
in the Cloud
03-10-2019 45
Transaction
Management
Semantics

Details of the Common Service Functions (CSFs)
Registration
Security
Discovery
Group Management
Data Management & Repository
Application & Service Management
Device Management
Subscription & Notification
Communication Management and
Delivery Handling
Service Charging & Accounting
Location
Network Service Exposure
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)
03-10-2019
46
Transaction Management
Semantics
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

• Applications access the
Connectivity Layer and built-in
sensors, via API’s provided by the
Operating System
• Operating System collects
connectivity requests from
applications, buffers messages,
optimizes & controls device’s
network use
• Connectivity Layer provides
device access to the Internet via the
3GPP mobile network, Wi-Fi, etc..
47
Learn form the modularity of smart Phones -
offer a framework for developers!
Operating SystemOperating System
ApplicationsApplications
Governance:
ConnectivityConnectivity
Apply the concept of an Operating System to IoT Devices and Application
Developers

Scope of and purpose of IoT
technology Layers
Connectivity LayerConnectivity Layer
Service LayerService Layer
IoT ApplicationIoT Application
▪ Measuring of Physical Parameters
▪ Execution of commands
▪ Storing of data in case of lack of
connectivity
▪ Security, Authentication &
Authorization
▪ Device Management & Firmware
update mechanism
▪ Connectivity Management
▪ Developer API
IoT Field
Device(s)
IoT Infrastructure
▪ UI / Presentation of Device Data
▪ Data Analytics etc.
▪ Developer API to control:
▪ Data Management
▪ Security
▪ Device Management
▪ Connectivity Management
▪ Reliable & efficient data transport▪ Reliable & efficient data transport ▪ Reliable & efficient data transport▪ Reliable & efficient data transport
48

Over 200 member
organizations
in oneM2M
Over 200 member
organizations
in oneM2M
49
The 8 regional Standards
Development Organizations jointly
develop the oneM2M technical
specifications. oneM2M standards are
then referenced by regional legal and
regulatory bodies
oneM2M a Global Partnership Project
to develop the IoT Service Layer

Individual technologies / Protocols used
today
50
Connectivity Layer
Standards
Connectivity Layer
Standards
Service Layer
Standards
Service Layer
Standards
IoT Field Device(s) IoT Infrastructure

Bundling of individual service Layer
technologies by oneM2M
51
Connectivity Layer
Standard
Connectivity Layer
Standard
Service Layer
Standards
Service Layer
Standards

Functions provided by oneM2M
52
oneM2M
Common
Service Layer
oneM2M
Common
Service Layer
Application developers can leverage
Common Service Functions (CSF’s) provided by
oneM2M
Registration
Registration
Group
Management
SecurityDiscovery
Data
Management
& Repository
Application &
Service
Management
Device
Management
Subscription
& Notification
Communicati
on
Management
Service
Charging &
Accounting
Location
Network
Service
Exposure
Semantics
Transaction
Management
Service Layer

53
Connectivity Layer
Standards
Connectivity Layer
Standards
Service Layer
Standards
Service Layer
Standards
oneM2M Application Developers Interface
oneM2M Common
Service Layer
oneM2M Common
Service Layer
IP Communication
Developer-InterfaceDeveloper-InterfaceDeveloper-Interface

54
Connectivity Layer
Standards
Connectivity Layer
Standards
Service Layer
Standards
Service Layer
Standards
oneM2M Interfaces with Underlying Transport
Networks
oneM2M Common
Service Layer
oneM2M Common
Service Layer
IP Communication
Network-InterfaceNetwork-InterfaceNetwork-Interface
SCEF
(Service Capability Exposure Function)
3GPP Network

oneM2M Breaks Down the Silos
56
Smart
Emergency
Services
Smart
Transportatio
n
Smart
Infrastructur
e
Vertical
InformationFlow
Vertical
InformationFlow
Vertical
InformationFlow
Horizontal
Information Flow
Smart
Emergency
Services
Smart
Transportatio
n
Smart
Infrastructur
e
Service LayerService Layer…
…
…

oneM2M is Distributive and Scalable
Service
Layer
Service
Layer Service
Layer
Service
Layer
Communication Network(s)Communication Network(s)
Service
Layer
Service
Layer
AppAppAppApp AppApp AppApp AppApp AppApp
Flexible
Deployment
Options
• IoT Cloud / Enterprise
• IoT Gateway
• IoT Edge Device
• IoT User Devices

58
Where to find more details
oneM2M
Device/Clou
d Integrator
IoT
Appication
Developer
http://www.onem2m.org
For globally certified products refer to: http://www.onem2mcert.com/main/main.php

Customers have the freedom of choice, in selecting their
cloud solution provider, IoT device manufacturer and their
application developer for the cloud and device
IoT Customers
Summary and conclusion
59
Developers can leverage from globally specified-, cloud
provider independent- API’s, to transfer data-, safely,
reliable, battery efficient and secure, -form an IoT device to a
cloud infrastructure
IoT Application
developers
Are able to protect their networks from badly developed IoT
applications and use their networks more efficient
Connectivity
provider
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

03-10-2019 60
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.
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 61
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.
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.
Description of Nodes in OneM2M Architecture

Conceptual Architecture View
62
NSE
Things:
Sensors,
Devices
Infrastructure
Node
Middle Node
Application
Service
Node
AE
CSE
CSE
AE
Mca
Mca
Application
Dedicated
Node
AE
CSE
AE
Mca
AE
Apps
Cloud
Services,
BSS
Network
NSE NSE
Gateways
Sensor Areas Cloud
AE: Application Entity
CSE: Common Services Entity
NSE: Network Services Entity

03-10-2019 63
Configurations supported by oneM2M Architecture

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
Smart Parking Smart Street Light Smart Metering Intelligent Transport
IN-CSE (M2MSP-1) IN-CSE (M2MSP-2)
MN
MN MN MN
ADN
ADN
03-10-2019 65
Deployment of IoT Applications : the oneM2M way
ADN ADN
ADN
MN

6603-10-2019 oneM2M Training in TEC
oneM2M Timeline

oneM2M Feature Summary by Release
6703-10-2019

Redundant LAN Fabric
Redundant Fibre Channel SAN Fabric
External world
Router , Firewall
Application servers
Storage Encryption
Device
Tape library
Disk Based Backup
Storage
Database servers
Servers for Miscellaneous Functions
M2M Service
Provider DoT
Application
Service Provider
ISP/TSP
1
ISP/TSP
2
ISP/TSP
3
ISP/TSP
5
ISP/TSP
4ADN/MN
PAN
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
Deployment of Standardised M2M/IoT Ecosystem
6803-10-2019

Strong Implementation Base
03-10-2019 69

03-10-2019 oneM2M Developer Event 70

Introduction IOT/M2M

Recomendados

Recomendados

Más contenido relacionado

La actualidad más candente

La actualidad más candente (20)

Similar a Introduction IOT/M2M

Similar a Introduction IOT/M2M (20)

Último

Último (20)

Introduction IOT/M2M