Be-Bound

The Be-Bound Developer Hub

Welcome to the Be-Bound developer hub. You'll find comprehensive guides and documentation to help you start working with Be-Bound as quickly as possible, as well as support if you get stuck. Let's jump right in!

Get Started    

Protocols

Be-Bound Technology abstracts different transfer protocols in an innovative and network agnostic layer, simplifying its usage and adding unique benefits. This article aims to explain:

  • The underlying standard protocols on which Be-Bound Technology is based.
  • Be-Bound Protocol, the technology which makes possible network agnostic and seamless communications.

Standard Protocols

Be-Bound Technology support the newest and most lightweight transport protocols available on the market. By default, Be-Bound Technology supports MQTT, HTTP/1.1 and HTTP/2. Additional communication protocols could be supported based on our customers needs.

Be-Bound protocols versus regular HTTP communications

Be-Bound protocols versus regular HTTP communications

By default, Be-Bound Technology uses the MQTT (Message Queuing Telemetry Transport) protocol (See more information here), to ensure efficient, reliable and lightweight communications.

Advantages

  • Less data to send, hence less energy needed.
  • Increase the device‚Äôs battery life.
  • Faster and more reliable communications.
  • Augmented network connectivity and capacity.
  • Business continuity under harsh or limited network conditions.

Be-Bound Protocol

Be-Bound Technology relies on a network agnostic communication protocol that enables the efficient, reliable and secure transfer of messages across various networks (e.g. 2G/SMS, gprs, WiFi, 3/4G, etc.) and transport protocols (e.g. HTTP, MQTT, etc.), as shown in the below figure.

Be-Bound Network Agnostic Protocol

Be-Bound Network Agnostic Protocol

Advantages

  • Data fragmentation: your transmitted data is split into packets according to the maximum transmit unit (MTU) of the underlying networks (e.g. 12 bytes for LoRa, 140 bytes for SMS, etc.).
  • Data acknowledgement: each delivered packet is acknowledged by the Be-Bound Network (positive or negative ACK mechanisms).
  • Data retransmission: each lost packet is detected, and retransmitted, eventually through another network.
  • Data ordering and Reassembly: received packets are reordered and reassembled, and your data is delivered to your connected services or apps.

Protocols


Suggested Edits are limited on API Reference Pages

You can only suggest edits to Markdown body content, but not to the API spec.