Dear All, thanks for all the comments sent. By merging them I have updated the picture as you see in the attachment. Probably there's something more that can be done but, maybe also for my poor knowledge of the representation styles with FMC notation. Here are the most important aspects: - At the moment I believe that concentrating in a unique stakeholder all the possible actors interacting with the four GEs is synthesizing better than other solutions the interaction with our GEs. - Question: do we need to have the 'Network Operators' actor explicitly shown as I have put it now? - About Thomas' feedback: I think that the different arcs connecting to a single agent not necessarily mean that they interact with different classes of interfaces; for me it's just as matter of showing separately the arcs, but maybe I'm wrong with the notation. Should we draw a single channel (e.g. circle) with multiple arcs from actors and a single arc to the agent? On the other hand, if every channel is to be separate according to its class of interfaces, then probably the drawing should be more complex. Are we ready to make this distinction clear right now? Any further feedback is highly welcome. BR Pier Da: fiware-i2nd-bounces at lists.fi-ware.eu [mailto:fiware-i2nd-bounces at lists.fi-ware.eu] Per conto di BANNIZA, Thomas-Rolf Inviato: lunedì 13 febbraio 2012 12:49 A: Hans.Einsiedler at telekom.de Cc: fiware-i2nd at lists.fi-ware.eu Oggetto: Re: [Fiware-i2nd] Overall architecture for I2ND GEs Hi Hans, thanks for the clarification, this makes the figure show about the same (but in a diffenrent way) what is shown in the figure in architecture overview in WiKi. But now I would like to ask (I think it is a similar issue to the qustion Jean-Piwerre already raised): The figure shows 3 north interfaces, does this mean that there are three different classes of interfaces or what should be the message behind this multiple interfaces? If they are different, are there restrictions for certain classes of clients to access them? ________________________________ Von: Hans.Einsiedler at telekom.de [mailto:Hans.Einsiedler at telekom.de] Gesendet: Montag, 13. Februar 2012 11:50 An: lorant.nemeth at nsn.com; BANNIZA, Thomas-Rolf Cc: fiware-i2nd at lists.fi-ware.eu Betreff: RE: [Fiware-i2nd] Overall architecture for I2ND GEs Dear all, I have added some interfaces. Please have a look. Cheers, Hans Message Classification: [ ] Public [ ] Private [ ] Internal Use Only [ ] For your eyes only [ ] General Business Use [ ] DTAG Internal Use Only [ ] DTAG Confidential Proprietary From: fiware-i2nd-bounces at lists.fi-ware.eu [mailto:fiware-i2nd-bounces at lists.fi-ware.eu] On Behalf Of Lorant Nemeth Sent: Montag, 13. Februar 2012 11:18 To: ext BANNIZA, Thomas-Rolf Cc: fiware-i2nd at lists.fi-ware.eu Subject: Re: [Fiware-i2nd] Overall architecture for I2ND GEs Hi, I share Thomas' view. Br, Loci On 02/13/2012 11:15 AM, ext BANNIZA, Thomas-Rolf wrote: Dear Pier, after a first look on the figure I'm not sure whether the differentiation between on one hand applications and cloud services only talking with CDI and CE (I assume this should reflect intercations with end devices?) and on the other hand FIWARE GEs only talking with NetIC and S3C is correct. Do you think that NetIC and S3C are only used by FiWare internal? In my eyes, there might exist applications outside FiWare which might request from S3C or NEtIC some specific connectivity or at least wants to gather information about e.g. the traffic situation in the network. Best regards, Thomas ________________________________ Von: fiware-i2nd-bounces at lists.fi-ware.eu<mailto:fiware-i2nd-bounces at lists.fi-ware.eu> [mailto:fiware-i2nd-bounces at lists.fi-ware.eu] Im Auftrag von Garino Pierangelo Gesendet: Montag, 13. Februar 2012 10:47 An: fiware-i2nd at lists.fi-ware.eu<mailto:fiware-i2nd at lists.fi-ware.eu> Betreff: [Fiware-i2nd] Overall architecture for I2ND GEs Dear All, I tried to represent through FMC notation, as planned for the entire Architecture deliverable, the high-level architecture of the I2ND GEs. You can find the current drawing in the attached image. Do you believe it could well represent/substitute the current picture we used so far? Please let me know what would you modify in it. One comment: as I don't have Visio, I downloaded the yEd (free) tool, and I generated this diagram with it. I'm also able to export it as SVG, but I'm not sure it will be possible to import e.g. in Visio (the reverse doesn't work, I already tried it!), can some of you attempt to do this with the attached .svg file? The use of different file formats is becoming an issue when trying to cooperatively work on the same diagram... BR Pier ------------------------------------------------------------------ Telecom Italia Pierangelo Garino Innovation & Industry Relations - Research & Prototyping Via G. Reiss Romoli 274, I-10148 TORINO Tel: +39 011 228 7142 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. _______________________________________________ Fiware-i2nd mailing list Fiware-i2nd at lists.fi-ware.eu<mailto:Fiware-i2nd at lists.fi-ware.eu> http://lists.fi-ware.eu/listinfo/fiware-i2nd -- Lóránt Németh R&D Team Leader Koztelek str. 6 1092, Budapest, HUNGARY Tel.: +36209849340 Fax: +3612154766 lorant.nemeth at nsn.com<mailto:lorant.nemeth at nsn.com> http://www.nokiasiemensnetworks.com/global/ This email message and any attachments are for the sole use of the intended recipients and may contain proprietary and/or confidential information which may be privileged or otherwise protected from disclosure. Any unauthorized review, use, disclosure or distribution is prohibited. If you are not an intended recipient, please contact the sender by reply email and destroy the original message and any copies of the message as well as any attachments to the original message. Local registered entity information: 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-i2nd/attachments/20120213/7313ea11/attachment.html> -------------- next part -------------- A non-text attachment was scrubbed... Name: I2D_Architecture-2.jpg Type: image/jpeg Size: 42638 bytes Desc: I2D_Architecture-2.jpg URL: <https://lists.fiware.org/private/old-fiware-i2nd/attachments/20120213/7313ea11/attachment.jpg> -------------- 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-i2nd/attachments/20120213/7313ea11/attachment-0001.jpg>
You can get more information about our cookies and privacy policies clicking on the following links: Privacy policy Cookies policy