蓝牙低功耗开发入门指南

低功耗蓝牙

需积分: 49 28 浏览量更新于2023-06-04 收藏 17.78MB PDF 举报

身份认证购VIP最低享 7 折!

领优惠券(最高得80元）

资源详情

资源推荐

phenomenal growth in smartphones, tablets, and mobile computing. Early and active

adoption of BLE by mobile industry heavyweights like Apple and Samsung broke open

the doors for wider implementation of BLE.

Apple, in particular, has put significant effort into producing a reliable BLE stack and

publishing design guidelines around BLE. This, in turn, pushed silicon vendors to

commit their limited resources to the technology they felt was the most likely to succeed

or flourish in the long run, and the Apple stamp of approval is clearly a compelling

argument when you need to justify every research and development dollar invested.

While the mobile and tablet markets become increasingly mature and costs and margins

are decreasing, the need for connectivity with the outside world on these devices has a

huge growth potential, and it offers peripheral vendors a unique opportunity to provide

innovative solutions to problems people might not even realize that they have today.

So many benefits have converged around BLE, and the doors have been opened wide

for small, nimble product designers to gain access to a potentially massive market with

task-specific, creative, and innovative products on a relatively modest design budget.

You can purchase all-in-one radio-plus-microcontroller (system-on-chip) solutions

today for well under $2 per chip and in low volumes, which is well below the total overall

price point of similar wireless technologies such as WiFi, GSM, Zigbee, etc. And BLE

allows you to design viable products today that can talk to any modern mobile platform

using chips, tools, and standards that are easy to access.

Perhaps one of the less visible key factors contributing to the success of BLE is that it

was designed to serve as an extensible framework to exchange data. This is a funda‐

mental difference with classic Bluetooth, which focused on a strict set of use cases. BLE,

on the other hand, was conceived to allow anyone with an idea and a bunch of data

points coming from an accessory to realize it without having to know a huge amount

about the underlying technology. The smartphone vendors understood the value of this

proposition early on, and they provided flexible and relatively low-level APIs to give

mobile application developers the freedom to use the BLE framework in any way they

see fit.

Devices that talk to smartphones or tablets also offer another easy-to-underestimate

advantage for product designers: they have an unusually low barrier to adoption. Users

are already accustomed to using the handsets or tablets in their possession, which means

the burden of learning a new UI is limited, as long as we respect the rich visual language

that people have grown accustomed to in the platforms they use.

With a relatively easy-to-understand data model, no intrusive licensing costs, no fees

to access the core specs, and a lean overall protocol stack, it should be clear why platform

designers and mobile vendors see a winner in BLE.

2 | Chapter 1: Introduction

www.it-ebooks.info

The Specification

In June 2010, the Bluetooth SIG introduced Bluetooth Low Energy with version 4.0 of

the Bluetooth Core Specfication. The specification had been several years in the making

and most of the controversial sections and decisions were finally ironed out by the

companies involved in the development process, with a few additional concerns left to

be dealt with in subsequent updates of the specification.

The first such major update, Bluetooth 4.1, was released in December 2013 and is the

current reference for anyone looking to develop BLE products. Althought the basic

building blocks, procedures, and concepts remained intact, this release also introduced

multiple changes and improvements to smooth the experience of the user.

As with all Bluetooth specifications, 4.1 is backwards compatible with 4.0, ensuring the

correct interoperability among devices implementing different specification versions.

The specifications allow developers to release and qualify products against either of the

versions (until deprecated), although the rapid adoption of new specification releases

and the fact that the 4.1 version standardizes several common practices among devices

makes it recommendable to target the latest available one.

Unless otherwise noted, this book uses the Bluetooth 4.1 specification as reference.

Wherever necessary, and especially when mentioning a noteworthy change or addition,

we will clarify when the previous 4.0 specification does not cover a particular area.

To obtain the latest adopted version of the Bluetooth specification, see the Bluetooth

SIG’s Specification Adopted Documents page.

Configurations

The Bluetooth specification covers both classic Bluetooth (the well-known wireless

standard that has been commonplace in many consumer devices for a number of years

now) and Bluetooth Low Energy (the new, highly optimized wireless standard intro‐

duced in 4.0). Those two wireless communication standards are not directly compati‐

ble and Bluetooth devices qualified on any specification version prior to 4.0 cannot

communicate in any way with a BLE device. The on-air protocol, the upper protocol

layers, and the applications are different and incompatible between the two technolo‐

gies.

Based on Specification Support

Table 1-1 shows the wireless technologies implemented for the three main device types

on the market today.

The Specification | 3

www.it-ebooks.info

More and more BR/EDR devices entering the market include BLE as well, and the trend

is expected to continue as single-mode BLE sensors become more ubiquitous. Those

dual-mode devices can forward the data obtained from a single-mode BLE device to

the internet using their GSM or WiFi radios, a feature that is becoming more and more

common as more BLE sensors enter the market.

Based on Chip Count

Chapter 2 introduces and discusses the several protocol layers that constitute the Blue‐

tooth protocol stack, but for now it suffices to outline the three main building blocks

of every Bluetooth device:

Application

The user application interfacing with the Bluetooth protocol stack to cover a par‐

ticular use case.

Host

The upper layers of the Bluetooth protocol stack.

Controller

The lower layers of the Bluetooth protocol stack, including the radio.

Additionally, the specification provides a standard communications protocol between

the host and the controller—the Host Controller Interface (HCI)—to allow interoper‐

ability between hosts and controllers produced by different companies.

These layers can be implemented in a single integrated circuit (IC) or chip, or they can

be split in several ICs connected through a communication layer (UART, USB, SPI, or

other).

These are the three most common configurations found in commercially available

products today:

SoC (system on chip)

A single IC runs the application, the host, and the controller.

Dual IC over HCI

One IC runs the application and the host and communicates using HCI with a

second IC running the controller. The advantage of this approach is that, since HCI

is defined by the Bluetooth specification, any host can be combined with any con‐

troller, regardless of the manufacturer.

Dual IC with connectivity device

One IC runs the application and communicates using a propietary protocol with a

second IC running both the host and the controller. Since the specification does

not include such a protocol, the application must be adapted to the specific protocol

of the chosen vendor.

Configurations | 5

www.it-ebooks.info

剩余179页未读，继续阅读

VioletL

粉丝: 1
资源: 15

会员权益专享

蓝牙低功耗开发入门指南

Getting Started with Bluetooth Low Energy

Getting started with bluetooth low energy

蓝牙协议的学习.pdf

Python Fundamentals: Getting Started with Python

Getting Started with ARCO Design Tools and Frameworks

Getting Started with Flink: Installation and Setup Guide

gsdml_getting_started_en.pdf

getting started with qt5 pdf

getting-started-with-bluetooth-low-energy

Cloning into 'getting-started'... fatal: unable to access 'https://github.com/docker/getting-started.git/': GnuTLS recv error (-54): Error in the pull function.

Installing build dependencies ... done Getting requirements to build wheel ... error error: subprocess-exited-with-error

paddlehub Getting requirements to build wheel ... error error: subprocess-exited-with-error

java给pdf加目录跳转

安装zxing报错Getting requirements to build wheel ... error

在idea里面按什么快捷键得到Getting started IntelliJ IDEA

https://spdk.io/doc/getting-started/example-applications.html还是没有

matlab app designer教程 pdf

使用pdf.js 下载源文件

getting started with machine learning

Getting requirements to build wheel ... error

会员权益专享

最新资源