[Fiware-iot] IoT Communication Architecture picture

[P.Barnaghi at surrey.ac.uk]

As Stefan said those are two different concepts; The diagram illustrates IoT Resource and Service enabler; perhaps the component should store Resource descriptions but if it is meant to support resource discovery (which I think it does) then EoI descriptions are also required.

One more comment: IoT resource Description is not a component; the component could include interfaces to publish and manage resource descriptions and also provide interfaces to access/use the resources; but resource description itself is only an information model.

Regards,
Payam



________________________________
From: fiware-iot-bounces at lists.fi-ware.eu [mailto:fiware-iot-bounces at lists.fi-ware.eu] On Behalf Of Haller, Stephan
Sent: 03 June 2011 13:23
To: Farkas, Lorant (NSN - HU/Budapest); ext Ricardo de las Heras; fiware-iot at lists.fi-ware.eu
Subject: Re: [Fiware-iot] IoT Communication Architecture picture

Well, IoT Resource and EoI are completely different things. I am not sure which one fits better here...

Regards,
-Stephan


From: fiware-iot-bounces at lists.fi-ware.eu [mailto:fiware-iot-bounces at lists.fi-ware.eu] On Behalf Of Farkas, Lorant (NSN - HU/Budapest)
Sent: Freitag, 3. Juni 2011 14:09
To: ext Ricardo de las Heras; fiware-iot at lists.fi-ware.eu
Subject: Re: [Fiware-iot] IoT Communication Architecture picture

Hi Ricardo,

We have the following comments/suggestions wrt the slide:
-EOI should be IoT resources
-Sensor description entity is IoT resource description entity
-Maybe entity should be replaced with component
-History storage - not clear, RM should not store anything
-Service protocol adaptor - this is clearly IoT communication
-Sensor tasking entity - not clear, maybe part of process automation
-Missing: the IoT resource configuration - now with the new version we actually understand this part is covered by the left hand side

FYI, we modified your 1st version, attached.
We will try to align our thinking based on the description you provide about the components.

Thanks & Br,

Lorant

________________________________
From: fiware-iot-bounces at lists.fi-ware.eu [mailto:fiware-iot-bounces at lists.fi-ware.eu] On Behalf Of ext Ricardo de las Heras
Sent: Friday, June 03, 2011 1:59 PM
To: 'fiware-iot at lists.fi-ware.eu'
Subject: Re: [Fiware-iot] IoT Communication Architecture picture
Dear all,

please find attached a refined version of the slide and a brief description of every module,

have a nice week-end,
best,
Ricardo.

Ricardo de las Heras wrote:
Hi Thierry, all,

please find attached the proposed architecture for T5.2 Rersource management.

I'll send you a brief description of every module by tomorrow, explaininig the realtionships as well,

comments are welcomed :)
best regards,
Ricardo.

Guerra Sabrina wrote:
Hi Thierry and all,
here it is the architecture picture for the IoT Communication.
I tried to stay on the same level of description as the Data Handling architecture, by describing the main elements and the relationships between them in the context of the other generic enablers and of the other Fi-Ware work packages.
Please feel free to send me any comments in order to have a better architecture for the next conf call.
Best regards,
Sabrina Guerra
__________________________________
Telecom Italia S.p.a.
Strategia e Innovazione,
Research & Trends

Telefono   +39 011 228 8359
Cellulare +39 331 600 1349
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.
[cid:image001.gif at 01CC21F4.F30C05D0]Rispetta l'ambiente. Non stampare questa mail se non è necessario.


--
-------------------------------------
Ricardo de las Heras
Research Project Manager
E-mail:<mailto:rheras at tid.es> rheras at tid.es<mailto:rheras at tid.es>
Phone1: (+34) 983 367625
Phone2: (+34) 91 1878107 + Ext:327
Telefónica I+D<http://www.tid.es>
-------------------------------------

--
-------------------------------------
Ricardo de las Heras
Research Project Manager
E-mail:<mailto:rheras at tid.es> rheras at tid.es<mailto:rheras at tid.es>
Phone1: (+34) 983 367625
Phone2: (+34) 91 1878107 + Ext:327
Telefónica I+D<http://www.tid.es>
-------------------------------------

________________________________
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/old-fiware-iot/attachments/20110603/c2220771/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image001.gif
Type: image/gif
Size: 677 bytes
Desc: image001.gif
URL: <https://lists.fiware.org/private/old-fiware-iot/attachments/20110603/c2220771/attachment.gif>