1. CDMA Standards Update M2M Small Group Discussion: CONVERGENCE LAYER CONCEPTS Orlett W. Pearson January 2012

2. Introduction and Objective Attendance: – Orlett W. Pearson, Omar Elloumi (Alcatel-Lucent) – Peter Nurse (Sigma Delta), – Josef Blanz (Qualcomm) – Mitch Tseng (Tseng InfoServ) Objective: – Discussion on M2M Convergence Layer – Joint activity between ETSI TC M2M and TR-50

3. Convergence (initial concepts) – Network Access (IP based) Access Technologies – TR-50 would issue a connect – Need to define a set of core primitives » QoS » Selection of Network – configure policies/protocol which would use as an indication for establishing a connection Service Class QoS Network Incentive Bearer Selection (WiFi, LTE, cdma, etc) » TC IP Protocol Stack and Network Driver Pre-configure device management Application is not aware Network Driver would be aware based on primitives

4. Convergence (initial concepts) – Standard Execution Environment Common platform (API) – Client Application – M2M (or MTC SP) Service Platform Ask Core Network to trigger the device Establish Network bearer – Think About Practical Use Cases Device based triggering – Establish Network Activity – Measurements Network based triggering – Network applications to trigger device to perform M2M Activity – Additional issues Latency QoS Translation across different networks

5. Convergence – Team with Verticals Develop liaison relationship with eHealth, Automotive, Industrial, Utility Organizations Via a liaison relationship, could possibly – Obtain recommendations from organizations such as the Continual Health Alliance and the World Health Organization. – Turn recommendations into requirements for Convergence Reach out to other industry (M2M Conference held in ATL) – Consider practical features/requirements Store and forward – Consider tolerable delay, behavior, policy Other general requirements – Work with ETSI TC M2M Functional Architecture

6. CONVERGENCE Use Cases

7. Convergence (use cases) – Convergence – Use Cases Scenario 1: A service provider wants an interface between all supported technologies on a platform and wants these technologies to operate as seamless connectivity. Solution : Allow for operational efficiency on a converged M2M network by developing a set of common parameters for access technologies. This would allow for handoffs between technologies or it would allow the device to connect to the strongest signal. Allow for better management of operations. Scenario 2: The Convergence Layer has to communicate with other Access Technologies by defined transport protocols. Solution: The Convergence Layer has to define a single or multiples protocols to interact with other access technologies. This single/multiple protocol record would contain the bear method (e.g., cmda, LTE, WiMAX, etc.) In the defined set of protocols, an ACCESS_TECH_ID and QoS could be used when establishing an initial interface. 7

8. Convergence (use cases) – Convergence - Use Cases Scenario 3: Device to establish a trigger to obtain information that will be sent to gas company for usage and billing records Solution: Device (sensor or meter) establishes connectivity, capture data which is an online event (temperature, electrical resources), connects to the bearer (e.g., a given technology) at the transport layer. The bearer connects to the application where data is translated and sent to the gas company. 8

9. Moving Forward – Joint Work between TR-50 and ETSI TC M2M Progress in parallel Cross-reference documents Watch for overlapping work Ensure compatibility with other SDOs (China, Japan, etc.) – Next Small Group meeting February 2012 (Date: TBD)