Hi Denes, here are our answers to your questions. 1st group (There is absolutely no change compared to my initial sketch) Gateway Data Pooling - just added to the wiki Gateway Data Access Policy - we understood that in the Architecture Description for tomorrow we should include just what we will have in the April 2012 release, and we agreed with Ericsson that it would be not realistic to include the Data Access Policy GE, so either we delete this entry from the list, or we write as a description that the GE will not be included in the April 2012 release (for the same reason we made some simplification in the other GE we described at gateway level) Gateway Local Storage - Ericsson is working on that Backend Connectivity Management Backend Service Control Backend Device Frontend - I know that TI is currently responsible for IoT Communication, but when we got the assignment to work on the Gateway with Ericsson we assumed that someone else would have dealt with the GEs at Backend level. Otherwise out of 11 GEs (13-2 that will not be included in the April release) we have to work on 6 of them, that is more than 50% of the work. It looks quite unfair. 2nd group (Minimal description) Gateway Exposure Gateway Connectivity Management Gateway Device Frontend - actually we started from Ricardo's Things and Resources Management GE description, that was indicated as a good example of the GE descriptions and in all these GEs description there is an overview, a list of basic concepts in the form of the interfaces included in the GE, an architecture of the GE in FMC with the description of the component, and the main interactions with a list of operations on the different interfaces. Following your comments I moved the short ETSI M2M description in the Gateway Exposure GE from the overview into the basic concepts section, I also get rid of the SCL references that were actually not described correctly. The information model is only included in the Connectivity Management GE (we are working on that), because it contains a store, the Connected Device List, while the other GEs does not have any store so we not included any information model. The descriptions are not really complex because we and Ericsson are really describing the content for the April release, so we simplified the components in these GEs in order to be realistic. 3rd group (Missing elements): Gateway Data Handling - By the way there is the Gateway Data Handling GE that was described but we do not know who is the author of this description. It looks like this is a long term description and does not much an April release in our opinion (TI and Ericsson). Maybe we need to talk about this with the author of the description (engaging him in the actual discussion between us and Ericsson) in order to have an agreed view at gateway level. Gateway Service Control - :) Yes, I actually asked to add the Service Control at gateway level for the symmetry of the system, but that was for the long term architectural view, not for the April release, so I added it to the list in the wiki, but it is one of those GEs that will not be included in the April release and we have to decide if leaving them with a note, or delete them. In conclusion, we have 5 GEs available on the gateway (Exposure, Data Pooling, Local Storage, Connectivity Management, and Device Frontend), there is one that is not harmonized with the others (Data Handling), and there are 2 that will not be included in the April 2012 release so are not described (Data Access Policy, and Service Control). I took care to introduce some modifications to some GEs descriptions following your comments and I tried to explain the reasoning behind these descriptions. Please let me know if you have any other comment or you disagree on my positions. About the Backend the situation is more complex since I really do not know how we could complete the work at platform level too. Best regards, Gian Piero Da: fiware-iot-bounces at lists.fi-ware.eu [mailto:fiware-iot-bounces at lists.fi-ware.eu] Per conto di Bisztray, Denes (NSN - HU/Budapest) Inviato: giovedì 16 febbraio 2012 15:13 A: fiware-iot at lists.fi-ware.eu Oggetto: [Fiware-iot] Arch Description Problems Dear All, There are some problems with the description of most of the GEs. 1st group: There is absolutely no change compared to my initial sketch: * FIWARE.ArchitectureDescription.IoT.Backend.ConnectivityManagement<https://forge.fi-ware.eu/plugins/mediawiki/wiki/fi-ware-private/index.php/FIWARE.ArchitectureDescription.IoT.Backend.ConnectivityManagement> * FIWARE.ArchitectureDescription.IoT.Backend.ServiceControl<https://forge.fi-ware.eu/plugins/mediawiki/wiki/fi-ware-private/index.php/FIWARE.ArchitectureDescription.IoT.Backend.ServiceControl> * FIWARE.ArchitectureDescription.IoT.Backend.DeviceFrontend<https://forge.fi-ware.eu/plugins/mediawiki/wiki/fi-ware-private/index.php/FIWARE.ArchitectureDescription.IoT.Backend.DeviceFrontend> * FIWARE.ArchitectureDescription.IoT.Gateway.DataPooling<https://forge.fi-ware.eu/plugins/mediawiki/wiki/fi-ware-private/index.php/FIWARE.ArchitectureDescription.IoT.Gateway.DataPooling> * FIWARE.ArchitectureDescription.IoT.Gateway.DataAccessPolicy<https://forge.fi-ware.eu/plugins/mediawiki/wiki/fi-ware-private/index.php/FIWARE.ArchitectureDescription.IoT.Gateway.DataAccessPolicy> * FIWARE.ArchitectureDescription.IoT.Gateway.LocalStorage<https://forge.fi-ware.eu/plugins/mediawiki/wiki/fi-ware-private/index.php/FIWARE.ArchitectureDescription.IoT.Gateway.LocalStorage> This is a LOT! As far as I understand, the Gateway GEs are Telecom Italia's and Ericssons' responsibility. The three Communication GEs on the backend should be also done by the IoT Communication Chapter, which also falls to Telecom Italia. 2nd group: Minimal description: - FIWARE.ArchitectureDescription.IoT.Gateway.Exposure<https://forge.fi-ware.eu/plugins/mediawiki/wiki/fi-ware-private/index.php/FIWARE.ArchitectureDescription.IoT.Gateway.Exposure> - FIWARE.ArchitectureDescription.IoT.Gateway.ConnectivityManagement<https://forge.fi-ware.eu/plugins/mediawiki/wiki/fi-ware-private/index.php/FIWARE.ArchitectureDescription.IoT.Gateway.ConnectivityManagement> - FIWARE.ArchitectureDescription.IoT.Gateway.DeviceFrontend<https://forge.fi-ware.eu/plugins/mediawiki/wiki/fi-ware-private/index.php/FIWARE.ArchitectureDescription.IoT.Gateway.DeviceFrontend> These GEs are described in a minimalistic manner. Also they hardy follow the template. The template is clear, Overview with possible architecture description. Basic Concepts and then Interactions. Most of these GEs mix these things up AND/OR does not describe elementary concepts that needed in order to understand the description (i.e. the SCL is not defined anywhere but used a lot), also there are no information model in most cases . 3rd group: Missing elements: - FIWARE.ArchitectureDescription.IoT.Gateway.DataHandling<https://forge.fi-ware.eu/plugins/mediawiki/wiki/fi-ware-private/index.php/FIWARE.ArchitectureDescription.IoT.Gateway.DataHandling> The Main Interactions section is completely missing. 3rd group: Missing GE. - Service Control GE from the Gateway. Although it was not in my initial FMC model, Gian Piero asked to have it in the Gateway. It is missing currently. Please, we have only half day before the deadline, and this is seriously a lot of work. For examples please have a look at these: - FIWARE.ArchitectureDescription.IoT.Backend.Exposure<https://forge.fi-ware.eu/plugins/mediawiki/wiki/fi-ware-private/index.php/FIWARE.ArchitectureDescription.IoT.Backend.Exposure> - FIWARE.ArchitectureDescription.IoT.Backend.ThingsAndResourcesManagement<https://forge.fi-ware.eu/plugins/mediawiki/wiki/fi-ware-private/index.php/FIWARE.ArchitectureDescription.IoT.Backend.ThingsAndResourcesManagement> I'm sorry if I sound desperate, but 2 out of 12 GEs are finished in a reasonably good manner one day before the deadline. Please don't count on the WPA this time to fill the missing gaps. Best, Dénes 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/20120216/1abd3c71/attachment.html> -------------- 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/20120216/1abd3c71/attachment.jpg>
You can get more information about our cookies and privacy policies clicking on the following links: Privacy policy Cookies policy