September 2014 Value of the M2M Connection Can LTE Networks be of Value to M2M Applications?

September 2014

Value of the M2M ConnectionCan LTE Networks be of Value to M2M Applications?

2© 2013-2014 Cisco and/or its affiliates. All rights reserved.

IoT Application Services Platforms Devices

Gateway

802.15.4 / Z-Wave / 802.11 / PLC / Bluetooth / NFC / Ethernet

Z-Wave, ZigBee, IP

MQTT, AMQP, CoAP, XMPP

802.11, Ethernet, 3G/LTE,

FTTX

IP

MPLS / Ethernet

IP

Ethernet

IP

MQTT, MQP, CoAP, XMPP

PH

Y /

Li

nk

Pro

toco

ls

Netw

ork

Pro

toco

lsA

pp

licati

on

Pro

toco

ls

Device Applicati

on

Cloud Applicati

on

IP


FTTX


Z-Wave, ZigBee, IP

• Platform is OTT• Network is a Transport Pipe – only provides

Connectivity

WANEPCField/Personal Area Network

REST, WS

Ethernet

IP

Enterprise Application

REST, WS

IoT Provider Cloud Enterpris

e


Architectural Shift: Network as IoT Application Services Platform

DevicesGateway


Z-Wave, ZigBee, IP



FTTX

IP

MPLS / Ethernet

IP

Ethernet

IP

MQTT, MQP, CoAP, XMPP

PH

Y /

Li

nk

Pro

toco

ls

Netw

ork

Pro

toco

lsA

pp

licati

on

Pro

toco

ls

Device Applicati

on

Cloud Applicati

on

IP


FTTX


Z-Wave, ZigBee, IP

WANEPCField/Personal Area Network

REST, WS

Ethernet

IP


REST, WS

IoT Provider Cloud Enterpris

e

Cloud Application

Application Services

Application Services

Application

Services

Dist. Network Applicati

on

Dist. Network Applicati

on


Application

Services


Mca McaMca

Mcc Mcc

McnMcn Mcn

Mca

Mcn

Mcc

oneM2M Model


Why LTE for IoT

By using LTE as the connection: CPE can be installed virtually

anywhere As long as have coverage and power*

Other benefits : IP addressing can be IPv6 so as to

scale to the IoT. Power to the CPE can be confirmed

simply through radio signaling Security of the radio link is inherent LTE is IP based and can scale to

billions of devices Last mile connection loss is not a

concern

LTE removes major network challenges: No need to punch holes through

firewalls for the protocols that could change on a regular basis

No need to have a NAT keep alive No need for IPSec or SSL for security No need for Ethernet to be wired to the

CPE No need to configure the WiFi

credentials of the backhaul router for WiFi 802.11u may help in the future thoughFrom this:

To this:

Data

Data

Network Awareness

* Power from battery may be sufficient with UEPCOP


Why not LTE

Challenge Solution

Cost of a connection is significant Reduce the session footprint, increase the value the connection offers

LTE is not pervasive Operators may have national coverage but what about international

Chip sets are expensive True but coming down and LTE is the future, 2/3G spectrum will be re-farmed

SMS based application so 2G is sufficient

LTE is all IP and IPv6 capable

Wi-Fi is cheaper but is susceptible to interference

LTE is licensed and spectrum is dedicated

Battery Concern Devices can sleep

Challenge Solution

Cost of a connection is significant Reduce the session footprint, increase the value the connection offers

LTE is not pervasive Operators may have national coverage but what about international

Chip sets are expensive True but coming down and LTE is the future, 2/3G spectrum will be re-farmed

SMS based application so 2G is sufficient

LTE is all IP and IPv6 capable

Wi-Fi is cheaper but is susceptible to interference

LTE is licensed and spectrum is dedicated

Battery Concern Devices can sleep


SMS/Triggering delivery over T4 defined

Small Data and Device Triggering Enhancements (SDDTE) No agreement reached

Monitoring enhancements (MONTE) Work item started in release 10, postponed to R13.

UE Power Consumption Optimizations (UEPCOP) Work item started in release 10, postponed to R13.

Group based feature (GROUP) Work item started in release 10, postponed to R13.

SEES/AESE New SID in SA1/SA2 for R13. Architecture

Enhancements for Service Exposure

3GPP MTCe Architectures


Provide APIs for the M2M applications to query session / device data Identity mapping session info (APN, QoS, IMSI, PLMN), Session status (active/offline) Roaming status Location SLA Network congestion status

Network State Examples

Provide ability for the application to subscribe to notifications Mobility events Location changes Roaming status changes Congestion status change KPI threshold exceeds


GSMA oneAPI

The GSMA oneAPI is the 3GPP method to expose network function to 3rd parties. The following capabilities are supported in version 3 of the oneAPI specifications:

Location

SMS

MMS

Payment

Device Capability

Data Connection Profile

Third Party Call

Anonymous Customer Reference

REST based with the option to subscribe to notifications Some operators advertised as using the framework Use cases may not be appropriate for bulk M2M applications 3GPP R13 SEES/AESE work looking at OMA and GSMA platforms


MONTE Framework• SCS/AS (M2M

Application) subscribes to service provider for device events

• API GW decides which network element to install triggers to report the event


Architecture Enhancements for Service Exposure Change “exposure layer”

to SCEF

Adds description of “Abstraction” along w/ other minor changes

Adds an example by way of SMS to show how SCEF can be employed

SCEF

SMS Capability Exposure

3rd partyApplication

SMS oneAPIOMA/GSMA

SMS-SC/GMSC/IWMSC

3GPP

OPER

ATOR

DOM

AIN

SMS Abstraction

E.g. Tsms,

T4


MTC Application Monitors the Location DeviceMTC application receives notification when normally fixed device is moved

API


Why Ping when a TAU is nearly the same

M2M server makes simple request to report when devices do not report in

API GW installs the subscription for TAU reports for this M2M customer

MME reports successful TAUs

API GW determines that after the TAU timer, one is missing and reports to M2M server

Device CheckAPIAPI


MTC Application Delays Sending DataMTC application delays sending data until device becomes active

Details: MTC application registers to be notified when device activates. Once device active sends data.

API


3GPP, OMA, GSMA, Services Providers and vendors are designing solutions to expose network state to 3rd parties

Exposure layer simplifies the implementation to 3rd parties

However adds complexity (cost) to SP’s

Is the cost/benefit there?

Network SLA and protection sufficient?

Are there sufficient use cases that need awareness?

What will M2M applications need from their connection to the Internet?

Network Connection Status Value

Thank you.

Documents

September 2014 Value of the M2M Connection Can LTE Networks be of Value to M2M Applications?