| Summary: | 碩士 === 國立交通大學 === 電機資訊國際學程 === 103 === IoT/M2M aims to integrate a large number of heterogeneous devices which are constantly required to be discovered and reconfigured in order to bring them up to date or to recover their failures. The device management protocol is needed to reduce the amount of time to configure and to manage those IoT/M2M devices, especially for the M2M devices located in the remote area. The device management protocol enables abstraction of an IoT/M2M device as a managed object to ease the management of device; to do this for IoT/M2M devices, this abstraction has to be concise and lightweight. The IoT/M2M international standard organizations, such as ETSI and OneM2M, proposed the use of lightweight device management protocol called Open Mobile Alliance Lightweight M2M (OMA LWM2M) protocol to manage and to configure the IoT/M2M devices from IoT/M2M platform. By incorporating device management in the IoT/M2M platform, we can establish device management sessions that allow an IoT/M2M application to manage IoT/M2M devices remotely from the IoT/M2M service platform. For example, by manipulating resource trees in the cyber space from the IoT/M2M platform we gain access and control to the corresponding sensors/devices in the physical world. However, how to perform resource mapping of OMA LWM2M in the IoT/M2M standard architecture platform is not well addressed by the standard.
In this research, we examine how to incorporate the OMA LWM2M in the M2M standard architecture and we analyze how the M2M standard architecture can collaborate and communicate with OMA LWM2M protocol to establish device management sessions. For the experimental process, we analyze the resource mapping of OMA LWM2M objects and resources into the ETSI M2M resource tree by analyzing the processes of (1) Bootstrapping, (2) Registration, and (3) Management and Service Enablement Session.
1. The bootstrapping process is used to provision the OMA LWM2M objects to the IoT/M2M platform for device management session.
2. The registration process is used to register the OMA LWM2M Client and its Objects in the OMA LWM2M Server. This process is analyzed during the device triggering session.
3. The Device Management and Service Enablement Session is a procedure of accessing Object or Resource of the OMA LWM2M Client by an M2M application using OMA LWM2M Server.
In order to proceed with our implementation and analysis, we develop Remote Entity Management (REM) Service Capability on top of the OpenMTC, an ETSI M2M standard compliant system from Fraunhofer FOKUS. We also utilize Eclipse Leshan and Wakaama that are the OMA LWM2M open-source reference implementations to implement the REM Capability. To proceed with the analysis, we build an IoT/M2M application and do features testing on it. The feature testing includes the manipulation of the device objects and resources using RESTful commands, the simulation of firmware update mechanism, and the simulation of the remote reboot mechanism for fault management.
|
|---|
