Technology
Can I use LEAPS to navigate and track nodes at the same time?
Yes, most network profiles allow multiple modes of location service. Depending on the selected network profile, the Tag’s position can be used in both navigation and tracking modes at the same time. The data are available via on-module and server API.
Please see the System Performance comparison for more details.
How many Anchors and Tags a LEAPS network can have?
The network stack is designed in the way that it always aims to reuse the air-time using an effective mechanism for both Anchors and Tags. In short, if a condition attenuates the signal of any transmitting node in a way that will not negatively influence transmission and reception by any other node then that air-time can be reused.
This allows virtually unlimited amount of nodes to be deployed in a spread area where this condition can be created. All of this happens automatically using effective mechanisms implemented in LEAPS.
What location techniques are supported in LEAPS?
LEAPS supports various locating techniques, including
TWR - Two-Way Ranging
UL-TDoA - Uplink Time Difference of Arrival
DL-TDoA - DownLink Time Difference of Arrival
Versatility makes it easy to balance the system requirements, costs, deployment time and maintenance complexity. Applications range from simple distance proximity, to high-speed tracking or navigation of an unlimited amount of receivers.
Can I send and receive user data on the edge nodes using LEAPS?
The Anchors and Tags can send and/or receive user data depending on the selected network profile.
Data sent from the Module toward the Server is called Uplink.
Data sent from the Server toward the Module is called Downlink.
Please see the System Performance comparison for more details.
How can I configure, receive and send data using a node?
LEAPS modules can be configured, and data can be handled using the following APIs
Bluetooth - New API over encrypted channel helps to handle data fragmentation commonly experienced on Bluetooth properly. The API is in TLV format andt supports the same command set used for UART, SPI and USB (in the future).
UART - TLV binary format
SPI - TLV binary format
USB - TLV binary format (in the future)
Shell over UART - Debug shell in human-readable format
Does LEAPS support wireless Ultra-wideband backhaul?
The system can support wireless Ultra-wideband backhaul depending on the selected network profile. The location and user data can be sent toward the Server and the nodes using Ultra-wideband radio.
There are two types of backhaul supported:
Non-routing UWB backhaul - This is a one-hop backhaul where a bridge-enabled device can forward the data between a Server over Ethernet and a node over UWB.
Routing UWB backhaul - This is a multi-hop backhaul where a bridge-enabled device can forward the data between a Server on Ethernet and a node on UWB. Other infrastructure devices can participate in forwarding the data with other nodes via UWB. Routing mechanism is fully automated and adaptive to the changes in the network.
Where the location and user uplink data are available?
The backhaul uplink location and user data are available via these APIs
Bluetooth - TLV binary format
UART - TLV binary format (limited data throughput)
SPI - TLV binary format
Data Server - MQTT protocol
What are the downlink events and commands?
They are service commands and events providing the following services via the Data Server.
Collection of the signal map between the Anchors - can be used for installation and debuggingg purpose.
Collection of distances between the Anchors - can be used for auto-positioning of the Anchors.
Remote control of GPIOs on the module.
and more.
How does security in LEAPS work?
The following security mechanisms are implemented in LEAPS
Secure key storage - the root of trust using hardware secure element.
Secure boot - to guarantee the consistency of the firmware.
Node authentication - nodes on the network are authorized using asymmetric authentication. The client’s key set is possible.
Key exchange - the network key is exchanged securely and automatically between the authorized nodes.
Node sign-up - Only authorized nodes can connect to the network when enabled.
Node access revoke - revoke access for nodes already connected to the network.
Encryption for UWB and Bluetooth communication - data frames sent via UWB and Bluetooth communication are encrypted using AES-128.
Data encryption is resistant against to attacks
Frame replay
Unauthorized nodes
Length extension attack
Data extraction when the AES cipher block repeats
Power interruption
DoS
A unique way to generate entropy uses network synchronicity which makes it very difficult to apply an attack even if the key is stolen.
Highly optimized for embedded modules with memory constraints.
Low data overhead being sent over UWB.
Changes in infrastructure detection - helps to detect when the infrastructure nodes have been moved.
Whole chain security - data are all protected from the input point until the output interface of the last component.
All communication via TCP/IP uses TLS 1.2.
The system should undergo penetration test in the future.
Is it possible to send data between the Anchors/Tags and the server?
Yes, depending on the profile, it is possible to send data from the Anchors or Tags to the LEAPS Server. There are two types of data.
Uplink - data from the Anchors and Tags to the LEAPS Server.
Downlink - data from the LEAPS Server to the Anchors or Tags.
Can I use the unused GPIOs on the module?
Yes, there are GPIOs available for your applications. They can be controlled via API - UART, SPI or MQTT.
What API interfaces are available?
LEAPS modules can be configured, and data can be handled using the following APIs
Bluetooth - New API over encrypted channel helps to handle data fragmentation commonly experienced on Bluetooth properly. The API is in TLV format and supports the same command set as used for UART, SPI and USB (in the future).
UART - TLV binary format
SPI - TLV binary format
USB - TLV binary format (in the future)
Shell over UART - Debug shell in human-readable format
What does LEAPS profile mean, and how is it unique from variant?
Variant is a pricing model. LEAPS modules are offered in 3 variants with different sets of supported networking profiles. The users can choose what would best fit their applications and budgets.
Profile is how the network protocol is organized. Each profile is designed to provide optimal performance for a specific type of applications. Depending on the variant, one or several profiles are supported. The user has to select the profile which best fits the application.
Is it possible to obtain the Tag Node (TN) position as well as the distances from all interfaces?
There is a difference in obtaining these values from Supported Interfaces:
Via BLE, UART, USB, or SPI, the user can obtain both the TN’s position and the distances.
Via MQTT, only the position is available.
How to achieve the longest possible range between 2 devices?
This has some relation to the Fresnel zones. Long time ago we have done some measurements in about 1.2m - 1.5m height the signal gets lost at some distance and then comes back after 5-10 m for a while. Then we realize the Fresnel zones and increased the height to 2m and since then we don’t observe this issues anymore.
For most radio signals you should take care only about 1st Fresnel zone, but for UWB it seems that also other zones are important.
Practical example:
Distance between antennas = 100m
Frequency = 6.5GHz
1st zone radius = 1.07m
2st zone radius = 1.52m
3st zone radius = 1.86m
Distance between antennas = 200m
Frequency = 6.5GHz
1st zone radius = 1.52m
2st zone radius = 2.15m
3st zone radius = 2.63m
Online calculator is here Fresnel Zone Calculator