Digital Object Memories for the Web of Things Dr.-Ing. Jens Haupert - - PowerPoint PPT Presentation

▶
digital object memories
SMART_READER_LITE
LIVE PREVIEW

Digital Object Memories for the Web of Things Dr.-Ing. Jens Haupert - - PowerPoint PPT Presentation

Mar 13, 2024 472 likes •883 views

Digital Object Memories for the Web of Things Dr.-Ing. Jens Haupert German Research Center for Artificial Intelligence (DFKI) Web of Things Workshop, June 25 th 2013 Sample Scenario Linking: Physical Object and Object Memory * Order *

slide-1
SLIDE 1

Digital Object Memories for the Web of Things

Dr.-Ing. Jens Haupert

Web of Things Workshop, June 25th 2013

German Research Center for Artificial Intelligence (DFKI)

slide-2
SLIDE 2

* Order * Components * Quality Checks Monitoring: * Temperature * Humidity * Acceleration * Price * Date of Sale * Storage Conditions * Transport Data * Usage Linking: Physical Object and Object Memory

2

Sample Scenario

* Recycling

slide-3
SLIDE 3

Open-Loop Scenarios

Open-Loop Closed-Loop

3

slide-4
SLIDE 4

Open-Loop Scenarios (2)

Open-Loop

4

  • A large set of

stakeholders

  • Ad-hoc lifecycle chain
  • No a priory definitions
  • Heterogeneous datasets
slide-5
SLIDE 5

New Requirements

  • Life Cycle Chain

– Object-related information – Open-loop distribution

  • Maintenance

– Specific configurations / Lot size one – Retrieving spare parts

  • After Sales

– (Remote) condition-based monitoring

  • Improved Recycling

– Provide information about components and elements – Recycling feedback to manufacturer

5

slide-6
SLIDE 6

6

Data Foundation

Data Foundation Infrastructure Processing OMS Activity OMM

slide-7
SLIDE 7

Object Memory Model

  • Structure model to partition heterogeneous
  • bject memory data
  • Group associated data to blocks
  • Each block consists of actual payload and

additional meta data

  • Payload can be out-sources to external media
  • Abstract model with XML- and embedded

HTML5-representations

  • W3C Incubator Group (OMM-XG)

7

slide-8
SLIDE 8

OMM Header Table of Contents Block 1 Block n …

Object Memory Model (2)

Block Metadata Block Payload Block Metadata Block Link

8 www

slide-9
SLIDE 9

Object Memory Model (3)

Block Metadata Block Payload

9 ID Name- space Format Title Description Creator Contributors Type Subject

Access History Clear Text Data Content Description M2M HCI

slide-10
SLIDE 10

Object Memory Model (4)

10

Block 2 Block n … Block 1 Block 3

Stakeholder A Stakeholder B Stakeholder Z

slide-11
SLIDE 11

Defined Blocks

11

OMM Structure Block OMM IDs-Block OMM+ Embedded Block OMM+ Semantics Block OMM+ PiVis Block OMM Key-Value-Template Extensions OMM-XG

slide-12
SLIDE 12

12 ID Format Title Creator Type Subject block_123 application/xml

Schema: http://mycomp.com/sensor.xsd

“SensorReading (temp/humi/shock)” 123456789@DUNS, 16.01.2013 16:15

http://purl.org/dc/dcmitype/Dataset “sensorReadings” http://mycomp.com/o.owl#Temperature http://mycomp.com/o.owl#Humidity http://mycomp.com/o.owl#Shock

<?xml version="1.0"> <log> <reading> <value>-6</value> <topic>#Temp</topic> <unit>#Celsius<unit> </reading> <reading> <value>80</value> <topic>#Humid</topic> <unit>#Percent<unit> </reading> <reading> <value>1.6</value> <topic>#Shock</topic> <unit>#G<unit> </reading> </log>

OMM-Block with sensor readings

Sample Memory (1)

slide-13
SLIDE 13

13

OMM-block with embedded memory

Sample Memory (2)

Integration

slide-14
SLIDE 14

14

OMM-Block with embedded memory

Sample Memory (3)

ID Namespace Format Title Creator Type Subject block_456 urn:ommplus:blocks:embeddedBlock application/xml “Memory: Sensor Optobero 124” 123456789@DUNS, 16.01.2013 16:15

http://purl.org/dc/dcmitype/PhysicalObject

„primaryID.opto124“ „myLoggingInfo“ http://ont.org/o.owl#Maintenance

OMM Header

Table of Content

Block 1 Block n … … …

slide-15
SLIDE 15

Infrastructure

15

Data Foundation Infrastructure Processing OMS Activity OMM

slide-16
SLIDE 16

Memory Access

16

RFID-Tag CPS OMS Barcode

www

slide-17
SLIDE 17

Object Memory Server

  • Modular Architecture

– Complete feature set with dedicated server – Partial functionality with embedded systems – Minimal core with simple systems

17

Server Server Link Smart Label Embedded System Infrastructure Object

slide-18
SLIDE 18

18

OMM Object Memory Server XML RDFa Microdata Mapper Java | JavaScript | REST Applications HTML5 User Version Control Role-based Access Binray

RESTful Interface

<memory name>

/ toc blockIDs block / creator subject type payload … / <block ID> GET GET > > GET | PUT > GET | PUT > GET | PUT > GET | PUT >

Object Memory Server (2)

slide-19
SLIDE 19

Processing

19

Data Foundation Infrastructure Processing OMS Activity OMM

slide-20
SLIDE 20

Activity

  • Previous Architecture:

– Passive data storage only

  • Add processing logic to object memories
  • Execute small, local operations (snippets)

within object memory

20

slide-21
SLIDE 21

Activity (2)

21

Cyber-physical System

User

slide-22
SLIDE 22

Activity (2)

22

Cyber-physical System

User

Object Memory Activity Module

Logic Interpreter Code Execution in Sandbox Result

19°C 19°C

Knowledge Heartbeat Memory Events REST Interface

slide-23
SLIDE 23

23

Activity (3)

Memory External Application Activity Module

Interpreter Integrity Check Code

Call Result

Code Execution in Sandbox

  • k

19°C 19°C Knowledge 1 2 3 4 5

Memory Activity Module

Monitoring Logic

Interpreter Code Exectution in Sandbox

Result

19°C 19°C

Knowledge

Heartbeat Call Result 1 2 3 4 5

Integrity Check Independent Object Monitoring

slide-24
SLIDE 24

24

Activity (4)

Memory

Logik

Activity Modules

Memory URL 1 Installed Snippets 2 Snippet Selection by User 3 Upload 4

19°C

Knowledge Logic

slide-25
SLIDE 25

ADOMe vs. CPS

25

Memory

19°C

Knowledge

Digital Object Memory

Memory

Logik

Activity Modules

19°C

Knowledge Logic

Active DOMe (ADOMe)

Memory

Logik

Activity Modules

19°C

Knowledge Logic

Cyber-physical System

Sensors / Actuators

slide-26
SLIDE 26

26

Raspberry Pi

Object Memory Server (OMS)

  • Java-Version w/o VCS und ACL
  • RESTful interface
  • Activity Module and Snippets
  • OMM XML representation

Gadgeteer

Object Memory Server (OMS)

  • C# compact implementation
  • RESTful interface
  • Transparent sensor integration
  • OMM Binary representation

Memory

Logik

Activity Modules

19°C

Knowledge

Logic

Sensors / Actuators Memory

Logik

19°C

Knowledge

Logic

Sensors / Actuators

Sensor 1 Sensor 2

R E S T R E S T

OMM on Embedded Platf.

slide-27
SLIDE 27

Visualization, Tools and Extensions

27

Data Foundation Infrastructure Processing OMS Activity OMM Visualization, Tools and Extensions

slide-28
SLIDE 28

Database Migration

28

Ontologie Modell Ontologie Modell

Datasource (Database)

Ontology Model

Datei Datei Files & Facts OMM- Blöcke OMM- Blöcke OMM- Blocks

Memory

Semantic Harmoni- zation

Extraction

Mapping

Storage

Phase 1 Phase 2

  • Today: Data stored in databases
  • The day after tomorrow: Digital object memories
  • Migration:

– Semantic Harmonization via Ontology Model – Facts and File-extraction – Automatic Memory generation

slide-29
SLIDE 29

Data Representation

29 Storage Core Interfaces

Object Memory Server

XML

Pros:

  • Standardized / Well defined
  • Widely used
  • Human readable

Cons:

  • Verbosity and complexity
  • Slow processing
  • Bad cost-value ratio
slide-30
SLIDE 30

Data Representation (2)

30 Storage Core Interfaces

Object Memory Server

Binary Mapper

  • Dynamic mapper for binary representation

– Lossless conversion for low storage space consumption – Lossy conversion for minimum space consumption

  • Partial restore of lost data possible via mapping table
slide-31
SLIDE 31

Secure Provenance

  • Warranty deeds and legal grounds

– Secure and verifiable data necessary

  • Memory with secure provenance

31

Block 1 Block n … Block 2

Cryptographic Hash Cryptographic Hash Cryptographic Hash

Link Link

slide-32
SLIDE 32

Secure Provenance

  • No later modification feasible

– No alteration of existing blocks – No insertion of new blocks – No deletion of existing blocks (with Authority Server)

32

Block 1 Block n … Block 2

Cryptographic Hash Cryptographic Hash

Link Link

Cryptographic Hash

Authority Server

slide-33
SLIDE 33

Results

  • Definition of a meta model to structure

heterogeneous object memory data and positioning in W3C OMM-XG

  • Reference implementation of a OMM-based

memory infrastructure for open-loop scenarios

  • Hardware abstraction allows usage independent
  • f object properties and capabilities
  • Plug-In-based, dynamic visualization for

heterogeneous data

  • Additional toolset to create new applications

and migrate existing systems

33

slide-34
SLIDE 34

Discussion

  • DOMe-related Data by Trumpf?
  • Where could digital object memories be used?

– Manufactured products? – Machinery?

  • New potentials and business models?

– Possible risks?

34

slide-35
SLIDE 35

Discussion

  • Which types of memories are suitable?

– Embedded/on-object – Server-based/off-object

  • What data could enrich the product life-cycle?
  • Where could autonomous activity be used?
  • How could a Snippet Store look like?

35

slide-36
SLIDE 36

Thank you very much for your attention.

http://www.dfki.de/omm-tools/

slide-37
SLIDE 37

Benefits

  • Open data storage

– Communicate with open-loop partners – Standardized formats and proprietary extensions

  • Self-explaining objects

– Object-related information attached to physical object – Replace paper documentation – Define monitoring conditions – Maintenance data

  • Maintenance data attached to product

– Retrospective – Spare parts

37

slide-38
SLIDE 38

Benefits

  • Object memory data storage location

– On-object for high value products – Off-object for low cost products – Arbitrary hybrid solutions possible – Communication via standardized web techniques

  • Versatile applications for object memories

– Raw materials – Machinery – Goods – Hierarchical solutions

38

slide-39
SLIDE 39

Benefits

  • Object memory as storage space for snippets
  • Secure sandbox execution
  • Update Snippets via AppStore

– Subsequent parameter adjustment

  • Object-related logic (lot size one)

– Integrity Check

  • Autonomous/independent monitoring

– Independent Object Monitoring

39