Example mapping of KNX to oneM2M base Ontology

Slides:

Advertisements

Similar presentations

1 The 2-to-4 decoder is a block which decodes the 2-bit binary inputs and produces four output All but one outputs are zero One output corresponding to.

Advertisements

CDA 3100 Recitation Week 10.

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

Section 10.3 Logic Gates.

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

On a Device Information Model for devices in oneM2M

KNX – ZigBee Gateway for Home Automation

Device Management using mgmtCmd resource

On Management, Abstraction & Semantics

Star I Controller Input/Output Numbering on Controller and MIRO Devices.

oneM2M-OIC Interworking Technical Comparison

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

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

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.

Management of CMDH Policies Group Name: WG5-MAS Source: Wolfgang Granzow, Qualcomm, Meeting Date: Agenda Item: Management.

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

Experience and Discussion on Interworking Proxy Implementation Group Name: WG2 Source: Korea Electronics Technology Institute (KETI) Meeting Date: ~24.

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.

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

Ontology Resource Discussion

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

OIC device management interworking procedure

OIC INTERWORKING OPERATIONAL PROCEDURE (ADDRESSING AND DISCOVERY) Group Name: Architecture WG Source: Kiran Vedula, Samsung Electronics,

LWM2M Interworking Group Name: Architecture

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

ARC R02 Modelling operations – problem statement and proposal Group Name: ARC#19.3 Source: Joerg Swetina, NEC,

© 2015 oneM2M Enrico Scarrone oneM2M Steering Committee Vice Chair M2M/IoT standard coordination-Telecom Italia ONEM2M INTERWORKING.

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

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

OIC INTERWORKING Resource mapping

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:

Streaming Session Support in oneM2M Framework Group Name: WG2 Source: George Foti, Ericsson Meeting Date: Work Item :WI GPP_Rel13_IWK.

3GPP SCEF Interworking Discussions

LWM2M Interworking Proxy Procedures ARC Considerations

Issues of Current Access Control Rule and New Proposal Introduction Group Name: ARC 21 Source: Wei Zhou, Datang, Meeting Date:

WG1 status report to TP#20 Group Name: oneM2M TP20 Source: Joerg Swetina (NEC) Meeting Date: to Agenda Item: TP#19, Item 10.4, Reports.

FUCTIONAL ARCHITECTURE FOR OIC INTERWORKING Group Name: Architecture WG Source: Jieun Keum, Samsung Electronics,

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

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.

Possible Solution of Interworking between oneM2M and OSGi

Introduction to Service Session Management Group Name: WG2-ARC Source: IDCC, LGE, ZTE Meeting Date: TP8 Agenda Item:

Specifying the Address of Management Client of Managed Entity Group Name: ARC Source: Hongbeom Ahn, SK Telecom, Meeting Date: TP#21 Agenda.

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

FUCTIONAL ARCHITECTURE FOR OIC INTERWORKING Group Name: Architecture WG Source: Jinhyeock Choi, Samsung Electronics,

Semantics in oneM2M MAS Group Name: MAS

How does Generic Interworking work?

Dimmer 6fold 10V Actuator M/DA

Group multicast fanOut Procedure

Modbus interworking Group Name: ARC

ABB STOTZ-KONTAKT GmbH ABB i-bus® KNX Room Master, Premium, RM/S 2.1

Discussion on Abstraction Application Entity

Proposed design principles for modelling interworked devices

ABB STOTZ-KONTAKT GmbH ABB i-bus® KNX Room Master, Basic, RM/S 1.1

OneM2M-ARC BRequest_Resource Architecture Proposal to address Broadcasting/Multicasting Requirements Group Name: WG2 Source: Takanori Iwai,

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

DMX512 Gateway M/DMX512.1.

3GPP Interworking Abstraction

ARC Proposed design principles for modelling services, datapoints and operations Group Name: ARC Source: Joerg Swetina, NEC

MOSFET Dimmer Actuator

LWM2M Interworking with <mgmtObj> Resources

ABB i-bus® KNX The new I/O-Actuators IO/S and IO/S

Presentation transcript:

Example mapping of KNX to oneM2M base Ontology MAS-2015-0618 Example mapping of KNX to oneM2M base Ontology Group Name: MAS#19 Source: Joerg Swetina, NEC, joerg.swetina@neclab.eu Meeting Date: 2015-09-07 Agenda Item: <agenda item topic name>

The KNX system KNX (by KNX Association) provides control technology for home and building applications Devices implement “Distributed Applications” Based on Datapoints that are grouped into Functional Blocks One or more functional blocks form a device Datapoints Represent process and control variables in the system May be: Inputs, Outputs, parameters, diagnostic data, … MAS-2015-0618

The KNX system (II) Functional blocks group a number of inputs, outputs and parameters. For this combination, a mandatory function description is provided Functional block of one or more devices are addressed as “group objects”, using multicast group addressing or individual device addresses MAS-2015-0618

Example: a KNX dimmer Functional Block – Dimming Actuator Basic (has been standardized). It contains DPTs: Switch, DPT 1.001 Relative dimming, DPT 3.007 Absolute dimming, DPT 5.001 MAS-2015-0618

DPT 1.001: 1 Bit DTP for on/off MAS-2015-0618

DPT 3.007: 3 Bit DTP with Control Note: similar DPT 3.008 (also 4 bit: B1U3) is called “DPT_Control_Blinds” MAS-2015-0618

DPT 5.001: 8 Bit unsigned value MAS-2015-0618

Mapping KNX ontology into base ontology “is-a” relationship between base ontology and “KNX ontology” “Dimming actuator basic” is-a Device Service: “default” Functionality: “dimming-control” refers to Aspect: “Electricity-Current” Operations DPT 1.001 DPT 3.007 DPT 5.001 Commands Switch Relative Dimming Absolute Dimming MAS-2015-0618

E.g.: command “relative dimming” operation DPT 3.007 Input InputBit4 hasDataTypeAndRange: Binary InputBits1-3 hasDataTypeAndRange: Integer [>=0, <=7] (no output) OperationState The dimmer itself does not provide state information The IPE could provide state of interworking (see next slide) MAS-2015-0618

KNX interworking via IPE IPE proxies KNX Device into proxied Device Middle Node KNX Device Area Network Interworking Proxy Entity (IPE) CRUDN AE <AE> of proxied device Mca <AE> IPE could provide interworking specific operation state info: "Operation_Initiated", "Operation_Input_ received", "Operation_Ended" MN-CSE attribute attribute <container> <container> For data (e.g. state-information) For commands For input/output parameters For state info <container> <container> MAS-2015-0618