1. WG 3 Progress Report at TP15 Group Name: oneM2M TP15 Source: Raymond Forbes, LM Ericsson, raymond.forbes@ericsson.com Meeting Date: 2015-01-19 to 2015-01-23 Agenda Item: TP#15, Item 10, Reports from Working Groups

2. Issues for DECISION in TP © 2013 oneM2M Partners 2 CR Packs for following Technical Specifations – TS-0004 v0.8.0(Core Protocol) Rapporteurs: Shingo Fujimoto & Nobuyuki Uchida see TP-2015-0002R02_TS-0004 CR Pack TP.15 [62 CRs] Progress at 95% Available to TP.15 for approval prior to TS-0004 V1.0.0 when the CRs incorporated - XSD Pack at Version 1.0.0 to be available for PRO15.1 – TS-0008 v0.6.0 (CoAP Protocol Binding) Rapporteur: SeongYoon Kim see TP-2015-0594_TS-0008 CR Pack TP.15 Progress at 100% Available to TP.15 for approval prior to TS-0008 V1.0.0 when the CRs incorporated – TS-0009 v0.6.0 (HTTP Protocol Binding) Rapporteur: SeungMyeong Jeong see TP-2015-0595_TS-0009 CR Pack TP.15 Progress at 100% Available to TP.15 for approval prior to TS-0009 v1.0.0 with the CRs incorporated – TS-0010 v0.4.0 (MQTT Protocol Binding) Rapporteur: Peter Niblett see PRO-2015-0698_TS-0010 CR Pack PRO.15 Progress at 95% Available to TP.15 for approval prior to TS-0010 v1.0.0 with the CRs incorporated – TS-0010 is available for TP approval at 95% as TP-2015-0607 The updated TS-0004, TS-0008, TS-0009 & TS-0010 all at 1.0.0 will be ready to be checked with CRs incorporated by PRO15.1 - middle of next week.

3. Items for INFORMATION © 2013 oneM2M Partners 3

4. Issues for INFORMATION in the TP © 2013 oneM2M Partners 4 TS-0004: ItemDocument NumberShort nameSourceLate ? 14.1.01PRO-2014-0604PRO-2014-0604R03CR_conventions_for_clause7.3LG ElectronicsAgreed as R03 14.1.02PRO-2014-0607PRO-2014-0607R01editorial_changes_clause7.3.9.2.1LG ElectronicsWG Agreed as R01 14.1.03PRO-2014-0608PRO-2014-0608R02editorial_changes_clause7.4.2.2LG ElectronicsAgreed as R02 14.1.05PRO-2014-0612common use of m2m:timeStampFUJITSUAgreed 14.1.06PRO-2014-0613PRO-2014-0613R01TS0004 XSD Change RequestPeter Niblett, IBMAgreed as R01 14.2.01PRO-2014-0610CR reference point applicabilityLG ElectronicsAgreed 14.2.04PRO-2014-0618externalID clarificationHuawei TechnologiesAgreed 14.2.05PRO-2014-0619PRO-2014-0619R03Response Status Code UpdateFUJITSUWG Agreed as R03 14.2.07PRO-2015-0002PRO-2015-0002R01CR for TS-0004 abbreviation clean-upQUALCOMMWG agreed as R02 14.3.02 PRO-2015-0623convention adoption for clause 7.3LG ElectronicsWG Agreed 14.3.07 PRO-2015-0628R01change-to-xsdtable-mgmtObjHuawei Technologies Co. WG agreed as R01 14.3.09 PRO-2015-0630R02cleanup-of-group-proceduresHuawei Technologies Co. WG agreed as R02 14.3.10 PRO-2015-0631R01editorial-to-node-resourceHuawei Technologies Co. WG agreed as R01 14.3.11 PRO-2015-0632R02modification_to_DM_common_operationHuawei Technologies Co. WG Agreed as R02 14.3.13 PRO-2015-0635R01CR for TS-0004 m2m:requestStatusQUALCOMM WG agreed as R01

5. Issues for INFORMATION in the TP © 2013 oneM2M Partners 5 TS-0004: ItemDocument NumberShort nameSourceLate ? 14.3.14 PRO-2015-0638 CR for TS-0004 Editorial clean-up in generic proceduresQUALCOMMWG Agreed 14.3.16 PRO-2015-0642R01CR modification of resource common attributesLG Electronics WG Agreed as R01 14.3.17 PRO-2015-0643R01CR default value clarificationLG Electronics WG Agreed as R01 14.3.18 PRO-2015-0644R01CR modification of memberListLG Electronics WG Agreed as R01 14.3.23PRO-2015-0664objectPath to objectPathsHuawei Technologies Co., Ltd. WG Agreed 14.3.01 PRO-2015-0622R03add resourceName to common attributesHuawei Technologies Co. WG Agreed as R03 15.0.01PRO-2015-0007Short Names correctionMichele Lupano, Telecom Italia WG Agreed 14.3.04 PRO-2015-0625R02RSC cleanup in proceduresLG ElectronicsWG Agreed 14.3.06 PRO-2015-0627R01aggregated-responseHuawei Technologies Co.WG Agreed 14.3.08 PRO-2015-0629R02cleanup_of_enumerationHuawei Technologies Co.WG Agreed 14.3.19 PRO-2015-0645R02 CR unsupported attribute in notification procedureLG Electronics WG Agree as R02 14.3.26PRO-2015-0669CR_annex_d_missing_procedureLG ElectronicsWG Agreed 14.3.25PRO-2015-0667PRO-2015-0667R03CR_typeOfContent_to_contentInfoFUJITSUWG Agree as R03

6. Issues for INFORMATION in the TP © 2013 oneM2M Partners 6 TS-0004: ItemDocument NumberShort nameSourceLate ? 14.3.27PRO-2015-0670PRO-2015-0670R01Clarify virtual resource handlingPeter Niblett, IBMWG Agreed 15.0.09PRO-2015-0673PRO-2015-0673R03CR_TS-0004-Annex-EHuawei TechnologiesWG Agreed 15.0.10PRO-2015-0674CR for TS-0004 clean-up based on the feedback from EditHelp QUALCOMMWG Agreed 15.0.12PRO-2015-0677PRO-2015-0677R04CR for TS-0004 serviceSubscribedAppRuleQUALCOMMWG Agreed as R04 15.0.15PRO-2015-0680CR annex G reference cleanupLG ElectronicsWG agreed 15.0.16PRO-2015-0681PRO-2015-0681R02TS0004_status_code_typeFUJITSUWG Agreed as R02 15.0.17PRO-2015-0682R01CR_RSC_definition_update LG Electronics WG agreed as R01 15.0.20PRO-2015-0685CR TS0004 for Service Subscription Profile Procedure LG Electronics, ALUWG Agreed 14.2.02PRO-2014-0615PRO-2014-0615R01Examples for oneM2M Simple Data TypesIMTWG Agreed 14.2.03PRO-2014-0617PRO-2014-0617R03scheduleElement data formatFUJITSUWG Agreed as R03 14.3.15PRO-2015-0640R03CR for TS-0004 clean-up for creating/updating resource QUALCOMMWG Agree as R03

7. Issues for INFORMATION in the TP © 2013 oneM2M Partners 7 TS-0004: ItemDocument NumberShort nameSourceLate ? 15.0.18PRO-2015-0683PRO-2015-0683R03clean-up-of-common-operationHuawei Technologies Co., Ltd. WG Agreed as R03 14.3.03PRO-2015-0624R01originator restrictionLG ElectronicsWG Agreed 14.3.05 PRO-2015-0626R02data type for pollingChannelURILG ElectronicsWG Agreed 15.0.11PRO-2015-0675CR for TS-0004 clean-up and resource procedure QUALCOMMWG Agreed 15.0.26PRO-2015-0692TS0004_Removal_of_Unicode referenceEricssonWG Agreed 15.0.28PRO-2015-0695PRO-2015-0695R01TS0004_JSON_serialization(replacement of 2015- 0005) FUJITSUWG Agreed as R01 14.2.08PRO-2015-0004PRO-2015-0004R03CR_Shortname_for_filterCriteriaFUJITSUWG Agreed as R03 14.3.24PRO-2015-0666PRO-2015-0666R05CR create responseLG ElectronicsWG Agreed as R05 15.0.06PRO-2015-0662PRO-2015-0662R02XML Schema-related changes to Clause 7Peter Niblett, IBM WG Agreed as R02 15.0.19PRO-2015-0684PRO-2015-0684R02XML_Schema-related_changes_to_notificationQUALCOMMWG Agreed as R02 15.0.21PRO-2015-0686PRO-2015-0686R03TS0004 m2m identifier and addressingFUJITSUWG Agreed as R03 15.0.22PRO-2015-0687PRO-2015-0687R04oneM2M Media TypeFUJITSUWG Agreed as R04 15.0.29PRO-2015-0696PRO-2015-0696R02CR for TS-0004 nonBlockingAsynch in the common procedure QUALCOMMWG Agreed as R02 15.0.30PRO-2015-0697PRO-2015-0697R01Partial retrievingMichele Lupano, Telecom Italia WG Agreed as R02

8. Issues for INFORMATION in the TP © 2013 oneM2M Partners 8 TS-0004: 15.0.25PRO-2015-0690R03TS0004_Removal_of_Annex-AEricssonWG Agreed as R03 15.0.07PRO-2015-0663PRO-2015-0663R05XML Schema-related changes to Annex DQUALCOMMWG Agreed as R05 14.0.22PRO-2014-0584PRO-2014-0584R07XML_serializationQualcommWG Agreed as R07 15.0.05PRO-2015-0661PRO-2015-0661R02XML Schema-related changes to Clause 6Peter Niblett, IBM WG Agreed as R01 15.0.24PRO-2015-0689PRO-2015-0689R05TS-0004_Notification_for_non-blockingAsyncQualcomm / FUJITSUWG Agreed 15.0.31PRO-2015-0701CR_CSE_AE_registration_referenceLG Electronics, QualcommWG Agreed 15.0.32PRO-2015-0702TS-0004_removal_of_res_def_RtemplateFUJITSUWG Agreed 15.0.33PRO-2015-0703PRO-2015-0703R01TS-0004 CR Verify From parameter clause 7_2_2_1Qualcomm Inc. (TIA)WG Agreed as R01 15.0.34PRO-2015-0704TS-0004_editorial_correctionsTS-0004 RapportuerWG Agreed

9. Issues for INFORMATION in the TP © 2013 oneM2M Partners 9 TS-0008: Contributions about Protocol TS-0009/WI-0012: CoAP binding – 100% ItemDocument NumberShort nameSourceResult 15.0.01 PRO-2015-0636Example ProceduresXuan HeWG Agreed 15.0.03PRO-2015-0649PRO-2015-0649R02CoAP New Options DescriptionsLG Electronics WG Agreed as R02 15.0.04PRO-2015-0650PRO-2015-0650R02CoAP Content FormatLG Electronics WG Agreed as R02 15.0.05PRO-2015-0651CoAP TS ClarificationLG Electronics WG Agreed 15.0.06PRO-2015-0678Edit Help for CoAP Binding TSLG ElectronicsWG Agreed 15.0.07PRO-2015-0694PRO-2015-0694R01CoAP Response Code Mapping UpdateLG ElectronicsWG Agreed as R01 15.0.08PRO-2015-0699CoAP Example UpdateLG ElectronicsWG Agreed 15.0.09PRO-2015-0700CoAP Content Mapping UpdateLG ElectronicsWG Agreed

10. Issues for INFORMATION in the TP © 2013 oneM2M Partners 10 TS-0009 & TS-0010: Contributions about Protocol TS-0009/WI-0013: HTTP binding – 100% Contributions about Protocol TS-0010/WI-0014: MQTT binding – 100% ItemDocument NumberShort nameSourceResult 15.0.02PRO-2015-0653PRO-2015-0653R02MQTT Binding SecurityPeter Niblett, IBMWG Agreed R02 15.0.03PRO-2015-0656editHelp changes to MQTT bindingPeter Niblett, IBMWG Agreed ItemDocument NumberShort nameSourceResult 14.2.01PRO-2015-0001PRO-2015-0001R02From mapping in HTTP bindingFUJITSUWG Agreed as R02 14.3.01PRO-2015-0658PRO-2015-0658R01TS-0009 acronym reference clean-upLG ElectronicsWG agreed as R01 14.3.02PRO-2015-0659PRO-2015-0659R02TS-0009_clause6_cleanupLG ElectronicsWG Agreed as R02 14.3.03PRO-2015-0660PRO-2015-0660R02TS-0009_mapping_example_updateLG ElectronicsWG Agreed as R02 14.3.04PRO-2015-0665PRO-2015-0665R01CR_HTTP_binding_overviewFUJITSUWG Agreed as R01 14.3.05PRO-2015-0668TS-0009_editHelp_comment_and_answersTS-0009 RapporteurAgreed – CRs in Progress

11. Comments to Aug. 2014 Release © 2013 oneM2M Partners 11 Public Comments: Should there be a summary table of the Enumerated Data Types to precede the sections where the data types are fully described? Addressed & Agreed in PRO-2015- 0002R01 An example in this section would be helpfulEach binding has a native status code Successful response – PRO-2014- 0619R01 Agreed CR for response Status codes. In Progress Should this section say how the originator determines the receiver CSE or is this left to the implementer? Routing may be an implementation issue being addressed Covered in a future release Some used Abbreviations are not defined. For instance it uses 3GPP2 and MQTT without defining them. Note a check should be done with all the documents Addressed& Agreed in PRO-2015- 0002R01 It only lists a normative Annex for device triggering for 3GPP. A similar Annex (like B.2 under B annex) should be included for 3GPP2. Note that in section 5.1.1 references to 3GPP2 device triggering to Annex B.1 which is not right. It should refer to Annex B.2 once it is added in the document. In Progress Need an editorial CR to Section 5.1.1 & also into to Annex B. LS to 3GPP2?

12. Next Meetings / Calls Conference Calls Face to Face – TP.16 Sophia-Antipolis 23-27 March 2015 © 2013 oneM2M Partners 12 PRO15.128-Jan-2015 Wednesday 22-23 UTCConference Call for WG3 TS approval of CR checking