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

2 © Cisco and/or its affiliates. All rights reserved. IoT Application Services Platforms Devices Gateway / Z-Wave / / PLC / Bluetooth / NFC / Ethernet Z-Wave, ZigBee, IP MQTT, AMQP, CoAP, XMPP , Ethernet, 3G/LTE, FTTX IP MPLS / Ethernet IP Ethernet IP MQTT, MQP, CoAP, XMPP PHY / Link Protocols Network Protocols Application Protocols Device Application Cloud Application IP , Ethernet, 3G/LTE, FTTX / Z-Wave / / PLC / Bluetooth / NFC / Ethernet Z-Wave, ZigBee, IP Platform is OTT Network is a Transport Pipe – only provides Connectivity WAN EPC Field/Personal Area Network REST, WS Ethernet IP Enterprise Application REST, WS IoT Provider Cloud Enterprise

3 © Cisco and/or its affiliates. All rights reserved. Architectural Shift: Network as IoT Application Services Platform Devices Gateway / Z-Wave / / PLC / Bluetooth / NFC / Ethernet Z-Wave, ZigBee, IP MQTT, AMQP, CoAP, XMPP , Ethernet, 3G/LTE, FTTX IP MPLS / Ethernet IP Ethernet IP MQTT, MQP, CoAP, XMPP PHY / Link Protocols Network Protocols Application Protocols Device Application Cloud Application IP , Ethernet, 3G/LTE, FTTX / Z-Wave / / PLC / Bluetooth / NFC / Ethernet Z-Wave, ZigBee, IP Network as Global Data Space Service + Transport Integration, Security Devices push data into the Global Data Space. Applications extract data via pull or push model. Security via strict Access Rights management Cloud + Fog Model WAN EPC Field/Personal Area Network REST, WS Ethernet IP Enterprise Application REST, WS IoT Provider Cloud Enterprise Cloud Application Application Services Dist. Network Application Enterprise Application Application Services MQTT, AMQP, CoAP, XMPP Mca Mcc Mcn Mca Mcn Mcc oneM2M Model

4 © Cisco and/or its affiliates. All rights reserved. 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  u may help in the future though From this: To this: Data Network Awareness * Power from battery may be sufficient with UEPCOP

5 © Cisco and/or its affiliates. All rights reserved. Why not LTE ChallengeSolution Cost of a connection is significantReduce the session footprint, increase the value the connection offers LTE is not pervasiveOperators may have national coverage but what about international Chip sets are expensiveTrue but coming down and LTE is the future, 2/3G spectrum will be re-farmed SMS based application so 2G is sufficientLTE is all IP and IPv6 capable Wi-Fi is cheaper but is susceptible to interference LTE is licensed and spectrum is dedicated Battery ConcernDevices can sleep ChallengeSolution Cost of a connection is significantReduce the session footprint, increase the value the connection offers LTE is not pervasiveOperators may have national coverage but what about international Chip sets are expensiveTrue but coming down and LTE is the future, 2/3G spectrum will be re-farmed SMS based application so 2G is sufficientLTE is all IP and IPv6 capable Wi-Fi is cheaper but is susceptible to interference LTE is licensed and spectrum is dedicated Battery ConcernDevices can sleep

6 © Cisco and/or its affiliates. All rights reserved.  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

7 © Cisco and/or its affiliates. All rights reserved.  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

8 © Cisco and/or its affiliates. All rights reserved. GSMA oneAPI  The GSMA oneAPI is the 3GPP method to expose network function to 3 rd parties.  The following capabilities are supported in version 3 of the oneAPI specifications:  Location Location  SMS SMS  MMS MMS  Payment Payment  Device Capability Device Capability  Data Connection Profile Data Connection Profile  Third Party Call Third Party Call  Anonymous Customer Reference 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

9 © Cisco and/or its affiliates. All rights reserved. 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

10 © Cisco and/or its affiliates. All rights reserved. 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

11 © Cisco and/or its affiliates. All rights reserved. MTC Application Monitors the Location Device MTC application receives notification when normally fixed device is moved API

12 © Cisco and/or its affiliates. All rights reserved.  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 Check API

13 © Cisco and/or its affiliates. All rights reserved. MTC Application Delays Sending Data MTC application delays sending data until device becomes active Details: MTC application registers to be notified when device activates. Once device active sends data. API

14 © Cisco and/or its affiliates. All rights reserved.  3GPP, OMA, GSMA, Services Providers and vendors are designing solutions to expose network state to 3 rd parties  Exposure layer simplifies the implementation to 3 rd 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.