Is it correct that most BLE communication uses GATT server/client relationships or BLE mesh networks
I am developing a Zephyr OS runtime system to use BLE for communication between two nrf52840dk boards. I want a generic API for facilitating this BLE communication, which would look like this:
Currently, I have a GATT server and client setup where the server notifies the client of attribute changes to send messages and the client also writes to the server's attribute to send messages.
In other words, I have two questions to ask:
1. Is it correct that most BLE communication uses GATT server/client relationships or BLE mesh networks?
2. Where can I find more information on creating a generic API like the one above, or does such an API already exist? @Middleware & OS
Currently, I have a GATT server and client setup where the server notifies the client of attribute changes to send messages and the client also writes to the server's attribute to send messages.
In other words, I have two questions to ask:
1. Is it correct that most BLE communication uses GATT server/client relationships or BLE mesh networks?
2. Where can I find more information on creating a generic API like the one above, or does such an API already exist? @Middleware & OS
Solution
You can check out this GitHub link
https://github.com/zephyrproject-rtos/zephyr/blob/main/samples/bluetooth/mesh_provisioner/README.rst
https://github.com/zephyrproject-rtos/zephyr/blob/main/samples/bluetooth/mesh_provisioner/README.rst
GitHub
Primary Git Repository for the Zephyr Project. Zephyr is a new generation, scalable, optimized, secure RTOS for multiple hardware architectures. - zephyrproject-rtos/zephyr
