Overview of oneM2M Home Appliances Information Model

Slides:



Advertisements
Similar presentations
oneM2M and AllJoyn Interworking
Advertisements

WG5 - MAS Progress Report at TP #16 Group Name: WG5 MAS (Management, Abstraction & Semantics) Source: Yongjing Zhang (Huawei, WG5 Chair) Meeting Date:
A Proposal of “Common Information Model” for HEMS domain Group Name: MAS WG Source: Yoshihisa Ito, Takefumi Yamazaki,
A Proposal of “Common Information Model” for HEMS domain
WG5 - MAS Progress Report at TP #17 Group Name: WG5 MAS (Management, Abstraction & Semantics) Source: Yongjing Zhang (Huawei, WG5 Chair) Meeting Date:
On a Device Information Model for devices in oneM2M
Proposed Co-convened WG1/2 Objectives, Schedule, and Activities Group Name: TP#1 Source: Omar Elloumi (Alcatel-Lucent), Laurent Laporte (Sprint) Meeting.
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.
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
WG1 status report to TP#17 Group Name: oneM2M TP17 Source: Shelby Kiewel (iconectiv) Meeting Date: to Agenda Item: TP#17, Item 10.3,
Work Group / Work Item Proposal Slide 1 © 2012 oneM2M Partners oneM2M-TP oneM2M_Work_Group_Work_Item_Proposal Group name: Technical Plenary Source:
WG5 - MAS Progress Report at TP #9 Group Name: WG5 MAS (Management, Abstraction & Semantics) Source: Yongjing Zhang, Chair, Meeting.
Wayforward of Abstract Information Model (Mapping Model with Resource Structure) Group Name: WG5 Source: Heedong LG Electronics.
WG5 - MAS Progress Report at TP #10 Group Name: WG5 MAS (Management, Abstraction & Semantics) Source: WG5 Chairs Meeting Date: to
WPM ad-hoc group report TP#17 closing Group Name: WPM (TP adhoc) Source: convener WPM Roland Hechwartner, Meeting Date:
TP WG1 status report to TP#16 Group Name: oneM2M TP16 Source: Shelby Kiewel (iconectiv) Meeting Date: to Agenda Item: TP#16,
1 HGI MESSAGE TO ONEM2M TECHNICAL PLENARY HANS WERNER BITZER, DEUTSCHE TELEKOM VICE CHAIR, HGI ONEM2M TP#19, SOPHIA ANTIPOLS, FRANCE.
Scenarios for oneM2M and OIC Interworking
Release Timeline Discussion R2 and beyond Group Name: TP_WPM Source: Roland Hechwartner, WPM Convenor, Meeting Date:
WG5 – MAS#19 Status Report Group Name: WG5 MAS (Management, Abstraction & Semantics) Source: Yongjing Zhang (Huawei, WG5 Chair) Meeting Date:
WG1 status report to TP#21 Group Name: oneM2M TP21 Source: Shelby Kiewel (iconectiv) Meeting Date: to Agenda Item: TP#21, Item 10.4,
WG5 – MAS#21 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:
Way Forward of Abstract Information Model (Mapping Model with Resource Structure) Group Name: WG2 Source: Heedong LG Electronics.
Introduction to oneM2M OMA - oneM2M Meeting, San Diego, Jan. 19th 2016
WG1 status report to TP#20 Group Name: oneM2M TP20 Source: Joerg Swetina (NEC) Meeting Date: to Agenda Item: TP#19, Item 10.4, Reports.
TP WG1 - REQ Progress Report at TP #14 Group Name: WG1 REQ (Requirements) Source: WG1 Vice Chair (Joerg Swetina, NEC), Secretary Changho RYOO,
WG5 – MAS#22 Status Report Group Name: WG5 MAS (Management, Abstraction & Semantics) Source: Tim Carey(Alcatel-Lucent, WG5 Vice Chair) Meeting Date:
Discussion on oneM2M and OSGi Interworking Group Name: ARC Source: Jessie, Huawei, Meeting Date: Agenda Item:
WG1 - REQ Progress Report at TP #11 Group Name: WG1 REQ (Requirements) Source: WG1 Vice Chairs Meeting Date: to Agenda Item: TP#11,
Possible Solution of Interworking between oneM2M and OSGi
Possible options of using DDS in oneM2M Group Name: ARC Source: KETI, Huawei, Hitachi, China Unicom Meeting Date: Agenda Item: DDS binding.
What is oneM2M? 2 Covers: Requirements Architecture API specifications Security Interoperability Facilitate, implement and promote IoT.
WG5 – MAS#23 Status Report Group Name: WG5 MAS (Management, Abstraction & Semantics) Source: Yongjing Zhang (Huawei, WG5 Chair) Meeting Date:
Semantics in oneM2M MAS Group Name: MAS
WG5 – MAS#24 Status Report Group Name: WG5 MAS (Management, Abstraction & Semantics) Source: Yongjing Zhang (Huawei, WG5 Chair) Meeting Date:
ONEM2M RELEASE 2: SETTING THE STANDARD FOR IOT INTEROPERABILITY
Status of Active Work Items Level of Completeness
oneM2M Work on IoT Semantic and Data Model Interoperability
CSE Retargeting to AE, IPE, and NoDN Hosted Resources
oneM2M Work on IoT Semantic and Data Model Interoperability
oneM2M Work on IoT Semantic and Data Model Interoperability
Proximal IoT Interworking discussion
oneM2M Work on IoT Semantic and Data Model Interoperability
WG2 - ARC TP#29 Status Report
3GPP interworking in R3 Group Name: ARC
Possible options of using DDS in oneM2M
Modbus interworking Group Name: ARC
Proposed design principles for modelling interworked devices
WPM ad-hoc group report TP#24
WG1 status report to TP#15 Group Name: oneM2M TP15
Release Timeline Discussion R2 and beyond
oneM2M Work on IoT Semantic and Data Model Interoperability
WPM ad-hoc group report TP#25
WG5 – MAS#27 Status Report Group Name: WG5 MAS (Management, Abstraction & Semantics) Source: Yongjing Zhang (Huawei, WG5 Chair) Meeting Date:
WG2 - ARC TP#29 Status Report
Proximal IoT Interworking solution discussion
ARC Proposed design principles for modelling services, datapoints and operations Group Name: ARC Source: Joerg Swetina, NEC
oneM2M Work on IoT Semantic and Data Model Interoperability
New WI on Industrial Domain Information Model
New WI on Industrial Domain Information Model
ETSI Standardization Activities on M2M communications
Release2 Workshop in Tokyo
An introduction to oneM2M
Current standardization activities – oneM2m
SMART HOME Expectation IN STANDARDS
Release2 Seminar in Tokyo
W3C WoT Standardization
Next Steps Bundang, Korea, July 2018.
Presentation transcript:

Overview of oneM2M Home Appliances Information Model Group Name: oneM2M-W3C Joint Web-conference Source: Rapporteur of TS-0023(oneM2M Home Appliance Information Model) Meeting Date: 2016-08-31 Agenda Item: oneM2M Home Appliance Information Model

Contents Introduction Design principle of HAIM1) in oneM2M Current progress and Example Tentative plan for Release-3 Collaboration with W3C 1) Home Appliance Information Model

Introduction Motivation Core contributors in this topic oneM2M system provides common service functions that can be utilized by multiple domains including home domain. However, application developers can use these functions differently and have multiple choices to describe the status of devices as resources on oneM2M platform, which does not guarantee cross-vendor interoperability. Defining common abstract information model is thus highly vital to resolve such an issue. Moreover, it would facilitate machine-to-machine interaction without human’s interaction. oneM2M started creating the information model for home domain first. Core contributors in this topic Deutsche Telekom, Fujitsu, Hitachi, Huawei, LG Electronics, NTT, Orange, Samsung, SKT, … History of HAIM in oneM2M `14.09, TP13 `15.03, TP16 `15.09, TP19 `16.05, TP23 `16.07, TP24 A new WI for Home Domain Enablement was created with a study on use cases, necessary technologies (TR-0013) TS-0023 was finalized for Release 2 including 13 devices and 41 module classes Reached on a consensus that HAIM is necessary and a new research was started to figure out how to define the information models (TR-0017) Principle of designing the models was agreed to apply HGI SDT1) and created a new normative technical specification (TS-0023) to specify HAIM Clean-up, protocol definition were complete. TS-0023 is included in the set of oneM2M Release 2 publication `16.08 ~ Further home appliance information models would be added and a research on interworking with external information models that are being developed out side of oneM2M such as OCF and AllJoyn would be conducted 1) Home Gateway Initiative SmartHome Device Template

Design principle of HAIM in oneM2M Using Smart Device Template (SDT) as template of oneM2M HAIM The SDT is an initiative from the Home Gateway Initiative (HGI) to find consensus amongst various SDOs and industry alliance to derive a common approach for device modelling oneM2M designed the principle of the HAIM based on HGI SDT 3.0 since it’s already well-generalized, expandable and efficient to reduce fragmentation among several technologies Available at https://git.onem2m.org/MAS/SDT , example models from other consortia include DECT ULE, ECHONET Lite, Energy@Home (s. https://github.com/Homegateway) SDT Structure Modularity for functions and device types Specification of a single service with one or more service(s). This can be re-used in many device definitions Unique name that acts like a namespace Arbitrary sequences of operations/methods Physical appliance/sensor Variable to be read/written Async signaling of stage change A device embedded in a device Instantiation of a ModuleClass Arbitrary additional information

Current progress and Example (1/3) HAIMs for Release 2 14 Devices Television, Air conditioner, Oven, Refrigerator, Robot cleaner, Clothes washer, Electric vehicle charger, Light, Micro-generation, Smart electric meter, Storage battery, Thermostat, Water heater 41 ModuleClasses Audio volume, Battery, Binary switch, Brightness, Colour, Clock, Push button, Temperature, Timer, Television Channel, … Television example ModuleClasses Home Domain toggle() Argument televisionChannel audioVolume binarySwitch audioVideoInput Action Module none powerState Data Point none Event serialNum deviceType modelName deviceName manufacturer none Property No Sub-device Property

Current progress and Example (2/3) Television example in the specification (TS-0023) ModuleClass Action Module Data point Property

Current progress and Example (3/3) Television example in SDT xml Television example in oneM2M resource tree Registration oneM2M G/W Television <CSEBase> <AE> <television> <flexContainer> 1 contDefinition 1 serialNum 1 [customAttr] deviceType 0..1 <binarySwitch> 1 <audioVolume> <flexContainer> 0..1 <televisionChannel> 0..1 <audioVideoInput>

Tentative plan for Release-3 HAIMs enhancement More devices, module classes Proximal IoT Technologies Interworking Mapping to external models such as OCF, AllJoyn Information model for new domains Vehicular domain Industrial domain Applications Mca Unified API oneM2M Resource Mapping <flexContainer> Common Information Model oneM2M HAIM AllJoyn OIC/OCF ZigBee … A variety of proximal IoT technologies

Collaboration with W3C Alignment between HAIM/SDT and WoT Thing Description (TD)? Using oneM2M HAIM to validate W3C WoT TD (e.g. in plugFest)?