gprivat's profile - activity

Dear Iknur

These GEs were specified and named before we made major changes to the FIWARE architecture, leading to a clearer separation of the Edge and backend parts of FIWARE implementations (gateway was the initial name for a subset of what we now call edge). I consider both of them to be deprecated and their functions to be taken over by the new IDEC GE, of which Cepheus is an implementation. Highlighting Cepheus as an edge enabler should make its differentiation with Perseo clear enough. Perseo and Cepheus are both based on the Esper CEP core, but, as an edge enabler, IDEC/Cepheus does more than CEP.

I am not aware of such projects, but you might have a look on what has been done within the FINESCE project (www.finesce.eu) and the corresponding specific enablers We are interested in your further feedback about this Cordially

The LWM2M protocol implemented by IDAS supports OTA provisioning of devices, amont others

Sorry for the late answer I am not sure what you mean exactly because the implicit acceptation of device pairing would be between devices rather than between devices and users. What we have is the association between devices and entities in the sense used by FIWARE, and users can be such entities. But the description of such associations in the current version of NGSI is rather awkward and we are discussing how to change it in the evolution of NGSI. The associations process itself is not directly supported and has to be done manually, in the course of the configuration process

Hello sorry for the delay inresponding and thanks for your interest in FIWARE We need more information to answer your questions : which network protocols do your devices use? what kind of processing would you perform on your device data? do you require "hard" realtime (with strictly bounded latencies)?