Dear all, Although the asset selection is still questionably finished, it would good to clarify the architecture around the gateways as well as the internal APIs. 1. Where do we have the gateway functionality? (i.e. microDB, instantaneous and real-time data, data aggregation filter, etc. ) - every asset implements the gateway functionality on its own, and provides an API that the gateway-northbound interface and application implementation can harness. - the assets only do protocol adaptation, the gateway functionality comes from outside (possibly one of the assetes) 2. We need to provide two interfaces within a gateway. One is the ETSI M2M interface that communicates with the backend, and another interface for the application layer within the gateway. How will they communicate with the assets? 3. Backend API problems. The IDAS which seems to be selected for all GEs within resources management (is it?). It needs to have an internal interface for communicating with both the northbound and southbound interface. When will it be public? Or have a service bus? This one needs to be worked out. 4. Who implements the ETSI M2M interfaces? Best, Dénes -------------- next part -------------- A non-text attachment was scrubbed... Name: Gateway Architecture.pptx Type: application/octet-stream Size: 78645 bytes Desc: Gateway Architecture.pptx URL: <https://lists.fiware.org/private/old-fiware-iot/attachments/20111206/d6cc58c9/attachment.obj>
You can get more information about our cookies and privacy policies clicking on the following links: Privacy policy Cookies policy