oneM2M Interworking Proxy Entity (LWM2M)

LWM2M device to work with oneM2M server side platform.

ETC

Interworking

v1.0.0
July 14, 2017

nmsung@keti.re.kr
Sung, Nak-Myoung

Git Hub Project Link
LWM2M-IPE

 

Gub Hub Release Direct DownLoad Link
Direct Link Revision Release Date
LWM2M IPE master.zip file v1.0 July 2017

Hardware Connectivity

  1. Connect LED light, DHT11 Sensor to Arduino UNO with pins.
  2. Connect Arduino UNO to PL2303 USB UART with pins.
  3. Connect PL2303 USB UART to Raspberry pi 3 with USB port.

 


IPE Sample Software

  1. Download LWM2M IPE sample source from IoT OCEAN home page.
  2. Download Eclipse Neon from Eclipse home page.
  3. Download Arduino IDE from Arduino IDE home page.
  4. Install Eclipse, Arduino IDE on Windows by double click the installer.

Execution

  1. Connect Arduino UNO to PC with debugging USB cable then compile and upload source.
  2. Export “keti_lwm2m_device” as runnable jar file named “.jar” then copy “.jar” file and “port.conf”(In project) file to raspberry pi.
  3. Export “keti_lwm2m_ipe” as runnable jar file named “<name.jar>” then copy “.jar” file and “tas_conf.xml”(In project) file to raspberry pi.
  4. Copy webapp folder to raspberry pi jar file path from “keti_lwm2m_device” project.
  5. Configure tas_conf.xml and port.conf.
  6. Run java thyme 1.5(Refer to Thyme guide document from IoT OCEAN home page.
  7. Run LWM2M IPE
  8. Run LWM2M device client.

Testing

  • LWM2M testing Open http://[raspberry pi IP]:8080 in web browser.

 

  • oneM2M testing
  1. Run Resource Tree Viewer available at IoT OCEAN Site.

2. Input AE resource path (depended the thyme conf.json) in textbox and click start then the above LWM2M IPE’s resource structure will be displayed. If temperature or humidity value is changed then viewer will add new resource object with “new!” tag. 3. Open post man from google chrome and send content instance create request to mobius-yt as figure 20. 4. If IPE sample build is successfully done, physical LED light turns on when LWM2M log device “led” status changes “off” to “on”.

oneM2M Interworking Proxy Entity(IPE): LWM2M


what is oneM2M LWM2M IPE?

oneM2M is an IoT server platform standard that supports devices as well as cloud server, while LWM2M(Light Weight Machine to Machine is an IoT service platform that supports devices. IPE(Interworking Proxy Entity) defined in oneM2Menables LWM2M device to work with oneM2M server side platform.


Environment

  • LWM2M IPE uses Eclipse Leshan source code as a basis which is aligned with LWM2M standard implemented in C and Java.
  • A gateway is required to run Eclipse Leshan core and oneM2M device platform which is implemented in in Java or Node.js.

BSD 3-Clause License

Copyright (c) 2017, IoTKETI All rights reserved Redistribution and use in source and binary forms, with or without modification, are permitted provided that the following conditions are met:

* Redistributions of source code must retain the above copyright notice, this list of conditions and the following disclaimer.

* Redistributions in binary form must reproduce the above copyright notice, this list of conditions and the following disclaimer in the documentation and/or other materials provided with the distribution.

* Neither the name of the copyright holder nor the names of its contributors may be used to endorse or promote products derived from this software without specific prior written permission.

THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS “AS IS” AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT HOLDER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.