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

Slides:

Advertisements

Similar presentations

Architectures for Data Access Services Practical considerations for design of discoverable, reusable interoperable data sources.

Advertisements

Semantic Annotation Options for Release2 Group Name: MAS WG Source: Catalina Mladin, Lijun Dong, InterDigital Meeting Date: Agenda Item: TBD.

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

1 Adaptive Management Portal April

Report on Intrusion Detection and Data Fusion By Ganesh Godavari.

A Similarity Measure for OWL-S Annotated Web Services Web Intelligence Laboratory, Sharif University of Technology, Tehran, Iran WI 2006 SeyedMohsen (Mohsen)

A Proposal of “Common Information Model” for HEMS domain

OneM2M Draft proposal for slide set. This is not intended to be a oneM2M presentation. It is a collection of source material slides which can be used.

On a Device Information Model for devices in oneM2M

Authors list to be completed.

© 2011 Open Mobile Alliance Ltd. All Rights Reserved. Used with the permission of the Open Mobile Alliance Ltd. under the terms as stated in this document.

Ontology-derived Activity Components for Composing Travel Web Services Matthias Flügge Diana Tourtchaninova

TDT4252/DT8802 Exam 2013 Guidelines to answers

Interoperability Scenario Producing summary versions of compound multimedia historical documents.

On Management, Abstraction & Semantics

Authors list to be completed.

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

Requirements Overview Group Name: Technical Plenary (TP19) Source: Shelby Kiewel, iconectiv, Meeting Date: Agenda Item:

App-ID Use Cases, Syntax and Attributes SEC App-ID_Use_Cases,_Syntax_and_Attributes Group Name: Architecture Source: Darold Hemphill, iconectiv,

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

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

Report on Intrusion Detection and Data Fusion By Ganesh Godavari.

In Dublin’s fair city, where the metadata are so pretty… John Roberts Archives New Zealand.

OneM2M-REQ R03 Proposed simple guidelines for writing use cases and requirements Group Name: oneM2M WG1 / WG2 Source: Joerg Swetina (NEC), Ataru.

Proposed Co-convened WG1/2 Objectives, Schedule, and Activities Group Name: TP#1 Source: Omar Elloumi (Alcatel-Lucent), Laurent Laporte (Sprint) Meeting.

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.

IHE Profile – SOA Analysis: In Progress Update Brian McIndoe January 18, 2011.

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

June 15, 2009GITB Open Meeting, Brussels1 GITB Alternative Architectures and Business Models CEN/ISSS eBIF Global eBusiness Interoperability Test Bed Methodologies.

Work Group / Work Item Proposal Slide 1 © 2012 oneM2M Partners oneM2M-TP oneM2M_Work_Group_Work_Item_Proposal Group name: Technical Plenary Source:

Service Service metadata what Service is who responsible for service constraints service creation service maintenance service deployment rules rules processing.

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

Proposal for WG3 & WG5 work area split

RSISIPL1 SERVICE ORIENTED ARCHITECTURE (SOA) By Pavan By Pavan.

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

WPM ad-hoc group report TP#17 closing Group Name: WPM (TP adhoc) Source: convener WPM Roland Hechwartner, Meeting Date:

Ontology Resource Discussion

IoT High Level Architecture (HLA) AIOTI Edited by AIOTI WG3 Chairs Patrick Guillemin Jean-Pierre Desbenoit AIOTI WG3 IoT High Level Architecture – Release.

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.

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

3GPP Rel-13 Interworking discussions

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

OneM2M Partnership Project. Contents Introduction Founding Partners Participation Scope & Objectives Structure Deliverables Contacts © 2013 oneM2M Partners.

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:

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

Proposed Co-convened WG1/2 Objectives, Schedule, and Activities Group Name: TP#1 Source: Omar Elloumi (Alcatel-Lucent), Laurent Laporte (Sprint) Meeting.

WG2 Roadmap Discussion Denise Warzel May 25, 2010 WG2 Convenor SC32 WG2N1424SC32 WG2N1424.

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

Semantics in Web Service Composition for Risk Management Michael Lutz European Commission – DG Joint Research Centre Ispra, Italy EcoTerm IV, Vienna,

Way Forward of Abstract Information Model (Mapping Model with Resource Structure) Group Name: WG2 Source: Heedong LG Electronics.

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

Reasons for CSF Clean-up (Issues & Next Steps) Group Name: WG2 Source: Syed Husain – NTT DOCOMO Meeting Date: (ARC_9.3) Agenda Item: 6 DOC#:

Directions for Release 3 Group Name: SEC Source: NEC Europe Ltd. Meeting Date: SEC22, Agenda Item: Discuss directions.

A Semi-Automated Digital Preservation System based on Semantic Web Services Jane Hunter Sharmin Choudhury DSTC PTY LTD, Brisbane, Australia Slides by Ananta.

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:

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 Work on IoT Semantic and Data Model Interoperability

Service Framework Proposal

Possible options of using DDS in oneM2M

Modbus interworking Group Name: ARC

WPM ad-hoc group report TP#25

CHAPTER 2 CREATING AN ARCHITECTURAL DESIGN.

On Management, Abstraction & Semantics

Presentation transcript:

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

Device abstraction & semantics 2 Physical Device Abstract Device Virtual Device Semantically annotated & shared Zigbee temp sensor KNX temp sensor room#1room#2 temp sensor (room#1) temp sensor (room#2) temp sensor (house) Access network HomeAutomation Application 1 HomeAutomation Application 1 HomeAutomation Application 2 HomeAutomation Application 2 EnergyMgt Application 1 EnergyMgt Application 1 Semantic query Normal query Semantic area Semantic mapping

3 Zigbee temp sensor KNX temp sensor room#1room#2 temp sensor (room#1) temp sensor (room#2) temp sensor (house) Physical Device Abstract Device Virtual Device Access network HomeAutomation Application 1 HomeAutomation Application 1 HomeAutomation Application 2 HomeAutomation Application 2 EnergyMgt Application 1 EnergyMgt Application 1 Semantics -How to annotate semantic information? -How to discover available resources without prior knowledge? -How to ensure semantic interoperability among actors? Virtual Entity -How to group resources to provide a meaningful information? -How to provide a new service using available resources? Device Abstraction -How to derive general information from raw M2M resource data? -How to map device specific functions to generic (abstract) functions? M2M Abstraction and Semantics

Potential requirements The M2M system shall provide the capability to map sets of similar functions of devices to specified abstract functions. (HLR-139) The M2M system shall provide a capability to associate abstract functions with the functionalities of a device. (HLR-140) The M2M system shall provide the capability for M2M Applications to invoke a function of the device through the abstract functions associated with the functionalities of the device. (HLR-141) Gateway Device shall have the following requirements: to support Home Appliances from multiple vendors as an abstracted object models. (HLR-084) The underlying networks and telco operator resources shall be abstracted as M2M resources to provide to the applications a consistent use of the M2M system capabilities. (HLR-056) The M2M system shall provide a semantic/meta-language model that can map industry-specific information models for end device application functionalities to common and application-agnostic abstract functions that are understood components of the M2M system. (HLR-142) The M2M system shall provide a capability to an Application to create Virtual Devices and Things in the M2M Service Capability Network. (HLR-099) The M2M system shall provide a capability to an Application to publish semantic descriptions and meta-data (e.g. location) of its Devices, Virtual Devices and Things in the M2M Service Capability Network. (HLR-100) The M2M system shall provide a capability to an Application to search for and discover Devices, Virtual Devices and Things in the M2M Service Capability Network based on their semantic descriptions and meta-data. The supported formats of semantic descriptions shall be described in the oneM2M standard. (HLR-101) The M2M system shall provide a capability to an Application to control, via the M2M Service Capability Network, access to semantic descriptions and meta-data of its Devices, Virtual Devices and Things. (HLR-102) The M2M system shall provide a capability to an Application shall to allow, via the M2M Service Capability Network, access to its Devices, Virtual Devices and Things to individual other applications. (HLR-103) 4

Schedule Overall schedule – The work on the TR will start immediately and is expected to continue throughout the release Target of first release – Collect, analyse and evaluate the state-of-the-art technologies on Device abstraction (incl. virtual things) and semantics. – Technical Report – Discovery of abstracted devices and virtual devices and things – Consolidating and agreeing on Abstraction and Semantic related requirements for input to the oneM2M Requirement TS – Input CRs for other related TR and TS, i.e., oneM2M Use Cases TR / Vocabulary, Role and Focus Area TR / oneM2M Architecture TS Target of later releases – Semantic annotation / Composition of M2M services with semantic (mashups) / semantic discovery, etc. – Semantic annotation and mashups TR – Semantic M2M TS 5

The End 6