Study of Service Transactions and Re-Usable Service Layer Context

6 ONEM2M TECHNICAL REPORT Document Number TR-0022-V-0.4.0

Document Name: Continuation & integration of HGI Smart Home activities

Date: 2016-Febr-11

Abstract: The document is a study of the continuation and integration of some HGI Smart Home activities into oneM2M, following the (PT2) HGI announcement of its closure by June 2016. It includes the description of HGI SH deliverables versus the appropriate oneM2M deliverables for the integration of these HGI achievements.

Template Version:23 February 2015 (Dot not modify)

7 8 9 10 11 12 This Specification is provided for future development work within oneM2M only. The Partners accept no 13 liability for any use of this Specification. 14 The present document has not been subject to any approval process by the oneM2M Partners Type 1. 15 Published oneM2M specifications and reports for implementation should be obtained via the oneM2M 16 Partners’ Publications Offices.

2 3 © oneM2M Partners Type 1 (ARIB, ATIS, CCSA, ETSI, TIA, TTA, TTC) Page 1 of 12 4 This is a draft oneM2M document and should not be relied upon; the final version, if any, will be made available by oneM2M Partners Type 1. 5

19 About oneM2M

20 The purpose and goal of oneM2M is to develop technical specifications which address the 21 need for a common M2M Service Layer that can be readily embedded within various 22 hardware and software, and relied upon to connect the myriad of devices in the field with 23 M2M application servers worldwide.

24 More information about oneM2M may be found at: http//www.oneM2M.org

25 Copyright Notification

28 The copyright and the foregoing restriction extend to reproduction in all media. 29 30 Notice of Disclaimer & Limitation of Liability

31 The information provided in this document is directed solely to professionals who have the 32 appropriate degree of experience to understand and interpret its contents in accordance with 33 generally accepted engineering or other professional standards and applicable regulations. 34 No recommendation as to products or vendors is made or should be implied.

35 NO REPRESENTATION OR WARRANTY IS MADE THAT THE INFORMATION IS 36 TECHNICALLY ACCURATE OR SUFFICIENT OR CONFORMS TO ANY STATUTE, 37 GOVERNMENTAL RULE OR REGULATION, AND FURTHER, NO 38 REPRESENTATION OR WARRANTY IS MADE OF MERCHANTABILITY OR 39 FITNESS FOR ANY PARTICULAR PURPOSE OR AGAINST INFRINGEMENT OF 40 INTELLECTUAL PROPERTY RIGHTS. NO oneM2M PARTNER TYPE 1 SHALL BE 41 LIABLE, BEYOND THE AMOUNT OF ANY SUM RECEIVED IN PAYMENT BY 42 THAT PARTNER FOR THIS DOCUMENT, WITH RESPECT TO ANY CLAIM, AND IN 43 NO EVENT SHALL oneM2M BE LIABLE FOR LOST PROFITS OR OTHER 44 INCIDENTAL OR CONSEQUENTIAL DAMAGES. oneM2M EXPRESSLY ADVISES 45 ANY AND ALL USE OF OR RELIANCE UPON THIS INFORMATION PROVIDED IN 46 THIS DOCUMENT IS AT THE RISK OF THE USER.

47 Contents

48 Contents...... 3 49 1 Scope...... 4 50 2 References...... 4 51 2.1 Normative references...... 4 52 2.2 Informative references...... 4 53 3 Definitions, symbols and abbreviations...... 4 54 3.1 Definitions...... 4 55 3.2 Symbols...... 4 56 3.3 Abbreviations...... 4 57 4 Conventions...... 5 58 5 Technical description of HGI Smart Home activities in a generic IoT context...... 5 59 5.1 General Introduction to HGI SmartHome concepts and motivation of integration to oneM2M...... 5 60 5.2 Smart Home Architecture & requirements for Reference Points, HGI RD-036...... 5 61 5.3 Smart Device Template, HGI RD-050...... 7 62 6 Integration of HGI SH items into oneM2M work items...... 7 63 6.1 Update of oneM2M WIs already including some HGI SH inputs...... 7 64 6.2 other oneM2M WIs to be involved...... 8 65 6.3 Potential need for (a) new oneM2M WI(s)...... 9 66 Annex : Follow-up of the integration...... 9 67 A.1 Check-list of HGI SH TF items integration into oneM2M...... 9 68 A.2 Roadmap...... 9 69 Annex : Bibliography...... 10 70 History...... 11 71

72 1 Scope

73 The present document is a study of the continuation and integration of some HGI Smart Home activities into oneM2M, 74 following the (PT2) HGI announcement of its closure by June 2016. It includes the description of HGI SH deliverables 75 versus the appropriate oneM2M deliverables for the integration of these HGI achievements.

76 It intends to be used as a liaison working document with HGI about the status progress of this continuation and 77 integration and is expected to be useful for both HGI and oneM2M to check that all technical items from HGI SH Task 78 Force expected to be integrated are appropriately handled by oneM2M.

79 2 References

80 References are either specific (identified by date of publication and/or edition number or version number) or 81 non-specific. For specific references, only the cited version applies. For non-specific references, the latest version of the 82 referenced document (including any amendments) applies.

83 2.1 Normative references

84 Not applicable for a Technical Report.

85 2.2 Informative references

86 The following referenced documents are not necessary for the application of the present document but they assist the 87 user with regard to a particular subject area.

88 [i.1] oneM2M Drafting Rules (http://member.onem2m.org/Static_pages/Others/Rules_Pages/oneM2M-Drafting- 89 Rules-V1_0.doc)

90 3 Definitions, symbols and abbreviations

91 3.1 Definitions

92 For the purposes of the present document, the [following] terms and definitions [given in ... and the following] apply:

94 [N]: [N] identifies the external document which must be listed in Section 2 References.

95 3.2 Symbols

96 For the purposes of the present document, the [following] symbols [given in ... and the following] apply:

97 98 <2nd symbol> <2nd Explanation> 99 <3rd symbol> <3rd Explanation>

100 3.3 Abbreviations

101 For the purposes of the present document, the [following] abbreviations [given in ... and the following] apply:

102 103

104 4 Conventions

105 The key words “Shall”, ”Shall not”, “May”, ”Need not”, “Should”, ”Should not” in this document are to be interpreted 106 as described in the oneM2M Drafting Rules [i.1]

107 5 Technical description of HGI Smart Home activities in 108 a generic IoT context

109 5.1 General Introduction to HGI SmartHome concepts and 110 motivation of integration to oneM2M 111 HGI Smart Home Task Force global objective was to defragment the Smart Home market and propose 112 unified concepts identified as of prime importance around the Smart Home Gateway (SHGW) in order to 113 facilitate the adoption and the use of such a product and related services in homes. 114 These concepts can be categorized into three main trends: 115 - modularity of the SHGW middleware to allow for flexible evolution of the services offered to the user; 116 - abstraction of the (possibly various) underlying connectivity technologies of the devices connected to the 117 SHGW; 118 - identification of reference points that need to be standardized to forster open exposure to mutualized 119 functions at the SHGW level as enablers for local or remote services. 120 As similar concepts are handled by oneM2M at the Sercice Layer level for IoT domain in general, some 121 technical achievements from HGI SHTF can be merged into some of the oneM2M deliverables, which is a 122 supplementary path towards more de-fragmentation of the IoT domain. The remaining subsections of this 123 section 5 summarizes these HGI SHTF achievements to be considered.

124 5.2 Smart Home Architecture & requirements for Reference Points, 125 HGI RD-036

126 Editor’s Note: explain the Smart Home issues and describe the HG-centered architecture, including the Device 127 Abstraction Layer, that enables Smart Home. How it maps into oneM2M main architectural concepts. Also explain the 128 reference points (identified in RD-036) that need to be standardized; how they may relate to oneM2M reference points / 129 APIs. 130 HGI RD-036 deliverable presents the HGI reference architecture for the Smart Home Gateway (SHGW) and 131 identifies the reference points that are at stake to deliver the smart home services, be it locally or remotely. 132 Figure 5.2-1 below shows this reference architecture, which is driven by the requirements of modularity and 133 device abstraction allowed by the SHGW. 134 The Reference Points between the appliances (devices) and the SHGW and between the SHGW and the 135 Cloud are designated by “RPx” on the Figure. 136

18 19 © oneM2M Partners Type 1 (ARIB, ATIS, CCSA, ETSI, TIA, TTA, TTC) Page 5 of 12 20 This is a draft oneM2M document and should not be relied upon; the final version, if any, will be made available by oneM2M Partners Type 1. 21 137

138 Figure 5.2-1 SHGW reference architecture and Reference Points

139 140 When comparing this architecture with the oneM2M architecture TS-0001, we can look at : 141 - the SHGW as a oneM2M Middle Node; 142 - RP4 as an example of oneM2M Mcc reference point, 143 - RP7 as an example of Mca reference point, and 144 - RP8 as an example of Mcn reference point. 145 This comparison is further detailed under Section 6.

146 147 As for the Device Abstraction Layer, this is further focused on Figure 5.2-2 below, which points out the 148 disctinction between 149 - the “south” part of the DAL where the goal is to abstract the various device-connectivity technologies, and 150 - the “north” part of the DAL where the goal is to decouple the applicative-specific i.e.various applicative 151 domains, with their specific ontologies, and unify the meaning of commands from the application side. 152 The purpose of device abstraction is indeed to allow creators of applications on SHGWs and/or in the Cloud 153 to discover, identify, read, configure and manipulate devices, without needing to modify the software for 154 each and every manufacturer model or type of wireless access, etc. 155 Figure 5.2-2 also shows the SDT (Smart Device Template) as part of this Device Abstraction process. This 156 SDT is explained in more details under section 5.3.

158 Figure 5.2-2 SDT place in the Device Abstraction process

160 5.3 Smart Device Template, HGI RD-050 161 The SDT (Smart Device Template, https://github.com/Homegateway/SmartDeviceTemplate/) is an initiative 162 from HGI to find consensus amongst various SDOs and industry alliances to derive a common approach for 163 device modelling. HGI and partners have the approach to agree on a set of automation commands, following 164 a common syntax, which are sufficient to model most home appliance functions. 165 Every software developed for home gateways or internet-of-things gateways needs to be capable of using 166 various different protocols (ZigBee, UPnP, EchonetLite, DECT ULE, etc) to interact with a range of devices 167 designed for the home environment. This adds extreme overheads in integrating, checking and updating 168 code. The purpose of SDT is to describe devices and device services in a way which is independent of the 169 LAN technology, in a format which is convenient and reliable for integration in modern code (Java, C/C+ 170 +, ...). 171 The key goals of the SDT are: 172 1) keep it simple, especially for manufacturers to contribute device information; 173 2) modularity for functions and device types; 174 3) make it easy for developers to create unified APIs; 175 4) be independent of underlying home-area network technologies; 176 5) enable extendibility of the system in place without service interruption; 177 6) allow a pass-through mechanism to enable use of proprietary or technology-specific functions. 178 The SDT approach is to define re-usable basic functions (or services), labelled "ModuleClass" in the figure 179 below, which can represent the typical functions found in many home automation systems, such as "on/off", 180 "dim a lamp", "receive events from binary sensor", "read data from sensor", etc. Each ModuleClass is 181 composed of a (small) number of actions, datapoint read/write operations, or asynchronous events. For

182 example, an "on/off" ModuleClass would consist perhaps of just one Action, but a "ReadKeypad" Action 183 might have a number of possible events, each with some data value and (usually) a sequence-ID or 184 timestamp start/stop to indicate when and how long each key was pressed. 185 More details about SDT can now be found in oneM2M TR-0017 section 5.1.3. 186 Also the ECHONET Consortium provided the mapping of the ECHONET-LITE technology in the SDT 187 format; this contribution can be found at https://github.com/Homegateway/ECHONET-SDT-Contribution. 188 189 It should be noted that the HGI work on SDT is closely aligned with the work of OSGi Alliance 190 (http://www.osgi.org) on Device Abstraction Layer (DAL). The OSGi Residential Specification Release 6 191 defines such a DAL that acts as an intermediate between technology-specifics of connected devices and 192 embedded applications. 193 The next step on top of DAL within the OSGi Alliance is to specify further support for device abstraction 194 using SDT. 195 In addition, OSGi Alliance already specified technologies binding for various connecting technologies such 196 as USB, enOcean, UPnP,… 197 198 Furthermore, SDT-related discussions happened with a part of the Eclipse Foundation, in particular the 199 Eclipse Vorto Project (http://eclipse.org/vorto). Vorto is an open source tool that allows to create and manage 200 technology agnostic, abstract device descriptions, so called information models. Vorto and SDT information 201 models are closely aligned in order to be able to exchange device descriptions in an interoperable way.

202 6 Integration of HGI SH items into oneM2M work items

203 6.1 Update of oneM2M WIs already including some HGI SH inputs 204 As introduced in Clause 5, the main HGI Smart Home technical achievements of interest for oneM2M 205 include: 206 - HGI RD-036 deliverable, defining the Smart Home Architecture, published in Q4-2015 207 - SDT3.0 Smart Device Template, which is the meta-data model defined for modeling devices 208 The abstraction layer explicitely defined by these HGI deliverables can indeed be mapped to the oneM2M 209 abstraction Common Services Entity at the Middle Node (MN-CSE), as illustrated in Figure 6.1-1 below 210 derived from Figure 5.2-1. 211

213 Figure 6.1-1 Mapping HGI SH architecture to oneM2M entities 214 The HGI Abstraction Layer concept is already mentioned in oneM2M TR-0007 (WI-0005) clause 6.2.2, and 215 the updated SDT3.0 is described into details in TR-0017 (WI-0017) clause 5.1.3. From the latter, the SDT3.0 216 appears to be particularly relevant to be the oneM2M reference for the normative Home Information Model 217 deliverable TS-0023 (also within WI-0017). 218 From Figure 5.2-2, the SDT is shown as a modeling template that can be used to : 219 - model devices in a unified way, be they technologyX-based or technologyY-based; for this part the 220 SDT can be exposed to the appliances through a oneM2M IPE (Interworking Proxy Entity) via a 221 oneM2M Mca instantiation that should meet the HGI requirements for RP1 Device Abstraction 222 Layer (see Figure 5.2-1) as copied in Table 6.2-1 (under clause 6.2 below); 223 - provide a unified template for modeling devices for any applicative domain, thus facilitating cross- 224 domain semantic interoperability; for this part, the SDT can be seen as the converging model to 225 which various appliances data models from the industry can be mapped to.

226 6.2 other oneM2M WIs to be involved 227 The mapping of the SDT to oneM2M MN-CSE involves mapping of SDT elements into some oneM2M 228 resource types e.g. semanticDescriptor, container of TS-0001 Release2 (WI-0025). 229 Editor’s Note: Additionnally, mapping HGI Reference Points to oneM2M Mca, Mcc, Mcn Reference Points 230 involves careful analysis of TS-0004 Release2.

231 Editor’s Note: In particular HGI requirements for RP1 DAL (HGI RD-036 section 6.1) and RP1 access 232 control (HGI RD-036 section 6.2) may be checked against TS-0001 and TS-0004 specifications for Mca. 233 Editor’s Note: HGI requirements for RP4 (HGI RD-036 section 6.5) may be checked against TS-0001 and 234 TS-0004 specifications for Mcc.

235 6.3 Potential need for (a) new oneM2M WI(s) 236 In Clause 5.2, the HGI RP8 was compared to oneM2M Mcn, as a possible mean to re-use relevant functions 237 from the fixed internet connection. Yet, currently the oneM2M Mcn is defined in relation with the mobile 238 network, i.e. for the 3GPP triggering function. There may be a need to create a new oneM2M WI to describe 239 Mcn in relation with fixed networks; such a new WI could be worked in close relation with e.g. BBF.

242 Annex : 243 Follow-up of the integration

244 A.1 Check-list of HGI SH TF items integration into oneM2M

245 Editor’s Note: include a list of possible Action Items to be tracked.

246 A.2 Roadmap

247 Editor’s Note: indicate the timeline of the integration of HGI achievement into oneM2M (as the one suggested in the 248 overview section of TP-2015-0773R02)

249 Annex : 250 Bibliography

251  : “”.</p><p>252 OR</p><p>253 <Publication>: “<Title>”.</p><p>42 43 © oneM2M Partners Type 1 (ARIB, ATIS, CCSA, ETSI, TIA, TTA, TTC) Page 11 of 12 44 This is a draft oneM2M document and should not be relied upon; the final version, if any, will be made available by oneM2M Partners Type 1. 45</p><p>254 History</p><p>Publication history V.1.1.1 <dd Mmm yyyy> <Milestone></p><p>255</p><p>Draft history (to be removed on publication) V.0.0.1 3rd August 2015 Very first Draft for discussion at the HGI SH TF call on 5th August 2015, after creation of the oneM2M new WI-0043 (approved at TP18, on 22nd July 2015).</p><p>V.0.0.2 26th August 2015 Revision taking into account comments received on the HGI diffusion list.</p><p>V.0.0.3 28th August 2015 Revised version validated by the HGI SHTF call on 28th August. This version was presented at the MAS#18.2 call (31st August) which was a joint call with HGI SHTF.</p><p>V.0.0.4 7th September Revised version to take into account comments from MAS#19 Monday opening 2015 session: section related to the management of the follow-up of the work is moved from the TR body to an annex. V.0.1.0 14th September Skeleton for TR-0022 (approved at oneM2M TP#19) 2015 V.0.2.0 29th October 2015 Integration of Approved contribution at MAS#19.2: MAS-2015-0656, adding text under §5.1 and §5.2. V.0.3.0 2nd December Integration of the Approved contribution at MAS#20: 2015 MAS-2015-0657R02, adding text under §6.1, 6.2, and 6.3. V0.4.0 11th February Integration of the Approved contribution at MAS#21: 2016 MAS-2016-0040, adding text under §5.3 256</p><p>257</p><p>46 47 © oneM2M Partners Type 1 (ARIB, ATIS, CCSA, ETSI, TIA, TTA, TTC) Page 12 of 12 48 This is a draft oneM2M document and should not be relied upon; the final version, if any, will be made available by oneM2M Partners Type 1.</p> </div> <div class="ft-cover"> <a href="#" id="scrollLink"><i class="iconfont icon-top-1-copy i-bottom"></i> Load more</a> </div> </div> </div> </div> </div> </div> <div class="about-item" data-tab-item="article"> <div class="article-container" id="loader"></div> <div class="load-content flex-column-center"> <p class="load-p" id="onLoadMore"><span id="surplus"></span></p> <p class="load-p" id="load-text"></p> </div> <div id="downTop"> <div class="reader-tools-bar"> <div class="tools flex-justify"> <a href="javascript:void(0);" title="previous page" class="tools-prev flex-justify"> <i class="iconfont icon-top-1-copy left"></i> </a> <input type="text" class="page-cur" value="1" /><span class="page-num"> 12</span> <a href="javascript:void(0);" title="next page" class="tools-next flex-justify"><i class="iconfont icon-top-1-copy right"></i></a> </div> <div class="bar-download"> <a href="javascript:;" id="copyLink"><i class="iconfont icon-lianjie i-size"></i> Copy Link</a> </div> </div> </div> </div> </div> </div> </article> <section class="recommend"> <div class="panel-box"> <div class="panel-success"> <div class="panel-heading"> <div class="panel-flex"> <div class="panel-left"> Recommended publications </div> </div> </div> <div class="panel-body"> <ul class="panel-body-ul"> </ul> </div> </div> </div> </section> </div> <div class="rw-right row-pd" id="side-right"> <aside class="side" id="side-list"> <div class="side-download"> <a href="" class="side-load-a flex-justify" title="Download"> <i class="icon-load"></i> <span>Download</span> </a> </div> <div class="side-tag"> <ul class="side-tag-ul"> <li><a href="javascript:;" data-tab-target="featured" class="active">Featured</a></li> <li><a href="javascript:;" data-tab-target="last" class="">Last Commenis</a> </li> <li><a href="javascript:;" data-tab-target="popular" class="">Popular</a></li> </ul> <div class="tab-items"> <div class="tab-item active" data-tab-item="featured"> <ul> <li><a href="/doc/13824931/the-elements-of-group-ii-are-known-as-the-alkali-earth-metals">The Elements of Group II Are Known As the Alkali Earth Metals</a></li> <li><a href="/doc/13824930/section-10-28-00-toilet-bath-and-laundry-accessories">Section 10 28 00 - Toilet, Bath, and Laundry Accessories</a></li> <li><a href="/doc/13824929/city-state-duel-ancient-athens-vs-ancient-sparta">City-State Duel: Ancient Athens Vs. Ancient Sparta</a></li> <li><a href="/doc/13824928/3-draw-the-electron-dot-diagram-in-the-box-below">3. Draw the Electron Dot Diagram in the Box Below</a></li> <li><a href="/doc/13824927/pull-from-the-test-kit-the-following-items-that-you-will-need">Pull from the Test Kit the Following Items That You Will Need</a></li> <li><a href="/doc/13824926/scheme-of-work-igcse-english-year-10">Scheme of Work Igcse English Year 10</a></li> </ul> </div> <div class="tab-item" data-tab-item="last"> <ul> <li><a href="/doc/13824925/what-is-deeming">What Is Deeming ?</a></li> <li><a href="/doc/13824924/west-midlands-historic-environment-forum">West Midlands Historic Environment Forum</a></li> <li><a href="/doc/13824923/prec-nat-agreement-shell">PREC - NAT - Agreement - Shell</a></li> <li><a href="/doc/13824922/on-15-01-ban-the-use-of-plastic-microbeads-in-personal-care-products-e-h">ON.15.01 Ban the Use of Plastic Microbeads in Personal Care Products E&H</a></li> <li><a href="/doc/13824921/web-site-tscustomseats-com-email-telephone-479-521-7339-fax-479-442-0777">Web Site: Tscustomseats.Com Email: Telephone: 479-521-7339 Fax: 479-442-0777</a></li> <li><a href="/doc/13824920/unit-plan-template-s22">Unit Plan Template s22</a></li> </ul> </div> <div class="tab-item" data-tab-item="popular"> <ul> </ul> </div> </div> </div> <div class="adspace"> <ins class="adsbygoogle" style="display:block" data-ad-client="ca-pub-8519364510543070" data-ad-slot="2167091933" data-ad-format="auto"></ins> <script>(adsbygoogle = window.adsbygoogle || []).push({});</script> </div> <div class="side-message"> <ul> </ul> </div> </aside> </div> </div> </div> </main> <script> var totalPage = 12; var dId = 13824932; var docId = '732128a95f545c904976fee6f4c9b87a'; </script> <script src="https://cdnjs.cloudflare.com/ajax/libs/jquery/3.5.1/jquery.min.js"></script> <script src="/js/article.js"></script> <footer> <div class="container-fluid"> <a href="#Top" data-toggle="tooltip" data-original-title="TO TOP"> <i class="iconfont icon-top-1-copy"></i> </a> <br /> <br /> <span>© 2024 Docslib.org </span><span><a href="/help/feedback">Feedback</a></span> </div> </footer> <script> $(".nav-menu").click(function () { $(".menu-list").toggle(); }); </script> <script type="text/javascript"> var sc_project = 11552861; var sc_invisible = 1; var sc_security = "b956b151"; </script> <script type="text/javascript" src="https://www.statcounter.com/counter/counter.js" async></script> </body> </html>