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

Slides:

Advertisements

Similar presentations

oneM2M and AllJoyn Interworking

Advertisements

ETSI M2M / TIA architecture harmonization O. Elloumi.

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

Test WG (WG6) 2015 Planning TST 15 Source: JaeSeung Song, TST WG Convenor (TTA), Meeting Date: TST WG6_2015_planning.

A Proposal of “Common Information Model” for HEMS domain

OneM2M Draft proposal for slide set. This is not intended to be a oneM2M presentation. It is a collection of source material slides which can be used.

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

ETSI Home Networking activities Rainer Münch ETSI TISPAN Chairman Presenter: Ian Spiers DOCUMENT #:GSC13-GTSC6-20r1 FOR:Presentation SOURCE:Rainer Münch,

TST WG Progress Report at TP 18 Group Name: TST WG Source: TST WG Chair, JaeSeung Song (KETI) Meeting Date: to Agenda Item: TP18,

Multi-Link Devices Group Name: WG1 Source: Kaonmedia, KETI Contact: Hwang Kwang Tae Yong-Suk Park

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,

Step by step approach Group Name: WG2

Focus on developing RESTful API Group Name: TP Source: Shingo Fujimoto, FUJITSU (TTC), Meeting Date: Agenda Item:

Discussion on Time Series Data Group Name: WG2 Source: Qi Yu, Mitch Tseng- Huawei Technologies, Co. LTD. Meeting Date: Work Item :WI-0033.

End-to-End security definition Group Name: SEC WG4 Source: Phil Hawkes, Qualcomm, Meeting Date:

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

\ 1 Presentation for SC25 WG1 N1651 RC (Residential Complex) -EMS for HES Wanki Park ETRI, Korea Ilwoo Lee (ETRI, Korea) ISO/IEC.

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.

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

Considerations on M2M URIs Group Name: WG2(ARC) Source: Yong-Suk Park, Sung-Chan Choi, Jaeho Kim, KETI, Meeting Date:

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

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

Step by step approach Group Name: WG2 Source: Michael hs. Yang, LG uplus, Jaeseung Song, NEC Europe, Meeting.

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.

Ontology Resource Discussion

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

1 HGI MESSAGE TO ONEM2M TECHNICAL PLENARY HANS WERNER BITZER, DEUTSCHE TELEKOM VICE CHAIR, HGI ONEM2M TP#19, SOPHIA ANTIPOLS, FRANCE.

TST WG Progress Report at TP 19 Group Name: TP Source: TST WG Chair, JaeSeung Song (KETI) Meeting Date: to Agenda Item: TP19, Item.

Scenarios for oneM2M and OIC Interworking

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

Supporting Time Series Data Group Name: WG2 Source: Qi Yu, Mitch Tseng- Huawei Technologies, Co. LTD. Meeting Date: Work Item :WI-0033.

Management of Semantic Instances in resources using SPARQL update operation with HTTP verbs Group Name: MAS 19 Source: Minwoo Ryu, jaeho Kim, Sungchan.

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

Release Timeline Discussion R2 and beyond Group Name: TP_WPM Source: Roland Hechwartner, WPM Convenor, Meeting Date:

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

OneM2M Partnership Project. Contents Introduction Founding Partners Participation Scope & Objectives Structure Deliverables Contacts © 2013 oneM2M Partners.

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

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:

TST WG Progress Report at TP 18 Group Name: TP Source: TST WG Chair, JaeSeung Song (KETI) Meeting Date: to Agenda Item: TP18, Item.

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

Way Forward of Abstract Information Model (Mapping Model with Resource Structure) Group Name: WG2 Source: Heedong LG Electronics.

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

Introduction to oneM2M OMA - oneM2M Meeting, San Diego, Jan. 19th 2016

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

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

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

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

2 nd oneM2M Interoperability Event Prof. Song JaeSeung (KETI, TST WG Chair) TST Introduction-to-2 nd -interop-event.

Discussion for Testing related Activities Group Name: TP Source: JaeSeung Song, KETI, Meeting Date: Agenda.

TST R01-MBT_for_test_suites_development Use of MBT for test suites development- discussion Group Name: TST WG Source: Easy Global Market (EGM)

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

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

TST MBT_for_test_suites_development Use of MBT for test suites development- discussion Group Name: TST WG Source: Easy Global Market (EGM) Meeting.

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:

Status of Active Work Items Level of Completeness

SEMANTICS OF SMART APPLIANCES INITIATIVE Presenter

Proximal IoT Interworking discussion

Possible options of using DDS in oneM2M

WPM ad-hoc group report TP#24

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

Release Timeline Discussion R2 and beyond

WPM ad-hoc group report TP#25

Considering issues regarding handling token

TTA M2M Activities & Proposal of revised resolution

SMART HOME Expectation IN STANDARDS

Presentation transcript:

Work for the next release Group Name: TP Source: JaeSeung Song, KETI, Jaeho Kim, KETI, Snagho Choi, SK Telecom, Michael hs. Yang, LG uplus, Jungsoo Park, ETRI, Jaeho Han, nTels, Kyunggeun Kim, KCA, Hong Soo Yoon, Kaonmedia, Meeting Date: Agenda Item: Discussion TP R01-Home_domain_work_for_the_next_release

Some Voices from the Markets Will oneM2M release specifications soon? YES Will oneM2M standard specs. can be used in a specific vertical? (e.g., Home Automation) ??? What should we do if we have some features that need to be standardized? ??? When oneM2M will start work for the next release? ???

Purpose Stimulate discussion on work for the next release. – What should we do? – Which work items we require? – When actually should we (WG1) start? – How various verticals can be involved? Decide a way forward to convince IoT/M2M related markets that oneM2M will keep standardizing and delivering various standard specifications on the following aspects: – Functions optimizing the first release; – Advanced/Enhanced features; – Functions for verticals

Why Home domain? One of main IoT/M2M verticals. Many home appliance vendors have already started to launch IoT/M2M services based on their own platform. ETSI Smart M2M is now working on defining ontology for home appliance energy efficiency. The MAS group handles many semantic issues on the Home domain. The MAS group may study defining ontology for a specific domain and analyse how ontology from a specific vertical can be used in oneM2M  likely the Home domain

Are there many missing features? We don’t know yet. But we also don’t know our release 1 specification is enough to be used in a vertical system? Here are some example use cases that possible can be discussed: – Device paring – Caching temporarily unused devices – Detection of inconsistencies – Device and Gateway replacement

Some Use Cases (1) – Paired devices IoT/M2M system CSEBase Node2 Node1 Refrigerator (Node 1) Smart plug for Refrigerator (Node 2) Application Others.. Application Others.. Data for the sam e device (i.e., ref rigerator) but fro m the two differ ent devices. Better to manag e these devices a s a single device. Data for the sam e device (i.e., ref rigerator) but fro m the two differ ent devices. Better to manag e these devices a s a single device.

Some Use Cases (2) – Device caching CSEBase Application 2 (device 2) Application 1 Node 2 (device 2) SUMMER Application 2 (device 2) Node 1 (device 1) Resource bin Application 2 (device 2) Node 2 (device 2) Application 2 (device 2) WINTER

Some Use Cases (3) – Consistency t=0 t=10 IoT/M2M system CSEBase Node2 Node1 Application Others.. Application Others.. Node3 Application Others..

Some Use Cases (4) – Replacement Replace because of low battery Replace gateway because a user finds a better one Siren Gateway

Proposal Select the Home Automation and Control domain as a target vertical that will be studies and standardized in the upcoming oneM2M release: – WG1: standardizes uses cases and requirements specifically related to Home Automation and Control – WG2: standardizes architecture aspect supporting the home related requirements – WG3: standardizes protocol specifications – WG4: studies and analyses necessary security mechanisms if existing security features are not enough – WG5: standardizes ontology and semantics for Home Appliances and Energy management

Proposal (Cont.) How to progress? Options: – Option 1: Create an umbrella vertical work item covering multiple working groups (preferred) – Option 2: Use existing WI (TRes & TSes) – Option 3: Create individual work items once they are required.