Machine to Machine Communication (From ETSI/3GPP Aspect)

21
1 M2M : Machine to Machine Communication (From ETSI/3GPP Aspect) Tzu-Ming Lin [email protected] 2010/03/04

description

 

Transcript of Machine to Machine Communication (From ETSI/3GPP Aspect)

Page 1: Machine to Machine Communication (From ETSI/3GPP Aspect)

1

M2M : Machine to Machine Communication

(From ETSI/3GPP Aspect)

Tzu-Ming Lin

[email protected]

2010/03/04

Page 2: Machine to Machine Communication (From ETSI/3GPP Aspect)

2

Outlines

• Introduction

• M2M Application and Architecture

• M2M in 3GPP

• Summary

Page 3: Machine to Machine Communication (From ETSI/3GPP Aspect)

3

Introduction

• What is M2M?

– Machine-to-Machine (M2M) involves

communication without (or only limited) human

intervention

– The human is not the input, but only (optionally)

the out put

– Also named Machine Type Communication

(MTC) in 3GPP

Source: ETSI

Page 4: Machine to Machine Communication (From ETSI/3GPP Aspect)

4

Introduction

• M2M applications– Security

• Surveillance applications, alarms, people tracking

– Transportation• Fleet management, emission control, toll payment

– Health care• e-Health

– Utilities• Measurement, provisioning and billing of utilities, such as Oil,

and water

– Manufacturing• Production chain monitoring and automation

– Facility Management• Home / building / campus automation

Source: ETSI

Page 5: Machine to Machine Communication (From ETSI/3GPP Aspect)

5

M2M Application – Smart Metering

Source: ETSI

Page 6: Machine to Machine Communication (From ETSI/3GPP Aspect)

6

M2M Application – e-Health

Source: ETSI

Page 7: Machine to Machine Communication (From ETSI/3GPP Aspect)

7

Network Architecture

M2MGateway

ClientApplication

M2M ApplicationM2M Area Network

Service

Capabilities

M2MCore

Source: ETSI

Page 8: Machine to Machine Communication (From ETSI/3GPP Aspect)

8

Key Elements• M2M Device

– A device capable of replying to request for data contained within those device or capable of transmitting data contained within those devices autonomously

• M2M Area Network (Device Domain)– Provide connectivity between M2M Devices and M2M Gateways

– E.g. personal area network

• M2M Gateway– Use M2M capabilities to ensure M2M Devices inter-working and interconnection to

the communication network

• M2M Communication Networks (Network Domain)– Communications between the M2M Gateway(s) and M2M application

– E.g. xDSL, LTE, WiMAX, and WLAN

• M2M Applications – Contains the middleware layer where data goes through various application

services and is used by the specific business-processing engines

Source: ETSI

Page 9: Machine to Machine Communication (From ETSI/3GPP Aspect)

9

M2M in 3GPP – The Reason

• 3GPP has started the specification in 2010 for:

– Interoperable Solution

• Endure Interoperability

– Product Innovation

• Encourages innovation through R&D

– New Markets

• Expands markets

– Standards Solution

• Reduces cost

– Regulatory Requirements

• Satisfies essential regulatory requirement

Source: ETSI

Page 10: Machine to Machine Communication (From ETSI/3GPP Aspect)

10

M2M in 3GPP – Architecture

3GPP bearer services / SMS / IMS

MTCi

MTC Server

MTCu MTC

Device

MTCsms

MTC Server

• MTC : Machine Type Communication

• MTCu : provides MTC devices access to the 3GPP network for the transport of user traffic

• MTCi : the reference point for MTC server to connect the 3GPP network via 3GPP bearer service

• MTCsms : the reference point for MTC server to connect the 3GPP network via 3GPP SMS

Source: 3GPP TS 23.888

Page 11: Machine to Machine Communication (From ETSI/3GPP Aspect)

11

M2M in 3GPP – Scenario 1

API

Operator domainAPI

MTC Server MTC User

MTC Device

MTC Device

MTC Device

MTC Device

Communication scenario with MTC Devices communicating with MTC Server.

MTC Server is located in the operator domain

Source: 3GPP TS 22.368

Page 12: Machine to Machine Communication (From ETSI/3GPP Aspect)

12

M2M in 3GPP – Scenario 2

Operator domain

MTC Device

MTC Device

MTC Device

MTC Device

MTC Server/

MTC User

Communication scenario with MTC Devices communicating with MTC Server.

MTC Server is located outside the operator domain.

Source: 3GPP TS 22.368

Page 13: Machine to Machine Communication (From ETSI/3GPP Aspect)

13

M2M in 3GPP – Scenario 3

MTC Device

MTC Device

MTC Device

MTC Device

Operator domain A Operator domain B

MTC Device

MTC Device

MTC Device

MTC Device

MTC Devices communicating directly with each other

without intermediate MTC Server

Source: 3GPP TS 22.368

Page 14: Machine to Machine Communication (From ETSI/3GPP Aspect)

14

M2M in 3GPP - Features

• Low Mobility– MTC Devices that do not move, move infrequently, or move only

within a certain region

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

• Time Tolerant– Data transfer can be delayed

• Packet Switched (PS) only– Network operator shall provide PS service with or without an

MSISDN

• Online small Data Transmissions– MTC Devices frequently send or receive small amounts of data.

Source: 3GPP TS 22.368

Page 15: Machine to Machine Communication (From ETSI/3GPP Aspect)

15

M2M in 3GPP - Features

• MTC Monitoring– Not intend to prevent theft or vandalism but provide functionality

to detect the events

• Offline Indication– For detecting the condition when it is no longer possible to

establish signalling between the MTC Device and the network

• Jamming Indication– Require timely notification when an MTC Devices is being

jammed due to an intentional broadband interferer

• Priority Alarm Message (PAM)– For the need of immediate attention, e.g. theft or vandalism

Source: 3GPP TS 22.368

Page 16: Machine to Machine Communication (From ETSI/3GPP Aspect)

16

M2M in 3GPP - Features

• Extra Low Power Consumption– Improving the ability of the system to efficiently service MTC

applications

• Secure Connection– Convey communication when some of the devices are connected

via a roaming operator

• Location Specific Trigger– Intending to trigger MTC device in a particular area, e.g. wake up

the device

• Group based MTC Features– MTC device may be associated with one group

Source: 3GPP TS 22.368

Page 17: Machine to Machine Communication (From ETSI/3GPP Aspect)

17

End-to-End Security for

Roaming MTC Devices

Operator

domain

Operatordomain

Operator

domain

Operator

domainOperator

domain

Operator

domainOperator

domain

Operator

domain

MTCDevice

MTCDevice

MTC

Server

truste

ddom

ain

truste

ddom

ain

MTCDevice

MTCDevice

Source: 3GPP TS 22.368

Page 18: Machine to Machine Communication (From ETSI/3GPP Aspect)

18

Issues

• Access Agnostic– Data format of M2M applications

• Naming, Address and routing– Alternative addressing solution based on IP addresses should be

studies

• Service levels and QoS– New QoS profiles needs to be defined

• Security, authentication, data integrity, privacy– Security association shall be maintained between “machines”

• Interconnect and interworking– Inter-communication via RATs

Page 19: Machine to Machine Communication (From ETSI/3GPP Aspect)

19

Example of MTC Applications

Digital photo frame

Digital camera

eBook

Consumer Devices

Power

Gas

Water

Heating

Grid control

Industrial metering

Metering

Sensors

Lighting

Pumps

Valves

Elevator control

Vending machine control

Vehicle diagnostics

Remote Maintenance/Control

Monitoring vital signs

Supporting the aged or handicapped

Web Access Telemedicine points

Remote diagnostics

Health

Point of sales

Vending machines

Gaming machines

Payment

Fleet Management

Order Management

Pay as you drive

Asset Tracking

Navigation

Traffic information

Road tolling

Road traffic optimisation/steering

Tracking & Tracing

Surveillance systems

Backup for landline

Control of physical access (e.g. to buildings)

Car/driver security

Security

MTC applicationsService Area

Page 20: Machine to Machine Communication (From ETSI/3GPP Aspect)

20

Summary

• M2M/MTC has been proposed to– Provide network operators with lower operational costs when

offering machine-type communication services

– Reduce the impact and effort of handling large machine-type communication groups

– Optimize network operations to minimize impact on device batterypower usage

– Stimulate new machine-type communication applications by enabling operators to offer services tailored to machine-type communication requirements

• Some features and applications are also investigated and 3GPP has started the specification in early 2010

Page 21: Machine to Machine Communication (From ETSI/3GPP Aspect)

M2M

leads killer applications everywhere

Thank You