1、 ETSI TR 118 522 V2.0.0 (2016-09) oneM2M; Continuation Essential, or potentially Essential, IPRs notified to ETSI in respect of ETSI standards“, which is available from the ETSI Secretariat. Latest updates are available on the ETSI Web server (https:/ipr.etsi.org/). Pursuant to the ETSI IPR Policy,
2、no investigation, including IPR searches, has been carried out by ETSI. No guarantee can be given as to the existence of other IPRs not referenced in ETSI SR 000 314 (or the updates on the ETSI Web server) which are, or may be, or may become, essential to the present document. Foreword This Technica
3、l Report (TR) has been produced by ETSI Partnership Project oneM2M (oneM2M). ETSI ETSI TR 118 522 V2.0.0 (2016-09) 5oneM2M TR-0022 version 2.0.01 Scope The present document is a study of the continuation and integration of some HGI Smart Home activities into oneM2M, following the (PT2) HGI announcem
4、ent 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. It intends to be used as a liaison working document with HGI about the status progress of this continuation and integration an
5、d is expected to be useful for both HGI and oneM2M to check that all technical items from HGI SH Task Force expected to be integrated are appropriately handled by oneM2M. 2 References 2.1 Normative references References are either specific (identified by date of publication and/or edition number or
6、version number) or non-specific. For specific references, only the cited version applies. For non-specific references, the latest version of the referenced document (including any amendments) applies. Referenced documents which are not found to be publicly available in the expected location might be
7、 found at https:/docbox.etsi.org/Reference/. NOTE: While any hyperlinks included in this clause were valid at the time of publication, ETSI cannot guarantee their long term validity. The following referenced documents are necessary for the application of the present document. Not applicable. 2.2 Inf
8、ormative references References are either specific (identified by date of publication and/or edition number or version number) or non-specific. For specific references, only the cited version applies. For non-specific references, the latest version of the referenced document (including any amendment
9、s) applies. NOTE: While any hyperlinks included in this clause were valid at the time of publication, ETSI cannot guarantee their long term validity. The following referenced documents are not necessary for the application of the present document but they assist the user with regard to a particular
10、subject area. i.1 oneM2M Drafting Rules. NOTE: Available at http:/www.onem2m.org/images/files/oneM2M-Drafting-Rules.pdf. i.2 ETSI TS 118 11 oneM2M TS-0011: “Common Terminology“. i.3 ETSI TR 118 517: “Home Domain Abstract Information Model“. i.4 ETSI TR 118 507: “Abstraction and Semantics Capability
11、Enablement“. i.5 ETSI TS 118 123: “Home Appliances Information Model and Mapping“. i.6 ETSI TS 118 101: “Functional Architecture“. i.7 Home Gateway Initiative HGI-RD036: “Smart Home architecture and system requirements“. NOTE: Available at http:/www.homegatewayinitiative.org/userfiles/file/downloads
12、/RD036Publication.pdf. i.8 Smart (Home) Device Template (SDT). NOTE: Available at https:/ ETSI ETSI TR 118 522 V2.0.0 (2016-09) 6oneM2M TR-0022 version 2.0.0i.9 Home Gateway Initiative HGI RD039: “Requirements for Wireless Home Area Networks (WHANs) Supporting Smart Home Services“. NOTE: Available a
13、t http:/www.homegatewayinitiative.org/userfiles/file/downloads/RD039-Req-for-Wireless-home-area-networks.pdf. i.10 Home Gateway Initiative HGI-RD048: “HG Requirements For HGI Open Platform 2.1“. NOTE: Available at http:/www.homegatewayinitiative.org/userfiles/file/downloads/HGI-RD048-HG_Requirements
14、_for_HGI_Open_Platform_2_0_published_text.pdf. i.11 ECHONET Consortium NOTE: Available at https:/ i.12 OSGi Alliance. NOTE: Available at http:/www.osgi.org. i.13 Eclipse Vorto Project. NOTE: Available at http:/eclipse.org/vorto. i.14 ETSI TS 118 104: “oneM2M; Service Layer Core Protocol Specificatio
15、n (oneM2M TS-0004)“. i.15 ETSI TS 118 112: “oneM2M; Base Ontology (oneM2M TS-0012)“. 3 Definitions, symbols and abbreviations 3.1 Definitions For the purposes of the present document, the terms and definitions given in ETSI TS 118 111 i.2 apply. 3.2 Symbols For the purposes of the present document,
16、the symbols given in ETSI TS 118 111 i.2 apply. 3.3 Abbreviations For the purposes of the present document, the abbreviations given in ETSI TS 118 111 i.2 and the following apply: CWMP CPE (Customer Premises Equipment) WAN (Wide Area Network) Management Protocol DAL Device Abstraction Layer HGI Home
17、 Gateway Initiative RMS Remote Management System SHGW Smart Home Gateway SHTF Smart Home Task Force WHAN Wireless Home Area Network WI Work Item4 Conventions The key words “Shall“, “Shall not“, “May“, “Need not“, “Should“, “Should not“ in the present document are to be interpreted as described in th
18、e oneM2M Drafting Rules i.1. ETSI ETSI TR 118 522 V2.0.0 (2016-09) 7oneM2M TR-0022 version 2.0.05 Technical description of HGI Smart Home activities in a generic IoT context 5.1 General Introduction to HGI SmartHome concepts and motivation of integration to oneM2M The HGI Smart Home Task Force globa
19、l objective was to defragment the Smart Home market and propose unified concepts identified as of prime importance around the Smart Home Gateway (SHGW) in order to facilitate the adoption and the use of such a product and related services in homes. These concepts can be categorized into three main t
20、rends: modularity of the SHGW middleware to allow for flexible evolution of the services offered to the user; abstraction of the (possibly various) underlying connectivity technologies of the devices connected to the SHGW; identification of reference points that need to be standardized to forster op
21、en exposure to mutualized functions at the SHGW level as enablers for local or remote services. As similar concepts are handled by oneM2M at the Sercice Layer level for the IoT domain in general, some technical achievements from HGI SHTF can be merged into some of the oneM2M deliverables, which is a
22、 supplementary path towards more de-fragmentation of the IoT domain. The remaining subsections of this section 5 summarizes these HGI SHTF achievements to be considered. 5.2 Smart Home Architecture and requirements for Reference Points, HGI-RD036 HGI-RD036 i.7 deliverable presents the HGI reference
23、architecture for the Smart Home Gateway (SHGW) and identifies the reference points that are at stake to deliver the smart home services, be it locally or remotely. Figure 5.2-1 shows this reference architecture, which is driven by the requirements of modularity and device abstraction allowed by the
24、SHGW. The Reference Points between the appliances (devices) and the SHGW and between the SHGW and the Cloud are designated by “RPx“ on figure 5.2-1. ETSI ETSI TR 118 522 V2.0.0 (2016-09) 8oneM2M TR-0022 version 2.0.0Figure 5.2-1: SHGW reference architecture and Reference Points When comparing this a
25、rchitecture with the oneM2M architecture ETSI TS 118 101 i.6, the following points can be examined: the SHGW as a oneM2M Middle Node; RP4 as an example of oneM2M Mcc reference point; RP7 as an example of Mca reference point; and RP8 as an example of Mcn reference point. This comparison is further de
26、tailed under clause 6. As for the Device Abstraction Layer, this is further focused on figure 5.2-2, which points out the disctinction between: the “south“ part of the DAL where the goal is to abstract the various device-connectivity technologies; and the “north“ part of the DAL where the goal is to
27、 decouple the applicative-specific i.e.various applicative domains, with their specific ontologies, and unify the meaning of commands from the application side. The purpose of device abstraction is indeed to allow creators of applications on SHGWs and/or in the Cloud to discover, identify, read, con
28、figure and manipulate devices, without needing to modify the software for each and every manufacturer model or type of wireless access, etc. Figure 5.2-2 also shows the SDT (Smart Device Template) as part of this Device Abstraction process. This SDT is explained in more details under clause 5.3. ETS
29、I ETSI TR 118 522 V2.0.0 (2016-09) 9oneM2M TR-0022 version 2.0.0Figure 5.2-2: SDT place in the Device Abstraction process 5.3 Smart Device Template The SDT (Smart Device Template i.8) is an initiative from HGI to find consensus amongst various SDOs and industry alliances to derive a common approach
30、for device modelling. HGI and partners have the approach to agree on a set of automation commands, following a common syntax, which are sufficient to model most home appliance functions. Every software developed for home gateways or internet-of-things gateways needs to be capable of using various di
31、fferent protocols (DECT ULE,EchonetLite, UpnP, ZigBee, etc.) to interact with a range of devices designed for the home environment. This adds extreme overheads in integrating, checking and updating code. The purpose of SDT is to describe devices and device services in a way which is independent of t
32、he LAN technology, in a format which is convenient and reliable for integration in modern code (Java, C/C+, etc.). The key goals of the SDT are: 1) keep it simple, especially for manufacturers to contribute device information; 2) modularity for functions and device types; 3) make it easy for develop
33、ers to create unified APIs; 4) be independent of underlying home-area network technologies; 5) enable extendibility of the system in place without service interruption; 6) allow a pass-through mechanism to enable use of proprietary or technology-specific functions. The SDT approach is to define re-u
34、sable basic functions (or services), labelled “ModuleClass“, which can represent the typical functions found in many home automation systems, such as “on/off“, “dim a lamp“, “receive events from binary sensor“, “read data from sensor“, etc. Each ModuleClass is composed of a (small) number of actions
35、, datapoint read/write operations, or asynchronous events. For example, an “on/off“ ModuleClass would consist perhaps of just one Action, but a “ReadKeypad“ Action might have a number of possible events, each with some data value and (usually) a sequence-ID or timestamp start/stop to indicate when a
36、nd how long each key was pressed. More details about SDT can now be found in ETSI TR 118 517 i.3, clause 5.1.3. ETSI ETSI TR 118 522 V2.0.0 (2016-09) 10oneM2M TR-0022 version 2.0.0Also the ECHONET Consortium provided the mapping of the ECHONET-LITE technology in the SDT format i.11. It should be not
37、ed that the HGI work on SDT is closely aligned with the work of OSGi Alliance i.12 on Device Abstraction Layer (DAL). The OSGi Residential Specification Release 6 defines such a DAL that acts as an intermediate between technology-specifics of connected devices and embedded applications. OSGi Allianc
38、e already specified technologies binding for various connecting technologies such as enOcean, UpnP, USB, ZB, Zwave, etc. The next step on top of DAL within the OSGi Alliance is to specify further support for device abstraction using SDT. This is expected to be done in collaboration with oneM2M, base
39、d on ETSI TS 118 123 i.5, through the new Work Item on technical axis of collaboration between OSGi Alliance and oneM2M. Furthermore, SDT-related discussions happened with a part of the Eclipse Foundation, in particular the Eclipse Vorto Project i.13. Vorto is an open source tool that allows to crea
40、te and manage technology agnostic, abstract device descriptions, so called information models. Vorto and SDT information models are closely aligned in order to be able to exchange device descriptions in an interoperable way. 5.4 Wireless Home Area Networks consideration, HGI-RD039 HGI-RD039 i.9 prov
41、ides guidance on WHAN technologies used for smart home services. This lists generic requirements expected for these technologies to enable functions such as bidirectional communication and pairing of devices with WHAN coordinators. In particular, the following sections of this HGI deliverable may be
42、 referenced in device management related oneM2M Work Items such as the Work Item on oneM2M Abstraction and Semantics Capability Enablement and the one on M2M Application clause 7.1 “Installation and configuration of devices“; clause 7.3 “Management and maintenance of devices“; clause 7.4 “Connectivi
43、ty management“. 5.5 Home gateway Open platform, HGI-RD048 HGI-RD048 i.10 specifies the requirements regarding modular software deployments on home gateway with an open platform. These modular software applications must run in a dedicated virtual execution environment to enable software flexibility.
44、In particular, software modules and module configuration data can be kept across the complete firmware updates, avoiding the overhead of maintaining different versions of firmware for several HG models. The solution of such an execution environment is defined as open platform. The open platform 2.1
45、i.10 enabled home gateway consists of several functional entities, including core functions (HG_Core), HG Execution Environment (HG_EE), HG Application Programming Interface (HG_API) and Management Agent (MA), as demonstrated in figure 5.5-1. ETSI ETSI TR 118 522 V2.0.0 (2016-09) 11oneM2M TR-0022 ve
46、rsion 2.0.0Figure 5.5-1: Home gateway architecture model HG_Core utilize an operation system, on which HG_Core runs the HG native softwares. Running on top of the HG_Core, HG_EE includes the HG_SP providing software lifecycle management and acting as a container for flexible application software mod
47、ules, which can use HG_API to access to residential gateway functions. Moreover, CWMP protocol is used by MA, a piece of software running on the HG, to handle the management commands from RMS. In addition, besides the general requirements, HGI-RD048 i.10 also specifies the technology-specific requir
48、ements for OSGI technology. This OSGI service platform is a Java based HG_SP with the addition of a comprehensive component model. Other technology-specific requirements could be developed in the same ways as the OSGI requirements, in conjunction with the generic requirements. 6 Integration of HGI S
49、H items into oneM2M work items 6.1 Update of oneM2M WIs already including some HGI SH inputs As introduced in clause 5, the main HGI Smart Home technical achievements of interest for oneM2M include: HGI-RD036 i.7 deliverable, defining the Smart Home Architecture, published in Q4-2015. SDT3.0 Smart Device Template i.8, which is the meta-data model defined for modelling devices. The abstraction layer
