Menu
Home Explore People Places Arts History Plants & Animals Science Life & Culture Technology
On this page
Bluetooth mesh networking
Computer mesh networking standard

Bluetooth Mesh is a computer mesh networking standard based on Bluetooth Low Energy that allows for many-to-many communication over Bluetooth radio. The Bluetooth Mesh specifications were defined in the Mesh Profile and Mesh Model specifications by the Bluetooth Special Interest Group (Bluetooth SIG). Bluetooth Mesh was conceived in 2014 and adopted on July 13, 2017 (2017-07-13).

We don't have any images related to Bluetooth mesh networking yet.
We don't have any YouTube videos related to Bluetooth mesh networking yet.
We don't have any PDF documents related to Bluetooth mesh networking yet.
We don't have any Books related to Bluetooth mesh networking yet.
We don't have any archived web articles related to Bluetooth mesh networking yet.

Overview

Bluetooth Mesh is a mesh networking standard that operates on a flood network principle. It's based on the nodes relaying the messages: every relay node that receives a network packet that

  • authenticates against a known network key
  • is not in message cache
  • has a TTL ≥ 2

can be retransmitted with TTL = TTL - 1. Message caching is used to prevent relaying recently seen messages.

Communication is carried in the messages that may be up to 384 bytes long, when using Segmentation and Reassembly (SAR) mechanism, but most of the messages fit in one segment, that is 11 bytes. Each message starts with an opcode, which may be a single byte (for special messages), 2 bytes (for standard messages), or 3 bytes (for vendor-specific messages).

Every message has a source and a destination address, determining which devices process messages. Devices publish messages to destinations which can be single things / groups of things / everything.

Each message has a sequence number that protects the network against replay attacks.

Each message is encrypted and authenticated. Two keys are used to secure messages: (1) network keys – allocated to a single mesh network, (2) application keys – specific for a given application functionality, e.g. turning the light on vs reconfiguring the light.

Messages have a time to live (TTL). Each time message is received and retransmitted, TTL is decremented which limits the number of "hops", eliminating endless loops.

Architecture

Bluetooth Mesh has a layered architecture, with multiple layers as below.

LayerFunctionality
Model LayerIt defines a standard way to exchange application specific messages. For example, a Light Lightness Model defines an interoperable way to control lightness. There are mandatory models, called Foundation Models, defining states and messages needed to manage a mesh network.
Access LayerIt defines mechanism to ensure that data is transmitted and received in the right context of a model and its associated application keys.
Upper Transport LayerIt defines authenticated encryption of access layer packets using an application (or device specific key). It also defines some control messages to manage Friendship or to notify the behavior of node using Heartbeat messages.
Lower Transport LayerThis layer defines a reliable (through a Block Acknowledgement) Segmented transmission upper layer packets, when a complete upper layer packet can't be carried in a single network layer packet. It also defines a mechanism to reassemble segments on the receiver.
Network LayerThis layer defines how transport packets are addressed over network to one or more nodes. It defines relay functionality for forwarding messages by a relay node to extended the range. It handles the network layer authenticated encryption using network key.
Bearer LayerIt defines how the network packets are exchanged between nodes. Mesh Profile Specification defines BLE advert bearer and BLE GATT bearer. Mesh Profile defines Proxy Protocol, through which mesh packets can be exchanged via other bearers like TCP/IP.

Types of nodes

Nodes that support the various features can be formed into a particular mesh network topology.

FeatureFunctionality
Relayreceive and retransmit mesh messages over the advertising bearer

to enable larger networks.

Proxyreceive and retransmit mesh messages between GATT and

advertising bearers.

Low Poweroperate within a mesh network at significantly reduced receiver

duty cycles only in conjunction with a node supporting the Friend feature.

Friendhelp a node supporting the Low Power feature to operate by storing

messages destined for those nodes.

Theoretical limits

The practical limits of Bluetooth Mesh technology are unknown. Some limits that are built into the specification include:

Limit for a networkValueRemarks
Maximum number of nodes32 767The limit is 32768 addresses and while a node may occupy more than one address, the practical limit is most likely lower.
Maximum number of groups16 384

Number of virtual groups is 2128.

Maximum number of scenes65 535
Maximum number of subnets4 096
Maximum TTL127

Mesh models

As of version 1.0 of Bluetooth Mesh specification,5 the following standard models and model groups have been defined:

Foundation models

Foundation models have been defined in the core specification. Two of them are mandatory for all mesh nodes.

  • Configuration Server (mandatory)
  • Configuration Client
  • Health Server (mandatory)
  • Health Client

Generic models

  • Generic OnOff Server, used to represent devices that do not fit any of the model descriptions defined but support the generic properties of On/Off
  • Generic Level Server, keeping the state of an element in a 16-bit signed integer
  • Generic Default Transition Time Server, used to represent a default transition time for a variety of devices
  • Generic Power OnOff Server & Generic Power OnOff Setup Server, used to represent devices that do not fit any of the model descriptions but support the generic properties of On/Off
  • Generic Power Level Server & Generic Power Level Setup Server, including a Generic Power Actual state, a Generic Power Last state, a Generic Power Default state and a Generic Power Range state
  • Generic Battery Server, representing a set of four values representing the state of a battery
  • Generic Location Server & Generic Location Setup Server, representing location information of an element, either global (Lat/Lon) or local
  • Generic User/Admin/Manufacturer/Client Property Server, representing any value to be stored by an element
  • Generic OnOff Client & Generic Level Client
  • Generic Default Transition Time Client
  • Generic Power OnOff Client & Generic Power Level Client
  • Generic Battery Client
  • Generic Location Client
  • Generic Property Client

Sensors

  • Sensor Server & Sensor Setup Server, representing a sensor device. Sensor device may be configured to return a measured value periodically or on request; measurement period (cadence) may be configured to be fixed or to change, so that more important value range is being reported faster.
  • Sensor Client

Time and scenes

  • Time Server & Time Setup Server, allowing for time synchronization in mesh network
  • Scene Server & Scene Setup Server, allowing for up to 65535 scenes to be configured and recalled when needed.
  • Scheduler Server & Scheduler Setup Server
  • Time Client, Scene Client & Scheduler Client

Lighting

  • Light Lightness Server & Light Lightness Setup Server, representing a dimmable light source
  • Light CTL Server, Light CTL Temperature Server & Light CTL Setup Server, representing a CCT or "tunable white" light source
  • Light HSL Server, Light HSL Hue Server, Light HSL Saturation Server & Light HSL Setup Server, representing a light source based on Hue, Saturation, Lightness color representation
  • Light xyL Server & Light xyL Setup Server, representing a light source based on modified CIE xyY color space.
  • Light LC (Lightness Control) Server & Light LC Setup Server, representing a light control device, able to control Light Lightness model using an occupancy sensor and ambient light sensor. It may be used for light control scenarios like Auto-On, Auto-Off and/or Daylight Harvesting.
  • Light Lightness Client, Light CTL Client, Light HSL Client, Light xyL Client & Light LC Client

Provisioning

Provisioning is a process of installing the device into a network. It is a mandatory step to build a Bluetooth Mesh network.

In the provisioning process, a provisioner securely distributes a network key and a unique address space for a device. The provisioning protocol uses P256 Elliptic Curve Diffie-Hellman Key Exchange to create a temporary key to encrypt network key and other information. This provides security from a passive eavesdropper. It also provides various authentication mechanisms to protect network information, from an active eavesdropper who uses man-in-the-middle attack, during provisioning process.

A key unique to a device known as "Device Key" is derived from elliptic curve shared secret on provisioner and device during the provisioning process. This device key is used by the provisioner to encrypt messages for that specific device.

The security of the provisioning process has been analyzed in a paper presented during the IEEE CNS 2018 conference.6

The provisioning can be performed using a Bluetooth GATT connection or advertising using the specific bearer.7

Terminology used in the Bluetooth Mesh Model and Mesh Profile specifications

  • Destination: The address to which a message is sent.
  • Element: An addressable entity within a device.
  • Model: Standardized operation of typical user scenarios.
  • Node: A provisioned device.
  • Provisioner: A node that can add a device to a mesh network.
  • Relay: A node able to retransmit messages.
  • Source: The address from which a message is sent.

Implementations

Approved ("qualified") by Bluetooth SIG

Bluetooth mesh implementations approved ("qualified") by Bluetooth SIG
NameSubmitterQualification dateQDIDType
Bluetooth Stack for Embedded Systems - MESH profile8Silvair, Inc.July 18, 201798880Profile Subsystem
Qualcomm Bluetooth Mesh9Qualcomm Technologies International, Ltd.July 18, 201798856Profile Subsystem
Silvair Mesh Models10Silvair, Inc.July 26, 201799282Profile Subsystem
Wireless Gecko Mesh Profile11Silicon LaboratoriesSeptember 21, 2017101318Profile Subsystem
CYW-MESH 1.012Cypress Semiconductor CorporationOctober 3, 2017101726Component (Tested)
Qualcomm Bluetooth Mesh Model13Qualcomm Technologies International, Ltd.October 20, 2017102243Profile Subsystem
EtherMind Bluetooth Protocol Stack, 5.0 (Single Mode) + Mesh14Mindtree LimitedJanuary 24, 2018106544Component (Tested)
Telink SIG Mesh SDK15Telink SemiconductorFebruary 1, 2018106546Profile Subsystem
TOSHIBA Bluetooth_stack_mesh-116Toshiba CorporationFebruary 13, 2018104143Component (Tested)
AMICCOM Mesh Profile17AMICCOM Electronics CorporationMarch 14, 2018109370Profile Subsystem
Amiccom Bluetooth Mesh Model18AMICCOM Electronics CorporationMarch 30, 2018110168Profile Subsystem
Airoha SIG mesh19Airoha Technology Corp.April 2, 2018110202Profile Subsystem
Marvell Mesh stack v1.020Marvell Technology GroupApril 27, 2018110569Component (Tested)
nRF5 SDK for Mesh 21Nordic SemiconductorMay 2, 2018111537Profile Subsystem
Realtek Bluetooth 5 Mesh Solution22Realsil Microelectronics IncJuly 27, 2018115668Profile Subsystem
STSW-BNRG-Mesh23STMicroelectronicsAugust 2, 2018116029Profile Subsystem
RDA BT Host 5.024RDA Microelectronics, Inc.September 13, 2018115860Profile Subsystem
JYMC-MESH-125Shanghai Frequen Microelectronics Co., Ltd.October 10, 2018119229End Product
RW-BLE-MESH26CEVA, Inc.October 31, 2018119268Component (Tested)
ARM Ltd Cordio Mesh27ARM LtdDecember 11, 2018116593Profile Subsystem
Samsung SLSI Bluetooth Mesh28Samsung Electronics Co., Ltd.December 21, 2018122442Profile Subsystem
Bluelet Host Stack V1229Barrot Technology LimitedDecember 25, 2018123056Component (Tested)
ESP BLE Mesh v0.630Espressif Systems (Shanghai) Pte. Ltd.January 14, 2019124137Profile Subsystem
BK3435 BLE Core Spec 5.0 with MESH31Beken CorpMarch 12, 2019127926End Product
Actions Mesh Profile Subsystem32Actions (Zhuhai) Technology Co., LimitedMarch 21, 2019127646Profile Subsystem
AliOS Things BLE host and mesh profile v2.1.033Alibaba (China) Co., Ltd.April 19, 2019129750Host Subsystem
Tonly SIG Mesh Stack34Shenzhen Tonli Science and Technology Development Co., LtdMay 5, 2019130160Profile Subsystem
Sino Wealth IBLE SIG Mesh Profile35Sino Wealth Electronic Ltd.June 18, 2019133403Profile Subsystem
Qualcomm Bluetooth Mesh and Mesh Model v4.036Qualcomm Technologies International, Ltd.June 19, 2019128410Profile Subsystem
PAN1020 Mesh Profile subsystem37Shanghai Panchip Microelectronics Co., LtdJuly 1, 2019129291Profile Subsystem
Apache NimBLE BLE Host including BLE Mesh38JUUL Labs, Inc.July 15, 2019131934Component (Tested)
Tmall mesh Stack39Alibaba (China) Co., Ltd.July 20, 2019128246Profile Subsystem
ClarinoxBlue40Clarinox Technologies Pty LtdAugust 2, 2019134454Host Subsystem
BlueX Mesh41BlueX Microelectronics Corp Ltd.August 20, 2019137436Profile Subsystem
Zephyr OS Mesh42The Linux FoundationSeptember 20, 2019139259Profile Subsystem
WCH Bluetooth Mesh43Nanjing Qinheng Microelectronics Co., Ltd.June 1, 2020144808Profile Subsystem

Free and open-source software implementations

Free software and open source software implementations include the following:

  • The official (included in Linux kernel by Linus Torvalds in 200144) Linux Bluetooth protocol stack BlueZ, dual free-licensed under the GPL45 and the LGPL,46 supports Mesh Profile, from release version 5.47,47 by providing meshctl tool (deprecated) to configure mesh devices. Release version 5.53 introduced mesh-cfgclient tool for configuring mesh networks. BlueZ was approved as a "qualified" software package by Bluetooth SIG in 2005.48 BlueZ is not considered to be a qualified Bluetooth Mesh stack as Bluetooth Mesh is not listed in aforementioned qualification record as a supported profile.
  • Apache Mynewt NimBLE, free-licensed under the Apache License 2.0,49 supports Bluetooth Mesh from release version 1.2.0.50 It was qualified on July 15, 2019 (2019-07-15) with QDID 131934.51
  • Zephyr OS Mesh, free-licensed under the Apache License 2.0,52 supports Bluetooth Mesh from release version 1.9.0.53 Zephyr OS Mesh 1.14.x was qualified on September 20, 2019 (2019-09-20) with QDID 139259.54

See also

References

  1. "Mesh Profile Bluetooth® Specification" (PDF download). Bluetooth Technology Website. 2017-07-13. Retrieved 2017-07-18. https://www.bluetooth.org/docman/handlers/downloaddoc.ashx?doc_id=429633 ↩

  2. "Mesh Model Bluetooth® Specification" (PDF download). Bluetooth Technology Website. 2017-07-13. Retrieved 2017-07-18. https://www.bluetooth.org/docman/handlers/downloaddoc.ashx?doc_id=429634 ↩

  3. "Range Limitation? What Range Limitation? Introducing Mesh Networks | Bluetooth Technology Website". blog.bluetooth.com. Archived from the original on 2016-04-09. Retrieved 2017-07-06. https://web.archive.org/web/20160409092727/http://blog.bluetooth.com/range-limitation-what-range-limitation-introducing-mesh-networks/ ↩

  4. "Low Energy: Mesh | Bluetooth Technology Website". www.bluetooth.com. Archived from the original on 2017-09-01. Retrieved 2017-07-18. https://web.archive.org/web/20170901202951/https://www.bluetooth.com/what-is-bluetooth-technology/how-it-works/le-mesh ↩

  5. "Mesh Model Bluetooth® Specification" (PDF download). Bluetooth Technology Website. 2017-07-13. Retrieved 2017-07-18. https://www.bluetooth.org/docman/handlers/downloaddoc.ashx?doc_id=429634 ↩

  6. Adomnicai, A.; Fournier, J. J. A.; Masson, L. (2018-05-30). "Hardware Security Threats Against Bluetooth Mesh Networks". 2018 IEEE Conference on Communications and Network Security (CNS). pp. 1–9. doi:10.1109/CNS.2018.8433184. ISBN 978-1-5386-4586-4. S2CID 52004479. 978-1-5386-4586-4 ↩

  7. "Mesh Profile Bluetooth® Specification" (PDF download). Bluetooth Technology Website. 2017-07-13. Retrieved 2017-07-18. https://www.bluetooth.org/docman/handlers/downloaddoc.ashx?doc_id=429633 ↩

  8. "QD ID 98880 | Launch Studio - Listing Details". launchstudio.bluetooth.com. Retrieved 2017-11-15. https://launchstudio.bluetooth.com/ListingDetails/20708 ↩

  9. "QD ID 98856 | Launch Studio - Listing Details". launchstudio.bluetooth.com. Retrieved 2017-11-15. https://launchstudio.bluetooth.com/ListingDetails/1903 ↩

  10. "QD ID 99282 | Launch Studio - Listing Details". launchstudio.bluetooth.com. Retrieved 2017-11-15. https://launchstudio.bluetooth.com/ListingDetails/18763 ↩

  11. "QD ID 101318 | Launch Studio - Listing Details". launchstudio.bluetooth.com. Retrieved 2017-11-15. https://launchstudio.bluetooth.com/ListingDetails/25011 ↩

  12. "QD ID 101726 | Launch Studio - Listing Details". launchstudio.bluetooth.com. Retrieved 2017-11-15. https://launchstudio.bluetooth.com/ListingDetails/480 ↩

  13. "QD ID 102243 | Launch Studio - Listing Details". launchstudio.bluetooth.com. Retrieved 2017-11-15. https://launchstudio.bluetooth.com/ListingDetails/1905 ↩

  14. "QD ID 106544 | Launch Studio - Listing Details". launchstudio.bluetooth.com. Retrieved 2018-03-05. https://launchstudio.bluetooth.com/ListingDetails/52845 ↩

  15. "QD ID 106546 | Launch Studio - Listing Details". launchstudio.bluetooth.com. Retrieved 2018-03-05. https://launchstudio.bluetooth.com/ListingDetails/52851 ↩

  16. "QD ID 104143 | Launch Studio - Listing Details". launchstudio.bluetooth.com. Retrieved 2018-03-05. https://launchstudio.bluetooth.com/ListingDetails/49426 ↩

  17. "QD ID 109370 | Launch Studio - Listing Details". launchstudio.bluetooth.com. Retrieved 2018-04-05. https://launchstudio.bluetooth.com/ListingDetails/RedirectFromQdid/109370 ↩

  18. "QD ID 110168 | Launch Studio - Listing Details". launchstudio.bluetooth.com. Retrieved 2018-04-05. https://launchstudio.bluetooth.com/ListingDetails/RedirectFromQdid/110168 ↩

  19. "QD ID 110202 | Launch Studio - Listing Details". launchstudio.bluetooth.com. Retrieved 2018-04-05. https://launchstudio.bluetooth.com/ListingDetails/RedirectFromQdid/110202 ↩

  20. "QD ID 110569 | Launch Studio - Listing Details". launchstudio.bluetooth.com. Retrieved 2018-05-03. https://launchstudio.bluetooth.com/ListingDetails/RedirectFromQdid/110569 ↩

  21. Systems, eZ. "nRF5 SDK for Mesh / Bluetooth Low Energy / Products / Home - Ultra Low Power Wireless Solutions from NORDIC SEMICONDUCTOR". www.nordicsemi.com. Retrieved 2018-05-03. https://www.nordicsemi.com/eng/Products/Bluetooth-low-energy/nRF5-SDK-for-Mesh ↩

  22. "QD ID 115668 | Launch Studio - Listing Details". launchstudio.bluetooth.com. Retrieved 2018-09-15. https://launchstudio.bluetooth.com/ListingDetails/RedirectFromQdid/115668 ↩

  23. "QD ID 116029 | Launch Studio - Listing Details". launchstudio.bluetooth.com. Retrieved 2018-09-15. https://launchstudio.bluetooth.com/ListingDetails/RedirectFromQdid/116029 ↩

  24. "QD ID 115860 | Launch Studio - Listing Details". launchstudio.bluetooth.com. Retrieved 2018-09-15. https://launchstudio.bluetooth.com/ListingDetails/RedirectFromQdid/115860 ↩

  25. "QD ID 119229 | Launch Studio - Listing Details". launchstudio.bluetooth.com. Retrieved 2018-11-07. https://launchstudio.bluetooth.com/ListingDetails/RedirectFromQdid/119229 ↩

  26. "QD ID 119268 | Launch Studio - Listing Details". launchstudio.bluetooth.com. Retrieved 2018-11-07. https://launchstudio.bluetooth.com/ListingDetails/RedirectFromQdid/119268 ↩

  27. "QD ID 116593 | Launch Studio - Listing Details". launchstudio.bluetooth.com. Retrieved 2018-12-21. https://launchstudio.bluetooth.com/ListingDetails/RedirectFromQdid/116593 ↩

  28. "QD ID 122442 | Launch Studio - Listing Details". launchstudio.bluetooth.com. Retrieved 2018-12-21. https://launchstudio.bluetooth.com/ListingDetails/RedirectFromQdid/122442 ↩

  29. "QD ID 123056 | Launch Studio - Listing Details". launchstudio.bluetooth.com. Retrieved 2018-12-21. https://launchstudio.bluetooth.com/ListingDetails/RedirectFromQdid/123056 ↩

  30. "QD ID 124137 | Launch Studio - Listing Details". launchstudio.bluetooth.com. Retrieved 2019-01-24. https://launchstudio.bluetooth.com/ListingDetails/RedirectFromQdid/124137 ↩

  31. "QD ID 127926 | Launch Studio - Listing Details". launchstudio.bluetooth.com. Retrieved 2019-04-14. https://launchstudio.bluetooth.com/ListingDetails/RedirectFromQdid/127926 ↩

  32. "QD ID 127646 | Launch Studio - Listing Details". launchstudio.bluetooth.com. Retrieved 2019-04-14. https://launchstudio.bluetooth.com/ListingDetails/RedirectFromQdid/127646 ↩

  33. "QD ID 129750 | Launch Studio - Listing Details". launchstudio.bluetooth.com. Retrieved 2019-05-06. https://launchstudio.bluetooth.com/ListingDetails/RedirectFromQdid/129750 ↩

  34. "QD ID 130160 | Launch Studio - Listing Details". launchstudio.bluetooth.com. Retrieved 2019-05-06. https://launchstudio.bluetooth.com/ListingDetails/RedirectFromQdid/130160 ↩

  35. "QD ID 133403 | Launch Studio - Listing Details". launchstudio.bluetooth.com. Retrieved 2019-06-19. https://launchstudio.bluetooth.com/ListingDetails/RedirectFromQdid/133403 ↩

  36. "QD ID 128410 | Launch Studio - Listing Details". launchstudio.bluetooth.com. Retrieved 2019-06-19. https://launchstudio.bluetooth.com/ListingDetails/RedirectFromQdid/128410 ↩

  37. "QD ID 129291 | Launch Studio - Listing Details". launchstudio.bluetooth.com. Retrieved 2019-08-27. https://launchstudio.bluetooth.com/ListingDetails/RedirectFromQdid/129291 ↩

  38. "QD ID 131934 | Launch Studio - Listing Details". launchstudio.bluetooth.com. Retrieved 2019-08-27. https://launchstudio.bluetooth.com/ListingDetails/RedirectFromQdid/131934 ↩

  39. "QD ID 128246 | Launch Studio - Listing Details". launchstudio.bluetooth.com. Retrieved 2019-08-27. https://launchstudio.bluetooth.com/ListingDetails/RedirectFromQdid/128246 ↩

  40. "QD ID 134454 | Launch Studio - Listing Details". launchstudio.bluetooth.com. Retrieved 2019-08-27. https://launchstudio.bluetooth.com/ListingDetails/RedirectFromQdid/134454 ↩

  41. "QD ID 137436 | Launch Studio - Listing Details". launchstudio.bluetooth.com. Retrieved 2019-08-27. https://launchstudio.bluetooth.com/ListingDetails/RedirectFromQdid/137436 ↩

  42. "QD ID 139259| Launch Studio - Listing Details". launchstudio.bluetooth.com. Retrieved 2020-03-12. https://launchstudio.bluetooth.com/ListingDetails/RedirectFromQdid/139259 ↩

  43. "QD ID 144808| Launch Studio - Listing Details". launchstudio.bluetooth.com. Retrieved 2020-06-01. https://launchstudio.bluetooth.com/ListingDetails/RedirectFromQdid/144808 ↩

  44. "BlueZ History". BlueZ. 2019-09-07. http://www.bluez.org/about/history/ ↩

  45. "index : bluez.git – Bluetooth protocol stack for Linux – Marcel Holtmann". kernel.org. 1991. Archived from the original on 2019-09-05. Retrieved 2019-09-05. https://git.kernel.org/pub/scm/bluetooth/bluez.git/tree/COPYING ↩

  46. "index : bluez.git – Bluetooth protocol stack for Linux – Marcel Holtmann". kernel.org. 1999. Archived from the original on 2019-09-05. Retrieved 2019-09-05. https://git.kernel.org/pub/scm/bluetooth/bluez.git/tree/COPYING.LIB ↩

  47. "BlueZ » Blog Archive » Release of BlueZ 5.47". www.bluez.org. Retrieved 2017-10-27. http://www.bluez.org/release-of-bluez-5-47/ ↩

  48. "Qualified Product Detail". Bluetooth SIG. Archived from the original on 2019-09-05. Retrieved 2019-09-05. https://www.bluetooth.org/qualweb/ProductDetails.cfm?ProductID=2379 ↩

  49. "apache/mynewt-core/LICENSE". GitHub. 2018-06-04. Archived from the original on 2019-09-05. Retrieved 2019-09-05. https://github.com/apache/mynewt-core/blob/master/LICENSE ↩

  50. "RN-1.2.0 - Apache Mynewt - Apache Software Foundation". cwiki.apache.org. Retrieved 2018-07-02. https://cwiki.apache.org/confluence/display/MYNEWT/RN-1.2.0 ↩

  51. "QD ID 131934 | Launch Studio - Listing Details". launchstudio.bluetooth.com. Retrieved 2019-08-27. https://launchstudio.bluetooth.com/ListingDetails/RedirectFromQdid/131934 ↩

  52. "zephyrproject-rtos/zephyr/blob/master/LICENSE". GitHub. 2020-03-21. Archived from the original on 2019-09-05. Retrieved 2020-03-21. https://github.com/apache/mynewt-core/blob/master/LICENSE ↩

  53. "Release Notes Zephyr Kernel 1.9.0". docs.zephyrproject.org. Retrieved 2020-03-21. https://docs.zephyrproject.org/latest/releases/release-notes-1.9.html#zephyr-kernel-1-9-0 ↩

  54. "QD ID 131934 | Launch Studio - Listing Details". launchstudio.bluetooth.com. Retrieved 2019-08-27. https://launchstudio.bluetooth.com/ListingDetails/RedirectFromQdid/131934 ↩