## 4 Applications and Market Adoption
ACKs} & \multirow{4}{*}{24-bit CRC. ACKs (payload). ACKs} \\ \cline{1-1} \cline{2-6}  & **Latency (ms)** & & & & \\ \cline{1-1} \cline{2-6}  & \multirow{4}{*}{16- and 64-bit MAC addresses, 16-bit addresses, 128-bit IPv6 addresses} & \multirow{4}{*}{16-bit address-bit (node ID), Bluetooth address or random address} & \multirow{4}{*}{48-bit public device Bluetooth address} \\ \cline{1-1} \cline{2-6}  & & & & & \\ \cline{1-1} \cline{2-6}  & \multirow{4}{*}{16-bit ACKs (optional)} & \multirow{4}{*}{8-bit checksum. ACKs (optional) ACKs (payload). ACKs} & \multirow{4}{*}{24-bit CRC. ACKs (payload). ACKs} \\ \cline{1-1} \cline{2-6}  & & & & & \\ \cline{1-1} \cline{2-6}  & \multirow{4}{*}{16-bit ACKs (optional) ACKs (payload). ACKs} & \multirow{4}{*}{16-bit ACKs (payload). ACKs} & \multirow{4}{*}{16-bit ACKs (payload). ACKs} \\ \cline{1-1} \cline{2-6}  & & & & & \\ \cline{1-1} \cline{2-6}  & \multirow{4}{*}{16-bit ACKs (pos)} & \multirow{4}{*}{16-bit ACKs (payload). \begin{table}
\begin{tabular}{|c|c|c|c|c|c|c|} \cline{2-7} \multicolumn{1}{c|}{} & \multicolumn{1}{c|}{**ZigBee**} & **6 LoWPAN (Over 802.15.4)** & **Z-Wave** & **Bluetooth Low Energy** & **Classic Bluetooth** \\ \hline \multirow{3}{*}{**Device types or roles**} & Coordinator, Router and End device & Edge Router, Mesh Node & \multirow{3}{*}{Controller and slave} & \multirow{3}{*}{Master and slave} & \multirow{3}{*}{Master and slave} \\  & and End device & & & & & \\  & & and End device & & & & \\  & & & over), Host & & & \\ \hline \multirow{5}{*}{**Network layer**} & \multirow{3}{*}{**Multi-hop solution**} & Mesh routing, tree routing, and source routing & RPL (other protocols are not excluded) & Source routing & Not currently supported &
\begin{tabular}{c} Scatternet (routing protocol out of the scope of the Bluetooth specifications) \\ \end{tabular} \\  & & & routing/tree routing/source routing & 255 & 4 & 1 & Outside scope of Bluetooth specifications \\ \hline \multirow{5}{*}{**Security**} & \multirow{5}{*}{Key management} & Integrity, confidentiality, access control & \multirow{5}{*}{128-bit AES} & Security Modes/Levels. Pairing, Key & Pairing and Link Key Generation. Authentication. \\  & & & out of scope & encryption (400 & Confidentiality, Confidentiality, Levels, Service Levels, and Authorization. \\  & & & & & \\  & & & & Integrity & & \\ \hline \multirow{2}{*}{**Implementation size**} & 45–128 kB (ROM), & 24 kB (ROM), & 32–64 kB (Flash), & \multirow{2}{*}{-40 kB (ROM), \(\sim\)2.5 kB (RAM)} & \multirow{2}{*}{-100 kB (ROM), \(\sim\)30 kB (RAM)} \\  & 2.7–12 kB (RAM) & 3.6 kB (RAM) & & & \\ \hline \end{tabular}
\end{table} 
Table 2: \(Cont.\)Healthcare, wellness and sports constitute an application domain where classic Bluetooth has already been used [14, 15], and for which BLE constitutes an improvement [16]. In fact, the Continua Health Alliance, an industry coalition of healthcare and technology companies [17], announced the selection of BLE for \"activity monitors and heart rate sensors to be used to monitor a user's health and fitness levels\" [18]. Another opportunity for BLE is the possibility that the mobile phone may constitute a universal remote control for the domestic devices in a home. Smart energy and home security applications may further exploit BLE-enabled mobile phones. The single-hop scope of BLE may require proper transmit power tuning. In fact, most Wireless Home Automation Network (WHAN) technologies support the formation of multihop networks [2]. The dimensions of a home and signal propagation therein will determine the appropriate transmit power setting for BLE devices and whether or not BLE will be the only technology used. On the other hand, BLE can be used for contactless applications, such as mobile payment, ticketing or access control. However, Near Field Communication (NFC) was primarily designed for this use case space [9, 19], and since then, the panoply of device models that support NFC has been growing at a moderate but steady rate.