OrgZephyr/zephyr
OrgZephyr
/
zephyr
mirror of https://github.com/zephyrproject-rtos/zephyr.git
1
0
Fork 0
Code Issues Releases Wiki Activity
zephyr/include/bluetooth/mesh.h

30 lines
728 B
C
Raw Normal View History

Bluetooth: Mesh: Add initial implementation Add an initial implementation for the Bluetooth Mesh Profile Specification. The main code resides in subsys/bluetooth/host/mesh and the public API can be found in include/bluetooth/mesh.h. There are a couple of samples provided as well under samples/bluetooth and tests/bluetooth. The implementation covers all layers of the Bluetooth Mesh stack and most optional features as well. The following is a list of some of these features and the c-files where the implementation can be found: - GATT & Advertising bearers (proxy.c & adv.c) - Network Layer (net.c) - Lower and Upper Transport Layers (transport.c) - Access Layer (access.c) - Foundation Models, Server role (health.c & cfg.c) - Both PB-ADV and PB-GATT based provisioning (prov.c) - Low Power Node support (lpn.c) - Relay support (net.c) - GATT Proxy (proxy.c) Notable features that are *not* part of the implementation: - Friend support (initial bits are in place in friend.c) - Provisioner support (low-value for typical Zephyr devices) - GATT Client (low-value for typical Zephyr devices) Jira: ZEP-2360 Change-Id: Ic773113dbfd84878ff8cee7fe2bb948f0ace19ed Signed-off-by: Johan Hedberg <johan.hedberg@intel.com>
2017-06-16 17:30:54 +08:00
/** @file
* @brief Bluetooth Mesh Profile APIs.
*/
/*
* Copyright (c) 2017 Intel Corporation
*
* SPDX-License-Identifier: Apache-2.0
*/
headers: Fix headers across the project Any word started with underscore followed by and uppercase letter or a second underscore is a reserved word according with C99. Signed-off-by: Flavio Ceolin <flavio.ceolin@intel.com>
2018-09-15 01:43:44 +08:00
#ifndef ZEPHYR_INCLUDE_BLUETOOTH_MESH_H_
#define ZEPHYR_INCLUDE_BLUETOOTH_MESH_H_
Bluetooth: Mesh: Add initial implementation Add an initial implementation for the Bluetooth Mesh Profile Specification. The main code resides in subsys/bluetooth/host/mesh and the public API can be found in include/bluetooth/mesh.h. There are a couple of samples provided as well under samples/bluetooth and tests/bluetooth. The implementation covers all layers of the Bluetooth Mesh stack and most optional features as well. The following is a list of some of these features and the c-files where the implementation can be found: - GATT & Advertising bearers (proxy.c & adv.c) - Network Layer (net.c) - Lower and Upper Transport Layers (transport.c) - Access Layer (access.c) - Foundation Models, Server role (health.c & cfg.c) - Both PB-ADV and PB-GATT based provisioning (prov.c) - Low Power Node support (lpn.c) - Relay support (net.c) - GATT Proxy (proxy.c) Notable features that are *not* part of the implementation: - Friend support (initial bits are in place in friend.c) - Provisioner support (low-value for typical Zephyr devices) - GATT Client (low-value for typical Zephyr devices) Jira: ZEP-2360 Change-Id: Ic773113dbfd84878ff8cee7fe2bb948f0ace19ed Signed-off-by: Johan Hedberg <johan.hedberg@intel.com>
2017-06-16 17:30:54 +08:00
#include <zephyr/types.h>
#include <stddef.h>
#include <net/buf.h>
Bluetooth: Mesh: Refactor public headers into dedicated subdirectory As the number of mesh APIs grows it becomes a bit cumbersome to have everything in a single header file. Split the mesh.h header file into multiple files in a new mesh subdirectory, and include the new headers from the old one to retain backwards compatibility and simplicity for apps (they only need to include <bluetooth/mesh.h>). Signed-off-by: Johan Hedberg <johan.hedberg@intel.com>
2017-11-12 19:33:26 +08:00
#include <bluetooth/mesh/access.h>
#include <bluetooth/mesh/main.h>
Bluetooth: Mesh: Encapsulate feature config Moves mesh feature configuration to a separate module, deprecating the bt_mesh_cfg_srv structure. The initial values for the features should now be enabled through KConfig, where new config entries have been added for each feature. This removes the upward dependency on the config server from the core stack, and makes the config server a pure frontend for the configuration states, as all spec mandated behavior around the feature states is now encapsulated. Signed-off-by: Trond Einar Snekvik <Trond.Einar.Snekvik@nordicsemi.no>
2020-08-18 19:36:38 +08:00
#include <bluetooth/mesh/cfg.h>
Bluetooth: Mesh: Refactor public headers into dedicated subdirectory As the number of mesh APIs grows it becomes a bit cumbersome to have everything in a single header file. Split the mesh.h header file into multiple files in a new mesh subdirectory, and include the new headers from the old one to retain backwards compatibility and simplicity for apps (they only need to include <bluetooth/mesh.h>). Signed-off-by: Johan Hedberg <johan.hedberg@intel.com>
2017-11-12 19:33:26 +08:00
#include <bluetooth/mesh/cfg_srv.h>
#include <bluetooth/mesh/health_srv.h>
Bluetooth: Mesh: Add skeleton for Configuration Client Model Signed-off-by: Johan Hedberg <johan.hedberg@intel.com>
2017-11-12 19:48:55 +08:00
#include <bluetooth/mesh/cfg_cli.h>
Bluetooth: Mesh: Add skeleton for Health Client model Add a skeleton for the Health Client model. Signed-off-by: Johan Hedberg <johan.hedberg@intel.com>
2017-11-22 14:49:52 +08:00
#include <bluetooth/mesh/health_cli.h>
Bluetooth: Mesh: Refactor public headers into dedicated subdirectory As the number of mesh APIs grows it becomes a bit cumbersome to have everything in a single header file. Split the mesh.h header file into multiple files in a new mesh subdirectory, and include the new headers from the old one to retain backwards compatibility and simplicity for apps (they only need to include <bluetooth/mesh.h>). Signed-off-by: Johan Hedberg <johan.hedberg@intel.com>
2017-11-12 19:33:26 +08:00
#include <bluetooth/mesh/proxy.h>
Bluetooth: Mesh: Move heartbeat to separate module Encapsulates the Heartbeat state and functionality in a separate heartbeat module, removing all manipulation of the heartbeat state from the transport and config server modules. Signed-off-by: Trond Einar Snekvik <Trond.Einar.Snekvik@nordicsemi.no>
2020-08-12 23:07:38 +08:00
#include <bluetooth/mesh/heartbeat.h>
Bluetooth: Mesh: Add database for managing nodes and keys Refactor the handling of network nodes and their keys into a separate Mesh Configuration Database (CDB). This, not only creates a separation of the local node and the other nodes, but also makes it possible to implement functions to manage the whole, or at least parts of the mesh network. Signed-off-by: Tobias Svehagen <tobias.svehagen@gmail.com>
2019-11-04 23:14:07 +08:00
#include <bluetooth/mesh/cdb.h>
Bluetooth: Mesh: Isolate cryptographic material This is a major refactoring of the handling of the cryptographic material of both the network and transport layers. The aim is to encapsulate the key object manipulation, and improve overall modularity. Pulls Applications and Subnets out of the bt_mesh and into separate modules, with static storage types on the data. This has several side-effects: - The Config Server no longer operates directly on the bt_mesh.subs and bt_mesh.apps lists, but goes through a public configuration interface, following the pattern set in #27908. - All iteration through the keys is done through iteration APIs - Key resolution on RX and TX is centralized. - Changes to the keys triggers events the other modules can register handlers for. - Friendship credentials are stored in the lpn and friend structures. Part of #27842. Signed-off-by: Trond Einar Snekvik <Trond.Einar.Snekvik@nordicsemi.no>
2020-08-25 17:03:42 +08:00
#include <bluetooth/mesh/cfg.h>
Bluetooth: Mesh: Add initial implementation Add an initial implementation for the Bluetooth Mesh Profile Specification. The main code resides in subsys/bluetooth/host/mesh and the public API can be found in include/bluetooth/mesh.h. There are a couple of samples provided as well under samples/bluetooth and tests/bluetooth. The implementation covers all layers of the Bluetooth Mesh stack and most optional features as well. The following is a list of some of these features and the c-files where the implementation can be found: - GATT & Advertising bearers (proxy.c & adv.c) - Network Layer (net.c) - Lower and Upper Transport Layers (transport.c) - Access Layer (access.c) - Foundation Models, Server role (health.c & cfg.c) - Both PB-ADV and PB-GATT based provisioning (prov.c) - Low Power Node support (lpn.c) - Relay support (net.c) - GATT Proxy (proxy.c) Notable features that are *not* part of the implementation: - Friend support (initial bits are in place in friend.c) - Provisioner support (low-value for typical Zephyr devices) - GATT Client (low-value for typical Zephyr devices) Jira: ZEP-2360 Change-Id: Ic773113dbfd84878ff8cee7fe2bb948f0ace19ed Signed-off-by: Johan Hedberg <johan.hedberg@intel.com>
2017-06-16 17:30:54 +08:00
headers: Fix headers across the project Any word started with underscore followed by and uppercase letter or a second underscore is a reserved word according with C99. Signed-off-by: Flavio Ceolin <flavio.ceolin@intel.com>
2018-09-15 01:43:44 +08:00
#endif /* ZEPHYR_INCLUDE_BLUETOOTH_MESH_H_ */