WG 3 Progress Report at TP15 Group Name: oneM2M TP15 Source: Raymond Forbes, LM Ericsson, Meeting Date: to Agenda Item: TP#15, Item 10, Reports from Working Groups

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 R02_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 to be available for PRO15.1 – TS-0008 v0.6.0 (CoAP Protocol Binding) Rapporteur: SeongYoon Kim see TP _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 _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 _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 The updated TS-0004, TS-0008, TS-0009 & TS-0010 all at will be ready to be checked with CRs incorporated by PRO middle of next week.

Items for INFORMATION © 2013 oneM2M Partners 3

Issues for INFORMATION in the TP © 2013 oneM2M Partners 4 TS-0004: ItemDocument NumberShort nameSourceLate ? PRO PRO R03CR_conventions_for_clause7.3LG ElectronicsAgreed as R PRO PRO R01editorial_changes_clause LG ElectronicsWG Agreed as R PRO PRO R02editorial_changes_clause LG ElectronicsAgreed as R PRO common use of m2m:timeStampFUJITSUAgreed PRO PRO R01TS0004 XSD Change RequestPeter Niblett, IBMAgreed as R PRO CR reference point applicabilityLG ElectronicsAgreed PRO externalID clarificationHuawei TechnologiesAgreed PRO PRO R03Response Status Code UpdateFUJITSUWG Agreed as R PRO PRO R01CR for TS-0004 abbreviation clean-upQUALCOMMWG agreed as R PRO convention adoption for clause 7.3LG ElectronicsWG Agreed PRO R01change-to-xsdtable-mgmtObjHuawei Technologies Co. WG agreed as R PRO R02cleanup-of-group-proceduresHuawei Technologies Co. WG agreed as R PRO R01editorial-to-node-resourceHuawei Technologies Co. WG agreed as R PRO R02modification_to_DM_common_operationHuawei Technologies Co. WG Agreed as R PRO R01CR for TS-0004 m2m:requestStatusQUALCOMM WG agreed as R01

Issues for INFORMATION in the TP © 2013 oneM2M Partners 5 TS-0004: ItemDocument NumberShort nameSourceLate ? PRO CR for TS-0004 Editorial clean-up in generic proceduresQUALCOMMWG Agreed PRO R01CR modification of resource common attributesLG Electronics WG Agreed as R PRO R01CR default value clarificationLG Electronics WG Agreed as R PRO R01CR modification of memberListLG Electronics WG Agreed as R PRO objectPath to objectPathsHuawei Technologies Co., Ltd. WG Agreed PRO R03add resourceName to common attributesHuawei Technologies Co. WG Agreed as R PRO Short Names correctionMichele Lupano, Telecom Italia WG Agreed PRO R02RSC cleanup in proceduresLG ElectronicsWG Agreed PRO R01aggregated-responseHuawei Technologies Co.WG Agreed PRO R02cleanup_of_enumerationHuawei Technologies Co.WG Agreed PRO R02 CR unsupported attribute in notification procedureLG Electronics WG Agree as R PRO CR_annex_d_missing_procedureLG ElectronicsWG Agreed PRO PRO R03CR_typeOfContent_to_contentInfoFUJITSUWG Agree as R03

Issues for INFORMATION in the TP © 2013 oneM2M Partners 6 TS-0004: ItemDocument NumberShort nameSourceLate ? PRO PRO R01Clarify virtual resource handlingPeter Niblett, IBMWG Agreed PRO PRO R03CR_TS-0004-Annex-EHuawei TechnologiesWG Agreed PRO CR for TS-0004 clean-up based on the feedback from EditHelp QUALCOMMWG Agreed PRO PRO R04CR for TS-0004 serviceSubscribedAppRuleQUALCOMMWG Agreed as R PRO CR annex G reference cleanupLG ElectronicsWG agreed PRO PRO R02TS0004_status_code_typeFUJITSUWG Agreed as R PRO R01CR_RSC_definition_update LG Electronics WG agreed as R PRO CR TS0004 for Service Subscription Profile Procedure LG Electronics, ALUWG Agreed PRO PRO R01Examples for oneM2M Simple Data TypesIMTWG Agreed PRO PRO R03scheduleElement data formatFUJITSUWG Agreed as R PRO R03CR for TS-0004 clean-up for creating/updating resource QUALCOMMWG Agree as R03

Issues for INFORMATION in the TP © 2013 oneM2M Partners 7 TS-0004: ItemDocument NumberShort nameSourceLate ? PRO PRO R03clean-up-of-common-operationHuawei Technologies Co., Ltd. WG Agreed as R PRO R01originator restrictionLG ElectronicsWG Agreed PRO R02data type for pollingChannelURILG ElectronicsWG Agreed PRO CR for TS-0004 clean-up and resource procedure QUALCOMMWG Agreed PRO TS0004_Removal_of_Unicode referenceEricssonWG Agreed PRO PRO R01TS0004_JSON_serialization(replacement of ) FUJITSUWG Agreed as R PRO PRO R03CR_Shortname_for_filterCriteriaFUJITSUWG Agreed as R PRO PRO R05CR create responseLG ElectronicsWG Agreed as R PRO PRO R02XML Schema-related changes to Clause 7Peter Niblett, IBM WG Agreed as R PRO PRO R02XML_Schema-related_changes_to_notificationQUALCOMMWG Agreed as R PRO PRO R03TS0004 m2m identifier and addressingFUJITSUWG Agreed as R PRO PRO R04oneM2M Media TypeFUJITSUWG Agreed as R PRO PRO R02CR for TS-0004 nonBlockingAsynch in the common procedure QUALCOMMWG Agreed as R PRO PRO R01Partial retrievingMichele Lupano, Telecom Italia WG Agreed as R02

Issues for INFORMATION in the TP © 2013 oneM2M Partners 8 TS-0004: PRO R03TS0004_Removal_of_Annex-AEricssonWG Agreed as R PRO PRO R05XML Schema-related changes to Annex DQUALCOMMWG Agreed as R PRO PRO R07XML_serializationQualcommWG Agreed as R PRO PRO R02XML Schema-related changes to Clause 6Peter Niblett, IBM WG Agreed as R PRO PRO R05TS-0004_Notification_for_non-blockingAsyncQualcomm / FUJITSUWG Agreed PRO CR_CSE_AE_registration_referenceLG Electronics, QualcommWG Agreed PRO TS-0004_removal_of_res_def_RtemplateFUJITSUWG Agreed PRO PRO R01TS-0004 CR Verify From parameter clause 7_2_2_1Qualcomm Inc. (TIA)WG Agreed as R PRO TS-0004_editorial_correctionsTS-0004 RapportuerWG Agreed

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 PRO Example ProceduresXuan HeWG Agreed PRO PRO R02CoAP New Options DescriptionsLG Electronics WG Agreed as R PRO PRO R02CoAP Content FormatLG Electronics WG Agreed as R PRO CoAP TS ClarificationLG Electronics WG Agreed PRO Edit Help for CoAP Binding TSLG ElectronicsWG Agreed PRO PRO R01CoAP Response Code Mapping UpdateLG ElectronicsWG Agreed as R PRO CoAP Example UpdateLG ElectronicsWG Agreed PRO CoAP Content Mapping UpdateLG ElectronicsWG Agreed

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 PRO PRO R02MQTT Binding SecurityPeter Niblett, IBMWG Agreed R PRO editHelp changes to MQTT bindingPeter Niblett, IBMWG Agreed ItemDocument NumberShort nameSourceResult PRO PRO R02From mapping in HTTP bindingFUJITSUWG Agreed as R PRO PRO R01TS-0009 acronym reference clean-upLG ElectronicsWG agreed as R PRO PRO R02TS-0009_clause6_cleanupLG ElectronicsWG Agreed as R PRO PRO R02TS-0009_mapping_example_updateLG ElectronicsWG Agreed as R PRO PRO R01CR_HTTP_binding_overviewFUJITSUWG Agreed as R PRO TS-0009_editHelp_comment_and_answersTS-0009 RapporteurAgreed – CRs in Progress

Comments to Aug 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 R01 An example in this section would be helpfulEach binding has a native status code Successful response – PRO R01 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 R01 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 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 & also into to Annex B. LS to 3GPP2?

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