[Fiware-iot] IoT Architecture Discussion

[Bisztray, Denes (NSN - HU/Budapest)]

Dear Martin and Tobias,

 

Can you please upload this to the wiki?

 

Best,

Dénes

 

From: fiware-iot-bounces at lists.fi-ware.eu [mailto:fiware-iot-bounces at lists.fi-ware.eu] On Behalf Of ext Tobias Jacobs
Sent: Tuesday, February 14, 2012 1:53 PM
To: fiware-iot at lists.fi-ware.eu; jhierro at tid.es
Cc: Salvatore Longo
Subject: Re: [Fiware-iot] IoT Architecture Discussion

 

Dear Juanjo, dear all,

 

In order to reach a conclusion in our discussion about the role of the Thing-Level interface, we propose a slightly modified architecture picture, see appendix. The changes are

-          The component responsible for translating NGSI requests into resource requests and performing those requests on behalf of the application is now called "request handler". It resides in the "Thing-Level API".

-          The Observation Handler now resides in the Thing-Level API as well. This is because its functionality is complementary to the request handler and therefore should reside in the same GE. Another reason for moving the Observation Handler is that it deals both with data and with resources and therefore does fit into task 5.4 better than into 5.2.

-          The Publish/Subscribe Broker now resides on top of the whole backend. Its single point of contact to the IoT Backend is the Observation Handler, which publishes events into it.

We hope that we can come to a final agreement in tomorrow's phone conference.

 

Best regards
Martin and Tobias

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.fiware.org/private/old-fiware-iot/attachments/20120215/b0efe944/attachment.html>