Bluetooth Low Energy (LE) overview
Bluetooth LE introduces a new physical layer that shares the same frequency space as Bluetooth basic rate. Profiles that are developed on this technology are organized into the generic attribute profile (GATT).
Each profile defines the use of one or more services to create a use case or scenario. Compliant service implementations are constructed from characteristics organized in a way that conforms to the established schema defined on the Bluetooth Special Interest Group developer website.
The following diagram illustrates the way objects are structured inside a typical GATT service.
When a Bluetooth LE device is paired with a Windows machine, the device becomes part of the system. Windows provides device objects to represent both the device and the primary services reported by the device.
Each device and its primary services are represented as device objects in Windows and these device objects can be queried and managed using the device installation functions such as SetupDiEnumDeviceInfo, and SetupDiGetDeviceProperty.
In addition to standard Bluetooth profile driver functions, Bluetooth LE functions provide functionality for the development of Bluetooth GATT client applications.
These functions allow for the enumeration of services and their objects (including services, characteristics and their descriptors) as well as read and write capabilities.
Collaborate with us on GitHub
The source for this content can be found on GitHub, where you can also create and review issues and pull requests. For more information, see our contributor guide.
Windows driver documentation
Общие сведения о Bluetooth Low Energy (LE)
Bluetooth LE представляет новый физический уровень, который использует то же пространство частоты, что и базовая скорость Bluetooth. Профили, разработанные на основе этой технологии, упорядочены в универсальный профиль атрибутов (GATT).
Каждый профиль определяет использование одной или нескольких служб для создания варианта использования или сценария. Соответствующие реализации служб создаются на основе характеристик, упорядоченных в соответствии с установленной схемой, определенной на веб-сайте разработчика Bluetooth Special Interest Group.
На следующей схеме показан способ структурирования объектов в типичной службе GATT.
Когда устройство Bluetooth LE связано с компьютером Windows, устройство становится частью системы. Windows предоставляет объекты устройства, представляющие как устройство, так и основные службы, о чем сообщает устройство.
Каждое устройство и его основные службы представлены как объекты устройств в Windows, и эти объекты устройств можно запрашивать и управлять ими с помощью таких функций установки устройств , как SetupDiEnumDeviceInfo и SetupDiGetDeviceProperty.
В дополнение к стандартным функциям драйвера профиля Bluetoothфункции Bluetooth LE предоставляют функции для разработки клиентских приложений Bluetooth GATT.
Эти функции позволяют выполнять перечисление служб и их объектов (включая службы, характеристики и их дескрипторы), а также возможности чтения и записи.
Совместная работа с нами на GitHub
Источник этого содержимого можно найти на GitHub, где также можно создавать и просматривать проблемы и запросы на вытягивание. Дополнительные сведения см. в нашем руководстве для участников.
Windows driver documentation
Общие сведения о профиле близкого взаимодействия Bluetooth LE
Обнаружение близкого взаимодействия — это распространенное использование Bluetooth Low Energy (LE). В этом разделе приведены рекомендации по созданию реализации профиля близкого взаимодействия для устройств, которую можно использовать для разработки приложения для устройств UWP.
Перед разработкой этого приложения необходимо ознакомиться с функциями Bluetooth LE и спецификацией профиля близкого взаимодействия Bluetooth LE.
Пример объявления службы
Bluetooth Low Energy представил новый физический уровень, который использует тот же диапазон частоты, что и Bluetooth Basic Rate. Профили с низким энергопотреблением организованы в так называемый универсальный профиль атрибутов (или GATT).
Профиль GATT объявляет одну или несколько служб, определяющих вариант использования или сценарий. Чтобы разработать соответствующую реализацию службы, необходимо упорядочить характеристики таким образом, чтобы они соответствовали установленной схеме, определенной на веб-сайте разработчика Bluetooth Special Interest Group (SIG).
На этой схеме показано, как характеристики структурированы в типичной службе GATT.
Пример профиля близкого взаимодействия описан далее в разделе Профиль близкого взаимодействия Bluetooth.
Совместная работа с нами на GitHub
Источник этого содержимого можно найти на GitHub, где также можно создавать и просматривать проблемы и запросы на вытягивание. Дополнительные сведения см. в нашем руководстве для участников.
Windows driver documentation
What Is Bluetooth LE and How Does It Work?
Bluetooth Low Energy or simply BLE, and the protocol that it sprang from, Bluetooth, are some of the most well known protocols for the average consumer. Bluetooth (BT), is used every single day for diverse applications. This includes headset audio, smart devices, peripheral connectivity (Keyboards, mice, microphones, printers) and even wearables like the FitBit and Amazon’s Halo Band.
BLE, in contrast to standard bluetooth, is much more often used for low-power consumption devices, eating up the market share for things like the aforementioned wearables, but also being used in industry for more standard IoT applications. BLE can have more range, longer run times, and more friendly power consumption stats than an always-on Bluetooth standard device.
Bluetooth is undoubtedly the king in IoT for sheer number of users and applications- Vector IT group in 2018 estimated there would be more than five billion combined Bluetooth devices across classic Bluetooth and BLE active by this year.
Where did BLE Originate?
Bluetooth Low Energy was introduced in December 2009 as an integration into the overarching Bluetooth standard 4.0. It’s still classified as a WPAN, or Wireless Personal Area Network (though that particular appellation is being stretched further and further as time progresses). It’s managed as a standard by the Bluetooth SIG, or Special interest group.
BLE rose out of a need to have a more energy-conscious design than regular Bluetooth, and to some degree to standardize some novel applications that vendors had begun using legacy Bluetooth for- After all, if you don’t need your device to beacon or listen all the time, it’s kind of a waste to have it doing so. The main goal, thusly, with BLE was to make a protocol deviation from the standard that would use less energy, while maintaining the usefulness and range of its previous incarnation.
Also notably, BLE and Bluetooth «classic» are not compatible naturally. One device can run both in many cases, however, your phone, for example, may be capable of communicating with both BLE IoT devices, and your legacy Bluetooth headset. The Bluetooth SIG originally even had a logo for devices that would be capable of this, but it has since been retired (inset).
Bluetooth Low Energy (BLE) was the brainchild of researchers at Nokia, which began work on use cases that Bluetooth may not be ideally suited for, but could likely be adapted to. Nokia published this development in 2004, then named Bluetooth Low End Extension. This development continued through partnership with popular peripheral maker Logitech and ended in a consumer product under the name Wibree. Seeing this development, Bluetooth SIG agreed to include it in a future standard, which it was in the future 4.0 standard. (Bluetooth is now at 5.0, as of writing in 2021). One of the more recent and important additions to the standard has been Mesh Profiles and Models, in 2017.
Use Cases and Profiles
The Bluetooth SIG designates specifications for ways that a BLE device may function, called Profiles. The most common being GATT, or Generic Attribute Profile, which covers the most general use case of sending small amounts of data in a PAN range with a low energy cost relative to the standard. They do, however define a number of other specialist profiles, such as:
- Mesh Profiles. BLE devices that can connect to other devices concurrently and route data between them, forming a mesh, contrasting with the 1:1 connection that Bluetooth is known for and the 1 to many that WiFi is best known for.
- Health Care Profiles. These serve dedicated clinical needs, like measuring Blood pressure, temperature, and blood sugar. These, with further development may even lead to a WBAN (Wireless Body Area Network) application.
- Sports and fitness Profiles. Mainly for scales, fitness trackers and some GPS enabled applications (or accelerometers) designed for its namesake. Your FitBit would «fit» here.
- Various others, including Battery and power level monitoring
BLE is quite the adaptive protocol, and has found nearly as many use cases as there are devices out there. If you were to take a spectrum analysis device out into the wild, you’d likely be shocked by how often you’d catch the signature of a BLE or Bluetooth transmission over the air. It’s become so incredibly prolific that we don’t much consider IF it will be there, but rather WHEN we’d like to use it.
Millions and millions of users simply leave the Bluetooth on their phone or computer on and expect services to auto-connect. A prime example would be when people get into the car for your morning commute. Provision has been given for it to «just work» by many car manufacturers where a certain device may be allowed or even set to connect and begin playing anything the user has configured on a playlist or through an application like Youtube.
BLE Spectrum and Transmission
Okay, now the nerdy stuff! How does BLE actually work? BLE works in a familiar frequency space, the 2.4 Ghz range. Savvy readers will recognize that this is the same range that WiFi and Bluetooth Classic, as well as many other protocols like ISA100.11a transmit in. However, both Bluetooth and BLE use different channel sets than both each other and WiFi.
Bluetooth classic runs 79 1MHz width channels, and BLE by contrast runs 40 2 MHz channels. While both are considered frequency-hopping, BT classic uses FHSS, or Frequency Hopping Spread Spectrum. BLE uses a version of Direct Sequence Spread Spectrum which is a bit more deterministic. Both use a modulation scheme referred to as Gaussian frequency shift Keying, or GFSK. Unlike FHSS/DSSS, you won’t see GFSK nearly ever represented in WiFi unless it’s a proprietary standard and device.
BLE doesn’t use the more popular beaconing method, but rather a specific type of packet called a broadcast advertising packet. The Packet is sent on a minimum of three channels, and is repeated in a driver defined period called the advertising interval which has a «salted» random delay, similar to the backoff timer in WiFi to avoid undetected interference.
Rate and Use Case Limitations
BLE and Bluetooth are great, but they do of course have use cases they’re simply not suited for, namely they have range and rate limitations. Bluetooth has an ideal throughput of about 2 Mbps, and BLE has an ideal throughput of just short of 1.5Mbps. This means that streaming HD or 4K video is of course, right out. This rate, as anyone who has used it can attest, is generally fine for music streaming, or chat, or audio generally but would be wholly unsuited for larger files. No one in the world is going to propose you beam your CAD file through Bluetooth! That said, most applications that transfer text, small pictures or steaming audio are handled quite well.
Keep in mind with BLE however, that one of the main goals of the protocol is to be low-energy; This means that constant, high throughput applications should generally be avoided. BLE wants to conserve your battery, and there is an inverse relation between frequency and length of transmission and your battery life.
A good example here would be the Amazon Halo band, which is set to update the app on your phone once per hour. It has about two days of practical battery life when that’s all that it’s doing. Conversely, it has a function where it can show your tone or your heart rate as a live reading, meaning that it’s transmitting constantly and therefore the battery life is reduced dramatically. Be mindful when you’re using, or suggesting BLE for a use case, that this relationship exists. A good example would be ISA100.11a deployments in the same vein; they’re designed to be battery driven and run for years without intervention.
Final Thoughts
BLE can be a great protocol as long as it’s kept within the bounds the protocol is established for, and benefits from incredibly wide adoption as well as a wide availability of both industrial and consumer support. APs are built with BLE radios, phones have them, just about every sophisticated wireless device is at least capable of being adapted to use it. Armed with this knowledge, you’re ready to go out and use this ubiquitous protocol for your home or office in the right way and get the most out of it!