WG 3 Progress Report at TP13

Group Name: oneM2M TP13Source: Raymond Forbes, LM Ericsson, raymond.forbes@ericsson.comMeeting Date: 2014-09-22 to 2014-09-27Agenda Item: TP#13, Item 10, Reports from Working Groups

Issues for DECISION in TP

© 2013 oneM2M Partners<Document number>

2

• CR Packs for following Work-items– TS-0004 v0.7.0 (Core Protocol) Rapporteurs: Shingo Fujimoto & Nobuyuki Uchida

see PRO-2014-0513-TS-0004WI-0009 Core Protocol - CR Pack 2014-09Progress at 75%

– Available to TP.13 for approval prior to TS-0004 V0.7.0 – TS-0009 v0.5.0 (HTTP Protocol Binding) Rapporteur: SeungMyeong Jeong

see PRO-2014-0512-TS-0009WI-0013 HTTP binding - CR Pack-2014-09Progress at 75%Available to TP.13 for approval prior to TS-0009 v0.5.0

– TS-0010 v0.2.0 (MQTT Protocol Binding) Rapporteur: Peter Niblettsee PRO-2014-0301-Output_Draft_TS-0010_MQTT_Protocol_Binding_v_0_2_0Progress at 70% Frozen at the Working Group with the CRs incorporated

• The updated TS-0004 v0.7.0 (some of the CRs) & TS-0009 v0.5.0 are ready to be checked with CRs incorporated.

Open Action Items for alignment in TP

© 2013 oneM2M Partners<Document number>

3

Item # Document Number(S) Short name Source Status

A-PRO-11.9-003

PRO-2014-0292ARC-2014-1492ARC-2914-1502

AE_CSE_ID_Issue Shingo: Fujitsu & Others

Open

To be solvedin WG2

A-PRO-11.9-006

ARC-2014-1487PRO-2014-0304R03email

Partial Updates – differentiate the primitives Nicolas: ALU, Qualcomm & Huawei

Closed

A-PRO-11.9-013

PRO-2014-0374PRO-2014-0384ARC-2014-1547

Presence of attributes in response message Nobu Open

A-PRO-12.4-001

PRO-2014-0489R01PRO-2014-0488R01

Align the Recourse descriptions with the New template in Annex I

All Open

A-PRO-13.0-001 ARC-2014-1592

Inter-release version negotiation at the API Madhi Open

A-PRO-13.0.003

ARC-2014-1595R01ARC-2014-1596

Common Attributes Phil & Rajesh Open

A-PRO-13.0.003 PRO-2014-0496R01Direct Upload/Download M2M data Shingo

Open

Items for INFORMATION

Items for INFORMATION

© 2013 oneM2M Partners<Document number>

4

Highlights• Baselines available

– TS-0004 v0.6.2 (Core Protocol) Rapporteurs: Shingo Fujimoto & Nobuyuki Uchidasee PRO-2014-0511 V0.7.0 – new baselineProgress at 75% when CRs are incorporated

– TS-0008 v0.5.0 (CoAP Protocol Binding) Rapporteur: SeongYoon Kim see PRO-2014-0414 v0.5.0 – FrozenProgress at 70% - no change

– TS-0009 v0.4.3 (HTTP Protocol Binding) Rapporteur: SeungMyeong Jeongsee PRO-2014-0513 v0.5.0 – New BaselineProgress at 75% when CRs are incorporated

– TS-0010 v0.2.0 (MQTT Protocol Binding) Rapporteur: Peter Niblettsee PRO-2014-0515-Output_Draft_TS-0010_MQTT_Protocol_Binding_v_0_3_0

– Progress at 70% Frozen at Working Group with the CRs incorporated

© 2013 oneM2M Partners<Document number>

5

Issues for INFORMATION in the TP

© 2013 oneM2M Partners<Document number>

6

TS-0004:

Item Document Number Short name Source Late ?12.4.01 PRO-2014-0436R03 TS-0004_Annex_F_Cleanup Qualcomm Agreed as revised

12.5.03 PRO-2014-0443R03 Complex_Type_Definitions_for_MIME_Types Fujitsu Agreed as R03

12.5.04 PRO-2014-0444R04 Restructuring Common Data Types Fujitsu Agreed as R04 13.0.04 PRO-2014-0489R03 TS-0004_sec_7.3.16_cleanup InterDigital Agreed as R0313.0.05 PRO-2014-0488R02 TS-0004_sec_7.3.15_cleanup InterDigital Agreed as R0213.0.06 PRO-2014-0483R02 TS-0004_updates_on_ac_and_cmdh_policies Qualcomm Inc. (TIA) Agreed as R0213.0.08

PRO-2014-0477R03 procedure-for-service-layer-managements Huawei Technologies Co. Agreed as R0313.0.09

PRO-2014-0476R01 aggregate-notifications Huawei Technologies Co. Agreed13.0.14 PRO-2014-0469R01 CR_TS-0004_subscription InterDigital Agreed13.0.15 PRO-2014-0468R02 CR_TS-0004_remoteCSE InterDigital Agreed as R0213.0.16 PRO-2014-0467R02 CR_TS-0004_node InterDigital Agreed as R0213.0.18 PRO-2014-0465R03 CR_TS-0004_contentInstance InterDigital Agreed as R0313.0.19 PRO-2014-0464R02 CR_TS-0004_container InterDigital Agreed as R0213.0.23 PRO-2014-0448R02 CR_TS-0004_statsConfig InterDigital Agreed as R0213.0.26 PRO-2014-0472R02 TS0004 XSD Change Request IBM Agreed as R0213.0.51 PRO-2014-0508R04 short names Telecom Italia Agreed as R0413.0.52 PRO-2014-0507R01 TS-0004_sec_6_3_2_2_update Interdigital Agreed

13.0.53 PRO-2014-0509R01 Event Category in Notification Procedure LG Electronics Agreed

Issues for INFORMATION in the TP

© 2013 oneM2M Partners<Document number>

7

TS-0004:

Item Document Number Short name Source Late ?13.0.12 PRO-2014-0471R03 Design principles IMT Agreed as R0313.0.17 PRO-2014-0466R03 CR_TS-0004_CSEBase InterDigital Revised13.0.20 PRO-2014-0463R02 CR_TS-0004_AE InterDigital Agreed as R0213.0.21 PRO-2014-0450R01 CR_TS-0004_statsCollect InterDigital Agreed13.0.22 PRO-2014-0449R02 CR_TS-0004_eventConfig InterDigital Agreed as R0213.0.54

PRO-2014-0510R02 JSON Principles IBM Agreed as R02

Issues for INFORMATION in the TP

© 2013 oneM2M Partners<Document number>

8

TS-0009 & TS-0010:Contributions about Protocol TS-0009/WI-0013: HTTP binding –

75%

Contributions about Protocol TS-0010/WI-0014: MQTT binding – 70%

Item Document Number

Short name Source Late ?

13.0.01 PRO-2014-0479R02 MQTT Editorial CR IBM Agreed as R02

13.0.02 PRO-2014-0490R01 MQTT Primitive Mapping IBM Agreed as R01

Item Document Number

Short name Source Late ?

13.0.01 PRO-2014-0475R03

HTTP Binding CRUD operations FUJITSU

Agreed as R03

13.0.02 PRO-2014-0474R01 HTTP Binding Overview FUJITSU Agreed

Next Steps - Core Spec/TS 0004

© 2013 oneM2M Partners<Document number>

9

TS Issue VolunteerCore Protocol “TBD”s in the spec. (list of this TBD

needs to be categorized first)one of the rapporteurs?

authorization check in the generic procedure (clause 7.2.1.2)

SeungMyeong

XSD (see list below) Wolfgang and PeterJSON Phil Brown & PeterData type definitions (clause 6.3)

This needs to be aligned with XSDs and described in the spec.

MIME type definition (clause 6.7) SeungMyeong and Shingofilter criteria in query string Shingodata type for typeOfContent in <contentInstance>

Protocol/Architecture (joint issue) Indication of full update and partial update

Bindings review of primitive parameter

mapping

PRIORITIES:

Next Steps - Core Spec/TS 0004• Issue regarding generating XSD files

– Small update to Annex F to allow the Management Resources to inherit from <mgmtObj>

– Resolution of a number of XML design questions. We have already made decisions on most of these, but there might be a case for changing some of these decisions

• What (if anything) do we want to be able to validate with the schemas - the actual resources, the request and response primitives, the cn payloads of the request and response primitives? The answers to this could result in a substantial change to Annex F and the schemas we have done to date

• ChildResourceRef (I have heard a suggestion that we should revisit the idea of allowing child resources to be in-lined)

• Allowing resource attributes to be serialized in any order • Allowing attributes of multiplicity > 1• Use of string-based enumerations in addition to integer ones • Conventions/guidance for names of the m2m: types • Guidelines for use of anonymous vs named types • Extensibility & Versioning

© 2013 oneM2M Partners<Document number>

10

Next Steps - Core Spec/TS 0004• Issue regarding generating XSD files

– Systematic review of the text descriptions of the Resources in clause 7 and Annex D, focussing on the parts of them that affect the schemas

• Check that the attribute lists match TS-0001 • Check that the types listed are appropriate (value space and m2m: type name) • Look for consistency of the types used across different Resources

– Updates to the Common Types and enumerations listed in clause 6.3 • Ensure all the m2m: types referenced in clause 7 and Annex D are there• Check the content models of the complex types, and the definitions of the simple types against TS-

0001

– Bring the common types / enumeration files into synch with the text in clause 6.3 – Review & fix up the Resource XSDs. This should be fairly mechanical once step 3 is complete

• Conformance to the Annex F (especially the copyright text and the namespace declarations)• Conformance to the clause 7 and Annex D definition • Conformance of cardinalities to TS-0001 • Schema validity

– Author the missing XSDs – Repeat the process for the parameter definitions (if we decide we need XSDs for them).

© 2013 oneM2M Partners<Document number>

11

Next Meetings / Calls• Conference Calls

– PRO13.1 Tuesday – 12:00 noon UTC, October 07 – 90 minutes– PRO13.2 Tuesday – 12:00 noon UTC, October 14 – 90 minutes– PRO13.3 Tuesday – 12:00 noon UTC, October 21 – 90 minutes– PRO13.4 Tuesday – 12:00 noon UTC, October 28 – 90 minutes– PRO13.5 face-to-face Wednesday November 05 – Friday November 07–

09:00 Bungang, nr. Seoul; Korea

• Face to Face– TP.14 Busan, Korea 10-14 November 2014

© 2013 oneM2M Partners<Document number>

12