Value of the M2M Connection

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

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

3. Architectural Shift: Network as IoT Application Services Platform Devices Gateway IoT Provider Cloud Field/Personal Area Network WAN EPC Enterprise Enterprise Application Enterprise Application Cloud Application Cloud Application Dist. Network Application Dist. Network Application Device Application Mca Mca Mcn Mcn Mcn Mcn Mca Mca Application Protocols Application Services Application Services REST, WS REST, WS MQTT, MQP, CoAP, XMPP Application Services Application Services MQTT, AMQP, CoAP, XMPP MQTT, AMQP, CoAP, XMPP Mcc Mcc Mcc Network Protocols IP IP IP Z-Wave, ZigBee, IP IP IP Z-Wave, ZigBee, IP Ethernet Ethernet MPLS / Ethernet 802.15.4 / Z-Wave / 802.11 / PLC / Bluetooth / NFC / Ethernet 802.11, Ethernet, 3G/LTE, FTTX 802.15.4 / Z-Wave / 802.11 / PLC / Bluetooth / NFC / Ethernet 802.11, Ethernet, 3G/LTE, FTTX PHY / Link Protocols • 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 oneM2M Model

4. 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 though From this: Data Network Awareness To this: Data * Power from battery may be sufficient with UEPCOP

5. Why not LTE

6. 3GPP MTCe Architectures • 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

7. Network State Examples • 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 • Provide ability for the application to subscribe to notifications • Mobility events • Location changes • Roaming status changes • Congestion status change • KPI threshold exceeds

8. 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

9. 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. 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. MTC Application Monitors the Location Device MTC application receives notification when normally fixed device is moved API

12. API Device Check • 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

13. 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. Network Connection Status Value • 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?