[Fiware-iot] New picture whole IoT Architecture

[Tobias Jacobs]

Hi Carsten,

Thanks a lot for the link and the explanations!

>From reading the descriptions I come to the conclusion that from the IoT Broker perspective the TH is an application (data consumer) retrieving for data.

Does it also serve as a data provider? So does it e.g. register its templates as entities in the Config Management, so that the IoT Broker GE would request data from the TH when applications ask for it?

Best
Tobias

From: Magerkurth, Carsten [mailto:carsten.magerkurth at sap.com]
Sent: Dienstag, 28. Januar 2014 09:08
To: Tobias Jacobs; thierry.nagellen at orange.com; fiware-iot at lists.fi-ware.eu
Subject: RE: [Fiware-iot] New picture whole IoT Architecture

Hi Tobias,

yes, as I said, an application using the Template Handler (not the TH itself) will need to interact with the other components. The TH will subscribe to events (subscribeContextRequest) in order to be notified of sensor readings (notifyContextRequest). The respective flow chart and some description is here:

https://forge.fi-ware.eu/plugins/mediawiki/wiki/fi-ware-private/index.php/Backend_Template_Handler_-_User_and_Programmers_Guide

best regards,
Carsten

From: Tobias Jacobs [mailto:Tobias.Jacobs at neclab.eu]
Sent: Montag, 27. Januar 2014 09:10
To: Magerkurth, Carsten; thierry.nagellen at orange.com<mailto:thierry.nagellen at orange.com>; fiware-iot at lists.fi-ware.eu<mailto:fiware-iot at lists.fi-ware.eu>
Subject: RE: [Fiware-iot] New picture whole IoT Architecture

Hi Carsten,

Are there already flow charts and/or examples showing how the Template Handler interacts with the other components?

Best
Tobias

From: Magerkurth, Carsten [mailto:carsten.magerkurth at sap.com]
Sent: Montag, 27. Januar 2014 08:53
To: Tobias Jacobs; thierry.nagellen at orange.com<mailto:thierry.nagellen at orange.com>; fiware-iot at lists.fi-ware.eu<mailto:fiware-iot at lists.fi-ware.eu>
Subject: RE: [Fiware-iot] New picture whole IoT Architecture

Hi Tobias, hi all,

the Template Handler needs to be provided with the entities, i.e. it will not query the Conf Man actively, but wait for an NGSI start event. This is, however, I believe not necessarily a problem in the architectural picture, as the relationships between the components are not directed anyway. That means, an application using the Template Handler will need to interact with the other components in order to be able to build the appropriate start event for the Template Handler.

Best regards,
Carsten

From: fiware-iot-bounces at lists.fi-ware.eu<mailto:fiware-iot-bounces at lists.fi-ware.eu> [mailto:fiware-iot-bounces at lists.fi-ware.eu] On Behalf Of Tobias Jacobs
Sent: Freitag, 24. Januar 2014 16:31
To: thierry.nagellen at orange.com<mailto:thierry.nagellen at orange.com>; fiware-iot at lists.fi-ware.eu<mailto:fiware-iot at lists.fi-ware.eu>
Subject: Re: [Fiware-iot] New picture whole IoT Architecture

Hi Thierry, all,

It is a bit unclear to me how the Template Handler interacts with the GEs it is connected to (Context Broker, IoT Broker, Conf. Man., Be Device Man.).
Can someone clarify?

Thanks & best regards
Tobias

From: fiware-iot-bounces at lists.fi-ware.eu<mailto:fiware-iot-bounces at lists.fi-ware.eu> [mailto:fiware-iot-bounces at lists.fi-ware.eu] On Behalf Of thierry.nagellen at orange.com<mailto:thierry.nagellen at orange.com>
Sent: Donnerstag, 23. Januar 2014 16:38
To: fiware-iot at lists.fi-ware.eu<mailto:fiware-iot at lists.fi-ware.eu>
Subject: [Fiware-iot] New picture whole IoT Architecture

Hi All,

Here is the new picture for the whole IoT architecture including some previous changes and Template Handler. Please check and comment if anything seems unclear or wrong.

BR
Thierry

_________________________________________________________________________________________________________________________



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,

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, 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-iot/attachments/20140128/cb6fbbc9/attachment.html>