[Fiware-espoo] Espo connection to FI-Lab meeting notes

[SERGIO GARCIA GOMEZ]

Hi again,
Some additional notes:

·         The Context Broker on its side can request the context information from Context Producers if they provide the ability to be queried (Context Producers able to act as servers are also referred as Context Providers). It’s somehow a terminology issue.

·         The protocol to be used is NGSI, and not ContextML.

·         The resulting application can be hosted in FI-Lab, but it can be also hosted somewhere else accessible from FI-Lab. Many GEs are open source and can be deployed anywhere, or use them “as a service” from FI-Lab.

Last but not least, take into account that the figure that I have sent shows an easy going architecture for the FI-Lab integration. If you build a full NGSI integration with a full fledge Context Broker, you would solve the two scenarios at once. Santiago, Jose Manuel, correct me if I’m wrong with this.

Best Regards,

Sergio.


From: SERGIO GARCIA GOMEZ
Sent: Thursday, February 27, 2014 18:11
To: fiware-espoo at lists.fi-ware.eu
Subject: Espo connection to FI-Lab meeting notes


Dear all,
I send some notes about this afternoon’s call. Find also below a diagram that depicts what I tried to explain about the integration through the Context Broker. I send also herewith some slides with pointers to the APIs and some integration examples.


·         We have two scenarios:

1.       First, in DoF VTT will develop a FI-WARE compliant context broker to connect DCA (and thus other districts sensor data) to VTT application layer.

2.       Second, VTT will publish Espoo data in FI-Lab and will develop a use case application in FI-Lab using that data and FI-WARE GEs.

·         Regarding scenario 2 (FI-Lab), VTT proposes two posibilities: to implement a context provider (that accepts queryContext Requests) or to implement a full NGSI context broker. This could be eventually used in DoF.

o   Telefonica explains that in order to create interesting applications, it is required to have updateContext notifications to publish automatically real time data from Espoo in FI-Lab, and not only on demand (queryContext).

§  AP: Sergio will send VTT’s slides modified to explain the messages exchange.

§  AP: Sergio will send a slides deck with references to the FI-WARE GEs and APIs.

o   All the data exposed in Espoo is dynamic but the info related to the buildings in the campus.

o   VTT do not have direct access to the sensors infrastructure and they receive the data through adaptors. Therefore, integrating through DCA doesn’t make much sense.

o   The public information of the campus is only related to the students hotel. The information about the other buildings is not open.

o   VTT proposes to develop an application that shows a dashboards with KPIs, historic information and some interesting insights (energetic efficiency, issues, users behavior…) that can be useful for the building operators. The analyzed information can include heating, water consumption, meteorological info, air quality (not from the campus)…

·         There are clear synergies between the two scenarios.

·         AP: VTT will send a short description and an effort estimation as soon as possible.

·         AP: VTT will send a detailed description of the integration and application to be implemented to be discussed next Thursday at 14.30h CET.

·         Telefonica team will check and provide some initial feedback about the proposal.



Best Regards,



Sergio.




[cid:image001.png at 01CF33E7.6FECB700]

--
Sergio Garcia Gomez
Telefonica Digital (TI+D)
FI-WARE [http://www.fi-ware.eu<http://www.fi-ware.eu/>]
Parque Tecnologico de Boecillo.
47151 Boecillo (Valladolid), SPAIN.
E-mail: sergg at tid.es<mailto:sergg at tid.es>
Phone: (+34) 9131.29098


________________________________

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
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.fiware.org/private/fiware-espoo/attachments/20140227/d59ab0fa/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image001.png
Type: image/png
Size: 47859 bytes
Desc: image001.png
URL: <https://lists.fiware.org/private/fiware-espoo/attachments/20140227/d59ab0fa/attachment.png>