1. HGI activities transfer to oneM2M Group Name: MAS Source: Patricia MARTIGNE (Orange), Deutsche Telekom, Telecom Italia Meeting Date: 2015-07-20 Agenda Item: Abstraction & Semantics

2. Topic Summary oneM2M PT2 HGI has announced its closure by June 2016 HGI Smart Home activities are already considered by oneM2M It is proposed to pursue some of the HGI Smart Home activities within oneM2M This contribution provides oneM2M WG5 with details to clarify the meaning of this proposed action. opinion and approval from oneM2M TP is seeked on the proposed actions. 2 © 2015 oneM2M Partners MAS-2015-0599-HGI_activities_transfer_to_oneM2M_WG5

3. Status of HGI Smart Home activities of interest for oneM2M 3 HGI DeliverablesRelation to oneM2MStatus of HGI deliverable HGI-RWD036 SH Architecture 1. Abstraction layerunder finalization… 2. Reference Points, APIs …publication : Q3-2015 SDT Smart Device Template 3. Home Domain Abstract Information Model SDT 2.0 available on GitHub; SDT 3.0 planned for Nov. ‘15 © 2015 oneM2M Partners MAS-2015-0599-HGI_activities_transfer_to_oneM2M_WG5

4. oneM2M WG5 & Smart Home related items Generic  TS-0002 Requirements (WG1 lead)  TS-0001 Functional Architecture (WG2 lead)  TS-0004 oneM2M Core protocol (WG3 lead)  TR-0007 Abstraction & Semantic (WG5 lead) Smart Home domain  TR-0013 Home Domain enablement (WG1 lead)  TR-0017 Home Information Abstract Model (WG5 lead) // is expected to be followed by a new TS for a normative Home abstract info model // oneM2M ontology, includes mapping to SAREF (Smart Appliances Reference ontology)  TS-0012 oneM2M Ontology (WG5 lead) 4 © 2015 oneM2M Partners MAS-2015-0599-HGI_activities_transfer_to_oneM2M_WG5

5. TS-0002 Requirements Release2 (v2.1.0)  Functional Requirements Overall System Requirements Management Requirements Semantics Requirements Security Requirements Charging Requirements Operational Requirements Communication Management Requirements LWM2M Interworking Requirements 5 TS-0002 Requirements versus HGI RWD- 036 Requirements © 2015 oneM2M Partners MAS-2015-0599-HGI_activities_transfer_to_oneM2M_WG5

6. TS-0001 Architecture Release2 6 resource type vs « grouping » under discussion in HGI RWD- 036 semantic-related aspects: SDT, SAREF. To be tested against a SH use case © 2015 oneM2M Partners MAS-2015-0599-HGI_activities_transfer_to_oneM2M_WG5

7. HGI RWD-036 Smart Home architecture Main items for oneM2M: Device abstraction layer – refered to in TR-0007 §6.2.2 – provides common, HAN technology agnostic, representations of appliances – SDT is part of the abstraction objective. Refered to in TR-0017 §5.1.3 HGI Ref.Points correspondance with oneM2M – RP4 versus oneM2M Mcc – RP7 versus oneM2M Mca -> check against TS-0002 & TS-0004 7 © 2015 oneM2M Partners MAS-2015-0599-HGI_activities_transfer_to_oneM2M_WG5

8. New HGI SDT 3.0 (draft) 8 © 2015 oneM2M Partners MAS-2015-0599-HGI_activities_transfer_to_oneM2M_WG5

9. Between TP18 and TP19 TP18 discuss the way forward related to HGI closure have a look at the GitHub public repository for the SDT propose dates for calls with HGI SHTF July & August 1 joint call related to SDT 1 joint call related to RWD036 SH Architecture TP19 see next slide 9 © 2015 oneM2M Partners MAS-2015-0599-HGI_activities_transfer_to_oneM2M_WG5

10. Suggested roadmap from TP19 oneM2M TP19 07-11/09 investigate SDT vs TS- Abstract InfoModel; feedback to HGI Rqrts from RD036; possible CRs to TS- 0002 Rqrts oneM2M TP20 09-13/11 SDT into TS oneM2M proposed modifs to SDT? any RD036-based CRs to TS-0001 Archi oneM2M Mca and Mcc vs RD036-based rqrts? oneM2M TP21 18-22/01 oneM2M vs SDT maintenance process? 10 Q3-2015Q4-2015Q1-2016 HGI 28/09-1/10. Decision SDT 3.. Publish RD036 >> RD036 input to oneM2M TP20 HGI 30/11-3/12. SDT enhancemnt. SDT maintenance process (draft). Documentation for SDT 3.x HGI Q1-2016 -document HGI SH activities transfer June 2016 last HGI © 2015 oneM2M Partners MAS-2015-0599-HGI_activities_transfer_to_oneM2M_WG5