The key component is the sensor. The sensor uses a Doppler Effect sensor and has a metering range from 2-300cm with ± 2 cm accuracy. It is powered by 2 x 3V type D disposable batteries which under normal use (3 measurements per day) can last up to 5 years. It features IP67/NEMA 6 certification and its enclosure is made by high density polyethylene.
It sends data via GPRS/EDGE protocol using TCP/IP and weights 450gr approximately and is attachable either by a single screw and / or adhesive material.
Optionally, RFIDs are placed on the bins so that the collection of each bin is identified as a single event for reporting purposes. The RFID tags are accompanied by:
An RFID tag reader
both installed inside the bin collection vehicle.
The RFID reader sends the data to the tablet which acts as a router in order to forward the data to the server. This infrastructure is optional since the server can estimate the bin collection timestamp in order to produce statistics and reports. Although this method is quite accurate, it can produce false collection timestamp so for clients require nothing less than 100% accuracy in their reports, using our RFID is the way to go.
Standards and technologies
Binalive nuts and bolts are based on standard frameworks and protocols so that they are futureproof, scalable and easy to evolve and upgrade.
The backend server exposes its functionality through a number of REST APIs. The frontend end server, is essentially an implementation of a REST API client using API of the appropriate application. Each customer has its own ‘application’ which is bound to specific resources. When logging in, he manages the resources and their metadata of his application. The apparent competitive advantage of our approach is that if a client wishes to develop his own, custom user interface, he is free to use our API. In addition, we can provide extensions for interfacing with any 3rd party system it provides some sort of API such as REST, SOAP, COM, .NET.
In order to allow for any number of sensors to send data to the server, MQTT protocol was chosen. MQTT is a lightweight protocol while the MQTT broker which dispenses messages from sensors to server and vice versa, allows the handling of tens of thousands of messages per second. This practically means that hundreds of thousands of sensors can be supported at any given time. MQTT is the industry standard protocol for the Internet of Things era and hence fully supported by Binalive.
Binalive is based on a general purpose telemetry middleware, Motesense. Motesense provides an API on top of which custom applications are built such as Binalive. The functionality of both Motesense and Binalive is exposed through distinct REST APIs.
A gateway exists between the device and the Motesense platform in order to relay data from device – specific protocol to Motesense API through the REST API
The overall approach dramatically accelerates custom application development compared to conventional methods