machine to machine - basics

8/13/2019 Machine to Machine - Basics

http://slidepdf.com/reader/full/machine-to-machine-basics 1/32

M2M

SHUBHA N BHAMBHANI DDG (NT-DOT



M2MM2M is the technology that establishes

intelligent communication between things



AGENDA

• Introduction Basic Definitions

How it works

How it is different

• Key features of M2M

• Applications of M2M

• Architecture and components of M2M• Requirements for M2M

• Issues /concerns in M2M

• Standardization Efforts for M2M

• Conclusion



M2M is an anagram for.... machine

machine

It means communication and the bi-directional transfer of dabetween:

· man and machine

· machine and management systems

M2M is also named as Machine Type Communication (MTC) in



BASICS…..

M2M communication refers to technology that enables machines networked so data can be freely exchanged among these assets.

It is a form of data communication that involves one or more entitnot necessarily require human interaction or intervention in the pcommunication. It can be in two ways :

• Uplink to collect product and usage information• Downlink to send instructions or software updates, or to remote

equipment



'In some applications, it can also mean 'mobile-to-machine' or 'mamobile'. M2M refers to systems that let machines communicate w

management systems or with people using compatible mobileterminals‘………..NOKIA



INTERNET of THINGS



How it works……..

• Collection of data

• Transmission of selected data through a communication ne

• Assessment of the data

• Response to the available information



Its working …..

M2M works by embedding a communication module, sensor, or taphysical asset ( service, finished product etc.) for sending the infoabout its status and performance to a computer information syste

The information flow is automated and allows to remotely monitomaintain, and track these machines.

Important data about a machine can be uploaded to a computer from the machine itself rather than being manually collected and by a human being.



How it is different ??

The concept is not new

In fact, the manufacturing and utility industries have deployethat connect machines to an IT network using sensor technolseveral years.

Few examples : Closed loop plant-floor automation solutionsWide-area remote monitoring solutions -- SC



The difference lies ….

The telemetry networks that enabled SCADA and similar applwere specifically built for and were the exclusive domain of thorganizations that implemented these systems.

M2M communication, on the other hand, is accomplished usexisting public wireless data networks and access methods suwireless Cellular and Ethernet.



M2M is also different because

It involves• new or different market scenarios

• lower costs and effort

• a potentially very large number of communicating terminal

• little traffic per terminal



KEY FEATURES

• Low Mobility : M2M Devices do not move, move infrequently, or move only within aregion

• Time Controlled : Send or receive data only at certain pre-defined periods

• Time Tolerant : Data transfer can be delayed

• Packet Switched : Network operator to provide packet switched service with or withMSISDN

• Online small Data Transmissions: MTC Devices frequently send or receive small amo

• Monitoring: Not intend to prevent theft or vandalism but provide functionality to deevents

• Low Power Consumption : To improve the ability of the system to efficiently service applications

• Location Specific Trigger : Intending to trigger M2M device in a particular area like wdevices



Applications of M2M

• Security : Surveillances, Alarm systems, Access control, Car/driver security

• Tracking & Tracing : Fleet Management, Order Management, Pay as yAsset Tracking, Navigation, Traffic information, Road tolling, Trafficoptimization/steering

• Payment : Point of sales, Vending machines, Gaming machines

• Health : Monitoring vital signs, Supporting the aged or handicapped, WTelemedicine points, Remote diagnostics

• Remote Maintenance/Control : Sensors, Lighting, Pumps, Valves, Elevcontrol, Vending machine control, Vehicle diagnostics

• Metering : Power, Gas, Water, Heating, Grid control, Industrial meteri

• Manufacturing : Production chain monitoring and automation

• Facility Management : Home / building / campus automation



Some facts

1.4 BILLION Connections in 2020.

157 BILLION In revenue in 2020.

3.8 MILLION Management systems in active use by 2015 in North Americ

7

MILLION Stolen vehicle recovery and consumer telematics market by 2014 in L

540 MILLION Asset tracking in 2010 and expects to double by 2014.

28.7 MILLION Active connected car subscribers in 2015 in Europe.

Components of M2M



Components of M2M

• M2M Device: Device capable of replying to request for data contained wdevices or capable of transmitting data autonomously.

Through Gateways- ZigBee or Bluetooth/ Direct -embedded SIM, radio stack/FLA

• M2M Area Network (Device Domain): Provide connectivity between M2and M2M Gateways, e.g. personal area network

• M2M Gateway: Equipment that uses M2M capabilities to ensure M2M Dinter-working and interconnection to the communication network.

• M2M Communication Networks (Network Domain): It covers the commbetween the M2M Gateway(s) and M2M application(s), e.g. xDSL, LTE, WWLAN.

• M2M Applications: It contains the middleware layer where data goes thrvarious application services and is used by the specific business-processin



Architecture



M2M Access Options

M2M communication could be carried over mobile networks --

GSM-GPRS

CDMA EVDO networks

iDEN (integrated digital enhanced network).

M2M deployments limited to a local area can use Wi-Fi, wireleswireless LAN. However, the deployments that cover wide areas, leexisting public wireless data networks for wireless transport.

In M2M, role of mobile network is largely confined as a transport



Requirements for M2M

• M2M Application communication principles: It shall be able t

communication between M2M Applications in the Network and ApplicDomain, and the M2M Device or M2M Gateway, by using multiple

communication means, e.g. SMS, GPRS and IP Access.

• Message Delivery for sleeping devices: The M2M System shall

manage communication towards a sleeping device.

• Delivery modes : The M2M System shall support anycast, unicast,

and broadcast communication mode.

• Message transmission scheduling: The M2M System shall be ab

manage the scheduling of network access and of messaging.



Requirements…

• Message communication path selection: The M2M System shall be aboptimize communication paths, based on network cost, delays or

transmission failures, when other communication paths exist.• Communication with devices behind a M2M gateway: The M2M System

able to communicate with Devices behind a M2M gateway.

• Communication failure notification: M2M Applications, requesting reliaof a message, shall be notified of any failures to deliver the message.

• Scalability: The M2M System shall be scalable in terms of number of ConObjects.

• Abstraction of technologies heterogeneity: The M2M Gateway may be c

interfacing to various M2M Area Network technologies.

R i t



Requirements…

• Mobility: If the underlying network supports seamless mobility and roaming, the M2shall be able to use such mechanisms.

• Communication integrity: It shall be able to support mechanisms to assure communwell as Device integrity check for M2M services.

• Continuous connectivity: The M2M System shall support continuous connectivity, foapplications requesting the same M2M service on a regular and continuous basis.

• Confirm: The M2M System shall support mechanisms to confirm messages. A messagunconfirmed, confirmed or transaction controlled.

• Priority: The M2M System shall support the management of priority levels of the sercommunications services. Pre-emption is possible



Requirements …

• Anonymity: shall be able to support . If anonymity is requested by an M2M ApplicatiM2M Device side and the request is accepted by the network, the network infrastruchide the identity and the location of the requestor, subject to regulatory requirement

• Time Stamp: The M2M System shall be able to support accurate and secure and truststamping.

• Device/Gateway failure robustness: After a non-destructive failure, e.g. after a poweoutage, a M2M Device or Gateway should immediately return in a full operating stateautonomously.

• Radio transmission activity indication and control: The radio transmitting parts (e.g. of the M2M Device/Gateway should be able to provide a real-time indication of radiotransmission activity to the application on the M2M Device/Gateway, and may be insttime by the application to suspend/resume the radio transmission activity.



Issues /concerns in M2M

• The key concerns in M2M are related to addressing and security

• The M2M System should be flexible in supporting more than onescheme.

• It should support identification of connected objects by their natemporary id, pseudonym (i.e. different names for the same entilocation or combination thereof (e.g. URIs or IMSI).

• It should be possible to reuse names for certain classes of device

devices operating in certain Resource constrained environments• The addressing schemes should include:

IP address of connected objects.

IP address of group of connected objects (including multicast ad

E.164 addresses of connected objects (e.g. MSISDN).



Concerns….

• M2M devices would typically operate unmanned and unguardedhumans and thus are subject to increased levels of security threaphysical tampering, hacking, unauthorized monitoring, etc.

• Deployment, tend to require remote management of their functis likely that M2Mes will be deployed in very large quantities, anthem will also be mobile, making it unrealistic or impossible for o

or subscribers to send personnel to manage or service them.• Some M2M Equipment's (M2Mes) are typically required to be sm

inexpensive, able to operate unattended by humans for extendeof time, and to communicate over the wireless area network (WWLA



Some more concerns….

• Today’s telecoms networks are designed mainly for human to hu

communication

• At present for human to machine and machine to machine commstandardization are limited to standalone system not involving thnetworks and other general transport models

• Today’s wireless networks are not truly fit for an intended purponot and cannot enable the optimum delivery of M2M and IoT ap

The networks of MNOs are colossally over-engineered for most of applications



Issues that are of concern……..

Cellular networks are designed for voice and high-volume data traffic, n

intermittent payloads of under 30 bytes only, requiring a throughput of bps. Further, the communications overhead can be 500 to 600 bytes – worder of magnitude higher.

This led to the development of lightweight protocols like MQTT (MessaTelemetry Transport) and CoAP (Constrained Application Protocol).

The real issue is intrinsic: in order to take M2M and the IoT to the next lenable a cost-effective, long-term future, a new kind of network is need

It has to be dedicated to M2M and the IoT



The Optical Network

• Low cost and low energy consumption – needed to increaselife

• Ease of use – including device management and integrationsystems

• Frequency independence – thereby facilitating cost-effectivwide coverage

• Embedded subscriber identification – no SIM cards, no needsubscriber lifecycle management

The new network has to be designed from the bottom up using a relatively new techna new business model.



UNB .. A Game Changer ??

Completely dedicated to low throughput Machine-to-Machine/ Internet of Things ap

• A patented radio technology that is currently based on UNB (Ultra Narrow-Band), wthe license free ISM bands . It enables the cost-effective transmission of data over spectrum to and from connected objects , minimizing the number of antennas (baneeded for wide area coverage.

• Each base station can handle up to a million battery-operated devices. Cell density iaverage rural range of about 30-50 km , 3-10 km for urban areas.

• Energy consumption is 200 to 600 times lower than an equivalent cellular network,

of payload data to protocol data is normally between 20 to 50 percent.• Unlike Wireless Modems, UNB modems do not require multi-band air interfaces an

• Low-throughput, low-data rate application fire detection and automatic meter read

• RF modules embedded in the meters----no need to have SIM cards

St d di ti Eff t f M2M



Standardization Efforts for M2M

• ETSI’s has been established Machine-to-Machine Communications Technic(TC M2M) : developing an end-to-end architecture to support multipmachine type applications.

• The development of a ‘horizontal’ platform which is application-agnostic bits evolved functionality, is capable of supporting a very wide range of servsmart metering, eHealth, city automation, consumer applications and car aut

(ETSI Technical Report(TR) outlining potential ‘use cases’ in each of 5 areas )

• The standardization efforts in ITU are being addressed under various bannerof Things (IoT)’, ‘Machine to Machine (M2M) communication’, ‘Maccommunication (MOC)’, ‘Smart ubiquitous networks (SUN)’, ‘Ubiquitous se(USN)’, etc.

• The standardization in the direction of special handling or optimization of thM2M specific service will lead for better support of M2M communications.

http://www.businesscloudnews.com/files/2013/09/Machine-2-Machine.jpg



M2M firm Telit buys cloud platform ILS Technology

September 4, 2013 , Written by Jonathan Brandon

Telit is moving into the cloud-based M2M service provision space with its latestacquisition

In a bid to expand its service portfolio global machine-to-machine (M2M) provider

Telit today announced that it will be acquiring ILS Technology, a cloud-based back-end service provider, for $8.5m.

London-based Telit communications specializes in the development of wirelessM2M technology and claims to be a “one-stop-shop” for M2M connection modules

and managed services including connectivity.

http://www.businesscloudnews.com/author/jbrandon/



http://www.businesscloudnews.com/author/jbrandon/



Conclusion:

M2M as an application holds the promise of bringing benefit to bo

operators and vendors.

For service providers it is an opportunity as low-bandwidth servireadily overlaid onto the current user services network.

Vendors are expected to profit from selling both M2M-capable defrom the network expansion brought about by increased throughp

Most MNOs were late to the M2M table, may be because the ARPUs were very low cvoice and data traffic….

machine to machine - basics

Documents