I am more familiar with the Nimble code. What is done there is define a transport for coap messages over a BLE connection. Of course there is also the Gatt profile/service that defines the BLE peripheral node as an OIC capable node so interested nodes can discover and connect to it. For the official iotivity linux code (resource/csdk/connectivity/src/bt_le_adapter/linux), it uses the Bluez stack which (in my opinion) is very complex. I am not sure what is exactly done but must be similar in concept to that.
On Tue, Jun 5, 2018 at 6:19 PM, Gregg Reynolds <d...@mobileink.com> wrote: > > > On Tue, Jun 5, 2018 at 5:01 AM, Khaled Elsayed <khaledi...@gmail.com> > wrote: > >> I don't think this an official Bluetooth SIG profile. I believe it is >> implemented in iotivity linux (https://wiki.iotivity.org/ble_for_linux) >> and runtime.io Nimble stack. So, you can have a look at the source code. >> It is straightforward if you are generally familiar with Bluetooth >> profiles/GATT. >> >> Thanks. I looked at the code a bit. It looks to me like the idea is > basically a kind of adapter that makes BLE devices look like OCF devices. > I.e. the code converts BLE data to and from Iotivity data structures, so it > looks like Iotivity stuff to the application. Something like that? > > Gregg > >> >> >> >> On Fri, Jun 1, 2018 at 7:54 PM, Gregg Reynolds <d...@mobileink.com> wrote: >> >>> Where can I find more information about the Bluetooth GATT-based OIC >>> Transport Profile? >>> >>> Thanks >>> Gregg >>> >>> >>> >> >
