1. Node-Specific Resource Group Name: ARC&MAS Source: LGE, hongbeom.ahn@lge.com Meeting Date: 2013-11-29 Agenda Item: Contribution

2. Outline Related Requirements Required Node-Specific Information Resource Location of Resource Representation of attributes of Discussion Points © 2013 oneM2M Partners oneM2M-ARC-2013-0573-Introduction_to_nodeSpecific 2

3. Requirements (1/2) We have several requirements that explain why we need to have specific information per a M2M Node at CSE level © 2013 oneM2M Partners oneM2M-ARC-2013-0573-Introduction_to_nodeSpecific 3 OSR-016The M2M System shall provide the capability to notify M2M Applications of the availability of, and changes to, available M2M Application/management information on the M2M Device/Gateway, including changes to the M2M Area Network. OSR-045The M2M System shall be able to be aware of the reachability status and to utilize reachability schedules generated by either the M2M Device or the Infrastructure Domain. OSR-069When available from the Underlying Network, the M2M System shall be able to maintain the M2M Service Operational Status of a M2M Device and update it when the Underlying Network connectivity service status changes.

4. Requirements (2/2) © 2013 oneM2M Partners oneM2M-ARC-2013-0573-Introduction_to_nodeSpecific 4 MGR-002The M2M System shall provide the capability to discover the M2M Area Networks including information about devices on those networks and the parameters (e.g. topology, protocol) of those networks.. MGR-003The M2M System shall be able to provide the capability to maintain and describe the management information model of devices and parameters (e.g. topology, protocol) of M2M Area Networks. MGR-016The M2M System shall be able to retrieve information related to the Static and Dynamic Device/Gateway Context for M2M Gateways/Devices as well as Device Context for other devices in M2M Area Networks.

5. Node-specific Information Required Node-specific information that can be utilized by other oneM2M operations – For ASN/ADN Reachability Schedule Static/Dynamic Device Context – For MN Reachability Schedule Static/Dynamic Gateway Context Topology/Devices behind the MN © 2013 oneM2M Partners oneM2M-ARC-2013-0573-Introduction_to_nodeSpecific 5

6. Related Operations based on Requirements OSR-019 The M2M System shall support the capabilities for data repository (i.e. to collect/store) and for data transfer from one or more M2M Devices or M2M Gateways, for delivery to one or more M2M Gateways, M2M Services Infrastructure, or M2M Application Infrastructure, in ways requested by the M2M Application Infrastructure as listed below: – when triggered by schedule or event; OSR-033 Based on the Dynamic Device/Gateway Context of the M2M Gateway and/or Device and the defined Event Categories, the M2M System shall provide the capability to dynamically adjust the scheduling of reporting and notification of the M2M Device/Gateway. © 2013 oneM2M Partners oneM2M-ARC-2013-0573-Introduction_to_nodeSpecific 6 Transfer scheduling is main role of CMDH CSF and the CSF needs to know about the reachability schedule and context information at the service layer

7. Resource reachabilitySchedule contextInformation topology Attribute NameDescription reachabilityScheduleDefines reachability schedule information of the node. The attributes expresses time periods defined by seconds, minutes, day of month, month and year. Supporting repeating periods and wildcards. contextInformationDefines the Static and Dynamic Context of the node. (e.g., available power and storage) topologyDescribes the list of nodes attached behind the MN node and its relation among the nodes. This attribute is defined in case the Node is MN. More attributes can be added © 2013 oneM2M Partners oneM2M-ARC-2013-0573-Introduction_to_nodeSpecific 7

8. Location of Resource The location of resource can be differentiated according to the type of node – ASN Under of the local CSE MN or IN connected with the ASN shall have the mirror-resource (Detail mechanism of mirroring is FFS) /BaseURI/nodeSpecific – ADN Under resource of the hosting CSE /BaseURI/ /nodeSpecific – MN Under of the local CSE /BaseURI/nodeSpecific © 2013 oneM2M Partners oneM2M-ARC-2013-0573-Introduction_to_nodeSpecific 8

9. Representation of Attributes reachabilitySchedule contextInformation topology reachabilitySchedule is represented by a XML format 1_OCT_2014 020000 000500 040000 4 This representation is determined in Protocol Stage (can be simplified) We can define a schema and reuse some existing schema © 2013 oneM2M Partners oneM2M-ARC-2013-0573-Introduction_to_nodeSpecific 9

10. Representation of Attributes reachabilitySchedule contextInformation topology contextInformation is represented by a XML format 81 okay 20 mega This representation is determined in Protocol Stage (can be simplified) We can define a schema and reuse some existing schema © 2013 oneM2M Partners oneM2M-ARC-2013-0573-Introduction_to_nodeSpecific 10

11. Representation of Attributes reachabilitySchedule contextInformation topology Topology is represented by a XML format This representation is determined in Protocol Stage (can be simplified) We can define a schema and reuse some existing schema © 2013 oneM2M Partners oneM2M-ARC-2013-0573-Introduction_to_nodeSpecific 11

12. Discussion Point 1 How to describe each attribute – Consider that there was a contribution that describe ‘reachabilitySchedule’ with many attributes as an example For Accessibility? Using the partial addressing functionality, AE can access the XML- level information e.g. / / – [WG2 phase] members discuss what kind of information (resource and attribute) is needed and when the resource is created and used for a service or operation – [WG3 phase] The detail of information will be described © 2013 oneM2M Partners oneM2M-ARC-2013-0573-Introduction_to_nodeSpecific 12

13. Discussion Point 2 Does DM-related resource contain these information (reachabilitySchedule, topology,…)? – Seems that following information can be retrieved by existing OMA DM/BBF TR-069 Topology (just attachedDevices) – OMA DM - urn:oma:mo:oma-gwmo-deviceinventory:1.0 – BBF TR-069 - InternetGatewayDeviceLANDevice Some Device/Gateway Context – OMA DM - urn:oma:mo:oma-diag:batteryinfo:1.0 – BBF TR-069 – DeviceInfo – However, what if the Node does not have OMA DM and BBF TR-069 capability, how to support this information? © 2013 oneM2M Partners oneM2M-ARC-2013-0573-Introduction_to_nodeSpecific 13

14. Discussion Point 3 More candidate attributes for this resource type? if we have, we can grow the list of possibly node specific information in the resource type – open to add more attributes Hope we can combine the resource type (ARC-2013-0512), resource can be a child resource of the resource. © 2013 oneM2M Partners oneM2M-ARC-2013-0573-Introduction_to_nodeSpecific 14