10
WG1 status report to TP#17 up Name: oneM2M TP17 rce: Shelby Kiewel (iconectiv) ting Date: 2015-05-17 to 2015-05-21 nda Item: TP#17, Item 10.3, Reports from Working Groups

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

Embed Size (px)

Citation preview

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

WG1 status report to TP#17

Group Name: oneM2M TP17Source: Shelby Kiewel (iconectiv) Meeting Date: 2015-05-17 to 2015-05-21Agenda Item: TP#17, Item 10.3, Reports from Working Groups

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

Issues for DECISION in TP• CR Packs

– TP-2015-717R01 – CR Pack for TS-0002– TP-2015-718 – CR Pack for TS-0011– TP-2015-721R01 – CR Pack for TR-0001

© 2013 oneM2M Partners

<TP-2015-0654> 2

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

Action Items for alignment in TP

• None

© 2013 oneM2M Partners

<TP-2015-0654> 3

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

Items for INFORMATION

• Requirements for inclusion in Release 2 need to be finalized by closing plenary of TP#18

© 2013 oneM2M Partners

<TP-2015-0654> 4

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

Highlights

• Reviewed/Noted/Agreed approximately 50 Contributions

• Joint sessions held – Security Working Group– Architecture Working Group

© 2013 oneM2M Partners

<TP-2015-0654> 5

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

Highlights• WG1 Contributions Reaching Agreement

• Home Domain Enablement TR-0013– Contribution REQ-2015-0549

• Industrial Domain Use Case– Contribution REQ-2015-0551

• Aircraft Construction and Maintenance Use Case– Contribution REQ-2015-0562R01

• Requirements Supporting Integrity of Data Collection– Contribution REQ-2015-0550R03

• Smart Automatic Driving Use Case– Contribution REQ-2015-0554

• Access Control User Group Use Case– Contribution REQ-2015-0556R01

• Multi-Cast User Group Use Case– Contribution REQ-2015-0557R01

• New Requirements on Grouping– Contribution REQ-2015-0558R01

© 2013 oneM2M Partners

<TP-2015-0654> 6

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

Highlights• WG1 Contributions Reaching Agreement

– Items related to TS-0002, TR-0018, etc…….• Group Registration Use Case

– Contribution REQ-2015-0561

• Data Process for Inter-factory manufacturing– Contribution REQ-2015-0552R01

• Requirements Supporting On-Demand Data Collection– Contribution REQ-2015-0553R02

• Smart Meter Reading Use Case – Contribution REQ-2015-0563

• Security Requirements for WI-0023– Contribution SEC-2015-0515R02

• SE Abstraction API– Contribution SEC-2015-0522R02

• App End-to-End Security Requirements – Contribution REQ-2015-0568R04

• Primitive End-to-end Security Requirements– Contribution REQ-2015-0569R03

© 2013 oneM2M Partners

<TP-2015-0654> 7

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

Highlights• WG1 Contributions Reaching Agreement

– Items related to TS-0002, TR-0018, etc…….• Security Requirements for WI-0016

– Contribution SEC-2015-0517R05

• Use Case of PPM– Contribution REQ-2015-0576

• Generic End-to-End Security Requirements– Contribution REQ-2015-0575R01

• Requirements for App/Field Domain Component Configuration– Contribution REQ-2015-0555R02

• Efficient Communication Requirements– Contribution REQ-2015-0564R02

• Changing Defined Terms to Upper Case– Contribution REQ-2015-0570R01

• TR-0013 Requirements Update– Contribution REQ-2015-0573R01

• Additional Group Requirements for TR-0001– Contribution REQ-2015-0574R01

• Home Domain Enablement Use Case Addition to TR-0013– Contribution REQ-2015-0578 © 2013 oneM2M

Partners<TP-2015-0654>

8

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

Next Steps• Advance Home Domain enablement document

(WI-0017)• Advance Industrial Domain enablement document

(WI-0028, TR-0018)• Advance the inclusion of definitions from various TS

documents into TS-0011• Advance new requirements in support of Release 2

developments• Edit/Update/Align definitions document related to

capitalization of terms• Work to provide indexing of Use Cases

© 2013 oneM2M Partners

<TP-2015-0654> 9

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

Next Meetings / Calls• Conference Calls

– One interim conference call prior to TP18• REQ 17.1 - Monday, June 15, 13:00 – 15:00 GMT

• Face to Face– TP18 in USA Location, 20 – 25 July 2015

• Expect at least 6-7 regular timeslots• Additional joint sessions with various working groups• Finalization of Release 2 Requirements

© 2013 oneM2M Partners

<TP-2015-0654>

10