Details
-
Type:
extRequest
-
Status: Closed
-
Priority:
Major
-
Resolution: Done
-
Component/s: FI-C3
-
Labels:None
-
Sender Email:
Description
Dear Sanawar
CEPHEUS has indeed 2 components : a lightweight broker and a Esper based complexe event processing (CEP - kind of rule engine)
It is intended to be run on the gateway side. A typical use case is to do some local processing on the gateway side:
You connect several devices to the gateway. They connect to the local context broker and the local CEP can generate new events based on some rules you defined (threshold detection based on sensors value average, etc …). Doing so allows you to bring some intelligence on the edge and offload your connectivity between gateway and cloud.
Cepheus can be runs on a standard raspberry
If unclear, we may provide some demos.
Kind regards
Franck
De : Sanawar Syed Azor Ali sanawar.syed@m4ke.it
Envoyé : mercredi 1 juin 2016 11:58
À : Franck Le Gall <franck.le-gall@eglobalmark.com>
Cc : Alexis Bedoret <alexis.bedoret@m4ke.it>; Johnny Waterschoot <johnny.waterschoot@iminds.be>
Objet : Helpilepsy // Need advice on cepheus.
Hi Franck,
I hope you are doing well.
We are having some trouble understanding correctly the benefits of the cepheus GE (http://catalogue.fiware.org/enablers/iot-data-edge-consolidation-ge-cepheus).
From what we understood, it is used in order to have a correct communication protocol (NGSI) between the “things” and the context broker for example but we already use a middleware backend where we already set up the communication protocol.
Can you provide more insight on this with a proper use-case example ?
Thank you very much for your help.
Best regards,
[logo-mail]
Sanawar Syed
Operating Partner
site web
email
phone
www.m4ke.it<http://www.m4ke.it>
sanawar.syed@m4ke.it<sanawar.syed@m4ke.it>
+32 (0) 484 74 04 44<phone:0484740444>
Since January 1st, old domains won't be supported and messages sent to any domain different to @lists.fiware.org will be lost.
Please, send your messages using the new domain (Fiware-fic3-coaching@lists.fiware.org) instead of the old one.
_______________________________________________
Fiware-fic3-coaching mailing list
Fiware-fic3-coaching@lists.fiware.org
https://lists.fiware.org/listinfo/fiware-fic3-coaching
Comment by sanawar.syed@m4ke.it :
Hi Franck,
Thank you for the information. We understand better in which case this GEs could be useful.
Unfortunately, I don’t think this GE can be use in our solution because the device sends directly the data to the internet without any gateway (directly with LORA)
Could you send the demo anyway ? It could still be useful for another project of ours.
Thank you very much.
Sanawar Syed
Operating Partner
site web
>
email
phone www.m4ke.it <http://www.m4ke.it/>
sanawar.syed@m4ke.it <sanawar.syed@m4ke.it
+32 (0) 484 74 04 44 <phone:0484740444>
> On 01 Jun 2016, at 15:42, Franck Le Gall <franck.le-gall@eglobalmark.com> wrote:
>
>
> Dear Sanawar
>
> CEPHEUS has indeed 2 components : a lightweight broker and a Esper based complexe event processing (CEP - kind of rule engine)
>
> It is intended to be run on the gateway side. A typical use case is to do some local processing on the gateway side:
>
> You connect several devices to the gateway. They connect to the local context broker and the local CEP can generate new events based on some rules you defined (threshold detection based on sensors value average, etc …). Doing so allows you to bring some intelligence on the edge and offload your connectivity between gateway and cloud.
> Cepheus can be runs on a standard raspberry
>
> If unclear, we may provide some demos.
>
> Kind regards
> Franck
>
>
> De : Sanawar Syed Azor Ali sanawar.syed@m4ke.it
> Envoyé : mercredi 1 juin 2016 11:58
> À : Franck Le Gall <franck.le-gall@eglobalmark.com>
> Cc : Alexis Bedoret <alexis.bedoret@m4ke.it>; Johnny Waterschoot <johnny.waterschoot@iminds.be>
> Objet : Helpilepsy // Need advice on cepheus.
>
> Hi Franck,
>
> I hope you are doing well.
>
> We are having some trouble understanding correctly the benefits of the cepheus GE (http://catalogue.fiware.org/enablers/iot-data-edge-consolidation-ge-cepheus <http://catalogue.fiware.org/enablers/iot-data-edge-consolidation-ge-cepheus>).
>
> From what we understood, it is used in order to have a correct communication protocol (NGSI) between the “things” and the context broker for example but we already use a middleware backend where we already set up the communication protocol.
>
> Can you provide more insight on this with a proper use-case example ?
>
> Thank you very much for your help.
>
> Best regards,
>
>
> Sanawar Syed
> Operating Partner
>
> site web
> email
> phone
> www.m4ke.it <http://www.m4ke.it/>
> sanawar.syed@m4ke.it <sanawar.syed@m4ke.it
> +32 (0) 484 74 04 44 <phone:0484740444>
Since January 1st, old domains won't be supported and messages sent to any domain different to @lists.fiware.org will be lost.
Please, send your messages using the new domain (Fiware-fic3-coaching@lists.fiware.org) instead of the old one.