Bluetooth mesh networking: Difference between revisions

Content deleted Content added
Notifying of move discussion on Talk:Bluetooth mesh networking
Citation bot (talk | contribs)
Removed URL that duplicated identifier. | Use this bot. Report bugs. | Suggested by Headbomb | Linked from Wikipedia:WikiProject_Academic_Journals/Journals_cited_by_Wikipedia/Sandbox | #UCB_webform_linked 301/1032
 
(48 intermediate revisions by 35 users not shown)
Line 1:
{{Short description|Computer mesh networking standard}}
<noinclude>{{User:RMCD bot/subject notice|1=Bluetooth Mesh|2=Talk:Bluetooth mesh networking#Requested move 7 September 2019 }}
</noinclude>{{Infobox protocol
| name = Bluetooth mesh networking
| image = Bluetooth- logo (2016).svg
| standard =
| developer = [[Bluetooth Special Interest Group|Bluetooth SIG]]
| introdate = {{Start date|2017|07|13}}
| industry = [[Lighting]], [[Internet of things|IoT]]
| connector =
| hardware =
| range = 100-1000100–1000 meters (depending on mesh relaying configuration)
}}
 
'''Bluetooth Mesh''' is a computer [[mesh networking]] [[Technical standard|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<ref name=":0">{{Cite web|url=https://www.bluetooth.org/docman/handlers/downloaddoc.ashx?doc_id=429633|title=Mesh Profile Bluetooth® Specification|last=|first=|date=2017-07-13|website=Bluetooth Technology Website|format=PDF download|archive-url=|archive-date=|dead-url=|access-date=2017-07-18}}</ref> and Mesh Model<ref name=":1">{{Cite web|url=https://www.bluetooth.org/docman/handlers/downloaddoc.ashx?doc_id=429634|title=Mesh Model Bluetooth® Specification|last=|first=|date=2017-07-13|website=Bluetooth Technology Website|format=PDF download|archive-url=|archive-date=|dead-url=|access-date=2017-07-18}}</ref> specifications by the [[Bluetooth Special Interest Group]] (Bluetooth SIG). Bluetooth Mesh was conceived in 20152014<ref>{{Cite web|url=httpshttp://blog.bluetooth.com/trashedrange-limitation-what-range-limitation-introducing-mesh-networks/|title=GetRange readyLimitation? forWhat BluetoothRange mesh!Limitation? Introducing Mesh Networks {{!}} Bluetooth Technology Website|website=blog.bluetooth.com|url-status=dead|archive-url=https://web.archive.org/web/20160409092727/http://blog.bluetooth.com/range-limitation-what-range-limitation-introducing-mesh-networks/|archive-date=2016-04-09|access-date=2017-07-06}}</ref>{{dead link|date=September 2019}} and adopted on {{Start date|2017|07|13}}.<ref>{{Cite web|url=https://www.bluetooth.com/what-is-bluetooth-technology/how-it-works/le-mesh|title=Low Energy: Mesh {{!}} Bluetooth Technology Website|last=|first=|date=|website=www.bluetooth.com|url-status=dead|archive-url=https://web.archive.org/web/20170901202951/https://www.bluetooth.com/what-is-bluetooth-technology/how-it-works/le-mesh|archive-date=|dead2017-url=09-01|access-date=2017-07-18}}</ref>
 
== Overview ==
Bluetooth Mesh is a [[mesh networking]] standard that operates on a [[Flooding (computer networking)|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 that
* is not in message cache, that
* has a TTL ≥ 2

can be retransmitted with TTL = TTL - 1. Message caching is used to prevent relaying messages 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).
Line 21 ⟶ 27:
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.
Line 27 ⟶ 33:
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.
 
{| class="wikitable"
!Layer
Line 49 ⟶ 57:
|Bearer&nbsp;Layer
|It 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.
 
{| class="wikitable"
!Feature
!Functionality
|-
|Relay
|receive and retransmit mesh messages over the advertising bearer
to enable larger networks.
|-
|Proxy
|receive and retransmit mesh messages between GATT and
advertising bearers.
|-
|Low Power
|operate within a mesh network at significantly reduced receiver
duty cycles only in conjunction with a node supporting the Friend feature.
|-
|Friend
|help a node supporting the Low Power feature to operate by storing
messages destined for those nodes.
|}
 
Line 105 ⟶ 137:
* 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.
Line 126 ⟶ 159:
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. ProvisioningThe provisioning protocol uses P256 Elliptic Curve [[Diffie–Hellman key exchange|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.
 
SecurityThe security of the provisioning process has been analyzed in a paper presented during the [[IEEE Communications Society|IEEE CNS]] 2018 conference.<ref>{{Cite journalbook|lastlast1=Adomnicai|firstfirst1=A.|last2=Fournier|first2=J. J. A.|last3=Masson|first3=L.|date=2018-05-30|title=Hardware Security Threats Against Bluetooth Mesh Networks|url=https://ieeexplore.ieee.org/document/8433184/|journal=2018 IEEE Conference on Communications and Network Security (CNS) |volumechapter=Hardware Security Threats Against Bluetooth Mesh Networks |date=2018-05-30|pages=1–9|doi=10.1109/CNS.2018.8433184|via=|isbn=978-1-5386-4586-4|s2cid=52004479 }}</ref>
 
The provisioning can be performed using a Bluetooth GATT connection or advertising using the specific bearer.<ref name=":0" />
Line 154 ⟶ 187:
!Type
|-
|Bluetooth Stack for Embedded Systems - MESH profile<ref>{{Cite web|url=https://launchstudio.bluetooth.com/ListingDetails/20708|title=QD ID 98880 {{!}} Launch Studio - Listing Details|last=|first=|date=|website=launchstudio.bluetooth.com|archive-url=|archive-date=|dead-url=|access-date=2017-11-15}}</ref>
|Silvair, Inc.
|{{Dts|2017-07-18}}
Line 160 ⟶ 193:
|Profile Subsystem
|-
|Qualcomm Bluetooth Mesh<ref>{{Cite web|url=https://launchstudio.bluetooth.com/ListingDetails/1903|title=QD ID 98856 {{!}} Launch Studio - Listing Details|last=|first=|date=|website=launchstudio.bluetooth.com|archive-url=|archive-date=|dead-url=|access-date=2017-11-15}}</ref>
|[[Qualcomm|Qualcomm Technologies International, Ltd.]]
|{{Dts|2017-07-18}}
Line 166 ⟶ 199:
|Profile Subsystem
|-
|Silvair Mesh Models<ref>{{Cite web|url=https://launchstudio.bluetooth.com/ListingDetails/18763|title=QD ID 99282 {{!}} Launch Studio - Listing Details|last=|first=|date=|website=launchstudio.bluetooth.com|archive-url=|archive-date=|dead-url=|access-date=2017-11-15}}</ref>
|Silvair, Inc.
|{{Dts|2017-07-26}}
Line 172 ⟶ 205:
|Profile Subsystem
|-
|Wireless Gecko Mesh Profile<ref>{{Cite web|url=https://launchstudio.bluetooth.com/ListingDetails/25011|title=QD ID 101318 {{!}} Launch Studio - Listing Details|last=|first=|date=|website=launchstudio.bluetooth.com|archive-url=|archive-date=|dead-url=|access-date=2017-11-15}}</ref>
|[[Silicon Laboratories]]
|{{Dts|2017-09-21}}
Line 178 ⟶ 211:
|Profile Subsystem
|-
|CYW-MESH 1.0<ref>{{Cite web|url=https://launchstudio.bluetooth.com/ListingDetails/480|title=QD ID 101726 {{!}} Launch Studio - Listing Details|last=|first=|date=|website=launchstudio.bluetooth.com|archive-url=|archive-date=|dead-url=|access-date=2017-11-15}}</ref>
|[[Cypress Semiconductor Corporation]]
|{{Dts|2017-10-03}}
Line 184 ⟶ 217:
|Component (Tested)
|-
|Qualcomm Bluetooth Mesh Model<ref>{{Cite web|url=https://launchstudio.bluetooth.com/ListingDetails/1905|title=QD ID 102243 {{!}} Launch Studio - Listing Details|last=|first=|date=|website=launchstudio.bluetooth.com|archive-url=|archive-date=|dead-url=|access-date=2017-11-15}}</ref>
|Qualcomm Technologies International, Ltd.
|{{Dts|2017-10-20}}
Line 190 ⟶ 223:
|Profile Subsystem
|-
|EtherMind Bluetooth Protocol Stack, 5.0 (Single Mode) + Mesh<ref>{{Cite web|url=https://launchstudio.bluetooth.com/ListingDetails/52845|title=QD ID 106544 {{!}} Launch Studio - Listing Details|last=|first=|date=|website=launchstudio.bluetooth.com|archive-url=|archive-date=|dead-url=|access-date=2018-03-05}}</ref>
|[[Mindtree|Mindtree Limited]]
|{{Dts|2018-01-24}}
Line 196 ⟶ 229:
|Component (Tested)
|-
|Telink SIG Mesh SDK<ref>{{Cite web|url=https://launchstudio.bluetooth.com/ListingDetails/52851|title=QD ID 106546 {{!}} Launch Studio - Listing Details|last=|first=|date=|website=launchstudio.bluetooth.com|archive-url=|archive-date=|dead-url=|access-date=2018-03-05}}</ref>
|[[Telink Semiconductor]]
|{{Dts|2018-02-01}}
Line 202 ⟶ 235:
|Profile Subsystem
|-
|TOSHIBA Bluetooth_stack_mesh-1<ref>{{Cite web|url=https://launchstudio.bluetooth.com/ListingDetails/49426|title=QD ID 104143 {{!}} Launch Studio - Listing Details|last=|first=|date=|website=launchstudio.bluetooth.com|archive-url=|archive-date=|dead-url=|access-date=2018-03-05}}</ref>
|[[Toshiba|Toshiba Corporation]]
|{{Dts|2018-02-13}}
Line 208 ⟶ 241:
|Component (Tested)
|-
|AMICCOM Mesh Profile<ref>{{Cite web|url=https://launchstudio.bluetooth.com/ListingDetails/RedirectFromQdid/109370|title=QD ID 109370 {{!}} Launch Studio - Listing Details|last=|first=|date=|website=launchstudio.bluetooth.com|archive-url=|archive-date=|dead-url=|access-date=2018-04-05}}</ref>
|[[AMICCOM|AMICCOM Electronics Corporation]]
|{{Dts|2018-03-14}}
Line 214 ⟶ 247:
|Profile Subsystem
|-
|Amiccom Bluetooth Mesh Model<ref>{{Cite web|url=https://launchstudio.bluetooth.com/ListingDetails/RedirectFromQdid/110168|title=QD ID 110168 {{!}} Launch Studio - Listing Details|last=|first=|date=|website=launchstudio.bluetooth.com|archive-url=|archive-date=|dead-url=|access-date=2018-04-05}}</ref>
|AMICCOM Electronics Corporation
|{{Dts|2018-03-30}}
Line 220 ⟶ 253:
|Profile Subsystem
|-
|Airoha SIG mesh<ref>{{Cite web|url=https://launchstudio.bluetooth.com/ListingDetails/RedirectFromQdid/110202|title=QD ID 110202 {{!}} Launch Studio - Listing Details|last=|first=|date=|website=launchstudio.bluetooth.com|archive-url=|archive-date=|dead-url=|access-date=2018-04-05}}</ref>
|[[Airoha|Airoha Technology Corp.]]
|{{Dts|2018-04-02}}
Line 226 ⟶ 259:
|Profile Subsystem
|-
|Marvell Mesh stack v1.0<ref>{{Cite web|url=https://launchstudio.bluetooth.com/ListingDetails/RedirectFromQdid/110569|title=QD ID 110569 {{!}} Launch Studio - Listing Details|last=|first=|date=|website=launchstudio.bluetooth.com|archive-url=|archive-date=|dead-url=|access-date=2018-05-03}}</ref>
|[[Marvell Technology Group]]
|{{Dts|2018-04-27}}
Line 238 ⟶ 271:
|Profile Subsystem
|-
|Realtek Bluetooth 5 Mesh Solution<ref>{{Cite web|url=https://launchstudio.bluetooth.com/ListingDetails/RedirectFromQdid/115668|title=QD ID 115668 {{!}} Launch Studio - Listing Details|last=|first=|date=|website=launchstudio.bluetooth.com|archive-url=|archive-date=|dead-url=|access-date=2018-09-15}}</ref>
|[[Realtek|Realsil Microelectronics Inc]]
|{{Dts|2018-07-27}}
Line 244 ⟶ 277:
|Profile Subsystem
|-
|STSW-BNRG-Mesh<ref>{{Cite web|url=https://launchstudio.bluetooth.com/ListingDetails/RedirectFromQdid/116029|title=QD ID 116029 {{!}} Launch Studio - Listing Details|last=|first=|date=|website=launchstudio.bluetooth.com|archive-url=|archive-date=|dead-url=|access-date=2018-09-15}}</ref>
|[[STMicroelectronics]]
|{{Dts|2018-08-02}}
Line 250 ⟶ 283:
|Profile Subsystem
|-
|RDA BT Host 5.0<ref>{{Cite web|url=https://launchstudio.bluetooth.com/ListingDetails/RedirectFromQdid/115860|title=QD ID 115860 {{!}} Launch Studio - Listing Details|last=|first=|date=|website=launchstudio.bluetooth.com|archive-url=|archive-date=|dead-url=|access-date=2018-09-15}}</ref>
|[[UNISOC|RDA Microelectronics, Inc.]]
|{{Dts|2018-09-13}}
Line 256 ⟶ 289:
|Profile Subsystem
|-
|JYMC-MESH-1<ref>{{Cite web|url=https://launchstudio.bluetooth.com/ListingDetails/RedirectFromQdid/119229|title=QD ID 119229 {{!}} Launch Studio - Listing Details|last=|first=|date=|website=launchstudio.bluetooth.com|archive-url=|archive-date=|dead-url=|access-date=2018-11-07}}</ref>
|[[Shanghai Frequen Microelectronics Co., Ltd.]]
|{{Dts|2018-10-10}}
Line 262 ⟶ 295:
|End Product
|-
|RW-BLE-MESH<ref>{{Cite web|url=https://launchstudio.bluetooth.com/ListingDetails/RedirectFromQdid/119268|title=QD ID 119268 {{!}} Launch Studio - Listing Details|last=|first=|date=|website=launchstudio.bluetooth.com|archive-url=|archive-date=|dead-url=|access-date=2018-11-07}}</ref>
|[[CEVA, Inc.#Connectivity Solutions|CEVA, Inc.]]
|{{Dts|2018-10-31}}
Line 268 ⟶ 301:
|Component (Tested)
|-
|ARM Ltd Cordio Mesh<ref>{{Cite web|url=https://launchstudio.bluetooth.com/ListingDetails/RedirectFromQdid/116593|title=QD ID 116593 {{!}} Launch Studio - Listing Details|last=|first=|date=|website=launchstudio.bluetooth.com|archive-url=|archive-date=|dead-url=|access-date=2018-12-21}}</ref>
|[[Arm Holdings|ARM Ltd]]
|{{Dts|2018-12-11}}
Line 274 ⟶ 307:
|Profile Subsystem
|-
|Samsung SLSI Bluetooth Mesh<ref>{{Cite web|url=https://launchstudio.bluetooth.com/ListingDetails/RedirectFromQdid/122442|title=QD ID 122442 {{!}} Launch Studio - Listing Details|last=|first=|date=|website=launchstudio.bluetooth.com|archive-url=|archive-date=|dead-url=|access-date=2018-12-21}}</ref>
|[[Samsung Electronics|Samsung Electronics Co., Ltd.]]
|{{Dts|2018-12-21}}
Line 280 ⟶ 313:
|Profile Subsystem
|-
|Bluelet Host Stack V12<ref>{{Cite web|url=https://launchstudio.bluetooth.com/ListingDetails/RedirectFromQdid/123056|title=QD ID 123056 {{!}} Launch Studio - Listing Details|last=|first=|date=|website=launchstudio.bluetooth.com|archive-url=|archive-date=|dead-url=|access-date=2018-12-21}}</ref>
|[[Barrot Technology Limited]]
|{{Dts|2018-12-25}}
Line 286 ⟶ 319:
|Component (Tested)
|-
|ESP BLE Mesh v0.6<ref>{{Cite web|url=https://launchstudio.bluetooth.com/ListingDetails/RedirectFromQdid/124137|title=QD ID 124137 {{!}} Launch Studio - Listing Details|last=|first=|date=|website=launchstudio.bluetooth.com|archive-url=|archive-date=|dead-url=|access-date=2019-01-24}}</ref>
|[[Espressif Systems|Espressif Systems (Shanghai) Pte. Ltd.]]
|{{Dts|2019-01-14}}
Line 292 ⟶ 325:
|Profile Subsystem
|-
|BK3435 BLE Core Spec 5.0 with MESH<ref>{{Cite web|url=https://launchstudio.bluetooth.com/ListingDetails/RedirectFromQdid/127926|title=QD ID 127926 {{!}} Launch Studio - Listing Details|last=|first=|date=|website=launchstudio.bluetooth.com|archive-url=|archive-date=|dead-url=|access-date=2019-04-14}}</ref>
|[[Beken Corp]]
|{{Dts|2019-03-12}}
Line 298 ⟶ 331:
|End Product
|-
|Actions Mesh Profile Subsystem<ref>{{Cite web|url=https://launchstudio.bluetooth.com/ListingDetails/RedirectFromQdid/127646|title=QD ID 127646 {{!}} Launch Studio - Listing Details|last=|first=|date=|website=launchstudio.bluetooth.com|archive-url=|archive-date=|dead-url=|access-date=2019-04-14}}</ref>
|[[Actions Semiconductor|Actions (Zhuhai) Technology Co., Limited]]
|{{Dts|2019-03-21}}
Line 304 ⟶ 337:
|Profile Subsystem
|-
|AliOS Things BLE host and mesh profile v2.1.0<ref>{{Cite web|url=https://launchstudio.bluetooth.com/ListingDetails/RedirectFromQdid/129750|title=QD ID 129750 {{!}} Launch Studio - Listing Details|last=|first=|date=|website=launchstudio.bluetooth.com|archive-url=|archive-date=|dead-url=|access-date=2019-05-06}}</ref>
|[[Alibaba Group|Alibaba (China) Co., Ltd.]]
|{{Dts|2019-04-19}}
Line 310 ⟶ 343:
|Host Subsystem
|-
|Tonly SIG Mesh Stack<ref>{{Cite web|url=https://launchstudio.bluetooth.com/ListingDetails/RedirectFromQdid/130160|title=QD ID 130160 {{!}} Launch Studio - Listing Details|last=|first=|date=|website=launchstudio.bluetooth.com|archive-url=|archive-date=|dead-url=|access-date=2019-05-06}}</ref>
|[[Tonli|Shenzhen Tonli Science and Technology Development Co., Ltd]]
|{{Dts|2019-05-05}}
|130160
|Profile Subsystem
|-
|Sino Wealth IBLE SIG Mesh Profile<ref>{{Cite web|url=https://launchstudio.bluetooth.com/ListingDetails/RedirectFromQdid/133403|title=QD ID 133403 {{!}} Launch Studio - Listing Details|last=|first=|date=|website=launchstudio.bluetooth.com|archive-url=|archive-date=|dead-url=|access-date=2019-06-19}}</ref>
|[[Sino Wealth|Sino Wealth Electronic Ltd.]]
|{{Dts|2019-06-18}}
Line 322 ⟶ 355:
|Profile Subsystem
|-
|Qualcomm Bluetooth Mesh and Mesh Model v4.0<ref>{{Cite web|url=https://launchstudio.bluetooth.com/ListingDetails/RedirectFromQdid/128410|title=QD ID 128410 {{!}} Launch Studio - Listing Details|last=|first=|date=|website=launchstudio.bluetooth.com|archive-url=|archive-date=|dead-url=|access-date=2019-06-19}}</ref>
|Qualcomm Technologies International, Ltd.
|{{Dts|2019-06-19}}
Line 328 ⟶ 361:
|Profile Subsystem
|-
|PAN1020 Mesh Profile subsystem<ref>{{Cite web|url=https://launchstudio.bluetooth.com/ListingDetails/RedirectFromQdid/129291|title=QD ID 129291 {{!}} Launch Studio - Listing Details|last=|first=|date=|website=launchstudio.bluetooth.com|archive-url=|archive-date=|dead-url=|access-date=2019-08-27}}</ref>
|Shanghai Panchip Microelectronics Co., Ltd
|{{Dts|2019-07-01}}
Line 334 ⟶ 367:
|Profile Subsystem
|-
|Apache NimBLE BLE Host including BLE Mesh<ref name=":2">{{Cite web|url=https://launchstudio.bluetooth.com/ListingDetails/RedirectFromQdid/131934|title=QD ID 131934 {{!}} Launch Studio - Listing Details|last=|first=|date=|website=launchstudio.bluetooth.com|archive-url=|archive-date=|dead-url=|access-date=2019-08-27}}</ref>
|[[JUUL Labs|JUUL Labs, Inc.]]
|{{Dts|2019-07-15}}
Line 340 ⟶ 373:
|Component (Tested)
|-
|Tmall mesh Stack<ref>{{Cite web|url=https://launchstudio.bluetooth.com/ListingDetails/RedirectFromQdid/128246|title=QD ID 128246 {{!}} Launch Studio - Listing Details|last=|first=|date=|website=launchstudio.bluetooth.com|archive-url=|archive-date=|dead-url=|access-date=2019-08-27}}</ref>
|Alibaba (China) Co., Ltd.
|{{Dts|2019-07-20}}
Line 346 ⟶ 379:
|Profile Subsystem
|-
|ClarinoxBlue<ref>{{Cite web|url=https://launchstudio.bluetooth.com/ListingDetails/RedirectFromQdid/134454|title=QD ID 134454 {{!}} Launch Studio - Listing Details|last=|first=|date=|website=launchstudio.bluetooth.com|archive-url=|archive-date=|dead-url=|access-date=2019-08-27}}</ref>
|[[Clarinox Technologies Pty Ltd]]
|{{Dts|2019-08-02}}
|134454
|Host Subsystem
|-
|BlueX Mesh<ref>{{Cite web|url=https://launchstudio.bluetooth.com/ListingDetails/RedirectFromQdid/137436|title=QD ID 137436 {{!}} Launch Studio - Listing Details|last=|first=|date=|website=launchstudio.bluetooth.com|archive-url=|archive-date=|dead-url=|access-date=2019-08-27}}</ref>
|BlueX Microelectronics Corp Ltd.
|{{Dts|2019-08-20}}
|137436
|Profile Subsystem
|-
|Zephyr OS Mesh<ref>{{Cite web|url=https://launchstudio.bluetooth.com/ListingDetails/RedirectFromQdid/139259|title=QD ID 139259{{!}} Launch Studio - Listing Details|website=launchstudio.bluetooth.com|access-date=2020-03-12}}</ref>
|[[The Linux Foundation]]
|{{Dts|2019-09-20}}
|139259
|Profile Subsystem
|-
|WCH Bluetooth Mesh<ref>{{Cite web|url=https://launchstudio.bluetooth.com/ListingDetails/RedirectFromQdid/144808|title=QD ID 144808{{!}} Launch Studio - Listing Details|website=launchstudio.bluetooth.com|access-date=2020-06-01}}</ref>
|Nanjing Qinheng Microelectronics Co., Ltd.
|{{Dts|2020-06-01}}
|144808
|Profile Subsystem
|}
Line 361 ⟶ 406:
=== Free and open-source software implementations ===
[[Free software]] and [[The Open Source Definition|open source software]] implementations include the following:
* The official (included in [[Linux kernel]] by [[Linus Torvalds|Linus Thorvalds]] in 2001<ref>{{Cite web|url=http://www.bluez.org/about/history/|title=BlueZ History|last=|first=|date=2019-09-07|website=BlueZ|url-status=live|archive-url=|archive-date=|access-date=}}</ref>) Linux Bluetooth protocol stack [[BlueZ]], dual free-licensed under the [[GNU General Public License|GPL]]<ref name="bluez_GPL" /> and the [[GNU Lesser General Public License|LGPL]],<ref name="bluez_LGPL" />, supports Mesh Profile, from release version 5.47,<ref>{{Cite web|url=http://www.bluez.org/release-of-bluez-5-47/|title=BlueZ » Blog Archive » Release of BlueZ 5.47|website=www.bluez.org|access-date=2017-10-27}}</ref>, 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.<ref name="bluez_SIGqualified" /> BlueZ is not considered to be a qualified Bluetooth Mesh stack as Bluetooth Mesh is not listed{{where|date=September 2019}}in aforementioned qualification record as a supported profile.
* [[Bluetooth stack#Apache Mynewt NimBLE|Apache Mynewt NimBLE]], free-licensed under the [[Apache License#Compatibility|Apache License 2.0]],<ref name="mynewt_apache2p0" /> supports Bluetooth Mesh from release version 1.2.0.<ref>{{Cite web|url=https://cwiki.apache.org/confluence/display/MYNEWT/RN-1.2.0|title=RN-1.2.0 - Apache Mynewt - Apache Software Foundation|website=cwiki.apache.org|access-date=2018-07-02}}</ref> It was qualified on {{Start date|2019|07|15}} with QDID 131934.<ref name=":2" />
* [[Bluetooth stack#Zephyr OS Mesh|Zephyr OS Mesh]], free-licensed under the [[Apache License#Compatibility|Apache License 2.0]],<ref name="zephyr_apache2p0" /> supports Bluetooth Mesh from release version 1.9.0.<ref>{{Cite web|url=https://docs.zephyrproject.org/latest/releases/release-notes-1.9.html#zephyr-kernel-1-9-0|title=Release Notes Zephyr Kernel 1.9.0|website=docs.zephyrproject.org|access-date=2020-03-21}}</ref> Zephyr OS Mesh 1.14.x was qualified on {{Start date|2019|09|20}} with QDID 139259.<ref name=":2" />
 
== See also ==
* [[Cabir (computer worm)]]
* [[BlackArch]]
* [[Bluejacking]]
* [[Bluebugging]]
* [[Bluesnarfing]]
* [[AirDrop]]
 
== References ==
{{Reflist|refs=
 
<ref name="bluez_SIGqualified">{{cite web | last1 = | first1 = | last2= | first2= | authorlink = | coauthors = | title = Qualified Product Detail | work = | publisher = | website= [[Bluetooth Special Interest Group|Bluetooth SIG]] |date = | url = https://www.bluetooth.org/qualweb/ProductDetails.cfm?ProductID=2379 |format = | doi = | accessdateaccess-date = 2019-09-05 |archiveurlarchive-url= https://web.archive.org/web/20190905203425/https://www.bluetooth.org/qualweb/ProductDetails.cfm?ProductID=2379 |archivedatearchive-date= 2019-09-05 |deadurlurl-status=nolive}}</ref>
 
<ref name="mynewt_apache2p0">{{cite web | title = apache/mynewt-core/LICENSE | website= [[GitHub]] |date = 2018-06-04 | url = https://github.com/apache/mynewt-core/blob/master/LICENSE | access-date = 2019-09-05 |archive-url= https://web.archive.org/web/20190905203215/https://github.com/apache/mynewt-core/blob/master/LICENSE |archive-date= 2019-09-05 |url-status=live}}</ref>
 
<ref name="mynewt_apache2p0zephyr_apache2p0">{{cite web | last1 = | first1 = | last2= | first2= | authorlink = | coauthors = | title = apachezephyrproject-rtos/zephyr/mynewt-coreblob/master/LICENSE | work = | publisher = | website= [[githubGitHub]] |date = 20182020-0603-0421 | url = https://github.com/apache/mynewt-core/blob/master/LICENSE |format = | doiaccess-date = | accessdate = 20192020-0903-0521 |archiveurlarchive-url= https://web.archive.org/web/20190905203215/https://github.com/apachezephyrproject-rtos/mynewt-corezephyr/blob/master/LICENSE |archivedatearchive-date= 2019-09-05 |deadurlurl-status=nolive}}</ref>
 
<ref name="bluez_GPL">{{cite web | last1 = | first1 = | last2= | first2= | authorlink = | coauthors = | title =index : bluez.git – Bluetooth protocol stack for Linux – Marcel Holtmann | work = | publisher = | website= [[kernel.org]] |year = 1991 | url = https://git.kernel.org/pub/scm/bluetooth/bluez.git/tree/COPYING |format = | doi = | accessdateaccess-date = 2019-09-05 |archiveurlarchive-url= https://web.archive.org/web/20190905201757/https://git.kernel.org/pub/scm/bluetooth/bluez.git/tree/COPYING |archivedatearchive-date= 2019-09-05 |deadurlurl-status=nolive}}</ref>
 
<ref name="bluez_LGPL">{{cite web | last1 = | first1 = | last2= | first2= | authorlink = | coauthors = | title = index : bluez.git – Bluetooth protocol stack for Linux – Marcel Holtmann | work = | publisher = | website= [[kernel.org]] | year = 1999 | url = https://git.kernel.org/pub/scm/bluetooth/bluez.git/tree/COPYING.LIB |format = | doi = | accessdateaccess-date = 2019-09-05 |archiveurlarchive-url= https://web.archive.org/web/20190905201816/https://git.kernel.org/pub/scm/bluetooth/bluez.git/tree/COPYING.LIB |archivedatearchive-date= 2019-09-05 |deadurlurl-status=nolive}}</ref>
 
}}
Line 379 ⟶ 435:
[[Category:Bluetooth]]
[[Category:Open standards]]
[[Category:Wireless networking]]
[[Category:Mesh networking]]