Presentation on theme: "Is a Node or not Node? ARC-2014-1194-Node_resolution Group Name: ARC Source: Barbara Pareglio, NEC, Meeting Date: ARC#9.1 Agenda."— Presentation transcript:
Is a Node or not Node? ARC Node_resolution Group Name: ARC Source: Barbara Pareglio, NEC, Meeting Date: ARC#9.1 Agenda Item: Contribution
Problem statement Node is a logical entity which sometimes it refers to the physical device The existence of node seems to be associate with the bootstrap for retrieving the CSE-ID, for this reason Nodeless- AE is not equal to ADN-AE The node is used to hook mgmtObj for the ADN node There is a need to have a device ID for DM, not clear if it can be the M2M-Node-ID or not. Nodeless-AE are considered different either from IN-AE and from ADN-AE. Not clear what it can be “managed” and how.
Current status of Node in TS0001 – Definitions: Node: A functional entity containing one of the following: one or more M2M Applications; one CSE and zero or more M2M Applications. – Section 6: Nodes: Two types of oneM2M Nodes are supported: A CSE-Capable Node is a functional entity that contains at least one oneM2M Common Services Entity and zero or more oneM2M Application Entities. ASN and MN are examples of such type of Nodes. A Non-CSE-Capable Node is a functional entity that contains one or more oneM2M Application Entities and no oneM2M Common Service Entity. ADN, Nodeless-AE isare an examples of such type of Nodes. Editor's Note: How Node-less AEs are classified is FFS.
Current status of Node in TS0001 – Section 6: Description of Nodes: oneM2M architecture foresees the following types of Nodes. It is important that as functional objects, such Nodes are not necessarily mapped to actual physical objects, although they may be mapped to actual physical objects.
Current status of Node in TS0001 – Section Application and Service Layer Management: Only Software Management is allowed for AEs, nothing else.
Current status of Node in TS0001 – Section Device Management: The Device Management (DMG) CSF is responsible for providing management of device capabilities on Middle Nodes (M2M Gateways), Application Service Nodes and Application Dedicated Nodes (M2M Devices) as well as devices that reside within an M2M Area network. Application Entities (AE) can manage the device capabilities on those Nodes by using the services provided by DMG CSF alleviating the need for the AE to have knowledge of the management technology specific protocols or data models. While the AE does not require an understanding of the management technology specific protocols or data models, this information is provided to the AE so that an AE may utilize this informaton for administrative purposes (e.g., diagnostics, troubleshooting, etc.). Which AEs? IN-AEs or any AE?
Current status of Node in TS0001 – Section Registration: A (physical) Device shall be able to register with its local CSE for registering its properties/attributes. Such registration enables correlation of Devices Identities such as M2M-Node-ID with the CSE-ID.
– Section M2M Node Identifier (M2M-Node- ID): M2M Node Identifier (M2M-Node-ID) An M2M node, hosting a CSE and/or Application(s) shall be identified by a globally unique identifier, the M2M ‑ Node ‑ ID. The M2M System shall allow the M2M Service Provider to set the CSE-ID and the M2M-Node-ID to the same value. The M2M-Node-ID enables the M2M Service Provider to bind a CSE-ID to a specific M2M node. Only true if there is a CSE in the Node Current status of Node in TS0001
– Section 7.2 M2M Identifiers lifecycle and characteristics: An M2M node host a CSE according to the table M2M Node Identifier Out of ScopeM2M Node hosting CSE Pre-provisionedLife of the M2M Node GlobalSecurity provisioning (FFS) Needs to be Read Only
Current status of Node in TS0001 – Section : Too much info, either use Node or list App and CSE This is for the subscription and we should refer to CSEs only and the Apps registered to those. Is this really node or CSE? Did we ever said in the TS that there are more CSEs in one node?
Current status of Node in TS0001 – Section : The resource represents specific information of a M2M Node that can be utilized by other oneM2M operations. For example, the CMDH CSF can determine when the CSE sends a request message to the target CSE based on the target CSE's reachability schedule. This resource type mainly contains the properties of an M2M Node such as reachability schedule, context information (e.g. memory and storage) and network topology. This node specific information stored in this resource type such as memory and storage can be obtained either by the existing device management technologies (OMA DM, BBF TR-069 [i.12]) or any other way (e.g. through JNI (Java Native Interface)). Since resource type represents the management functions including both ways, the types of sub-resources are resource type.
Current status of Node in TS0001 – Section : Contains 2 type of information: – mgmtObj – schedule DTMF
Summary ADN and Nodeless are considered Node (section 6) Nodes are not physical devices (section 6) The only Application layer management is for SW (section 6.2.1). Actually also for CSE, since CF and DMF are not really defined. DM allows to manage the ADN-Node but is identify as a devices (6.4 which contradict 6). (manage DCF, DDMF, DFMF and DTMF) Only DTMF seems to be part of resource M2M-Node-ID is considered as the device ID (6.2.9, contradict 6)
Summary The M2M-Node-ID is assigned to node with a CSE (section 7.2 contradict 6) CSEBase, remoteCSE and Application resources are not consistenly using and
Proposal Add also to resource Move directly under the resources:, and Define if needed,,, as independent Eliminate Either remove the mgmtObj software from application or add it also in the CSEs resources.
Proposal Define, not clear which protocol it refers to. (probably we need it also for other reference point and not only Mca). Change name of to and if possible avoid to use the node-ID, but only CSE-ID and AE-ID Remove the notation of Nodeless-AE, just use IN-AE Do not show the node in the figure 6.1, only show the entities defined in (AE, CSE, NSE) or show it only in the field domain. Preferred solution would be to use device, if that is what it is.