1. A Proposal of “Common Information Model” for HEMS domain Group Name: MAS WG Source: Yoshihisa Ito, Takefumi Yamazaki, NTT(ito.yoshihisa@lab.ntt.co.jp) Meeting Date: 2015-01-19 Agenda Item: TBD

2. Motivation / Background Concrete resource mapping rules are not defined yet corresponding to various application domains. If a globally common application domain is decided and the resource mapping rules with Rel. 1 specs are provided, it will lead to value oneM2M standard based platforms. HEMS (Home Energy Management System) is currently promoted nationwide with the unified device protocol “ECHONET Lite”. Various kinds of services with HEMS data (ex. visualization, AAL, etc.) are expected to be developed in the future. Thus, such services can be strongly promoted if any oneM2M standard based platform is available.

3. Related project at oneM2M Our proposal is related to the concept shown in TR-0007 “ Study of Abstraction and Semantics Enablements ”. We also think that the definition of the “Common Information Models” for various M2M domains is essential to specify APIs.

4. Home Energy Management System (HEMS) is one of typical M2M service domains. HEMS data was accumulated through gateway devices and sent to the remote management server to realize various applications. (see the below example) Home Energy Management System oneM2M-REQ-2012-0072 Use Case Home Energy Management System (HEMS)

5. Architecture The components for HEMS can be mapped onto the architecture of oneM2M. M2M platform can provide services with HEMS data through APIs. APIs can be defined based on common information model for HEMS. HEMS Service Server GW HEMS GW Smart Meter Power network in the home Power Sensor Access Network Service wireless wired APIs M2M Platform

6. An example of resource mapping for HEMS According to oneM2M Rel.1, resource mapping for HEMS data can be described as follows. Amount of electric power selling / buying on smart meter Content=2.1kWh Content=0.8kWh

7. Various patterns for HEMS data: (Japanese use case) Power consumption data at many possible places can be measured at HEMS. Resources mapping for the corresponding data must be considered. DiningKitchenBathBed room Breaker Box ToiletLiving LightHVACTVLightHVACLight HVACMicrowave Water heater Light Smart Meter Power Network Cogeneration Solar power genelation Charger for EV Gas Network Main Breaker Breaker Room Device Whole house Device

8. Expected Results / Effects From the global standard point of view, M2M platform should provide the Unified APIs. To realize such APIs, resource mapping rules at HEMS domain should also be common globally. HEMS 【 region-X 】 Unified APIs M2M PF HEMS 【 region-Y 】 M2M PF Service Developer (Energy Domain) HEMS 【 region-X 】 Fragmented APIs M2M PF HEMS 【 region-Y 】 M2M PF Service Developer (Energy Domain)

9. Summary After Rel.1, we propose a new work item called “Common Information Model for Home Energy Management System”. In order to establish such a work item, we would like to have your comments and supports regarding future actions. We will share our consideration results about concrete resource mapping for the target use cases in the coming TPs.