UWB Network Topology: Application Note
UWB Network Topology: Application Note
Application note
Introduction
The first step of every deployment is an offline study of the area to cover all predictable environment constraints. An adapted
UWB network topology is the key to ensure the best UWB communication between all devices and robust global coverage.
This document is a general application note. It is not related to one particular product, like the B-UWB-MEK1 embedding
the B-UWB-MOD1, but provides general information as well as a few examples which can be used for all location systems
developed by BeSpoon.
Legend
SUB-CELL SUB-CELL
fixed device which transmits the
ROOT beacon frames for the whole -
network synchronization
beacon frames transmitted by the
root
fixed devices which receive
RELAY
RELAY beacon frames from the root and
repeat them
beacon frames transmitted by the
relays RELAY
RELAY
RELAY
RELAY
MASTER
CELL
1 General information
B-UWB-MEK1 embeds the B-UWB-MOD1, which features the STM32L476JE 32-bit microcontroller based on the
Arm® 32-bit Cortex®‑M4 processor.
Note: Arm is a registered trademark of Arm Limited (or its subsidiaries) in the US and/or elsewhere.
Definitions
Table 1 presents the definition of acronyms that are relevant for a better understanding of this document.
Term Definition
References
Refer to the following documents for an introduction to the B-UWB-MEK1 and B-UWB-MOD1 products in indoor
location systems:
• Ultra-wideband module for high-precision indoor location (DB4404)
• Evaluation kit for the B-UWB-MOD1 ultra-wideband module (DB4392)
• B-UWB-MEK1 quick start guide (UM2798)
• Modification of the superframe information for UWB products (AN5602)
• SDK advanced documentation
Demonstration software
Contact the local STMicroelectronics sales office or distributor (refer to www.st.com) for the latest software and
associated documentation.
2 Topology rules
The rules described in this document concern the fixed devices (infrastructure).
The topology starts from a master cell, managed by a root device. Its role is to ensure the time synchronization of
the cell of other devices, by sending a beacon frame at a regular time interval.
The master cell can be composed of one root device and up to 63 other devices (current maximum capacity of
the system). All the devices must be placed in a way they can receive the beacon frame of the root device. The
root device can be placed at any position. Best practices may be to place the root in line of sight (LoS) with other
anchors of the cell to give the best UWB synchronization link and so the best localization precision.
In case the beacon frame of the root device is not available for all devices (if the positions hinder LoS, for
example), the system administrator must choose one or more devices to relay the beacon frame.
These devices are called relay devices also called secondary beacons, up to 15 devices can be chosen for this
role. Then, other devices can be configured to listen to one of the relay devices to compose a sub-cell also called
a secondary cell. Some other sub-cells can be created, synchronized on other relay devices for a highly extended
setup.
Tracked devices also need to receive a beacon frame to be synchronized. They find by themselves (according to
their positions) from which fixed device (root or relay) they may obtain their synchronization.
In Multi-Tag Tracking mode, the use of all relay devices is recommended to optimize the signal quality. In
GPS‑like positioning mode, the use of all relay devices is mandatory.
The exact amount of relay devices depends on advanced protocol settings called Superframe Information (SFI)
and described in the application note Modification of the superframe information for UWB products (AN5602)
3 Deployment examples
Relay device
Here is an example where the administrator chooses to add a relay device to deal with a localization problem in
the room where device 11 (an anchor) is placed.
In this area, the tracked device has trouble getting synchronized with the root device because of a white obstacle,
shown by the left side of the black arrow in Figure 3. Adding a relay device role to anchor 11 can solve this
issue as the tracked device automatically searches for the best beacon available for synchronization. Device 11 is
configured as shown in Figure 3:
• UWB Type: Beacon
• Beacon Id: 1
Sub-cells
In cases where the area to cover is very large and so all the devices cannot get synchronized with the root device,
sub-cells can be created to extend the range. Each sub-cell is managed by a relay device and all the devices of
the sub-cell are synchronized with it, as shown in Figure 4.
Additional information is available from the documents listed in References. All documents may be updated
without notice to individual users beforehand.
For up-to-date support or information about standardized as well as customized solutions, refer to the UWB and
product pages on www.st.com, or to the nearest STMicroelectronics office.
Revision history
Contents
1 General information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2
2 Topology rules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3
3 Deployment examples . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4
4 Ask for support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .7
Revision history . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .8
Contents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .9
List of tables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .10
List of figures. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .11
List of tables
Table 1. List of acronyms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2
Table 2. One master cell without sub-cells topology . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4
Table 3. One master cell without sub-cells topology . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5
Table 4. One master cell without sub-cells topology . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6
Table 5. Document revision history . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8
List of figures
Figure 1. Overview on the star network topology . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1
Figure 2. Single master cell . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4
Figure 3. One master cell with relay device topology . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5
Figure 4. One master cell with sub-cells topology . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6