1. Work for the next release Group Name: TP Source: JaeSeung Song, KETI, jssong@sejong.ac.kr; Jaeho Kim, KETI, jhkim@keti.re.kr;jssong@sejong.ac.krjhkim@keti.re.kr Snagho Choi, SK Telecom, sangho.choi@sk.com;sangho.choi@sk.com Michael hs. Yang, LG uplus, hsyang@lguplus.co.kr;hsyang@lguplus.co.kr Jungsoo Park, ETRI, pjs@etri.re.kr;pjs@etri.re.kr Jaeho Han, nTels, hanlux@ntels.com;hanlux@ntels.com Kyunggeun Kim, KCA, relmk3@kca.kr;relmk3@kca.kr Hong Soo Yoon, Kaonmedia, hsyoon@kaonmedia.com;hsyoon@kaonmedia.com Meeting Date: 2014-06-09 Agenda Item: Discussion TP-2014-0429R01-Home_domain_work_for_the_next_release

2. Some Voices from the Markets Will oneM2M release specifications soon? YES Will oneM2M standard specs. can be used in a specific vertical? (e.g., Home Automation) ??? What should we do if we have some features that need to be standardized? ??? When oneM2M will start work for the next release? ???

3. Purpose Stimulate discussion on work for the next release. – What should we do? – Which work items we require? – When actually should we (WG1) start? – How various verticals can be involved? Decide a way forward to convince IoT/M2M related markets that oneM2M will keep standardizing and delivering various standard specifications on the following aspects: – Functions optimizing the first release; – Advanced/Enhanced features; – Functions for verticals

4. Why Home domain? One of main IoT/M2M verticals. Many home appliance vendors have already started to launch IoT/M2M services based on their own platform. ETSI Smart M2M is now working on defining ontology for home appliance energy efficiency. The MAS group handles many semantic issues on the Home domain. The MAS group may study defining ontology for a specific domain and analyse how ontology from a specific vertical can be used in oneM2M  likely the Home domain

5. Are there many missing features? We don’t know yet. But we also don’t know our release 1 specification is enough to be used in a vertical system? Here are some example use cases that possible can be discussed: – Device paring – Caching temporarily unused devices – Detection of inconsistencies – Device and Gateway replacement

6. Some Use Cases (1) – Paired devices IoT/M2M system CSEBase Node2 Node1 Refrigerator (Node 1) Smart plug for Refrigerator (Node 2) Application Others.. Application Others.. Data for the sam e device (i.e., ref rigerator) but fro m the two differ ent devices. Better to manag e these devices a s a single device. Data for the sam e device (i.e., ref rigerator) but fro m the two differ ent devices. Better to manag e these devices a s a single device.

7. Some Use Cases (2) – Device caching CSEBase Application 2 (device 2) Application 1 Node 2 (device 2) SUMMER Application 2 (device 2) Node 1 (device 1) Resource bin Application 2 (device 2) Node 2 (device 2) Application 2 (device 2) WINTER

8. Some Use Cases (3) – Consistency t=0 t=10 IoT/M2M system CSEBase Node2 Node1 Application Others.. Application Others.. Node3 Application Others..

9. Some Use Cases (4) – Replacement Replace because of low battery Replace gateway because a user finds a better one Siren Gateway

10. Proposal Select the Home Automation and Control domain as a target vertical that will be studies and standardized in the upcoming oneM2M release: – WG1: standardizes uses cases and requirements specifically related to Home Automation and Control – WG2: standardizes architecture aspect supporting the home related requirements – WG3: standardizes protocol specifications – WG4: studies and analyses necessary security mechanisms if existing security features are not enough – WG5: standardizes ontology and semantics for Home Appliances and Energy management

11. Proposal (Cont.) How to progress? Options: – Option 1: Create an umbrella vertical work item covering multiple working groups (preferred) – Option 2: Use existing WI (TRes & TSes) – Option 3: Create individual work items once they are required.