Value of the M 2 M Connection Can

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

Io. T Application Services Platforms Devices Gateway PHY / Link Network Application Protocols Field/Personal Area Network EPC WAN Z-Wave, Zig. Bee, IP IP 802. 15. 4 / Z-Wave 802. 11, / 802. 11 / PLC / Ethernet, Bluetooth / NFC / 3 G/LTE, Ethernet FTTX Enterprise Application MQTT, MQP, REST, Co. AP, XMPP WS MQTT, AMQP, Co. AP, XMPP 802. 15. 4 / Z-Wave / 802. 11 / PLC / Bluetooth / NFC / Ethernet Enterprise Cloud Application Device Application Z-Wave, Zig. Bee, IP Io. T Provider Cloud REST, WS IP IP 802. 11, Ethernet, 3 G/LTE, FTTX MPLS / Ethernet • Platform is OTT • Network is a Transport Pipe – only provides Connectivity © 2013 -2014 Cisco and/or its affiliates. All rights reserved. 2

Architectural Shift: Network as Io. T Application Services Platform Devices Gateway PHY / Link Network Application Protocols Field/Personal Area Network Dist. Network Application Device Application MQTT, AMQP, Co. AP, XMPP Z-Wave, Zig. Bee, IP 802. 15. 4 / Z-Wave / 802. 11 / PLC / Bluetooth / NFC / Ethernet • • MQTT, AMQP, Co. AP, XMPP Mca Mcc Application Services Z-Wave, Zig. Bee, IP Mcn IP 802. 15. 4 / Z-Wave 802. 11, / 802. 11 / PLC / Ethernet, Bluetooth / NFC / 3 G/LTE, Ethernet FTTX Dist. Network Application Mca Mcc Application Services Mcn Cloud Application MQTT, MQP, REST, Services Co. AP, XMPP WS Enterprise Mca Mcc Mcn Enterprise Application REST, WS Services IP IP 802. 11, Ethernet, 3 G/LTE, FTTX MPLS / Ethernet 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. © 2013 -2014 Cisco and/or its affiliates. All rights reserved. Io. T Provider Cloud WAN EPC Security via strict Access Rights management Cloud + Fog Model one. M 2 M Model 3

Why LTE for Io. T § 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 IPv 6 so as to scale to the Io. T. 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 Wi. Fi credentials of the backhaul router for Wi. Fi § 802. 11 u may help in the future though From this: Data To this: Network Awareness Data * Power from battery may be sufficient with UEPCOP © 2013 -2014 Cisco and/or its affiliates. All rights reserved. 4

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/3 G spectrum will be re-farmed SMS based application so 2 G is sufficient LTE is all IP and IPv 6 capable Wi-Fi is cheaper but is susceptible to interference LTE is licensed and spectrum is dedicated Battery Concern Devices can sleep © 2013 -2014 Cisco and/or its affiliates. All rights reserved. 5

3 GPP MTCe Architectures § SMS/Triggering delivery over T 4 defined § Small Data and Device Triggering Enhancements (SDDTE) § No agreement reached § Monitoring enhancements (MONTE) § Work item started in release 10, postponed to R 13. § UE Power Consumption Optimizations (UEPCOP) § Work item started in release 10, postponed to R 13. § Group based feature (GROUP) § Work item started in release 10, postponed to R 13. § SEES/AESE § New SID in SA 1/SA 2 for R 13. Architecture Enhancements for Service Exposure © 2013 -2014 Cisco and/or its affiliates. All rights reserved. 6

Network State Examples § Provide APIs for the M 2 M applications to query session / device data § Identity mapping § session info (APN, Qo. S, IMSI, PLMN), Session status (active/offline) § Roaming status § Location § SLA § Network congestion status § Provide ability for the application to subscribe to notifications § Mobility events § Location changes § Roaming status changes § Congestion status change § KPI threshold exceeds © 2013 -2014 Cisco and/or its affiliates. All rights reserved. 7

GSMA one. API § The GSMA one. API is the 3 GPP method to expose network function to 3 rd parties. § The following capabilities are supported in version 3 of the one. API 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 M 2 M applications § 3 GPP R 13 SEES/AESE work looking at OMA and GSMA platforms © 2013 -2014 Cisco and/or its affiliates. All rights reserved. 8

MONTE Framework • SCS/AS (M 2 M Application) subscribes to service provider for device events • API GW decides which network element to install triggers to report the event © 2013 -2014 Cisco and/or its affiliates. All rights reserved. 9

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 SCEF can be employed © 2013 -2014 Cisco and/or its affiliates. All rights reserved. 10

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

Device Check § Why Ping when a TAU is nearly the same § M 2 M server makes simple request to report when devices do not report in § API GW installs the subscription for TAU reports for this M 2 M customer § MME reports successful TAUs § API GW determines that after the TAU timer, one is missing and reports to M 2 M server © 2013 -2014 Cisco and/or its affiliates. All rights reserved. 12

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

Network Connection Status Value § 3 GPP, 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 M 2 M applications need from their connection to the Internet? © 2013 -2014 Cisco and/or its affiliates. All rights reserved. 14

Thank you.