4.7 [5] Structure of M2M Consolidation

1. 4.7 [5] Structure of M2M Consolidation Brian Daly – Member of ATIS Delegation(AT&T Director, Core Network & Government/Regulatory Standards) Meeting of Potential M2M Consolidation Partners #2 August 17-18, 2011 Washington, DC M2MCons02_13r1

2. Goals for M2M Consolidation • Any M2M consolidation effort needs to be responsive to the needs of the stakeholders and the marketplace: • Vertical market stakeholders; • SDOs; and • Service providers (as previously defined) • Structure needs to be flexible and allow a natural evolution: • Needs to balance regional requirements and differences; • Needs to address timeframe objectives across the regions; • Needs to support global harmonization; • Needs to afford a level playing field for all stakeholders; and • Needs to be practical • less global travel; • practical resource commitment; and • address vertical players which may be more regionally focused and have resource or travel limitations for global participation.

3. Global Harmonization Initiative Structure Steering Committee Plenary Requirements & Use Case Harmonization Working Group Common Service Architecture & Protocol Working Group Security Aspects Working Group Test & Conformance Working Group Keep number of working groups manageable to minimize resource requirements

4. Details of the Structure • Steering Committee • Made up of a delegation from each SDO and key vertical market players • Defines the work scope & direction, tracks overall progress, resolves issues between regions/verticals • Plenary • Responsible for end-to-end view, overall technical project management & work plan, approval of work items, approval of specifications • Open to all members, but primarily comprised of working group leadership, delegations from regional SDOs, vertical market players • Handles liaisons/relationships to other industry fora

5. Details of the Structure – Working Groups • Requirements and Use Case Harmonization Working Group • Develops a common set of harmonized service layer use cases and requirements • Harmonizes use cases and requirements could be the most significant task of this entire initiative • First group to be formed • Common Service Architecture and Protocol Working Group • Develops a common service architecture that can meet the harmonized use cases and requirements • Develops or identifies protocols/enhancement to protocols to support the service architecture • Develops or identifies common objects to support services • Develops APIs to support service layer architecture • Liaisons to other groups as needed to identify adaptation layer requirements • Is started when the harmonized requirements & use cases are developed • Security Aspects Working Group • Develops common security architecture within the defined service layer architecture • Develops security services and protocols across the service layer • Testing and Conformance Working Group • Develops test and conformance specifications • Is started when the harmonized requirements & use cases and architecture are developed

6. Steps to Harmonization • Develop market-driven use cases & requirements taking into account regional vertical market and technical issues, regulatory factors, etc. • Input from: • Ongoing regional use case and requirements efforts • Existing standards already developed in the SDOs • Vertical market segment input • M2M Global Harmonization Initiative takes use cases & requirement input and develops/identifies a common set of harmonized service layer use cases and requirements • Development of the service architecture is based upon this harmonized view rather than driven by any regional-centric view • Once the harmonized use cases are identified, the Global Harmonization Initiative develops the architecture, protocols, APIs, etc., for the service layer

7. Define Use Cases and Requirements • The first step in defining a common service layer is to harmonize use cases and requirementsso that the level of commonality can be identified • This is possibly the most important step for ultimate technical success of M2M service layer consolidation • This work should be proceeding now in parallel with M2M consolidation structure discussions • Each region reaches out to vertical market segments within their region and develops use cases and requirements supporting M2M applications • Provides balance into requirements and use case development • Key is it includes vertical players from each region • Accounts for regional market drivers, regulatory aspects, etc. • Focus of this initial effort is to provide a regional view of use cases and requirements into the M2M global harmonization initiative

8. Responsive to Stakeholder Needs • One concern is there may be a considerable number of regional vertical market players that cannot (or will not) participate at the global level, for a variety of reasons • It is important for the verticals’ needs to be captured in ongoing work • To maximize opportunities that all voices are heard, the harmonization structure should include Regional Outreach as an integral part of the overall M2M global harmonization initiative structure • Driven by unique M2M ecosystem • Regional Standards Alignment Meeting held 2x per year by each SDO • Continued outreach to share overview of progress, technical discussions, and solicit input to be brought back into the global initiative • Reports back to both the Steering Committee and Plenary, and provides technical input to working groups as needed

9. Global Harmonization Initiative Structure Steering Committee Regional Outreach Plenary Requirements & Use Case Harmonization Working Group Common Service Architecture & Protocol Working Group Security Aspects Working Group Test & Conformance Working Group

10. Meetings • Steering Committee & Plenary • 3x per year rotated North America, EU and Asia • Major hub cities only • Working groups • Virtual meetings as needed • Face to face 4x per year • may or may not be at same time as steering committee and plenary • Regional Standards Alignment Meetings • 2x per year

11. Benefits of this Structure • Regional development of use cases and requirements can begin immediately in parallel with the formation of the Global Harmonization Initiative. • No lost time and the steps toward global harmonization are in motion • Provides balance into requirements and use case development. • Regional needs must be addressed anyway • Harmonizes the use cases and requirements across the regions into a common service layer view which an architecture can be built on. • Development of the service architecture is based upon this harmonized view rather than driven by any regional-centric view. • Regional Outreach component provides avenues for key stakeholders at regional level to remain involved.