[Fiware-iot] IoT Communication Architecture picture

[thierry.nagellen at orange-ftgroup.com]

Hi Ricardo
 
Your picture and your text are too much related to the IDAS platform but it was what we agreed last week to initiate this work. Now we have to align both with IoT Service Enablement chapter regarding glossary we validated last telco and the 4 generic enablers or tasks.
 
Of course this is relevant for the next step to analyse how some assets should cover some functionalities of IoT chapter and each of us will have to do the same exercise in the following weeks. But for this first version of the deliverable we have to deliver a clear picture for our "customers" regarding the 4 GE (Communication, Resources management, Process automation & Data Handling)
 
We have defined a kind of hierarchy from devices to IoT resrouces and Things and typically for configuration and management, they will not required the same features. This is also a point for IoT Communication to explain how we can configure some connectivity parameters for devices.
In the same way, we have a block "Naming" in IoT Communication but I think that to manage correctly unequivocal names for things, a kind of naming resolution should appear in IoT Resources Management.
 
So we have now to work on this consistency between the different pictures and maintain also this consistency with the DoW and previous description of the tasks.
 
BR
 
Thierry

________________________________

De : fiware-iot-bounces at lists.fi-ware.eu [mailto:fiware-iot-bounces at lists.fi-ware.eu] De la part de Farkas, Lorant (NSN - HU/Budapest)
Envoyé : vendredi 3 juin 2011 14:09
À : ext Ricardo de las Heras; fiware-iot at lists.fi-ware.eu
Objet : 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. 

 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
	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
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/20110605/8261beca/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: ATT157680.jpg
Type: image/jpeg
Size: 677 bytes
Desc: ATT157680.jpg
URL: <https://lists.fiware.org/private/old-fiware-iot/attachments/20110605/8261beca/attachment.jpg>