ATIS Machine-to-Machine Focus Group (M2M-FG)

1. ATIS Machine-to-Machine Focus Group (M2M-FG) Gale Lightfoot M2M Focus Group Co-Chair • Senior Staff Program Manager • Office of the CTO, SPB • Cisco

2. ATIS M2M Mission Advance the capability of M2M services through technology development that will: • Enable supplier interoperability; • Support the monitization of services; • Reduce operating and capital expenses; • Improve time-to-market; • Enable mass-market economies of scale; and • Deliver a quality user experience.

3. ATIS M2M Initiative:Opportunities and Benefits Opportunities • Solutions are currently unique to each industry. • Potential for telecommunications providers to enhance services. • Potential to guide required M2M standards development. Benefits • Boost economies of scale. • Shorten time-to-market. • Simplify development of applications. • Expand business opportunities. • Reduce standardization overlap.

4. Why is the interest in this FG so high? • The revenue opportunity is enormous. • Forecasted >15B Connected Devices by 2015; >50B by 2020! • Analysts, academics, journalists, not to mention service providers are all talking about M2M. • Subscriber saturation in the U.S. has occurred. There are now more mobile subscriptions than U.S. residents. • Machines and sensors represent the clearest way for mobile revenue and services to grow. • Many telemetry applications do not use much bandwidth. • Attraction is similar to short message service: high margins, low bandwidth consumption. • Industrial and other specialized M2M applications will be more churn resistant than traditional “man” vs. machine subscribers.

5. Participation • Co-Chaired by Jeff Edlund, HP, and Gale Lightfoot, Cisco. • 20 participating companies: AT&T ADTRAN Alcatel-Lucent Cisco Ericsson Hitachi Hewlett-Packard Huawei Intel Juniper LG Motorola Nokia Siemens Networks Qualcomm Sprint SureWest Syniverse Telephone & Data Systems Telcordia Verizon

6. Verticals S M A R T G R I D C O N N E C T E D V E H I C L E eHealth Landscape Team M2M-FG Vertical Specific APIs M2M Core Needs M2M Common ICT Services for Verticals

7. Working Objectives • The M2M-FG addresses the M2M, Smart Grid, and Connected Vehicle opportunities identified by the Landscape Team. • The FG is currently assessing: • In depth Use Case Analysis for Smart Grid and Connected Vehicle: • Intent to tease out specific features / functions required for ICT to support use cases; and • Hypothesis is that multiple use cases will need many COMMON feature / functions and parameters supporting a common service platform for M2M. • Architectural definition for M2M Service Platform. • Identification of players across the value chain.

8. M2M Value Chain System Integrator Service Provider Machine Module Middleware Network End User Customer Service Modem Enablers mgmt App’s Gateway Transport IC Sensor Service Operations Integration Middleware Providers Service Providers Network Equipment Providers Machine & Device Manufacturers System Integrators Application Developers

9. Connected Vehicle Sub-Team • Completed assessment of selected use cases that appear to provide significant commercial opportunities within the ITS sector. • Analysis determines how ICT communications could be leveraged within various use cases and considers the advantages and challenges associated with utilizing commercial communication services. • Initial use cases sourced from U.S. DOT, BII, DMA, AERIS, ETSI and ATIS Landscape information. • Assessed industry architectural frameworks and currently comparing the different frameworks in order to determine what is most applicable. • Sub-team will analyze the status of standards related to the use cases and will highlight standards needs to address the use cases.

10. Connected Vehicle Sub-TeamUse Cases • Data for travel issues (congestion, bad weather, bad roads, etc.) • Location-based data on nearby gas, lodging, alternative fuel locations, etc. • Information to synchronize traffic light patterns to optimize traffic flow • Data from vehicles to better plan roads and how to balance traffic • Electronic toll collection • Electronic Payments • Charging vehicle from a charging station at someone else’s home • Charging vehicle from a public charging station • Collecting diagnostic information and informing when a repair is needed • SOS Services/911

11. Smart Grid Sub-Team • Completed assessment of selected uses cases that are relevant to the transmission of the Smart Meter data and focused on key actors in the consumer domain. • Initial use cases were selected based on SGIP use case work already completed (1400+ observed). • Assessed industry architectural frameworks and currently comparing the different frameworks in order to determine what is most applicable. • Sub-team will analyze the status of standards related to the use cases and will highlight standards needs to address the use cases.

12. Smart Grid Use Cases • Meter Reading • Meter Events • EV/PHEV (Electric Vehicles/Plug-in Hybrid Electric Vehicles) • Pre-Pay • DR/DLC (Demand Response/Demand Load Control) • Premise Network Admin • Service Switch • Firmware/Program Update

13. Common Service Functions/Capabilities • FG is identifying common service functions across the different use cases of M2M, following prior work on individual use cases. • Recognized that the current status of M2M is that the application usually incorporates an application specific service layer function within it and these functions many times are duplicated across different M2M applications. • There can be substantial benefit from creating a common service layer in the network that provides functions and/or capabilities that are common across multiple M2M applications. • The FG will outline some of the common functions/capabilities that are required for most M2M applications, in particular, the Smart Grid and Connected Vehicle use cases.

14. Common Service Functions/Capabilities (cont’d) • Service Layer Functionality where commonalities may be identified: • Provisioning • Device Management • Configuration Management • Firmware Management • Device Application Software Management • Authentication and Registration • Device Triggering • Device Communication • Group Management for Communication • QoS • Policy Management • Data Processing and Storage • Notifications • Diagnostics • API Management • Billing

15. Common Service Functions; Business Needs • Having a common service layer simplifies application development allowing the application developer to focus on the application rather than the communication and management of devices. • According to the Beecham report, the value for such a service layer is several 10s of billions of dollars.

16. Focus Group Value to ATIS Members • Identifying the commonalities across the M2M verticals which no other standards bodies are addressing. • Opportunity to define ICT’s contribution and role in these emerging markets. • The mobility aspect of M2M, Connected Vehicle, & Smart Grid makes ICT’s role critical. • LTE will be a significant enabler. • M2M value-added services remain a relatively untapped market for ICT. • Definition of service catalogs for quick discovery & activation of revenue generating services. • Changing Business Paradigms

17. Next Steps The Focus Group will: • Finalize identification of commonalities across the verticals. • Identify standards needs along with APIs and protocols. Contact Gale Lightfoot for further details: lightfg@cisco.com