-
Notifications
You must be signed in to change notification settings - Fork 16
Use cases
For the current implementation (all nodes with the same content)
These are cases in which the devices must access (read and/or write) data even when they are off-line.
Using biometry or cards (for people) or wireless and image recognition (for vehicles)
Having on the db (AergoLite):
- The allowed people / vehicles
- Records of their entrances and exits
It is a good example of an application in which the devices should work even when off-line. If the connectivity between then is down they can still access the table of allowed people or vehicles and record new accesses locally. When the connectivity is reestablished the node will synchronize its local database with its peers, all following node authorization with private key signing of transactions and consensus between the nodes on the final state of the database.
Good for schools, universities, organizations, public and private institutions. All that use more than one device for the access control.
This also includes access control on events/shows that take place far from the city. AergoLite could also be used on handheld devices used for reading tickets or bracelets.
The trucks, people and robots making delivery can be out of reach of connectivity but still require to store information about which products were delivered.
Maybe this use case requires the next version of AergoLite, with support for many thousands of devices.
Harvesters tracking information about themselves can share a common database and communicate just locally in the field (LoRa, WiFi, RF) without a central server.
Automated robots in agriculture can use the same.
Databases on ships and airplanes that must be synchronized to a central system for data analytics and reporting.
Drones making work on the field can synchronize their data between themselves instead of a central server.
Applications on mobile apps that should work even when off-line and require synchronization of data between them, but just for a private group of allowed users/devices.
Those who accept cash and coins can work off-line. The collected data can be shared between themselves and them synchronized to a central db for reports.
They must work even when off-line, and they must track how much energy was served.
Always measuring, even when off-line. Then they need to share its measurements with the company.
Must work when off-line. The data can be collected on the company for analytics.
Search more cases for:
- Energy
- Food
- Health
- Transportation (incl. public), logistics and delivery
- Supply chain
- Security
- Education
- Industry (automation)
- Mobile Apps