[Fiware-data] CEP<->P/S

[fano.ramparany at orange.com]

Hi Boris and all,

My feedback in line below.

De : Moltchanov Boris [mailto:boris.moltchanov at telecomitalia.it]

Objet : RE: [Fiware-data] CEP<->P/S
...
It seems to be so simple that I’m not sure whether we need that sort of schema (two components exchanging info CEP<->P/S where CEP is containing the reasoning event logic and P/S is connected to its providers and to subscribed applications).
[FR]  As simple as it could be, that schema would make explicit the type of data those two components would exchange and which protocol they would use to exchange this information.  In the simplest case, as you suggest the protocol would be OMA NGSI for CEP to connect to P/S. A decision has then to be made on how the P/S will connect to CEP. Still in the simplest case, the data to be exchanged between the two components are event descriptions in both direction. In which case, as you suggest a convention has to be decided on how data about “entity” in the P/S event description should be converted in the CEP event description and on how data about “entity” should be retrieved from CEP events description.
Unless we know all this type of information, It is not easy for Carlos to evaluate the amount of work required nor identify who can do the job.


From: fano.ramparany at orange.com [mailto:fano.ramparany at orange.com]
Sent: Monday, February 18, 2013 4:11 PM
To: Moltchanov Boris; fermin at tid.es; fiware-data at lists.fi-ware.eu
Cc: BELLABAS Alia OLNC/OLPS
Subject: RE: [Fiware-data] CEP<->P/S

Dear all,

Determining the respective roles of the CEP and P/S in the overall architecture is very important and will dictate what additional components need to be implemented.
In the discussion so far, it is considered that P/S is an event source that feeds the CEP with events, which I think is fine. I think that conversely the CEP should be a context provider for the P/S. Because if an application would like a pattern of events to be detected such as in the case of OUTSMART UC “a street lamp is not switched on whereas it is dusk”, it should subscribe to the P/S. The simplest scenario I foresee is that the CEP create an event which corresponds to this situation (this pattern of events) as soon as is occurrs and push it towards the P/S.  The application would then be notified, provided that it has subscribed to this event.

More generally, could we draw the overall architecture depicting the GEs and the dataflow they exchange? It will then be clearer for UC projects, how they can use the GE involved.

Best regards,

Fano


De : fiware-data-bounces at lists.fi-ware.eu<mailto:fiware-data-bounces at lists.fi-ware.eu> [mailto:fiware-data-bounces at lists.fi-ware.eu] De la part de Moltchanov Boris
Envoyé : vendredi 15 février 2013 07:18
À : fermin at tid.es<mailto:fermin at tid.es>; fiware-data at lists.fi-ware.eu<mailto:fiware-data at lists.fi-ware.eu>
Objet : Re: [Fiware-data] CEP<->P/S

yes, P/S NGSI.

BR,
B


Отправлено с Samsung Mobile

Fermín Galán Márquez <fermin at tid.es<mailto:fermin at tid.es>> написал:
Dear Boris,

I have two doubts regarding this topic:

  *   Is the interface exposed by CEP documented in some place (e.g. URL in the FIWARE wiki)?
  *   I understand you are considering NGSI as the interface exposed by P/S, right?

Thanks!

Best regards,

------
Fermín

El 14/02/2013 17:57, Moltchanov Boris escribió:
Dear All,

The conclusion after our AC would be that, as WP6, we need an intermediate component (converter, middleware, platform) performing the following functions between the CEP and P/S GEs:
-          Subscribe the P/S only for needed data/scope/entityIDs.
-          Enrich events containing the data, becoming the context, with entityIDs and scopes taken from events attribute;
-          Parse the context, becoming the events, and build the events integrating into the event structure the entityID and scopes as the attributes for feeding the CEP with the event coming from context P/S flow;
-          Converting JSON2XML and vice versa XML2JSON. This piece could be used also for other components , GEs, etc. in FI-WARE and UCPs.
Then, given the application (UCP or generically application domain) the P/S will be subscribed only to that context, which is relevant for the event generation for that UCP, or generally speaking application domain, by the CEP.

Best Regards,
Boris
Questo messaggio e i suoi allegati sono indirizzati esclusivamente alle persone indicate. La diffusione, copia o qualsiasi altra azione derivante dalla conoscenza di queste informazioni sono rigorosamente vietate. Qualora abbiate ricevuto questo documento per errore siete cortesemente pregati di darne immediata comunicazione al mittente e di provvedere alla sua distruzione, Grazie.

This e-mail and any attachments is confidential and may contain privileged information intended for the addressee(s) only. Dissemination, copying, printing or use by anybody else is unauthorised. If you are not the intended recipient, please delete this message and any attachments and advise the sender by return e-mail, Thanks.
[rispetta l'ambiente]Rispetta l'ambiente. Non stampare questa mail se non è necessario.



_______________________________________________

Fiware-data mailing list

Fiware-data at lists.fi-ware.eu<mailto:Fiware-data at lists.fi-ware.eu>

http://lists.fi-ware.eu/listinfo/fiware-data

________________________________

Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra política de envío y recepción de correo electrónico en el enlace situado más abajo.
This message is intended exclusively for its addressee. We only send and receive email on the basis of the terms set out at:
http://www.tid.es/ES/PAGINAS/disclaimer.aspx

_________________________________________________________________________________________________________________________



Ce message et ses pieces jointes peuvent contenir des informations confidentielles ou privilegiees et ne doivent donc

pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce message par erreur, veuillez le signaler

a l'expediteur et le detruire ainsi que les pieces jointes. Les messages electroniques etant susceptibles d'alteration,

France Telecom - Orange decline toute responsabilite si ce message a ete altere, deforme ou falsifie. Merci.



This message and its attachments may contain confidential or privileged information that may be protected by law;

they should not be distributed, used or copied without authorisation.

If you have received this email in error, please notify the sender and delete this message and its attachments.

As emails may be altered, France Telecom - Orange is not liable for messages that have been modified, changed or falsified.

Thank you.

_________________________________________________________________________________________________________________________

Ce message et ses pieces jointes peuvent contenir des informations confidentielles ou privilegiees et ne doivent donc
pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce message par erreur, veuillez le signaler
a l'expediteur et le detruire ainsi que les pieces jointes. Les messages electroniques etant susceptibles d'alteration,
France Telecom - Orange decline toute responsabilite si ce message a ete altere, deforme ou falsifie. Merci.

This message and its attachments may contain confidential or privileged information that may be protected by law;
they should not be distributed, used or copied without authorisation.
If you have received this email in error, please notify the sender and delete this message and its attachments.
As emails may be altered, France Telecom - Orange is not liable for messages that have been modified, changed or falsified.
Thank you.

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.fiware.org/private/old-fiware-data/attachments/20130218/1e2ea7c6/attachment.html>