2012. 6 / [email protected] M2MWG2(12)000002 Discrimination methods for container resource with nodeID 20 th June 2012 / Sang-Eon Kim

2012. 6 / [email protected]

M2MWG2(12)000002

Discrimination methods for container resource with nodeID

20th June 2012 / Sang-Eon Kim


Early discussion

Early discussion by E-mail

Michele LUPANO, 22th May.

- the nodeID attribute should be “optional”

- this attribute is useful in the use cases that you (Sang-Eon) mentioned.

George Foti, 23th May

- I view this as optimization.

- I understand the point but I question where optimization on an ad hoc basis is the way to go.

Raymond Forbes, 23th May

- This will be discussed in the M2M WG3 Call Thursday 24 May 15.00-16.00 CEST

Zhou Jingyi, 24th May

- Please see attached slides that demonstrate similar problem(I think).

Notes for GoToMeeting Invitation - M2M WG3 no.4

M2M(12)20_034 “A Discrimination methods for container resource with node identification” discussed

at WG3 conference call on 24th May.

Results of the discussion [reference: E-mail on 24th May]

- This presents the need for a Node ID to identify the unique instance & routing of the information &

control. This provoked a wider discussion that will be continued Offline & at the next meeting.

2


Discussion at M2M#20

M2M#20 Meeting at Kista

M2M(12)20_125 ““A Discrimination methods for container resource with node identification” was

discussed at WG2 on 5th June.

Results of the WG2 discussion [reference: M2M(12)20_143]

- Discussion on multi-thread support & different application Ids. Also discussed that no current

requirement exist for this CR.

- Further discussion required.

Revised Document based on face-to-face discussion during the M2M#20 [reference:

M2M(12)20_125r3]

- Introduce ‘creator’ attribute instead of nodeID

- Propose to add creator attribute to resources which has ‘creationTime’ attribute in section 9.2.3

and Annex B.

Postponed at Plenary on 8th June. [reference: M2M(12)20_002r7]

3


Summary of the M2M(12)20_125r3

Introduce ‘creator’ attribute in section 9.2.2

Propose a change 1

Change request for Common attributes in section 9.2.2

4



Propose to add ‘creator’ attribute to the resources in section 9.2.3.

Propose a change 2 – change 29.

Change Request for Resources: 9.2.3.X

2 <sclBase>, 3 scls, 4 <scl>, 5 applications, 6 <application>, 8 accessRights, 9 <accessRight>,

11 containers, 12 <container>, 14 <locationContainer>, 16 contentInstances, 17

<contentInstance>

18 groups, 19 <group>, 23 <subscription>, 24. m2mPocs, 25 <m2mPoc>, 26 mgmtObjs, 27

<mgmtObj>

28 <parameters>, 29 <mgmtCmd>, 30 execInstances, 31 <execInstance>, 32 attachedDevices

33 <attachedDevice>, 34 notificationChannels, 35 <notificationChannel>, 37 subcontainers

An example of change request

5



Propose to add ‘creator’ attribute to the resources in Annex B.

Propose a change 30 – change 58.

Change Request for Resources: B.X.X.(X)

2.1 etsiSclMo, 2.1.1 sclMoAction , 2.1.2 <safPolicySet>, 2.1.3 <anpPolicy>, 2.1.4 m2mSpPolicy,

2.2 etsiDeviceInfo, 2.3 etsiDeviceCapability, 2.3.1 <capabilityInstance>, 2.3.2 capabilityAction,

2.4 etsiBattery, 2.4.1 <batteryInstance>, 2.5 etsiMemory, 2.6 etsiTrapEvent, 2.6.1 <trapInstance>,

2.6.2 trapEventAction , 2.7 etsiPerformanceLog, 2.7.1 perfLogAction, 2.8 etsiFirmware, 2.8.1

<fwInstance>,

2.8.2 firmwareAction, 2.9 etsiSoftware, 2.9.1 <swInstance>, 2.9.2 softwareAction, 2.10 etsiReboot,

2.10.1 rebootAction, 2.11 etsiAreaNwkInfo, 2.11.1 <areaNwkInstance>, 2.12 etsiAreaNwkDeviceInfo,

2.12.1 <areaNwkDeviceInfoInstance>,

An example of change request

6


Use case: e-Health

ETSI M2M server

mIddIa mIa

M2M Authentication Server

GA

Jean

Jack

John

jackson

NA

GSCL

NSCL

M2M Service Bootstrap Function

Network Application Function

Heart

Rate

Monitor

Applicatio

n

D’ G

N

M2M Application

Heart rate monitor

D

Heart rate monitor

james

smith

mary

How John, Jack and Jean been distinguished in N/G/DSCL for communication?

How data consumed by John, Jack and Jean in access network been calculated in NSCL

independently? [reference] Jingyi, “M2M Multi-User Heart Rate Monitor App.” Verizon, May. 2012

7


Discussion

Usage of ‘creator’ attribute for a resources

All resource that has creationTime attribute [M2M(12)20_125r3] vs. container related resources

[M2M(12)20_125]

<NSCLBase>/applications/HeartRateMonitor/containers/heartRateMonitor

- When the same container is shared between different apps, is it important to allow filtering based on the

creator.

How to use the creator attribute only in the filterCriteria used for subscriptions and retrieving resources.

The uniqueness of the creator. It may implementation issues.

Requirement (102 689)

6.1 Data collection & reporting

The M2M System shall support the reporting from a specific M2M Device or M2M Gateway or group of M2M

Devices or group of M2M Gateways in the way requested by the M2M Application as listed below:

- a periodic reporting with the time period being defined by the M2M application;

- ……

The M2M System shall support identification of source information for data collection and reporting.

6.2 Remote control of M2M Devices

The M2M System shall support the capability for an Application to remotely control M2M Devices that support

this capability.

- Identification of SCL or Application of M2M Device/Gateway

8

Documents

2012. 6 / [email protected] M2MWG2(12)000002 Discrimination methods for container resource with nodeID 20 th June 2012 / Sang-Eon Kim