From thierry.nagellen at orange-ftgroup.com Wed Jun 1 15:40:49 2011 From: thierry.nagellen at orange-ftgroup.com (thierry.nagellen at orange-ftgroup.com) Date: Wed, 1 Jun 2011 15:40:49 +0200 Subject: [Fiware-iot] Minutes form today telco meeting Message-ID: Dear all Please find the minutes from morning meeting (Thanks Lorant for your minutes). The architecture document is now on the forge (http://forge.fi-ware.eu/docman/?group_id=11) <> BR Thierry -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: IoT-Minutes-Telco-06012011.doc Type: application/msword Size: 49664 bytes Desc: IoT-Minutes-Telco-06012011.doc URL: From sabrina.guerra at telecomitalia.it Wed Jun 1 17:49:11 2011 From: sabrina.guerra at telecomitalia.it (Guerra Sabrina) Date: Wed, 1 Jun 2011 17:49:11 +0200 Subject: [Fiware-iot] IoT Communication Architecture picture In-Reply-To: References: Message-ID: <36A93B31228D3B49B691AD31652BCAE9A53382016D@GRFMBX702BA020.griffon.local> 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. [cid:00000000000000000000000000000001 at TI.Disclaimer]Rispetta l'ambiente. Non stampare questa mail se non ? necessario. -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: IoT Communication-Architecture-v01.ppt Type: application/vnd.ms-powerpoint Size: 117248 bytes Desc: IoT Communication-Architecture-v01.ppt URL: -------------- 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: From lorant.farkas at nsn.com Thu Jun 2 08:00:42 2011 From: lorant.farkas at nsn.com (Farkas, Lorant (NSN - HU/Budapest)) Date: Thu, 2 Jun 2011 09:00:42 +0300 Subject: [Fiware-iot] IoT Communication Architecture picture In-Reply-To: <36A93B31228D3B49B691AD31652BCAE9A53382016D@GRFMBX702BA020.griffon.local> References: <36A93B31228D3B49B691AD31652BCAE9A53382016D@GRFMBX702BA020.griffon.local> Message-ID: <93D28BDF64839C468B848D14227151A201D75461@FIESEXC014.nsn-intra.net> Dear Sabrina and Gian Piero, Please register under Forge so that I can add you to the IoT project in Forge. This will enable you to see the submitted documents. We plan to send around in e-mails just the links to these rather than the entire documents, preventing your mailboxes getting too big. This will also enable us to use the tools for tasks assignment and potentially other tools as well, provided by Forge, also in your case. Please see the registration howto from the e-mail of Juanjo, attached. Best regards, Lorant ________________________________ From: fiware-iot-bounces at lists.fi-ware.eu [mailto:fiware-iot-bounces at lists.fi-ware.eu] On Behalf Of ext Guerra Sabrina Sent: Wednesday, June 01, 2011 5:49 PM To: 'fiware-iot at lists.fi-ware.eu' Subject: [Fiware-iot] IoT Communication Architecture picture 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. -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- 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: -------------- next part -------------- An embedded message was scrubbed... From: "ext Juanjo Hierro" Subject: [Fiware-iot] Reminder and updated instructions for registering at FusionForge and be able to access to shared documentation Date: Tue, 17 May 2011 17:55:12 +0300 Size: 16907 URL: From rheras at tid.es Thu Jun 2 17:07:20 2011 From: rheras at tid.es (Ricardo de las Heras) Date: Thu, 02 Jun 2011 17:07:20 +0200 Subject: [Fiware-iot] IoT Communication Architecture picture In-Reply-To: <36A93B31228D3B49B691AD31652BCAE9A53382016D@GRFMBX702BA020.griffon.local> References: <36A93B31228D3B49B691AD31652BCAE9A53382016D@GRFMBX702BA020.griffon.local> Message-ID: <4DE7A728.1060204@tid.es> An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: image/jpeg Size: 677 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: Fiware-IoT-Resource.Mngmt-T5.2.pptx Type: application/vnd.ms-powerpoint.presentation.12 Size: 83998 bytes Desc: not available URL: From rheras at tid.es Fri Jun 3 13:58:58 2011 From: rheras at tid.es (Ricardo de las Heras) Date: Fri, 03 Jun 2011 13:58:58 +0200 Subject: [Fiware-iot] IoT Communication Architecture picture In-Reply-To: <4DE7A728.1060204@tid.es> References: <36A93B31228D3B49B691AD31652BCAE9A53382016D@GRFMBX702BA020.griffon.local> <4DE7A728.1060204@tid.es> Message-ID: <4DE8CC82.4060000@tid.es> An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: image/jpeg Size: 677 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: Fiware-IoT-Resource Mngmt-T5 2.pptx Type: application/vnd.openxmlformats-officedocument.presentationml.presentation Size: 92328 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: Fiware-T5.2-Description.docx Type: application/vnd.openxmlformats-officedocument.wordprocessingml.document Size: 18349 bytes Desc: not available URL: From lorant.farkas at nsn.com Fri Jun 3 14:09:15 2011 From: lorant.farkas at nsn.com (Farkas, Lorant (NSN - HU/Budapest)) Date: Fri, 3 Jun 2011 15:09:15 +0300 Subject: [Fiware-iot] IoT Communication Architecture picture In-Reply-To: <4DE8CC82.4060000@tid.es> References: <36A93B31228D3B49B691AD31652BCAE9A53382016D@GRFMBX702BA020.griffon.local><4DE7A728.1060204@tid.es> <4DE8CC82.4060000@tid.es> Message-ID: <93D28BDF64839C468B848D14227151A201D75A0F@FIESEXC014.nsn-intra.net> 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: rheras at tid.es Phone1: (+34) 983 367625 Phone2: (+34) 91 1878107 + Ext:327 Telef?nica I+D ------------------------------------- -- ------------------------------------- Ricardo de las Heras Research Project Manager E-mail: rheras at tid.es Phone1: (+34) 983 367625 Phone2: (+34) 91 1878107 + Ext:327 Telef?nica I+D ------------------------------------- ________________________________ 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: -------------- next part -------------- A non-text attachment was scrubbed... Name: ATT157680.jpg Type: image/jpeg Size: 677 bytes Desc: ATT157680.jpg URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: Resource-Mngmt-v02.pptx Type: application/octet-stream Size: 52361 bytes Desc: Resource-Mngmt-v02.pptx URL: From stephan.haller at sap.com Fri Jun 3 14:22:43 2011 From: stephan.haller at sap.com (Haller, Stephan) Date: Fri, 3 Jun 2011 14:22:43 +0200 Subject: [Fiware-iot] IoT Communication Architecture picture In-Reply-To: <93D28BDF64839C468B848D14227151A201D75A0F@FIESEXC014.nsn-intra.net> References: <36A93B31228D3B49B691AD31652BCAE9A53382016D@GRFMBX702BA020.griffon.local><4DE7A728.1060204@tid.es> <4DE8CC82.4060000@tid.es> <93D28BDF64839C468B848D14227151A201D75A0F@FIESEXC014.nsn-intra.net> Message-ID: <0D2446AEB6CAED48BB046223733964A54BCF05C4CC@DEWDFECCR01.wdf.sap.corp> Well, IoT Resource and EoI are completely different things. I am not sure which one fits better here... Regards, -Stephan From: fiware-iot-bounces at lists.fi-ware.eu [mailto:fiware-iot-bounces at lists.fi-ware.eu] On Behalf Of Farkas, Lorant (NSN - HU/Budapest) Sent: Freitag, 3. Juni 2011 14:09 To: ext Ricardo de las Heras; fiware-iot at lists.fi-ware.eu Subject: 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. [cid:image001.gif at 01CC21F9.B3F1E6D0]Rispetta l'ambiente. Non stampare questa mail se non ? necessario. -- ------------------------------------- Ricardo de las Heras Research Project Manager E-mail: rheras at tid.es Phone1: (+34) 983 367625 Phone2: (+34) 91 1878107 + Ext:327 Telef?nica I+D ------------------------------------- -- ------------------------------------- Ricardo de las Heras Research Project Manager E-mail: rheras at tid.es Phone1: (+34) 983 367625 Phone2: (+34) 91 1878107 + Ext:327 Telef?nica I+D ------------------------------------- ________________________________ 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: -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.gif Type: image/gif Size: 677 bytes Desc: image001.gif URL: From P.Barnaghi at surrey.ac.uk Fri Jun 3 14:48:42 2011 From: P.Barnaghi at surrey.ac.uk (P.Barnaghi at surrey.ac.uk) Date: Fri, 3 Jun 2011 13:48:42 +0100 Subject: [Fiware-iot] IoT Communication Architecture picture In-Reply-To: <0D2446AEB6CAED48BB046223733964A54BCF05C4CC@DEWDFECCR01.wdf.sap.corp> References: <36A93B31228D3B49B691AD31652BCAE9A53382016D@GRFMBX702BA020.griffon.local><4DE7A728.1060204@tid.es> <4DE8CC82.4060000@tid.es> <93D28BDF64839C468B848D14227151A201D75A0F@FIESEXC014.nsn-intra.net> <0D2446AEB6CAED48BB046223733964A54BCF05C4CC@DEWDFECCR01.wdf.sap.corp> Message-ID: As Stefan said those are two different concepts; The diagram illustrates IoT Resource and Service enabler; perhaps the component should store Resource descriptions but if it is meant to support resource discovery (which I think it does) then EoI descriptions are also required. One more comment: IoT resource Description is not a component; the component could include interfaces to publish and manage resource descriptions and also provide interfaces to access/use the resources; but resource description itself is only an information model. Regards, Payam ________________________________ From: fiware-iot-bounces at lists.fi-ware.eu [mailto:fiware-iot-bounces at lists.fi-ware.eu] On Behalf Of Haller, Stephan Sent: 03 June 2011 13:23 To: Farkas, Lorant (NSN - HU/Budapest); ext Ricardo de las Heras; fiware-iot at lists.fi-ware.eu Subject: Re: [Fiware-iot] IoT Communication Architecture picture Well, IoT Resource and EoI are completely different things. I am not sure which one fits better here... Regards, -Stephan From: fiware-iot-bounces at lists.fi-ware.eu [mailto:fiware-iot-bounces at lists.fi-ware.eu] On Behalf Of Farkas, Lorant (NSN - HU/Budapest) Sent: Freitag, 3. Juni 2011 14:09 To: ext Ricardo de las Heras; fiware-iot at lists.fi-ware.eu Subject: 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. [cid:image001.gif at 01CC21F4.F30C05D0]Rispetta l'ambiente. Non stampare questa mail se non ? necessario. -- ------------------------------------- Ricardo de las Heras Research Project Manager E-mail: rheras at tid.es Phone1: (+34) 983 367625 Phone2: (+34) 91 1878107 + Ext:327 Telef?nica I+D ------------------------------------- -- ------------------------------------- Ricardo de las Heras Research Project Manager E-mail: rheras at tid.es Phone1: (+34) 983 367625 Phone2: (+34) 91 1878107 + Ext:327 Telef?nica I+D ------------------------------------- ________________________________ 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: -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.gif Type: image/gif Size: 677 bytes Desc: image001.gif URL: From thierry.nagellen at orange-ftgroup.com Sun Jun 5 21:10:27 2011 From: thierry.nagellen at orange-ftgroup.com (thierry.nagellen at orange-ftgroup.com) Date: Sun, 5 Jun 2011 21:10:27 +0200 Subject: [Fiware-iot] IoT Communication Architecture picture In-Reply-To: <93D28BDF64839C468B848D14227151A201D75A0F@FIESEXC014.nsn-intra.net> References: <36A93B31228D3B49B691AD31652BCAE9A53382016D@GRFMBX702BA020.griffon.local><4DE7A728.1060204@tid.es><4DE8CC82.4060000@tid.es> <93D28BDF64839C468B848D14227151A201D75A0F@FIESEXC014.nsn-intra.net> Message-ID: 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: rheras at tid.es Phone1: (+34) 983 367625 Phone2: (+34) 91 1878107 + Ext:327 Telef?nica I+D ------------------------------------- -- ------------------------------------- Ricardo de las Heras Research Project Manager E-mail: rheras at tid.es Phone1: (+34) 983 367625 Phone2: (+34) 91 1878107 + Ext:327 Telef?nica I+D ------------------------------------- ________________________________ 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: -------------- next part -------------- A non-text attachment was scrubbed... Name: ATT157680.jpg Type: image/jpeg Size: 677 bytes Desc: ATT157680.jpg URL: From rheras at tid.es Mon Jun 6 15:54:37 2011 From: rheras at tid.es (Ricardo de las Heras) Date: Mon, 06 Jun 2011 15:54:37 +0200 Subject: [Fiware-iot] IoT Communication Architecture picture In-Reply-To: References: <36A93B31228D3B49B691AD31652BCAE9A53382016D@GRFMBX702BA020.griffon.local> <4DE7A728.1060204@tid.es> <4DE8CC82.4060000@tid.es> <93D28BDF64839C468B848D14227151A201D75A0F@FIESEXC014.nsn-intra.net> Message-ID: <4DECDC1D.5030805@tid.es> An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: image/jpeg Size: 677 bytes Desc: not available URL: From thierry.nagellen at orange-ftgroup.com Tue Jun 7 15:29:35 2011 From: thierry.nagellen at orange-ftgroup.com (thierry.nagellen at orange-ftgroup.com) Date: Tue, 7 Jun 2011 15:29:35 +0200 Subject: [Fiware-iot] =?iso-8859-1?q?Mis=28e=29_=E0_jour=3A_IoT_weekly_tel?= =?iso-8859-1?q?co?= Message-ID: Quand : mercredi 8 juin 2011 10:00-11:30 (GMT+01:00) Brussels, Copenhagen, Madrid, Paris. *~*~*~*~*~*~*~*~*~* Please note that we have change the slot of our weekly meetong for all the meetings, not only the last one. We have now only 1 week to finalize IoT contribution to Architecture Deliverable. **** You can forward this email invitation to attendees **** Hello , L?r?nt Farkas invites you to attend this online meeting. Topic: IOT WP weekly Date: Every Wednesday, from Wednesday, 11 May 2011 to Wednesday, 26 March 2014 Time: 9:30, Europe Summer Time (Paris, GMT+02:00) Meeting Number: 709 472 921 Meeting Password: FI-WARE ------------------------------------------------------- To join the online meeting ------------------------------------------------------- 1. Go to https://nsn.webex.com/nsn/j.php?ED=175018962&UID=0&PW=NYzEzYWM0ZTNk&RT=MTgjMjM%3D 2. Enter your name and email address. 3. Enter the meeting password: FI-WARE 4. Click "Join Now". To view in other time zones or languages, please click the link: https://nsn.webex.com/nsn/j.php?ED=175018962&UID=0&PW=NYzEzYWM0ZTNk&ORT=MTgjMjM%3D ------------------------------------------------------- NSN Voice Conference information Conference ID: 58465 PIN: 9012 Making a conference call - from the office: 8071870 (in Finland and Germany) - from out of office: +358 7180 71870 (in Finland) and +49 89 5159 43800 (in Germany) All out-of-office conference access numbers are listed in page . Country/Site Conference access number All sites From company office conference phone or desk phone 8071870. This number also works from company mobiles in several countries. See Internal Numbers page for more information. Argentina - Buenos Aires +54 11 5983 9400 (PRIMARY) or +54 11 4814 9373 Argentina - Cordoba +54 35 1568 2208 Australia - Sydney +61 28 014 7189 (PRIMARY) or +61 29 429 9664 Australia - Melbourne +61 38 739 4333 Austria +43 72 088 0245 Bahrain +97 31 619 9028 Belgium - Generic +32 1448 0116 Belgium - Diegem-Machelen +32 2710 3300 Brazil - Belo Horizonte +55 31 3956 0546 Brazil - Brazil +55 61 3717 2043 Brazil - Curitiba +55 41 3906 0826 Brazil - Manaus +55 92 3652 7576 Brazil - Rio De Janeiro +55 21 3958 0804 (PRIMARY) or +55 21 3431 1999 Brazil - Salvador +55 71 3717 5351 Brazil - Sao Paolo +55 11 5508 0630 Bulgaria +359 2491 7085 Canada - Ajax +1 90 5619 4346 Canada - Burnaby +1 60 4456 5897 Canada - Hamilton +1 905 581 0212 Canada - Mississauga +1 289 360 3950 Canada - Montreal +1 51 4789 9125 Canada - Ottawa +1 61 3800 0568 Chile - Santiago +56 2350 6485 China - Mainland +86 10 8405 5000 ext 1870 China - Beijing +86 10 8405 5000 ext 1870 China - Chengdu +86 28 8689 0188 ext 1870 China - Dongguan +86 0769 2240 2844 ext 1870 China - Guangzhou +86 20 8755 6190 ext 1870 China - Hangzhou +86 571 8722 0877 ext 1870 China - Hong Kong +852 259 70220 ext 1870 China - Kunming +86 871 362 2880 ext 1870 China - Shanghai +86 21 6101 1870 ext 1870 China - ShenZhen +86 755 8613 3688 ext 1870 China - Suzhou +86 512 6761 6166 ext 1870 China - Zhengzhou +86 371 6566 9768 ext 1870 Colombia +57 1640 7979 ext 444 Croatia +38 51 777 6122 Czech Republic +42 02 460 19300 Denmark +45 699 18450 (PRIMARY) or +45 3329 2882 Egypt +97 31 619 9028 (Bahrain nbr) Estonia +37 266 67297 Finland +358 7180 71870 France +33 17 061 7813 (PRIMARY) or +33 14 915 1553 Germany +49 89 5159 43800 Greece +30 21 1176 8207 (PRIMARY) or +30 21 1120 3677 Hungary - Budapest +36 17 009 888 Hungary - Kom?rom +36 20 884 2499 India 000 800 100 7777 Indonesia - Jakarta (Menara Mulia/Plaza Kuningan +62 21 2557 9102 Indonesia - Bandung +62 22 8427 5992 Indonesia - Medan +62 61 3001 2702 Indonesia - Semarang +62 24 3300 0702 Ireland +353 1526 2862 Israel +97 29 775 1700 Italy - Milan +39 024 004 2007 Italy - Rome +39 069 481 6656 Japan +81 3 4578 0230 (PRIMARY) or +81 3 5474 7979 Kuwait +97 31 619 9028 (Bahrain nbr) Latvia +37 16 765 2510 Lithuania +37 0 5205 8994 Luxembourg +352 2088 0106 Malaysia +60 323 029 009 Mexico - Mexico City +52 55 3686 9759 (PRIMARY) or +52 55 5261 7245 Mexico - Reynosa +52 89 9909 1555 Netherlands +31 79 346 5225 New Zealand +64 9306 6933 Norway - Oslo +47 21 548 223 Oman +97 31 619 9028 (Bahrain nbr) Pakistan +92 512 092 444 Panama +507 832 7981 Peru +51 1708 5370 (PRIMARY) or +51 1215 7650 Philippines +63 2754 1700 Poland - Warsaw +48 22 398 8116 Poland - Wroclaw +48 71 718 1215 Portugal +351 21 044 4698 Qatar +97 31 619 9028 (Bahrain nbr) Romania +40 36 440 3799 Russia +74 95 725 2706 Saudi Arabia +97 31 619 9028 (Bahrain nbr) Singapore +65 3103 1065 (PRIMARY) or +65 6723 2582 Slovakia +42 12 3300 6924 Slovenia +38 61 600 2713 South Africa - Johannesburg +27 1 0500 2221 South Africa - Pretoria +27 1 2004 2334 South Korea - Masan +82 5 5290 7690 South Korea - Seoul +82 2 2186 5088 Spain +349 1187 5929 Sweden +46 85 250 0862 (PRIMARY), +46 84 100 9299 Switzerland +41 44 279 7943 Taiwan +88 62 8175 9298 Thailand +66 2762 6750 Turkey +90 216 570 2345 Ukraine +38 044 520 2272 UK +44 12 5275 8334 UK - Camberley +44 12 5286 5849 UK - Church Crookham +44 12 5261 1100 UK - Huntingdon +44 14 8087 8220 (PRIMARY), +44 14 8044 4206 UK - London +44 20 3318 1924 United Arab Emirates +97 31 619 9028 (Bahrain nbr) USA - Alpharetta +1 770 871 3050 USA - Arizona +1 480 588 3748 USA - Atlanta +1 404 236 4550 USA - Atlanta Notheast +1 678 317 3165 USA - Austin/Round Rock +1 512 600 2027 USA - Belleville +1 973 547 7982 USA - Boca Raton +1 561 910 2843 USA - Boston +1 617 963 8320 (PRIMARY) or +1 781 993 4850 USA - Burlington +1 781 993 4850 USA - Calabasas +1 818 914 0215 USA - Canoga Park +1 818 914 0215 USA - Cary +1 919 655 1388 USA - Chelmsford/Littleton +1 978 679 0233 USA - Chicago +1 773 303 4710 USA - Dallas +1 214 269 7626 USA - Dallas/Fort Worth +1 214 270 0352 USA - Greenville, NC +1 252 329 1677 USA - Herndon +1 703 483 4485 USA - Johnson City +1 423 952 1545 USA - Kirkland +1 425 242 3113 USA - Miami +1 786 388 4150 or +1 786 329 7177 USA - Naperville +1 630 596 2203 USA - New Brunswick +1 732 579 6483 USA - New Century, KS +1 913 254 5900 USA - New York White Plains +1 914 368 0650 USA - New York Peekskill, White Plains +1 914 293 1885 USA - Palo Alto +1 650 644 1349 USA - Redmond +1 425 242 3113 USA - San Diego +1 858 769 5309 or +1 619 330 9699 USA - Sunnyvale +1 408 419 1750 USA - Washington D.C +1 202 552 4781 Vietnam +84 4 3724 6110 Yemen +97 31 619 9028 (Bahrain nbr) Please check and prioritize them. If there is no access number for your country then please use access numbers of the area where to the calling costs are lowest. ------------------------------------------------------- For assistance ------------------------------------------------------- 1. Go to https://nsn.webex.com/nsn/mc 2. On the left navigation bar, click "Support". You can contact me at: lorant.farkas at nsn.com To add this meeting to your calendar program (for example Microsoft Outlook), click this link: https://nsn.webex.com/nsn/j.php?ED=175018962&UID=0&ICS=MI&LD=1&RD=18&ST=1&SHA2=gVmoQ/CXj05nzcI-4TFgQ2qtqmAulzDfzoOWKpcyLyg=&RT=MTgjMjM%3D -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: meeting.ics Type: text/calendar Size: 10886 bytes Desc: not available URL: From gianpiero.fici at telecomitalia.it Tue Jun 7 17:32:18 2011 From: gianpiero.fici at telecomitalia.it (Fici Gian Piero) Date: Tue, 7 Jun 2011 17:32:18 +0200 Subject: [Fiware-iot] I: Comments on IoT Communication Architecture In-Reply-To: References: Message-ID: Hi Thierry. Here you can find the description regarding the architectural picture related to the IoT Communication Generic Enabler. It is inserted into the IoT Communication chapter (the first part is not changed, look just at the picture and at the following description). Please, feel free to send any comment. Bye, Gian Piero Da: thierry.nagellen at orange-ftgroup.com [mailto:thierry.nagellen at orange-ftgroup.com] Inviato: marted? 7 giugno 2011 11:17 A: Fici Gian Piero; Guerra Sabrina Cc: lorant.farkas at nsn.com Oggetto: Comments on IoT Communication Architecture Hi Gianpiero and Sabrina We expect a new description for the IoT Communication regarding the picture you sent last week. We have to finalize the architecture document for IoT next week for the whole integration so we need your contribution for tomorrow to discuss it in details. Thanks BR Thierry 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: -------------- next part -------------- A non-text attachment was scrubbed... Name: IoT Communication-Architecture-v01.zip Type: application/x-zip-compressed Size: 202690 bytes Desc: IoT Communication-Architecture-v01.zip URL: -------------- 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: From Ernoe.Kovacs at neclab.eu Wed Jun 8 09:39:37 2011 From: Ernoe.Kovacs at neclab.eu (Ernoe Kovacs) Date: Wed, 8 Jun 2011 07:39:37 +0000 Subject: [Fiware-iot] Today's Telco: Start Time? / Repository Organization Message-ID: <8152E2132B13FB488CFD1947E2DEF19C13A5DCFF@DAPHNIS.office.hd> Thierry, all, for today's telco... (a) I am bit confused. The Outlook meeting invitation is 10:00, the text says 9:30. --> I assume 10:00. Correct? (b) Forge Organisation / Document Repository I had to catch up 2 weeks out of the office and found it hard to understand which is the latest version of the document, which is the main document and which is a sub-document. Also, FusionForge seems not to have meta-data for the document (who uploaded what, what time, ...) -->If you know how to see that, I would be happy My suggestion is actually two-folded: - better naming so that it can be more easily identified, e.g. "IOT SE v0.x" is the main document, "IoT SA v0.x - 3.1.2.1 Comm Architecture" the respective sub-part, based on v0.x of the main document. /* But how do we know later that this part is already in the main document included ??? */ - suggestion structure according to our weekly mini-sprints (from Telco-To Telco) Idea is that after each Telco, we ... - create a directory for the next Telco, - add the latest version of the main document there (with all sub-parts updated) - add new contributions for the next Telco into this new directory - add agenda and meeting minutes as well (c) Agenda / meeting minutes As said above, we should have them on the Forge for fast access Actually, my greatest wish would be that do not use the Web folders for storing documents and editing. I would suggest to completely go to the SVN for that. - you have always local copies (much faster access) - one command to update all - LOCK-EDIT-UNLOCK pattern for joint editing of documents /* !!! very important to avoid the unnecessary, editing of merging sections of the document */ - history of accesses and updates We managed complete IPs with that! - Ernoe -----Original Appointment----- From: NAGELLEN Thierry RD-BIZZ-SOP Sent: Dienstag, 31. Mai 2011 15:21 To: NAGELLEN Thierry RD-BIZZ-SOP; fiware-iot at lists.fi-ware.eu Cc: Barnaghi P Dr (Electronic Eng); Ignacio Soler Jubert; Farkas, Lorant (NSN - HU/Budapest); AGHINA Xavier RD-MAPS-ISS; Haller, Stephan; Ernoe Kovacs Subject: Mis(e) ? jour: IoT weekly telco When: Occurs every Mittwoch effective 25.05.2011 from 09:30 to 11:00 GMT +0100 (Standard) / GMT +0200 (Daylight). Where: **** You can forward this email invitation to attendees **** Hello , L?r?nt Farkas invites you to attend this online meeting. Topic: IOT WP weekly Date: Every Wednesday, from Wednesday, 11 May 2011 to Wednesday, 26 March 2014 Time: 9:30, Europe Summer Time (Paris, GMT+02:00) Meeting Number: 709 472 921 Meeting Password: FI-WARE ------------------------------------------------------- To join the online meeting ------------------------------------------------------- 1. Go to0https://nsn.webex.com/nsn/j.php?ED=175018962&UID=0&PW=NY0EzYWM0ZTNk&RT=MTgjMjM%3D 2. Enter your name and email address. 3. Enter the meeting password: FI-WARE 4. Click "Join Now". To view in other time zones or languages, please click the link: https://nsn.webex.com/nsn/j.php?ED=175018962&UID=0&PW=NYzEzYWM0ZTNk&ORT=MTgjMjM%3D ------------------------------------------------------- NSN Voice Conference information Conference ID: 58465 PIN: 9012 Making a conference call - from the office: 8071870 (in Finland and Germany) - from out of office: +358 7180 71870 (in Finland) and +49 89 5159 43800 (in Germany) All out-of-office conference access numbers are listed in page . Country/Site Conference access number All sites From company office conference phone or desk phone 8071870. This number also works from company mobiles in several countries. See Internal Numbers page for more information. Argentina - Buenos Aires +54 11 5983 9400 (PRIMARY) or +54 11 4814 9373 Argentina - Cordoba +54 35 1568 2208 Australia - Sydney +61 28 014 7189 (PRIMARY) or +61 29 429 9664 Australia - Melbourne +61 38 739 4333 Austria +43 72 088 0245 Bahrain +97 31 619 9028 Belgium - Generic +32 1448 0116 Belgium - Diegem-Machelen +32 2710 3300 Brazil - Belo Horizonte +55 31 3956 0546 Brazil - Brazil +55 61 3717 2043 Brazil - Curitiba +55 41 3906 0826 Brazil - Manaus +55 92 3652 7576 Brazil - Rio De Janeiro +55 21 3958 0804 (PRIMARY) or +55 21 3431 1999 Brazil - Salvador +55 71 3717 5351 Brazil - Sao Paolo +55 11 5508 0630 Bulgaria +359 2491 7085 Canada - Ajax +1 90 5619 4346 Canada - Burnaby +1 60 4456 5897 Canada - Hamilton +1 905 581 0212 Canada - Mississauga +1 289 360 3950 Canada - Montreal +1 51 4789 9125 Canada - Ottawa +1 61 3800 0568 Chile - Santiago +56 2350 6485 China - Mainland +86 10 8405 5000 ext 1870 China - Beijing +86 10 8405 5000 ext 1870 China - Chengdu +86 28 8689 0188 ext 1870 China - Dongguan +86 0769 2240 2844 ext 1870 China - Guangzhou +86 20 8755 6190 ext 1870 China - Hangzhou +86 571 8722 0877 ext 1870 China - Hong Kong +852 259 70220 ext 1870 China - Kunming +86 871 362 2880 ext 1870 China - Shanghai +86 21 6101 1870 ext 1870 China - ShenZhen +86 755 8613 3688 ext 1870 China - Suzhou +86 512 6761 6166 ext 1870 China - Zhengzhou +86 371 6566 9768 ext 1870 Colombia +57 1640 7979 ext 444 Croatia +38 51 777 6122 Czech Republic +42 02 460 19300 Denmark +45 699 18450 (PRIMARY) or +45 3329 2882 Egypt +97 31 619 9028 (Bahrain nbr) Estonia +37 266 67297 Finland +358 7180 71870 France +33 17 061 7813 (PRIMARY) or +33 14 915 1553 Germany +49 89 5159 43800 Greece +30 21 1176 8207 (PRIMARY) or +30 21 1120 3677 Hungary - Budapest +36 17 009 888 Hungary - Kom?rom +36 20 884 2499 India 000 800 100 7777 Indonesia - Jakarta (Menara Mulia/Plaza Kuningan +62 21 2557 9102 Indonesia - Bandung +62 22 8427 5992 Indonesia - Medan +62 61 3001 2702 Indonesia - Semarang +62 24 3300 0702 Ireland +353 1526 2862 Israel +97 29 775 1700 Italy - Milan +39 024 004 2007 Italy - Rome +39 069 481 6656 Japan +81 3 4578 0230 (PRIMARY) or +81 3 5474 7979 Kuwait +97 31 619 9028 (Bahrain nbr) Latvia +37 16 765 2510 Lithuania +37 0 5205 8994 Luxembourg +352 2088 0106 Malaysia +60 323 029 009 Mexico - Mexico City +52 55 3686 9759 (PRIMARY) or +52 55 5261 7245 Mexico - Reynosa +52 89 9909 1555 Netherlands +31 79 346 5225 New Zealand +64 9306 6933 Norway - Oslo +47 21 548 223 Oman +97 31 619 9028 (Bahrain nbr) Pakistan +92 512 092 444 Panama +507 832 7981 Peru +51 1708 5370 (PRIMARY) or +51 1215 7650 Philippines +63 2754 1700 Poland - Warsaw +48 22 398 8116 Poland - Wroclaw +48 71 718 1215 Portugal +351 21 044 4698 Qatar +97 31 619 9028 (Bahrain nbr) Romania +40 36 440 3799 Russia +74 95 725 2706 Saudi Arabia +97 31 619 9028 (Bahrain nbr) Singapore +65 3103 1065 (PRIMARY) or +65 6723 2582 Slovakia +42 12 3300 6924 Slovenia +38 61 600 2713 South Africa - Johannesburg +27 1 0500 2221 South Africa - Pretoria +27 1 2004 2334 South Korea - Masan +82 5 5290 7690 South Korea - Seoul +82 2 2186 5088 Spain +349 1187 5929 Sweden +46 85 250 0862 (PRIMARY), +46 84 100 9299 Switzerland +41 44 279 7943 Taiwan +88 62 8175 9298 Thailand +66 2762 6750 Turkey +90 216 570 2345 Ukraine +38 044 520 2272 UK +44 12 5275 8334 UK - Camberley +44 12 5286 5849 UK - Church Crookham +44 12 5261 1100 UK - Huntingdon +44 14 8087 8220 (PRIMARY), +44 14 8044 4206 UK - London +44 20 3318 1924 United Arab Emirates +97 31 619 9028 (Bahrain nbr) USA - Alpharetta +1 770 871 3050 USA - Arizona +1 480 588 3748 USA - Atlanta +1 404 236 4550 USA - Atlanta Notheast +1 678 317 3165 USA - Austin/Round Rock +1 512 600 2027 USA - Belleville +1 973 547 7982 USA - Boca Raton +1 561 910 2843 USA - Boston +1 617 963 8320 (PRIMARY) or +1 781 993 4850 USA - Burlington +1 781 993 4850 USA - Calabasas +1 818 914 0215 USA - Canoga Park +1 818 914 0215 USA - Cary +1 919 655 1388 USA - Chelmsford/Littleton +1 978 679 0233 USA - Chicago +1 773 303 4710 USA - Dallas +1 214 269 7626 USA - Dallas/Fort Worth +1 214 270 0352 USA - Greenville, NC +1 252 329 1677 USA - Herndon +1 703 483 4485 USA - Johnson City +1 423 952 1545 USA - Kirkland +1 425 242 3113 USA - Miami +1 786 388 4150 or +1 786 329 7177 USA - Naperville +1 630 596 2203 USA - New Brunswick +1 732 579 6483 USA - New Century, KS +1 913 254 5900 USA - New York White Plains +1 914 368 0650 USA - New York Peekskill, White Plains +1 914 293 1885 USA - Palo Alto +1 650 644 1349 USA - Redmond +1 425 242 3113 USA - San Diego +1 858 769 5309 or +1 619 330 9699 USA - Sunnyvale +1 408 419 1750 USA - Washington D.C +1 202 552 4781 Vietnam +84 4 3724 6110 Yemen +97 31 619 9028 (Bahrain nbr) Please check and prioritize them. If there is no access number for your country then please use access numbers of the area where to the calling costs are lowest. ------------------------------------------------------- For assistance ------------------------------------------------------- 1. Go to https://nsn.webex.com/nsn/mc 2. On the left navigation bar, click "Support". You can contact me at: lorant.farkas at nsn.com To add this meeting to your calendar program (for example Microsoft Outlook), click this link: https://nsn.webex.com/nsn/j.php?ED=175018962&UID=0&ICS=MI&LD=1&RD=18&ST=1&SHA2=gVmoQ/CXj05nzcI-4TFgQ2qtqmAulzDfzoOWKpcyLyg=&RT=MTgjMjM%3D -------------- next part -------------- An HTML attachment was scrubbed... URL: From thierry.nagellen at orange-ftgroup.com Wed Jun 8 09:46:00 2011 From: thierry.nagellen at orange-ftgroup.com (thierry.nagellen at orange-ftgroup.com) Date: Wed, 8 Jun 2011 09:46:00 +0200 Subject: [Fiware-iot] Today's Telco: Start Time? / Repository Organization In-Reply-To: <8152E2132B13FB488CFD1947E2DEF19C13A5DCFF@DAPHNIS.office.hd> References: <8152E2132B13FB488CFD1947E2DEF19C13A5DCFF@DAPHNIS.office.hd> Message-ID: Hi Ernoe 10.00 for the meeting you're right We will discuss the point for the latest version based also on TID (Juanjo) request to have official version for revision. BR Thierry ________________________________ De : Ernoe Kovacs [mailto:Ernoe.Kovacs at neclab.eu] Envoy? : mercredi 8 juin 2011 09:40 ? : NAGELLEN Thierry RD-BIZZ-SOP; fiware-iot at lists.fi-ware.eu Cc : Barnaghi P Dr (Electronic Eng); Ignacio Soler Jubert; Farkas, Lorant (NSN - HU/Budapest); AGHINA Xavier RD-MAPS-ISS; Haller, Stephan Objet : Today's Telco: Start Time? / Repository Organization Thierry, all, for today's telco... a. I am bit confused. The Outlook meeting invitation is 10:00, the text says 9:30. --> I assume 10:00. Correct? b. Forge Organisation / Document Repository I had to catch up 2 weeks out of the office and found it hard to understand which is the latest version of the document, which is the main document and which is a sub-document. Also, FusionForge seems not to have meta-data for the document (who uploaded what, what time, ...) -->If you know how to see that, I would be happy My suggestion is actually two-folded: - better naming so that it can be more easily identified, e.g. "IOT SE v0.x" is the main document, "IoT SA v0.x - 3.1.2.1 Comm Architecture" the respective sub-part, based on v0.x of the main document. /* But how do we know later that this part is already in the main document included ??? */ - suggestion structure according to our weekly mini-sprints (from Telco-To Telco) Idea is that after each Telco, we ... - create a directory for the next Telco, - add the latest version of the main document there (with all sub-parts updated) - add new contributions for the next Telco into this new directory - add agenda and meeting minutes as well c. Agenda / meeting minutes As said above, we should have them on the Forge for fast access Actually, my greatest wish would be that do not use the Web folders for storing documents and editing. I would suggest to completely go to the SVN for that. - you have always local copies (much faster access) - one command to update all - LOCK-EDIT-UNLOCK pattern for joint editing of documents /* !!! very important to avoid the unnecessary, editing of merging sections of the document */ - history of accesses and updates We managed complete IPs with that! * Ernoe -----Original Appointment----- From: NAGELLEN Thierry RD-BIZZ-SOP Sent: Dienstag, 31. Mai 2011 15:21 To: NAGELLEN Thierry RD-BIZZ-SOP; fiware-iot at lists.fi-ware.eu Cc: Barnaghi P Dr (Electronic Eng); Ignacio Soler Jubert; Farkas, Lorant (NSN - HU/Budapest); AGHINA Xavier RD-MAPS-ISS; Haller, Stephan; Ernoe Kovacs Subject: Mis(e) ? jour: IoT weekly telco When: Occurs every Mittwoch effective 25.05.2011 from 09:30 to 11:00 GMT +0100 (Standard) / GMT +0200 (Daylight). Where: **** You can forward this email invitation to attendees **** Hello , L?r?nt Farkas invites you to attend this online meeting. Topic: IOT WP weekly Date: Every Wednesday, from Wednesday, 11 May 2011 to Wednesday, 26 March 2014 Time: 9:30, Europe Summer Time (Paris, GMT+02:00) Meeting Number: 709 472 921 Meeting Password: FI-WARE ------------------------------------------------------- To join the online meeting ------------------------------------------------------- 1. Go to0https://nsn.webex.com/nsn/j.php?ED=175018962&UID=0&PW=NY0EzYWM0ZTNk&RT=MTgjMjM%3D 2. Enter your name and email address. 3. Enter the meeting password: FI-WARE 4. Click "Join Now". To view in other time zones or languages, please click the link: https://nsn.webex.com/nsn/j.php?ED=175018962&UID=0&PW=NYzEzYWM0ZTNk&ORT=MTgjMjM%3D ------------------------------------------------------- NSN Voice Conference information Conference ID: 58465 PIN: 9012 Making a conference call - from the office: 8071870 (in Finland and Germany) - from out of office: +358 7180 71870 (in Finland) and +49 89 5159 43800 (in Germany) All out-of-office conference access numbers are listed in page . Country/Site Conference access number All sites From company office conference phone or desk phone 8071870. This number also works from company mobiles in several countries. See Internal Numbers page for more information. Argentina - Buenos Aires +54 11 5983 9400 (PRIMARY) or +54 11 4814 9373 Argentina - Cordoba +54 35 1568 2208 Australia - Sydney +61 28 014 7189 (PRIMARY) or +61 29 429 9664 Australia - Melbourne +61 38 739 4333 Austria +43 72 088 0245 Bahrain +97 31 619 9028 Belgium - Generic +32 1448 0116 Belgium - Diegem-Machelen +32 2710 3300 Brazil - Belo Horizonte +55 31 3956 0546 Brazil - Brazil +55 61 3717 2043 Brazil - Curitiba +55 41 3906 0826 Brazil - Manaus +55 92 3652 7576 Brazil - Rio De Janeiro +55 21 3958 0804 (PRIMARY) or +55 21 3431 1999 Brazil - Salvador +55 71 3717 5351 Brazil - Sao Paolo +55 11 5508 0630 Bulgaria +359 2491 7085 Canada - Ajax +1 90 5619 4346 Canada - Burnaby +1 60 4456 5897 Canada - Hamilton +1 905 581 0212 Canada - Mississauga +1 289 360 3950 Canada - Montreal +1 51 4789 9125 Canada - Ottawa +1 61 3800 0568 Chile - Santiago +56 2350 6485 China - Mainland +86 10 8405 5000 ext 1870 China - Beijing +86 10 8405 5000 ext 1870 China - Chengdu +86 28 8689 0188 ext 1870 China - Dongguan +86 0769 2240 2844 ext 1870 China - Guangzhou +86 20 8755 6190 ext 1870 China - Hangzhou +86 571 8722 0877 ext 1870 China - Hong Kong +852 259 70220 ext 1870 China - Kunming +86 871 362 2880 ext 1870 China - Shanghai +86 21 6101 1870 ext 1870 China - ShenZhen +86 755 8613 3688 ext 1870 China - Suzhou +86 512 6761 6166 ext 1870 China - Zhengzhou +86 371 6566 9768 ext 1870 Colombia +57 1640 7979 ext 444 Croatia +38 51 777 6122 Czech Republic +42 02 460 19300 Denmark +45 699 18450 (PRIMARY) or +45 3329 2882 Egypt +97 31 619 9028 (Bahrain nbr) Estonia +37 266 67297 Finland +358 7180 71870 France +33 17 061 7813 (PRIMARY) or +33 14 915 1553 Germany +49 89 5159 43800 Greece +30 21 1176 8207 (PRIMARY) or +30 21 1120 3677 Hungary - Budapest +36 17 009 888 Hungary - Kom?rom +36 20 884 2499 India 000 800 100 7777 Indonesia - Jakarta (Menara Mulia/Plaza Kuningan +62 21 2557 9102 Indonesia - Bandung +62 22 8427 5992 Indonesia - Medan +62 61 3001 2702 Indonesia - Semarang +62 24 3300 0702 Ireland +353 1526 2862 Israel +97 29 775 1700 Italy - Milan +39 024 004 2007 Italy - Rome +39 069 481 6656 Japan +81 3 4578 0230 (PRIMARY) or +81 3 5474 7979 Kuwait +97 31 619 9028 (Bahrain nbr) Latvia +37 16 765 2510 Lithuania +37 0 5205 8994 Luxembourg +352 2088 0106 Malaysia +60 323 029 009 Mexico - Mexico City +52 55 3686 9759 (PRIMARY) or +52 55 5261 7245 Mexico - Reynosa +52 89 9909 1555 Netherlands +31 79 346 5225 New Zealand +64 9306 6933 Norway - Oslo +47 21 548 223 Oman +97 31 619 9028 (Bahrain nbr) Pakistan +92 512 092 444 Panama +507 832 7981 Peru +51 1708 5370 (PRIMARY) or +51 1215 7650 Philippines +63 2754 1700 Poland - Warsaw +48 22 398 8116 Poland - Wroclaw +48 71 718 1215 Portugal +351 21 044 4698 Qatar +97 31 619 9028 (Bahrain nbr) Romania +40 36 440 3799 Russia +74 95 725 2706 Saudi Arabia +97 31 619 9028 (Bahrain nbr) Singapore +65 3103 1065 (PRIMARY) or +65 6723 2582 Slovakia +42 12 3300 6924 Slovenia +38 61 600 2713 South Africa - Johannesburg +27 1 0500 2221 South Africa - Pretoria +27 1 2004 2334 South Korea - Masan +82 5 5290 7690 South Korea - Seoul +82 2 2186 5088 Spain +349 1187 5929 Sweden +46 85 250 0862 (PRIMARY), +46 84 100 9299 Switzerland +41 44 279 7943 Taiwan +88 62 8175 9298 Thailand +66 2762 6750 Turkey +90 216 570 2345 Ukraine +38 044 520 2272 UK +44 12 5275 8334 UK - Camberley +44 12 5286 5849 UK - Church Crookham +44 12 5261 1100 UK - Huntingdon +44 14 8087 8220 (PRIMARY), +44 14 8044 4206 UK - London +44 20 3318 1924 United Arab Emirates +97 31 619 9028 (Bahrain nbr) USA - Alpharetta +1 770 871 3050 USA - Arizona +1 480 588 3748 USA - Atlanta +1 404 236 4550 USA - Atlanta Notheast +1 678 317 3165 USA - Austin/Round Rock +1 512 600 2027 USA - Belleville +1 973 547 7982 USA - Boca Raton +1 561 910 2843 USA - Boston +1 617 963 8320 (PRIMARY) or +1 781 993 4850 USA - Burlington +1 781 993 4850 USA - Calabasas +1 818 914 0215 USA - Canoga Park +1 818 914 0215 USA - Cary +1 919 655 1388 USA - Chelmsford/Littleton +1 978 679 0233 USA - Chicago +1 773 303 4710 USA - Dallas +1 214 269 7626 USA - Dallas/Fort Worth +1 214 270 0352 USA - Greenville, NC +1 252 329 1677 USA - Herndon +1 703 483 4485 USA - Johnson City +1 423 952 1545 USA - Kirkland +1 425 242 3113 USA - Miami +1 786 388 4150 or +1 786 329 7177 USA - Naperville +1 630 596 2203 USA - New Brunswick +1 732 579 6483 USA - New Century, KS +1 913 254 5900 USA - New York White Plains +1 914 368 0650 USA - New York Peekskill, White Plains +1 914 293 1885 USA - Palo Alto +1 650 644 1349 USA - Redmond +1 425 242 3113 USA - San Diego +1 858 769 5309 or +1 619 330 9699 USA - Sunnyvale +1 408 419 1750 USA - Washington D.C +1 202 552 4781 Vietnam +84 4 3724 6110 Yemen +97 31 619 9028 (Bahrain nbr) Please check and prioritize them. If there is no access number for your country then please use access numbers of the area where to the calling costs are lowest. ------------------------------------------------------- For assistance ------------------------------------------------------- 1. Go to https://nsn.webex.com/nsn/mc 2. On the left navigation bar, click "Support". You can contact me at: lorant.farkas at nsn.com To add this meeting to your calendar program (for example Microsoft Outlook), click this link: https://nsn.webex.com/nsn/j.php?ED=175018962&UID=0&ICS=MI&LD=1&RD=18&ST=1&SHA2=gVmoQ/CXj05nzcI-4TFgQ2qtqmAulzDfzoOWKpcyLyg=&RT=MTgjMjM%3D -------------- next part -------------- An HTML attachment was scrubbed... URL: From lorant.farkas at nsn.com Wed Jun 8 09:47:59 2011 From: lorant.farkas at nsn.com (Farkas, Lorant (NSN - HU/Budapest)) Date: Wed, 8 Jun 2011 10:47:59 +0300 Subject: [Fiware-iot] Today's Telco: Start Time? / Repository Organization In-Reply-To: References: <8152E2132B13FB488CFD1947E2DEF19C13A5DCFF@DAPHNIS.office.hd> Message-ID: <93D28BDF64839C468B848D14227151A201DEF182@FIESEXC014.nsn-intra.net> For the easy parts (meeting minutes) I very much agree and already created a folder. I also attempted to create forge tasks based on the action items from the minutes, the problem here is that not all project members are subscribed to forge yet. Br, Lorant ________________________________ From: ext thierry.nagellen at orange-ftgroup.com [mailto:thierry.nagellen at orange-ftgroup.com] Sent: Wednesday, June 08, 2011 9:46 AM To: Ernoe.Kovacs at neclab.eu; fiware-iot at lists.fi-ware.eu Cc: P.Barnaghi at surrey.ac.uk; ignacio.solerjubert at atosresearch.eu; Farkas, Lorant (NSN - HU/Budapest); xavier.aghina at orange-ftgroup.com; stephan.haller at sap.com Subject: RE: Today's Telco: Start Time? / Repository Organization Hi Ernoe 10.00 for the meeting you're right We will discuss the point for the latest version based also on TID (Juanjo) request to have official version for revision. BR Thierry ________________________________ De : Ernoe Kovacs [mailto:Ernoe.Kovacs at neclab.eu] Envoy? : mercredi 8 juin 2011 09:40 ? : NAGELLEN Thierry RD-BIZZ-SOP; fiware-iot at lists.fi-ware.eu Cc : Barnaghi P Dr (Electronic Eng); Ignacio Soler Jubert; Farkas, Lorant (NSN - HU/Budapest); AGHINA Xavier RD-MAPS-ISS; Haller, Stephan Objet : Today's Telco: Start Time? / Repository Organization Thierry, all, for today's telco... a. I am bit confused. The Outlook meeting invitation is 10:00, the text says 9:30. --> I assume 10:00. Correct? b. Forge Organisation / Document Repository I had to catch up 2 weeks out of the office and found it hard to understand which is the latest version of the document, which is the main document and which is a sub-document. Also, FusionForge seems not to have meta-data for the document (who uploaded what, what time, ...) -->If you know how to see that, I would be happy My suggestion is actually two-folded: - better naming so that it can be more easily identified, e.g. "IOT SE v0.x" is the main document, "IoT SA v0.x - 3.1.2.1 Comm Architecture" the respective sub-part, based on v0.x of the main document. /* But how do we know later that this part is already in the main document included ??? */ - suggestion structure according to our weekly mini-sprints (from Telco-To Telco) Idea is that after each Telco, we ... - create a directory for the next Telco, - add the latest version of the main document there (with all sub-parts updated) - add new contributions for the next Telco into this new directory - add agenda and meeting minutes as well c. Agenda / meeting minutes As said above, we should have them on the Forge for fast access Actually, my greatest wish would be that do not use the Web folders for storing documents and editing. I would suggest to completely go to the SVN for that. - you have always local copies (much faster access) - one command to update all - LOCK-EDIT-UNLOCK pattern for joint editing of documents /* !!! very important to avoid the unnecessary, editing of merging sections of the document */ - history of accesses and updates We managed complete IPs with that! * Ernoe -----Original Appointment----- From: NAGELLEN Thierry RD-BIZZ-SOP Sent: Dienstag, 31. Mai 2011 15:21 To: NAGELLEN Thierry RD-BIZZ-SOP; fiware-iot at lists.fi-ware.eu Cc: Barnaghi P Dr (Electronic Eng); Ignacio Soler Jubert; Farkas, Lorant (NSN - HU/Budapest); AGHINA Xavier RD-MAPS-ISS; Haller, Stephan; Ernoe Kovacs Subject: Mis(e) ? jour: IoT weekly telco When: Occurs every Mittwoch effective 25.05.2011 from 09:30 to 11:00 GMT +0100 (Standard) / GMT +0200 (Daylight). Where: **** You can forward this email invitation to attendees **** Hello , L?r?nt Farkas invites you to attend this online meeting. Topic: IOT WP weekly Date: Every Wednesday, from Wednesday, 11 May 2011 to Wednesday, 26 March 2014 Time: 9:30, Europe Summer Time (Paris, GMT+02:00) Meeting Number: 709 472 921 Meeting Password: FI-WARE ------------------------------------------------------- To join the online meeting ------------------------------------------------------- 1. Go to0https://nsn.webex.com/nsn/j.php?ED=175018962&UID=0&PW=NY0EzYWM0ZTNk&RT=MTgjMjM%3D 2. Enter your name and email address. 3. Enter the meeting password: FI-WARE 4. Click "Join Now". To view in other time zones or languages, please click the link: https://nsn.webex.com/nsn/j.php?ED=175018962&UID=0&PW=NYzEzYWM0ZTNk&ORT=MTgjMjM%3D ------------------------------------------------------- NSN Voice Conference information Conference ID: 58465 PIN: 9012 Making a conference call - from the office: 8071870 (in Finland and Germany) - from out of office: +358 7180 71870 (in Finland) and +49 89 5159 43800 (in Germany) All out-of-office conference access numbers are listed in page . Country/Site Conference access number All sites From company office conference phone or desk phone 8071870. This number also works from company mobiles in several countries. See Internal Numbers page for more information. Argentina - Buenos Aires +54 11 5983 9400 (PRIMARY) or +54 11 4814 9373 Argentina - Cordoba +54 35 1568 2208 Australia - Sydney +61 28 014 7189 (PRIMARY) or +61 29 429 9664 Australia - Melbourne +61 38 739 4333 Austria +43 72 088 0245 Bahrain +97 31 619 9028 Belgium - Generic +32 1448 0116 Belgium - Diegem-Machelen +32 2710 3300 Brazil - Belo Horizonte +55 31 3956 0546 Brazil - Brazil +55 61 3717 2043 Brazil - Curitiba +55 41 3906 0826 Brazil - Manaus +55 92 3652 7576 Brazil - Rio De Janeiro +55 21 3958 0804 (PRIMARY) or +55 21 3431 1999 Brazil - Salvador +55 71 3717 5351 Brazil - Sao Paolo +55 11 5508 0630 Bulgaria +359 2491 7085 Canada - Ajax +1 90 5619 4346 Canada - Burnaby +1 60 4456 5897 Canada - Hamilton +1 905 581 0212 Canada - Mississauga +1 289 360 3950 Canada - Montreal +1 51 4789 9125 Canada - Ottawa +1 61 3800 0568 Chile - Santiago +56 2350 6485 China - Mainland +86 10 8405 5000 ext 1870 China - Beijing +86 10 8405 5000 ext 1870 China - Chengdu +86 28 8689 0188 ext 1870 China - Dongguan +86 0769 2240 2844 ext 1870 China - Guangzhou +86 20 8755 6190 ext 1870 China - Hangzhou +86 571 8722 0877 ext 1870 China - Hong Kong +852 259 70220 ext 1870 China - Kunming +86 871 362 2880 ext 1870 China - Shanghai +86 21 6101 1870 ext 1870 China - ShenZhen +86 755 8613 3688 ext 1870 China - Suzhou +86 512 6761 6166 ext 1870 China - Zhengzhou +86 371 6566 9768 ext 1870 Colombia +57 1640 7979 ext 444 Croatia +38 51 777 6122 Czech Republic +42 02 460 19300 Denmark +45 699 18450 (PRIMARY) or +45 3329 2882 Egypt +97 31 619 9028 (Bahrain nbr) Estonia +37 266 67297 Finland +358 7180 71870 France +33 17 061 7813 (PRIMARY) or +33 14 915 1553 Germany +49 89 5159 43800 Greece +30 21 1176 8207 (PRIMARY) or +30 21 1120 3677 Hungary - Budapest +36 17 009 888 Hungary - Kom?rom +36 20 884 2499 India 000 800 100 7777 Indonesia - Jakarta (Menara Mulia/Plaza Kuningan +62 21 2557 9102 Indonesia - Bandung +62 22 8427 5992 Indonesia - Medan +62 61 3001 2702 Indonesia - Semarang +62 24 3300 0702 Ireland +353 1526 2862 Israel +97 29 775 1700 Italy - Milan +39 024 004 2007 Italy - Rome +39 069 481 6656 Japan +81 3 4578 0230 (PRIMARY) or +81 3 5474 7979 Kuwait +97 31 619 9028 (Bahrain nbr) Latvia +37 16 765 2510 Lithuania +37 0 5205 8994 Luxembourg +352 2088 0106 Malaysia +60 323 029 009 Mexico - Mexico City +52 55 3686 9759 (PRIMARY) or +52 55 5261 7245 Mexico - Reynosa +52 89 9909 1555 Netherlands +31 79 346 5225 New Zealand +64 9306 6933 Norway - Oslo +47 21 548 223 Oman +97 31 619 9028 (Bahrain nbr) Pakistan +92 512 092 444 Panama +507 832 7981 Peru +51 1708 5370 (PRIMARY) or +51 1215 7650 Philippines +63 2754 1700 Poland - Warsaw +48 22 398 8116 Poland - Wroclaw +48 71 718 1215 Portugal +351 21 044 4698 Qatar +97 31 619 9028 (Bahrain nbr) Romania +40 36 440 3799 Russia +74 95 725 2706 Saudi Arabia +97 31 619 9028 (Bahrain nbr) Singapore +65 3103 1065 (PRIMARY) or +65 6723 2582 Slovakia +42 12 3300 6924 Slovenia +38 61 600 2713 South Africa - Johannesburg +27 1 0500 2221 South Africa - Pretoria +27 1 2004 2334 South Korea - Masan +82 5 5290 7690 South Korea - Seoul +82 2 2186 5088 Spain +349 1187 5929 Sweden +46 85 250 0862 (PRIMARY), +46 84 100 9299 Switzerland +41 44 279 7943 Taiwan +88 62 8175 9298 Thailand +66 2762 6750 Turkey +90 216 570 2345 Ukraine +38 044 520 2272 UK +44 12 5275 8334 UK - Camberley +44 12 5286 5849 UK - Church Crookham +44 12 5261 1100 UK - Huntingdon +44 14 8087 8220 (PRIMARY), +44 14 8044 4206 UK - London +44 20 3318 1924 United Arab Emirates +97 31 619 9028 (Bahrain nbr) USA - Alpharetta +1 770 871 3050 USA - Arizona +1 480 588 3748 USA - Atlanta +1 404 236 4550 USA - Atlanta Notheast +1 678 317 3165 USA - Austin/Round Rock +1 512 600 2027 USA - Belleville +1 973 547 7982 USA - Boca Raton +1 561 910 2843 USA - Boston +1 617 963 8320 (PRIMARY) or +1 781 993 4850 USA - Burlington +1 781 993 4850 USA - Calabasas +1 818 914 0215 USA - Canoga Park +1 818 914 0215 USA - Cary +1 919 655 1388 USA - Chelmsford/Littleton +1 978 679 0233 USA - Chicago +1 773 303 4710 USA - Dallas +1 214 269 7626 USA - Dallas/Fort Worth +1 214 270 0352 USA - Greenville, NC +1 252 329 1677 USA - Herndon +1 703 483 4485 USA - Johnson City +1 423 952 1545 USA - Kirkland +1 425 242 3113 USA - Miami +1 786 388 4150 or +1 786 329 7177 USA - Naperville +1 630 596 2203 USA - New Brunswick +1 732 579 6483 USA - New Century, KS +1 913 254 5900 USA - New York White Plains +1 914 368 0650 USA - New York Peekskill, White Plains +1 914 293 1885 USA - Palo Alto +1 650 644 1349 USA - Redmond +1 425 242 3113 USA - San Diego +1 858 769 5309 or +1 619 330 9699 USA - Sunnyvale +1 408 419 1750 USA - Washington D.C +1 202 552 4781 Vietnam +84 4 3724 6110 Yemen +97 31 619 9028 (Bahrain nbr) Please check and prioritize them. If there is no access number for your country then please use access numbers of the area where to the calling costs are lowest. ------------------------------------------------------- For assistance ------------------------------------------------------- 1. Go to https://nsn.webex.com/nsn/mc 2. On the left navigation bar, click "Support". You can contact me at: lorant.farkas at nsn.com To add this meeting to your calendar program (for example Microsoft Outlook), click this link: https://nsn.webex.com/nsn/j.php?ED=175018962&UID=0&ICS=MI&LD=1&RD=18&ST=1&SHA2=gVmoQ/CXj05nzcI-4TFgQ2qtqmAulzDfzoOWKpcyLyg=&RT=MTgjMjM%3D -------------- next part -------------- An HTML attachment was scrubbed... URL: From Ernoe.Kovacs at neclab.eu Wed Jun 8 11:42:13 2011 From: Ernoe.Kovacs at neclab.eu (Ernoe Kovacs) Date: Wed, 8 Jun 2011 09:42:13 +0000 Subject: [Fiware-iot] FIWare WP5 description In-Reply-To: References: <8152E2132B13FB488CFD1947E2DEF19C13A5DCFF@DAPHNIS.office.hd> Message-ID: <8152E2132B13FB488CFD1947E2DEF19C13A5DE9F@DAPHNIS.office.hd> Thierry, all, (a) short question: can we have a look at what other WPs are doing? I think it could be good to see how they deal with this complex process. Any hint where I can access that? (b) WP5 Work I am also not sure what is our main problem to tackle: (a) Interactions with the other WPs? - Purpose of this? - Level of Detail (Example: Easy to say I need security, more complex to say I need "secure ids" or "distributed policy mng", even harder to say "a cryptographic secured identification schema") (b) WP internal architecture - I see pictures poping up right and left, all different, many not agreed on the large scope - internal interfaces You said you need to understand these internal interfaces. - Why? What purpose does it serve in the document? (c) Concept View - You said we need to explain to the UC project what they can expect. This is a highlevel concept view, ideally with some good terms and simple pictures. (d) Detailed Enabler View - which enablers, which sub-systems, which APIs, wich information model (e) Unique Selling Points - Again something different, and also completely different to present. Sorry for nasty question, but I am confused. - Ern? From lorant.farkas at nsn.com Wed Jun 8 12:42:51 2011 From: lorant.farkas at nsn.com (Farkas, Lorant (NSN - HU/Budapest)) Date: Wed, 8 Jun 2011 13:42:51 +0300 Subject: [Fiware-iot] FIWare WP5 description In-Reply-To: <8152E2132B13FB488CFD1947E2DEF19C13A5DE9F@DAPHNIS.office.hd> References: <8152E2132B13FB488CFD1947E2DEF19C13A5DCFF@DAPHNIS.office.hd> <8152E2132B13FB488CFD1947E2DEF19C13A5DE9F@DAPHNIS.office.hd> Message-ID: <93D28BDF64839C468B848D14227151A201DEF3C0@FIESEXC014.nsn-intra.net> Ern?, (a) The way I see is to ask for access to the other WP projects, or another one would be to look at the contributions other WP-s are submitting to the FI-WARE docman. I will try to ask around from people in the security WP because one of them sits next to me. (b) (a) Avoid the functionality overlap the second example rather than the first (b) You see every version in Forge. The first version was created yesterday, the second version today. In this document we describe the features of the generic enablers, as well as the architectural components. The interfaces will have open specifications publicised to the usage area projects. We should at least have an idea at this stage what the interface does (c) Yes, if you have a better proposal feel free to propose and we can change it. At the time I created this there was no comment from anyone (d) "Then, a number of paragraphs should come describing the GE. This will free style, but we suggest that you highlight the critical attributes of the GE and establish any relevant comparison with existing products along the description. It would be nice to have some figure which helps to understand the description." (e) Example (see page 4 of https://forge.fi-ware.eu/docman/view.php/7/48/FI-WARE+High-Level+Description+11-06-1+v0.4.doc) * Middleware component for unified access to distributed and heterogeneous repositories (with particular focus on support for multimedia repositories) * Provisioning of metadata format interoperability via schema transformation * Abstraction from heterogeneous retrieval paradigms in the underlying data bases and search engines Br, Lorant -----Original Message----- From: ext Ernoe Kovacs [mailto:Ernoe.Kovacs at neclab.eu] Sent: Wednesday, June 08, 2011 11:42 AM To: thierry.nagellen at orange-ftgroup.com; fiware-iot at lists.fi-ware.eu Cc: P.Barnaghi at surrey.ac.uk; ignacio.solerjubert at atosresearch.eu; Farkas, Lorant (NSN - HU/Budapest); xavier.aghina at orange-ftgroup.com; stephan.haller at sap.com Subject: FIWare WP5 description Thierry, all, (a) short question: can we have a look at what other WPs are doing? I think it could be good to see how they deal with this complex process. Any hint where I can access that? (b) WP5 Work I am also not sure what is our main problem to tackle: (a) Interactions with the other WPs? - Purpose of this? - Level of Detail (Example: Easy to say I need security, more complex to say I need "secure ids" or "distributed policy mng", even harder to say "a cryptographic secured identification schema") (b) WP internal architecture - I see pictures poping up right and left, all different, many not agreed on the large scope - internal interfaces You said you need to understand these internal interfaces. - Why? What purpose does it serve in the document? (c) Concept View - You said we need to explain to the UC project what they can expect. This is a highlevel concept view, ideally with some good terms and simple pictures. (d) Detailed Enabler View - which enablers, which sub-systems, which APIs, wich information model (e) Unique Selling Points - Again something different, and also completely different to present. Sorry for nasty question, but I am confused. - Ern? -------------- next part -------------- An HTML attachment was scrubbed... URL: From thierry.nagellen at orange-ftgroup.com Wed Jun 8 13:42:35 2011 From: thierry.nagellen at orange-ftgroup.com (thierry.nagellen at orange-ftgroup.com) Date: Wed, 8 Jun 2011 13:42:35 +0200 Subject: [Fiware-iot] FIWare WP5 description In-Reply-To: <93D28BDF64839C468B848D14227151A201DEF3C0@FIESEXC014.nsn-intra.net> References: <8152E2132B13FB488CFD1947E2DEF19C13A5DCFF@DAPHNIS.office.hd> <8152E2132B13FB488CFD1947E2DEF19C13A5DE9F@DAPHNIS.office.hd> <93D28BDF64839C468B848D14227151A201DEF3C0@FIESEXC014.nsn-intra.net> Message-ID: Hi Ern? There are no nasty question, just some collaboration difficulties for example to are aware in the same time about the last version of the document. Till now, the Task leaders have sent the architecture pictures to the IoT mainling list so you hyave received them from last Wednesday to yesterday afternoon for the last version of Gian Piero so check your emails and your spam or junk folder, maybe mailing list emails are not well managed. To complete Lorant answer, we are providing a part of the global high-level architecture deliverable of FI-Ware so we have: 1- to provide a comprehensive dexcription of what we expect to deliever to facilitate future UA projects requirements 2- to be correctly integrated with the other technical chapters of FI-Ware At this moment, as we do not have the final description of the other parts from the other chapters we can define the links we the other chapter on general basys but just write "will interact with Security, privacy & trust" is not enough but "will be supported by Sec Privacy & Trust to provide relevant mechanisms for access rights" describe what kind of privacy features we are expecting. Between the 4 GEs of IoT chapter, we have to avoid functionality overlap and miss some other. The process in in 3 steps: * based on the DoW improve this high-level description from architectural point of view (end of June) * July to September: define features backlog, so give more details, features identification and priorities should be established * July to September: map existing assets on the architecture we have defined previously to be ready to develop in September or October We will have feedback from UA projects, which are defining scenarios at this moment, between July and September (but not mandataory by the program) but surely between October and December. So we will revised the picture we are building now several times. So to improve the work, we need all written contributions and can let some open question marks also... But we have to identified them! And for the end of this year we need a clear identification of what is missing because we have the open call to find new partners for the missing parts. So, as you can check that each 3 months we have specific issues and results to provide the best picture, open specifications and first middleware modules. BR Thierry ________________________________ De : Farkas, Lorant (NSN - HU/Budapest) [mailto:lorant.farkas at nsn.com] Envoy? : mercredi 8 juin 2011 12:43 ? : ext Ernoe Kovacs; NAGELLEN Thierry RD-BIZZ-SOP; fiware-iot at lists.fi-ware.eu Cc : P.Barnaghi at surrey.ac.uk; ignacio.solerjubert at atosresearch.eu; AGHINA Xavier RD-MAPS-ISS; stephan.haller at sap.com Objet : RE: FIWare WP5 description Ern?, (a) The way I see is to ask for access to the other WP projects, or another one would be to look at the contributions other WP-s are submitting to the FI-WARE docman. I will try to ask around from people in the security WP because one of them sits next to me. (b) (a) Avoid the functionality overlap the second example rather than the first (b) You see every version in Forge. The first version was created yesterday, the second version today. In this document we describe the features of the generic enablers, as well as the architectural components. The interfaces will have open specifications publicised to the usage area projects. We should at least have an idea at this stage what the interface does (c) Yes, if you have a better proposal feel free to propose and we can change it. At the time I created this there was no comment from anyone (d) "Then, a number of paragraphs should come describing the GE. This will free style, but we suggest that you highlight the critical attributes of the GE and establish any relevant comparison with existing products along the description. It would be nice to have some figure which helps to understand the description." (e) Example (see page 4 of https://forge.fi-ware.eu/docman/view.php/7/48/FI-WARE+High-Level+Description+11-06-1+v0.4.doc ) * Middleware component for unified access to distributed and heterogeneous repositories (with particular focus on support for multimedia repositories) * Provisioning of metadata format interoperability via schema transformation * Abstraction from heterogeneous retrieval paradigms in the underlying data bases and search engines Br, Lorant -----Original Message----- From: ext Ernoe Kovacs [mailto:Ernoe.Kovacs at neclab.eu ] Sent: Wednesday, June 08, 2011 11:42 AM To: thierry.nagellen at orange-ftgroup.com; fiware-iot at lists.fi-ware.eu Cc: P.Barnaghi at surrey.ac.uk; ignacio.solerjubert at atosresearch.eu; Farkas, Lorant (NSN - HU/Budapest); xavier.aghina at orange-ftgroup.com; stephan.haller at sap.com Subject: FIWare WP5 description Thierry, all, (a) short question: can we have a look at what other WPs are doing? I think it could be good to see how they deal with this complex process. Any hint where I can access that? (b) WP5 Work I am also not sure what is our main problem to tackle: (a) Interactions with the other WPs? - Purpose of this? - Level of Detail (Example: Easy to say I need security, more complex to say I need "secure ids" or "distributed policy mng", even harder to say "a cryptographic secured identification schema") (b) WP internal architecture - I see pictures poping up right and left, all different, many not agreed on the large scope - internal interfaces You said you need to understand these internal interfaces. - Why? What purpose does it serve in the document? (c) Concept View - You said we need to explain to the UC project what they can expect. This is a highlevel concept view, ideally with some good terms and simple pictures. (d) Detailed Enabler View - which enablers, which sub-systems, which APIs, wich information model (e) Unique Selling Points - Again something different, and also completely different to present. Sorry for nasty question, but I am confused. - Ern? -------------- next part -------------- An HTML attachment was scrubbed... URL: From thierry.nagellen at orange-ftgroup.com Wed Jun 8 15:11:53 2011 From: thierry.nagellen at orange-ftgroup.com (thierry.nagellen at orange-ftgroup.com) Date: Wed, 8 Jun 2011 15:11:53 +0200 Subject: [Fiware-iot] Weekly meeting minutes Message-ID: Dear all Here are the minutes of our morning meeting <> BR Thierry -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: IoT-Minutes-Telco-06082011.doc Type: application/msword Size: 54272 bytes Desc: IoT-Minutes-Telco-06082011.doc URL: From sabrina.guerra at telecomitalia.it Wed Jun 8 18:18:25 2011 From: sabrina.guerra at telecomitalia.it (Guerra Sabrina) Date: Wed, 8 Jun 2011 18:18:25 +0200 Subject: [Fiware-iot] IoT Communication: new version of the architecture description Message-ID: <36A93B31228D3B49B691AD31652BCAE9A533820B2E@GRFMBX702BA020.griffon.local> Hi Thierry, we just tried to submit on Fusion Forge a revised version of our contribution (IoT Communication-Architecture-Description-v0.2.doc) but I do not know if it is available (Fusion Forge says: pending state (need validation)). We see you changed the architecture picture we sent you. Some changes are ok, but we have comments on other, so we modified the picture in the contribution, and we updated the description reflecting the new picture, and we will explain in this e-mail the differences between your picture and ours. You put an arrow between Connectivity Management and IoT Resources Management and between Content Control and IoT Resources Management, in this way it seems a message coming from a Device or a Gateway can be passed from the Front-end either to the Connectivity Management block or to the Content Control block and from there can be passed to the IoT Resources Management, like if there are 2 different paths leading from IoT Communication to IoT Resoureces Management. While we think all the messages coming from a Device or a Gateway are received by the Front-end block and then passed from the Front-end to the IoT Resources Management GE. The other blocks (Connectivity Management and Content Control) group functionalities that are used by the Front-end on the traffic coming from, and/or going to, Devices and Gateways. For this reason we put a single arrow between the Front-End and the Iot Resources Management deleting the other two between Connectivity Management and Content Control and IoT Resources Management (and also the arrow between Connectivity Management and Content Control, since there are no interactions between these 2 blocks). We also deleted the interaction with the IoT Data Handling GE, since we believe the Data Handling will be used only by the IoT Resources Management. Well, at least we cannot think of a case where IoT Communication should access directly to the resources data. Finally we changed the aspect of the arrow between Interfaces to the Networks and the Front-end and of the 2 blocks Access Policy Control and Quality of Service Control. The first one to show that the interaction between the Front-end and the Interfaces to the Network GE is not at run-time, ItoN will define the protocols that will be used in the communication between the platform and the Devices and Gateways, but these protocols will be implemented directly in the Connection Protocol Adapters. The second one to show that the 2 blocks Access Policy Control and Quality of Service Control can be implemented either in the IoT Communication or in the IoT Resources Management, if implemented in the IoT communication the controls will be applied in advance and not allowed messages will be rejected early, otherwise if implemented in the IoT Resources Management all the traffic will be passed to the IoT Resources Management that will provide to apply the controls. Of course if these controls (access rights and quality of services) have to be applied also on traffic coming from applications (besides traffic coming from devices and gateways) it is more convenient implement them in the IoT Resources Management. We hope we have been clear in my explanation, in any case please feel free to ask for clarifications. Bye, Sabrina and Gian Piero 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: -------------- 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: From lorant.farkas at nsn.com Wed Jun 8 19:55:36 2011 From: lorant.farkas at nsn.com (Farkas, Lorant (NSN - HU/Budapest)) Date: Wed, 8 Jun 2011 20:55:36 +0300 Subject: [Fiware-iot] IoT Communication: new version of the architecturedescription In-Reply-To: <36A93B31228D3B49B691AD31652BCAE9A533820B2E@GRFMBX702BA020.griffon.local> References: <36A93B31228D3B49B691AD31652BCAE9A533820B2E@GRFMBX702BA020.griffon.local> Message-ID: <93D28BDF64839C468B848D14227151A201DEF6F1@FIESEXC014.nsn-intra.net> Hi Sabrina, Thanks for the submission. The reason for the pending state was that you were not registered to the IoT project but only forge. Now I registered you to the project so whatever you submit will be visible. I looked for Gian Piero as well, he seems not to be registered to forge, so Gian Piero please register there. As for the content of the submission we will review this with Thierry soon and give feedback. I would like to ask you to submit to forge the "master copy" of your architecture figure (the ppt) so that if we want to propose changes, we don't need to redraw it. 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 Guerra Sabrina Sent: Wednesday, June 08, 2011 6:18 PM To: 'fiware-iot at lists.fi-ware.eu' Subject: [Fiware-iot] IoT Communication: new version of the architecturedescription Hi Thierry, we just tried to submit on Fusion Forge a revised version of our contribution (IoT Communication-Architecture-Description-v0.2.doc) but I do not know if it is available (Fusion Forge says: pending state (need validation)). We see you changed the architecture picture we sent you. Some changes are ok, but we have comments on other, so we modified the picture in the contribution, and we updated the description reflecting the new picture, and we will explain in this e-mail the differences between your picture and ours. You put an arrow between Connectivity Management and IoT Resources Management and between Content Control and IoT Resources Management, in this way it seems a message coming from a Device or a Gateway can be passed from the Front-end either to the Connectivity Management block or to the Content Control block and from there can be passed to the IoT Resources Management, like if there are 2 different paths leading from IoT Communication to IoT Resoureces Management. While we think all the messages coming from a Device or a Gateway are received by the Front-end block and then passed from the Front-end to the IoT Resources Management GE. The other blocks (Connectivity Management and Content Control) group functionalities that are used by the Front-end on the traffic coming from, and/or going to, Devices and Gateways. For this reason we put a single arrow between the Front-End and the Iot Resources Management deleting the other two between Connectivity Management and Content Control and IoT Resources Management (and also the arrow between Connectivity Management and Content Control, since there are no interactions between these 2 blocks). We also deleted the interaction with the IoT Data Handling GE, since we believe the Data Handling will be used only by the IoT Resources Management. Well, at least we cannot think of a case where IoT Communication should access directly to the resources data. Finally we changed the aspect of the arrow between Interfaces to the Networks and the Front-end and of the 2 blocks Access Policy Control and Quality of Service Control. The first one to show that the interaction between the Front-end and the Interfaces to the Network GE is not at run-time, ItoN will define the protocols that will be used in the communication between the platform and the Devices and Gateways, but these protocols will be implemented directly in the Connection Protocol Adapters. The second one to show that the 2 blocks Access Policy Control and Quality of Service Control can be implemented either in the IoT Communication or in the IoT Resources Management, if implemented in the IoT communication the controls will be applied in advance and not allowed messages will be rejected early, otherwise if implemented in the IoT Resources Management all the traffic will be passed to the IoT Resources Management that will provide to apply the controls. Of course if these controls (access rights and quality of services) have to be applied also on traffic coming from applications (besides traffic coming from devices and gateways) it is more convenient implement them in the IoT Resources Management. We hope we have been clear in my explanation, in any case please feel free to ask for clarifications. Bye, Sabrina and Gian Piero 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. -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- 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: From ignacio.solerjubert at atosresearch.eu Thu Jun 9 11:57:53 2011 From: ignacio.solerjubert at atosresearch.eu (Ignacio Soler Jubert) Date: Thu, 9 Jun 2011 11:57:53 +0200 Subject: [Fiware-iot] iot-Week Presentation In-Reply-To: References: Message-ID: Dear All, Yesterday I have done the presentation of WP5 of FIWARE in the iot-Week. It did like to people. And generate so many question about Generic Enablers and Specific/Domain Enablers. Which is the difference? How we identify the generic vs specific and where is the scope of them and if a specific enabler could potentially become a Generic one? Best regards, Ignacio. Ignacio Soler Head of Smart Objects Laboratory ATOS Research and Innovation Diagonal, 200 - 08018 Barcelona (SPAIN) Tel: +34 934 861 818 , --> NEW CELLULAR: +34 675 620 202 ignacio.solerjubert at atosorigin.com www.atosresearch.eu ------------------------------------------------------------------ This e-mail and the documents attached are confidential and intended solely for the addressee; it may also be privileged. If you receive this e-mail in error, please notify the sender immediately and destroy it. As its integrity cannot be secured on the Internet, the Atos Origin group liability cannot be triggered for the message content. Although the sender endeavours to maintain a computer virus-free network, the sender does not warrant that this transmission is virus-free and will not be liable for any damages resulting from any virus transmitted. Este mensaje y los ficheros adjuntos pueden contener informacion confidencial destinada solamente a la(s) persona(s) mencionadas anteriormente pueden estar protegidos por secreto profesional. Si usted recibe este correo electronico por error, gracias por informar inmediatamente al remitente y destruir el mensaje. Al no estar asegurada la integridad de este mensaje sobre la red, Atos Origin no se hace responsable por su contenido. Su contenido no constituye ningun compromiso para el grupo Atos Origin, salvo ratificacion escrita por ambas partes. Aunque se esfuerza al maximo por mantener su red libre de virus, el emisor no puede garantizar nada al respecto y no sera responsable de cualesquiera danos que puedan resultar de una transmision de virus. ------------------------------------------------------------------ -------------- next part -------------- An HTML attachment was scrubbed... URL: From P.Barnaghi at surrey.ac.uk Thu Jun 9 15:13:09 2011 From: P.Barnaghi at surrey.ac.uk (P.Barnaghi at surrey.ac.uk) Date: Thu, 9 Jun 2011 14:13:09 +0100 Subject: [Fiware-iot] iot-Week Presentation In-Reply-To: References: Message-ID: Dear Ignacio, Thanks for this. I think specific enablers are a subset of Generic enablers; In WP5, the focus is on IoT communication, data handling and service enablers; The Generic models will provide common functions and interfaces and for specific scenarios some features might be customised and/or added depending on the application and environment. Best regards, Payam ________________________________ From: fiware-iot-bounces at lists.fi-ware.eu [mailto:fiware-iot-bounces at lists.fi-ware.eu] On Behalf Of Ignacio Soler Jubert Sent: 09 June 2011 10:58 To: thierry.nagellen at orange-ftgroup.com; fiware-iot at lists.fi-ware.eu Subject: [Fiware-iot] iot-Week Presentation Dear All, Yesterday I have done the presentation of WP5 of FIWARE in the iot-Week. It did like to people. And generate so many question about Generic Enablers and Specific/Domain Enablers. Which is the difference? How we identify the generic vs specific and where is the scope of them and if a specific enabler could potentially become a Generic one? Best regards, Ignacio. Ignacio Soler Head of Smart Objects Laboratory ATOS Research and Innovation Diagonal, 200 - 08018 Barcelona (SPAIN) Tel: +34 934 861 818 , --> NEW CELLULAR: +34 675 620 202 ignacio.solerjubert at atosorigin.com www.atosresearch.eu ------------------------------------------------------------------ This e-mail and the documents attached are confidential and intended solely for the addressee; it may also be privileged. If you receive this e-mail in error, please notify the sender immediately and destroy it. As its integrity cannot be secured on the Internet, the Atos Origin group liability cannot be triggered for the message content. Although the sender endeavours to maintain a computer virus-free network, the sender does not warrant that this transmission is virus-free and will not be liable for any damages resulting from any virus transmitted. Este mensaje y los ficheros adjuntos pueden contener informacion confidencial destinada solamente a la(s) persona(s) mencionadas anteriormente pueden estar protegidos por secreto profesional. Si usted recibe este correo electronico por error, gracias por informar inmediatamente al remitente y destruir el mensaje. Al no estar asegurada la integridad de este mensaje sobre la red, Atos Origin no se hace responsable por su contenido. Su contenido no constituye ningun compromiso para el grupo Atos Origin, salvo ratificacion escrita por ambas partes. Aunque se esfuerza al maximo por mantener su red libre de virus, el emisor no puede garantizar nada al respecto y no sera responsable de cualesquiera danos que puedan resultar de una transmision de virus. ------------------------------------------------------------------ -------------- next part -------------- An HTML attachment was scrubbed... URL: From thierry.nagellen at orange-ftgroup.com Thu Jun 9 15:38:05 2011 From: thierry.nagellen at orange-ftgroup.com (thierry.nagellen at orange-ftgroup.com) Date: Thu, 9 Jun 2011 15:38:05 +0200 Subject: [Fiware-iot] iot-Week Presentation In-Reply-To: References: Message-ID: Dear all Specific enablers should be enablers developed by UA projects because they are not used by the other. Another wording could be "vertical enablers" because there are dedicated to vertical features: health features, transport features, tourism features. FI-Ware has to develop GE because 2 or 3 UA projects need them. If only one requires an enabler, it will be specific and not generic. BR THierry De : P.Barnaghi at surrey.ac.uk [mailto:P.Barnaghi at surrey.ac.uk] Envoy? : jeudi 9 juin 2011 15:13 ? : ignacio.solerjubert at atosresearch.eu; NAGELLEN Thierry RD-BIZZ-SOP; fiware-iot at lists.fi-ware.eu Objet : RE: iot-Week Presentation Dear Ignacio, Thanks for this. I think specific enablers are a subset of Generic enablers; In WP5, the focus is on IoT communication, data handling and service enablers; The Generic models will provide common functions and interfaces and for specific scenarios some features might be customised and/or added depending on the application and environment. Best regards, Payam ________________________________ From: fiware-iot-bounces at lists.fi-ware.eu [mailto:fiware-iot-bounces at lists.fi-ware.eu] On Behalf Of Ignacio Soler Jubert Sent: 09 June 2011 10:58 To: thierry.nagellen at orange-ftgroup.com; fiware-iot at lists.fi-ware.eu Subject: [Fiware-iot] iot-Week Presentation Dear All, Yesterday I have done the presentation of WP5 of FIWARE in the iot-Week. It did like to people. And generate so many question about Generic Enablers and Specific/Domain Enablers. Which is the difference? How we identify the generic vs specific and where is the scope of them and if a specific enabler could potentially become a Generic one? Best regards, Ignacio. Ignacio Soler Head of Smart Objects Laboratory ATOS Research and Innovation Diagonal, 200 - 08018 Barcelona (SPAIN) Tel: +34 934 861 818 , --> NEW CELLULAR: +34 675 620 202 ignacio.solerjubert at atosorigin.com www.atosresearch.eu ------------------------------------------------------------------ This e-mail and the documents attached are confidential and intended solely for the addressee; it may also be privileged. If you receive this e-mail in error, please notify the sender immediately and destroy it. As its integrity cannot be secured on the Internet, the Atos Origin group liability cannot be triggered for the message content. Although the sender endeavours to maintain a computer virus-free network, the sender does not warrant that this transmission is virus-free and will not be liable for any damages resulting from any virus transmitted. Este mensaje y los ficheros adjuntos pueden contener informacion confidencial destinada solamente a la(s) persona(s) mencionadas anteriormente pueden estar protegidos por secreto profesional. Si usted recibe este correo electronico por error, gracias por informar inmediatamente al remitente y destruir el mensaje. Al no estar asegurada la integridad de este mensaje sobre la red, Atos Origin no se hace responsable por su contenido. Su contenido no constituye ningun compromiso para el grupo Atos Origin, salvo ratificacion escrita por ambas partes. Aunque se esfuerza al maximo por mantener su red libre de virus, el emisor no puede garantizar nada al respecto y no sera responsable de cualesquiera danos que puedan resultar de una transmision de virus. ------------------------------------------------------------------ -------------- next part -------------- An HTML attachment was scrubbed... URL: From Ernoe.Kovacs at neclab.eu Fri Jun 10 14:15:48 2011 From: Ernoe.Kovacs at neclab.eu (Ernoe Kovacs) Date: Fri, 10 Jun 2011 12:15:48 +0000 Subject: [Fiware-iot] iot-Week Presentation In-Reply-To: References: Message-ID: <8152E2132B13FB488CFD1947E2DEF19C13A5EDC2@DAPHNIS.office.hd> Ignacio, is the IoT Week presentation available on the server somewhere or could you make it available? Thank you Ern? From: fiware-iot-bounces at lists.fi-ware.eu [mailto:fiware-iot-bounces at lists.fi-ware.eu] On Behalf Of Ignacio Soler Jubert Sent: Donnerstag, 9. Juni 2011 11:58 To: thierry.nagellen at orange-ftgroup.com; fiware-iot at lists.fi-ware.eu Subject: [Fiware-iot] iot-Week Presentation Dear All, Yesterday I have done the presentation of WP5 of FIWARE in the iot-Week. It did like to people. And generate so many question about Generic Enablers and Specific/Domain Enablers. Which is the difference? How we identify the generic vs specific and where is the scope of them and if a specific enabler could potentially become a Generic one? Best regards, Ignacio. Ignacio Soler Head of Smart Objects Laboratory ATOS Research and Innovation Diagonal, 200 - 08018 Barcelona (SPAIN) Tel: +34 934 861 818 , --> NEW CELLULAR: +34 675 620 202 ignacio.solerjubert at atosorigin.com www.atosresearch.eu ------------------------------------------------------------------ This e-mail and the documents attached are confidential and intended solely for the addressee; it may also be privileged. If you receive this e-mail in error, please notify the sender immediately and destroy it. As its integrity cannot be secured on the Internet, the Atos Origin group liability cannot be triggered for the message content. Although the sender endeavours to maintain a computer virus-free network, the sender does not warrant that this transmission is virus-free and will not be liable for any damages resulting from any virus transmitted. Este mensaje y los ficheros adjuntos pueden contener informacion confidencial destinada solamente a la(s) persona(s) mencionadas anteriormente pueden estar protegidos por secreto profesional. Si usted recibe este correo electronico por error, gracias por informar inmediatamente al remitente y destruir el mensaje. Al no estar asegurada la integridad de este mensaje sobre la red, Atos Origin no se hace responsable por su contenido. Su contenido no constituye ningun compromiso para el grupo Atos Origin, salvo ratificacion escrita por ambas partes. Aunque se esfuerza al maximo por mantener su red libre de virus, el emisor no puede garantizar nada al respecto y no sera responsable de cualesquiera danos que puedan resultar de una transmision de virus. ------------------------------------------------------------------ -------------- next part -------------- An HTML attachment was scrubbed... URL: From Ernoe.Kovacs at neclab.eu Fri Jun 10 15:22:41 2011 From: Ernoe.Kovacs at neclab.eu (Ernoe Kovacs) Date: Fri, 10 Jun 2011 13:22:41 +0000 Subject: [Fiware-iot] FIWare WP5 description In-Reply-To: <8152E2132B13FB488CFD1947E2DEF19C13A5DE9F@DAPHNIS.office.hd> References: <8152E2132B13FB488CFD1947E2DEF19C13A5DCFF@DAPHNIS.office.hd> <8152E2132B13FB488CFD1947E2DEF19C13A5DE9F@DAPHNIS.office.hd> Message-ID: <8152E2132B13FB488CFD1947E2DEF19C13A5EE43@DAPHNIS.office.hd> Thierry, all, I think you asked for support during the PhC to identify the USP of FIWare WP5. Please find a text file attached. It is basically extracting from the existing text the major point and identifying what is different to others. I am not sure where you want to include this into the long text ("IoT SE v0.9 (v09_IOTSE.doc)"). I actually suggest to have a text even befor the long explanation text, so a section 3.1.1. If we select that schema, then all sub-section should do it accordingly. Alternative would be to have this as a summary at the end. Feel free to use and adapt the text. - Ern? > -----Original Message----- > From: fiware-iot-bounces at lists.fi-ware.eu [mailto:fiware-iot- > bounces at lists.fi-ware.eu] On Behalf Of Ernoe Kovacs > Sent: Mittwoch, 8. Juni 2011 11:42 > To: thierry.nagellen at orange-ftgroup.com; fiware-iot at lists.fi-ware.eu > Subject: [Fiware-iot] FIWare WP5 description > > Thierry, all, > > (a) short question: can we have a look at what other WPs are doing? > I think it could be good to see how they deal with this complex process. > > Any hint where I can access that? > > (b) WP5 Work > > I am also not sure what is our main problem to tackle: > (a) Interactions with the other WPs? > - Purpose of this? > - Level of Detail (Example: Easy to say I need security, more complex > to say I need "secure ids" or "distributed policy mng", even > harder to say "a cryptographic secured identification schema") > (b) WP internal architecture > - I see pictures poping up right and left, all different, many not > agreed on the large scope > - internal interfaces > You said you need to understand these internal interfaces. > - Why? What purpose does it serve in the document? > (c) Concept View > - You said we need to explain to the UC project what they can > expect. > This is a highlevel concept view, ideally with some good terms > and > simple pictures. > (d) Detailed Enabler View > - which enablers, which sub-systems, which APIs, wich information > model > (e) Unique Selling Points > - Again something different, and also completely different to > present. > > > Sorry for nasty question, but I am confused. > - Ern? > > > _______________________________________________ > Fiware-iot mailing list > Fiware-iot at lists.fi-ware.eu > http://lists.fi-ware.eu/listinfo/fiware-iot -------------- next part -------------- An embedded and charset-unspecified text was scrubbed... Name: FIWare-WP5_IoT_USP.txt URL: From Ernoe.Kovacs at neclab.eu Fri Jun 10 16:57:24 2011 From: Ernoe.Kovacs at neclab.eu (Ernoe Kovacs) Date: Fri, 10 Jun 2011 14:57:24 +0000 Subject: [Fiware-iot] FiWare D2.2[WP5] : Fig.7 IoT Concepts References: <8152E2132B13FB488CFD1947E2DEF19C13A5DCFF@DAPHNIS.office.hd> <8152E2132B13FB488CFD1947E2DEF19C13A5DE9F@DAPHNIS.office.hd> Message-ID: <8152E2132B13FB488CFD1947E2DEF19C13A5EF4A@DAPHNIS.office.hd> Thierry all, during Wednesday discussion I mentioned that Fig. 7 could be re-arranged for clarification. Please find a proposal attached thought it is actually more a discussion and identification of open issues contribution... (a) Slide 2: Re-arrangement of the blocks Note especially the split into real-world aspects (right) and virtual aspects (left). (b) Slide 3: Adding IoT Application that can live on Device, GW, Backend (very much in line with ETSI M2M) (c) Slide 4: SENSEI Concept (at least my understanding) Please note: - one thing can have many devices associated with it. Best examples are "buildings with many sensors" - an IoT Resource is something than can be access, e.g. a device. A thing cannot be access, only the devices it is attached to. - a Virtual Entity is representing a complete Thing (d) Slide 5: After talking with an IoT-A member, I am not sure how to map concepts. See Slide 5. I color coded different mapping. IMHO it is either the black one or the blue one. The red one is wrong. Overall, I think the comparison with the IoT-A model shows that we are missing some of the concepts or are not clear on them. This includes the definition given in the Glossary and concept picture in Fig. 7. So what shall we do? Point is, if we communicate with the UC projects, we should have a good and stable vision. To be honest, I personally would try to harmonize the definitions and concepts with IoT_A as much as possible to avoid confusion in the community. The reason for that is that FIWare has NOT (!!!!!!!) the mission to do R&D and architecture work on IoT. FIWare ahs the mission to provide a platform with generic enable. This should be based on the outcome of former or running EU projects. (!!!!) Maybe I am too extreme here, but we should harmonize within the EJU not create division... One way out would be to reduce what we describe to real simple concepts. (a) Physical World <-> Virtual World View Thing <-> Virtual Entity (b) Deployment View IoT Backend <-> Iot Gateway <-> Device (c) API View IOT Resource + Event + Mng IF + Service IF Keep them separated for simplicity. What do you think? Ernoe - Ernoe > -----Original Message----- > From: Ernoe Kovacs > Sent: Freitag, 10. Juni 2011 15:23 > To: Ernoe Kovacs; thierry.nagellen at orange-ftgroup.com; fiware- > iot at lists.fi-ware.eu > Subject: RE: FIWare WP5 description > > Thierry, all, > > I think you asked for support during the PhC to identify the USP of FIWare > WP5. > > Please find a text file attached. It is basically extracting from the > existing text the major point and identifying what is different to others. > > > I am not sure where you want to include > this into the long text ("IoT SE v0.9 (v09_IOTSE.doc)"). > I actually suggest to have a text even befor the long explanation text, so > a section 3.1.1. > If we select that schema, then all sub-section should do it accordingly. > Alternative would be to have this as a summary at the end. > > Feel free to use and adapt the text. > - Ern? > > > > > > -----Original Message----- > > From: fiware-iot-bounces at lists.fi-ware.eu [mailto:fiware-iot- > > bounces at lists.fi-ware.eu] On Behalf Of Ernoe Kovacs > > Sent: Mittwoch, 8. Juni 2011 11:42 > > To: thierry.nagellen at orange-ftgroup.com; fiware-iot at lists.fi-ware.eu > > Subject: [Fiware-iot] FIWare WP5 description > > > > Thierry, all, > > > > (a) short question: can we have a look at what other WPs are doing? > > I think it could be good to see how they deal with this complex process. > > > > Any hint where I can access that? > > > > (b) WP5 Work > > > > I am also not sure what is our main problem to tackle: > > (a) Interactions with the other WPs? > > - Purpose of this? > > - Level of Detail (Example: Easy to say I need security, more > complex > > to say I need "secure ids" or "distributed policy mng", even > > harder to say "a cryptographic secured identification schema") > > (b) WP internal architecture > > - I see pictures poping up right and left, all different, many not > > agreed on the large scope > > - internal interfaces > > You said you need to understand these internal interfaces. > > - Why? What purpose does it serve in the document? > > (c) Concept View > > - You said we need to explain to the UC project what they can > expect. > > This is a highlevel concept view, ideally with some good terms > and > > simple pictures. > > (d) Detailed Enabler View > > - which enablers, which sub-systems, which APIs, wich information > > model > > (e) Unique Selling Points > > - Again something different, and also completely different to > > present. > > > > > > Sorry for nasty question, but I am confused. > > - Ern? > > > > > > _______________________________________________ > > Fiware-iot mailing list > > Fiware-iot at lists.fi-ware.eu > > http://lists.fi-ware.eu/listinfo/fiware-iot -------------- next part -------------- A non-text attachment was scrubbed... Name: WP5 IoT Concept.pptx Type: application/vnd.openxmlformats-officedocument.presentationml.presentation Size: 435664 bytes Desc: WP5 IoT Concept.pptx URL: From oteiza at tid.es Fri Jun 10 17:38:31 2011 From: oteiza at tid.es (FRANCISCO OTEIZA LACALLE) Date: Fri, 10 Jun 2011 17:38:31 +0200 Subject: [Fiware-iot] IoT Resource Management Message-ID: <400B1E0D509AB14C95FFDC1DE303B9A881E0F7FBDF@EXCLU2K7.hi.inet> Hello Thierry, Enclosed you can find a new version of the IoT Resource management architecture, I have refined the graph. ? I have modified the graph with your previous comments in the name components ? I have changed some component names to provide more coherence among them. ? I have Included arrows to show interface between the building blocks ? Description of the interfaces Take into account that I have changed slightly the graphic and the name of the building blocks, please could you include this changes in the document? Regards Fran [cid:image001.jpg at 01CC2795.36FD6BD0] Francisco Oteiza Lacalle Technology Specialist M2M Platform Phone: +34 913129726 Mobile: +34 629537618 oteiza at tid.es Parque Tecnol?gico Walqa Ed. 1. Carretera Zaragoza 330, Km 566 22197 Cuarte (Huesca) Spain ________________________________ 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: -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.jpg Type: image/jpeg Size: 6541 bytes Desc: image001.jpg URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: Fiware-IoT-Resource Mngmt-T5 2.pptx Type: application/vnd.openxmlformats-officedocument.presentationml.presentation Size: 93960 bytes Desc: Fiware-IoT-Resource Mngmt-T5 2.pptx URL: From Ernoe.Kovacs at neclab.eu Wed Jun 15 09:28:17 2011 From: Ernoe.Kovacs at neclab.eu (Ernoe Kovacs) Date: Wed, 15 Jun 2011 07:28:17 +0000 Subject: [Fiware-iot] FIWare-IoT: Concept Discussion / Comments on terms Message-ID: <8152E2132B13FB488CFD1947E2DEF19C13A5FD3E@DAPHNIS.office.hd> Hi all, please find enclose (a) Some discussion on the IoT terms (b) an update on the Concept discussion presentation (c) a small update on the unique selling points one new entry is marked with /* new */ I have not seen an agenda for today's PhC. Will it happen? - Ernoe ========================================================== Dr. Ern? Kovacs??????? Senior Manager Internet Services NEC Europe Ltd.??????? NEC Laboratories Europe Kurf?rsten-Anlage 36???D-69115 Heidelberg, Germany Phone:? +49 (6221) 4342 - 131 Fax:??? +49 (6221) 4342 - 155 Mobile: +49 (163) 2086046 EMail: ernoe.kovacs at nw.neclab.eu http://www.netlab.nec.de ========================================================== Registered Office: NEC House, 1 Victoria Road, London W3 6BL, UK Registered in England, No. 2832014 -------------- next part -------------- A non-text attachment was scrubbed... Name: WP5 IoT Discussion-Terms.pptx Type: application/vnd.openxmlformats-officedocument.presentationml.presentation Size: 116936 bytes Desc: WP5 IoT Discussion-Terms.pptx URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: WP5 IoT Concept_v0.02.ppt Type: application/vnd.ms-powerpoint Size: 568320 bytes Desc: WP5 IoT Concept_v0.02.ppt URL: -------------- next part -------------- An embedded and charset-unspecified text was scrubbed... Name: FIWare-WP5_IoT_USP_v0.02.txt URL: From lorant.farkas at nsn.com Wed Jun 15 09:41:35 2011 From: lorant.farkas at nsn.com (Farkas, Lorant (NSN - HU/Budapest)) Date: Wed, 15 Jun 2011 10:41:35 +0300 Subject: [Fiware-iot] FIWare-IoT: Concept Discussion / Comments on terms In-Reply-To: <8152E2132B13FB488CFD1947E2DEF19C13A5FD3E@DAPHNIS.office.hd> References: <8152E2132B13FB488CFD1947E2DEF19C13A5FD3E@DAPHNIS.office.hd> Message-ID: <93D28BDF64839C468B848D14227151A201E6733A@FIESEXC014.nsn-intra.net> Dear Ern?, -Thanks for the contributions. -Yes, it will happen. Agenda points as we see them: 1. check status of AP-s, discuss about the new deadlines (from Lorant) 2. check the Unique Selling Points (based on Ern? contribution) (from Thierry) 3. short discussion on Ern? contribution for the picture regarding IoT-A work (this could be include a bit later, or in the 2nd version) (from Thierry) 4. short discussion on Ern? contribution for the glossary (from Lorant) 5. ask a general reading for everybody for the whole text because we are now expecting TID comments (from Thierry) 6. missing parts e.g. from Process Automation (from Thierry) Meeting will start at 10 AM. Br, Lorant -----Original Message----- From: fiware-iot-bounces at lists.fi-ware.eu [mailto:fiware-iot-bounces at lists.fi-ware.eu] On Behalf Of ext Ernoe Kovacs Sent: Wednesday, June 15, 2011 9:28 AM To: fiware-iot at lists.fi-ware.eu Subject: [Fiware-iot] FIWare-IoT: Concept Discussion / Comments on terms Hi all, please find enclose (a) Some discussion on the IoT terms (b) an update on the Concept discussion presentation (c) a small update on the unique selling points one new entry is marked with /* new */ I have not seen an agenda for today's PhC. Will it happen? - Ernoe ========================================================== Dr. Ern? Kovacs??????? Senior Manager Internet Services NEC Europe Ltd.??????? NEC Laboratories Europe Kurf?rsten-Anlage 36???D-69115 Heidelberg, Germany Phone:? +49 (6221) 4342 - 131 Fax:??? +49 (6221) 4342 - 155 Mobile: +49 (163) 2086046 EMail: ernoe.kovacs at nw.neclab.eu http://www.netlab.nec.de ========================================================== Registered Office: NEC House, 1 Victoria Road, London W3 6BL, UK Registered in England, No. 2832014 From lorant.farkas at nsn.com Thu Jun 16 07:55:23 2011 From: lorant.farkas at nsn.com (Farkas, Lorant (NSN - HU/Budapest)) Date: Thu, 16 Jun 2011 08:55:23 +0300 Subject: [Fiware-iot] Weekly meeting minutes Message-ID: <93D28BDF64839C468B848D14227151A201E67917@FIESEXC014.nsn-intra.net> Dear All, Please find the meeting minutes from yesterday under this link: https://forge.fi-ware.eu/docman/view.php/11/157/IoT-Minutes-Telco-061520 11.doc Br, Lorant -------------- next part -------------- An HTML attachment was scrubbed... URL: From lorant.farkas at nsn.com Thu Jun 16 08:26:32 2011 From: lorant.farkas at nsn.com (Farkas, Lorant (NSN - HU/Budapest)) Date: Thu, 16 Jun 2011 09:26:32 +0300 Subject: [Fiware-iot] Meetings in July Message-ID: <93D28BDF64839C468B848D14227151A201E67957@FIESEXC014.nsn-intra.net> Dear All, Wrt IOT07_15062011 (physical meetings in July) I have the following information: -the calendar of meetings will be set up soon -with UA projects there won't be any meetings before we finish the deliverable in M2 and this is to be agreed with the rest of the architecture board members. A virtual meeting might take place with UA projects by mid July -with other WP-s task forces will be set up - in case this is needed - once the content of each technical chapter is read through. I don't have any information supporting that this would happen under the form of physical meetings Br, Lorant -------------- next part -------------- An HTML attachment was scrubbed... URL: From thierry.nagellen at orange-ftgroup.com Tue Jun 21 08:38:34 2011 From: thierry.nagellen at orange-ftgroup.com (thierry.nagellen at orange-ftgroup.com) Date: Tue, 21 Jun 2011 08:38:34 +0200 Subject: [Fiware-iot] =?iso-8859-1?q?Annul=E9=3A_IoT_weekly_telco?= Message-ID: Quand : A lieu chaque mercredi ? compter du 25/05/2011 de 09:30 ? 11:00 (GMT+01:00) Brussels, Copenhagen, Madrid, Paris. Remarque : le d?calage GMT ci-dessus ne tient pas compte des r?glages de l'heure d'?t?. *~*~*~*~*~*~*~*~*~* **** You can forward this email invitation to attendees **** Hello , L?r?nt Farkas invites you to attend this online meeting. Topic: IOT WP weekly Date: Every Wednesday, from Wednesday, 11 May 2011 to Wednesday, 26 March 2014 Time: 9:30, Europe Summer Time (Paris, GMT+02:00) Meeting Number: 709 472 921 Meeting Password: FI-WARE ------------------------------------------------------- To join the online meeting ------------------------------------------------------- 1. Go to https://nsn.webex.com/nsn/j.php?ED=175018962&UID=0&PW=NYzEzYWM0ZTNk&RT=MTgjMjM%3D 2. Enter your name and email address. 3. Enter the meeting password: FI-WARE 4. Click "Join Now". To view in other time zones or languages, please click the link: https://nsn.webex.com/nsn/j.php?ED=175018962&UID=0&PW=NYzEzYWM0ZTNk&ORT=MTgjMjM%3D ------------------------------------------------------- NSN Voice Conference information Conference ID: 58465 PIN: 9012 Making a conference call - from the office: 8071870 (in Finland and Germany) - from out of office: +358 7180 71870 (in Finland) and +49 89 5159 43800 (in Germany) All out-of-office conference access numbers are listed in page . Country/Site Conference access number All sites From company office conference phone or desk phone 8071870. This number also works from company mobiles in several countries. See Internal Numbers page for more information. Argentina - Buenos Aires +54 11 5983 9400 (PRIMARY) or +54 11 4814 9373 Argentina - Cordoba +54 35 1568 2208 Australia - Sydney +61 28 014 7189 (PRIMARY) or +61 29 429 9664 Australia - Melbourne +61 38 739 4333 Austria +43 72 088 0245 Bahrain +97 31 619 9028 Belgium - Generic +32 1448 0116 Belgium - Diegem-Machelen +32 2710 3300 Brazil - Belo Horizonte +55 31 3956 0546 Brazil - Brazil +55 61 3717 2043 Brazil - Curitiba +55 41 3906 0826 Brazil - Manaus +55 92 3652 7576 Brazil - Rio De Janeiro +55 21 3958 0804 (PRIMARY) or +55 21 3431 1999 Brazil - Salvador +55 71 3717 5351 Brazil - Sao Paolo +55 11 5508 0630 Bulgaria +359 2491 7085 Canada - Ajax +1 90 5619 4346 Canada - Burnaby +1 60 4456 5897 Canada - Hamilton +1 905 581 0212 Canada - Mississauga +1 289 360 3950 Canada - Montreal +1 51 4789 9125 Canada - Ottawa +1 61 3800 0568 Chile - Santiago +56 2350 6485 China - Mainland +86 10 8405 5000 ext 1870 China - Beijing +86 10 8405 5000 ext 1870 China - Chengdu +86 28 8689 0188 ext 1870 China - Dongguan +86 0769 2240 2844 ext 1870 China - Guangzhou +86 20 8755 6190 ext 1870 China - Hangzhou +86 571 8722 0877 ext 1870 China - Hong Kong +852 259 70220 ext 1870 China - Kunming +86 871 362 2880 ext 1870 China - Shanghai +86 21 6101 1870 ext 1870 China - ShenZhen +86 755 8613 3688 ext 1870 China - Suzhou +86 512 6761 6166 ext 1870 China - Zhengzhou +86 371 6566 9768 ext 1870 Colombia +57 1640 7979 ext 444 Croatia +38 51 777 6122 Czech Republic +42 02 460 19300 Denmark +45 699 18450 (PRIMARY) or +45 3329 2882 Egypt +97 31 619 9028 (Bahrain nbr) Estonia +37 266 67297 Finland +358 7180 71870 France +33 17 061 7813 (PRIMARY) or +33 14 915 1553 Germany +49 89 5159 43800 Greece +30 21 1176 8207 (PRIMARY) or +30 21 1120 3677 Hungary - Budapest +36 17 009 888 Hungary - Kom?rom +36 20 884 2499 India 000 800 100 7777 Indonesia - Jakarta (Menara Mulia/Plaza Kuningan +62 21 2557 9102 Indonesia - Bandung +62 22 8427 5992 Indonesia - Medan +62 61 3001 2702 Indonesia - Semarang +62 24 3300 0702 Ireland +353 1526 2862 Israel +97 29 775 1700 Italy - Milan +39 024 004 2007 Italy - Rome +39 069 481 6656 Japan +81 3 4578 0230 (PRIMARY) or +81 3 5474 7979 Kuwait +97 31 619 9028 (Bahrain nbr) Latvia +37 16 765 2510 Lithuania +37 0 5205 8994 Luxembourg +352 2088 0106 Malaysia +60 323 029 009 Mexico - Mexico City +52 55 3686 9759 (PRIMARY) or +52 55 5261 7245 Mexico - Reynosa +52 89 9909 1555 Netherlands +31 79 346 5225 New Zealand +64 9306 6933 Norway - Oslo +47 21 548 223 Oman +97 31 619 9028 (Bahrain nbr) Pakistan +92 512 092 444 Panama +507 832 7981 Peru +51 1708 5370 (PRIMARY) or +51 1215 7650 Philippines +63 2754 1700 Poland - Warsaw +48 22 398 8116 Poland - Wroclaw +48 71 718 1215 Portugal +351 21 044 4698 Qatar +97 31 619 9028 (Bahrain nbr) Romania +40 36 440 3799 Russia +74 95 725 2706 Saudi Arabia +97 31 619 9028 (Bahrain nbr) Singapore +65 3103 1065 (PRIMARY) or +65 6723 2582 Slovakia +42 12 3300 6924 Slovenia +38 61 600 2713 South Africa - Johannesburg +27 1 0500 2221 South Africa - Pretoria +27 1 2004 2334 South Korea - Masan +82 5 5290 7690 South Korea - Seoul +82 2 2186 5088 Spain +349 1187 5929 Sweden +46 85 250 0862 (PRIMARY), +46 84 100 9299 Switzerland +41 44 279 7943 Taiwan +88 62 8175 9298 Thailand +66 2762 6750 Turkey +90 216 570 2345 Ukraine +38 044 520 2272 UK +44 12 5275 8334 UK - Camberley +44 12 5286 5849 UK - Church Crookham +44 12 5261 1100 UK - Huntingdon +44 14 8087 8220 (PRIMARY), +44 14 8044 4206 UK - London +44 20 3318 1924 United Arab Emirates +97 31 619 9028 (Bahrain nbr) USA - Alpharetta +1 770 871 3050 USA - Arizona +1 480 588 3748 USA - Atlanta +1 404 236 4550 USA - Atlanta Notheast +1 678 317 3165 USA - Austin/Round Rock +1 512 600 2027 USA - Belleville +1 973 547 7982 USA - Boca Raton +1 561 910 2843 USA - Boston +1 617 963 8320 (PRIMARY) or +1 781 993 4850 USA - Burlington +1 781 993 4850 USA - Calabasas +1 818 914 0215 USA - Canoga Park +1 818 914 0215 USA - Cary +1 919 655 1388 USA - Chelmsford/Littleton +1 978 679 0233 USA - Chicago +1 773 303 4710 USA - Dallas +1 214 269 7626 USA - Dallas/Fort Worth +1 214 270 0352 USA - Greenville, NC +1 252 329 1677 USA - Herndon +1 703 483 4485 USA - Johnson City +1 423 952 1545 USA - Kirkland +1 425 242 3113 USA - Miami +1 786 388 4150 or +1 786 329 7177 USA - Naperville +1 630 596 2203 USA - New Brunswick +1 732 579 6483 USA - New Century, KS +1 913 254 5900 USA - New York White Plains +1 914 368 0650 USA - New York Peekskill, White Plains +1 914 293 1885 USA - Palo Alto +1 650 644 1349 USA - Redmond +1 425 242 3113 USA - San Diego +1 858 769 5309 or +1 619 330 9699 USA - Sunnyvale +1 408 419 1750 USA - Washington D.C +1 202 552 4781 Vietnam +84 4 3724 6110 Yemen +97 31 619 9028 (Bahrain nbr) Please check and prioritize them. If there is no access number for your country then please use access numbers of the area where to the calling costs are lowest. ------------------------------------------------------- For assistance ------------------------------------------------------- 1. Go to https://nsn.webex.com/nsn/mc 2. On the left navigation bar, click "Support". You can contact me at: lorant.farkas at nsn.com To add this meeting to your calendar program (for example Microsoft Outlook), click this link: https://nsn.webex.com/nsn/j.php?ED=175018962&UID=0&ICS=MI&LD=1&RD=18&ST=1&SHA2=gVmoQ/CXj05nzcI-4TFgQ2qtqmAulzDfzoOWKpcyLyg=&RT=MTgjMjM%3D -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: meeting.ics Type: text/calendar Size: 39281 bytes Desc: not available URL: From thierry.nagellen at orange-ftgroup.com Tue Jun 21 09:52:51 2011 From: thierry.nagellen at orange-ftgroup.com (thierry.nagellen at orange-ftgroup.com) Date: Tue, 21 Jun 2011 09:52:51 +0200 Subject: [Fiware-iot] IoT Weekly Telco Message-ID: Quand : A lieu chaque mercredi ? compter du 22/06/2011 jusqu'au 13/07/2011 de 10:00 ? 11:30 (GMT+01:00) Brussels, Copenhagen, Madrid, Paris. Remarque : le d?calage GMT ci-dessus ne tient pas compte des r?glages de l'heure d'?t?. *~*~*~*~*~*~*~*~*~* Dear all To avoid any misunderstanding I've cancelled the previous weekly meeting at 9:30 and submit a new one at 10:00 AM. We will have to discuss later how we will organize the meetings during vacation times and for the second version of D2.2. BR Thierry --------------------------------------------------- Meeting Number: 709 472 921 Meeting Password: FI-WARE ------------------------------------------------------- To join the online meeting ------------------------------------------------------- 1. Go to https://nsn.webex.com/nsn/j.php?ED=175018962&UID=0&PW=NYzEzYWM0ZTNk&RT=MTgjMjM%3D 2. Enter your name and email address. 3. Enter the meeting password: FI-WARE 4. Click "Join Now". To view in other time zones or languages, please click the link: https://nsn.webex.com/nsn/j.php?ED=175018962&UID=0&PW=NYzEzYWM0ZTNk&ORT=MTgjMjM%3D ------------------------------------------------------- NSN Voice Conference information Conference ID: 58465 PIN: 9012 Making a conference call - from the office: 8071870 (in Finland and Germany) - from out of office: +358 7180 71870 (in Finland) and +49 89 5159 43800 (in Germany) All out-of-office conference access numbers are listed in page . Country/Site Conference access number All sites From company office conference phone or desk phone 8071870. This number also works from company mobiles in several countries. See Internal Numbers page for more information. Argentina - Buenos Aires +54 11 5983 9400 (PRIMARY) or +54 11 4814 9373 Argentina - Cordoba +54 35 1568 2208 Australia - Sydney +61 28 014 7189 (PRIMARY) or +61 29 429 9664 Australia - Melbourne +61 38 739 4333 Austria +43 72 088 0245 Bahrain +97 31 619 9028 Belgium - Generic +32 1448 0116 Belgium - Diegem-Machelen +32 2710 3300 Brazil - Belo Horizonte +55 31 3956 0546 Brazil - Brazil +55 61 3717 2043 Brazil - Curitiba +55 41 3906 0826 Brazil - Manaus +55 92 3652 7576 Brazil - Rio De Janeiro +55 21 3958 0804 (PRIMARY) or +55 21 3431 1999 Brazil - Salvador +55 71 3717 5351 Brazil - Sao Paolo +55 11 5508 0630 Bulgaria +359 2491 7085 Canada - Ajax +1 90 5619 4346 Canada - Burnaby +1 60 4456 5897 Canada - Hamilton +1 905 581 0212 Canada - Mississauga +1 289 360 3950 Canada - Montreal +1 51 4789 9125 Canada - Ottawa +1 61 3800 0568 Chile - Santiago +56 2350 6485 China - Mainland +86 10 8405 5000 ext 1870 China - Beijing +86 10 8405 5000 ext 1870 China - Chengdu +86 28 8689 0188 ext 1870 China - Dongguan +86 0769 2240 2844 ext 1870 China - Guangzhou +86 20 8755 6190 ext 1870 China - Hangzhou +86 571 8722 0877 ext 1870 China - Hong Kong +852 259 70220 ext 1870 China - Kunming +86 871 362 2880 ext 1870 China - Shanghai +86 21 6101 1870 ext 1870 China - ShenZhen +86 755 8613 3688 ext 1870 China - Suzhou +86 512 6761 6166 ext 1870 China - Zhengzhou +86 371 6566 9768 ext 1870 Colombia +57 1640 7979 ext 444 Croatia +38 51 777 6122 Czech Republic +42 02 460 19300 Denmark +45 699 18450 (PRIMARY) or +45 3329 2882 Egypt +97 31 619 9028 (Bahrain nbr) Estonia +37 266 67297 Finland +358 7180 71870 France +33 17 061 7813 (PRIMARY) or +33 14 915 1553 Germany +49 89 5159 43800 Greece +30 21 1176 8207 (PRIMARY) or +30 21 1120 3677 Hungary - Budapest +36 17 009 888 Hungary - Kom?rom +36 20 884 2499 India 000 800 100 7777 Indonesia - Jakarta (Menara Mulia/Plaza Kuningan +62 21 2557 9102 Indonesia - Bandung +62 22 8427 5992 Indonesia - Medan +62 61 3001 2702 Indonesia - Semarang +62 24 3300 0702 Ireland +353 1526 2862 Israel +97 29 775 1700 Italy - Milan +39 024 004 2007 Italy - Rome +39 069 481 6656 Japan +81 3 4578 0230 (PRIMARY) or +81 3 5474 7979 Kuwait +97 31 619 9028 (Bahrain nbr) Latvia +37 16 765 2510 Lithuania +37 0 5205 8994 Luxembourg +352 2088 0106 Malaysia +60 323 029 009 Mexico - Mexico City +52 55 3686 9759 (PRIMARY) or +52 55 5261 7245 Mexico - Reynosa +52 89 9909 1555 Netherlands +31 79 346 5225 New Zealand +64 9306 6933 Norway - Oslo +47 21 548 223 Oman +97 31 619 9028 (Bahrain nbr) Pakistan +92 512 092 444 Panama +507 832 7981 Peru +51 1708 5370 (PRIMARY) or +51 1215 7650 Philippines +63 2754 1700 Poland - Warsaw +48 22 398 8116 Poland - Wroclaw +48 71 718 1215 Portugal +351 21 044 4698 Qatar +97 31 619 9028 (Bahrain nbr) Romania +40 36 440 3799 Russia +74 95 725 2706 Saudi Arabia +97 31 619 9028 (Bahrain nbr) Singapore +65 3103 1065 (PRIMARY) or +65 6723 2582 Slovakia +42 12 3300 6924 Slovenia +38 61 600 2713 South Africa - Johannesburg +27 1 0500 2221 South Africa - Pretoria +27 1 2004 2334 South Korea - Masan +82 5 5290 7690 South Korea - Seoul +82 2 2186 5088 Spain +349 1187 5929 Sweden +46 85 250 0862 (PRIMARY), +46 84 100 9299 Switzerland +41 44 279 7943 Taiwan +88 62 8175 9298 Thailand +66 2762 6750 Turkey +90 216 570 2345 Ukraine +38 044 520 2272 UK +44 12 5275 8334 UK - Camberley +44 12 5286 5849 UK - Church Crookham +44 12 5261 1100 UK - Huntingdon +44 14 8087 8220 (PRIMARY), +44 14 8044 4206 UK - London +44 20 3318 1924 United Arab Emirates +97 31 619 9028 (Bahrain nbr) USA - Alpharetta +1 770 871 3050 USA - Arizona +1 480 588 3748 USA - Atlanta +1 404 236 4550 USA - Atlanta Notheast +1 678 317 3165 USA - Austin/Round Rock +1 512 600 2027 USA - Belleville +1 973 547 7982 USA - Boca Raton +1 561 910 2843 USA - Boston +1 617 963 8320 (PRIMARY) or +1 781 993 4850 USA - Burlington +1 781 993 4850 USA - Calabasas +1 818 914 0215 USA - Canoga Park +1 818 914 0215 USA - Cary +1 919 655 1388 USA - Chelmsford/Littleton +1 978 679 0233 USA - Chicago +1 773 303 4710 USA - Dallas +1 214 269 7626 USA - Dallas/Fort Worth +1 214 270 0352 USA - Greenville, NC +1 252 329 1677 USA - Herndon +1 703 483 4485 USA - Johnson City +1 423 952 1545 USA - Kirkland +1 425 242 3113 USA - Miami +1 786 388 4150 or +1 786 329 7177 USA - Naperville +1 630 596 2203 USA - New Brunswick +1 732 579 6483 USA - New Century, KS +1 913 254 5900 USA - New York White Plains +1 914 368 0650 USA - New York Peekskill, White Plains +1 914 293 1885 USA - Palo Alto +1 650 644 1349 USA - Redmond +1 425 242 3113 USA - San Diego +1 858 769 5309 or +1 619 330 9699 USA - Sunnyvale +1 408 419 1750 USA - Washington D.C +1 202 552 4781 Vietnam +84 4 3724 6110 Yemen +97 31 619 9028 (Bahrain nbr) Please check and prioritize them. If there is no access number for your country then please use access numbers of the area where to the calling costs are lowest. ------------------------------------------------------- For assistance ------------------------------------------------------- 1. Go to https://nsn.webex.com/nsn/mc 2. On the left navigation bar, click "Support". You can contact me at: lorant.farkas at nsn.com To add this meeting to your calendar program (for example Microsoft Outlook), click this link: https://nsn.webex.com/nsn/j.php?ED=175018962&UID=0&ICS=MI&LD=1&RD=18&ST=1&SHA2=gVmoQ/CXj05nzcI-4TFgQ2qtqmAulzDfzoOWKpcyLyg=&RT=MTgjMjM%3D -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: meeting.ics Type: text/calendar Size: 9852 bytes Desc: not available URL: From thierry.nagellen at orange-ftgroup.com Tue Jun 21 17:01:21 2011 From: thierry.nagellen at orange-ftgroup.com (thierry.nagellen at orange-ftgroup.com) Date: Tue, 21 Jun 2011 17:01:21 +0200 Subject: [Fiware-iot] Weekly meeting Message-ID: Dear all, You can check the last version on the website (https://forge.fi-ware.eu/docman/view.php/11/182/v016_IOTSE.docx ) Based on our meeting with Juanjo, here are the points for the discussion tomorrow: 1. Simplify SotA (too long in our document) 2. Missing points: no updates for Unique Selling Points and What kind of stakeholders should be interested in IoT GEs 3. GEs: regarding the other WPs, the grey boxes from the overall IoT picture could be Generic Enablers (in this case how to define the task level?) 4. Packaging of all architecture pictures 5. Process for the next weeks (merging all WPs documents) => final D2.2 deliveablre planned now for mid-July BR Thierry -------------- next part -------------- An HTML attachment was scrubbed... URL: From Ernoe.Kovacs at neclab.eu Wed Jun 22 11:23:00 2011 From: Ernoe.Kovacs at neclab.eu (Ernoe Kovacs) Date: Wed, 22 Jun 2011 09:23:00 +0000 Subject: [Fiware-iot] Weekly meeting In-Reply-To: References: Message-ID: <8152E2132B13FB488CFD1947E2DEF19C13A7A76F@Polydeuces.office.hd> Thierry, Lorant, all, during the PHC we had a discussion on the "grey boxes" and whether that would be the GE. I draw the attached picture for clarification, maybe to be included as an overview somewhere at the beginning of the D2.2 text. Question arising: (a) Are the mentioned "grey boxes" really the generic enablers? They do not look right for me. Rather some blocks of functionality, but not necessary a GE. (b) Also, looking at the names used her (which should mach the ones in the grey boxes of the sub-component diagrams). Without the boxes, they sometimes look rather meaningless (Frontend, Semantic Components, ...) without the further sub-structuring. I have the feeling it was not clear that the grey boxes would be the GEs and they were chosen for different reasons... (c) Furthermore, there are different way of defining the grey boxes. For example in IoT Process Automation we have Exposure Component. usually every GE would have an internal exposure layer and related components. This is clearly showing that the boxes there was made under the assumption the IoT Process Automation is a GE. (d) IMHO, same line of discussion: a GE is an independent piece of software. Would the GE called "AAA" be independent? Let me ask the following questions Q1: Are we agreeing that the picture and the drawn levels are correct (Interfaces, GE, Grouping of GE?)? Q2: Are we agreeing on the mentioned names on the GE level? (To jump ahead, IMHO, we need to revise things...) Q3: Are we agreeing on the multiple IF per GE aspect? Hope this helps in clarifying and better structuring the IoT section. BTW, I suggest to submit to all work packages this picture so that they can draw an overview about their own enablers in the same way. Regards Ern? From: fiware-iot-bounces at lists.fi-ware.eu [mailto:fiware-iot-bounces at lists.fi-ware.eu] On Behalf Of thierry.nagellen at orange-ftgroup.com Sent: Dienstag, 21. Juni 2011 17:01 To: fiware-iot at lists.fi-ware.eu Subject: [Fiware-iot] Weekly meeting Dear all, You can check the last version on the website (https://forge.fi-ware.eu/docman/view.php/11/182/v016_IOTSE.docx ) Based on our meeting with Juanjo, here are the points for the discussion tomorrow: 1. Simplify SotA (too long in our document) 2. Missing points: no updates for Unique Selling Points and What kind of stakeholders should be interested in IoT GEs 3. GEs: regarding the other WPs, the grey boxes from the overall IoT picture could be Generic Enablers (in this case how to define the task level?) 4. Packaging of all architecture pictures 5. Process for the next weeks (merging all WPs documents) => final D2.2 deliveablre planned now for mid-July BR Thierry -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: WP5 IoT Enabler_v0.01.pptx Type: application/vnd.openxmlformats-officedocument.presentationml.presentation Size: 119374 bytes Desc: WP5 IoT Enabler_v0.01.pptx URL: From Ernoe.Kovacs at neclab.eu Wed Jun 22 11:24:17 2011 From: Ernoe.Kovacs at neclab.eu (Ernoe Kovacs) Date: Wed, 22 Jun 2011 09:24:17 +0000 Subject: [Fiware-iot] D2.2: Editor Remark In-Reply-To: References: Message-ID: <8152E2132B13FB488CFD1947E2DEF19C13A7A78E@Polydeuces.office.hd> Hi, small editing remark on the D2. document. When printed in B&W, the white text in the grey boxes are nearly not readable... - Ernoe From: fiware-iot-bounces at lists.fi-ware.eu [mailto:fiware-iot-bounces at lists.fi-ware.eu] On Behalf Of thierry.nagellen at orange-ftgroup.com Sent: Dienstag, 21. Juni 2011 17:01 To: fiware-iot at lists.fi-ware.eu Subject: [Fiware-iot] Weekly meeting Dear all, You can check the last version on the website (https://forge.fi-ware.eu/docman/view.php/11/182/v016_IOTSE.docx ) Based on our meeting with Juanjo, here are the points for the discussion tomorrow: 1. Simplify SotA (too long in our document) 2. Missing points: no updates for Unique Selling Points and What kind of stakeholders should be interested in IoT GEs 3. GEs: regarding the other WPs, the grey boxes from the overall IoT picture could be Generic Enablers (in this case how to define the task level?) 4. Packaging of all architecture pictures 5. Process for the next weeks (merging all WPs documents) => final D2.2 deliveablre planned now for mid-July BR Thierry -------------- next part -------------- An HTML attachment was scrubbed... URL: From stephan.haller at sap.com Wed Jun 22 11:56:55 2011 From: stephan.haller at sap.com (Haller, Stephan) Date: Wed, 22 Jun 2011 11:56:55 +0200 Subject: [Fiware-iot] Weekly meeting In-Reply-To: References: Message-ID: <0D2446AEB6CAED48BB046223733964A54BD10B5E1C@DEWDFECCR01.wdf.sap.corp> All, Based on today's call, I made some comments to that version and uploaded it to https://forge.fi-ware.eu/docman/view.php/11/186/v016_IOTSE-SH.docx. I'd like to ask in particular the task leaders of 5.2 (Resource Mgmt) and 5.4 (Process Automation) to check these. Regards, -Stephan From: fiware-iot-bounces at lists.fi-ware.eu [mailto:fiware-iot-bounces at lists.fi-ware.eu] On Behalf Of thierry.nagellen at orange-ftgroup.com Sent: Dienstag, 21. Juni 2011 17:01 To: fiware-iot at lists.fi-ware.eu Subject: [Fiware-iot] Weekly meeting Dear all, You can check the last version on the website (https://forge.fi-ware.eu/docman/view.php/11/182/v016_IOTSE.docx ) Based on our meeting with Juanjo, here are the points for the discussion tomorrow: 1. Simplify SotA (too long in our document) 2. Missing points: no updates for Unique Selling Points and What kind of stakeholders should be interested in IoT GEs 3. GEs: regarding the other WPs, the grey boxes from the overall IoT picture could be Generic Enablers (in this case how to define the task level?) 4. Packaging of all architecture pictures 5. Process for the next weeks (merging all WPs documents) => final D2.2 deliveablre planned now for mid-July BR Thierry -------------- next part -------------- An HTML attachment was scrubbed... URL: From Martin.Bauer at neclab.eu Wed Jun 22 18:29:28 2011 From: Martin.Bauer at neclab.eu (Martin Bauer) Date: Wed, 22 Jun 2011 16:29:28 +0000 Subject: [Fiware-iot] Weekly meeting In-Reply-To: <0D2446AEB6CAED48BB046223733964A54BD10B5E1C@DEWDFECCR01.wdf.sap.corp> References: <0D2446AEB6CAED48BB046223733964A54BD10B5E1C@DEWDFECCR01.wdf.sap.corp> Message-ID: Hi all, I added a number of comments to section 5.2 https://forge.fi-ware.eu/docman/view.php/11/191/v016_IOTSE-SH-MB.docx Best regards, Martin ------------------------------------------ Dr. Martin Bauer Senior Researcher NEC Europe Ltd. NEC Laboratories Europe Software & Services Research Division Kurf?rsten-Anlage 36 D-69115 Heidelberg Tel: +49/ (0)6221/4342-168 Fax: +49/ (0)6221/4342-155 E-Mail: Martin.Bauer at neclab.eu http://www.nw.neclab.eu From: fiware-iot-bounces at lists.fi-ware.eu [mailto:fiware-iot-bounces at lists.fi-ware.eu] On Behalf Of Haller, Stephan Sent: Mittwoch, 22. Juni 2011 11:57 To: thierry.nagellen at orange-ftgroup.com; fiware-iot at lists.fi-ware.eu Subject: Re: [Fiware-iot] Weekly meeting All, Based on today's call, I made some comments to that version and uploaded it to https://forge.fi-ware.eu/docman/view.php/11/186/v016_IOTSE-SH.docx. I'd like to ask in particular the task leaders of 5.2 (Resource Mgmt) and 5.4 (Process Automation) to check these. Regards, -Stephan From: fiware-iot-bounces at lists.fi-ware.eu [mailto:fiware-iot-bounces at lists.fi-ware.eu] On Behalf Of thierry.nagellen at orange-ftgroup.com Sent: Dienstag, 21. Juni 2011 17:01 To: fiware-iot at lists.fi-ware.eu Subject: [Fiware-iot] Weekly meeting Dear all, You can check the last version on the website (https://forge.fi-ware.eu/docman/view.php/11/182/v016_IOTSE.docx ) Based on our meeting with Juanjo, here are the points for the discussion tomorrow: 1. Simplify SotA (too long in our document) 2. Missing points: no updates for Unique Selling Points and What kind of stakeholders should be interested in IoT GEs 3. GEs: regarding the other WPs, the grey boxes from the overall IoT picture could be Generic Enablers (in this case how to define the task level?) 4. Packaging of all architecture pictures 5. Process for the next weeks (merging all WPs documents) => final D2.2 deliveablre planned now for mid-July BR Thierry -------------- next part -------------- An HTML attachment was scrubbed... URL: From jhierro at tid.es Wed Jun 22 22:52:37 2011 From: jhierro at tid.es (Juanjo Hierro) Date: Wed, 22 Jun 2011 22:52:37 +0200 Subject: [Fiware-iot] Please confirm what is the last version of the contribution to the IoT Services Enablement chapter Message-ID: <4E025615.8000000@tid.es> Hi, Is the following document the final submitted contribution to the IoT chapter ? https://forge.fi-ware.eu/docman/view.php/7/166/v013_IOTSE.docx I'm asking this because I found several entries linked to different versions of the IoT Service Enablement chapter (instead of a single one with the last version uploaded according to instructions on how to upload contributions) ... I assumed that v013_IOTSE.docx was the last version based on the numbering included in the filename, but I would like to doublecheck. Thanks, -- Juanjo 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 -------------- A non-text attachment was scrubbed... Name: jhierro.vcf Type: text/x-vcard Size: 429 bytes Desc: not available URL: From Ernoe.Kovacs at neclab.eu Thu Jun 23 00:30:20 2011 From: Ernoe.Kovacs at neclab.eu (Ernoe Kovacs) Date: Wed, 22 Jun 2011 22:30:20 +0000 Subject: [Fiware-iot] Please confirm what is the last version of the contribution to the IoT Services Enablement chapter In-Reply-To: <4E025615.8000000@tid.es> References: <4E025615.8000000@tid.es> Message-ID: <8152E2132B13FB488CFD1947E2DEF19C13A7AEC0@Polydeuces.office.hd> Juanjo, there is definitely a v16 (higher in the list, sorting problems). And that is this morning's version, assume updates incorporated today... - Ernoe (bank holiday tomorrow in Germany) > -----Original Message----- > From: fiware-iot-bounces at lists.fi-ware.eu [mailto:fiware-iot- > bounces at lists.fi-ware.eu] On Behalf Of Juanjo Hierro > Sent: Mittwoch, 22. Juni 2011 22:53 > To: fiware-iot at lists.fi-ware.eu > Subject: [Fiware-iot] Please confirm what is the last version of the > contribution to the IoT Services Enablement chapter > > Hi, > > Is the following document the final submitted contribution to the IoT > chapter ? > > https://forge.fi-ware.eu/docman/view.php/7/166/v013_IOTSE.docx > > I'm asking this because I found several entries linked to different > versions of the IoT Service Enablement chapter (instead of a single one > with the last version uploaded according to instructions on how to > upload contributions) ... I assumed that v013_IOTSE.docx was the last > version based on the numbering included in the filename, but I would like > to doublecheck. > > Thanks, > > -- Juanjo > > > > 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 From lorant.farkas at nsn.com Thu Jun 23 06:58:04 2011 From: lorant.farkas at nsn.com (Farkas, Lorant (NSN - HU/Budapest)) Date: Thu, 23 Jun 2011 07:58:04 +0300 Subject: [Fiware-iot] Please confirm what is the last version of the contribution to the IoT Services Enablement chapter In-Reply-To: <4E025615.8000000@tid.es> References: <4E025615.8000000@tid.es> Message-ID: <93D28BDF64839C468B848D14227151A201ED483D@FIESEXC014.nsn-intra.net> Hi, Our mistake, sorry. As you don't seem to have commented version 0.13, I uploaded this morning version 0.16. https://forge.fi-ware.eu/docman/view.php/7/192/v016_IOTSE.docx But if you commented it in the meantime, we will update v0.16 (or the next v0.17) with them. Thanks & Br, Lorant -----Original Message----- From: fiware-iot-bounces at lists.fi-ware.eu [mailto:fiware-iot-bounces at lists.fi-ware.eu] On Behalf Of ext Juanjo Hierro Sent: Wednesday, June 22, 2011 10:53 PM To: fiware-iot at lists.fi-ware.eu Subject: [Fiware-iot] Please confirm what is the last version of the contribution to the IoT Services Enablement chapter Hi, Is the following document the final submitted contribution to the IoT chapter ? https://forge.fi-ware.eu/docman/view.php/7/166/v013_IOTSE.docx I'm asking this because I found several entries linked to different versions of the IoT Service Enablement chapter (instead of a single one with the last version uploaded according to instructions on how to upload contributions) ... I assumed that v013_IOTSE.docx was the last version based on the numbering included in the filename, but I would like to doublecheck. Thanks, -- Juanjo 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 From lorant.farkas at nsn.com Thu Jun 23 07:08:53 2011 From: lorant.farkas at nsn.com (Farkas, Lorant (NSN - HU/Budapest)) Date: Thu, 23 Jun 2011 08:08:53 +0300 Subject: [Fiware-iot] Weekly minutes Message-ID: <93D28BDF64839C468B848D14227151A201ED4844@FIESEXC014.nsn-intra.net> Dear All, Please find the minutes from yesterday here: https://forge.fi-ware.eu/docman/view.php/11/193/IoT-Minutes-Telco-062220 11.doc Br, Lorant -------------- next part -------------- An HTML attachment was scrubbed... URL: From jhierro at tid.es Thu Jun 23 07:40:44 2011 From: jhierro at tid.es (Juanjo Hierro) Date: Thu, 23 Jun 2011 07:40:44 +0200 Subject: [Fiware-iot] Please confirm what is the last version of the contribution to the IoT Services Enablement chapter In-Reply-To: <93D28BDF64839C468B848D14227151A201ED483D@FIESEXC014.nsn-intra.net> References: <4E025615.8000000@tid.es> <93D28BDF64839C468B848D14227151A201ED483D@FIESEXC014.nsn-intra.net> Message-ID: <4E02D1DC.8000601@tid.es> It's ok. I'll take that one. Hadn't started with the integration yet. Cheers, -- Juanjo On 23/06/11 06:58, Farkas, Lorant (NSN - HU/Budapest) wrote: > Hi, > > Our mistake, sorry. > As you don't seem to have commented version 0.13, I uploaded this morning version 0.16. > https://forge.fi-ware.eu/docman/view.php/7/192/v016_IOTSE.docx > But if you commented it in the meantime, we will update v0.16 (or the next v0.17) with them. > > Thanks& Br, > > Lorant > > -----Original Message----- > From: fiware-iot-bounces at lists.fi-ware.eu [mailto:fiware-iot-bounces at lists.fi-ware.eu] On Behalf Of ext Juanjo Hierro > Sent: Wednesday, June 22, 2011 10:53 PM > To: fiware-iot at lists.fi-ware.eu > Subject: [Fiware-iot] Please confirm what is the last version of the contribution to the IoT Services Enablement chapter > > Hi, > > Is the following document the final submitted contribution to the IoT > chapter ? > > https://forge.fi-ware.eu/docman/view.php/7/166/v013_IOTSE.docx > > I'm asking this because I found several entries linked to different > versions of the IoT Service Enablement chapter (instead of a single one > with the last version uploaded according to instructions on how to > upload contributions) ... I assumed that v013_IOTSE.docx was the last > version based on the numbering included in the filename, but I would > like to doublecheck. > > Thanks, > > -- Juanjo > > > > 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 > . > 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 -------------- A non-text attachment was scrubbed... Name: jhierro.vcf Type: text/x-vcard Size: 429 bytes Desc: not available URL: From lorant.farkas at nsn.com Thu Jun 23 09:09:30 2011 From: lorant.farkas at nsn.com (Farkas, Lorant (NSN - HU/Budapest)) Date: Thu, 23 Jun 2011 10:09:30 +0300 Subject: [Fiware-iot] FW: Doodle: Link for poll "IoT summer vacations" Message-ID: <93D28BDF64839C468B848D14227151A201ED4916@FIESEXC014.nsn-intra.net> Dear All, This is a Doodle voting for summer vacations. Please press "Yes" for the weeks you will be on holiday the entire week, "(Yes)" for the weeks you will be partially on holiday (3 or 4 days out of 5) and "No" for the weeks you are not on holiday (1 or 2 days out of 5). http://doodle.com/szs7fc4zctbcegy4 Thanks & Br, Lorant From oteiza at tid.es Thu Jun 23 11:54:55 2011 From: oteiza at tid.es (FRANCISCO OTEIZA LACALLE) Date: Thu, 23 Jun 2011 11:54:55 +0200 Subject: [Fiware-iot] Weekly meeting In-Reply-To: <8152E2132B13FB488CFD1947E2DEF19C13A7A76F@Polydeuces.office.hd> References: <8152E2132B13FB488CFD1947E2DEF19C13A7A76F@Polydeuces.office.hd> Message-ID: <400B1E0D509AB14C95FFDC1DE303B9A881E0F8025C@EXCLU2K7.hi.inet> Only one comment. In resources management, In the current formulation management is consider as GE. But I?m afraid that we should reformulate this component: 1: keep it as it is, but changing his name by something more specific, IoT services, Resources & Things management (quite long) 2: Split it in two different GE, Things manager and IoT Services & resources manager 3: Split it and move the functional blocks into his respective GE, so we only offer two GE in this task. ( I prefer this option) Fran De: fiware-iot-bounces at lists.fi-ware.eu [mailto:fiware-iot-bounces at lists.fi-ware.eu] En nombre de Ernoe Kovacs Enviado el: mi?rcoles, 22 de junio de 2011 11:23 Para: thierry.nagellen at orange-ftgroup.com; fiware-iot at lists.fi-ware.eu Asunto: Re: [Fiware-iot] Weekly meeting Thierry, Lorant, all, during the PHC we had a discussion on the "grey boxes" and whether that would be the GE. I draw the attached picture for clarification, maybe to be included as an overview somewhere at the beginning of the D2.2 text. Question arising: (a) Are the mentioned "grey boxes" really the generic enablers? They do not look right for me. Rather some blocks of functionality, but not necessary a GE. (b) Also, looking at the names used her (which should mach the ones in the grey boxes of the sub-component diagrams). Without the boxes, they sometimes look rather meaningless (Frontend, Semantic Components, ...) without the further sub-structuring. I have the feeling it was not clear that the grey boxes would be the GEs and they were chosen for different reasons... (c) Furthermore, there are different way of defining the grey boxes. For example in IoT Process Automation we have Exposure Component. usually every GE would have an internal exposure layer and related components. This is clearly showing that the boxes there was made under the assumption the IoT Process Automation is a GE. (d) IMHO, same line of discussion: a GE is an independent piece of software. Would the GE called "AAA" be independent? Let me ask the following questions Q1: Are we agreeing that the picture and the drawn levels are correct (Interfaces, GE, Grouping of GE?)? Q2: Are we agreeing on the mentioned names on the GE level? (To jump ahead, IMHO, we need to revise things...) Q3: Are we agreeing on the multiple IF per GE aspect? Hope this helps in clarifying and better structuring the IoT section. BTW, I suggest to submit to all work packages this picture so that they can draw an overview about their own enablers in the same way. Regards Ern? From: fiware-iot-bounces at lists.fi-ware.eu [mailto:fiware-iot-bounces at lists.fi-ware.eu] On Behalf Of thierry.nagellen at orange-ftgroup.com Sent: Dienstag, 21. Juni 2011 17:01 To: fiware-iot at lists.fi-ware.eu Subject: [Fiware-iot] Weekly meeting Dear all, You can check the last version on the website (https://forge.fi-ware.eu/docman/view.php/11/182/v016_IOTSE.docx ) Based on our meeting with Juanjo, here are the points for the discussion tomorrow: 1. Simplify SotA (too long in our document) 2. Missing points: no updates for Unique Selling Points and What kind of stakeholders should be interested in IoT GEs 3. GEs: regarding the other WPs, the grey boxes from the overall IoT picture could be Generic Enablers (in this case how to define the task level?) 4. Packaging of all architecture pictures 5. Process for the next weeks (merging all WPs documents) => final D2.2 deliveablre planned now for mid-July BR Thierry ________________________________ 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: From sabrina.guerra at telecomitalia.it Tue Jun 28 10:43:56 2011 From: sabrina.guerra at telecomitalia.it (Guerra Sabrina) Date: Tue, 28 Jun 2011 10:43:56 +0200 Subject: [Fiware-iot] IoT Communication: new version of the architecture description In-Reply-To: <36A93B31228D3B49B691AD31652BCAE9A5331DDAEA@GRFMBX702BA020.griffon.local> References: <36A93B31228D3B49B691AD31652BCAE9A5331DDAEA@GRFMBX702BA020.griffon.local> Message-ID: <36A93B31228D3B49B691AD31652BCAE9A533A06C4F@GRFMBX702BA020.griffon.local> Hi all, we submit on Fusion Forge a revised version of our contribution (IoT_Communication-Architecture-v03.doc) . This contribution concerns the IoTCommunication chapter that has been extracted from the document v016_IOTSE.doc. We have updated the list of the stakeholders and the list of the Unique Selling Points (new Unique Selling Point has been added: "Virtualization of resources and abstraction from the heterogeneity of the physical world"). At the end of this document we have synthetized the SoTA. Bye, Sabrina and Gian Piero 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: -------------- 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: From ignacio.solerjubert at atosresearch.eu Tue Jun 28 14:15:13 2011 From: ignacio.solerjubert at atosresearch.eu (Ignacio Soler Jubert) Date: Tue, 28 Jun 2011 14:15:13 +0200 Subject: [Fiware-iot] [Good Bye] - See you soon! Message-ID: Dear all, After a while in Atos (7 years) .. winds of change are coming. I have decided to leave the company at the end of the month. I would like to thank all of you for all the lessons learned with all of you, and all the nice moments everywhere in Europe. I hereby want to provide to you my personal coordinates: Ignacio Soler GSM: +34 600 580 080 nacho.soler at gmail.com http://www.linkedin.com/pub/ignacio-soler/2/5a4/686 skype: Ignacio.soler With my best wishes of success, Ignacio Further issues related to Atos activities in the project please contact Jorge Pereira: Jorge.pereirac at atosresearch.eu ------------------------------------------------------------------ This e-mail and the documents attached are confidential and intended solely for the addressee; it may also be privileged. If you receive this e-mail in error, please notify the sender immediately and destroy it. As its integrity cannot be secured on the Internet, the Atos Origin group liability cannot be triggered for the message content. Although the sender endeavours to maintain a computer virus-free network, the sender does not warrant that this transmission is virus-free and will not be liable for any damages resulting from any virus transmitted. Este mensaje y los ficheros adjuntos pueden contener informacion confidencial destinada solamente a la(s) persona(s) mencionadas anteriormente pueden estar protegidos por secreto profesional. Si usted recibe este correo electronico por error, gracias por informar inmediatamente al remitente y destruir el mensaje. Al no estar asegurada la integridad de este mensaje sobre la red, Atos Origin no se hace responsable por su contenido. Su contenido no constituye ningun compromiso para el grupo Atos Origin, salvo ratificacion escrita por ambas partes. Aunque se esfuerza al maximo por mantener su red libre de virus, el emisor no puede garantizar nada al respecto y no sera responsable de cualesquiera danos que puedan resultar de una transmision de virus. ------------------------------------------------------------------ -------------- next part -------------- An HTML attachment was scrubbed... URL: From lorant.farkas at nsn.com Tue Jun 28 16:36:40 2011 From: lorant.farkas at nsn.com (Farkas, Lorant (NSN - HU/Budapest)) Date: Tue, 28 Jun 2011 17:36:40 +0300 Subject: [Fiware-iot] Weekly meeting for tomorrow cancelled Message-ID: <93D28BDF64839C468B848D14227151A201F3D4AC@FIESEXC014.nsn-intra.net> Dear All, We are working on the latest comments by Juanjo and there are chances that we are not able to finish before our weekly meeting tomorrow, therefore we propose to cancel the meeting tomorrow. We will provide more information and the new consolidated version of the doc before the end of the week. Thierry is not able to access his company e-mail, therefore we cannot cancel the meeting from your calendars, I would ask you to do it by hand. Sorry for the inconvenience. Thanks & Br, Lorant -------------- next part -------------- An HTML attachment was scrubbed... URL: From thierry.nagellen at orange-ftgroup.com Tue Jun 28 23:32:44 2011 From: thierry.nagellen at orange-ftgroup.com (thierry.nagellen at orange-ftgroup.com) Date: Tue, 28 Jun 2011 23:32:44 +0200 Subject: [Fiware-iot] =?iso-8859-1?q?Annul=E9=3A_IoT_Weekly_Telco?= Message-ID: Quand : mercredi 29 juin 2011 10:00-11:30 (GMT+01:00) Brussels, Copenhagen, Madrid, Paris. Remarque : le d?calage GMT ci-dessus ne tient pas compte des r?glages de l'heure d'?t?. *~*~*~*~*~*~*~*~*~* Dear all To avoid any misunderstanding I've cancelled the previous weekly meeting at 9:30 and submit a new one at 10:00 AM. We will have to discuss later how we will organize the meetings during vacation times and for the second version of D2.2. BR Thierry --------------------------------------------------- Meeting Number: 709 472 921 Meeting Password: FI-WARE ------------------------------------------------------- To join the online meeting ------------------------------------------------------- 1. Go to https://nsn.webex.com/nsn/j.php?ED=175018962&UID=0&PW=NYzEzYWM0ZTNk&RT=MTgjMjM%3D 2. Enter your name and email address. 3. Enter the meeting password: FI-WARE 4. Click "Join Now". To view in other time zones or languages, please click the link: https://nsn.webex.com/nsn/j.php?ED=175018962&UID=0&PW=NYzEzYWM0ZTNk&ORT=MTgjMjM%3D ------------------------------------------------------- NSN Voice Conference information Conference ID: 58465 PIN: 9012 Making a conference call - from the office: 8071870 (in Finland and Germany) - from out of office: +358 7180 71870 (in Finland) and +49 89 5159 43800 (in Germany) All out-of-office conference access numbers are listed in page . Country/Site Conference access number All sites From company office conference phone or desk phone 8071870. This number also works from company mobiles in several countries. See Internal Numbers page for more information. Argentina - Buenos Aires +54 11 5983 9400 (PRIMARY) or +54 11 4814 9373 Argentina - Cordoba +54 35 1568 2208 Australia - Sydney +61 28 014 7189 (PRIMARY) or +61 29 429 9664 Australia - Melbourne +61 38 739 4333 Austria +43 72 088 0245 Bahrain +97 31 619 9028 Belgium - Generic +32 1448 0116 Belgium - Diegem-Machelen +32 2710 3300 Brazil - Belo Horizonte +55 31 3956 0546 Brazil - Brazil +55 61 3717 2043 Brazil - Curitiba +55 41 3906 0826 Brazil - Manaus +55 92 3652 7576 Brazil - Rio De Janeiro +55 21 3958 0804 (PRIMARY) or +55 21 3431 1999 Brazil - Salvador +55 71 3717 5351 Brazil - Sao Paolo +55 11 5508 0630 Bulgaria +359 2491 7085 Canada - Ajax +1 90 5619 4346 Canada - Burnaby +1 60 4456 5897 Canada - Hamilton +1 905 581 0212 Canada - Mississauga +1 289 360 3950 Canada - Montreal +1 51 4789 9125 Canada - Ottawa +1 61 3800 0568 Chile - Santiago +56 2350 6485 China - Mainland +86 10 8405 5000 ext 1870 China - Beijing +86 10 8405 5000 ext 1870 China - Chengdu +86 28 8689 0188 ext 1870 China - Dongguan +86 0769 2240 2844 ext 1870 China - Guangzhou +86 20 8755 6190 ext 1870 China - Hangzhou +86 571 8722 0877 ext 1870 China - Hong Kong +852 259 70220 ext 1870 China - Kunming +86 871 362 2880 ext 1870 China - Shanghai +86 21 6101 1870 ext 1870 China - ShenZhen +86 755 8613 3688 ext 1870 China - Suzhou +86 512 6761 6166 ext 1870 China - Zhengzhou +86 371 6566 9768 ext 1870 Colombia +57 1640 7979 ext 444 Croatia +38 51 777 6122 Czech Republic +42 02 460 19300 Denmark +45 699 18450 (PRIMARY) or +45 3329 2882 Egypt +97 31 619 9028 (Bahrain nbr) Estonia +37 266 67297 Finland +358 7180 71870 France +33 17 061 7813 (PRIMARY) or +33 14 915 1553 Germany +49 89 5159 43800 Greece +30 21 1176 8207 (PRIMARY) or +30 21 1120 3677 Hungary - Budapest +36 17 009 888 Hungary - Kom?rom +36 20 884 2499 India 000 800 100 7777 Indonesia - Jakarta (Menara Mulia/Plaza Kuningan +62 21 2557 9102 Indonesia - Bandung +62 22 8427 5992 Indonesia - Medan +62 61 3001 2702 Indonesia - Semarang +62 24 3300 0702 Ireland +353 1526 2862 Israel +97 29 775 1700 Italy - Milan +39 024 004 2007 Italy - Rome +39 069 481 6656 Japan +81 3 4578 0230 (PRIMARY) or +81 3 5474 7979 Kuwait +97 31 619 9028 (Bahrain nbr) Latvia +37 16 765 2510 Lithuania +37 0 5205 8994 Luxembourg +352 2088 0106 Malaysia +60 323 029 009 Mexico - Mexico City +52 55 3686 9759 (PRIMARY) or +52 55 5261 7245 Mexico - Reynosa +52 89 9909 1555 Netherlands +31 79 346 5225 New Zealand +64 9306 6933 Norway - Oslo +47 21 548 223 Oman +97 31 619 9028 (Bahrain nbr) Pakistan +92 512 092 444 Panama +507 832 7981 Peru +51 1708 5370 (PRIMARY) or +51 1215 7650 Philippines +63 2754 1700 Poland - Warsaw +48 22 398 8116 Poland - Wroclaw +48 71 718 1215 Portugal +351 21 044 4698 Qatar +97 31 619 9028 (Bahrain nbr) Romania +40 36 440 3799 Russia +74 95 725 2706 Saudi Arabia +97 31 619 9028 (Bahrain nbr) Singapore +65 3103 1065 (PRIMARY) or +65 6723 2582 Slovakia +42 12 3300 6924 Slovenia +38 61 600 2713 South Africa - Johannesburg +27 1 0500 2221 South Africa - Pretoria +27 1 2004 2334 South Korea - Masan +82 5 5290 7690 South Korea - Seoul +82 2 2186 5088 Spain +349 1187 5929 Sweden +46 85 250 0862 (PRIMARY), +46 84 100 9299 Switzerland +41 44 279 7943 Taiwan +88 62 8175 9298 Thailand +66 2762 6750 Turkey +90 216 570 2345 Ukraine +38 044 520 2272 UK +44 12 5275 8334 UK - Camberley +44 12 5286 5849 UK - Church Crookham +44 12 5261 1100 UK - Huntingdon +44 14 8087 8220 (PRIMARY), +44 14 8044 4206 UK - London +44 20 3318 1924 United Arab Emirates +97 31 619 9028 (Bahrain nbr) USA - Alpharetta +1 770 871 3050 USA - Arizona +1 480 588 3748 USA - Atlanta +1 404 236 4550 USA - Atlanta Notheast +1 678 317 3165 USA - Austin/Round Rock +1 512 600 2027 USA - Belleville +1 973 547 7982 USA - Boca Raton +1 561 910 2843 USA - Boston +1 617 963 8320 (PRIMARY) or +1 781 993 4850 USA - Burlington +1 781 993 4850 USA - Calabasas +1 818 914 0215 USA - Canoga Park +1 818 914 0215 USA - Cary +1 919 655 1388 USA - Chelmsford/Littleton +1 978 679 0233 USA - Chicago +1 773 303 4710 USA - Dallas +1 214 269 7626 USA - Dallas/Fort Worth +1 214 270 0352 USA - Greenville, NC +1 252 329 1677 USA - Herndon +1 703 483 4485 USA - Johnson City +1 423 952 1545 USA - Kirkland +1 425 242 3113 USA - Miami +1 786 388 4150 or +1 786 329 7177 USA - Naperville +1 630 596 2203 USA - New Brunswick +1 732 579 6483 USA - New Century, KS +1 913 254 5900 USA - New York White Plains +1 914 368 0650 USA - New York Peekskill, White Plains +1 914 293 1885 USA - Palo Alto +1 650 644 1349 USA - Redmond +1 425 242 3113 USA - San Diego +1 858 769 5309 or +1 619 330 9699 USA - Sunnyvale +1 408 419 1750 USA - Washington D.C +1 202 552 4781 Vietnam +84 4 3724 6110 Yemen +97 31 619 9028 (Bahrain nbr) Please check and prioritize them. If there is no access number for your country then please use access numbers of the area where to the calling costs are lowest. ------------------------------------------------------- For assistance ------------------------------------------------------- 1. Go to https://nsn.webex.com/nsn/mc 2. On the left navigation bar, click "Support". You can contact me at: lorant.farkas at nsn.com To add this meeting to your calendar program (for example Microsoft Outlook), click this link: https://nsn.webex.com/nsn/j.php?ED=175018962&UID=0&ICS=MI&LD=1&RD=18&ST=1&SHA2=gVmoQ/CXj05nzcI-4TFgQ2qtqmAulzDfzoOWKpcyLyg=&RT=MTgjMjM%3D -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: meeting.ics Type: text/calendar Size: 11060 bytes Desc: not available URL: