1. 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 from Working Groups TP-2015-0863

2. Issues for DECISION in TP CR Packs – TP-2015-0864-CR_to_TS- 0011_definition_of_Interworking_Proxy_Application_Entity_IPE © 2014 oneM2M Partners TP-2015-0837 2 TP-2015-0863

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

4. 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-2015-0837 4 TP-2015-0863

5. 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-0002 3.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-2015-0837 5 TP-2015-0863

6. 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-2015-0837 6 TP-2015-0863

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

8. 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-2015-0837 8 TP-2015-0863

9. 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-2015-0837 9 TP-2015-0863