Sorry for the length excerpts below, it took me a bit of reading to get my head around this. This is article talks about how to handle data coming from edge devices, and claims there are two models.The “Pass Thru” model just filters the data around rules and passes what is appropriate; the “REST” model sucks all the data in to the vendor’s cloud and then presents an API to access that data.
The idea is that there is a [Application Enablement Platform (AEP)] made up of an edge agent on one side and cloud storage and API servers on the other. The small device side agent is placed on an IoT edge device…. That edge agent exposes an application level API to the IoT application itself and it hides the “complexity” of the cloud protocol from the application. In this manner it simplifies the edge device on-boarding and the secure sending of data from the edge device to the AEP cloud platform.
On the cloud side the AEP’s have two main data handling strategies: “Pass thru” and “at Rest”.
In the “pass thru” model the AEP is an intelligent pipe that is in essence a smart 2-way filter and applies rules as to when to actually transport the data from the edge device to the customer’s back-end and back. For example in the pass-thru model one could tell the AEP to pass temperature readings to an gas tank monitoring service only if the temperature exceeds 32 degrees C two times in a row and in this case to also configure the edge device accept a command to activate a cooling mechanism originating from the customer’s back-end. This allows a service provider to take an edge device and quickly integrate new business logic on top of an existing back-end and implement an over the top IoT solution.
The second data handling strategy is the “at REST” strategy. In this case the customer’s edge devices do not send the data directly to the customer’s back-end, rather they send them to the AEP cloud. The AEP stores all the customer’s data and handles all issues of scale, secure transmission and data storage. The AEP in turn exposes a set of web service APIs on top of which the customer back-end application can be built.