User Manual

WiSe 1210 Bluetooth Low Energy Module User’s Guide
WiSilica Inc Proprietary and Confidential
Introduction
This chapter introduces the WiSe1210 Bluetooth Low Energy module which also
includes some fundamentals concepts of Bluetooth Low Energy (BLE). The
WiSe1210 Bluetooth® Low Energy Module is a single mode Bluetooth Smart module
that complies with Bluetooth Core Specification v4.1. WiSe1210 enables ultra-low-
power connectivity and basic data transfer for applications previously limited by the
power consumption, size constraints and complexity of other wireless standards.
WiSe 1210 module provides everything required to create a Bluetooth low energy
product with RF, baseband, MCU, qualified Bluetooth v4.1 specification stack and
customer application running on a single IC The WiSe1210 module is easy to use
and provides users with a fast-to-market, flexible, and powerful solution for BTLE
technology.
Finally, the WiSe1210 module also supports a user-defined private profile/service,
which can precisely fit a user's particular application. All configurations will be saved
in on-board non-volatile memory (NVM), so users need to set up the module only
once.
Bluetooth Low Energy Fundamentals
All BTLE device roles are built on top of the Generic Accessory Profile (GAP), which
defines the devices to be either Central, Peripheral, Observer or a Broadcaster.
When two BTLE devices need to establish a connection, one is in a central role and
the other in a peripheral role. Only central role devices can initiate a connection to
peripheral role devices. Likewise, peripheral devices are not allowed to initiate
connections. The peripheral advertises its connection status, while the central device
starts the connection process. Once connected, either end of the connection can
initiate the bond. Once bonded, all security-related keys will be saved and the
security process will be waived when reconnecting. The bonded peripheral device
can only perform direct advertise; therefore, it is no longer able to connect to devices
other than its bonded peer. Similar to Bluetooth Classic, BTLE uses the concept of
profiles to ensure interoperability between different devices. However, unlike
Bluetooth Classic, BTLE profiles are a collection of services.
All BTLE services are built on top of the Generic Attribute Profile (GATT), where
GATT defines the accessibility of attributes, which are called characteristics.
Therefore, the main functionality of BTLE profiles is built around these characteristics.
Devices that maintain the value of characteristics in a service are the “server” of the
service. Conversely, devices that acquire data from their peer are considered the
“client”. Each service and its characteristics are identified by their Universally Unique
Identifier (UUID). The UUID can either be short form (16-bit) or long form (128-bit).
All Bluetooth SIG adopted services and characteristics have a short UUID, whereas
a user-defined private UUID must be in long form. For information on the Bluetooth
SIG adopted services and characteristics, visit the Bluetooth Developer Portal at:
https://developer.bluetooth.org/gatt/profiles/Pages/ProfilesHome.aspx