Introducing concept of M2M-application data modeling Group Name: MAS Source: FUJITSU Meeting Date: 2015-07-20 Agenda Item: Semantics and Device Configuration.

Slides:

Advertisements

Similar presentations

SEC Clarification Group Name: WG4 (SEC-2014-xxxx) Decision  Meeting Date: Discussion  Source: OBERTHUR Technologies Information  Contact:

Advertisements

A Proposal of “Common Information Model” for HEMS domain Group Name: MAS WG Source: Yoshihisa Ito, Takefumi Yamazaki,

Copyright © Clifford Neuman - UNIVERSITY OF SOUTHERN CALIFORNIA - INFORMATION SCIENCES INSTITUTE USC CSci599 Trusted Computing Lecture Six –

A Proposal of “Common Information Model” for HEMS domain

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

Conflict Management Group Name: WG1 Source: KETI, ETRI, SK Telecom, nTels, KCA, Kaonmedia Meeting Date: dd Agenda Item: Discussion.

Mechanism to support establishment of charging policies Group Name: WG2-ARC Source: InterDigital Meeting Date: TP8 Agenda Item:

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.

Optimized M2M interworking with mobile networks Group Name: oneM2M REQ Source: Takanori Iwai, NEC, Meeting Date: Agenda.

An Operators Input for oneM2M Baseline  Group name: TP#2/WG1  Source: DTAG, Vodafone Group  Meeting Date:  Agenda Item: WG1 agenda item.

Introduction of PRO WG activities Group Name: TP Source: Shingo Fujimoto, FUJITSU, Meeting Date: Agenda Item:

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

Lockheed Martin Aeronautics Company Candidate Collaborative Projects for Net-Centric Application Michael F. Siok, PE Lockheed Martin Aeronautics Company.

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.

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

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

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

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.

Proposal for WG3 & WG5 work area split

Work for the next release Group Name: TP Source: JaeSeung Song, KETI, Jaeho Kim, KETI,

Primitive End-to-End Security Requirements Group Name: SEC WG4 Source: Phil Hawkes, Qualcomm, Meeting.

Ontology Resource Discussion

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:

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.

Summary of main questions on the Partnership Agreement and the secretariat support.

M2M Service Subscription Profile Discussion Group Name: oneM2M TP #19.2 Source: LG Electronics Meeting Date: Agenda Item:

App and Management End- to-End Security Requirements Group Name: SEC WG4 Source: Phil Hawkes, Qualcomm,

Introducing Event handler Group Name: SEC & ARC Source: FUJITSU Meeting Date: Agenda Item: Device Configuration.

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

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

Security API discussion Group Name: SEC Source: Shingo Fujimoto, FUJITSU Meeting Date: Agenda Item: Security API.

App End-to-End Security Requirements Group Name: SEC WG4 Source: Phil Hawkes, Qualcomm, Meeting Date:

Admin API for Secure Environment Group Name: SEC Source: Giesecke & Devrient 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.

Status of Active Work Items Level of Completeness Group Name: WPM Source: Roland Hechwartner, WPM Convenor Updated:

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

Adding Non-blocking Requests Contribution: oneM2M-ARC-0441R01R01 Source: Josef Blanz, Qualcomm UK, Meeting Date: ARC 7.0,

Consideration Security Issues on Registration Group Name: WG4 (SEC) Source: Shingo Fujimoto, FUJITSU, Meeting Date:

Introducing concept of M2M-application data modeling Group Name: MAS Source: FUJITSU Meeting Date: Agenda Item: Semantics and Device Configuration.

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:

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.

Directions for Release 3 Group Name: SEC Source: NEC Europe Ltd. Meeting Date: SEC22, Agenda Item: Discuss directions.

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

Possible options of using DDS in oneM2M Group Name: ARC Source: KETI, Huawei, Hitachi, China Unicom Meeting Date: Agenda Item: DDS binding.

Introducing User’s Role concept Group Name: WG2(ARC) and WG4(SEC) Source: Shingo Fujimoto, FUJITSU, Meeting Date:

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

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

Internet Of Things (IoT)

Managing The Internet of Things

Group multicast fanOut Procedure

3GPP interworking in R3 Group Name: ARC

Possible options of using DDS in oneM2M

Modbus interworking Group Name: ARC

WPM ad-hoc group report TP#24

Discussions on Heterogeneous Identification Service

WPM ad-hoc group report TP#25

Considering issues regarding handling token

New WI on Industrial Domain Information Model

New WI on Industrial Domain Information Model

Artem A. Nazarenko, Joao Sarraipa, Paulo Figueiras,

Topic 1: Be able to combine functions and determine the resulting function. Topic 2: Be able to find the product of functions and determine the resulting.

Presentation transcript:

Introducing concept of M2M-application data modeling Group Name: MAS Source: FUJITSU Meeting Date: Agenda Item: Semantics and Device Configuration

Topic Summary The preparation of the data content is responsibility of the field domain entities, but that makes difficult to integrate collected data. oneM2M should provide mechanism to instruct the field domain entities which data is prepared. Proposal of ‘collected data centric model’: – MAS group discussed on modeling device capabilities deeply, but modeling for combined data from multiple device or partial data within device is not covered yet. – ‘collected data’ is the destination of M2M data collection (‘device model’ is the source of it) MAS R01 2

Use Case: IoT Platform HEMS Application Home Automation Application Adaptor + Interests on: Energy Consumption, Switch-Status Interests on: Switch-status, SW-control, Place MAS R01 3

Potential Problem IoT Platform HEMS Application Home Automation Application Adaptor + Interests on: Energy Consumption, Switch-Status Interests on: Switch-status, SW-control, Place May not have remote-control capability May not be compatible with others Could be Propriety Solution MAS R01 4

Assumed use of IoT Platform HEMS Application Home Automation Application Adaptor + Interests on: Energy Consumption, Switch-Status Interests on: Switch-status, SW-control, Place Containers for HEMS Containers for HA They can be separated MAS R01 5

Retrieve partial data SensorPlatformService App RESISTER (with available data components ) NOTIFY (available data components) Request to configure Device (desired data components [partial]) Configure Device Setting (desired data components) CREATE to store collected data from Device CREATE at instructed Apply setting to produce desired data MAS R01 6

Retrieve data from two dev. Sensor-1PlatformService App Request to configure Virtual Device (desired data components) Configure Sensor-1 Setting (desired data component-1) CREATE at instructed Sensor-2 Configure Sensor-2 Setting (desired data component-2) CREATE at instructed Combine data containers into single data at Access to combined as Virtual Device (desired data components) MAS R01 7

Proposals Adding (producing) data modeling in scope of MAS discussion Adding potential requirement regarding ‘data modeling’ MAS R01 8

Potential Requirements M2M Platform shall be able to collect data from M2M Device, with specifying desired data components. M2M Devices shall be able to provide available data components. MAS R01 9