Hi Dénes and All, I would like to ask the opinion of all the partners about this general issue of the Backend and Gateway architecture: since we are going to consider the gateway architecture as well, besides the backend (platform) architecture, is it better to maintain a symmetry between components at backend and at gateway level? Or can they be different? (I am referring to Dénes' point 2 in his attached e-mail). The reason behind this general question is the one already pointed out by Sabrina in her previous e-mail: the ETSI M2M architecture is very similar to what we are approaching with our work in this project. The reason of the ETSI M2M architecture is that the Device, Gateway and Network elements are functionally similar (of course they are different in relation to performances and reachability), all of them can host resources that can be accessed by applications both at local and network level (this is just an hint, I can be more precise in the ETSI M2M conference calls and workshop in the GA). We could, of course, adopt just the ETSI M2M reference points and not the architecture, but the ETSI M2M architecture has some good points too that maybe we can consider in our discussion since we moved from a simple platform architecture to a more complex architecture dealing with backend and gateway functionalities (by the way, we should consider also IoT compliant Devices besides IoT Gateways :)). What is your opinion? I can refine or change the current backend and platform FMC description only when this general issue has been addressed by all the partners involved, otherwise I can modify the architecture in a way that it is not shared by the others (these are the pros and cons of an un-moderated wiki :)) Ciao, Gian Piero Da: Bisztray, Denes (NSN - HU/Budapest) [mailto:denes.bisztray at nsn.com] Inviato: lunedì 16 gennaio 2012 11:42 A: Guerra Sabrina; fiware-iot at lists.fi-ware.eu Cc: Fici Gian Piero Oggetto: RE: [Fiware-iot] Feedback IoT Communication Architecture Hi All, My answers to the two topics you mentioned: 1. The Access Rights Control component is a bit controversial component. In the backend its functionalities is clear. However, in the Gateway, you already have a Access Policy Control within Data Access Policy GE. It would be good if we could clear what this one is responsible for, and what the one in the IoT Communication is responsible for. 2. I assumed that the Gateways are dealing with non-ETSI compliant devices. Thus, the service control GE as a central component does not have a sense. The reasons include that devices may connect in completely different manner, so QoS or Traffic Management may not be necessary. Do you think we need it there? Please take the initiative and change it as you prefer it. Best, Dénes From: ext Guerra Sabrina [mailto:sabrina.guerra at telecomitalia.it] Sent: Monday, January 16, 2012 11:07 AM To: Bisztray, Denes (NSN - HU/Budapest); 'fiware-iot at lists.fi-ware.eu' Cc: Fici Gian Piero Subject: R: [Fiware-iot] Feedback IoT Communication Architecture Hi All, we would like to discuss these generic aspects of the platform with you and to collect the your feedback about the following observations: we have seen that in the architecture on the Wiki there are asymmetries between the Backend and the Gateway diagram, in the case of IoT Communication. In the ETSI M2M Specifications there is a similar approach as the functionalities are distributed either to the platform level or to the gateway/device level but in the ETSI M2M the functionalities are symmetries. We would know if this difference between the backend/platform and the gateway architecture is shared and which are the reasons of this choice. For example the "Service Control" GE is only identified in the backend diagram and not in the gateway diagram. An other example: the "Access Rights Control" component is only identified in the gateway diagram and not in the backend diagram. Best regards, Sabrina 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 01CCD45B.F28A3CC0]Rispetta l'ambiente. Non stampare questa mail se non è necessario. 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:00000000000000000000000000000001 at TI.Disclaimer]Rispetta l'ambiente. Non stampare questa mail se non è necessario. -------------- next part -------------- An HTML attachment was scrubbed... URL: <https://lists.fiware.org/private/old-fiware-iot/attachments/20120116/4a5090ff/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/20120116/4a5090ff/attachment.gif> -------------- next part -------------- A non-text attachment was scrubbed... Name: logo Ambiente_foglia.jpg Type: image/jpeg Size: 677 bytes Desc: logo Ambiente_foglia.jpg URL: <https://lists.fiware.org/private/old-fiware-iot/attachments/20120116/4a5090ff/attachment.jpg>
You can get more information about our cookies and privacy policies clicking on the following links: Privacy policy Cookies policy