oneM2M Interworking Proxy Entity (OCF)

Development Environmental Setup

• Download IoTivity open source from IoTvity home page. URL.(https://www.iotivity.org)

Compilation

1. Unzip OCF IPE sample file and get a set of source files & libraries.
2. Copy all sample source files to “…//resource/examples” folder.
3. Open SConscript file in “…//resource/examples” folder and add the code at “Source file and Target”
4. Go to “…/” folder and compile the source with “scons” command line in Ubuntu Terminal.

Execution

In case of testing without real OCF device, we recommend to run [simpleserver] as a virtual OCF light device in “…//out///release/resource/examples” folder. OCF IPE sample code is designed to communicate with Mobius platform using Thyme(&Cube).

1. Activate a local Mobius platform if you don’t want to use the KETI Mobius-yt.
2. Activate Thyme after editing configuration file as below.
3. Activate the “simpleserver” in “…//out/linux//release/resource/examples” folder.
4. Activate ocf_ipe in “…//out/linux//release/resource/example” folder.

5. Retrieve virtual OCF device status with Mobius-yt API using postman.

6. Control virtual OCF devices with Mobius-yt API using postman.

oneM2M Interworking Proxy Entity(IPE): OCF

what is oneM2M OCF IPE?

oneM2M is an IoT server platform standard that supports devices as well as cloud server, while OCF(Open Connectivity Foundation) is an IoT service platform that supports devices. IPE(Interworking Proxy Entity) defined in oneM2M enables OCF devices to work with oneM2M server side platform.

Environment

• OCF IPE uses IoTivity source code as basis which is aligned with OCF standard. It is implemented in C++ and C.
• A gateway is requried to run IoTivity core and oneM2M device platform which is implemented in Java or Node.js.

Notice

This version of OCF IPE is working base on IoTivity 1.2.1. Other version of IoTivity that we did not test yet.

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.