Applying SAREF to oneM2M Proposal for discussion in MAS – DRAFT From: Omar Elloumi (ALU) Source: Alcatel-Lucent (ATIS) Meeting Date: 2015-03-23 Agenda.

Slides:

Advertisements

Similar presentations

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

Advertisements

REQ WG Reuse of underlying networks, 3GPP

REQ WG Reuse of underlying networks, 3GPP

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

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

REQ WG Reuse of underlying networks, 3GPP From: Omar Elloumi (ALU) Source: Alcatel-Lucent (ATIS) Meeting Date: Agenda Item:

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.

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,

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

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:

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

Collaboration with IEEE P2413 Source: Omar Elloumi, TP Chair WG: TP Meeting: TP17.

VIKEF – Take the VIKEF train towards smart services …

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

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

A Context Model based on Ontological Languages: a Proposal for Information Visualization School of Informatics Castilla-La Mancha University Ramón Hervás.

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

Fuctional Procedure for oiC interworking

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

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

Ontology Mapping in Pervasive Computing Environment C.Y. Kong, C.L. Wang, F.C.M. Lau The University of Hong Kong.

WG5 - MAS Progress Report at TP #10 Group Name: WG5 MAS (Management, Abstraction & Semantics) Source: WG5 Chairs Meeting Date: to

An introduction to oneM2M

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.

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

Introducing WI Proposal about Authorization Architecture and Policy Group Name: WG4 Source: Wei Zhou, Datang, Meeting Date: Agenda Item:

Management of Semantic Instances in resources using SPARQL update operation with HTTP verbs Group Name: MAS 19 Source: Minwoo Ryu, jaeho Kim, Sungchan.

LWM2M Interworking Group Name: Architecture

Release Timeline Discussion R2 and beyond Group Name: TP_WPM Source: Roland Hechwartner, WPM Convenor, 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:

Discussion about RESTful Admin API Group Name: SEC & ARC Source: FUJITSU Meeting Date: Agenda Item: Device Configuration.

Device & Device Type Modelling Group Name: WG5 Source: NEC Meeting Date: Agenda Item: WI-0005 MAS Device_&_Device_Type_Modelling.

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.

Technical Plenary Update on collaborations From: oneM2M TP Chair Source: Meeting Date: Agenda Item:

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

Example mapping of KNX to oneM2M base Ontology

Subscription and Notification Issue Group Name: WG2 Source: Qi Yu, Mitch Tseng- Huawei Technologies, Co. LTD. Meeting Date: ~23 Agenda Item:

Technical Plenary Terms for the collaboration with P2413 From: oneM2M TP Chair Source: Meeting Date: Agenda Item:

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:

Group Name: oneM2M WG1 Requirements Source: Phil Hawkes, Rapporteur “Benefits of oneM2M technology” TR,

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:

OneM2M next steps Group Name: TP Source: TP leadership Meeting Date: Agenda Item: TBD.

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:

How does Generic Interworking work?

Service Framework Proposal

Discussion about Use Case and Architecture in Developer Guide

Discussion on Abstraction Application Entity

Semantic testing in oneM2M

Release Timeline Discussion R2 and beyond

WPM ad-hoc group report TP#25

How does Generic Interworking work? (R01 based on SAREF discussion)

Considering issues regarding handling token

Semantic Web Technologies

An introduction to oneM2M

Information Architecture

Presentation transcript:

Applying SAREF to oneM2M Proposal for discussion in MAS – DRAFT From: Omar Elloumi (ALU) Source: Alcatel-Lucent (ATIS) Meeting Date: Agenda Item:

© 2015 oneM2MMARCOM Report oneM2M Release 1 did not support semantic interoperability: it is assumed that AE (application entities) that produce/consume data have a prior common understanding of the data that is being exchanged oneM2M Release 2 will support semantic interoperability TR-0007 provides initial study on how to make oneM2M system semantic enabled. Objective of the slide: what normative work needs to take place in the context of oneM2M Release 2: Impact on resource structure Impact on procedures and message flows (discovery) Impact on SCF or functions Methodology: let’s take a concrete ontology as a basis: SAREF Introduction

© 2015 oneM2MMARCOM Report Introduction to SAREF (Smart Applicances Reference ontology Origin)

© 2015 oneM2MMARCOM Report Introduction to SAREF (Smart Applicances Reference ontology

© 2015 oneM2MMARCOM Report saref:WashingMachine rdf:type saref:WashingMachine, owl:Class ; rdfs:comment "A washing machine is a device that has category saref:Appliance, accomplishes the task saref:cleaning and performs an actuating function of type saref:StartPauseFunction"^^xsd:string ; rdfs:label "Washing machine"^^xsd:string ; rdfs:subClassOf saref:Device ; saref:accomplishes saref:Washing ; saref:hasCategory saref:Appliance, saref:Load ; saref:hasFunction saref:StartStopFunction ; saref:hasState saref:START, saref:STOP. saref:WashingMachine ontologyReference AE? commandContainter ? stateContainer?

© 2015 oneM2MMARCOM Report saref:WashingMachine

© 2015 oneM2MMARCOM Report saref:WashingMachine representation in oneM2M AEwashingMachine1 descriptor startStopContainer hasStateContainer

© 2015 oneM2MMARCOM Report saref:WashingMachine descriptor saref: WashingMachine category A Whirlpool saref: WMStateService saref: WMStartStopService saref: WMStateOperation> saref: GET /CSE1/AEwashingMachine1/hasStateContainer wMSM: hasOutput> saref: Start, saref: Stop

© 2015 oneM2MMARCOM Report Need to enrich SAREF with hREST and MSM to allow integration into oneM2M Relationship to oneM2M base ontology?