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

Slides:

Advertisements

Similar presentations

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

Advertisements

Testing the Usability of Paper Prototype Interfaces Christine Julien, PhD and Seth Holloway, PhD Candidate The University of Texas at Austin IRB#

Release 2: Work Items best practices Group Name: TP15 Source: Scarrone Enrico, Telecom Italia Meeting Date:

Protecting people, property and the environment Protect Who You Most Care About Fit Automatic Fire Sprinklers.

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

590ES1 Design of Plant Care System Mike Swift Steve Swanson Stefan Bjarni Sigurdsson.

A Proposal of “Common Information Model” for HEMS domain

HACS HOME IN YOUR POCKET. Today’s Topic User Interaction User Interaction User Authentication User Authentication Database Database Design of Devices.

Gaylen Atkinson March 16, AGENDA Market Potential Customer Need Tridium Solution Benefits to Users Customer “Hot” Buttons Product Offerings How.

Technology and Hotel Security Hotel Mgmt. Hospitality Services R. McCann.

OneM2M portal introduction Group Name: Technical Plenary Source: Gerry McAuley, ETSI, Meeting Date: Agenda Item: 1.5.

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

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,

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

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

Home Control and Monitoring for Ambient Assisted Living Project Description and Demonstration Martin Moghadam – Kalle Grafström – Kristoffer Ravnholt.

OneM2M-REQ R03 Proposed simple guidelines for writing use cases and requirements Group Name: oneM2M WG1 / WG2 Source: Joerg Swetina (NEC), Ataru.

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

In-Band Access Control Framework Group Name: WG4 SEC Source: Qualcomm Meeting Date: Agenda Item:

An operator’s perspective on support for different M2M deployment scenarios AT&T Group Name: TP Source: Farooq Bari, Jianrong Wang; AT&T;

Testing the Usability of the SEEU System Seth Holloway, PhD Candidate Christine Julien, PhD The University of Texas at Austin IRB#

App-ID Discussion Group Name: ARC WG Source: Seongyoon Kim, LG Electronics, Meeting Date: 31 July 2014 Agenda Item: TBD.

Setting oneM2M’s Market direction

 Problem Definition  Presented by Sushant and Alex Overview of the problem space Scenario Issues Example (plant care example) Discussion conclusion open.

Discussion on the problem of non- Blocking Synchronous mode Group Name: ARC WG Source: Yuan Tao, Mitch Tseng, Huawei Technologies Meeting Date: ARC 15.2.

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

Work Programme Management Ad hoc Group Report Group Name: one M2M TP13 Source: Convenor WPM Nicolas Damour, Meeting Date:

Technical questions on oneM2M certification Group Name: TST Source: JaeSeung Song KETI, TST WG Chair Meeting Date: Agenda.

TP WG1 status report to TP#16 Group Name: oneM2M TP16 Source: Shelby Kiewel (iconectiv) Meeting Date: to Agenda Item: TP#16,

Potential use case for discussion – Street Light Automation Group Name: WG1/2 Source: Cisco Meeting Date: Joint-REQ-ARC-WGs-call Agenda Item: Use cases.

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

Scenarios for oneM2M and OIC Interworking

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

WG 2 Progress Report at TP#9 Group Name: oneM2M TP #9 Source: WG2 leadership Meeting Date: /21 Agenda Item: WG Reports.

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

Ronald J. Zimmer CAE President & CEO Continental Automated Buildings Association LinkedIn Profile M2M Canada: Driving the Machine to.

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

Doc.: IEEE yy/xxxxr0 Submission 11/0191r0 Month Year Tom Siep, CSRSlide 1 Use Case Discussion Date: Authors: ai.

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

OIC INTERWORKING Resource mapping

WG1 status report to TP#21 Group Name: oneM2M TP21 Source: Shelby Kiewel (iconectiv) Meeting Date: to Agenda Item: TP#21, Item 10.4,

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

Attribute-level access control Group Name: ARC WG Source: Yuan Tao, Mitch Tseng, Huawei Technologies Meeting Date: ARC 16 Agenda Item: TBD.

A discussion on Release duration TP #14 Source: JaeSeung Song, KETI (TTA), Meeting Date: TP Discussion_on_Release_duration.

Feedbacks on oneM2M certification Group Name: TP Source: JaeSeung Song KETI, TST WG Chair Meeting Date: Agenda Item:

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

Authorization Architecture Discussion Group Name: SEC WG Source: Seongyoon Kim, LG Electronics, Meeting Date: 28 MAY, 2014 Agenda.

Home Device Caching & Replacement Group Name: WG1 Source: KETI, ETRI, SK Telecom, nTels, KCA, Kaonmedia Meeting Date: dd Agenda Item: Discussion.

Subscription and Notification Issue Group Name: WG2 Source: Qi Yu, Mitch Tseng- Huawei Technologies, Co. LTD. Meeting Date: ~23 Agenda Item:

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

DM Collaboration – OMA & BBF: Deployment Scenarios Group Name: WG5 - MAS Source: Tim Carey, ALU, Meeting Date:

WG1 - REQ Progress Report at TP #11 Group Name: WG1 REQ (Requirements) Source: WG1 Vice Chairs Meeting Date: to Agenda Item: TP#11,

Environment Care System -- Home Automation. Environment Care System Features Air quality data live indicate on the control terminal Detect available with.

Jeju, 13 – 16 May 2013Standards for Shared ICT TTA M2M Activities & Proposal of revised resolution Peter J. Kim, Principal Specialist, TTA Document No:

The reading is 7.38 mm. The reading is 7.72 mm.

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

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

Methods of Work Report Group Name: TP#10 Source: Enrico Scarrone, Telecom Italia, Meeting.

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

Sensors Control Systems with Flowol.

Provisional Architecture for oneM2M

Why Box Cameras are still Cool?

Possible options of using DDS in oneM2M

Discussion about Use Case and Architecture in Developer Guide

WG1 status report to TP#15 Group Name: oneM2M TP15

Invite IIC testbeds to oneM2M interops

Considering issues regarding handling token

TTA M2M Activities & Proposal of revised resolution

Houseplants Project By:.

Presentation transcript:

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

Introduction Conflict management scenarios – On the Same resource – Multiple resources Derive requirements for the common service platform from home domain use cases and Study advance/enhanced features for the next oneM2M release related with the conflict management scenarios

Conflict management on the same resource Sunshine Sensors: detect temperature and light levels App2App1 Rule: control based on light and heat level Rule: control based on times Concurrency conflict Automated Blind Control prerequisite Resolution

Conflict management associated with multiple resources Fire System Flood System M2M Application 1 Fire Detection M2M Application 2 Flood Detection Fire detection Sensor Sprinkler Actuators Water detection Sensor Water main Actuators Harmonize/orchestrate resource conflict Priority Policy Fire detection Water detection Sprinkler Water controller Detect fire Activate sprinklers Detect water Activate closing water main