Reference for device builders
When you add Blecon support to your device, you gain access to a request/response-based communication API that operates over Bluetooth Low Energy. In addition, Blecon takes care of device identification, device connection and provisioning, time services, and secure communication with the Blecon network service.
A Blecon modem can be integrated into your device and a host MCU can leverage its API over a SPI, UART or USB connection. It manages the whole Blecon stack from security, RPC and down to radio and optimising power consumption.
On the cloud-end, a collection of devices can be associated with HTTP web-hook endpoints which are triggered on different events (device request, device spotted, etc) forming a network. This gives a clear integration contract to cloud and device teams.
For more information, start with the Blecon Introduction.


Request/Response communication

A typical interaction with a Blecon modem
A host MCU can request a connection to a Blecon network. Once established, the host MCU receives an event from the modem and can start sending requests and retrieving responses from the corresponding cloud application.
Blecon request/response model


On the first power-up, a modem will generate its identity (unique UUID) and credentials (public/private key pair) and register itself in-band with the Blecon infrastructure, ensuring security throughout its lifecycle without a complex provisioning process.
Provisioning Procedure

Device Identification and Connection

Each modem possesses a unique identifier (UUID). This UUID can be recovered by the host MCU using the modem's API. Additionally if a NFC antenna is connected to the modem, NFC can be used to identify the device. Finally, the host MCU can trigger an identification procedure (typically at the push of a button) over BLE to let nearby hotpots retrieve the device's UUID.
Once retrieved, this unique identifier can be used to connect the device to a Blecon network, and/or associate the device using application-specific logic.
Blecon Network Connection

Secure Bluetooth Communication from device to cloud

Blecon modems manage Bluetooth advertising and connections to Blecon hotspots. Unlike typical Bluetooth security, Blecon security is ensured from device to cloud, so a Blecon hotspot cannot understand or tamper with any data. Additionally this means no pairing is necessary for a Blecon device to operate, meaning any hotspot can provide a device with connectivity.
Blecon Security model
For more information about the Blecon security model and threat model, please contact us.

Blecon Modem

The Blecon Modem is available in a variety of forms to suit your use case.

Blecon Modem Prototyping Breakout

The simplest for prototyping is the Blecon Modem breakout board. This is a self-contained and zero-configuration module which is suitable for both prototyping and production use. Your MCU communicates with the modem over SPI or a UART connection to use the Blecon Command Protocol.
The Blecon Modem breakout also features a USB connection for prototyping using the Blecon Modem CLI.
The Blecon Modem Breakout is now available to Early Access participants. For more information on the modem, see Seeed Modem Breakout and Using the Blecon Modem.
Follow the Seeed Modem Quickstart to start sending requests using the Blecon Modem.

Blecon Chip

The Blecon chip (BCN2201) includes everything needed for direct integration in to your product alongside a host MCU provide the simplest way for rapid development and deployment.
Read the BCN2201's documentation, and for more details, please contact us.

Blecon Modem Firmware

Firmware modem for direct integration alongside your application to run on a Bluetooth enabled MCU.
Our reference implementation is based on the Nordic nRF52 family of Bluetooth Low Energy MCUs:
For more details, please contact us.