A Proposal of “Common Information Model” for HEMS domain

Slides:

Advertisements

Similar presentations

A Proposal of “Common Information Model” for HEMS domain Group Name: MAS WG Source: Yoshihisa Ito, Takefumi Yamazaki,

Advertisements

WG5 - MAS Progress Report at TP #17 Group Name: WG5 MAS (Management, Abstraction & Semantics) Source: Yongjing Zhang (Huawei, WG5 Chair) Meeting Date:

CURRENT STANDARDIZATION ACTIVITIES – ONEM2M GSC-18 Meeting, July 2014, Sophia Antipolis, France Document No: GSC(14)18_012 Source: ETSI Contact:

TTA Views on Technical Scope of M2M Consolidation 17 August 2011 TTA M2MCons02_16 (Agenda 4.3)

On a Device Information Model for devices in oneM2M

Conflict Management Group Name: WG1 Source: KETI, ETRI, SK Telecom, nTels, KCA, Kaonmedia Meeting Date: dd Agenda Item: Discussion.

Authors list to be completed.

Method of Converting Resource definitions into XSD Group Name: WG3 (PRO) Source: Shingo Fujimoto, FUJITSU, Meeting Date:

TEC Automobile WG. Joint Work Group Meeting.

Home Control Protocol for Smart Devices Hojin Park WG!-N1505.

INTERNATIONAL ELECTROTECHNICAL COMMISSION © IEC:2007 PC118 WG1 Draft Framework China PC 118/WG1 Meeting, , Santa Clara.

Mechanism to support establishment of charging policies Group Name: WG2-ARC Source: InterDigital Meeting Date: TP8 Agenda Item:

Progressing the Work on the MAS TR-0006, TR-0007 Group Name: Management Abstraction and Semantics Source: Tim Carey, ALU,

Metadata IN Smart Grid Group Name: REQ

Discussions for oneM2M Semantics Standardization Group Name: WG5 Source: InterDigital Communications Meeting Date: Agenda Item: WI-0005 ASN/MN-CSE.

1 OPSAWG Agenda Items 7,8, 9 Juergen Quittek, John Parello, Benoit Claise 78th IETF Meeting, Maastricht, Energy Management Framework / Architecture.

Optimized M2M interworking with mobile networks Group Name: oneM2M REQ Source: Takanori Iwai, NEC, Meeting Date: Agenda.

Environmental Monitoring for Hydro-Power Generating Group Name: WG#1 Source: Kerry-Lynn Gauci, Inmarsat, Meeting Date:

Report of co-conveners WG1/WG2 meetings between TP1 and TP2 Group Name: Technical Plenary #2 Source: Omar Elloumi, Alcatel-Lucent,

Introduction of PRO WG activities Group Name: TP Source: Shingo Fujimoto, FUJITSU, Meeting Date: Agenda Item:

End-to-End security definition Group Name: SEC WG4 Source: Phil Hawkes, Qualcomm, Meeting Date:

\ 1 Presentation for SC25 WG1 N1651 RC (Residential Complex) -EMS for HES Wanki Park ETRI, Korea Ilwoo Lee (ETRI, Korea) ISO/IEC.

M2M Abstraction & Semantics Group Name: WG5 Source: France Telecom, NEC Europe Ltd., Meeting Date: xx.

3GPP Rel-13 Interworking discussions

HGI activities transfer to oneM2M Group Name: MAS Source: Patricia MARTIGNE (Orange), Deutsche Telekom, Telecom Italia Meeting Date: Agenda.

Potential use case for discussion – Device Abstraction Group Name: WG1/2 Source: Alcatel-Lucent Meeting Date: Joint-REQ-ARC-WGs-call Agenda Item: Use cases.

JEMMA: an open platform for a connected Smart Grid Gateway GRUPPO TELECOM ITALIA MAS2TERING Smart Grid Workshop Brussels, September Strategy &

What and Why? Next steps for oneM2M Semantics Group Name: WG5 Source: Joerg Swetina, Martin Bauer (NEC) Meeting Date: Agenda Item: WI-0005 oneM2M-MAS

ETRI-KPU ISO/IEC JTC1 SC25 WG1, Oct A Home-oriented IPTV Service Platform on Residential Gateway for Interworking between Home Network and IPTV.

WG1 status report to TP#17 Group Name: oneM2M TP17 Source: Shelby Kiewel (iconectiv) Meeting Date: to Agenda Item: TP#17, Item 10.3,

WG5 - MAS Progress Report at TP #9 Group Name: WG5 MAS (Management, Abstraction & Semantics) Source: Yongjing Zhang, Chair, Meeting.

Proposal for WG3 & WG5 work area split

Architectural Principles for Services Group Name: WG2- ARC Source: Tim Carey, ALU, Meeting Date: Agenda Item:

Work for the next release Group Name: TP Source: JaeSeung Song, KETI, Jaeho Kim, KETI,

Step by step approach Group Name: WG2 Source: Michael hs. Yang, LG uplus, Jaeseung Song, NEC Europe, Meeting.

Halifax, 31 Oct – 3 Nov 2011ICT Accessibility For All Home Networking activities in TTC Kenji KORO TTC Next-Generation Home Network system WG Document.

IEEE MEDIA INDEPENDENT HANDOVER DCN: REVP-Proposal-on-the-security-of Title: Proposal on the security of Date Submitted:

Introducing concept of M2M-application data modeling Group Name: MAS Source: FUJITSU Meeting Date: Agenda Item: Semantics and Device Configuration.

1 HGI MESSAGE TO ONEM2M TECHNICAL PLENARY HANS WERNER BITZER, DEUTSCHE TELEKOM VICE CHAIR, HGI ONEM2M TP#19, SOPHIA ANTIPOLS, FRANCE.

Ontology Architectural Support Options Group Name: MAS WG Source: Catalina Mladin, Lijun Dong, InterDigital Meeting Date: Agenda Item: TBD.

Scenarios for oneM2M and OIC Interworking

Intelligent Home Scenario Group Name: WG1 Source: KETI, ETRI, SK Telecom, nTels, KCA, Kaonmedia Meeting Date: dd Agenda Item: Discussion.

Fostering worldwide interoperabilityGeneva, July 2009 Inter-Industrial Standardization Hyungsoo KIM TTA Global Standards Collaboration (GSC) 14 DOCUMENT.

Realizing Ms Interface with OMA DM Group Name: MAS WG Source: Seungkyu Park, LG Meeting Date:

Architectural Considerations for Semantic Support Group Name: WG5 Source: Martin Bauer (NEC), Joerg Swetina (NEC) Meeting Date: Agenda Item:

WG5 – MAS#19 Status Report Group Name: WG5 MAS (Management, Abstraction & Semantics) Source: Yongjing Zhang (Huawei, WG5 Chair) Meeting Date:

Status of Active Work Items Level of Completeness Group Name: WPM Source: Roland Hechwartner, WPM Convenor Updated:

Introduction to oneM2M OMA - oneM2M Meeting, San Diego, Jan. 19th 2016

TP WG1 - REQ Progress Report at TP #14 Group Name: WG1 REQ (Requirements) Source: WG1 Vice Chair (Joerg Swetina, NEC), Secretary Changho RYOO,

Introducing concept of M2M-application data modeling Group Name: MAS Source: FUJITSU Meeting Date: Agenda Item: Semantics and Device Configuration.

WG5 – MAS#22 Status Report Group Name: WG5 MAS (Management, Abstraction & Semantics) Source: Tim Carey(Alcatel-Lucent, WG5 Vice Chair) Meeting Date:

DM Collaboration – OMA & BBF: Deployment Scenarios Group Name: WG5 - MAS Source: Tim Carey, ALU, Meeting Date:

Management CSF(s) Architectural choices Group Name: WG2 (ARC), WG5(MAS) Source: Catalina Mladin, InterDigital Comm., Meeting.

CloudMAC: Moving MAC frames processing of the Sink to Cloud.

Discussion for Testing related Activities Group Name: TP Source: JaeSeung Song, KETI, Meeting Date: Agenda.

Possible options of using DDS in oneM2M Group Name: ARC Source: KETI, Huawei, Hitachi, China Unicom Meeting Date: Agenda Item: DDS binding.

WG5 – MAS#23 Status Report Group Name: WG5 MAS (Management, Abstraction & Semantics) Source: Yongjing Zhang (Huawei, WG5 Chair) Meeting Date:

WG5 – MAS#24 Status Report Group Name: WG5 MAS (Management, Abstraction & Semantics) Source: Yongjing Zhang (Huawei, WG5 Chair) Meeting Date:

Overview of oneM2M Home Appliances Information Model

3GPP interworking in R3 Group Name: ARC

Possible options of using DDS in oneM2M

Discussions on Heterogeneous Identification Service

Home Networking activities in TTC

oneM2M Work on IoT Semantic and Data Model Interoperability

Considering issues regarding handling token

New WI on Industrial Domain Information Model

Release2 Workshop in Tokyo

Home Networking activities in TTC

SMART HOME Expectation IN STANDARDS

Release2 Seminar in Tokyo

Presentation transcript:

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) 　　　　　Nick Yamasaki, KDDI (nr-yamasaki@kddi.com) Meeting Date: 2015-01-19 Agenda 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 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) 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. Service Service Service Service APIs Server M2M Platform Access Network GW GW GW Power network in the home HEMS HEMS HEMS HEMS HEMS wired Smart Meter Power Sensor wireless

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. Power Network Gas Network Breaker Breaker Main Breaker Cogeneration Solar power genelation Charger for EV Smart Meter Device Breaker Breaker Breaker Breaker Box Whole house Living Dining Kitchen Room Bath Room Toilet Bed room Device Light HVAC TV Light HVAC Light HVAC Microwave Light Water heater Light Light

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】 Fragmented APIs M2M PF 【region-Y】 Service Developer (Energy Domain) HEMS 【region-X】 Unified　APIs M2M PF 【region-Y】 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 Comment What is best target work program. How to use management function. There is Control function (ex. setting device’s power-limitation). It should be <AE>? Which one is better? How to collaborate with semantic approach. When propose to TP.