Trillbit proprietary technology encodes any data into a series of sound frequencies. This encoded data gets played by a sending device by their speaker in form of Trill tones, over the air, to a receiving device where it is received by microphone and decoded by Trillbit SDK.
1. We do not need extra chip or special hardware.
2. We are cross -OS. cross -platform solution.
3. We are more secure and truly contactless and can work from a distance.
See the comparison diagram for more details
Extremely secure if needed. Trill acts as the Transportation layer same as TCP does in the internet stack. Our technology gets the data from one device to another device but does not itself directly implement security measures.
Security protocol are imposed on top of our Transport Layer so that they are in place as the data is passed to Trillbit SDK for transmission. Importantly, this means that Trillbit does not have knowledge of any customer data or transaction details or security protocol implemented by customers' applications. Customers can effectively add any type of encryption, tokenisation or other security protocols required before transmission.
We work in the harshest of environments. Even where ambient sound levels exceed 100DB (sports stadium noise). Our powerful noise filter algorithm works like a charm and makes Trill technology ultra-reliable.
Trillbit main protocol is ultrasonic. However, we do provide both audible and inaudible (ultrasonic) audio protocols across our full product suite for situations in which an audible protocol would be more desired.
The range of sound is a function of volume. The Rule of thumb is if you can hear the sound, Trillbit can transmit the data. The typical use cases where Trillbit SDK is being used require a reliable range of 0-15 ft. However, we have successfully transmitted data bits over longer distances on the order of a few hundred feet in a live sports stadium environment.
Our SDK is currently available as a suite of cross-platform, interoperable SDKs including iOS, Mac OS, Android, Windows, JavaScript, Web Browsers, Python, Arduino, Raspberry Pi, and Linux. We can also develop custom SDKs and bespoke protocols for client’s specific requirements if needed.
No. Trillbit works across OS and platform. Any device with a speaker can play a trill tone and almost all devices with a microphone and a small amount of processing power can receive and decode it.
No. Trillbit works across OS and platform. Any device with a speaker can play a trill tone and almost all devices with a microphone and a small amount of processing power can receive and decode it.
No, Trillbit SDK does not record and store audio. Firstly, Trillbit SDK uses bandpass filters around the Trill tone frequencies (19kHZ) and all other frequencies including voice get rejected. Secondly, a temporary audio buffer is assigned to decode the Trill Tone, and this temporary buffer gets overwritten and is never stored.
Theoretical range of human hearing is 20-20000 HZ but most of the humans cannot hear the tone above 16 kHZ and Trillbit operate around 19 kHZ. Barring exceptions we are inaudible to humans. Some animals can hear the tone, however, it is very faint and completely safe for them.
