Release Timeline Discussion R2 and beyond Group Name: TP_WPM Source: Roland Hechwartner, WPM Convenor, Meeting Date: 2015-11-12.

Slides:



Advertisements
Similar presentations
Technical Plenary From: oneM2M TP leadership Source: Meeting Date: Agenda Item:
Advertisements

oneM2M and AllJoyn Interworking
Methods Of Work Ad hoc Report TP#11 Source: Enrico Scarrone, Telecom Italia, Meeting Date:
WG5 - MAS Progress Report at TP #17 Group Name: WG5 MAS (Management, Abstraction & Semantics) Source: Yongjing Zhang (Huawei, WG5 Chair) Meeting Date:
CURRENT STANDARDIZATION ACTIVITIES – ONEM2M GSC-18 Meeting, July 2014, Sophia Antipolis, France Document No: GSC(14)18_012 Source: ETSI Contact:
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.
Authors list to be completed.
Authors list to be completed.
Progressing the Work on the MAS TR-0006, TR-0007 Group Name: Management Abstraction and Semantics Source: Tim Carey, ALU,
Requirements Overview Group Name: Technical Plenary (TP19) Source: Shelby Kiewel, iconectiv, Meeting Date: Agenda Item:
Discussions for oneM2M Semantics Standardization Group Name: WG5 Source: InterDigital Communications Meeting Date: Agenda Item: WI-0005 ASN/MN-CSE.
An Operators Input for oneM2M Baseline  Group name: TP#2/WG1  Source: DTAG, Vodafone Group  Meeting Date:  Agenda Item: WG1 agenda item.
Status of Active New Work Items Group Name: WPM Source: Karen Hughes, ETSI Updated:
Report of co-conveners WG1/WG2 meetings between TP1 and TP2 Group Name: Technical Plenary #2 Source: Omar Elloumi, Alcatel-Lucent,
Status of Active New Work Items Group Name: WPM Source: Karen Hughes, ETSI Meeting Date:
3GPP Rel-13 Interworking discussions
HGI activities transfer to oneM2M Group Name: MAS Source: Patricia MARTIGNE (Orange), Deutsche Telekom, Telecom Italia Meeting Date: Agenda.
Work Programme Management Ad hoc Group Report Group Name: one M2M TP9 Source: Convenor WPM Joachim Koss, Gemalto M2M,
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
MoW&M&P Report Group Name: TP19 Source: MoW Convenor, Enrico Scarrone, Telecom Italia, Meeting Date:
Group Name: oneM2M WG1 Requirements Source: Phil Hawkes, Rapporteur “Benefits of oneM2M technology” TR,
WG1 status report to TP#17 Group Name: oneM2M TP17 Source: Shelby Kiewel (iconectiv) Meeting Date: to Agenda Item: TP#17, Item 10.3,
Work Group / Work Item Proposal Slide 1 © 2012 oneM2M Partners oneM2M-TP oneM2M_Work_Group_Work_Item_Proposal Group name: Technical Plenary Source:
WG5 - MAS Progress Report at TP #9 Group Name: WG5 MAS (Management, Abstraction & Semantics) Source: Yongjing Zhang, Chair, Meeting.
Customized Resource Types MAS Group Name: MAS + ARC + PRO WGs Source: Wolfgang Granzow, Qualcomm Inc., Meeting Date:
WPM ad-hoc group report TP#17 closing Group Name: WPM (TP adhoc) Source: convener WPM Roland Hechwartner, Meeting Date:
TP WG1 status report to TP#16 Group Name: oneM2M TP16 Source: Shelby Kiewel (iconectiv) Meeting Date: to Agenda Item: TP#16,
WG 2 Progress Report at TP#9 Group Name: oneM2M TP #9 Source: WG2 leadership Meeting Date: /21 Agenda Item: WG Reports.
Discussion for the next oneM2M release Group Name: TP Source: JaeSeung Song, KETI, Jaeho Kim, KETI,
3GPP Rel-13 Interworking discussions
WG-2 - ARC TP #18 Status Report Group Name: oneM2M TP #18 Source: WG2 Chair (Nicolas Damour – Meeting Date: Agenda.
Release Timeline Discussion R2 and beyond Group Name: TP_WPM Source: Roland Hechwartner, WPM Convenor, Meeting Date:
Architectural Considerations for Semantic Support Group Name: WG5 Source: Martin Bauer (NEC), Joerg Swetina (NEC) Meeting Date: Agenda Item:
Group Name: oneM2M WG1 Requirements Source: Phil Hawkes, Rapporteur “Benefits of oneM2M technology” TR,
WG5 – MAS#19 Status Report Group Name: WG5 MAS (Management, Abstraction & Semantics) Source: Yongjing Zhang (Huawei, WG5 Chair) Meeting Date:
SEC #11 WG4 Status & Release 1 Outlook Group Name: Source:,, Meeting Date: Agenda Item:
WG1 status report to TP#21 Group Name: oneM2M TP21 Source: Shelby Kiewel (iconectiv) Meeting Date: to Agenda Item: TP#21, Item 10.4,
WG5 – MAS#21 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 Group Name: WPM Source: Roland Hechwartner, WPM Convenor Updated:
A discussion on Release duration TP #14 Source: JaeSeung Song, KETI (TTA), Meeting Date: TP Discussion_on_Release_duration.
WG2 - ARC TP #20 Status Report Group Name: oneM2M TP #20 Source: WG2 Chair (Nicolas Damour – Meeting Date: Agenda.
Call for input from WGs on things to test Group Name: TST Source: Jiaxin Yin, Huawei Technologies Co., Ltd., 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.
Technical Plenary Terms for the collaboration with P2413 From: oneM2M TP Chair Source: Meeting Date: Agenda Item:
WG5 – MAS#22 Status Report Group Name: WG5 MAS (Management, Abstraction & Semantics) Source: Tim Carey(Alcatel-Lucent, WG5 Vice Chair) Meeting Date:
Status of Active Work Items Summary Group Name: TP Source: Roland Hechwartner, WPM Convenor Updated: source: TP_WPM R08-New_Work_Item_Status_Report.
WPM ad-hoc group report TP#20 Group Name: WPM (TP adhoc) Source: convener WPM Roland Hechwartner, Meeting Date:
Reasons for CSF Clean-up (Issues & Next Steps) Group Name: WG2 Source: Syed Husain – NTT DOCOMO Meeting Date: (ARC_9.3) Agenda Item: 6 DOC#:
Group Name: oneM2M WG1 Requirements Source: Phil Hawkes, Rapporteur “Benefits of oneM2M technology” TR,
Methods of Work Report Group Name: TP#10 Source: Enrico Scarrone, Telecom Italia, Meeting.
3GPP Rel-13 Interworking discussions Group Name: TP #18 Source: Rejesh Bhalla, ZTE Corporation, Meeting Date: Agenda Item:
What is oneM2M? 2 Covers: Requirements Architecture API specifications Security Interoperability Facilitate, implement and promote IoT.
WG5 – MAS#23 Status Report Group Name: WG5 MAS (Management, Abstraction & Semantics) Source: Yongjing Zhang (Huawei, WG5 Chair) Meeting Date:
WG5 – MAS#24 Status Report Group Name: WG5 MAS (Management, Abstraction & Semantics) Source: Yongjing Zhang (Huawei, WG5 Chair) Meeting Date:
ONEM2M RELEASE 2: SETTING THE STANDARD FOR IOT INTEROPERABILITY
Status of Active Work Items Level of Completeness
CSE Retargeting to AE, IPE, and NoDN Hosted Resources
CSE Retargeting to AE, IPE, and NoDN Hosted Resources
Proximal IoT Interworking discussion
3GPP interworking in R3 Group Name: ARC
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
Overview onem2m.org.
Overview onem2m.org.
Status of Active New Work Items
Current standardization activities – oneM2m
Presentation transcript:

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

Timeline for Release 2 & beyond Release 2 timeline as discussed and agreed (see slide 4) – oneM2M Release 2 Features As discussed in interim TP and WPM session during TP#20 meeting week – Final assessment based on R2 content at TP#22 i.e. after stage 2 freeze (TP#21) Timing considerations for R2 => R3* (see slide 3) – Based on MoW guideline for workflow amongst releases oneM2M Method_of_Work-V (see Backup) Initiate discussion on duration of Release 3* (see slide 5) – Proposal for discussion Initial brief discussion in WPM – Further assessment of timeline (scope - duration) of R3* at Stage 3 freeze of release 2 (TP#23) * Release beyond Release 2 © 2015 oneM2M Partners TP WPM R02 2

3 oneM2M release 2 features Industrial domain enablement (at least 1 normative feature) Time series, etc. In conjunction with the TR oneM2M Beyond initial release Semantic interoperability base ontology semantic discovery semantic descriptions Security Enhancement for authorization privacy support e2e security (?) oneM2M interworking framework Generic interworking AllJoyn/AllSeen and/or OIC and/or OMA LightWeight M2M (OMA LWM2M) and/or 3GPP Rel.13 Interworking Home domain enablement (at least 1 normative feature) Home appliance information models APP identifiers and registry services Advanced protocol binding WebSocket (?) Efficient content representations (?)

Release Timeline R2 normative work JulAugSepOctNovDecJanFebMarAprMayJunJulAugSep Stage 1 R3 non-normative work R3 normative work Stage1 Freeze R2 normative work Stage 2 R3 non normative work R3 normative work R2 normative work Stage 3 R3 normative work Stage3 Freeze TP24 R3 start norm work OctNov TP25 Stage2 Freeze TP18TP19TP20TP21TP22TP23 R2 approval R2 ratification TP26 ARC 19.4 © 2015 oneM2M Partners TP WPM R02 4 Release 2 Release 3 Color Code R2 R3 Review of R2 timeline Review of R3 timeline

Release Timeline cont´d © 2015 oneM2M Partners TP WPM R02 5 R2 normative work Q3Q4Q1Q2Q3Q4Q1 Stage 1 R3 non-normative work R3 normative work R2 normative work Stage 2 R3 non normative work R3 normative work R2 normative work Stage 3 R3 normative work Stage3 Freeze 2015 TP24 R3 start norm work Q2Q3 Stage2 Freeze TP18TP21 R2 approval R2 ratification TP30 Q1Q2Q3Q TP meeting # Stage1 Freeze TP23 TP27 TP31 TP33 R3 Stage 1 freeze R3 Stage 2 freeze R3 Stage 3 freeze TP34 TP35 R3 approval R3 ratification Release 2 Release 3 Color Code Release 4 R4 - Start Normative Work R2 R4 R3

Release Timeline Proposal It is proposed to review this contribution in order to agree on the timeline for Release 2 – Including review and final assessment at TP#22 agree on an initial working assumption for the release beyond R2 (Release 3) – Further review and assessment at TP#23 * Release beyond Release 2 © 2015 oneM2M Partners TP WPM R02 6

Backup

Method of Work See also TP Method_of_Work-v1_3_2 The following guidelines are therefore given to govern the workflow among subsequent releases development (Release x+1 respect to Release x) : – Release x+1 stage 1 normative work cannot be initiated before the freezing of Release x stage 3 – Release x+1 stage 2 normative work cannot be initiated before the ratification of Release-x – Non normative work on stage 1 of Release x+1 can be performed at any time of Release x – Non normative work on stage 2 Rel x+1 can be performed after the freezing of stage 3 Release x – Testing is seen as an independent process not directly linked to the 3 stages model. these guidelines are general principles for all the Releases, the TP may decide different timelines for a specific release based on identified needs/opportunities. © 2015 oneM2M Partners TP WPM R02 8