Presentation is loading. Please wait.

Presentation is loading. Please wait.

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

Similar presentations


Presentation on theme: "WG1 status report to TP#21 Group Name: oneM2M TP21 Source: Shelby Kiewel (iconectiv) Meeting Date: 2016-01-18 to 2016-01-22 Agenda Item: TP#21, Item 10.4,"— Presentation transcript:

1 WG1 status report to TP#21 Group Name: oneM2M TP21 Source: Shelby Kiewel (iconectiv) Meeting Date: 2016-01-18 to 2016-01-22 Agenda Item: TP#21, Item 10.4, Reports from Working Groups TP-2016-0035R01

2 Issues for DECISION in TP CR Packs – TP-2016-0028-TR-0018-Industrial-Domain-Enablement Requesting approval of TR-0018 Industrial Domain Enablement Document to be included in Release 2 – TP-2016-0032 TS-0002 CR Pack for TP Approval Contribution REQ-2016-0013R01  Informative Annex has been agreed for addition to TS-0002 to allow for new requirements to be added as Informative  Any requirements added to the Informative Annex will require CR to be moved into the Normative section of TS-0002 after Stage 3 Freeze Contribution REQ-2016-0019  Update to Requirements Note regarding Geo-fencing  Note 7, related to OSR-047 © 2014 oneM2M Partners TP-2015-0837 2

3 Action Items for alignment in TP None © 2014 oneM2M Partners TP-2015-0837 3

4 Items for INFORMATION None © 2014 oneM2M Partners TP-2015-0837 4

5 Highlights Addressed submitted contributions primarily associated with new Use Cases Migrated vehicle specific Use Cases from TR-0001 to TR-0026 on Vehicular Enablement Finalized TR on Industrial Domain Enablement (TR ‑ 0018) Addressed new terms based on updates to TS-0001 Meeting minutes can be found in REQ-2016-0016 – Open for comment through 29 January 2016 © 2014 oneM2M Partners TP-2015-0837 5

6 Highlights Agreed contributions © 2014 oneM2M Partners TP-2015-0837 6 Doc-NumberTitleSource REQ-2016-0002R01Vehicle Management based on Geo-fence_TR-0026SK Telecom REQ-2016-0007Draft-TR-0018-Industrial_Domain_Enablement-V0_5_0Hitachi REQ-2016-0008R01TR-0018-ConclusionHitachi, Huawei REQ-2016-0011R02CR to add contents for clause 5,7,8 in TR0013KETI REQ-2016-0005CR_to_TR0001_move_Use_Cases_to_TR0026Hitachi, Huawei, LGE REQ-2016-0006TR-0026-_Vehicular_Domain_Enablement_Clause_6Hitachi, Huawei, LGE REQ-2016-0001R03TR-0026-_Vehicular_Domain_Enablement_Clause_5_Introduction_to _Vehicular_DomainHitachi, Huawei, LGE REQ-2016-0004Terminology: Geo-fenceSK Telecom REQ-2016-0012R01Use Case on OTA Firmware Update for ECUsKDDI REQ-2016-0013R01Addition of Informative Annex to TS0002Shelby Kiewel - iconectiv REQ-2016-0017R02Draft-TR-0018-Industrial_Domain_EnablementHitachi, Huawei REQ-2016-0019CR for Geo-fence event information support of OSR-047SK Telecom REQ-2016-0020Definition_of_Content_Sharing_ResourceSamsung Electronics

7 Next Steps Advance Home Domain enablement document (WI-0017) Advance Vehicular Domain enablement document (WI-0046, TR-0026) Continue validation of requirements implemented in Release 2 prior to final release freeze as agreed during TP#19 © 2014 oneM2M Partners TP-2015-0837 7

8 Next Meetings / Calls Conference Calls No conference calls prior to TP#22 Face to Face TP#22 in Sophia Antipolis, FR, 14 – 18 March 2016 Timeslot allocations unknown at this time Advance Use Cases Advance ideas for requirements necessary for the next release. © 2014 oneM2M Partners TP-2015-0837 8


Download ppt "WG1 status report to TP#21 Group Name: oneM2M TP21 Source: Shelby Kiewel (iconectiv) Meeting Date: 2016-01-18 to 2016-01-22 Agenda Item: TP#21, Item 10.4,"

Similar presentations


Ads by Google