Embed Size (px)
Citation preview
WG 3 Progress Report at TP15
Group Name: oneM2M TP15Source: Raymond Forbes, LM Ericsson, [email protected] Date: 2015-01-19 to 2015-01-23Agenda Item: TP#15, Item 10, Reports from Working Groups
Issues for DECISION in TP
© 2013 oneM2M Partners<Document number>
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.15Progress 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 Jeongsee TP-2015-0595_TS-0009 CR Pack TP.15Progress 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 Niblettsee PRO-2015-0698_TS-0010 CR Pack PRO.15Progress 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.
Items for INFORMATION
Items for INFORMATION
© 2013 oneM2M Partners<Document number>
3
Issues for INFORMATION in the TP
© 2013 oneM2M Partners<Document number>
4
TS-0004:
Item Document Number Short name Source Late ?14.1.01 PRO-2014-0604R03 CR_conventions_for_clause7.3 LG Electronics Agreed as R0314.1.02 PRO-2014-0607R01 editorial_changes_clause7.3.9.2.1 LG Electronics WG Agreed as
R0114.1.03 PRO-2014-0608R02 editorial_changes_clause7.4.2.2 LG Electronics Agreed as R0214.1.05 PRO-2014-0612 common use of m2m:timeStamp FUJITSU Agreed14.1.06 PRO-2014-0613R01 TS0004 XSD Change Request Peter Niblett, IBM Agreed as R0114.2.01 PRO-2014-0610 CR reference point applicability LG Electronics Agreed14.2.04 PRO-2014-0618 externalID clarification Huawei Technologies Agreed14.2.05 PRO-2014-0619R03 Response Status Code Update FUJITSU WG Agreed as
R0314.2.07 PRO-2015-0002R01 CR for TS-0004 abbreviation clean-up QUALCOMM WG agreed as
R0214.3.02 PRO-2015-0623 convention adoption for clause 7.3 LG Electronics WG Agreed14.3.07
PRO-2015-0628R01 change-to-xsdtable-mgmtObj Huawei Technologies Co.WG agreed as R01
14.3.09PRO-2015-0630R02 cleanup-of-group-procedures Huawei Technologies Co.
WG agreed as R02
14.3.10PRO-2015-0631R01 editorial-to-node-resource Huawei Technologies Co.
WG agreed as R01
14.3.11PRO-2015-0632R02 modification_to_DM_common_operation Huawei Technologies Co.
WG Agreed as R02
14.3.13PRO-2015-0635R01 CR for TS-0004 m2m:requestStatus QUALCOMM
WG agreed as R01
Issues for INFORMATION in the TP
© 2013 oneM2M Partners<Document number>
5
TS-0004:
Item Document Number Short name Source Late ?14.3.14
PRO-2015-0638CR for TS-0004 Editorial clean-up in generic procedures QUALCOMM WG Agreed
14.3.16PRO-2015-0642R01 CR modification of resource common attributes LG Electronics
WG Agreed as R01
14.3.17PRO-2015-0643R01 CR default value clarification LG Electronics
WG Agreed as R01
14.3.18PRO-2015-0644R01 CR modification of memberList LG Electronics
WG Agreed as R01
14.3.23 PRO-2015-0664 objectPath to objectPaths Huawei Technologies Co., Ltd.
WG Agreed
14.3.01PRO-2015-0622R03 add resourceName to common attributes Huawei Technologies Co.
WG Agreed as R03
15.0.01 PRO-2015-0007 Short Names correction Michele Lupano, Telecom Italia
WG Agreed
14.3.04 PRO-2015-0625R02 RSC cleanup in procedures LG Electronics WG Agreed14.3.06 PRO-2015-0627R01 aggregated-response Huawei Technologies Co. WG Agreed14.3.08 PRO-2015-0629R02 cleanup_of_enumeration Huawei Technologies Co. WG Agreed14.3.19
PRO-2015-0645R02CR unsupported attribute in notification procedure LG Electronics
WG Agree as R02
14.3.26 PRO-2015-0669 CR_annex_d_missing_procedure LG Electronics WG Agreed14.3.25 PRO-2015-0667R03 CR_typeOfContent_to_contentInfo FUJITSU WG Agree as
R03
Issues for INFORMATION in the TP
© 2013 oneM2M Partners<Document number>
6
TS-0004:
Item Document Number Short name Source Late ?14.3.27 PRO-2015-0670R01 Clarify virtual resource handling Peter Niblett, IBM WG Agreed15.0.09 PRO-2015-0673R03 CR_TS-0004-Annex-E Huawei Technologies WG Agreed15.0.10 PRO-2015-0674 CR for TS-0004 clean-up based on the feedback fr
om EditHelpQUALCOMM WG Agreed
15.0.12 PRO-2015-0677R04 CR for TS-0004 serviceSubscribedAppRule QUALCOMM WG Agreed as R04
15.0.15 PRO-2015-0680 CR annex G reference cleanup LG Electronics WG agreed15.0.16 PRO-2015-0681R02 TS0004_status_code_type FUJITSU WG Agreed as
R0215.0.17 PRO-2015-0682R01 CR_RSC_definition_update
LG ElectronicsWG agreed as R01
15.0.20 PRO-2015-0685 CR TS0004 for Service Subscription Profile Procedure
LG Electronics, ALU WG Agreed
14.2.02 PRO-2014-0615R01 Examples for oneM2M Simple Data Types IMT WG Agreed14.2.03 PRO-2014-0617R03 scheduleElement data format FUJITSU WG Agreed as
R0314.3.15 PRO-2015-0640R03 CR for TS-0004 clean-up for creating/updating
<request> resourceQUALCOMM WG Agree as
R03
Issues for INFORMATION in the TP
© 2013 oneM2M Partners<Document number>
7
TS-0004:
Item Document Number Short name Source Late ?15.0.18 PRO-2015-0683R03 clean-up-of-common-operation Huawei Technologies Co.,
Ltd.WG Agreed as R03
14.3.03 PRO-2015-0624R01 originator restriction LG Electronics WG Agreed14.3.05 PRO-2015-0626R02 data type for pollingChannelURI LG Electronics WG Agreed15.0.11 PRO-2015-0675 CR for TS-0004 clean-up <delivery> and <request> r
esource procedureQUALCOMM WG Agreed
15.0.26 PRO-2015-0692 TS0004_Removal_of_Unicode reference Ericsson WG Agreed15.0.28 PRO-2015-0695R01 TS0004_JSON_serialization(replacement of 2015-00
05)FUJITSU WG Agreed as R01
14.2.08 PRO-2015-0004R03 CR_Shortname_for_filterCriteria FUJITSU WG Agreed as R03
14.3.24 PRO-2015-0666R05 CR create response LG Electronics WG Agreed as R05
15.0.06 PRO-2015-0662R02 XML Schema-related changes to Clause 7 Peter Niblett, IBMWG Agreed as R02
15.0.19 PRO-2015-0684R02 XML_Schema-related_changes_to_notification QUALCOMM WG Agreed as R02
15.0.21 PRO-2015-0686R03 TS0004 m2m identifier and addressing FUJITSU WG Agreed as R03
15.0.22 PRO-2015-0687R04 oneM2M Media Type FUJITSU WG Agreed as R04
15.0.29 PRO-2015-0696R02 CR for TS-0004 nonBlockingAsynch in the common procedure
QUALCOMM WG Agreed as R02
15.0.30 PRO-2015-0697R01 Partial retrieving Michele Lupano, Telecom Italia
WG Agreed as R02
Issues for INFORMATION in the TP
© 2013 oneM2M Partners<Document number>
8
TS-0004:
15.0.25 PRO-2015-0690R03 TS0004_Removal_of_Annex-A Ericsson WG Agreed as R03
15.0.07 PRO-2015-0663R05 XML Schema-related changes to Annex D QUALCOMM WG Agreed as R05
14.0.22 PRO-2014-0584R07 XML_serialization Qualcomm WG Agreed as R07
15.0.05 PRO-2015-0661R02 XML Schema-related changes to Clause 6 Peter Niblett, IBM WG Agreed as R01
15.0.24 PRO-2015-0689R05 TS-0004_Notification_for_non-blockingAsync Qualcomm / FUJITSU WG Agreed15.0.31 PRO-2015-0701 CR_CSE_AE_registration_reference LG Electronics, Qualcomm WG Agreed15.0.32 PRO-2015-0702 TS-0004_removal_of_res_def_Rtemplate FUJITSU WG Agreed15.0.33 PRO-2015-0703R01 TS-0004 CR Verify From parameter clause 7_2_2_1 Qualcomm Inc. (TIA) WG Agreed as
R0115.0.34 PRO-2015-0704 TS-0004_editorial_corrections TS-0004 Rapportuer WG Agreed
Issues for INFORMATION in the TP
© 2013 oneM2M Partners<Document number>
9
TS-0008: Contributions about Protocol TS-0009/WI-0012: CoAP binding – 100%
Item Document Number Short name Source Result15.0.01 PRO-2015-0636 Example Procedures Xuan He WG Agreed15.0.03 PRO-2015-0649R02 CoAP New Options Descriptions LG Electronics WG Agreed as R0215.0.04 PRO-2015-0650R02 CoAP Content Format LG Electronics WG Agreed as R0215.0.05 PRO-2015-0651 CoAP TS Clarification LG Electronics WG Agreed15.0.06 PRO-2015-0678 Edit Help for CoAP Binding TS LG Electronics WG Agreed15.0.07 PRO-2015-0694R01 CoAP Response Code Mapping Update LG Electronics WG Agreed as R0115.0.08 PRO-2015-0699 CoAP Example Update LG Electronics WG Agreed15.0.09 PRO-2015-0700 CoAP Content Mapping Update LG Electronics WG Agreed
Issues for INFORMATION in the TP
© 2013 oneM2M Partners<Document number>
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%
Item Document Number Short name Source Result15.0.02 PRO-2015-0653R02 MQTT Binding Security Peter Niblett, IBM WG Agreed
R0215.0.03 PRO-2015-0656 editHelp changes to MQTT binding Peter Niblett, IBM WG Agreed
Item Document Number Short name Source Result14.2.01 PRO-2015-0001R02 From mapping in HTTP binding FUJITSU WG Agreed as R0214.3.01 PRO-2015-0658R01 TS-0009 acronym reference clean-up LG Electronics WG agreed as R0114.3.02 PRO-2015-0659R02 TS-0009_clause6_cleanup LG Electronics WG Agreed as R0214.3.03 PRO-2015-0660R02 TS-0009_mapping_example_update LG Electronics WG Agreed as R0214.3.04 PRO-2015-0665R01 CR_HTTP_binding_overview FUJITSU WG Agreed as R0114.3.05 PRO-2015-0668 TS-0009_editHelp_comment_and_answers TS-0009 Rapporteur Agreed – CRs in
Progress
Comments to Aug. 2014 Release
© 2013 oneM2M Partners<Document number>
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 helpful Each 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.1references 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 ProgressNeed an editorial CR to Section 5.1.1 & also into to Annex B.
LS to 3GPP2?
Next Meetings / Calls• Conference Calls
• Face to Face– TP.16 Sophia-Antipolis 23-27 March 2015
© 2013 oneM2M Partners<Document number>
12
PRO15.1 28-Jan-2015Wednesday
22-23 UTC Conference Call for WG3 TS approval of CR checking
