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

Slides:

Advertisements

Similar presentations

June 22, 2007 CMPE588 Term Project Presentation Discovery of Composable Web Services Presented by: Vassilya Abdulova.

Advertisements

CH-4 Ontologies, Querying and Data Integration. Introduction to RDF(S) RDF stands for Resource Description Framework. RDF is a standard for describing.

Call for test suites Group Name: REQ Source: Jiaxin Yin, Huawei Technologies Co., Ltd., Meeting Date: Agenda Item: TBD.

Access Control Mechanism for User Group Name: SEC WG Source: Seongyoon Kim, LG Electronics, Meeting Date: Agenda Item:

OOD - Principles Design Class Diagrams Chapter 10 pp ; ;

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

On a Device Information Model for devices in oneM2M

Processing of structured documents Spring 2003, Part 6 Helena Ahonen-Myka.

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

OneM2M-MP Data_Model_Repository Establishing Data Model Repository for oneM2M Group Name: Method and Procedure Sub-commitee Source: WG3 chair.

1 CIM User Group Conference Call december 8th 2005 Using UN/CEFACT Core Component methodology for EIC/TC 57 works and CIM Jean-Luc SANSON Electrical Network.

1 Yolanda Gil Information Sciences InstituteJanuary 10, 2010 Requirements for caBIG Infrastructure to Support Semantic Workflows Yolanda.

Ontology Alignment/Matching Prafulla Palwe. Agenda ► Introduction  Being serious about the semantic web  Living with heterogeneity  Heterogeneity problem.

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

Source: Yuan Tao, Huawei Technologies WG: MAS Meeting: MAS17.

Proposal for OID-based M2M Node ID Group Name: WG2 Architecture at TP#8 (Miyazaki, December 2013) Source: Yong-Suk Park, KETI, Meeting.

Announcement Resources ARC Announcement_Issues Group Name: WG2 Source: Barbara Pareglio, NEC Meeting Date: Agenda Item: Input Contribution.

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

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.

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

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

Supporting long polling Group Name: ARC WG Source: SeungMyeong, LG Electronics, Meeting Date: x-xx Agenda Item: TBD.

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.

Customized Resource Types MAS Group Name: MAS + ARC + PRO WGs Source: Wolfgang Granzow, Qualcomm Inc., Meeting Date:

ESA UNCLASSIFIED – For Official Use Inputs to SOIS EDS Schema F. Torelli CCSDS SOIS WG, Darmstadt 17/04/2012.

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

6 Dec Rev. 14 Dec CmpE 583 Fall 2008OWL Intro 1 OWL Intro Notes off Lacy Ch. 4 Atilla Elçi.

Ontology Resource Discussion

Extending the MDR for Semantic Web November 20, 2008 SC32/WG32 Interim Meeting Vilamoura, Portugal - Procedure for the Specification of Web Ontology -

ISO/IEC JTC 1/SC 32 Plenary and WGs Meetings Jeju, Korea, June 25, 2009 Jeong-Dong Kim, Doo-Kwon Baik, Dongwon Jeong {kjd4u,

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

ELIS – Multimedia Lab PREMIS OWL Sam Coppens Multimedia Lab Department of Electronics and Information Systems Faculty of Engineering Ghent University.

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

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.

3GPP Rel-13 Interworking discussions

OOD - Principles Design Class Diagrams

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

OIC INTERWORKING Resource mapping

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

SEC #11 WG4 Status & Release 1 Outlook Group Name: Source:,, Meeting Date: Agenda Item:

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

Extending the Metadata Registry for Semantic Web - Enforcing the MDR for supporting ontology concept - May 28, 2008 ISO/IEC JTC 1/SC 32 WG 2 Meeting Sydney,

Device Management Deployments In oneM2m Group Name: MAS Working Group Source: Timothy Carey, Alcatel-Lucent, Meeting Date:

LWM2M Interworking Proxy Procedures ARC Considerations

Example mapping of KNX to oneM2M base Ontology

Template proposal Group Name: PRO Source: Barbara PAreglio, NEC, Meeting Date: Agenda Item: input contribution.

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

Discussion on Certification Group Name: TST WG Source: JaeSeung Song, WG6 Chair, Meeting Date: TST #21.

Discussion on oneM2M and OSGi Interworking Group Name: ARC Source: Jessie, Huawei, Meeting Date: Agenda Item:

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

TS-0004 guideline for new resource type definition Group Name: PRO WG Source: SeungMyeong JEONG, LG Electronics Meeting Date: Agenda Item: TS.

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

IEC TC3 Blank Detail Specification

How does Generic Interworking work?

Service Framework Proposal

CSE Retargeting to AE, IPE, and NoDN Hosted Resources

<Student’s name>

Proposed design principles for modelling interworked devices

WPM ad-hoc group report TP#25

Web Ontology Language for Service (OWL-S)

Discussion on XSD open issues

Inputs to SOIS EDS Schema

Service Layer Dynamic Authorization [SLDA]

MCM Ontology Notes.

Presentation transcript:

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

Motivation This contribution follows MAS , suggesting we should focus on Device Type Template with the following information: – Input- Output operations – Manufacture specific data [optionally] Name/ID of manufacturer Product Identifier  Enables creation of (oneM2M) representations – resources [Disclaimer: this presentation describes our proposal for the general approach, but should not be interpreted as specifying the final model]

MAS Device_&_Device_Type_Modelling Modelling principle Modelling follows a two-layer approach: – Upper Layer: The Device Type Template is modelled as Classes and Properties of an Ontology Device Types are instances of that ontology – Lower Layer: The Device Types now become the Classes of an Ontology (= Templates for individual devices) Individual devices are the instances 3

MAS Device_&_Device_Type_Modelling 3 Levels of Modelling 4 Device Type TemplateDevice Type (by manufacturer) = Template for individual Device individual Device DeviceType Operation Parameter Datatype Manufacturer Product ID … R2D2_Temperature_Sensor R2D2_TempReading R2D2_Temperature double R2D2_Enterprises R2D2_4711 Resource:My_SensorNo_3 OntRef => R2D2_Temperature_Sensor Resource: R2D2_TempReading Res: R2D2_Temperature instance

MAS Device_&_Device_Type_Modelling Using classes/subclasses in modeling the Device Type Template 5 Class => SubClassExplanation DeviceType Manufacturer defined name/ID for a class of alike devices (= type) that are e.g. described in a product description Operation Identifies an operation of the device => OutputOperation The operation produces only an output message. The device does not expect correlated input/ack => InputOperation The operation consists of an input message only. The device does not produce correlated input/ack => In-OutOperation The operation receives an input message and produces a correlated output/ack Parameter Identifies a parameter of the operation DataType Identifies the datatype of the parameter (e.g. xsd: double) Manufacturer Name/ID of the manufacturer Product ID Manufacturer defined handle/ID to identify the type of the device, e.g. Type/Model-number.

MAS Device_&_Device_Type_Modelling Using Properties in modelling the Device Type Template 6 DomainPropertyRange DeviceTypehasOperationOperation hasParameterParameter hasParameterTypeDatatype DeviceTypehasManufacturerxsd:string DeviceTypehasProductIDxsd:string Object Properties Datatype Properties

MAS Device_&_Device_Type_Modelling Device Instance Description Describes instances of individual devices R2D2_Temperature_Sensor Resource:My_SensorNo_3 – R2D2_TempReadingRes.: R2D2_TempReading R2D2_TemperatureRes.: R2D2_Temperature – Double12.34 – MetadataUnit:Celsius Timestamp:12:34:51,123 7 Instances of the Device Type Template become Classes when describing individual Device Instances DeviceType:R2D2_Temperature_Sensor –Operation:R2D2_TempReading Parameter:R2D2_Temperature –Datatype:double

MAS Device_&_Device_Type_Modelling Using classes/subclasses in modelling the Template for individual Devices 8 Class => SubClassExplanation Device=> R2D2_Temperature_Sensor User defined name/ID for a specific instance of the R2D2_Temperature_Sensor instance., e.g. My_SensorNo_3 R2D2_TempReading Specific operation of the instance of R2D2_Temperature_Sensor R2D2_Temperature Specific parameter of the instance of R2D2_TempReading Metadata Metadata related to the value of an R2D2_Temperature

MAS Device_&_Device_Type_Modelling Using Properties in modelling the Template for individual Devices 9 DomainPropertyRange R2D2_Temperature _Sensor hasTemperatureOperationR2D2_TempReading hasTemperatureParameterR2D2_Temperature hasMetadataMetadata R2D2_TemperaturehasValuexsd:double Object Properties Datatype Properties

MAS Device_&_Device_Type_Modelling Device Instance (in rdf:type owl:Ontology ; owl:imports :Resource:My_SensorNo_3 rdf:type dev-temp: R2D2_Temperature_Sensor, owl:NamedIndividual ; dev:hasTemperatureOperation :R2D2_TempReading. :R2D2_TempReading rdf:type dev-temp:R2D2_TempReading, owl:NamedIndividual ; dev:hasTemperatureParameter :R2D2_Temperature. :R2D2_Temperature rdf:type dev-temp:R2D2_Temperature, owl:NamedIndividual ; dev:hasValue “23.45"^^xsd:double. 10