1. Work Group / Work Item Proposal Slide 1 © 2012 oneM2M Partners oneM2M-TP-2012-0007-oneM2M_Work_Group_Work_Item_Proposal Group name: Technical Plenary Source: Philip Jacobs, Cisco Systems, phjacobs@cisco.com Source: Laurent Laporte, Sprint, Laurent.Laporte@sprint.com Source: Joe Lenart, Hitachi, Joe.Lenart@hitachi-cta.comJoe.Lenart@hitachi-cta.com Source: Jianrong Wang, AT&T, jw8065@att.comjw8065@att.com Source: Josef Blanz, Qualcomm, jblanz@qualcomm.comjblanz@qualcomm.com Meeting Date: Agenda Items: 7.4 and 7.5 Intended purpose of document: Decision Discussion Information Other

2. Purpose A vision of where oneM2M is heading will better align the direction of partners A draft work group plan will provide a roadmap of how to better reach the destination – Flexible to include unforeseen work items – Reduces unaligned contributions

3. Working Group Sub Topics Industry Requirements WG (1) Use Cases ECO-system context Requirements Arch WG (2) Architecture Evolution plan Data modeling Reference points Protocols WG (3) APIs and messages Message data structures Service data structures Inter-working Implementation guidelines Implementation examples Reference Design Protocols Procedures O&M WG (4) Provisioning and Discovery Device Management Security and Privacy WG (5) Security Framework Threat Assessment Proposed Working Groups

4. Aligned to oneM2M Partnership scope definitions: Use cases and requirements for a common set of Service Layer capabilities Common use cases, terminal/module aspects, including Service Layer interfaces/APIs between: 1.Application and Service Layers 2.Service Layer and communication functions Sub-topic scope: Use cases – Describes the interactions between actors (existing outside of the M2M system) and the M2M system as a sequence of steps to achieve a goal. Ecosystem context – Describes how the M2M system is expected to fit together with selected vertical eco-systems, including all non-M2M system components required to deploy a complete solution. Requirements – Specifies what the M2M system is needed to do at architectural and functional levels. Requirements are derived from use cases, prioritized, and used as a basis for coverage analysis for architectural and functional specifications. Functions include inter-working, etc. Working Group 1 – Industry Requirements

5. Working Group 2 – Architecture Aligned to oneM2M Partnership scope definitions: Service Layer aspects with high level and detailed service architecture, in light of an access independent view of end-to-end services Information models and data management (including store and subscribe/notify functionality) Implementation aspects (missing from Partnership scope) Sub-topic scope: Architecture – Specifies the M2M functional architecture, including the identification of the functional entities and the related reference points (inter- working, etc.). Evolution Plan – Describes the architectural steps that existing selected vertical M2M solutions are expected to take to migrate to use oneM2M components in their solution. Data modeling – Specifies the information/data model. Reference Points – Specifies the information that crosses the reference points.

6. Working Group 3 – Protocols Aligned to oneM2M Partnership scope definitions: Protocols/APIs/standard objects based on this architecture (open interfaces & protocols) Information models and data management (including store and subscribe/notify functionality) Interoperability, including test and conformance specifications Implementation aspects (missing from Partnership scope) Common use cases, terminal/module aspects, including Service Layer interfaces/APIs between: 1.Application and Service Layers 2.Service Layer and communication functions Sub-topic scope: APIs and Messages – Specifies and describes APIs and message flows oneM2M interface protocols – Specifies interfaces and message flows internal to oneM2M Message data structures – Specifies the structure of each message Service data structures – Specifies data structures for each service Procedures – Specifies the functional flows of the M2M system under normal and abnormal situations Inter-working – describes how the oneM2M standard works together with – other standards (e.g. 3GPP/2, Wi-Fi, Zigbee, KNX, oBIX) – profiles of standards (e.g. Continua Health Alliance) – deployed solutions Implementation guidelines – provides technical comparisons of options and suggests which ones be considered for different type of vertical use cases Implementation examples – contains detailed examples of vertical use case scenarios using data structures and messages to validate specifications and guide implementers Reference Design – contains the essential elements of the system, one choice among each options is selected to produce a system which can be enhanced as required and enables faster time to market

7. Aligned to oneM2M Partnership scope definitions: Management aspects (including remote management of entities) Reachability and discovery of applications Identification and naming of devices and applications Sub-topic scope: Provisioning and Discovery – Specifies how the M2M system is provisioned and how the provisioned information is then discovered by M2M entities. Device Management – Specifies how the life cycle of M2M entities is managed Working Group 4 – O&M

8. Aligned to oneM2M Partnership scope definitions: Security and privacy aspects (authentication, encryption, integrity verification) Sub-topic scope: Security and Privacy Framework – Specifies how authentication, confidentiality, integrity, privacy and non-repudiation are to work in an end-to-end framework in the oneM2M system Threat Assessment - Evaluates the credibility and seriousness of a threat and the likelihood that it will be carried out Working Group 5 – Security and Privacy

9. Proposals 1.The Technical Plenary should consider the creation of the five Working Groups and their associated scope/terms of reference 2.The Working Groups should consider creation of work Items aligned with the sub-topics