Get started
In this documentation you will find all data necessary to understand AirTrace architecture and make the best out of it.
Architecture
The current architecture of our AirTrace is shown next. As the project evolves, the architecture will progressively have modifictions in its structure. They will all be shown here. In the following figure, a diagram of the last version of the architecture is presented:
As we can see in the illustration above, different clients connect to the platform thanks to the middleware we prepare. Alternatively, clients can connect through other SaaS platforms that will make use of AirTrace API to performe the same operations (left and right branches).
Then, the party begins, depending on the type of processing that data goes through. Le us have a full description in next subsection.
Description
Depending on the type of service the end-client wishes to implement, there are two available options:
Direct submission: the cumulate set of readings will be submitted and stored in Blockchain..
Data quality characterization: including submissions to the blockchain, data will also be part of a data quality quantification in which, thanks to the available AI (artificial intelligence) models available in ADOS (AirTrace Decentralized Oracle System), the end-client will have the chance to insert data in the blockchain along with a value that gives insight on its reliability.
Currently, we are making use of iExec platform for automatic model inference and deployment, despite this is additionally under development. On the other hand, for the moment we make use of Ethereum and Polygon as our available Blockchain platform.
Last updated