Hi, we've begun to analyze the list of assets related to the "IoT Communication" task submitted by the FI-WARE partners. Some initial considerations for the components are: * Component Connection Protocol Adapter - the better solution is that as many as possible protocols are supported by the IoT Services Enablement Platform, for this reason all the assets presented can be included into the implementation of the IoT SE Platform, provided that it's possible to translate them in a common internal form through the component Communication Protocol Abstraction Definition. * Component Communication Protocol Abstraction Definition - the epic for this component is different from the description included in the document "FI-WARE High-level Description". Our goal was to introduce a layer that allows an abstraction level for all Connection Protocol Adapters in order to communicate with the IoT SE Platform Core using a common internal language. The "templates", we are referring to in the document, are a kind of rules to translate any specific protocol into the common internal language and not a mechanism to generate Connection Protocol Adapters. This mechanism to automatically generate Connection Protocol Adapters is in any case very interesting and we could add it to the architecture document, if needed. * Component Access Policy Control - The second point of the epic for this component treats the access as a matter of payment (e.g. access only free services), while we intend the access as a matter of permissions to access resources. In our opinion these are different levels and they don't belong to the same component. * Component Quality of Service Control - From the grid it looks like that no asset has this functionality readily available, but since this component is not fundamental for a prototype of the IoT SE Platform, it can be left out or postponed in the future. For the other components we don't have specific considerations for the moment, but it looks like that Pangoo/M2MPlanet (by Orange) and Cumulocity (by NSN) are the assets that are more in line with our requirements. What do you think of this initial analysis of the assets? Are there any comments on these considerations? If you agree we could proceed with a more detailed analysis of the two proposed assets. 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: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/20110905/c84a55d6/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/20110905/c84a55d6/attachment.jpg>
You can get more information about our cookies and privacy policies clicking on the following links: Privacy policy Cookies policy