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

Slides:

Advertisements

Similar presentations

WG 3 Progress Report at TP12 Group Name: oneM2M TP12 Source: Raymond Forbes, LM Ericsson, Meeting Date: to

Advertisements

Methods Of Work Ad hoc Report TP#11 Source: Enrico Scarrone, Telecom Italia, Meeting Date:

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

REQ WG Reuse of underlying networks, 3GPP

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

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

TST WG Progress Report at TP 17 Group Name: TST WG Source: TST WG Chair, JaeSeung Song (KETI) Meeting Date: to , Sapporo, Japan Agenda.

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:

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:

WG-2 - ARC TP #16 Status Report Group Name: oneM2M TP #16 Source: WG2 Chair (Nicolas Damour – Meeting Date: Agenda.

3GPP Rel-13 Interworking discussions

HGI activities transfer to oneM2M Group Name: MAS Source: Patricia MARTIGNE (Orange), Deutsche Telekom, Telecom Italia Meeting Date: Agenda.

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:

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

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

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:

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

WG 3 Progress Report at TP #7 Group Name: oneM2M TP #7 Source: Raymond Forbes, LM Ericsson, Meeting Date: /18 Agenda.

Status Report on Access TP8 Group Name: WG2 Decision  Meeting Date: Discussion  Source: OBERTHUR Technologies Information  Contact:

WPM ad-hoc group report TP#17 closing Group Name: WPM (TP adhoc) Source: convener WPM Roland Hechwartner, Meeting Date:

WG 3 Progress Report at TP15 Group Name: oneM2M TP15 Source: Raymond Forbes, LM Ericsson, Meeting Date: to

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.

SEC Conference calls following TP#11 Group Name: WG4 (SEC ) Decision  Meeting Date: Discussion  Source: OBERTHUR Technologies Information.

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

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

MoW&M&P Report Group Name: TP18 Source: MoW Convenor, Enrico Scarrone, Telecom Italia, Meeting Date:

3GPP Rel-13 Interworking discussions

Work Programme Management Ad hoc Group Report Group Name: one M2M TP7 Source: Convenor WPM Joachim Koss, Gemalto M2M,

ARC ordinary F2F meeting Seoul, June 2013 WG2 MEETING NOTES.

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:

PRO/ARC and TST/PRO joint sessions at TP20 Group Name: oneM2M TP20 Source: Peter Niblett, IBM Meeting Date:

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:

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:

WG 3 Progress Report at TP10 Group Name: oneM2M TP10 Source: Raymond Forbes, LM Ericsson, Meeting Date: to

WG2 - ARC TP #20 Status Report Group Name: oneM2M TP #20 Source: WG2 Chair (Nicolas Damour – Meeting Date: Agenda.

WG2 PRO Status Report at TP19 Group Name: oneM2M TP19 Source: Peter Niblett, IBM Meeting Date: to Agenda Item: TP19, Item 10.3, Reports.

Call for input from WGs on things to test Group Name: TST Source: Jiaxin Yin, Huawei Technologies Co., Ltd., Meeting Date:

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

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

TP WG1 - REQ Progress Report at TP #14 Group Name: WG1 REQ (Requirements) Source: WG1 Vice Chair (Joerg Swetina, NEC), Secretary Changho RYOO,

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#:

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

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:

Status of Active Work Items Level of Completeness

WG2 - ARC TP#29 Status Report

3GPP interworking in R3 Group Name: ARC

Possible options of using DDS in oneM2M

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

Release Timeline Discussion R2 and beyond

WPM ad-hoc group report TP#25

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

WG2 - ARC TP#29 Status Report

Status of Active New Work Items

Presentation transcript:

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 from Working Groups TP

Issues for DECISION in TP CR Packs – TP CR_to_TS- 0011_definition_of_Interworking_Proxy_Application_Entity_IPE © 2014 oneM2M Partners TP TP

Action Items for alignment in TP None © 2014 oneM2M Partners TP TP

Items for INFORMATION Agreed Path Forward on TS-0002 between Stage 1 and Stage 3 Freeze (any release … now X = 2) A)Requirement confirmed as normative, but not met in Release X-1 1.These requirements will remain in the main body of TS-0002, but be noted as “Targeted for Release X” (Regardless of if we think it will actually happen or not) B)Requirements “Partially Met in Release X-1” 1.These requirements will remain unchanged until after Stage 3 freeze of Release X 2.After Stage 3 freeze, these requirements will be reviewed for inclusion in Release X 3.If they are not fully met in Release X, they will remain in the main body of TS-0002, and will be updated to reflect “Partially Met”, not indicating a release. Footnotes will continue to reflect how the requirement was partially met. 4.If the requirement is fully met, it will be updated to say “Met in Release X” © 2014 oneM2M Partners TP TP

Items for INFORMATION (ctd.) C)Requirement developed after Stage 1 freeze and before Stage 3 freeze of Release X 1.Requirements intended for Release X+1 will be added to TS-0002 in an Informative Annex 2.After Stage 3 freeze, contributions may be uploaded to move these requirements individually from the Informative Annex to the main body of TS When moved to the main body, they will reflect “Targeted for Release X+1” 4.If requirements are added to the Informative Annex and are later determined not to become part of the oneM2M System, they may be removed from the Informative Annex via contribution © 2014 oneM2M Partners TP TP

Highlights All submitted contributions were addressed by the working group Started TR on Vehicular Enablement (WI-0046) Worked on Use cases for machine self learning, taxi advertisement, machine socialization, vending machine With SEC: agreed Security analysis for TR-0018 (Industrial Domain Enablement V0_4_0) With ARC: agreed CR to TS-0011 definition of Interworking Proxy Application Entity (IPE) © 2014 oneM2M Partners TP TP

Highlights Agreed contributions © 2014 oneM2M Partners TP REQ R02Draft-TR-0xx on Vehicluar Domain Enablement V0 1 0Hitachi, Huawei, LGE REQ R01use_case_for_machine_socializationCMCC REQ TR-0018-Security_AnalysisHitachi REQ CR to TS-0011 definition of Interworking Proxy Application Entity IPENEC REQ Change the potential requirement of use case taxi advertisementCMCC TP

Next Steps Advance Home Domain enablement document (WI-0017) Advance Industrial Domain enablement document (WI-0028, TR-0018) Validation of requirements implemented in Release 2 prior to release freeze as agreed during TP19 © 2014 oneM2M Partners TP TP

Next Meetings / Calls Conference Calls No conference call prior to TP21 Face to Face TP21 in San Diego, CA, USA 18 – 22 January 2016 Timeslot allocations unknown at this time but probably not many needed. Advance Use Cases Begin thinking about requirements for the next release. © 2014 oneM2M Partners TP TP