1. 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

2. Motivation This contribution follows MAS-2014-0335, 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]

3. MAS-2014-0346-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

4. MAS-2014-0346-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 12.345 instance

5. MAS-2014-0346-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.

6. MAS-2014-0346-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

7. MAS-2014-0346-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

8. MAS-2014-0346-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

9. MAS-2014-0346-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

10. MAS-2014-0346-Device_&_Device_Type_Modelling Device Instance (in OWL/Turtle) @prefix :. @prefix owl:. @prefix rdf:. @prefix xsd:. @prefix dev:. @prefix dev-temp:. @base. 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