From lorant.farkas at nsn.com Mon Jul 4 13:25:39 2011 From: lorant.farkas at nsn.com (Farkas, Lorant (NSN - HU/Budapest)) Date: Mon, 4 Jul 2011 14:25:39 +0300 Subject: [Fiware-iot] task 7.1 References: <9A1182381FFDE14CAB9A25A4B695126A0145026F16@FIESEXC014.nsn-intra.net> Message-ID: <93D28BDF64839C468B848D14227151A2C530F6@FIESEXC014.nsn-intra.net> Dear Sabrina and Gian Piero, Could you please check potential overlaps of IoT communications with task 7.1 from the Interface to the Networks and express an opinion about it? Thanks & br, Lorant From thierry.nagellen at orange-ftgroup.com Tue Jul 5 17:09:28 2011 From: thierry.nagellen at orange-ftgroup.com (thierry.nagellen at orange-ftgroup.com) Date: Tue, 5 Jul 2011 17:09:28 +0200 Subject: [Fiware-iot] =?iso-8859-1?q?Annul=E9=3A_IoT_Weekly_Telco?= Message-ID: Quand : mercredi 6 juillet 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?. *~*~*~*~*~*~*~*~*~* I'm travelling tomorrow and we have just finished a version fro integration (I will uploaded it this evening) so I prefer to cancelled the meeting tomorrow and I will check with lorant if we can plan it for Friday morning. 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: 11034 bytes Desc: not available URL: From thierry.nagellen at orange-ftgroup.com Thu Jul 7 07:59:49 2011 From: thierry.nagellen at orange-ftgroup.com (thierry.nagellen at orange-ftgroup.com) Date: Thu, 7 Jul 2011 07:59:49 +0200 Subject: [Fiware-iot] IoT weekly meeting Message-ID: Quand : vendredi 8 juillet 2011 09:00-10: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?. *~*~*~*~*~*~*~*~*~* Dear all, We will discuss the following points: Last version validated with Juanjo to have a global consistency with the other technical chapters (main point: Publish/Subscribe has been transfered from Process Automation to Data Handling) Architecture Board the 11th & 12th in Madrid: dedicated topics to address to the other projects Mapping of the assets 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: 9899 bytes Desc: not available URL: From lorant.farkas at nsn.com Thu Jul 7 10:28:31 2011 From: lorant.farkas at nsn.com (Farkas, Lorant (NSN - HU/Budapest)) Date: Thu, 7 Jul 2011 11:28:31 +0300 Subject: [Fiware-iot] IoT weekly meeting In-Reply-To: References: Message-ID: <93D28BDF64839C468B848D14227151A201FB793F@FIESEXC014.nsn-intra.net> The correct webex link for tomorrow is: https://nsn.webex.com/nsn/j.php?ED=175018962&UID=0&PW=NYzEzYWM0ZTNk&RT=MTgjMjM%3D Br, Lorant > _____________________________________________ > From: NAGELLEN Thierry RD-BIZZ-SOP [mailto:thierry.nagellen at orange-ftgroup.com] > Sent: Thursday, July 07, 2011 8:00 AM > To: fiware-iot at lists.fi-ware.eu > Subject: [Fiware-iot] IoT weekly meeting > When: 2011. j?lius 8. 9:00-10:00 (GMT+01:00) Belgrade, Bratislava, Budapest, Ljubljana, Prague. > Where: > > Dear all, > > We will discuss the following points: > > Last version validated with Juanjo to have a global consistency with the other technical chapters (main point: Publish/Subscribe has been transfered from Process Automation to Data Handling) > > Architecture Board the 11th & 12th in Madrid: dedicated topics to address to the other projects > > Mapping of the assets > > 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 > << File: ATT291309.txt >> -------------- next part -------------- An HTML attachment was scrubbed... URL: From Ernoe.Kovacs at neclab.eu Thu Jul 7 10:51:15 2011 From: Ernoe.Kovacs at neclab.eu (Ernoe Kovacs) Date: Thu, 7 Jul 2011 08:51:15 +0000 Subject: [Fiware-iot] IoT weekly meeting In-Reply-To: References: Message-ID: <8152E2132B13FB488CFD1947E2DEF19C1CED1A5B@DAPHNIS.office.hd> Hi all, I am out tomorrow. Sorry. - Ernoe -----Original Appointment----- From: NAGELLEN Thierry RD-BIZZ-SOP [mailto:thierry.nagellen at orange-ftgroup.com] Sent: Donnerstag, 7. Juli 2011 08:00 To: 'fiware-iot at lists.fi-ware.eu' Subject: [Fiware-iot] IoT weekly meeting When: Freitag, 8. Juli 2011 09:00-10:00 (UTC+01:00) Amsterdam, Berlin, Bern, Rome, Stockholm, Vienna. Where: Dear all, We will discuss the following points: Last version validated with Juanjo to have a global consistency with the other technical chapters (main point: Publish/Subscribe has been transfered from Process Automation to Data Handling) Architecture Board the 11th & 12th in Madrid: dedicated topics to address to the other projects Mapping of the assets 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 << File: ATT00001.txt >> -------------- next part -------------- An HTML attachment was scrubbed... URL: From thierry.nagellen at orange-ftgroup.com Thu Jul 7 11:54:26 2011 From: thierry.nagellen at orange-ftgroup.com (thierry.nagellen at orange-ftgroup.com) Date: Thu, 7 Jul 2011 11:54:26 +0200 Subject: [Fiware-iot] Docs on the forge Message-ID: Hi all, The forge is open again. You can find the last version of IoT part in Consolidated versions (v024) et architectures pictures (v06) into Drawing Contributions. https://forge.fi-ware.eu/docman/?group_id=11&feedback=Document%20submitt ed%20sucessfully BR Thierry Nagellen Orange Labs Networks & Carriers 905 rue Albert Einstein 06921 Sophia Antipolis Cedex +33 492 94 52 84 +33 679 85 08 44 -------------- next part -------------- An HTML attachment was scrubbed... URL: From lorant.farkas at nsn.com Mon Jul 11 08:00:52 2011 From: lorant.farkas at nsn.com (Farkas, Lorant (NSN - HU/Budapest)) Date: Mon, 11 Jul 2011 09:00:52 +0300 Subject: [Fiware-iot] Minutes, 08 July 2011 Message-ID: <93D28BDF64839C468B848D14227151A201FF929B@FIESEXC014.nsn-intra.net> Dear All, Please find under the attached link the minutes of our weekly meeting from Friday. https://forge.fi-ware.eu/docman/view.php/11/243/IoT-Minutes-Telco-070820 11.doc Br, Lorant -------------- next part -------------- An HTML attachment was scrubbed... URL: From lorant.farkas at nsn.com Mon Jul 11 08:07:06 2011 From: lorant.farkas at nsn.com (Farkas, Lorant (NSN - HU/Budapest)) Date: Mon, 11 Jul 2011 09:07:06 +0300 Subject: [Fiware-iot] Partner asset table Message-ID: <93D28BDF64839C468B848D14227151A201FF92A3@FIESEXC014.nsn-intra.net> Dear All, Please find under the following links: -the partner asset table, old version, from the time of the project preparation, https://forge.fi-ware.eu/docman/view.php/11/244/old_IoT_platform_asset_t able_v4.xls -the version 01 put together by Thierry during last week, https://forge.fi-ware.eu/docman/view.php/11/245/v01_IoT-Architecture-Ass ets-mapping.xlsx Br, Lorant -------------- next part -------------- An HTML attachment was scrubbed... URL: From rheras at tid.es Mon Jul 11 13:29:28 2011 From: rheras at tid.es (Ricardo de las Heras) Date: Mon, 11 Jul 2011 13:29:28 +0200 Subject: [Fiware-iot] Minutes, 08 July 2011 In-Reply-To: <93D28BDF64839C468B848D14227151A201FF929B@FIESEXC014.nsn-intra.net> References: <93D28BDF64839C468B848D14227151A201FF929B@FIESEXC014.nsn-intra.net> Message-ID: <4E1ADE98.3040402@tid.es> An HTML attachment was scrubbed... URL: From Martin.Bauer at neclab.eu Mon Jul 11 13:49:25 2011 From: Martin.Bauer at neclab.eu (Martin Bauer) Date: Mon, 11 Jul 2011 11:49:25 +0000 Subject: [Fiware-iot] Minutes, 08 July 2011 In-Reply-To: <4E1ADE98.3040402@tid.es> References: <93D28BDF64839C468B848D14227151A201FF929B@FIESEXC014.nsn-intra.net> <4E1ADE98.3040402@tid.es> Message-ID: Hi Ricardo, all, I think it could be a grave mistake to completely remove the publish/subscribe aspects from WP5. I am not sure that the particular aspects relevant for IoT are taken into account by WP6 - I have only started reading the deliverable, so I don't know what is currently there. Of course, we have to see how we integrate the WP5 and WP6 enablers. The question is also whether our data enabler will be usable stand-alone or whether it is just a kind of "helper" for the WP6 enabler. 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 Ricardo de las Heras Sent: Montag, 11. Juli 2011 13:29 To: Farkas, Lorant (NSN - HU/Budapest) Cc: fiware-iot at lists.fi-ware.eu Subject: Re: [Fiware-iot] Minutes, 08 July 2011 Dear Lorant, there is a misunderstanding according to the minutes, please I would like to clarify it. When I referred to CEP and Pub/Subs/Notify, I said that we should NOT include the description of these type of technologies/assets in both wps: WP5 and WP6. It doesn't make sense, because we are writing a unique document, and those type of technologies are already covered by WP6, indeed both are part of its core. So, we can make references to them, because we need of course these technologies in the IoT (WP5) as well, but we should not duplicate their description in the deliverable of HLD. Indeed Juanjo removed the paragraphs we had in the Data handling task (T5.3). Finally, the idea I exposed is that we can use both technologies in a local scope (example of a house, monitored by sensors, intelligent ambients, etc), not as a Generic Enabler for the Fiware platform, because those assets are provided by WP6. I hope this clarifies the comments I did by phone on Fridays' conf. call. thanks, best, Ricardo. Farkas, Lorant (NSN - HU/Budapest) wrote: Dear All, Please find under the attached link the minutes of our weekly meeting from Friday. https://forge.fi-ware.eu/docman/view.php/11/243/IoT-Minutes-Telco-07082011.doc Br, Lorant -- ------------------------------------- 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: From thierry.nagellen at orange-ftgroup.com Mon Jul 11 14:33:37 2011 From: thierry.nagellen at orange-ftgroup.com (thierry.nagellen at orange-ftgroup.com) Date: Mon, 11 Jul 2011 14:33:37 +0200 Subject: [Fiware-iot] Minutes, 08 July 2011 In-Reply-To: References: <93D28BDF64839C468B848D14227151A201FF929B@FIESEXC014.nsn-intra.net><4E1ADE98.3040402@tid.es> Message-ID: Dear all, This is not an open question. We assume that specific topics are related to IoT and that we have to manage the collaboration and interface with WP6 Data & Context management. Please read carefully CEP and Pub/Sub assets description in the high level architecture deliverable and you will identify the missing points for IoT. I did it and I have some items that are not covered. We are here to work in a coherent way with the other WPs and to improve technically what is not possible today and there are lots of hole we have to fulfil. Please, check this Chinese initiative which expect a campus with 15;000 Engineers in 3 years dedicated to IoT and from European point of view we have lots to do to be able to compete with them. http://www.nacsa.com/archives/files/wuxi_event_20100526.pdf BR Thierry De : fiware-iot-bounces at lists.fi-ware.eu [mailto:fiware-iot-bounces at lists.fi-ware.eu] De la part de Martin Bauer Envoy? : lundi 11 juillet 2011 13:49 ? : Ricardo de las Heras; Farkas, Lorant (NSN - HU/Budapest) Cc : fiware-iot at lists.fi-ware.eu Objet : Re: [Fiware-iot] Minutes, 08 July 2011 Hi Ricardo, all, I think it could be a grave mistake to completely remove the publish/subscribe aspects from WP5. I am not sure that the particular aspects relevant for IoT are taken into account by WP6 - I have only started reading the deliverable, so I don't know what is currently there. Of course, we have to see how we integrate the WP5 and WP6 enablers. The question is also whether our data enabler will be usable stand-alone or whether it is just a kind of "helper" for the WP6 enabler. 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 Ricardo de las Heras Sent: Montag, 11. Juli 2011 13:29 To: Farkas, Lorant (NSN - HU/Budapest) Cc: fiware-iot at lists.fi-ware.eu Subject: Re: [Fiware-iot] Minutes, 08 July 2011 Dear Lorant, there is a misunderstanding according to the minutes, please I would like to clarify it. When I referred to CEP and Pub/Subs/Notify, I said that we should NOT include the description of these type of technologies/assets in both wps: WP5 and WP6. It doesn't make sense, because we are writing a unique document, and those type of technologies are already covered by WP6, indeed both are part of its core. So, we can make references to them, because we need of course these technologies in the IoT (WP5) as well, but we should not duplicate their description in the deliverable of HLD. Indeed Juanjo removed the paragraphs we had in the Data handling task (T5.3). Finally, the idea I exposed is that we can use both technologies in a local scope (example of a house, monitored by sensors, intelligent ambients, etc), not as a Generic Enabler for the Fiware platform, because those assets are provided by WP6. I hope this clarifies the comments I did by phone on Fridays' conf. call. thanks, best, Ricardo. Farkas, Lorant (NSN - HU/Budapest) wrote: Dear All, Please find under the attached link the minutes of our weekly meeting from Friday. https://forge.fi-ware.eu/docman/view.php/11/243/IoT-Minutes-Telco-07082011.doc Br, Lorant -- ------------------------------------- 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: From rheras at tid.es Mon Jul 11 15:13:33 2011 From: rheras at tid.es (Ricardo de las Heras) Date: Mon, 11 Jul 2011 15:13:33 +0200 Subject: [Fiware-iot] Minutes, 08 July 2011 In-Reply-To: References: <93D28BDF64839C468B848D14227151A201FF929B@FIESEXC014.nsn-intra.net> <4E1ADE98.3040402@tid.es> Message-ID: <4E1AF6FD.8000309@tid.es> An HTML attachment was scrubbed... URL: From gianpiero.fici at telecomitalia.it Tue Jul 12 11:42:18 2011 From: gianpiero.fici at telecomitalia.it (Fici Gian Piero) Date: Tue, 12 Jul 2011 11:42:18 +0200 Subject: [Fiware-iot] R: task 7.1 In-Reply-To: <93D28BDF64839C468B848D14227151A2C530F6@FIESEXC014.nsn-intra.net> References: <9A1182381FFDE14CAB9A25A4B695126A0145026F16@FIESEXC014.nsn-intra.net> <93D28BDF64839C468B848D14227151A2C530F6@FIESEXC014.nsn-intra.net> Message-ID: Hi Lorant and everybody, I had a look at the description of the task 7 (Interface to Networks and Devices - I2ND) and in particular at the work package 1 (Connected Devices Interfacing - CDI). You can find the file attached, since I do not know if all of you can access their document (I had it from Pier Garino that is the task leader). In the task 7 they defined 4 GEs: (1) Connected Device Interfacing (CDI), i.e. Interfaces to end devices (addressed by connected device), (2) Cloud Edge (CE), i.e. interfaces to gateways (cloud proxy), (3) Network Information & Control (NetIC), i.e. interfaces to connectivity functions inside the network (open networking), (4) Service, Capability, Connectivity and Control (S3C), i.e. interfaces to services offered by the network operators (network services). All of these GEs have relations with our platform (in particular CDI and CE) and the I2ND descriptions are very complete and ambitious, but there is no explicit link to our platform. It looks like the applications/services use directly those interfaces, or better they do not mind if there is something in between. Maybe I was not able to understand correctly their descriptions, but I see that we put in our figures a relationship with the other tasks (not only Interface to the Networks, but also Data & Context Management Services; Security, Privacy, Trust; Applications & Services Ecosystem and Delivery Framework) but I2ND did not put any relationships with us. I think it is worth to try to understand together with them how they see the overall picture of the FI-WARE architecture. I already contacted directly my colleague Pier Garino for a brief exchange of ideas but unfortunately (well, not really :-) I will be away for the rest of the week on vacation and I will be back on July 19th, so any further information will be delayed to next week. (I will not participate to the weekly call conference tomorrow, sorry). I hope these short notes are clear enough. :-) Bye, Gian Piero -----Messaggio originale----- Da: fiware-iot-bounces at lists.fi-ware.eu [mailto:fiware-iot-bounces at lists.fi-ware.eu] Per conto di Farkas, Lorant (NSN - HU/Budapest) Inviato: luned? 4 luglio 2011 13:26 A: Farkas, Lorant (NSN - HU/Budapest); fiware-iot at lists.fi-ware.eu Cc: Nemeth, Lorant (NSN - HU/Budapest) Oggetto: [Fiware-iot] task 7.1 Dear Sabrina and Gian Piero, Could you please check potential overlaps of IoT communications with task 7.1 from the Interface to the Networks and express an opinion about it? Thanks & br, Lorant _______________________________________________ Fiware-iot mailing list Fiware-iot at lists.fi-ware.eu http://lists.fi-ware.eu/listinfo/fiware-iot 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. -------------- next part -------------- A non-text attachment was scrubbed... Name: FI-WARE High-Level Description 11-07-06 - Copy.zip Type: application/x-zip-compressed Size: 2663566 bytes Desc: FI-WARE High-Level Description 11-07-06 - Copy.zip URL: From thierry.nagellen at orange-ftgroup.com Tue Jul 12 11:55:35 2011 From: thierry.nagellen at orange-ftgroup.com (thierry.nagellen at orange-ftgroup.com) Date: Tue, 12 Jul 2011 11:55:35 +0200 Subject: [Fiware-iot] R: task 7.1 In-Reply-To: References: <9A1182381FFDE14CAB9A25A4B695126A0145026F16@FIESEXC014.nsn-intra.net><93D28BDF64839C468B848D14227151A2C530F6@FIESEXC014.nsn-intra.net> Message-ID: Hi all Some feedback from the Architecture Board about this subject IoT Communication and CDI. It is not clear also for the reader what does it mean "sensor" in the picture of task 7.1. The main answer for the moment (but we have to clarify it) is that task 7.1 would more managed this aspect for mobile devices (or classical devices for telcos). So we could understand that this enabler should support our approach in IoT communication but we need really a clarification. Another point is also Cloud Proxy and how it could be an IoT Gateway managing all devices into the house. My understanding at this moment is that it is more a gateway we try to include as part of the cloud, and not really an IoT gateway but we know also that some boxes could include for example Zigbee technology but we have also to manage also this issue. BR THierry -----Message d'origine----- De?: fiware-iot-bounces at lists.fi-ware.eu [mailto:fiware-iot-bounces at lists.fi-ware.eu] De la part de Fici Gian Piero Envoy??: mardi 12 juillet 2011 11:42 ??: Farkas, Lorant (NSN - HU/Budapest); fiware-iot at lists.fi-ware.eu Cc?: Nemeth, Lorant (NSN - HU/Budapest) Objet?: [Fiware-iot] R: task 7.1 Hi Lorant and everybody, I had a look at the description of the task 7 (Interface to Networks and Devices - I2ND) and in particular at the work package 1 (Connected Devices Interfacing - CDI). You can find the file attached, since I do not know if all of you can access their document (I had it from Pier Garino that is the task leader). In the task 7 they defined 4 GEs: (1) Connected Device Interfacing (CDI), i.e. Interfaces to end devices (addressed by connected device), (2) Cloud Edge (CE), i.e. interfaces to gateways (cloud proxy), (3) Network Information & Control (NetIC), i.e. interfaces to connectivity functions inside the network (open networking), (4) Service, Capability, Connectivity and Control (S3C), i.e. interfaces to services offered by the network operators (network services). All of these GEs have relations with our platform (in particular CDI and CE) and the I2ND descriptions are very complete and ambitious, but there is no explicit link to our platform. It looks like the applications/services use directly those interfaces, or better they do not mind if there is something in between. Maybe I was not able to understand correctly their descriptions, but I see that we put in our figures a relationship with the other tasks (not only Interface to the Networks, but also Data & Context Management Services; Security, Privacy, Trust; Applications & Services Ecosystem and Delivery Framework) but I2ND did not put any relationships with us. I think it is worth to try to understand together with them how they see the overall picture of the FI-WARE architecture. I already contacted directly my colleague Pier Garino for a brief exchange of ideas but unfortunately (well, not really :-) I will be away for the rest of the week on vacation and I will be back on July 19th, so any further information will be delayed to next week. (I will not participate to the weekly call conference tomorrow, sorry). I hope these short notes are clear enough. :-) Bye, Gian Piero -----Messaggio originale----- Da: fiware-iot-bounces at lists.fi-ware.eu [mailto:fiware-iot-bounces at lists.fi-ware.eu] Per conto di Farkas, Lorant (NSN - HU/Budapest) Inviato: luned? 4 luglio 2011 13:26 A: Farkas, Lorant (NSN - HU/Budapest); fiware-iot at lists.fi-ware.eu Cc: Nemeth, Lorant (NSN - HU/Budapest) Oggetto: [Fiware-iot] task 7.1 Dear Sabrina and Gian Piero, Could you please check potential overlaps of IoT communications with task 7.1 from the Interface to the Networks and express an opinion about it? Thanks & br, Lorant _______________________________________________ Fiware-iot mailing list Fiware-iot at lists.fi-ware.eu http://lists.fi-ware.eu/listinfo/fiware-iot 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. From lorant.farkas at nsn.com Tue Jul 12 13:47:23 2011 From: lorant.farkas at nsn.com (Farkas, Lorant (NSN - HU/Budapest)) Date: Tue, 12 Jul 2011 14:47:23 +0300 Subject: [Fiware-iot] Review of technical chapters Message-ID: <93D28BDF64839C468B848D14227151A201FF99AE@FIESEXC014.nsn-intra.net> Dear All, I made a review of the Data and Context Management chapter, please find it attached here. https://forge.fi-ware.eu/docman/view.php/11/251/LF_FI-WARE+High-Level+De scription+integrated+draft+0.1+11-07-06.doc Martin, if you have not started to review this yet, you could maybe edit this file directly. I will now start to review the ASE as stated in the minutes. Thanks & Br, Lorant -------------- next part -------------- An HTML attachment was scrubbed... URL: From Martin.Bauer at neclab.eu Tue Jul 12 18:35:18 2011 From: Martin.Bauer at neclab.eu (Martin Bauer) Date: Tue, 12 Jul 2011 16:35:18 +0000 Subject: [Fiware-iot] Review of technical chapters In-Reply-To: <93D28BDF64839C468B848D14227151A201FF99AE@FIESEXC014.nsn-intra.net> References: <93D28BDF64839C468B848D14227151A201FF99AE@FIESEXC014.nsn-intra.net> Message-ID: Hi all, I provided my review of Chapter 4 - Data and Context Management, adding my comments to the document provided by Lorant and uploading it to the same folder as Lorant. (Is there a way to simply provide a new version - I was not able to quickly figure it out.) As a co-author I was happy to find pieces of the OMA NGSI Context Interface in the P/S Broker part, but I would have liked it even better if it had been referenced. Regarding the specification of the actual enabler (which is something the OMA NGSI does not address as it only specifies an interface) I anyway expressed some concerns in my comment. 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 Farkas, Lorant (NSN - HU/Budapest) Sent: Dienstag, 12. Juli 2011 13:47 To: fiware-iot at lists.fi-ware.eu Subject: [Fiware-iot] Review of technical chapters Dear All, I made a review of the Data and Context Management chapter, please find it attached here. https://forge.fi-ware.eu/docman/view.php/11/251/LF_FI-WARE+High-Level+Description+integrated+draft+0.1+11-07-06.doc Martin, if you have not started to review this yet, you could maybe edit this file directly. I will now start to review the ASE as stated in the minutes. Thanks & Br, Lorant -------------- next part -------------- An HTML attachment was scrubbed... URL: From jorge.pereirac at atosresearch.eu Tue Jul 12 21:20:21 2011 From: jorge.pereirac at atosresearch.eu (Jorge Pereira Carlos) Date: Tue, 12 Jul 2011 21:20:21 +0200 Subject: [Fiware-iot] Review of technical chapters In-Reply-To: References: <93D28BDF64839C468B848D14227151A201FF99AE@FIESEXC014.nsn-intra.net> Message-ID: <2EE66FDA12949F488E5115A9974BB42C0506BB3D@INTMAIL02.es.int.atosorigin.com> Dear all, I just submitted in https://forge.fi-ware.eu/docman/view.php/11/260/ATOS_ML__FI-WARE+High-Level+Description+-+Security+chapter+-+v1-1.0.doc A review of the security chapter provided by my colleague Maarten Los. In addition I tried to submit a few additional comments on chapters 4, 6 and 8, but I got a pending state (need validation) message for the second document: ATOS_ML__FI-WARE High-Level Description - Add review Notes on Chapters 4- 6- and 8 .docx I'm attaching the document as input for tomorrow discussion, just in case... Best regards! Jorge. From: fiware-iot-bounces at lists.fi-ware.eu [mailto:fiware-iot-bounces at lists.fi-ware.eu] On Behalf Of Martin Bauer Sent: martes, 12 de julio de 2011 18:35 To: Farkas, Lorant (NSN - HU/Budapest); fiware-iot at lists.fi-ware.eu Subject: Re: [Fiware-iot] Review of technical chapters Hi all, I provided my review of Chapter 4 - Data and Context Management, adding my comments to the document provided by Lorant and uploading it to the same folder as Lorant. (Is there a way to simply provide a new version - I was not able to quickly figure it out.) As a co-author I was happy to find pieces of the OMA NGSI Context Interface in the P/S Broker part, but I would have liked it even better if it had been referenced. Regarding the specification of the actual enabler (which is something the OMA NGSI does not address as it only specifies an interface) I anyway expressed some concerns in my comment. 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 Farkas, Lorant (NSN - HU/Budapest) Sent: Dienstag, 12. Juli 2011 13:47 To: fiware-iot at lists.fi-ware.eu Subject: [Fiware-iot] Review of technical chapters Dear All, I made a review of the Data and Context Management chapter, please find it attached here. https://forge.fi-ware.eu/docman/view.php/11/251/LF_FI-WARE+High-Level+Description+integrated+draft+0.1+11-07-06.doc Martin, if you have not started to review this yet, you could maybe edit this file directly. I will now start to review the ASE as stated in the minutes. Thanks & Br, Lorant ------------------------------------------------------------------ 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 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 no se hace responsable por su contenido. Su contenido no constituye ningun compromiso para el grupo Atos, 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: -------------- next part -------------- A non-text attachment was scrubbed... Name: ATOS_ML__FI-WARE High-Level Description - Add review Notes on Chapters 4- 6- and 8 .docx Type: application/octet-stream Size: 14926 bytes Desc: ATOS_ML__FI-WARE High-Level Description - Add review Notes on Chapters 4- 6- and 8 .docx URL: From Mario.LOPEZRAMOS at fr.thalesgroup.com Tue Jul 12 22:15:47 2011 From: Mario.LOPEZRAMOS at fr.thalesgroup.com (Mario.LOPEZRAMOS at fr.thalesgroup.com) Date: Tue, 12 Jul 2011 22:15:47 +0200 Subject: [Fiware-iot] task 7.1 In-Reply-To: Message-ID: <13300_1310501749_4E1CAB75_13300_9037_1_37594163625A204998BF307D7B5EA0F703FAF6C80C@thsonea01rel01p> Hi everyone, I tend to agree with what Gian Piero stated about I2ND chapter. I only have general remarks, so I will add them here : In general, the terminology used in this chapter is very telco-oriented, and "device" means rather "connected hardware terminal with a user interface" for them (i.e. smartphones, tablets, PCs, TVs...). The contents does not describe how IoT resources such as unattended sensors and actuators should interface to the network. The only mention to IoT is in the description of the "Device services" which may include "Short Range Radio" technologies to ease the interaction with IoT. The following bullet points are my understanding of how IoT could fit in. Option A : IoT resource = I2ND device * We can assume that IoT devices are "devices" in the I2ND sense with less capabilities (i.e. no display, no personal data services, no media services). * Following the NGN strata model (Figure 64 in page 167), IoT devices would be in one or more "technology-related control space" (IEEE 802.15.4, Wavenis...) under the control of an operator. * The IoT gateways would have to implement the "Connected Device Interfacing" on behalf of the resource-constrained IoT nodes. * Depending on the business model, the 2 types of technology-independent mandatory interfaces to devices they could also make sense for IoT : * CDIL-NET : Interface to network services owned by network operators * CDIL-APP - Interface to applications created by application developers : if we assume that applications can be deployed to IoT devices (e.g. a request to publish temperature for next 24h can be considered running an application) Option B : IoT gateway = I2ND device, IoT resource = subsystem of a I2ND device * If we assume that an application is delivered by a network of IoT nodes as a whole, we can * However, we would not benefit of the standard interfaces which would make sense for individual IoT nodes, such as checking network status, battery, remote management, etc. Unfortunately, I won't be able to attend tomorrow's telco. Thursday is bank holiday in France, and many of us are taking a few days off. Best regards, -- Mario LOPEZ-RAMOS Thales Communications & Security e-mail: mario.lopezramos at fr.thalesgroup.com Tel: +33 (0)1 46 13 32 10 Fax: +33 (0)1 46 13 26 86 Add: 160 bd de Valmy - BP 82 - 92704 Colombes Cedex - France > -----Message d'origine----- > De : fiware-iot-bounces at lists.fi-ware.eu > [mailto:fiware-iot-bounces at lists.fi-ware.eu] De la part de > Fici Gian Piero > Envoy? : mardi 12 juillet 2011 11:42 > ? : Farkas, Lorant (NSN - HU/Budapest); fiware-iot at lists.fi-ware.eu > Cc : Nemeth, Lorant (NSN - HU/Budapest) > Objet : [Fiware-iot] R: task 7.1 > > Hi Lorant and everybody, > > I had a look at the description of the task 7 (Interface to > Networks and Devices - I2ND) and in particular at the work > package 1 (Connected Devices Interfacing - CDI). > You can find the file attached, since I do not know if all of > you can access their document (I had it from Pier Garino that > is the task leader). > > In the task 7 they defined 4 GEs: > (1) Connected Device Interfacing (CDI), i.e. Interfaces to > end devices (addressed by connected device), > (2) Cloud Edge (CE), i.e. interfaces to gateways (cloud proxy), > (3) Network Information & Control (NetIC), i.e. interfaces to > connectivity functions inside the network (open networking), > (4) Service, Capability, Connectivity and Control (S3C), i.e. > interfaces to services offered by the network operators > (network services). > > All of these GEs have relations with our platform (in > particular CDI and CE) and the I2ND descriptions are very > complete and ambitious, but there is no explicit link to our > platform. It looks like the applications/services use > directly those interfaces, or better they do not mind if > there is something in between. > > Maybe I was not able to understand correctly their > descriptions, but I see that we put in our figures a > relationship with the other tasks (not only Interface to the > Networks, but also Data & Context Management Services; > Security, Privacy, Trust; Applications & Services Ecosystem > and Delivery Framework) but I2ND did not put any > relationships with us. > > I think it is worth to try to understand together with them > how they see the overall picture of the FI-WARE architecture. > I already contacted directly my colleague Pier Garino for a > brief exchange of ideas but unfortunately (well, not really > :-) I will be away for the rest of the week on vacation and I > will be back on July 19th, so any further information will be > delayed to next week. (I will not participate to the weekly > call conference tomorrow, sorry). > > I hope these short notes are clear enough. :-) > > Bye, > Gian Piero > > > -----Messaggio originale----- > Da: fiware-iot-bounces at lists.fi-ware.eu > [mailto:fiware-iot-bounces at lists.fi-ware.eu] Per conto di > Farkas, Lorant (NSN - HU/Budapest) > Inviato: luned? 4 luglio 2011 13:26 > A: Farkas, Lorant (NSN - HU/Budapest); fiware-iot at lists.fi-ware.eu > Cc: Nemeth, Lorant (NSN - HU/Budapest) > Oggetto: [Fiware-iot] task 7.1 > > Dear Sabrina and Gian Piero, > > Could you please check potential overlaps of IoT > communications with task 7.1 from the Interface to the > Networks and express an opinion about it? > > Thanks & br, > > Lorant > _______________________________________________ > Fiware-iot mailing list > Fiware-iot at lists.fi-ware.eu > http://lists.fi-ware.eu/listinfo/fiware-iot > > 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. > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From stephan.haller at sap.com Wed Jul 13 09:56:09 2011 From: stephan.haller at sap.com (Haller, Stephan) Date: Wed, 13 Jul 2011 09:56:09 +0200 Subject: [Fiware-iot] task 7.1 In-Reply-To: <13300_1310501749_4E1CAB75_13300_9037_1_37594163625A204998BF307D7B5EA0F703FAF6C80C@thsonea01rel01p> References: <13300_1310501749_4E1CAB75_13300_9037_1_37594163625A204998BF307D7B5EA0F703FAF6C80C@thsonea01rel01p> Message-ID: <0D2446AEB6CAED48BB046223733964A54C268922E6@DEWDFECCR01.wdf.sap.corp> All, As we have defined IoT Resource as a computational element (e.g., software), an IoT resource is definitely NOT equal to a I2ND device. In my opinion, the I2ND Device = IoT Device. Regards, -Stephan From: fiware-iot-bounces at lists.fi-ware.eu [mailto:fiware-iot-bounces at lists.fi-ware.eu] On Behalf Of Mario.LOPEZRAMOS at fr.thalesgroup.com Sent: Dienstag, 12. Juli 2011 22:16 To: fiware-iot at lists.fi-ware.eu Subject: Re: [Fiware-iot] task 7.1 Hi everyone, I tend to agree with what Gian Piero stated about I2ND chapter. I only have general remarks, so I will add them here : In general, the terminology used in this chapter is very telco-oriented, and "device" means rather "connected hardware terminal with a user interface" for them (i.e. smartphones, tablets, PCs, TVs...). The contents does not describe how IoT resources such as unattended sensors and actuators should interface to the network. The only mention to IoT is in the description of the "Device services" which may include "Short Range Radio" technologies to ease the interaction with IoT. The following bullet points are my understanding of how IoT could fit in. Option A : IoT resource = I2ND device * We can assume that IoT devices are "devices" in the I2ND sense with less capabilities (i.e. no display, no personal data services, no media services). * Following the NGN strata model (Figure 64 in page 167), IoT devices would be in one or more "technology-related control space" (IEEE 802.15.4, Wavenis...) under the control of an operator. * The IoT gateways would have to implement the "Connected Device Interfacing" on behalf of the resource-constrained IoT nodes. * Depending on the business model, the 2 types of technology-independent mandatory interfaces to devices they could also make sense for IoT : * CDIL-NET : Interface to network services owned by network operators * CDIL-APP - Interface to applications created by application developers : if we assume that applications can be deployed to IoT devices (e.g. a request to publish temperature for next 24h can be considered running an application) Option B : IoT gateway = I2ND device, IoT resource = subsystem of a I2ND device * If we assume that an application is delivered by a network of IoT nodes as a whole, we can * However, we would not benefit of the standard interfaces which would make sense for individual IoT nodes, such as checking network status, battery, remote management, etc. Unfortunately, I won't be able to attend tomorrow's telco. Thursday is bank holiday in France, and many of us are taking a few days off. Best regards, -- Mario LOPEZ-RAMOS Thales Communications & Security e-mail: mario.lopezramos at fr.thalesgroup.com Tel: +33 (0)1 46 13 32 10 Fax: +33 (0)1 46 13 26 86 Add: 160 bd de Valmy - BP 82 - 92704 Colombes Cedex - France > -----Message d'origine----- > De : fiware-iot-bounces at lists.fi-ware.eu > [mailto:fiware-iot-bounces at lists.fi-ware.eu] De la part de > Fici Gian Piero > Envoy? : mardi 12 juillet 2011 11:42 > ? : Farkas, Lorant (NSN - HU/Budapest); fiware-iot at lists.fi-ware.eu > Cc : Nemeth, Lorant (NSN - HU/Budapest) > Objet : [Fiware-iot] R: task 7.1 > > Hi Lorant and everybody, > > I had a look at the description of the task 7 (Interface to > Networks and Devices - I2ND) and in particular at the work > package 1 (Connected Devices Interfacing - CDI). > You can find the file attached, since I do not know if all of > you can access their document (I had it from Pier Garino that > is the task leader). > > In the task 7 they defined 4 GEs: > (1) Connected Device Interfacing (CDI), i.e. Interfaces to > end devices (addressed by connected device), > (2) Cloud Edge (CE), i.e. interfaces to gateways (cloud proxy), > (3) Network Information & Control (NetIC), i.e. interfaces to > connectivity functions inside the network (open networking), > (4) Service, Capability, Connectivity and Control (S3C), i.e. > interfaces to services offered by the network operators > (network services). > > All of these GEs have relations with our platform (in > particular CDI and CE) and the I2ND descriptions are very > complete and ambitious, but there is no explicit link to our > platform. It looks like the applications/services use > directly those interfaces, or better they do not mind if > there is something in between. > > Maybe I was not able to understand correctly their > descriptions, but I see that we put in our figures a > relationship with the other tasks (not only Interface to the > Networks, but also Data & Context Management Services; > Security, Privacy, Trust; Applications & Services Ecosystem > and Delivery Framework) but I2ND did not put any > relationships with us. > > I think it is worth to try to understand together with them > how they see the overall picture of the FI-WARE architecture. > I already contacted directly my colleague Pier Garino for a > brief exchange of ideas but unfortunately (well, not really > :-) I will be away for the rest of the week on vacation and I > will be back on July 19th, so any further information will be > delayed to next week. (I will not participate to the weekly > call conference tomorrow, sorry). > > I hope these short notes are clear enough. :-) > > Bye, > Gian Piero > > > -----Messaggio originale----- > Da: fiware-iot-bounces at lists.fi-ware.eu > [mailto:fiware-iot-bounces at lists.fi-ware.eu] Per conto di > Farkas, Lorant (NSN - HU/Budapest) > Inviato: luned? 4 luglio 2011 13:26 > A: Farkas, Lorant (NSN - HU/Budapest); fiware-iot at lists.fi-ware.eu > Cc: Nemeth, Lorant (NSN - HU/Budapest) > Oggetto: [Fiware-iot] task 7.1 > > Dear Sabrina and Gian Piero, > > Could you please check potential overlaps of IoT > communications with task 7.1 from the Interface to the > Networks and express an opinion about it? > > Thanks & br, > > Lorant > _______________________________________________ > Fiware-iot mailing list > Fiware-iot at lists.fi-ware.eu > http://lists.fi-ware.eu/listinfo/fiware-iot > > 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. > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From P.Barnaghi at surrey.ac.uk Wed Jul 13 10:13:45 2011 From: P.Barnaghi at surrey.ac.uk (P.Barnaghi at surrey.ac.uk) Date: Wed, 13 Jul 2011 09:13:45 +0100 Subject: [Fiware-iot] Review of technical chapters In-Reply-To: <93D28BDF64839C468B848D14227151A201FF99AE@FIESEXC014.nsn-intra.net> References: <93D28BDF64839C468B848D14227151A201FF99AE@FIESEXC014.nsn-intra.net> Message-ID: Dear all, W3C Semantic Sensor Network report is available at: http://www.w3.org/2005/Incubator/ssn/XGR-ssn-20110628/ Best wishes, Payam ________________________________ 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: 12 July 2011 12:47 To: fiware-iot at lists.fi-ware.eu Subject: [Fiware-iot] Review of technical chapters Dear All, I made a review of the Data and Context Management chapter, please find it attached here. https://forge.fi-ware.eu/docman/view.php/11/251/LF_FI-WARE+High-Level+Description+integrated+draft+0.1+11-07-06.doc Martin, if you have not started to review this yet, you could maybe edit this file directly. I will now start to review the ASE as stated in the minutes. Thanks & Br, Lorant -------------- next part -------------- An HTML attachment was scrubbed... URL: From lorant.farkas at nsn.com Wed Jul 13 13:24:37 2011 From: lorant.farkas at nsn.com (Farkas, Lorant (NSN - HU/Budapest)) Date: Wed, 13 Jul 2011 14:24:37 +0300 Subject: [Fiware-iot] [FI-WARE IoT] weekly meeting inutes, 17 July 2011 Message-ID: <93D28BDF64839C468B848D14227151A201FF9EC3@FIESEXC014.nsn-intra.net> Dear All, Please find under the following link the meeting minutes of our weekly telco. https://forge.fi-ware.eu/docman/view.php/11/263/IoT-Minutes-Telco-071320 11.doc Thanks & Br, Lorant -------------- next part -------------- An HTML attachment was scrubbed... URL: From lorant.farkas at nsn.com Wed Jul 13 16:13:27 2011 From: lorant.farkas at nsn.com (Farkas, Lorant (NSN - HU/Budapest)) Date: Wed, 13 Jul 2011 17:13:27 +0300 Subject: [Fiware-iot] IoT commented by Data and Context Management Message-ID: <93D28BDF64839C468B848D14227151A201FF9FFF@FIESEXC014.nsn-intra.net> Dear All, In the meantime between our weekly meeting and now we received a version commented by the data and context management team. I stored here: https://forge.fi-ware.eu/docman/view.php/11/270/v024_IOTSE_reviewed_by_D CM.doc And rather than concentrating on a merged document with all our comments for the different chapters, I modified our own contribution according to the received comments where I saw it appropriate and I also answered to the comments. This document is attached here: https://forge.fi-ware.eu/docman/view.php/11/271/v025_IOTSE_reviewed_by_N SN_based_on_DCM_comments.doc I would really appreciate if some of you could take a second look before tomorrow morning 10 AM when I have the synchronization meeting with Juanjo. Thanks & Br, Lorant -------------- next part -------------- An HTML attachment was scrubbed... URL: From stephan.haller at sap.com Wed Jul 13 17:10:01 2011 From: stephan.haller at sap.com (Haller, Stephan) Date: Wed, 13 Jul 2011 17:10:01 +0200 Subject: [Fiware-iot] [FI-WARE IoT] weekly meeting inutes, 17 July 2011 In-Reply-To: <93D28BDF64839C468B848D14227151A201FF9EC3@FIESEXC014.nsn-intra.net> References: <93D28BDF64839C468B848D14227151A201FF9EC3@FIESEXC014.nsn-intra.net> Message-ID: <0D2446AEB6CAED48BB046223733964A54C26892E60@DEWDFECCR01.wdf.sap.corp> All, I did a (quick) review, please see comments in https://forge.fi-ware.eu/docman/view.php/11/272/LF_FI-WARE%2BHigh-Level%2BDescription%2Bintegrated%2Bdraft%2B0.1%2B11-07-06-SH.docx. Generally I agree with the comments from Lorant in that document. The main issues I have are: * The description style of the IoT GEs and the other GE's is quite different. The other chapters have details on every GE (and the GEs are visible from the ToC!), while in the IoT Enablement section the GEs are grouped. * There is some overlap between Data/Context Management and the IoT Data Handling * As mentioned before, there is a terminology overlap between (IoT) Device and I2ND Device. While I2ND Devices seem to be pirmarily mobile phones, the boundary is fuzz * 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: Mittwoch, 13. Juli 2011 13:25 To: fiware-iot at lists.fi-ware.eu Subject: [Fiware-iot] [FI-WARE IoT] weekly meeting inutes, 17 July 2011 Dear All, Please find under the following link the meeting minutes of our weekly telco. https://forge.fi-ware.eu/docman/view.php/11/263/IoT-Minutes-Telco-07132011.doc Thanks & Br, Lorant -------------- next part -------------- An HTML attachment was scrubbed... URL: From stephan.haller at sap.com Wed Jul 13 17:32:05 2011 From: stephan.haller at sap.com (Haller, Stephan) Date: Wed, 13 Jul 2011 17:32:05 +0200 Subject: [Fiware-iot] IoT commented by Data and Context Management In-Reply-To: <93D28BDF64839C468B848D14227151A201FF9FFF@FIESEXC014.nsn-intra.net> References: <93D28BDF64839C468B848D14227151A201FF9FFF@FIESEXC014.nsn-intra.net> Message-ID: <0D2446AEB6CAED48BB046223733964A54C26892ED9@DEWDFECCR01.wdf.sap.corp> Hi Lorant, I basically agree with your corrections. Regarding the issue of defining gateway, thing, backend etc., it would be really helpful to have some figure at the beginning (as you suggested in one of the answers), even though the formal definitions come at the end. Some details (page numbers refer to the "Word" page, not the page number displayed): * Page 15 (2.2.1.2): o "[...] leverage on reader device-specific device abstraction drivers." Replace with "[...] leverage device abstraction drivers to connect to specific reader devices using proprietary protocols". I think that is clearer o "[...]the platforms existing today are not able to provide these kinds of solutions." Missing 's' in "kinds". 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: Mittwoch, 13. Juli 2011 16:13 To: fiware-iot at lists.fi-ware.eu Subject: [Fiware-iot] IoT commented by Data and Context Management Dear All, In the meantime between our weekly meeting and now we received a version commented by the data and context management team. I stored here: https://forge.fi-ware.eu/docman/view.php/11/270/v024_IOTSE_reviewed_by_DCM.doc And rather than concentrating on a merged document with all our comments for the different chapters, I modified our own contribution according to the received comments where I saw it appropriate and I also answered to the comments. This document is attached here: https://forge.fi-ware.eu/docman/view.php/11/271/v025_IOTSE_reviewed_by_NSN_based_on_DCM_comments.doc I would really appreciate if some of you could take a second look before tomorrow morning 10 AM when I have the synchronization meeting with Juanjo. Thanks & Br, Lorant ________________________________ -------------- next part -------------- An HTML attachment was scrubbed... URL: From lorant.farkas at nsn.com Thu Jul 14 08:20:53 2011 From: lorant.farkas at nsn.com (Farkas, Lorant (NSN - HU/Budapest)) Date: Thu, 14 Jul 2011 09:20:53 +0300 Subject: [Fiware-iot] [FI-WARE IoT] weekly meeting inutes, 17 July 2011 Message-ID: <93D28BDF64839C468B848D14227151A201FFA0CA@FIESEXC014.nsn-intra.net> Dear Juanjo, I tried to create a merged version where all comments wrt section 4 from NEC, SAP, Orange and NSN colleagues in the IoT WP are included, maybe this way it is more convenient for you to review. See it under this link and sorry for the delay. https://forge.fi-ware.eu/docman/view.php/11/273/Section4_FI-WARE+High-Le vel+Description+integrated+draft+0.1+11-07-06.doc Br, Lorant ________________________________ From: Farkas, Lorant (NSN - HU/Budapest) Sent: Thursday, July 14, 2011 7:44 AM To: 'ext Juanjo Hierro' Subject: FW: [FI-WARE IoT] weekly meeting inutes, 17 July 2011 FYI, other set of comments from the colleague from SAP in IoT with respect to Data and Context Management. Br, Lorant ________________________________ From: ext Haller, Stephan [mailto:stephan.haller at sap.com] Sent: Wednesday, July 13, 2011 5:10 PM To: Farkas, Lorant (NSN - HU/Budapest); fiware-iot at lists.fi-ware.eu Subject: RE: [FI-WARE IoT] weekly meeting inutes, 17 July 2011 All, I did a (quick) review, please see comments in https://forge.fi-ware.eu/docman/view.php/11/272/LF_FI-WARE%2BHigh-Level% 2BDescription%2Bintegrated%2Bdraft%2B0.1%2B11-07-06-SH.docx. Generally I agree with the comments from Lorant in that document. The main issues I have are: * The description style of the IoT GEs and the other GE's is quite different. The other chapters have details on every GE (and the GEs are visible from the ToC!), while in the IoT Enablement section the GEs are grouped. * There is some overlap between Data/Context Management and the IoT Data Handling * As mentioned before, there is a terminology overlap between (IoT) Device and I2ND Device. While I2ND Devices seem to be pirmarily mobile phones, the boundary is fuzz * 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: Mittwoch, 13. Juli 2011 13:25 To: fiware-iot at lists.fi-ware.eu Subject: [Fiware-iot] [FI-WARE IoT] weekly meeting inutes, 17 July 2011 Dear All, Please find under the following link the meeting minutes of our weekly telco. https://forge.fi-ware.eu/docman/view.php/11/263/IoT-Minutes-Telco-071320 11.doc Thanks & Br, Lorant -------------- next part -------------- An HTML attachment was scrubbed... URL: From lorant.farkas at nsn.com Thu Jul 14 13:43:45 2011 From: lorant.farkas at nsn.com (Farkas, Lorant (NSN - HU/Budapest)) Date: Thu, 14 Jul 2011 14:43:45 +0300 Subject: [Fiware-iot] Review commented by DCM Message-ID: <93D28BDF64839C468B848D14227151A202034F59@FIESEXC014.nsn-intra.net> Hi Martin, The data and context management group reviewed the comments from our merged list, could you please take a look whether they are acceptable from your perspective? https://forge.fi-ware.eu/docman/view.php/11/275/DCM_revised_NSN_NEC_comm ents_FI-WARE+High-Level+Description+-+Data-Context+chapter+-+v1.0.doc Thanks & Br, Lorant -------------- next part -------------- An HTML attachment was scrubbed... URL: From lorant.farkas at nsn.com Fri Jul 15 12:18:02 2011 From: lorant.farkas at nsn.com (Farkas, Lorant (NSN - HU/Budapest)) Date: Fri, 15 Jul 2011 13:18:02 +0300 Subject: [Fiware-iot] IoT commented by Data and Context Management, reviewed and cleaned Message-ID: <93D28BDF64839C468B848D14227151A202035254@FIESEXC014.nsn-intra.net> Dear All, Please find under this link the latest version 0.26 which takes into account and hopefully solves all the comments from the Data and Contex Management team. https://forge.fi-ware.eu/docman/view.php/11/277/v026_IOTSE.doc Thanks & Br, Lorant -------------- next part -------------- An HTML attachment was scrubbed... URL: From Martin.Bauer at neclab.eu Fri Jul 15 13:45:59 2011 From: Martin.Bauer at neclab.eu (Martin Bauer) Date: Fri, 15 Jul 2011 11:45:59 +0000 Subject: [Fiware-iot] Review commented by DCM In-Reply-To: <93D28BDF64839C468B848D14227151A202034F59@FIESEXC014.nsn-intra.net> References: <93D28BDF64839C468B848D14227151A202034F59@FIESEXC014.nsn-intra.net> Message-ID: Dear Lorant and Juanjo, I had a look at the answers to my comments and in some cases provided a final comment from my side. Below you find a few points that I consider important, not just for the deliverable, but in general: - Discussion about the "type" in the context element attribute: My main point simply was that if type is just a data type, the semantic type is not explicitly represented in the structure, e.g., if you have an attribute called indoor temperature, which is of type float, you have no way of directly saying that the result is a "temperature". Of course, you may have this information somewhere else, i.e., a model that says that the attribute with the name "indoor temperature" (of an entity of type "room") is a temperature. - Regarding subscriptions to IoT resources: Looking at the Publish/Subscribe Enabler Interface picture, Juanjo suggested that the CB might be integrated in an IoT-oriented GE running on the same device as the IoT Resource. My comment: This depends very much on what assumptions you make for the CB (which stands for Context Broker, right?). Yes, you could do it - if that is the best way depends on further assumptions. For example, the device may be resource-constraint so putting CB functionality there may not be the best idea. Also, this picture says nothing about distribution, i.e., how many CB instances would you have, do they interact with each other, i.e., as a CC do I have to find one CB and get the information I require or do I first have to find hundreds of CBs and chose the ones I need? I think there are a lot of open points here, which require further discussions. 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 Farkas, Lorant (NSN - HU/Budapest) Sent: Donnerstag, 14. Juli 2011 13:44 To: fiware-iot at lists.fi-ware.eu Subject: [Fiware-iot] Review commented by DCM Hi Martin, The data and context management group reviewed the comments from our merged list, could you please take a look whether they are acceptable from your perspective? https://forge.fi-ware.eu/docman/view.php/11/275/DCM_revised_NSN_NEC_comments_FI-WARE+High-Level+Description+-+Data-Context+chapter+-+v1.0.doc Thanks & Br, Lorant -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: DCM_revised_NSN_NEC_comments_FI-WARE High-Level Description - Data-Context chapter - v1.0-1.doc Type: application/msword Size: 3804672 bytes Desc: DCM_revised_NSN_NEC_comments_FI-WARE High-Level Description - Data-Context chapter - v1.0-1.doc URL: From Martin.Bauer at neclab.eu Fri Jul 15 15:23:02 2011 From: Martin.Bauer at neclab.eu (Martin Bauer) Date: Fri, 15 Jul 2011 13:23:02 +0000 Subject: [Fiware-iot] [FI-WARE IoT] weekly meeting inutes, 17 July 2011 In-Reply-To: <93D28BDF64839C468B848D14227151A201FF9EC3@FIESEXC014.nsn-intra.net> References: <93D28BDF64839C468B848D14227151A201FF9EC3@FIESEXC014.nsn-intra.net> Message-ID: Hi Lorant, Correction: Ern? said NEC is NOT involved in OGC. We have limited background on their SWE standards (SensorML, O&M, etc.), but we are not aware that NEC has any connection to them. 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 Farkas, Lorant (NSN - HU/Budapest) Sent: Mittwoch, 13. Juli 2011 13:25 To: fiware-iot at lists.fi-ware.eu Subject: [Fiware-iot] [FI-WARE IoT] weekly meeting inutes, 17 July 2011 Dear All, Please find under the following link the meeting minutes of our weekly telco. https://forge.fi-ware.eu/docman/view.php/11/263/IoT-Minutes-Telco-07132011.doc Thanks & Br, Lorant -------------- next part -------------- An HTML attachment was scrubbed... URL: From lorant.farkas at nsn.com Fri Jul 15 15:39:34 2011 From: lorant.farkas at nsn.com (Farkas, Lorant (NSN - HU/Budapest)) Date: Fri, 15 Jul 2011 16:39:34 +0300 Subject: [Fiware-iot] [FI-WARE IoT] weekly meeting inutes, 17 July 2011 In-Reply-To: References: <93D28BDF64839C468B848D14227151A201FF9EC3@FIESEXC014.nsn-intra.net> Message-ID: <93D28BDF64839C468B848D14227151A20203536F@FIESEXC014.nsn-intra.net> Will correct, thanks! Br, Lorant ________________________________ From: ext Martin Bauer [mailto:Martin.Bauer at neclab.eu] Sent: Friday, July 15, 2011 3:23 PM To: Farkas, Lorant (NSN - HU/Budapest); fiware-iot at lists.fi-ware.eu Subject: RE: [FI-WARE IoT] weekly meeting inutes, 17 July 2011 Hi Lorant, Correction: Ern? said NEC is NOT involved in OGC. We have limited background on their SWE standards (SensorML, O&M, etc.), but we are not aware that NEC has any connection to them. 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 Farkas, Lorant (NSN - HU/Budapest) Sent: Mittwoch, 13. Juli 2011 13:25 To: fiware-iot at lists.fi-ware.eu Subject: [Fiware-iot] [FI-WARE IoT] weekly meeting inutes, 17 July 2011 Dear All, Please find under the following link the meeting minutes of our weekly telco. https://forge.fi-ware.eu/docman/view.php/11/263/IoT-Minutes-Telco-07132011.doc Thanks & Br, Lorant -------------- next part -------------- An HTML attachment was scrubbed... URL: From lorant.farkas at nsn.com Mon Jul 25 10:50:52 2011 From: lorant.farkas at nsn.com (Farkas, Lorant (NSN - HU/Budapest)) Date: Mon, 25 Jul 2011 11:50:52 +0300 Subject: [Fiware-iot] IoT Weekly Telco Message-ID: <93D28BDF64839C468B848D14227151A20209D6D5@FIESEXC014.nsn-intra.net> When: 2011. j?lius 29. 10:00-11:30 (GMT+01:00) Belgrade, Bratislava, Budapest, Ljubljana, Prague. Where: Telco (58465 / 9369002)/ Webex (attached) Note: The GMT offset above does not reflect daylight saving time adjustments. *~*~*~*~*~*~*~*~*~* Dear All, Let's have our weekly telco this week, around the following topics: 1. Report from the discussions on the last two WPA/WPL meetings 2. Status of the HLD deliverable 3. Next work items: -Excel sheet for the asset mapping -Backlog Only this time we would like to organize it on Friday instead of Wednesday. Details for joining attached below. I would also like to remind those of you not having filled the Doodle for the summer vacations about the link where you should do this: http://doodle.com/szs7fc4zctbcegy4 Thanks & Br, Lorant Topic: IoT weekly Date: Friday, 29 July 2011 Time: 10:00, Europe Summer Time (Paris, GMT+02:00) Meeting Number: 704 250 207 Password: cool ------------------------------------------------------- To join the meeting online(Now from mobile devices!) ------------------------------------------------------- 1. Go to https://nsn.webex.com/nsn/j.php?ED=182644752&UID=483150557&PW=NMmEwZDcyMzUy&RT=MTgjMjM%3D 2. If requested, enter your name and email address. 3. If a password is required, enter the meeting password: cool 4. Click "Join". 5. If the meeting includes a teleconference, follow the instructions that appear on your screen. ------------------------------------------------------- To join the audio conference only ------------------------------------------------------- ID: 58465 / PIN (modified!!!): 9369002 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) -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: meeting.ics Type: text/calendar Size: 8934 bytes Desc: not available URL: From lorant.farkas at nsn.com Tue Jul 26 10:28:19 2011 From: lorant.farkas at nsn.com (Farkas, Lorant (NSN - HU/Budapest)) Date: Tue, 26 Jul 2011 11:28:19 +0300 Subject: [Fiware-iot] Agile docs in forge Message-ID: <93D28BDF64839C468B848D14227151A2020ECBD2@FIESEXC014.nsn-intra.net> Dear All, I created a new directory in forge for storing documentation about agile. Please two docs under the following links: -a white paper about information models of agile enterprises https://forge.fi-ware.eu/docman/view.php/11/286/a-lean-and-scalable-requ irements-information-model-for-agile-enterprises.pdf -a presentation about AgileFant, the tool we are going to use, created by request of the architecture board https://forge.fi-ware.eu/docman/view.php/11/287/agilefant.txt (I stored the link in the text file) Br, Lorant -------------- next part -------------- An HTML attachment was scrubbed... URL: From randradas at libresoft.es Thu Jul 28 00:28:39 2011 From: randradas at libresoft.es (Roberto Andradas Izquierdo) Date: Thu, 28 Jul 2011 00:28:39 +0200 Subject: [Fiware-iot] FI-WARE mailing lists are now again operative Message-ID: Dear FI-WARE project members, This mail is to announce you that the FI-WARE mailing lists are now again operative. Nevertheless, we will monitor them tomorrow to make sure there are no incidents with them. Please let us know if you still experience any problem by sending an email to fiware-support at lists.fi-ware.eu Apologize for the inconvenience all this may have caused. Sincerely, The FI-WARE infrastructure support team email: fiware-support at lists.fi-ware.eu From thomas.michael.bohnert at sap.com Thu Jul 28 12:30:21 2011 From: thomas.michael.bohnert at sap.com (Bohnert, Thomas Michael) Date: Thu, 28 Jul 2011 12:30:21 +0200 Subject: [Fiware-iot] Agile docs in forge In-Reply-To: <93D28BDF64839C468B848D14227151A2020ECBD2@FIESEXC014.nsn-intra.net> References: <93D28BDF64839C468B848D14227151A2020ECBD2@FIESEXC014.nsn-intra.net> Message-ID: <771C9B001456D64783596DDC3801C6EA281562705B@DEWDFECCR09.wdf.sap.corp> Hi Lorant, great documents. We should share this kind of documentations with the whole project. Cheers, Thomas 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: Dienstag, 26. Juli 2011 10:28 To: fiware-iot at lists.fi-ware.eu Subject: [Fiware-iot] Agile docs in forge Dear All, I created a new directory in forge for storing documentation about agile. Please two docs under the following links: -a white paper about information models of agile enterprises https://forge.fi-ware.eu/docman/view.php/11/286/a-lean-and-scalable-requirements-information-model-for-agile-enterprises.pdf -a presentation about AgileFant, the tool we are going to use, created by request of the architecture board https://forge.fi-ware.eu/docman/view.php/11/287/agilefant.txt (I stored the link in the text file) Br, Lorant -------------- next part -------------- An HTML attachment was scrubbed... URL: From Martin.Bauer at neclab.eu Fri Jul 29 11:13:01 2011 From: Martin.Bauer at neclab.eu (Martin Bauer) Date: Fri, 29 Jul 2011 09:13:01 +0000 Subject: [Fiware-iot] Meeting Minutes, 29 July 2011 Message-ID: Dear All, You can find the meeting minutes of today's FI-WARE-IoT telephone conference on forge: https://forge.fi-ware.eu/docman/view.php/11/288/IoT-Minutes-Telco-07292011.doc 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 -------------- next part -------------- An HTML attachment was scrubbed... URL: