Embed Size (px)
Citation preview
A Proposal of “Common Information Model” for HEMS domain
Group Name: MAS WGSource: Yoshihisa Ito, Takefumi Yamazaki, NTT([email protected]) Nick Yamasaki, KDDI ([email protected])Meeting Date: 2015-01-19Agenda Item: TBD
Motivation / Background< Our view about the current release.1 specs >•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.< Domestic situations in Japan (especially HEMS domain) >•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.
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.
• 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)
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 HEMS HEMS HEMS
GW
GW
Smart Meter
Power networkin the home
Power Sensor
Access Network
Service Service Service
wirelesswired
APIs
M2M Platform
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
<CSE><remoteCSE>
<AE[MyHomeSmartMeter]><container[powerConsumption]>
<contentInstance>Content=2.1kWh
<container[powerGeneration]><contentInstance>
Content=0.8kWh<AE[other device…]>
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.
Dining Kitchen Bath Bed room
Breaker Box
ToiletLiving
Light HVAC TV Light HVAC LightLight HVAC Microwave Waterheater Light Light
Smart Meter
Power Network
Cogeneration Solar powergenelation
Chargerfor EV
Gas Network
MainBreaker
Breaker
Breaker
Breaker
Breaker
Breaker
Room Room
Device
Whole house
Device
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 APIsM2M PF
HEMS
【 region-Y 】
M2M PF
Service Developer(Energy Domain)
HEMS
【 region-X 】
FragmentedAPIsM2M PF
HEMS
【 region-Y 】
M2M PF
Service Developer(Energy Domain)
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.
Point of Comment1. What is best target work program.
2. How to use management function.– There is Control function (ex. setting device’s power-limitation).– It should be <AE>?– Which one is better?
3. How to collaborate with semantic approach.
4. When propose to TP.
