From Tobias.Jacobs at neclab.eu Mon Apr 2 08:45:23 2012 From: Tobias.Jacobs at neclab.eu (Tobias Jacobs) Date: Mon, 2 Apr 2012 06:45:23 +0000 Subject: [Fiware-iot] IoT Broker Interactions Message-ID: <8755F290097BD941865DC4245B335D2D08BBCCEE@Polydeuces.office.hd> Hi all, I am sending a short slide set explaining the main interactions of the "IoT Broker GE" in the Process Automation subchapter of IoT. Note that this only captures the functionality of the "Request Handler" (see architecture of IoT), which is what NEC is planning to implement in the next weeks. The slides can also be seen as an example of the usage and interplay of NGSI-9 and NGSI-10. Best Tobias -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: IoT-Broker and NGSI interactions.pdf Type: application/pdf Size: 211878 bytes Desc: IoT-Broker and NGSI interactions.pdf URL: From Tobias.Jacobs at neclab.eu Mon Apr 2 12:56:40 2012 From: Tobias.Jacobs at neclab.eu (Tobias Jacobs) Date: Mon, 2 Apr 2012 10:56:40 +0000 Subject: [Fiware-iot] IoT Broker Interactions In-Reply-To: <8755F290097BD941865DC4245B335D2D08BBCCEE@Polydeuces.office.hd> References: <8755F290097BD941865DC4245B335D2D08BBCCEE@Polydeuces.office.hd> Message-ID: <8755F290097BD941865DC4245B335D2D08BBCEC3@Polydeuces.office.hd> Hi all, According to the discussion in this morning's confcall I updated the slide set. Best regards Tobias From: fiware-ngsi-bounces at lists.fi-ware.eu [mailto:fiware-ngsi-bounces at lists.fi-ware.eu] On Behalf Of Tobias Jacobs Sent: Montag, 2. April 2012 08:45 To: fiware-iot at lists.fi-ware.eu; Juanjo Hierro Cc: fiware-ngsi at lists.fi-ware.eu Subject: [Fiware-ngsi] IoT Broker Interactions Hi all, I am sending a short slide set explaining the main interactions of the "IoT Broker GE" in the Process Automation subchapter of IoT. Note that this only captures the functionality of the "Request Handler" (see architecture of IoT), which is what NEC is planning to implement in the next weeks. The slides can also be seen as an example of the usage and interplay of NGSI-9 and NGSI-10. Best Tobias -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: IoT-Broker and NGSI interactions.pdf Type: application/pdf Size: 231276 bytes Desc: IoT-Broker and NGSI interactions.pdf URL: From lorant.farkas at nsn.com Tue Apr 3 09:18:43 2012 From: lorant.farkas at nsn.com (Farkas, Lorant (NSN - HU/Budapest)) Date: Tue, 3 Apr 2012 10:18:43 +0300 Subject: [Fiware-iot] IoT weekly meeting Message-ID: <93D28BDF64839C468B848D14227151A203512826@FIESEXC014.nsn-intra.net> When: 2012. ?prilis 4. 10:00-11:30 (GMT+01:00) Belgrade, Bratislava, Budapest, Ljubljana, Prague. Where: telco/webex Note: The GMT offset above does not reflect daylight saving time adjustments. *~*~*~*~*~*~*~*~*~* Dear All, We propose the following topics for the meeting tomorrow: 1. The NGSI topic: there was a proposal that a technical issue should be raised at the AB level (the unique EntityID topic), we would like to get your opinion on this and more generally on how decisions are made within the IoT team related to the NGSI topic 2. Todos per partner for the 1st release (end of April, end of July), based on the Technical Roadmap (FYI, we received feedback yesterday, it is under work currently under the following link and will be submitted most probably today: http://forge.fi-ware.eu/plugins/mediawiki/wiki/fiware/index.php/Roadmap_of_Internet_of_Things_(IoT)_Services) 3. The Open Specifications M12 deliverable (guidelines: https://forge.fi-ware.eu/plugins/mediawiki/wiki/fi-ware-private/index.php/FiwareDeliverableD2.3-8.1) 4. Testbed WP meetings: which of the partner attends to this, who can give an update Thanks & Br, Lorant Dear All, Let's resume our weekly meeting starting from next week in the usual day/time, which is Wednesday, 10:00 AM (CET) to 11:30. Either WPL or WPA will be present to host the meeting. In case we find good reason to skip the meeting, then we will skip it, but I propose not to deviate from this slot. Thanks & Br, Lorant Topic: IOT WP weekly Date: Every Wednesday, from Wednesday, 10 August 2011 to Wednesday, 26 March 2014 Time: 10:00, Europe Summer Time (Paris, GMT+02:00) Meeting Number: 709 472 921 Meeting Password: FI-WARE ------------------------------------------------------- To join the online meeting ------------------------------------------------------- 1. Go to https://nsn.webex.com/nsn/j.php?ED=175018962&UID=0&PW=NYzEzYWM0ZTNk&RT=MTgjMjM%3D 2. Enter your name and email address. 3. Enter the meeting password: FI-WARE 4. Click "Join Now". 5. Follow the instructions that appear on your screen. 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 New PIN: 9369002 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 https://inside.nokiasiemensnetworks.com/global/MyServices/IT/Infrastructure_Services/RealTimeCommunication/VoiceService/NSNVoiceConference/MakingaCall/LocalAccessNumbers/Pages/Outofofficenumbers.aspx. 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 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: 11170 bytes Desc: not available URL: From lorant.farkas at nsn.com Wed Apr 4 09:52:12 2012 From: lorant.farkas at nsn.com (Farkas, Lorant (NSN - HU/Budapest)) Date: Wed, 4 Apr 2012 10:52:12 +0300 Subject: [Fiware-iot] IoT weekly meeting Message-ID: <93D28BDF64839C468B848D14227151A203512DC1@FIESEXC014.nsn-intra.net> When: 2012. ?prilis 4. 10:00-11:30 (GMT+01:00) Belgrade, Bratislava, Budapest, Ljubljana, Prague. Where: new PIN: 1628 telco/webex Note: The GMT offset above does not reflect daylight saving time adjustments. *~*~*~*~*~*~*~*~*~* Dear All, We propose the following topics for the meeting tomorrow: 1. The NGSI topic: there was a proposal that a technical issue should be raised at the AB level (the unique EntityID topic), we would like to get your opinion on this and more generally on how decisions are made within the IoT team related to the NGSI topic 2. Todos per partner for the 1st release (end of April, end of July), based on the Technical Roadmap (FYI, we received feedback yesterday, it is under work currently under the following link and will be submitted most probably today: http://forge.fi-ware.eu/plugins/mediawiki/wiki/fiware/index.php/Roadmap_of_Internet_of_Things_(IoT)_Services) 3. The Open Specifications M12 deliverable (guidelines: https://forge.fi-ware.eu/plugins/mediawiki/wiki/fi-ware-private/index.php/FiwareDeliverableD2.3-8.1) 4. Testbed WP meetings: which of the partner attends to this, who can give an update Thanks & Br, Lorant Dear All, Let's resume our weekly meeting starting from next week in the usual day/time, which is Wednesday, 10:00 AM (CET) to 11:30. Either WPL or WPA will be present to host the meeting. In case we find good reason to skip the meeting, then we will skip it, but I propose not to deviate from this slot. Thanks & Br, Lorant Topic: IOT WP weekly Date: Every Wednesday, from Wednesday, 10 August 2011 to Wednesday, 26 March 2014 Time: 10:00, Europe Summer Time (Paris, GMT+02:00) Meeting Number: 709 472 921 Meeting Password: FI-WARE ------------------------------------------------------- To join the online meeting ------------------------------------------------------- 1. Go to https://nsn.webex.com/nsn/j.php?ED=175018962&UID=0&PW=NYzEzYWM0ZTNk&RT=MTgjMjM%3D 2. Enter your name and email address. 3. Enter the meeting password: FI-WARE 4. Click "Join Now". 5. Follow the instructions that appear on your screen. 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 New PIN: 1628 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 https://inside.nokiasiemensnetworks.com/global/MyServices/IT/Infrastructure_Services/RealTimeCommunication/VoiceService/NSNVoiceConference/MakingaCall/LocalAccessNumbers/Pages/Outofofficenumbers.aspx. 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 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: 11182 bytes Desc: not available URL: From lorant.farkas at nsn.com Thu Apr 5 11:20:23 2012 From: lorant.farkas at nsn.com (Farkas, Lorant (NSN - HU/Budapest)) Date: Thu, 5 Apr 2012 12:20:23 +0300 Subject: [Fiware-iot] IOT weekly minutes Message-ID: <93D28BDF64839C468B848D14227151A203513387@FIESEXC014.nsn-intra.net> Dear All, The minutes are under the following link, sorry for the delay: https://forge.fi-ware.eu/docman/view.php/11/898/IoT-Minutes-Telco-040420 12.docx Thanks & Br, Lorant -------------- next part -------------- An HTML attachment was scrubbed... URL: From lorant.farkas at nsn.com Tue Apr 10 08:55:31 2012 From: lorant.farkas at nsn.com (Farkas, Lorant (NSN - HU/Budapest)) Date: Tue, 10 Apr 2012 09:55:31 +0300 Subject: [Fiware-iot] IoT weekly meeting Message-ID: <93D28BDF64839C468B848D14227151A20355BA74@FIESEXC014.nsn-intra.net> When: 2012. ?prilis 11. 10:00-11:30 (GMT+01:00) Belgrade, Bratislava, Budapest, Ljubljana, Prague. Where: telco/webex (new PIN: 1628) Note: The GMT offset above does not reflect daylight saving time adjustments. *~*~*~*~*~*~*~*~*~* Dear All, We propose the following topics for the meeting tomorrow: 1. Exploitation plan 2. Status of assets for the end of April release 3. Open specifications (+ other M12) deliverables, next points Thierry will not attend the meeting, Lorant and Denes will host it. Thanks & Br, Lorant Dear All, Let's resume our weekly meeting starting from next week in the usual day/time, which is Wednesday, 10:00 AM (CET) to 11:30. Either WPL or WPA will be present to host the meeting. In case we find good reason to skip the meeting, then we will skip it, but I propose not to deviate from this slot. Thanks & Br, Lorant Topic: IOT WP weekly Date: Every Wednesday, from Wednesday, 10 August 2011 to Wednesday, 26 March 2014 Time: 10:00, Europe Summer Time (Paris, GMT+02:00) Meeting Number: 709 472 921 Meeting Password: FI-WARE ------------------------------------------------------- To join the online meeting ------------------------------------------------------- 1. Go to https://nsn.webex.com/nsn/j.php?ED=175018962&UID=0&PW=NYzEzYWM0ZTNk&RT=MTgjMjM%3D 2. Enter your name and email address. 3. Enter the meeting password: FI-WARE 4. Click "Join Now". 5. Follow the instructions that appear on your screen. 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 New PIN: 1628 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 https://inside.nokiasiemensnetworks.com/global/MyServices/IT/Infrastructure_Services/RealTimeCommunication/VoiceService/NSNVoiceConference/MakingaCall/LocalAccessNumbers/Pages/Outofofficenumbers.aspx. 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 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: 10518 bytes Desc: not available URL: From Tobias.Jacobs at neclab.eu Tue Apr 10 09:05:16 2012 From: Tobias.Jacobs at neclab.eu (Tobias Jacobs) Date: Tue, 10 Apr 2012 07:05:16 +0000 Subject: [Fiware-iot] IoT weekly meeting In-Reply-To: <93D28BDF64839C468B848D14227151A20355BA74@FIESEXC014.nsn-intra.net> References: <93D28BDF64839C468B848D14227151A20355BA74@FIESEXC014.nsn-intra.net> Message-ID: <8755F290097BD941865DC4245B335D2D08BBDA58@Polydeuces.office.hd> Hi Lorant, Can we put "NGSI-10 xml schema" on the agenda (see mail by Salvatore on the ngsi list from last Thursday). I guess this will be a rather short point. Best Tobias 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, 10. April 2012 08:56 To: fiware-iot at lists.fi-ware.eu Subject: [Fiware-iot] IoT weekly meeting When: 2012. ?prilis 11. 10:00-11:30 (GMT+01:00) Belgrade, Bratislava, Budapest, Ljubljana, Prague. Where: telco/webex (new PIN: 1628) Note: The GMT offset above does not reflect daylight saving time adjustments. *~*~*~*~*~*~*~*~*~* Dear All, We propose the following topics for the meeting tomorrow: 1. Exploitation plan 2. Status of assets for the end of April release 3. Open specifications (+ other M12) deliverables, next points Thierry will not attend the meeting, Lorant and Denes will host it. Thanks & Br, Lorant Dear All, Let's resume our weekly meeting starting from next week in the usual day/time, which is Wednesday, 10:00 AM (CET) to 11:30. Either WPL or WPA will be present to host the meeting. In case we find good reason to skip the meeting, then we will skip it, but I propose not to deviate from this slot. Thanks & Br, Lorant Topic: IOT WP weekly Date: Every Wednesday, from Wednesday, 10 August 2011 to Wednesday, 26 March 2014 Time: 10:00, Europe Summer Time (Paris, GMT+02:00) Meeting Number: 709 472 921 Meeting Password: FI-WARE ------------------------------------------------------- To join the online meeting ------------------------------------------------------- 1. Go to https://nsn.webex.com/nsn/j.php?ED=175018962&UID=0&PW=NYzEzYWM0ZTNk&RT=MTgjMjM%3D 2. Enter your name and email address. 3. Enter the meeting password: FI-WARE 4. Click "Join Now". 5. Follow the instructions that appear on your screen. 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 New PIN: 1628 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 https://inside.nokiasiemensnetworks.com/global/MyServices/IT/Infrastructure_Services/RealTimeCommunication/VoiceService/NSNVoiceConference/MakingaCall/LocalAccessNumbers/Pages/Outofofficenumbers.aspx. 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 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: From thierry.nagellen at orange.com Tue Apr 10 14:23:59 2012 From: thierry.nagellen at orange.com (thierry.nagellen at orange.com) Date: Tue, 10 Apr 2012 14:23:59 +0200 Subject: [Fiware-iot] REMINDER: IoT Weekly meeting Message-ID: Dear all, I would remind you that our IoT weekly meeting is essential to maintain the team spirit and to achieve our ambitious goals in FI-Ware project. We have lots of deliverables to deliver before the next review including API description and we have to check assets status for what we promised for the end of April, and then next steps, especially July 2012. If you cannot attend the meeting sometimes, please inform us before the meeting. I would also remind you that as Work Package leader I have to validate your involvement in WP5 based on your contribution and should reject some PM if I cannot evaluate that you did the job for which you claim resources. We try to keep this weekly meeting as effective as possible for everybody and to check only main technical points. We manage dedicated technical issues in separate telcos for the required teams. So do not forget to attend the weekly meeting each Wednesday morning. Best regards. Thierry Nagellen Program Manager Future Internet Orange Labs Networks & Carriers 905 rue Albert Einstein 06921 Sophia Antipolis Cedex +33 492 94 52 84 +33 679 85 08 44 New email address: thierry.nagellen at orange.com -------------- next part -------------- An HTML attachment was scrubbed... URL: From P.Barnaghi at surrey.ac.uk Tue Apr 10 15:11:41 2012 From: P.Barnaghi at surrey.ac.uk (P.Barnaghi at surrey.ac.uk) Date: Tue, 10 Apr 2012 14:11:41 +0100 Subject: [Fiware-iot] REMINDER: IoT Weekly meeting Message-ID: <5766F65D-F6B6-43F4-BE8F-E99844260D83@surrey.ac.uk> Dear Thierry, all, University is closed this week for easter break and we won't be able to participate in the call this week. Best, Payam Sent from my HTC ----- Reply message ----- From: "thierry.nagellen at orange.com" To: "fiware-iot at lists.fi-ware.eu" Subject: [Fiware-iot] REMINDER: IoT Weekly meeting Date: Tue, Apr 10, 2012 13:24 Dear all, I would remind you that our IoT weekly meeting is essential to maintain the team spirit and to achieve our ambitious goals in FI-Ware project. We have lots of deliverables to deliver before the next review including API description and we have to check assets status for what we promised for the end of April, and then next steps, especially July 2012. If you cannot attend the meeting sometimes, please inform us before the meeting. I would also remind you that as Work Package leader I have to validate your involvement in WP5 based should reject some PM if I cannot evaluate that you did the job for which you claim resources. We try to keep this weekly meeting as effective as possible for everybody and to check only main technical points. We manage dedicated technical issues in separate telcos for the required teams. So do not forget to attend the weekly meeting each Wednesday morning. Best regards. Thierry Nagellen Orange Labs Networks & Carriers 905 rue Albert Einstein 06921 Sophia Antipolis Cedex +33 492 94 52 84 +33 679 85 08 44 New email address: thierry.nagellen at orange.com -------------- next part -------------- An HTML attachment was scrubbed... URL: From gianpiero.fici at telecomitalia.it Tue Apr 10 18:38:22 2012 From: gianpiero.fici at telecomitalia.it (Fici Gian Piero) Date: Tue, 10 Apr 2012 18:38:22 +0200 Subject: [Fiware-iot] R: REMINDER: IoT Weekly meeting In-Reply-To: References: Message-ID: Hi Thierry, tomorrow I will still be on Easter holiday, and Sabrina too. Unfortunately we will not be able to attend this weekly meeting, sorry. BR Gian Piero Da: fiware-iot-bounces at lists.fi-ware.eu [mailto:fiware-iot-bounces at lists.fi-ware.eu] Per conto di thierry.nagellen at orange.com Inviato: marted? 10 aprile 2012 14:24 A: fiware-iot at lists.fi-ware.eu Oggetto: [Fiware-iot] REMINDER: IoT Weekly meeting Dear all, I would remind you that our IoT weekly meeting is essential to maintain the team spirit and to achieve our ambitious goals in FI-Ware project. We have lots of deliverables to deliver before the next review including API description and we have to check assets status for what we promised for the end of April, and then next steps, especially July 2012. If you cannot attend the meeting sometimes, please inform us before the meeting. I would also remind you that as Work Package leader I have to validate your involvement in WP5 based should reject some PM if I cannot evaluate that you did the job for which you claim resources. We try to keep this weekly meeting as effective as possible for everybody and to check only main technical points. We manage dedicated technical issues in separate telcos for the required teams. So do not forget to attend the weekly meeting each Wednesday morning. Best regards. Thierry Nagellen Orange Labs Networks & Carriers 905 rue Albert Einstein 06921 Sophia Antipolis Cedex +33 492 94 52 84 +33 679 85 08 44 New email address: thierry.nagellen at orange.com Questo messaggio e i suoi allegati sono indirizzati esclusivamente alle persone indicate. La diffusione, copia o qualsiasi altra azione derivante dalla conoscenza di queste informazioni sono rigorosamente vietate. Qualora abbiate ricevuto questo documento per errore siete cortesemente pregati di darne immediata comunicazione al mittente e di provvedere alla sua distruzione, Grazie. This e-mail and any attachments is confidential and may contain privileged information intended for the addressee(s) only. Dissemination, copying, printing or use by anybody else is unauthorised. If you are not the intended recipient, please delete this message and any attachments and advise the sender by return e-mail, Thanks. [cid:00000000000000000000000000000003 at TI.Disclaimer]Rispetta l'ambiente. Non stampare questa mail se non ? necessario. -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: logo Ambiente_foglia2.jpg Type: image/jpeg Size: 677 bytes Desc: logo Ambiente_foglia2.jpg URL: From lorant.farkas at nsn.com Wed Apr 11 15:19:30 2012 From: lorant.farkas at nsn.com (Farkas, Lorant (NSN - HU/Budapest)) Date: Wed, 11 Apr 2012 16:19:30 +0300 Subject: [Fiware-iot] IoT weekly minutes Message-ID: <93D28BDF64839C468B848D14227151A20355C47C@FIESEXC014.nsn-intra.net> Dear All, The minutes are under the following link: https://forge.fi-ware.eu/docman/view.php/11/905/IoT-Minutes-Telco-110420 12.docx Thanks & Br, Lorant -------------- next part -------------- An HTML attachment was scrubbed... URL: From jan.holler at ericsson.com Wed Apr 11 18:32:54 2012 From: jan.holler at ericsson.com (=?iso-8859-1?Q?Jan_H=F6ller?=) Date: Wed, 11 Apr 2012 18:32:54 +0200 Subject: [Fiware-iot] IoT and the IETF CoRE work - reference material In-Reply-To: <93D28BDF64839C468B848D14227151A20355C47C@FIESEXC014.nsn-intra.net> Message-ID: Dear all, As requested, below you find the list of most relevant work in the IETF CoRE WG. CoRE = Constrained RESTful Environments, i.e. how to take REST to tiny IoT devices. IETF CoRE Charter: https://datatracker.ietf.org/wg/core/charter This explains the purpose and scope of the CoRE working group. Core CoAP: https://datatracker.ietf.org/doc/draft-ietf-core-coap/ This is the application level protocol running over UDP that realizes REST in constrained environments ("binary HTTP with simplified transport" for the layman) Core Link: https://datatracker.ietf.org/doc/draft-ietf-core-link-format/ This document defines how to describe hosted resources and their attributes as well as discovery. CoAP Interface: https://datatracker.ietf.org/doc/draft-shelby-core-interfaces/ This document defines well-known REST interface descriptions. Resource Directory: https://datatracker.ietf.org/doc/draft-shelby-core-resource-directory/ This document describes a directory hosting descriptions of resources held on other servers. Cf the Fiware resource management. Core Observation: https://datatracker.ietf.org/doc/draft-ietf-core-observe This is a CoAP extension providing the capability to observe changes in the state of a resource. HTTP-CoAP Proxy: https://datatracker.ietf.org/doc/draft-castellani-core-http-mapping/ This provides a base reference documentation for HTTP-CoAP proxy implementation. I hope this helps. As for the IoT gateway we have implemented, the above specifications is what we are using (and partly contributing to). Jan From stephan.haller at sap.com Thu Apr 12 11:12:50 2012 From: stephan.haller at sap.com (Haller, Stephan) Date: Thu, 12 Apr 2012 11:12:50 +0200 Subject: [Fiware-iot] Next Deliverables Message-ID: <0D2446AEB6CAED48BB046223733964A54CB1960AF3@DEWDFECCR01.wdf.sap.corp> All, Regarding the test client based on JUnit for GE's implementing NGSI 10, it would be good to have access to the implementations of at least one of those - it would help in the testing of our stuff... Can something be made available? We don't need any code, an Internet-accessible URL would be sufficient. Regards, -Stephan Stephan Haller Development Architect - Internet of Things, SAP Research SAP (Schweiz) AG, Althardstrasse 80, CH-8105 Regensdorf, Switzerland T +41 58 871 78 45, F +41 58 871 78 12 mailto:stephan.haller at sap.com Note that the postal address has changed! Please consider the impact on the environment before printing this e-mail. -------------- next part -------------- An HTML attachment was scrubbed... URL: From lorant.farkas at nsn.com Thu Apr 12 17:03:22 2012 From: lorant.farkas at nsn.com (Farkas, Lorant (NSN - HU/Budapest)) Date: Thu, 12 Apr 2012 18:03:22 +0300 Subject: [Fiware-iot] IoT weekly meeting Message-ID: <93D28BDF64839C468B848D14227151A2035A63F3@FIESEXC014.nsn-intra.net> When: 2012. ?prilis 18. 10:00-11:30 (GMT+01:00) Belgrade, Bratislava, Budapest, Ljubljana, Prague. Where: telco/webex (new PIN: 1628) Note: The GMT offset above does not reflect daylight saving time adjustments. *~*~*~*~*~*~*~*~*~* Update on all instances to reflect the change in the PIN code (will changes every 6 months, unfortunately). Dear All, Let's resume our weekly meeting starting from next week in the usual day/time, which is Wednesday, 10:00 AM (CET) to 11:30. Either WPL or WPA will be present to host the meeting. In case we find good reason to skip the meeting, then we will skip it, but I propose not to deviate from this slot. Thanks & Br, Lorant Topic: IOT WP weekly Date: Every Wednesday, from Wednesday, 10 August 2011 to Wednesday, 26 March 2014 Time: 10:00, Europe Summer Time (Paris, GMT+02:00) Meeting Number: 709 472 921 Meeting Password: FI-WARE ------------------------------------------------------- To join the online meeting ------------------------------------------------------- 1. Go to https://nsn.webex.com/nsn/j.php?ED=175018962&UID=0&PW=NYzEzYWM0ZTNk&RT=MTgjMjM%3D 2. Enter your name and email address. 3. Enter the meeting password: FI-WARE 4. Click "Join Now". 5. Follow the instructions that appear on your screen. 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 New PIN: 1628 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 https://inside.nokiasiemensnetworks.com/global/MyServices/IT/Infrastructure_Services/RealTimeCommunication/VoiceService/NSNVoiceConference/MakingaCall/LocalAccessNumbers/Pages/Outofofficenumbers.aspx. 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 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: 10313 bytes Desc: not available URL: From lorant.farkas at nsn.com Thu Apr 12 17:04:40 2012 From: lorant.farkas at nsn.com (Farkas, Lorant (NSN - HU/Budapest)) Date: Thu, 12 Apr 2012 18:04:40 +0300 Subject: [Fiware-iot] IoT weekly meeting Message-ID: <93D28BDF64839C468B848D14227151A2035A63F5@FIESEXC014.nsn-intra.net> When: Occurs every szerda effective 2011. 09. 28. until 2014. 03. 26. from 10:00 to 11:30 GMT +0100 (Standard) / GMT +0200 (Daylight). Where: telco/webex (new PIN: 1628) Note: The GMT offset above does not reflect daylight saving time adjustments. *~*~*~*~*~*~*~*~*~* Update on all instances to reflect the change in the PIN code (will change every 6 months, unfortunately). Dear All, Let's resume our weekly meeting starting from next week in the usual day/time, which is Wednesday, 10:00 AM (CET) to 11:30. Either WPL or WPA will be present to host the meeting. In case we find good reason to skip the meeting, then we will skip it, but I propose not to deviate from this slot. Thanks & Br, Lorant Topic: IOT WP weekly Date: Every Wednesday, from Wednesday, 10 August 2011 to Wednesday, 26 March 2014 Time: 10:00, Europe Summer Time (Paris, GMT+02:00) Meeting Number: 709 472 921 Meeting Password: FI-WARE ------------------------------------------------------- To join the online meeting ------------------------------------------------------- 1. Go to https://nsn.webex.com/nsn/j.php?ED=175018962&UID=0&PW=NYzEzYWM0ZTNk&RT=MTgjMjM%3D 2. Enter your name and email address. 3. Enter the meeting password: FI-WARE 4. Click "Join Now". 5. Follow the instructions that appear on your screen. 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 New PIN: 9369002 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 https://inside.nokiasiemensnetworks.com/global/MyServices/IT/Infrastructure_Services/RealTimeCommunication/VoiceService/NSNVoiceConference/MakingaCall/LocalAccessNumbers/Pages/Outofofficenumbers.aspx. 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 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: 206764 bytes Desc: not available URL: From lorant.farkas at nsn.com Thu Apr 12 17:04:41 2012 From: lorant.farkas at nsn.com (Farkas, Lorant (NSN - HU/Budapest)) Date: Thu, 12 Apr 2012 18:04:41 +0300 Subject: [Fiware-iot] IoT weekly meeting Message-ID: <93D28BDF64839C468B848D14227151A2035A63F6@FIESEXC014.nsn-intra.net> When: 2012. ?prilis 18. 10:00-11:30 (GMT+01:00) Belgrade, Bratislava, Budapest, Ljubljana, Prague. Where: telco/webex (new PIN: 1628) Note: The GMT offset above does not reflect daylight saving time adjustments. *~*~*~*~*~*~*~*~*~* Update on all instances to reflect the change in the PIN code (will changes every 6 months, unfortunately). Dear All, Let's resume our weekly meeting starting from next week in the usual day/time, which is Wednesday, 10:00 AM (CET) to 11:30. Either WPL or WPA will be present to host the meeting. In case we find good reason to skip the meeting, then we will skip it, but I propose not to deviate from this slot. Thanks & Br, Lorant Topic: IOT WP weekly Date: Every Wednesday, from Wednesday, 10 August 2011 to Wednesday, 26 March 2014 Time: 10:00, Europe Summer Time (Paris, GMT+02:00) Meeting Number: 709 472 921 Meeting Password: FI-WARE ------------------------------------------------------- To join the online meeting ------------------------------------------------------- 1. Go to https://nsn.webex.com/nsn/j.php?ED=175018962&UID=0&PW=NYzEzYWM0ZTNk&RT=MTgjMjM%3D 2. Enter your name and email address. 3. Enter the meeting password: FI-WARE 4. Click "Join Now". 5. Follow the instructions that appear on your screen. 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 New PIN: 1628 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 https://inside.nokiasiemensnetworks.com/global/MyServices/IT/Infrastructure_Services/RealTimeCommunication/VoiceService/NSNVoiceConference/MakingaCall/LocalAccessNumbers/Pages/Outofofficenumbers.aspx. 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 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: 10313 bytes Desc: not available URL: From Tobias.Jacobs at neclab.eu Fri Apr 13 17:44:17 2012 From: Tobias.Jacobs at neclab.eu (Tobias Jacobs) Date: Fri, 13 Apr 2012 15:44:17 +0000 Subject: [Fiware-iot] Open API spec for NGSI-10 Message-ID: <8755F290097BD941865DC4245B335D2D08BCB05F@Polydeuces.office.hd> Hi WP5, I have finished a first draft of the open API spec of the IoT Broker, including NGSI-10. It can be accessed on the WP5 private wiki starting at https://forge.fi-ware.eu/plugins/mediawiki/wiki/fi-ware-private/index.php/FIWARE.ArchitectureDescription.IoT.Backend.IoTBroker#Open_API_Specifications Known bugs: - The table looks awful, but the "wikitable" class does not seem to work in this wiki. - The xml in the example looks strange, as the toplevel tags are outside the box I am happy to receive hints about how to solve the above issues, and also general feedback on the style and level of details of the presentation. Have a nice weekend! Tobias -------------- next part -------------- An HTML attachment was scrubbed... URL: From lorant.farkas at nsn.com Tue Apr 17 09:40:50 2012 From: lorant.farkas at nsn.com (Farkas, Lorant (NSN - HU/Budapest)) Date: Tue, 17 Apr 2012 10:40:50 +0300 Subject: [Fiware-iot] IoT weekly meeting Message-ID: <93D28BDF64839C468B848D14227151A2035EA7E0@FIESEXC014.nsn-intra.net> When: 2012. ?prilis 18. 10:00-11:30 (GMT+01:00) Belgrade, Bratislava, Budapest, Ljubljana, Prague. Where: telco/webex (new PIN: 1628) Note: The GMT offset above does not reflect daylight saving time adjustments. *~*~*~*~*~*~*~*~*~* Dear All, We propose the following topics for tomorrow: 1. D11.2 (https://forge.fi-ware.eu/plugins/mediawiki/wiki/exploitation/index.php/Business_description_GE_Internet_of_Things) due in M12 - to agree what each partner should to. Fairly complex issue because initial content by ATOS is desynchronized both with our architecture specifications and technical roadmap. First input from WPL will be available before the meeting 2. Open specification: review the contribution from NEC on the IoT broker, define the next steps 3. Educational sessions (https://docs.google.com/spreadsheet/ccc?key=0AqGGeaQGro3fdC1zSUdlVjJ2WldESHZmZU13bTdjT3c#gid=0 ): -date & time, venues -who could/should attend locally/remotely (if we have acceptable quality internet connection at the venue, NSN could provide telco & webex facility for remote presentations) -agenda, duration of the sessions -what we present content-wise (backend only or gateway as well), who should prepare content 4. Status of NGSI presentation: D?nes would give a short demo on what we have currently on top of Cumulocity 5. Architecture revisited (if there is time left): from both the perspective of Open Specifications and the educational sessions we should revisit the architecture and the description of the GE-s both on the backend and the gateway Thanks & Br, Lorant Update on all instances to reflect the change in the PIN code (will changes every 6 months, unfortunately). Dear All, Let's resume our weekly meeting starting from next week in the usual day/time, which is Wednesday, 10:00 AM (CET) to 11:30. Either WPL or WPA will be present to host the meeting. In case we find good reason to skip the meeting, then we will skip it, but I propose not to deviate from this slot. Thanks & Br, Lorant Topic: IOT WP weekly Date: Every Wednesday, from Wednesday, 10 August 2011 to Wednesday, 26 March 2014 Time: 10:00, Europe Summer Time (Paris, GMT+02:00) Meeting Number: 709 472 921 Meeting Password: FI-WARE ------------------------------------------------------- To join the online meeting ------------------------------------------------------- 1. Go to https://nsn.webex.com/nsn/j.php?ED=175018962&UID=0&PW=NYzEzYWM0ZTNk&RT=MTgjMjM%3D 2. Enter your name and email address. 3. Enter the meeting password: FI-WARE 4. Click "Join Now". 5. Follow the instructions that appear on your screen. 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 New PIN: 1628 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 https://inside.nokiasiemensnetworks.com/global/MyServices/IT/Infrastructure_Services/RealTimeCommunication/VoiceService/NSNVoiceConference/MakingaCall/LocalAccessNumbers/Pages/Outofofficenumbers.aspx. 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 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: 11809 bytes Desc: not available URL: From thierry.nagellen at orange.com Tue Apr 17 10:03:10 2012 From: thierry.nagellen at orange.com (thierry.nagellen at orange.com) Date: Tue, 17 Apr 2012 10:03:10 +0200 Subject: [Fiware-iot] Exploitation deliverable Message-ID: Dear all, I've extracted from the wiki the content regarding IoT chapter and begun a description for France Telecom exploitation plan. I think we have to deeply change the content of our part, first to have the same approach than for the technical description (backend and gateway layers) which should simplify the structure of the doc and second to avoid lots of repetitions regarding the assets. We need also to revise competitors and to decide if we want to provide more details regarding existing offers to better show what we bring to the market. We will discuss all these points tomorrow during the weekly meeting. BR Thierry -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: D11.2 Internet of Things April2012.docx Type: application/octet-stream Size: 38959 bytes Desc: not available URL: From lorant.farkas at nsn.com Wed Apr 18 14:06:27 2012 From: lorant.farkas at nsn.com (Farkas, Lorant (NSN - HU/Budapest)) Date: Wed, 18 Apr 2012 15:06:27 +0300 Subject: [Fiware-iot] FW: High-level description of Ericsson Gateway Message-ID: <93D28BDF64839C468B848D14227151A2035EB13E@FIESEXC014.nsn-intra.net> Dear All, FYI (especially Payam/Tarek). Thanks & Br, Lorant From: ext Jakob Saros [mailto:jakob.saros at ericsson.com] Sent: Friday, April 13, 2012 6:15 PM To: Fici Gian Piero; Guerra Sabrina; thierry.nagellen at orange.com; Farkas, Lorant (NSN - HU/Budapest); Bisztray, Denes (NSN - HU/Budapest) Cc: Jan H?ller Subject: High-level description of Ericsson Gateway Hi, Attached is a description of the Ericsson Gateway for further discussions. Please note that this is a DRAFT! The document includes information of gateway components, i.e. OSGi bundles, and interfaces northbound/southbound. I look forward to hearing your comments. BR/Jakob -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: Description of Ericsson GW for Fiware.pdf Type: application/pdf Size: 162822 bytes Desc: Description of Ericsson GW for Fiware.pdf URL: From lorant.farkas at nsn.com Wed Apr 18 14:19:38 2012 From: lorant.farkas at nsn.com (Farkas, Lorant (NSN - HU/Budapest)) Date: Wed, 18 Apr 2012 15:19:38 +0300 Subject: [Fiware-iot] IoT weekly minutes Message-ID: <93D28BDF64839C468B848D14227151A2035EB160@FIESEXC014.nsn-intra.net> Dear All, The meeting minutes are stored under https://forge.fi-ware.eu/docman/view.php/11/922/IoT-Minutes-Telco-180420 12.docx Thanks & Br, Lroant -------------- next part -------------- An HTML attachment was scrubbed... URL: From lorant.farkas at nsn.com Thu Apr 19 08:27:41 2012 From: lorant.farkas at nsn.com (Farkas, Lorant (NSN - HU/Budapest)) Date: Thu, 19 Apr 2012 09:27:41 +0300 Subject: [Fiware-iot] important action item missing from the minutes Message-ID: <93D28BDF64839C468B848D14227151A2035EB3DE@FIESEXC014.nsn-intra.net> Dear Partners, As discussed, please provide a first version of the description of your exploitation plan by the end of this week, in a textual format, in e-mail. You can use Thierry's exploitation plan from the document he sent on 17.04.2012 at 10:03 CET. This item was mentioned in the minutes, but not in the table with the action items. I apologize for that. Thanks & Br, Lorant -------------- next part -------------- An HTML attachment was scrubbed... URL: From sabrina.guerra at telecomitalia.it Fri Apr 20 12:13:22 2012 From: sabrina.guerra at telecomitalia.it (Guerra Sabrina) Date: Fri, 20 Apr 2012 12:13:22 +0200 Subject: [Fiware-iot] R: important action item missing from the minutes In-Reply-To: <93D28BDF64839C468B848D14227151A2035EB3DE@FIESEXC014.nsn-intra.net> References: <93D28BDF64839C468B848D14227151A2035EB3DE@FIESEXC014.nsn-intra.net> Message-ID: <36A93B31228D3B49B691AD31652BCAE9A598D56A44@GRFMBX702BA020.griffon.local> Dear Thierry and Lorant, we attach our contribution: our first company description of the exploitation plan (you may find it as track changes in the Thierry's original document). Could you have a look to this contribution and give us your feedback? By the way we communicate you that April 25th is an Italian Holiday so we will not be able to attend the next weekly meeting. Best regards, Sabrina and Gian Piero Sabrina Guerra __________________________________ Telecom Italia S.p.a. Strategia e Innovazione, Research & Trends Telefono +39 011 228 8359 Cellulare +39 331 600 1349 ________________________________ 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: Thursday, April 19, 2012 8:28 AM A: fiware-iot at lists.fi-ware.eu Oggetto: [Fiware-iot] important action item missing from the minutes Dear Partners, As discussed, please provide a first version of the description of your exploitation plan by the end of this week, in a textual format, in e-mail. You can use Thierry's exploitation plan from the document he sent on 17.04.2012 at 10:03 CET. This item was mentioned in the minutes, but not in the table with the action items. I apologize for that. Thanks & Br, Lorant Questo messaggio e i suoi allegati sono indirizzati esclusivamente alle persone indicate. La diffusione, copia o qualsiasi altra azione derivante dalla conoscenza di queste informazioni sono rigorosamente vietate. Qualora abbiate ricevuto questo documento per errore siete cortesemente pregati di darne immediata comunicazione al mittente e di provvedere alla sua distruzione, Grazie. This e-mail and any attachments is confidential and may contain privileged information intended for the addressee(s) only. Dissemination, copying, printing or use by anybody else is unauthorised. If you are not the intended recipient, please delete this message and any attachments and advise the sender by return e-mail, Thanks. [cid:00000000000000000000000000000003 at TI.Disclaimer]Rispetta l'ambiente. Non stampare questa mail se non ? necessario. -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: TI_Contribution_D11.2 Internet of Things April2012.docx Type: application/vnd.openxmlformats-officedocument.wordprocessingml.document Size: 38115 bytes Desc: TI_Contribution_D11.2 Internet of Things April2012.docx URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: logo Ambiente_foglia2.jpg Type: image/jpeg Size: 677 bytes Desc: logo Ambiente_foglia2.jpg URL: From Tobias.Jacobs at neclab.eu Fri Apr 20 16:58:41 2012 From: Tobias.Jacobs at neclab.eu (Tobias Jacobs) Date: Fri, 20 Apr 2012 14:58:41 +0000 Subject: [Fiware-iot] API open specs Message-ID: <8755F290097BD941865DC4245B335D2D08BCCEB6@Polydeuces.office.hd> Dear Lorant, dear all, Sorry for raising that issue again, but I want to propose yet another structure of the API specs for the IoT Broker. How about I structure the pages for NGSI-10 (and later NGSI9) more in the style proposed in https://forge.fi-ware.eu/plugins/mediawiki/wiki/fi-ware-private/index.php/Dedicated_API_wiki_page. We still can have a dedicated page for each API of the GE, but this would then only contain the information not already contained in the NGSI-9/10 pages. See https://forge.fi-ware.eu/plugins/mediawiki/wiki/fi-ware-private/index.php/IoT_Broker_Northbound_API for a first example of how this could look like (still incomplete). Otherwise the whole resource structure/table of operations would have to be repeated and maintained multiple times. In general, I think a benefit of using standards is that their description can be centralized somewhere, so why not exploit that benefit. Have a great weekend Tobias -------------- next part -------------- An HTML attachment was scrubbed... URL: From lorant.farkas at nsn.com Sat Apr 21 10:08:47 2012 From: lorant.farkas at nsn.com (Farkas, Lorant (NSN - HU/Budapest)) Date: Sat, 21 Apr 2012 11:08:47 +0300 Subject: [Fiware-iot] API open specs In-Reply-To: <8755F290097BD941865DC4245B335D2D08BCCEB6@Polydeuces.office.hd> References: <8755F290097BD941865DC4245B335D2D08BCCEB6@Polydeuces.office.hd> Message-ID: <93D28BDF64839C468B848D14227151A2036292CE@FIESEXC014.nsn-intra.net> Dear Tobias, This is a good approach. Thanks & Br, Lorant From: ext Tobias Jacobs [mailto:Tobias.Jacobs at neclab.eu] Sent: Friday, April 20, 2012 4:59 PM To: Farkas, Lorant (NSN - HU/Budapest); fiware-iot at lists.fi-ware.eu Cc: thierry.nagellen at orange.com Subject: API open specs Dear Lorant, dear all, Sorry for raising that issue again, but I want to propose yet another structure of the API specs for the IoT Broker. How about I structure the pages for NGSI-10 (and later NGSI9) more in the style proposed in https://forge.fi-ware.eu/plugins/mediawiki/wiki/fi-ware-private/index.ph p/Dedicated_API_wiki_page. We still can have a dedicated page for each API of the GE, but this would then only contain the information not already contained in the NGSI-9/10 pages. See https://forge.fi-ware.eu/plugins/mediawiki/wiki/fi-ware-private/index.ph p/IoT_Broker_Northbound_API for a first example of how this could look like (still incomplete). Otherwise the whole resource structure/table of operations would have to be repeated and maintained multiple times. In general, I think a benefit of using standards is that their description can be centralized somewhere, so why not exploit that benefit. Have a great weekend Tobias -------------- next part -------------- An HTML attachment was scrubbed... URL: From denes.bisztray at nsn.com Mon Apr 23 09:56:04 2012 From: denes.bisztray at nsn.com (Bisztray, Denes (NSN - HU/Budapest)) Date: Mon, 23 Apr 2012 09:56:04 +0200 Subject: [Fiware-iot] IoT Chapter streamlined architecture Message-ID: <3F4C11BC54A36642BFB5875D599F47BD05D18CC0@DEMUEXC013.nsn-intra.net> Dear all, As mentioned in the previouw weekly meeting, the architecture is getting incomprehensible. This is painful for two reasons. 1. We have to give educational sessions to the UC projects. If we ourselves don't completely understand the architecture, we can't give a proper presentation about it. 2. The open specifications are coming closer. We have way too many GEs compared to other projects, and there are way too many interfaces between these GEs. We supposed to give a fully specified description for every single circle on the FMC diagram. As Gian Piero felt right, the architecture does indeed needs rationalisation. The current GEs are just modules and are not functional outside their context. Thus I created a proposal for a more streamlined architecture. I uploaded to the project svn: https://forge.fi-ware.eu/scmrepos/svn/iot/trunk/documents/FMC/IoT-Streamlined.graphml Also attached to this message. A short presentation on the fundamental changes. We need to discuss this on the Wednesday session, thus I sent it ASAP for you to be able to have a detailed look at it. The asset selection does not change, as you will see, they will seem more natural. We have only 5 GE: 1. Core Functionalities 2. Things Management 3. Advanced Communications 4. Security 5. Protocol Adapter Core Functionalities GE As its name suggests this contains the core functionality of the Backend or Gateway. It includes device-level resource management. The implementation of the northbound and southbound device-level interfaces. Core communication functionality with discontinuous connectivity features as well as a plugin architecture that allows developers to further extensions. Important that this is the basic building block of our system, this is a mandatory component. However if we have this component, the system is already functional. On the gateway this is basically "the gateway", i.e. the Ericsson and TI Gateway. On the Backend this WAS the TID asset, however now I have no idea who will do this. Things Management GE This deals with everything Things-level. We have the IoT Broker, Configuration Management, Configuration Repository and Inference Engine within this GE. It uses the information of the Core Functionalities GE to optain information on the resources. Interfaces: only the things-level extension interface that works on the top of the Core's Resource Management. As a vision this interface should be generic enough to use the Things Management GE on the top of other entities that can be uplifted to a things-level functionality. This supposed to be the NEC and University of Surrey asset. Advanced Communications GE This GE gives advanced communications capabilities, that are not part of the Core functionalities. Mobility Management, Session Management, Traffic Flow management, Quality of Service. This works as an "official" plugin for the Core's communication plugin architecture. This has no current asset selected, as there was no asset for this before. Security GE: PEP, and everything security. Since this has one interface, it can use standards for the security interface. Need to be checked with the Security WP. Protocol Adapter Same as before. It translates the various device-level protocols to the official FIWARE IoT device-level protocol, which is ETSI M2M at the moment. I understand the implications of changing the architecture today. But we need something that we can work with as soon as possible, otherwise we will not able to deliver anything at all. Best, D?nes -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: IoT-Streamlined.graphml Type: application/octet-stream Size: 81991 bytes Desc: IoT-Streamlined.graphml URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: IoT-Streamlined.png Type: image/png Size: 48754 bytes Desc: IoT-Streamlined.png URL: From maarten.los at atosresearch.eu Mon Apr 23 13:57:19 2012 From: maarten.los at atosresearch.eu (Maarten Los) Date: Mon, 23 Apr 2012 13:57:19 +0200 Subject: [Fiware-iot] IoT weekly meeting In-Reply-To: <8755F290097BD941865DC4245B335D2D08BBDA58@Polydeuces.office.hd> References: <93D28BDF64839C468B848D14227151A20355BA74@FIESEXC014.nsn-intra.net> <8755F290097BD941865DC4245B335D2D08BBDA58@Polydeuces.office.hd> Message-ID: <461EDDC0FEB25648B2FE8B0145848AA59EB1CE@INTMAIL02.es.int.atosorigin.com> Dear partners, Due to medical leave I will have limited availability until the 2nd week of May (depending on injured thumb recovery speed), but I will try to check my mail on a regular basis. Until then, for all urgent matters, please get in touch with my colleague Jorge Pereira. Best regards, Maarten From: fiware-iot-bounces at lists.fi-ware.eu [mailto:fiware-iot-bounces at lists.fi-ware.eu] On Behalf Of Tobias Jacobs Sent: martes, 10 de abril de 2012 9:05 To: Farkas, Lorant (NSN - HU/Budapest); fiware-iot at lists.fi-ware.eu Subject: Re: [Fiware-iot] IoT weekly meeting Hi Lorant, Can we put "NGSI-10 xml schema" on the agenda (see mail by Salvatore on the ngsi list from last Thursday). I guess this will be a rather short point. Best Tobias 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, 10. April 2012 08:56 To: fiware-iot at lists.fi-ware.eu Subject: [Fiware-iot] IoT weekly meeting When: 2012. ?prilis 11. 10:00-11:30 (GMT+01:00) Belgrade, Bratislava, Budapest, Ljubljana, Prague. Where: telco/webex (new PIN: 1628) Note: The GMT offset above does not reflect daylight saving time adjustments. *~*~*~*~*~*~*~*~*~* Dear All, We propose the following topics for the meeting tomorrow: 1. Exploitation plan 2. Status of assets for the end of April release 3. Open specifications (+ other M12) deliverables, next points Thierry will not attend the meeting, Lorant and Denes will host it. Thanks & Br, Lorant Dear All, Let's resume our weekly meeting starting from next week in the usual day/time, which is Wednesday, 10:00 AM (CET) to 11:30. Either WPL or WPA will be present to host the meeting. In case we find good reason to skip the meeting, then we will skip it, but I propose not to deviate from this slot. Thanks & Br, Lorant Topic: IOT WP weekly Date: Every Wednesday, from Wednesday, 10 August 2011 to Wednesday, 26 March 2014 Time: 10:00, Europe Summer Time (Paris, GMT+02:00) Meeting Number: 709 472 921 Meeting Password: FI-WARE ------------------------------------------------------- To join the online meeting ------------------------------------------------------- 1. Go to https://nsn.webex.com/nsn/j.php?ED=175018962&UID=0&PW=NYzEzYWM0ZTNk&RT=MTgjMjM%3D 2. Enter your name and email address. 3. Enter the meeting password: FI-WARE 4. Click "Join Now". 5. Follow the instructions that appear on your screen. 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 New PIN: 1628 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 https://inside.nokiasiemensnetworks.com/global/MyServices/IT/Infrastructure_Services/RealTimeCommunication/VoiceService/NSNVoiceConference/MakingaCall/LocalAccessNumbers/Pages/Outofofficenumbers.aspx . 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 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) ------------------------------------------------------------------ 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: From lorant.farkas at nsn.com Mon Apr 23 14:44:34 2012 From: lorant.farkas at nsn.com (Farkas, Lorant (NSN - HU/Budapest)) Date: Mon, 23 Apr 2012 15:44:34 +0300 Subject: [Fiware-iot] installation and administration guidelines Message-ID: <93D28BDF64839C468B848D14227151A2036296E6@FIESEXC014.nsn-intra.net> Dear All, These are the installation and administration guidelines, please comment before/during our weekly call. Sorry for the late dissemination... Thanks & Br, Lorant From: fiware-wpa-bounces at lists.fi-ware.eu [mailto:fiware-wpa-bounces at lists.fi-ware.eu] On Behalf Of ext Miguel Carrillo Sent: Monday, April 16, 2012 6:41 PM To: fiware-wpl at lists.fi-ware.eu; fiware-wpa at lists.fi-ware.eu Subject: [Fiware-wpa] TOC for 2 sections of the Installation and Admin Guide Dear all, As agreed on the WPL/WPA confcall, the installation and admin manual does not have a fixed TOC and it will be decided internally in each WP. However, there are two sections that will appear in each installation and admin manual from each chapter. These sections will have the same TOC always. I refer to the sanity check procedures and the diagnosis procedures. The TOCs for these sections can be found on the private Wiki: * Private wiki -> FI-WARE Project Deliverables Placeholders for common edition -> FI-WARE Deliverable "D2.3-8.3 FIWARE Installation and Administration Guide" Please disseminate this within your Work Packages. Best regards, Miguel -- ---------------------------------------------------------------------- _/ _/_/ Miguel Carrillo Pacheco _/ _/ _/ _/ Telef?nica Distrito Telef?nica _/ _/_/_/ _/ _/ Investigaci?n y Edifico Oeste 1, Planta 9 _/ _/ _/ _/ Desarrollo Ronda de la Comunicaci?n S/N _/ _/_/ 28050 Madrid (Spain) Tel: (+34) 91 483 26 77 e-mail: mcp at tid.es Follow FI-WARE on the net Website: http://www.fi-ware.eu Facebook: http://www.facebook.com/pages/FI-WARE/251366491587242 Twitter: http://twitter.com/Fiware LinkedIn: http://www.linkedin.com/groups/FIWARE-4239932 ---------------------------------------------------------------------- ________________________________ Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra pol?tica de env?o y recepci?n de correo electr?nico en el enlace situado m?s abajo. This message is intended exclusively for its addressee. We only send and receive email on the basis of the terms set out at. http://www.tid.es/ES/PAGINAS/disclaimer.aspx -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- An embedded and charset-unspecified text was scrubbed... Name: ATT3743618.txt URL: From lorant.farkas at nsn.com Tue Apr 24 07:59:11 2012 From: lorant.farkas at nsn.com (Farkas, Lorant (NSN - HU/Budapest)) Date: Tue, 24 Apr 2012 08:59:11 +0300 Subject: [Fiware-iot] FW: [Fiware-wpa] Agenda for 'FI-WARE Educational Sessions' (Weeks May 21st & June 4th) Message-ID: <93D28BDF64839C468B848D14227151A2036298C8@FIESEXC014.nsn-intra.net> Dear All, FYI, latest news on the educational sessions. We can have discuss this topic tomorrow. Thanks & Br, Lorant -----Original Message----- From: fiware-wpa-bounces at lists.fi-ware.eu [mailto:fiware-wpa-bounces at lists.fi-ware.eu] On Behalf Of ext CARLOS RALLI UCENDO Sent: Monday, April 23, 2012 5:58 PM To: fiware-wpl at lists.fi-ware.eu; fiware-wpa at lists.fi-ware.eu Subject: [Fiware-wpa] Agenda for 'FI-WARE Educational Sessions' (Weeks May 21st & June 4th) Dear Colleagues, Find hereby enclosed a link to the Agenda of these sessions as discussed in our conference call this morning: https://docs.google.com/spreadsheet/ccc?key=0ArcymbqnpOfkdGJqeEFlblNEUkdxdkl2NW1sM0FWUUE#gid=0 File is attached too, in case you are not able to access this googledoc resources. For its preparation we have considered each chapter requested slots (#days), your preferences regarding the dates as much as possible and the number of attendees as communicated by the use-case projects so far. Please, share this link with your teams (GE owners) and let us know before tomorrow EoB any issue regarding your specific chapter sessions. In the absence of issues, this file will be shared with the use-case projects at the end of the day tomorrow. Ps. I will be subscribing WPl and WPa to the 'fiware-training' list before today EoB. Please, **be aware use-case project members are also members of that list** Thanks for your cooperation. Best regards, -- ------------------------------------------------------------------------------------------------------------------------ Carlos Ralli Ucendo (ralli at tid.es) Cell: +34696923588 Twitter: @carlosralli Product Development & Innovation (Telef?nica Digital) Telef?nica I+D SAU Madrid, Spain ------------------------------------------------------------------------------------------------------------------------ Follow FI-WARE project (Future Internet Services Core Platform): Website: http://www.fi-ware.eu Facebook: http://www.facebook.com/pages/FI-WARE/251366491587242 Twitter: @fiware LinkedIn: http://www.linkedin.com/groups/FIWARE-4239932 ------------------------------------------------------------------------------------------------------------------------ Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra pol?tica de env?o y recepci?n de correo electr?nico en el enlace situado m?s abajo. This message is intended exclusively for its addressee. We only send and receive email on the basis of the terms set out at http://www.tid.es/ES/PAGINAS/disclaimer.aspx -------------- next part -------------- A non-text attachment was scrubbed... Name: FI-WARE_Educational_Sessions.xlsx Type: application/vnd.openxmlformats-officedocument.spreadsheetml.sheet Size: 20788 bytes Desc: FI-WARE_Educational_Sessions.xlsx URL: -------------- next part -------------- An embedded and charset-unspecified text was scrubbed... Name: ATT5340401.txt URL: From lorant.farkas at nsn.com Tue Apr 24 08:31:33 2012 From: lorant.farkas at nsn.com (Farkas, Lorant (NSN - HU/Budapest)) Date: Tue, 24 Apr 2012 09:31:33 +0300 Subject: [Fiware-iot] IoT weekly meeting Message-ID: <93D28BDF64839C468B848D14227151A203629905@FIESEXC014.nsn-intra.net> When: 2012. ?prilis 25. 10:00-11:30 (GMT+01:00) Belgrade, Bratislava, Budapest, Ljubljana, Prague. Where: telco/webex (new PIN: 1628) Note: The GMT offset above does not reflect daylight saving time adjustments. *~*~*~*~*~*~*~*~*~* Dear All, We propose the following topics for tomorrow: 1. Architecture revisited: discuss about the proposal from D?nes 2. NGSI: NSN would give you a short demo on the implementation we have and we could have an update on the status of the specifications 3. Educational sessions: to share with you the latest information and get feedback from you for any issues 4. M12 deliverables (exploitation plan, open specifications): status update Thierry is on vacation this week, NSN will host the meeting. Thanks & Br, Lorant Update on all instances to reflect the change in the PIN code (will change every 6 months, unfortunately). Dear All, Let's resume our weekly meeting starting from next week in the usual day/time, which is Wednesday, 10:00 AM (CET) to 11:30. Either WPL or WPA will be present to host the meeting. In case we find good reason to skip the meeting, then we will skip it, but I propose not to deviate from this slot. Thanks & Br, Lorant Topic: IOT WP weekly Date: Every Wednesday, from Wednesday, 10 August 2011 to Wednesday, 26 March 2014 Time: 10:00, Europe Summer Time (Paris, GMT+02:00) Meeting Number: 709 472 921 Meeting Password: FI-WARE ------------------------------------------------------- To join the online meeting ------------------------------------------------------- 1. Go to https://nsn.webex.com/nsn/j.php?ED=175018962&UID=0&PW=NYzEzYWM0ZTNk&RT=MTgjMjM%3D 2. Enter your name and email address. 3. Enter the meeting password: FI-WARE 4. Click "Join Now". 5. Follow the instructions that appear on your screen. 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 New PIN: 9369002 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 https://inside.nokiasiemensnetworks.com/global/MyServices/IT/Infrastructure_Services/RealTimeCommunication/VoiceService/NSNVoiceConference/MakingaCall/LocalAccessNumbers/Pages/Outofofficenumbers.aspx. 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 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: 10874 bytes Desc: not available URL: From jan.holler at ericsson.com Wed Apr 25 09:10:33 2012 From: jan.holler at ericsson.com (=?Windows-1252?Q?Jan_H=F6ller?=) Date: Wed, 25 Apr 2012 09:10:33 +0200 Subject: [Fiware-iot] IoT Chapter streamlined architecture In-Reply-To: <3F4C11BC54A36642BFB5875D599F47BD05D18CC0@DEMUEXC013.nsn-intra.net> Message-ID: Hello, First of all, I think this is a good and appropriate step forward. Some comments related to the gateway part. 1. It would be good to add devices below the gw and connected to the different circles. Devices are more or less out of the scope, but they should be there. 2. I think there should be a direct line between the Backend and a device ? not all devices will connect via a gw. 3. You have arrows between RD and RM in gw, but no other lines inside the core GE. Either you indicate lines between all boxes, or you remove all lines inside a GE. 4. I do not see why there is a line between Interface and southbound ETSI M2M circle. 5. I propose to move Security GE to the left or right of the core GE and not below. 6. I suggest to add a line between Protocol Adapter and Plugin Architecture that contains a circle (i.e. an "open" API). This API is needed for integration of third party protocol adapters. Perhaps PA should be in plural, i.e. "Protocol AdapterS"? 7. I suggest to add a northbound Protocol Adapter in the gateway outside the Core GE but within the gateway. This PA should have a circled line to the backend perhaps stating ETSI M2M (we have no such assets as we are all painfully aware of unless somebody has some news). This PA should also have a line to the Core GE containing a circle for the same reason as in 6 above. 8. There needs to be a gateway external interface towards DH GE, at least for setting filters etc in CEP. This should be a line with a circle interface. I guess the interface will be proprietary. 9. It can be discussed whether there needs to be an open interface towards Local Storage and whether LS should be in DH GE or in Core GE. Disc Conn in the Core GE has to have means for handling off-line devices which implies various types of storage. This storage is perhaps more of a system internal cache than an appropriate open data base requiring an open interface. 10. What Advanced Connectivity will be in the first release? 11. How do we view Remote Device Management? Via ETSI M2M or via a separate interface? The architectural principle of "Separation of Concerns" would make me argue that it should not be part of ETSI M2M, but a separate interface. Following this, as RDM is not specific to IoT, I would also argue that it is not part of the IoT chapter. It should be part of I2ND, but I haven't checked if that is the case. How come there is not CEP or Storage in the Backend? Jan From: "Bisztray, Denes (NSN - HU/Budapest)" > Date: Mon, 23 Apr 2012 09:56:04 +0200 To: "fiware-iot at lists.fi-ware.eu" > Cc: Jan H?ller >, Jakob Saros >, "thierry.nagellen at orange.com" >, Ernoe Kovacs >, Stephan Haller >, "Farkas, Lorant (NSN - HU/Budapest)" >, "jhierro at tid.es" >, Fici Gian Piero >, Guerra Sabrina > Subject: IoT Chapter streamlined architecture Dear all, As mentioned in the previouw weekly meeting, the architecture is getting incomprehensible. This is painful for two reasons. 1. We have to give educational sessions to the UC projects. If we ourselves don?t completely understand the architecture, we can?t give a proper presentation about it. 2. The open specifications are coming closer. We have way too many GEs compared to other projects, and there are way too many interfaces between these GEs. We supposed to give a fully specified description for every single circle on the FMC diagram. As Gian Piero felt right, the architecture does indeed needs rationalisation. The current GEs are just modules and are not functional outside their context. Thus I created a proposal for a more streamlined architecture. I uploaded to the project svn: https://forge.fi-ware.eu/scmrepos/svn/iot/trunk/documents/FMC/IoT-Streamlined.graphml Also attached to this message. A short presentation on the fundamental changes. We need to discuss this on the Wednesday session, thus I sent it ASAP for you to be able to have a detailed look at it. The asset selection does not change, as you will see, they will seem more natural. We have only 5 GE: 1. Core Functionalities 2. Things Management 3. Advanced Communications 4. Security 5. Protocol Adapter Core Functionalities GE As its name suggests this contains the core functionality of the Backend or Gateway. It includes device-level resource management. The implementation of the northbound and southbound device-level interfaces. Core communication functionality with discontinuous connectivity features as well as a plugin architecture that allows developers to further extensions. Important that this is the basic building block of our system, this is a mandatory component. However if we have this component, the system is already functional. On the gateway this is basically ?the gateway?, i.e. the Ericsson and TI Gateway. On the Backend this WAS the TID asset, however now I have no idea who will do this. Things Management GE This deals with everything Things-level. We have the IoT Broker, Configuration Management, Configuration Repository and Inference Engine within this GE. It uses the information of the Core Functionalities GE to optain information on the resources. Interfaces: only the things-level extension interface that works on the top of the Core?s Resource Management. As a vision this interface should be generic enough to use the Things Management GE on the top of other entities that can be uplifted to a things-level functionality. This supposed to be the NEC and University of Surrey asset. Advanced Communications GE This GE gives advanced communications capabilities, that are not part of the Core functionalities. Mobility Management, Session Management, Traffic Flow management, Quality of Service. This works as an ?official? plugin for the Core?s communication plugin architecture. This has no current asset selected, as there was no asset for this before. Security GE: PEP, and everything security. Since this has one interface, it can use standards for the security interface. Need to be checked with the Security WP. Protocol Adapter Same as before. It translates the various device-level protocols to the official FIWARE IoT device-level protocol, which is ETSI M2M at the moment. I understand the implications of changing the architecture today. But we need something that we can work with as soon as possible, otherwise we will not able to deliver anything at all. Best, D?nes From lorant.farkas at nsn.com Wed Apr 25 09:18:51 2012 From: lorant.farkas at nsn.com (Farkas, Lorant (NSN - HU/Budapest)) Date: Wed, 25 Apr 2012 10:18:51 +0300 Subject: [Fiware-iot] educational session agenda v0.2 Message-ID: <93D28BDF64839C468B848D14227151A203678435@FIESEXC014.nsn-intra.net> Dear All, Please find initial proposal for the agenda of the educational sessions, adjusted to the "central" proposal from the project coordination. We can discuss both in more detail during our meeting. Thanks & Br, Lorant Tue, May 22nd 9:00 - 11:00 -NGSI 9/10 basics: actors, roles, vocabulary (35 minutes + 5 minutes Q&A) -NGSI 9/10 specifications (35 minutes + 5 minutes Q&A) -NGSI binding (35 minutes + 5 minutes Q&A) Coffee break 11:15 - 12:15 -Use case scenarios/examples based on NGSI (35 minutes + 5 minutes Q&A) -Morning session wrap-up (20 minutes) 13:30 - 15:30 -Pub/Sub broker GE (DCM, 35 minutes + 5 minutes Q&A) -IoT broker GE / Things Management GE (IoT, 35 minutes + 5 minutes Q&A) (-Things and Resources Management GE / Backend core functionalities GE) (IoT, 35 minutes + 5 minutes Q&A) Lunch break 15:30 - 17:00 -UC2 Coffee break 17:15 - 18:45 -UC3 Wed, May 23rd 9:00 - 11:00 FI-WARE IoT architecture -Backend, gateway, devices (55 minutes + 5 minutes Q&A) -Southbound, northbound interfaces: focus on ETSI M2M, CoRE (55 minutes + 5 minutes Q&A) Coffee break 11:15 - 12:15 -Backend GE-s: functionalities, interface specs (60 minutes) Lunch break 13:30 - 15:30 -Backend GE-s contd: functionalities, interface specs (20 minutes + 10 minutes Q&A) -Gateway GE-s: functionalities, interface specs (80 minutes + 10 minutes Q&A) 15:30 - 17:00 -UC4 Coffee break 17:15 - 18:45 -UC5 ________________________________________________________________________ __________________ Tue, June 5th 9:00 - 11:00 -NGSI 9/10 basics: actors, roles, vocabulary (35 minutes + 5 minutes Q&A) -NGSI 9/10 specifications (35 minutes + 5 minutes Q&A) -NGSI binding (35 minutes + 5 minutes Q&A) Coffee break 11:15 - 12:15 -Use case scenarios/examples based on NGSI (35 minutes + 5 minutes Q&A) -Morning session wrap-up (20 minutes) 13:30 - 15:30 -Pub/Sub broker GE (DCM, 35 minutes + 5 minutes Q&A) -IoT broker GE / Things Management GE (IoT, 35 minutes + 5 minutes Q&A) (-Things and Resources Management GE / Backend core functionalities GE) (IoT, 35 minutes + 5 minutes Q&A) Lunch break 15:30 - 17:00 -UC2 Coffee break 17:15 - 18:45 -UC3 Wed, June 6th 9:00 - 11:00 FI-WARE IoT architecture -Backend, gateway, devices (55 minutes + 5 minutes Q&A) -Southbound, northbound interfaces: focus on ETSI M2M, CoRE (55 minutes + 5 minutes Q&A) Coffee break 11:15 - 12:15 -Backend GE-s: functionalities, interface specs (60 minutes) Lunch break 13:30 - 15:30 -Backend GE-s contd: functionalities, interface specs (20 minutes + 10 minutes Q&A) -Gateway GE-s: functionalities, interface specs (80 minutes + 10 minutes Q&A) 15:30 - 17:00 -UC4 Coffee break 17:15 - 18:45 -UC5 -------------- next part -------------- An HTML attachment was scrubbed... URL: From jan.holler at ericsson.com Wed Apr 25 09:20:38 2012 From: jan.holler at ericsson.com (=?Windows-1252?Q?Jan_H=F6ller?=) Date: Wed, 25 Apr 2012 09:20:38 +0200 Subject: [Fiware-iot] IoT Chapter streamlined architecture In-Reply-To: <3F4C11BC54A36642BFB5875D599F47BD05D18CC0@DEMUEXC013.nsn-intra.net> Message-ID: Hello, First of all, I think this is a good and appropriate step forward. Some comments related to the gateway part. 1. It would be good to add devices below the gw and connected to the different circles. Devices are more or less out of the scope, but they should be there. 2. I think there should be a direct line between the Backend and a device ? not all devices will connect via a gw. 3. You have arrows between RD and RM in gw, but no other lines inside the core GE. Either you indicate lines between all boxes, or you remove all lines inside a GE. 4. I do not see why there is a line between Interface and southbound ETSI M2M circle. 5. I propose to move Security GE to the left or right of the core GE and not below. 6. I suggest to add a line between Protocol Adapter and Plugin Architecture that contains a circle (i.e. an "open" API). This API is needed for integration of third party protocol adapters. Perhaps PA should be in plural, i.e. "Protocol AdapterS"? 7. I suggest to add a northbound Protocol Adapter in the gateway outside the Core GE but within the gateway. This PA should have a circled line to the backend perhaps stating ETSI M2M (we have no such assets as we are all painfully aware of unless somebody has some news). This PA should also have a line to the Core GE containing a circle for the same reason as in 6 above. 8. There needs to be a gateway external interface towards DH GE, at least for setting filters etc in CEP. This should be a line with a circle interface. I guess the interface will be proprietary. 9. It can be discussed whether there needs to be an open interface towards Local Storage and whether LS should be in DH GE or in Core GE. Disc Conn in the Core GE has to have means for handling off-line devices which implies various types of storage. This storage is perhaps more of a system internal cache than an appropriate open data base requiring an open interface. 10. What Advanced Connectivity will be in the first release? 11. How do we view Remote Device Management? Via ETSI M2M or via a separate interface? The architectural principle of "Separation of Concerns" would make me argue that it should not be part of ETSI M2M, but a separate interface. Following this, as RDM is not specific to IoT, I would also argue that it is not part of the IoT chapter. It should be part of I2ND, but I haven't checked if that is the case. How come there is not CEP or Storage in the Backend? Jan From: "Bisztray, Denes (NSN - HU/Budapest)" > Date: Mon, 23 Apr 2012 09:56:04 +0200 To: "fiware-iot at lists.fi-ware.eu" > Cc: Jan H?ller >, Jakob Saros >, "thierry.nagellen at orange.com" >, Ernoe Kovacs >, Stephan Haller >, "Farkas, Lorant (NSN - HU/Budapest)" >, "jhierro at tid.es" >, Fici Gian Piero >, Guerra Sabrina > Subject: IoT Chapter streamlined architecture Dear all, As mentioned in the previouw weekly meeting, the architecture is getting incomprehensible. This is painful for two reasons. 1. We have to give educational sessions to the UC projects. If we ourselves don?t completely understand the architecture, we can?t give a proper presentation about it. 2. The open specifications are coming closer. We have way too many GEs compared to other projects, and there are way too many interfaces between these GEs. We supposed to give a fully specified description for every single circle on the FMC diagram. As Gian Piero felt right, the architecture does indeed needs rationalisation. The current GEs are just modules and are not functional outside their context. Thus I created a proposal for a more streamlined architecture. I uploaded to the project svn: https://forge.fi-ware.eu/scmrepos/svn/iot/trunk/documents/FMC/IoT-Streamlined.graphml Also attached to this message. A short presentation on the fundamental changes. We need to discuss this on the Wednesday session, thus I sent it ASAP for you to be able to have a detailed look at it. The asset selection does not change, as you will see, they will seem more natural. We have only 5 GE: 1. Core Functionalities 2. Things Management 3. Advanced Communications 4. Security 5. Protocol Adapter Core Functionalities GE As its name suggests this contains the core functionality of the Backend or Gateway. It includes device-level resource management. The implementation of the northbound and southbound device-level interfaces. Core communication functionality with discontinuous connectivity features as well as a plugin architecture that allows developers to further extensions. Important that this is the basic building block of our system, this is a mandatory component. However if we have this component, the system is already functional. On the gateway this is basically ?the gateway?, i.e. the Ericsson and TI Gateway. On the Backend this WAS the TID asset, however now I have no idea who will do this. Things Management GE This deals with everything Things-level. We have the IoT Broker, Configuration Management, Configuration Repository and Inference Engine within this GE. It uses the information of the Core Functionalities GE to optain information on the resources. Interfaces: only the things-level extension interface that works on the top of the Core?s Resource Management. As a vision this interface should be generic enough to use the Things Management GE on the top of other entities that can be uplifted to a things-level functionality. This supposed to be the NEC and University of Surrey asset. Advanced Communications GE This GE gives advanced communications capabilities, that are not part of the Core functionalities. Mobility Management, Session Management, Traffic Flow management, Quality of Service. This works as an ?official? plugin for the Core?s communication plugin architecture. This has no current asset selected, as there was no asset for this before. Security GE: PEP, and everything security. Since this has one interface, it can use standards for the security interface. Need to be checked with the Security WP. Protocol Adapter Same as before. It translates the various device-level protocols to the official FIWARE IoT device-level protocol, which is ETSI M2M at the moment. I understand the implications of changing the architecture today. But we need something that we can work with as soon as possible, otherwise we will not able to deliver anything at all. Best, D?nes From denes.bisztray at nsn.com Wed Apr 25 09:45:45 2012 From: denes.bisztray at nsn.com (Bisztray, Denes (NSN - HU/Budapest)) Date: Wed, 25 Apr 2012 09:45:45 +0200 Subject: [Fiware-iot] IoT Chapter streamlined architecture In-Reply-To: References: <3F4C11BC54A36642BFB5875D599F47BD05D18CC0@DEMUEXC013.nsn-intra.net> Message-ID: <3F4C11BC54A36642BFB5875D599F47BD05D58638@DEMUEXC013.nsn-intra.net> Hi Jan, Thanks for your detailed reply, my comments are inline: 1. It would be good to add devices below the gw and connected to the different circles. Devices are more or less out of the scope, but they should be there. BD: Agree, Done. 2. I think there should be a direct line between the Backend and a device - not all devices will connect via a gw. BD: Agree, will do ASAP. Needs major rearrange. 3. You have arrows between RD and RM in gw, but no other lines inside the core GE. Either you indicate lines between all boxes, or you remove all lines inside a GE. BD: Agree as well, removed the lines. 4. I do not see why there is a line between Interface and southbound ETSI M2M circle. BD: The interface supposed to mean the implementation of the interface. The circle is "the" interface connection between the elements. The implementation of south and northbound ETSI M2M is possibly the same modul. 5. I propose to move Security GE to the left or right of the core GE and not below. BD: Agree, Done. 6. I suggest to add a line between Protocol Adapter and Plugin Architecture that contains a circle (i.e. an "open" API). This API is needed for integration of third party protocol adapters. Perhaps PA should be in plural, i.e. "Protocol AdapterS"? BD: I assumed here that there is an official protocol on the southbound of the gateway. This is ETSI M2M currently, but may be turn out to be IETF Core. The protocol adapters will use this protocol to translate to, and no to another protocol that is not the official, but used within the system. 7. I suggest to add a northbound Protocol Adapter in the gateway outside the Core GE but within the gateway. This PA should have a circled line to the backend perhaps stating ETSI M2M (we have no such assets as we are all painfully aware of unless somebody has some news). This PA should also have a line to the Core GE containing a circle for the same reason as in 6 above. BD: I believe that is not really an adapter. That is the interface module within the Core GE. Apparently, we are close to finishing an ETSI M2M device with important core functionalities as well as protocol implementation on the centralized backend/gateway. 8. There needs to be a gateway external interface towards DH GE, at least for setting filters etc in CEP. This should be a line with a circle interface. I guess the interface will be proprietary. BD: Agree completely. Added. 9. It can be discussed whether there needs to be an open interface towards Local Storage and whether LS should be in DH GE or in Core GE. Disc Conn in the Core GE has to have means for handling off-line devices which implies various types of storage. This storage is perhaps more of a system internal cache than an appropriate open data base requiring an open interface. BD: The gateway is based on your, TI and Orange assets. Obviously the principle is not to tailor the architecture to a specific asset, but still real-world solution helps to understand the architecture better. I would like to assume more of a coordinator role in such low-level discussions, feel free to propose changes and discuss it with TI and Orange. 10. What Advanced Connectivity will be in the first release? BD: Nothing :). It is the union of those Service Control GE and Connectivity Management GE capabilities that I thought not to be core functionality. It was not assumed to be delivered in the first release. 11. How do we view Remote Device Management? Via ETSI M2M or via a separate interface? The architectural principle of "Separation of Concerns" would make me argue that it should not be part of ETSI M2M, but a separate interface. Following this, as RDM is not specific to IoT, I would also argue that it is not part of the IoT chapter. It should be part of I2ND, but I haven't checked if that is the case. BD: ETSI M2M does provide device commands. I assumed we use it. Feel free to propose different solution. How come there is not CEP or Storage in the Backend? BD: that is the task of the Data and Context Management chapter. Best, D?nes From: "Bisztray, Denes (NSN - HU/Budapest)" > Date: Mon, 23 Apr 2012 09:56:04 +0200 To: "fiware-iot at lists.fi-ware.eu" > Cc: Jan H?ller >, Jakob Saros >, "thierry.nagellen at orange.com" >, Ernoe Kovacs >, Stephan Haller >, "Farkas, Lorant (NSN - HU/Budapest)" >, "jhierro at tid.es" >, Fici Gian Piero >, Guerra Sabrina > Subject: IoT Chapter streamlined architecture Dear all, As mentioned in the previouw weekly meeting, the architecture is getting incomprehensible. This is painful for two reasons. 1. We have to give educational sessions to the UC projects. If we ourselves don't completely understand the architecture, we can't give a proper presentation about it. 2. The open specifications are coming closer. We have way too many GEs compared to other projects, and there are way too many interfaces between these GEs. We supposed to give a fully specified description for every single circle on the FMC diagram. As Gian Piero felt right, the architecture does indeed needs rationalisation. The current GEs are just modules and are not functional outside their context. Thus I created a proposal for a more streamlined architecture. I uploaded to the project svn: https://forge.fi-ware.eu/scmrepos/svn/iot/trunk/documents/FMC/IoT-Streamlined.graphml Also attached to this message. A short presentation on the fundamental changes. We need to discuss this on the Wednesday session, thus I sent it ASAP for you to be able to have a detailed look at it. The asset selection does not change, as you will see, they will seem more natural. We have only 5 GE: 1. Core Functionalities 2. Things Management 3. Advanced Communications 4. Security 5. Protocol Adapter Core Functionalities GE As its name suggests this contains the core functionality of the Backend or Gateway. It includes device-level resource management. The implementation of the northbound and southbound device-level interfaces. Core communication functionality with discontinuous connectivity features as well as a plugin architecture that allows developers to further extensions. Important that this is the basic building block of our system, this is a mandatory component. However if we have this component, the system is already functional. On the gateway this is basically "the gateway", i.e. the Ericsson and TI Gateway. On the Backend this WAS the TID asset, however now I have no idea who will do this. Things Management GE This deals with everything Things-level. We have the IoT Broker, Configuration Management, Configuration Repository and Inference Engine within this GE. It uses the information of the Core Functionalities GE to optain information on the resources. Interfaces: only the things-level extension interface that works on the top of the Core's Resource Management. As a vision this interface should be generic enough to use the Things Management GE on the top of other entities that can be uplifted to a things-level functionality. This supposed to be the NEC and University of Surrey asset. Advanced Communications GE This GE gives advanced communications capabilities, that are not part of the Core functionalities. Mobility Management, Session Management, Traffic Flow management, Quality of Service. This works as an "official" plugin for the Core's communication plugin architecture. This has no current asset selected, as there was no asset for this before. Security GE: PEP, and everything security. Since this has one interface, it can use standards for the security interface. Need to be checked with the Security WP. Protocol Adapter Same as before. It translates the various device-level protocols to the official FIWARE IoT device-level protocol, which is ETSI M2M at the moment. I understand the implications of changing the architecture today. But we need something that we can work with as soon as possible, otherwise we will not able to deliver anything at all. Best, D?nes From lorant.farkas at nsn.com Wed Apr 25 13:59:29 2012 From: lorant.farkas at nsn.com (Farkas, Lorant (NSN - HU/Budapest)) Date: Wed, 25 Apr 2012 14:59:29 +0300 Subject: [Fiware-iot] IoT meeting minutes Message-ID: <93D28BDF64839C468B848D14227151A2036786A4@FIESEXC014.nsn-intra.net> Dear All, Please find the meeting minutes under the following link: https://forge.fi-ware.eu/docman/view.php/11/930/IoT-Minutes-Telco-250420 12.docx Thanks & Br, Lorant -------------- next part -------------- An HTML attachment was scrubbed... URL: From lorant.farkas at nsn.com Wed Apr 25 14:08:43 2012 From: lorant.farkas at nsn.com (Farkas, Lorant (NSN - HU/Budapest)) Date: Wed, 25 Apr 2012 15:08:43 +0300 Subject: [Fiware-iot] info on educational sessions Message-ID: <93D28BDF64839C468B848D14227151A2036786C4@FIESEXC014.nsn-intra.net> Dear All, Please find attached the latest info on the educational sessions. <<[Fiware-training] 'FI-PPP Software Architects Week' Event proposal>> Thanks & Br, Lorant -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- An embedded message was scrubbed... From: "ext CARLOS RALLI UCENDO" Subject: [Fiware-training] 'FI-PPP Software Architects Week' Event proposal Date: Tue, 24 Apr 2012 18:47:32 +0300 Size: 64289 URL: From lorant.farkas at nsn.com Wed Apr 25 14:19:17 2012 From: lorant.farkas at nsn.com (Farkas, Lorant (NSN - HU/Budapest)) Date: Wed, 25 Apr 2012 15:19:17 +0300 Subject: [Fiware-iot] report here the FI-WARE related publications Message-ID: <93D28BDF64839C468B848D14227151A2036786D9@FIESEXC014.nsn-intra.net> Hi Tarek, I found this wiki page where you can report the publication: http://forge.fi-ware.eu/plugins/mediawiki/wiki/fiware/index.php/Dissemin ation_activities Other partners FYI Thanks & Br, Lorant -------------- next part -------------- An HTML attachment was scrubbed... URL: From lorant.farkas at nsn.com Wed Apr 25 14:22:41 2012 From: lorant.farkas at nsn.com (Farkas, Lorant (NSN - HU/Budapest)) Date: Wed, 25 Apr 2012 15:22:41 +0300 Subject: [Fiware-iot] presence in FI week/Aalborg Message-ID: <93D28BDF64839C468B848D14227151A2036786E5@FIESEXC014.nsn-intra.net> Dear All, I forgot to ask you today, but please give me feedback ASAP: who is going to participate in the future internet week in Aalborg? Thanks & Br, Lorant -------------- next part -------------- An HTML attachment was scrubbed... URL: From Martin.Bauer at neclab.eu Wed Apr 25 14:24:09 2012 From: Martin.Bauer at neclab.eu (Martin Bauer) Date: Wed, 25 Apr 2012 12:24:09 +0000 Subject: [Fiware-iot] presence in FI week/Aalborg In-Reply-To: <93D28BDF64839C468B848D14227151A2036786E5@FIESEXC014.nsn-intra.net> References: <93D28BDF64839C468B848D14227151A2036786E5@FIESEXC014.nsn-intra.net> Message-ID: Hi Lorant, all, I will be at FIA in Aalborg. 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 ************************************************************* NEC Europe Limited Registered Office: NEC House, 1 Victoria Road, London W3 6BL Registered in England 2832014 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: Wednesday, April 25, 2012 2:23 PM To: fiware-iot at lists.fi-ware.eu Subject: [Fiware-iot] presence in FI week/Aalborg Dear All, I forgot to ask you today, but please give me feedback ASAP: who is going to participate in the future internet week in Aalborg? Thanks & Br, Lorant -------------- next part -------------- An HTML attachment was scrubbed... URL: From T.Elsaleh at surrey.ac.uk Wed Apr 25 19:17:47 2012 From: T.Elsaleh at surrey.ac.uk (T.Elsaleh at surrey.ac.uk) Date: Wed, 25 Apr 2012 18:17:47 +0100 Subject: [Fiware-iot] High-level description of Ericsson Gateway In-Reply-To: <93D28BDF64839C468B848D14227151A2035EB13E@FIESEXC014.nsn-intra.net> References: <93D28BDF64839C468B848D14227151A2035EB13E@FIESEXC014.nsn-intra.net> Message-ID: <2AAC0B6FF99A064C853BFB1C9295F3CCA59223F92B@EXMB05CMS.surrey.ac.uk> Hello Lorant, Jakob, I would like to follow up on the action point regarding: IoT04_18042012: "AP Payam to look at the GW description and check if USurrey could contribute to the Device Handler in the backend (open specs, implementation)." As I have been away last week, I would like to clarify what exactly is required here. UoS does have an alternative gateway middleware solution, but what is required exactly from us in order to contribute to the "Device Handler"? is it wrt "gateway-to-backend" (northbound) or "gateway-to-device" (southbound)? By the way, isn't the Device Handler GE in the Gateway? In terms of compatibility, is this with respect to CoAP, OSGi, or both? In either case, we currently don't support either of them, but can be considered for near future, as we are interested in using CoAP. Best regards, Tarek Tarek Elsaleh Research Assistant Centre for Commuication Systems Research (CCSR) Department of Electronic Engineering University of Surrey Guildford, GU2 7XH Tel: 01483 689485 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: 18 April 2012 13:06 To: fiware-iot at lists.fi-ware.eu Subject: [Fiware-iot] FW: High-level description of Ericsson Gateway Dear All, FYI (especially Payam/Tarek). Thanks & Br, Lorant From: ext Jakob Saros [mailto:jakob.saros at ericsson.com] Sent: Friday, April 13, 2012 6:15 PM To: Fici Gian Piero; Guerra Sabrina; thierry.nagellen at orange.com; Farkas, Lorant (NSN - HU/Budapest); Bisztray, Denes (NSN - HU/Budapest) Cc: Jan H?ller Subject: High-level description of Ericsson Gateway Hi, Attached is a description of the Ericsson Gateway for further discussions. Please note that this is a DRAFT! The document includes information of gateway components, i.e. OSGi bundles, and interfaces northbound/southbound. I look forward to hearing your comments. BR/Jakob ________________________________ No virus found in this message. Checked by AVG - www.avg.com Version: 2012.0.1913 / Virus Database: 2411/4948 - Release Date: 04/20/12 -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: IoT-Streamlined.png Type: image/png Size: 48754 bytes Desc: IoT-Streamlined.png URL: From lorant.farkas at nsn.com Thu Apr 26 08:22:15 2012 From: lorant.farkas at nsn.com (Farkas, Lorant (NSN - HU/Budapest)) Date: Thu, 26 Apr 2012 09:22:15 +0300 Subject: [Fiware-iot] High-level description of Ericsson Gateway In-Reply-To: <2AAC0B6FF99A064C853BFB1C9295F3CCA59223F92B@EXMB05CMS.surrey.ac.uk> References: <93D28BDF64839C468B848D14227151A2035EB13E@FIESEXC014.nsn-intra.net> <2AAC0B6FF99A064C853BFB1C9295F3CCA59223F92B@EXMB05CMS.surrey.ac.uk> Message-ID: <93D28BDF64839C468B848D14227151A203678934@FIESEXC014.nsn-intra.net> Hello Tarek, The action item is a bit outdated, device handler as GE will not exist under this name any more (pending on approval, of course). Last week we were discussing the issue that there is no owner for the device handler GE and device frontend GE. Payam volunteered to take a look at one of these GE. The additional issue with the device frontend is that the Ericsson asset (gateway asset) speaks a proprietary REST interface on the northbound, implemented by their http server and http-coap proxy, whereas on the backend there is noone to implement the component (earlier this was called device frontend) that discusses with the gateway over this interface. I think it was wrongly captured in the minutes that Payam volunteered to take a look at the device handler, I think he was meaning device frontend. In the new architecture both device frontend and device handler functionalitites should become part of the backend core functionalities GE, I think. The biggest question now is who will implement/specify backend core functionalities GE and your contribution would be welcome here from the frontend perspective because Telefonica will likely not have an interface that discusses with the Ericsson gateway. FYI we were announced yesterday that there is one person from Telefonica dedicated to IoT and also a team will be set up on their side. We will discuss with them next week Thursday or Friday and it would be good if you Tarek could also participate in this call, if you are interested in/can contribute to this GE. Including the alternative gateway middleware solution from your side requires further discussions, but the first step would be for you to share document describing the features and its availability as an asset. Thanks & Br, Lorant From: ext T.Elsaleh at surrey.ac.uk [mailto:T.Elsaleh at surrey.ac.uk] Sent: Wednesday, April 25, 2012 7:18 PM To: Farkas, Lorant (NSN - HU/Budapest); jakob.saros at ericsson.com Cc: fiware-iot at lists.fi-ware.eu Subject: RE: High-level description of Ericsson Gateway Hello Lorant, Jakob, I would like to follow up on the action point regarding: IoT04_18042012: "AP Payam to look at the GW description and check if USurrey could contribute to the Device Handler in the backend (open specs, implementation)." As I have been away last week, I would like to clarify what exactly is required here. UoS does have an alternative gateway middleware solution, but what is required exactly from us in order to contribute to the "Device Handler"? is it wrt "gateway-to-backend" (northbound) or "gateway-to-device" (southbound)? By the way, isn't the Device Handler GE in the Gateway? In terms of compatibility, is this with respect to CoAP, OSGi, or both? In either case, we currently don't support either of them, but can be considered for near future, as we are interested in using CoAP. Best regards, Tarek Tarek Elsaleh Research Assistant Centre for Commuication Systems Research (CCSR) Department of Electronic Engineering University of Surrey Guildford, GU2 7XH Tel: 01483 689485 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: 18 April 2012 13:06 To: fiware-iot at lists.fi-ware.eu Subject: [Fiware-iot] FW: High-level description of Ericsson Gateway Dear All, FYI (especially Payam/Tarek). Thanks & Br, Lorant From: ext Jakob Saros [mailto:jakob.saros at ericsson.com] Sent: Friday, April 13, 2012 6:15 PM To: Fici Gian Piero; Guerra Sabrina; thierry.nagellen at orange.com; Farkas, Lorant (NSN - HU/Budapest); Bisztray, Denes (NSN - HU/Budapest) Cc: Jan H?ller Subject: High-level description of Ericsson Gateway Hi, Attached is a description of the Ericsson Gateway for further discussions. Please note that this is a DRAFT! The document includes information of gateway components, i.e. OSGi bundles, and interfaces northbound/southbound. I look forward to hearing your comments. BR/Jakob ________________________________ No virus found in this message. Checked by AVG - www.avg.com Version: 2012.0.1913 / Virus Database: 2411/4948 - Release Date: 04/20/12 -------------- next part -------------- An HTML attachment was scrubbed... URL: From jan.holler at ericsson.com Thu Apr 26 08:36:35 2012 From: jan.holler at ericsson.com (=?utf-8?B?SmFuIEjDtmxsZXI=?=) Date: Thu, 26 Apr 2012 08:36:35 +0200 Subject: [Fiware-iot] High-level description of Ericsson Gateway In-Reply-To: <93D28BDF64839C468B848D14227151A203678934@FIESEXC014.nsn-intra.net> References: <93D28BDF64839C468B848D14227151A2035EB13E@FIESEXC014.nsn-intra.net> <2AAC0B6FF99A064C853BFB1C9295F3CCA59223F92B@EXMB05CMS.surrey.ac.uk> <93D28BDF64839C468B848D14227151A203678934@FIESEXC014.nsn-intra.net> Message-ID: <7B0160AE-1EA0-4BED-9400-39C634F514C3@ericsson.com> Hello, Just one minor clarification. The gw northbound interface isn't entirely proprietary. It is based on IRTF CoRE work and there are hence openly available specifications that define the interface in smaller or larger parts. There is one remaining component though that remains to be sorted out, and that is an appropriate profile for IoT resources. This is something being worked at, but it is for the time being entirely proprietary. Jan 26 apr 2012 kl. 08:22 skrev "Farkas, Lorant (NSN - HU/Budapest)" >: Hello Tarek, The action item is a bit outdated, device handler as GE will not exist under this name any more (pending on approval, of course). Last week we were discussing the issue that there is no owner for the device handler GE and device frontend GE. Payam volunteered to take a look at one of these GE. The additional issue with the device frontend is that the Ericsson asset (gateway asset) speaks a proprietary REST interface on the northbound, implemented by their http server and http-coap proxy, whereas on the backend there is noone to implement the component (earlier this was called device frontend) that discusses with the gateway over this interface. I think it was wrongly captured in the minutes that Payam volunteered to take a look at the device handler, I think he was meaning device frontend. In the new architecture both device frontend and device handler functionalitites should become part of the backend core functionalities GE, I think. The biggest question now is who will implement/specify backend core functionalities GE and your contribution would be welcome here from the frontend perspective because Telefonica will likely not have an interface that discusses with the Ericsson gateway. FYI we were announced yesterday that there is one person from Telefonica dedicated to IoT and also a team will be set up on their side. We will discuss with them next week Thursday or Friday and it would be good if you Tarek could also participate in this call, if you are interested in/can contribute to this GE. Including the alternative gateway middleware solution from your side requires further discussions, but the first step would be for you to share document describing the features and its availability as an asset. Thanks & Br, Lorant From: ext T.Elsaleh at surrey.ac.uk [mailto:T.Elsaleh at surrey.ac.uk] Sent: Wednesday, April 25, 2012 7:18 PM To: Farkas, Lorant (NSN - HU/Budapest); jakob.saros at ericsson.com Cc: fiware-iot at lists.fi-ware.eu Subject: RE: High-level description of Ericsson Gateway Hello Lorant, Jakob, I would like to follow up on the action point regarding: IoT04_18042012: ?AP Payam to look at the GW description and check if USurrey could contribute to the Device Handler in the backend (open specs, implementation).? As I have been away last week, I would like to clarify what exactly is required here. UoS does have an alternative gateway middleware solution, but what is required exactly from us in order to contribute to the ?Device Handler?? is it wrt ?gateway-to-backend? (northbound) or ?gateway-to-device? (southbound)? By the way, isn?t the Device Handler GE in the Gateway? In terms of compatibility, is this with respect to CoAP, OSGi, or both? In either case, we currently don?t support either of them, but can be considered for near future, as we are interested in using CoAP. Best regards, Tarek Tarek Elsaleh Research Assistant Centre for Commuication Systems Research (CCSR) Department of Electronic Engineering University of Surrey Guildford, GU2 7XH Tel: 01483 689485 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: 18 April 2012 13:06 To: fiware-iot at lists.fi-ware.eu Subject: [Fiware-iot] FW: High-level description of Ericsson Gateway Dear All, FYI (especially Payam/Tarek). Thanks & Br, Lorant From: ext Jakob Saros [mailto:jakob.saros at ericsson.com] Sent: Friday, April 13, 2012 6:15 PM To: Fici Gian Piero; Guerra Sabrina; thierry.nagellen at orange.com; Farkas, Lorant (NSN - HU/Budapest); Bisztray, Denes (NSN - HU/Budapest) Cc: Jan H?ller Subject: High-level description of Ericsson Gateway Hi, Attached is a description of the Ericsson Gateway for further discussions. Please note that this is a DRAFT! The document includes information of gateway components, i.e. OSGi bundles, and interfaces northbound/southbound. I look forward to hearing your comments. BR/Jakob ________________________________ No virus found in this message. Checked by AVG - www.avg.com Version: 2012.0.1913 / Virus Database: 2411/4948 - Release Date: 04/20/12 _______________________________________________ Fiware-iot mailing list Fiware-iot at lists.fi-ware.eu http://lists.fi-ware.eu/listinfo/fiware-iot From T.Elsaleh at surrey.ac.uk Thu Apr 26 17:47:01 2012 From: T.Elsaleh at surrey.ac.uk (T.Elsaleh at surrey.ac.uk) Date: Thu, 26 Apr 2012 16:47:01 +0100 Subject: [Fiware-iot] High-level description of Ericsson Gateway In-Reply-To: <7B0160AE-1EA0-4BED-9400-39C634F514C3@ericsson.com> References: <93D28BDF64839C468B848D14227151A2035EB13E@FIESEXC014.nsn-intra.net> <2AAC0B6FF99A064C853BFB1C9295F3CCA59223F92B@EXMB05CMS.surrey.ac.uk> <93D28BDF64839C468B848D14227151A203678934@FIESEXC014.nsn-intra.net> <7B0160AE-1EA0-4BED-9400-39C634F514C3@ericsson.com> Message-ID: <2AAC0B6FF99A064C853BFB1C9295F3CCA59223FA35@EXMB05CMS.surrey.ac.uk> Hello Jan, Just to clarify, when you say gw northbound, do you mean "resource-to-gateway" or "gateway-to-backend"? Could you tell me what interface type you are using? Is it CoAP-related? Because from what I understand of CoAP is that it works between the gateway and the resource (e.g. sensor). So what do you expect to use between gateway and backend? Please correct me if I am mistaken. Best regards, Tarek > -----Original Message----- > From: Jan H?ller [mailto:jan.holler at ericsson.com] > Sent: 26 April 2012 07:37 > To: Farkas, Lorant (NSN - HU/Budapest) > Cc: Elsaleh T Mr (Electronic Eng); Jakob Saros; fiware-iot at lists.fi- > ware.eu > Subject: Re: [Fiware-iot] High-level description of Ericsson Gateway > > Hello, > > Just one minor clarification. The gw northbound interface isn't > entirely proprietary. It is based on IRTF CoRE work and there are hence > openly available specifications that define the interface in smaller or > larger parts. There is one remaining component though that remains to > be sorted out, and that is an appropriate profile for IoT resources. > This is something being worked at, but it is for the time being > entirely proprietary. > > Jan > > 26 apr 2012 kl. 08:22 skrev "Farkas, Lorant (NSN - HU/Budapest)" > >: > > Hello Tarek, > > The action item is a bit outdated, device handler as GE will not exist > under this name any more (pending on approval, of course). > Last week we were discussing the issue that there is no owner for the > device handler GE and device frontend GE. Payam volunteered to take a > look at one of these GE. > The additional issue with the device frontend is that the Ericsson > asset (gateway asset) speaks a proprietary REST interface on the > northbound, implemented by their http server and http-coap proxy, > whereas on the backend there is noone to implement the component > (earlier this was called device frontend) that discusses with the > gateway over this interface. > > I think it was wrongly captured in the minutes that Payam volunteered > to take a look at the device handler, I think he was meaning device > frontend. > > In the new architecture both device frontend and device handler > functionalitites should become part of the backend core functionalities > GE, I think. > > The biggest question now is who will implement/specify backend core > functionalities GE and your contribution would be welcome here from the > frontend perspective because Telefonica will likely not have an > interface that discusses with the Ericsson gateway. > FYI we were announced yesterday that there is one person from > Telefonica dedicated to IoT and also a team will be set up on their > side. We will discuss with them next week Thursday or Friday and it > would be good if you Tarek could also participate in this call, if you > are interested in/can contribute to this GE. > > Including the alternative gateway middleware solution from your side > requires further discussions, but the first step would be for you to > share document describing the features and its availability as an > asset. > > Thanks & Br, > > Lorant > > > > From: ext T.Elsaleh at surrey.ac.uk > [mailto:T.Elsaleh at surrey.ac.uk] > Sent: Wednesday, April 25, 2012 7:18 PM > To: Farkas, Lorant (NSN - HU/Budapest); > jakob.saros at ericsson.com > Cc: fiware-iot at lists.fi-ware.eu > Subject: RE: High-level description of Ericsson Gateway > > Hello Lorant, Jakob, > > I would like to follow up on the action point regarding: > > IoT04_18042012: ?AP Payam to look at the GW description and check if > USurrey could contribute to the Device Handler in the backend (open > specs, implementation).? > > As I have been away last week, I would like to clarify what exactly is > required here. UoS does have an alternative gateway middleware > solution, but what is required exactly from us in order to contribute > to the ?Device Handler?? is it wrt ?gateway-to-backend? (northbound) or > ?gateway-to-device? (southbound)? > > By the way, isn?t the Device Handler GE in the Gateway? > > In terms of compatibility, is this with respect to CoAP, OSGi, or both? > In either case, we currently don?t support either of them, but can be > considered for near future, as we are interested in using CoAP. > > > Best regards, > Tarek > > Tarek Elsaleh > Research Assistant > Centre for Commuication Systems Research (CCSR) Department of > Electronic Engineering University of Surrey Guildford, GU2 7XH > Tel: 01483 689485 > > > > From: fiware-iot-bounces at lists.fi-ware.eu bounces at lists.fi-ware.eu> [mailto:fiware-iot-bounces at lists.fi-ware.eu] > On Behalf Of Farkas, Lorant (NSN - HU/Budapest) > Sent: 18 April 2012 13:06 > To: fiware-iot at lists.fi-ware.eu > Subject: [Fiware-iot] FW: High-level description of Ericsson Gateway > > Dear All, > > FYI (especially Payam/Tarek). > > Thanks & Br, > > Lorant > > > From: ext Jakob Saros [mailto:jakob.saros at ericsson.com] > Sent: Friday, April 13, 2012 6:15 PM > To: Fici Gian Piero; Guerra Sabrina; > thierry.nagellen at orange.com; > Farkas, Lorant (NSN - HU/Budapest); Bisztray, Denes (NSN - HU/Budapest) > Cc: Jan H?ller > Subject: High-level description of Ericsson Gateway > > Hi, > > Attached is a description of the Ericsson Gateway for further > discussions. Please note that this is a DRAFT! The document includes > information of gateway components, i.e. OSGi bundles, and interfaces > northbound/southbound. I look forward to hearing your comments. > > BR/Jakob > > > ________________________________ > No virus found in this message. > Checked by AVG - www.avg.com > Version: 2012.0.1913 / Virus Database: 2411/4948 - Release Date: > 04/20/12 _______________________________________________ > Fiware-iot mailing list > Fiware-iot at lists.fi-ware.eu > http://lists.fi-ware.eu/listinfo/fiware-iot > > ----- > No virus found in this message. > Checked by AVG - www.avg.com > Version: 2012.0.1913 / Virus Database: 2411/4958 - Release Date: > 04/25/12 From T.Elsaleh at surrey.ac.uk Thu Apr 26 17:54:32 2012 From: T.Elsaleh at surrey.ac.uk (T.Elsaleh at surrey.ac.uk) Date: Thu, 26 Apr 2012 16:54:32 +0100 Subject: [Fiware-iot] High-level description of Ericsson Gateway In-Reply-To: <93D28BDF64839C468B848D14227151A203678934@FIESEXC014.nsn-intra.net> References: <93D28BDF64839C468B848D14227151A2035EB13E@FIESEXC014.nsn-intra.net> <2AAC0B6FF99A064C853BFB1C9295F3CCA59223F92B@EXMB05CMS.surrey.ac.uk> <93D28BDF64839C468B848D14227151A203678934@FIESEXC014.nsn-intra.net> Message-ID: <2AAC0B6FF99A064C853BFB1C9295F3CCA59223FA39@EXMB05CMS.surrey.ac.uk> Hello Lorant, My initial understanding from "Device Frontend" is that handles interaction between device and gateway. So why should it be in the backend? ...Or what is meant by "device" is really the gateway representing the devices...? Is there any reference to what functionalities are expected from a "device frontend" at this moment? Best regards, Tarek From: Farkas, Lorant (NSN - HU/Budapest) [mailto:lorant.farkas at nsn.com] Sent: 26 April 2012 07:22 To: Elsaleh T Mr (Electronic Eng); jakob.saros at ericsson.com Cc: fiware-iot at lists.fi-ware.eu Subject: RE: High-level description of Ericsson Gateway Hello Tarek, The action item is a bit outdated, device handler as GE will not exist under this name any more (pending on approval, of course). Last week we were discussing the issue that there is no owner for the device handler GE and device frontend GE. Payam volunteered to take a look at one of these GE. The additional issue with the device frontend is that the Ericsson asset (gateway asset) speaks a proprietary REST interface on the northbound, implemented by their http server and http-coap proxy, whereas on the backend there is noone to implement the component (earlier this was called device frontend) that discusses with the gateway over this interface. I think it was wrongly captured in the minutes that Payam volunteered to take a look at the device handler, I think he was meaning device frontend. In the new architecture both device frontend and device handler functionalitites should become part of the backend core functionalities GE, I think. The biggest question now is who will implement/specify backend core functionalities GE and your contribution would be welcome here from the frontend perspective because Telefonica will likely not have an interface that discusses with the Ericsson gateway. FYI we were announced yesterday that there is one person from Telefonica dedicated to IoT and also a team will be set up on their side. We will discuss with them next week Thursday or Friday and it would be good if you Tarek could also participate in this call, if you are interested in/can contribute to this GE. Including the alternative gateway middleware solution from your side requires further discussions, but the first step would be for you to share document describing the features and its availability as an asset. Thanks & Br, Lorant From: ext T.Elsaleh at surrey.ac.uk [mailto:T.Elsaleh at surrey.ac.uk] Sent: Wednesday, April 25, 2012 7:18 PM To: Farkas, Lorant (NSN - HU/Budapest); jakob.saros at ericsson.com Cc: fiware-iot at lists.fi-ware.eu Subject: RE: High-level description of Ericsson Gateway Hello Lorant, Jakob, I would like to follow up on the action point regarding: IoT04_18042012: "AP Payam to look at the GW description and check if USurrey could contribute to the Device Handler in the backend (open specs, implementation)." As I have been away last week, I would like to clarify what exactly is required here. UoS does have an alternative gateway middleware solution, but what is required exactly from us in order to contribute to the "Device Handler"? is it wrt "gateway-to-backend" (northbound) or "gateway-to-device" (southbound)? By the way, isn't the Device Handler GE in the Gateway? In terms of compatibility, is this with respect to CoAP, OSGi, or both? In either case, we currently don't support either of them, but can be considered for near future, as we are interested in using CoAP. Best regards, Tarek Tarek Elsaleh Research Assistant Centre for Commuication Systems Research (CCSR) Department of Electronic Engineering University of Surrey Guildford, GU2 7XH Tel: 01483 689485 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: 18 April 2012 13:06 To: fiware-iot at lists.fi-ware.eu Subject: [Fiware-iot] FW: High-level description of Ericsson Gateway Dear All, FYI (especially Payam/Tarek). Thanks & Br, Lorant From: ext Jakob Saros [mailto:jakob.saros at ericsson.com] Sent: Friday, April 13, 2012 6:15 PM To: Fici Gian Piero; Guerra Sabrina; thierry.nagellen at orange.com; Farkas, Lorant (NSN - HU/Budapest); Bisztray, Denes (NSN - HU/Budapest) Cc: Jan H?ller Subject: High-level description of Ericsson Gateway Hi, Attached is a description of the Ericsson Gateway for further discussions. Please note that this is a DRAFT! The document includes information of gateway components, i.e. OSGi bundles, and interfaces northbound/southbound. I look forward to hearing your comments. BR/Jakob ________________________________ No virus found in this message. Checked by AVG - www.avg.com Version: 2012.0.1913 / Virus Database: 2411/4948 - Release Date: 04/20/12 ________________________________ No virus found in this message. Checked by AVG - www.avg.com Version: 2012.0.1913 / Virus Database: 2411/4958 - Release Date: 04/25/12 -------------- next part -------------- An HTML attachment was scrubbed... URL: From jan.holler at ericsson.com Thu Apr 26 20:48:22 2012 From: jan.holler at ericsson.com (=?iso-8859-1?Q?Jan_H=F6ller?=) Date: Thu, 26 Apr 2012 20:48:22 +0200 Subject: [Fiware-iot] High-level description of Ericsson Gateway In-Reply-To: <2AAC0B6FF99A064C853BFB1C9295F3CCA59223FA35@EXMB05CMS.surrey.ac.uk> Message-ID: Hello Tarek, Sorry if this was somewhat confusing and unclear. By northbound gw I mean the interface between the gateway and the backend. I also mistakenly wrote IRTF, it should be IETF (IRTF is not doing any similar work). This interface is based on CoRE, so yes, it relates to CoAP. But in CoRE there is also work on CoAP-HTTP proxying. What is more important in this context, I would say, is the web resource model proposed in CoRE. That is sort of independent on if you run it over CoAP or HTTP. This is what we are proposing. And just to be clear, it is perfectly possible to terminate CoAP in the backend as well, both via a gateway (then in one instance acting more as an IP gateway), or directly from an IoT device. I hope this helps. Best regards, Jan On 26042012 5:47 PM, "T.Elsaleh at surrey.ac.uk" wrote: >Hello Jan, > >Just to clarify, when you say gw northbound, do you mean >"resource-to-gateway" or "gateway-to-backend"? > >Could you tell me what interface type you are using? Is it CoAP-related? >Because from what I understand of CoAP is that it works between the >gateway and the resource (e.g. sensor). So what do you expect to use >between gateway and backend? > >Please correct me if I am mistaken. > >Best regards, >Tarek > > >> -----Original Message----- >> From: Jan H?ller [mailto:jan.holler at ericsson.com] >> Sent: 26 April 2012 07:37 >> To: Farkas, Lorant (NSN - HU/Budapest) >> Cc: Elsaleh T Mr (Electronic Eng); Jakob Saros; fiware-iot at lists.fi- >> ware.eu >> Subject: Re: [Fiware-iot] High-level description of Ericsson Gateway >> >> Hello, >> >> Just one minor clarification. The gw northbound interface isn't >> entirely proprietary. It is based on IRTF CoRE work and there are hence >> openly available specifications that define the interface in smaller or >> larger parts. There is one remaining component though that remains to >> be sorted out, and that is an appropriate profile for IoT resources. >> This is something being worked at, but it is for the time being >> entirely proprietary. >> >> Jan >> >> 26 apr 2012 kl. 08:22 skrev "Farkas, Lorant (NSN - HU/Budapest)" >> >: >> >> Hello Tarek, >> >> The action item is a bit outdated, device handler as GE will not exist >> under this name any more (pending on approval, of course). >> Last week we were discussing the issue that there is no owner for the >> device handler GE and device frontend GE. Payam volunteered to take a >> look at one of these GE. >> The additional issue with the device frontend is that the Ericsson >> asset (gateway asset) speaks a proprietary REST interface on the >> northbound, implemented by their http server and http-coap proxy, >> whereas on the backend there is noone to implement the component >> (earlier this was called device frontend) that discusses with the >> gateway over this interface. >> >> I think it was wrongly captured in the minutes that Payam volunteered >> to take a look at the device handler, I think he was meaning device >> frontend. >> >> In the new architecture both device frontend and device handler >> functionalitites should become part of the backend core functionalities >> GE, I think. >> >> The biggest question now is who will implement/specify backend core >> functionalities GE and your contribution would be welcome here from the >> frontend perspective because Telefonica will likely not have an >> interface that discusses with the Ericsson gateway. >> FYI we were announced yesterday that there is one person from >> Telefonica dedicated to IoT and also a team will be set up on their >> side. We will discuss with them next week Thursday or Friday and it >> would be good if you Tarek could also participate in this call, if you >> are interested in/can contribute to this GE. >> >> Including the alternative gateway middleware solution from your side >> requires further discussions, but the first step would be for you to >> share document describing the features and its availability as an >> asset. >> >> Thanks & Br, >> >> Lorant >> >> >> >> From: ext T.Elsaleh at surrey.ac.uk >> [mailto:T.Elsaleh at surrey.ac.uk] >> Sent: Wednesday, April 25, 2012 7:18 PM >> To: Farkas, Lorant (NSN - HU/Budapest); >> jakob.saros at ericsson.com >> Cc: fiware-iot at lists.fi-ware.eu >> Subject: RE: High-level description of Ericsson Gateway >> >> Hello Lorant, Jakob, >> >> I would like to follow up on the action point regarding: >> >> IoT04_18042012: ?AP Payam to look at the GW description and check if >> USurrey could contribute to the Device Handler in the backend (open >> specs, implementation).? >> >> As I have been away last week, I would like to clarify what exactly is >> required here. UoS does have an alternative gateway middleware >> solution, but what is required exactly from us in order to contribute >> to the ?Device Handler?? is it wrt ?gateway-to-backend? (northbound) or >> ?gateway-to-device? (southbound)? >> >> By the way, isn?t the Device Handler GE in the Gateway? >> >> In terms of compatibility, is this with respect to CoAP, OSGi, or both? >> In either case, we currently don?t support either of them, but can be >> considered for near future, as we are interested in using CoAP. >> >> >> Best regards, >> Tarek >> >> Tarek Elsaleh >> Research Assistant >> Centre for Commuication Systems Research (CCSR) Department of >> Electronic Engineering University of Surrey Guildford, GU2 7XH >> Tel: 01483 689485 >> >> >> >> From: fiware-iot-bounces at lists.fi-ware.eu> bounces at lists.fi-ware.eu> [mailto:fiware-iot-bounces at lists.fi-ware.eu] >> On Behalf Of Farkas, Lorant (NSN - HU/Budapest) >> Sent: 18 April 2012 13:06 >> To: fiware-iot at lists.fi-ware.eu >> Subject: [Fiware-iot] FW: High-level description of Ericsson Gateway >> >> Dear All, >> >> FYI (especially Payam/Tarek). >> >> Thanks & Br, >> >> Lorant >> >> >> From: ext Jakob Saros [mailto:jakob.saros at ericsson.com] >> Sent: Friday, April 13, 2012 6:15 PM >> To: Fici Gian Piero; Guerra Sabrina; >> thierry.nagellen at orange.com; >> Farkas, Lorant (NSN - HU/Budapest); Bisztray, Denes (NSN - HU/Budapest) >> Cc: Jan H?ller >> Subject: High-level description of Ericsson Gateway >> >> Hi, >> >> Attached is a description of the Ericsson Gateway for further >> discussions. Please note that this is a DRAFT! The document includes >> information of gateway components, i.e. OSGi bundles, and interfaces >> northbound/southbound. I look forward to hearing your comments. >> >> BR/Jakob >> >> >> ________________________________ >> No virus found in this message. >> Checked by AVG - www.avg.com >> Version: 2012.0.1913 / Virus Database: 2411/4948 - Release Date: >> 04/20/12 _______________________________________________ >> Fiware-iot mailing list >> Fiware-iot at lists.fi-ware.eu >> http://lists.fi-ware.eu/listinfo/fiware-iot >> >> ----- >> No virus found in this message. >> Checked by AVG - www.avg.com >> Version: 2012.0.1913 / Virus Database: 2411/4958 - Release Date: >> 04/25/12 From jan.holler at ericsson.com Thu Apr 26 21:20:37 2012 From: jan.holler at ericsson.com (=?iso-8859-1?Q?Jan_H=F6ller?=) Date: Thu, 26 Apr 2012 21:20:37 +0200 Subject: [Fiware-iot] IoT Chapter streamlined architecture In-Reply-To: <3F4C11BC54A36642BFB5875D599F47BD05D58638@DEMUEXC013.nsn-intra.net> Message-ID: Hello Denes As discussed in the telco, please find the proposed update of the FMC diagram wrt the gateway. The rationale behind the change is the following. I have moved the device interfaces/circles to be outside of the gateway since they do not represent (software) APIs but interfaces specified by a protocol (stack). I make a distinction between a software architecture or sw component oriented view and a functional view of a gateway. A software view points towards an implementation. I think the FMC diagram should capture the functional view rather than the implementation view. The only thing that is dictating the implementation is the interfaces and APIs we have. These represent "fix points" that we need to have for various reasons (openness towards systems integration being one). So that is the reason for having a protocol adapter in the gateway towards the backend as well. This is a mapping of the internal API (denoted IETF CoRE) towards the ETSI M2M interface, as well as the protocol itself. This is a comment towards point 4 in the previous mail below. The interface as such (ETSI M2M) is not part of the Gateway Core GE in our opinion. We need to make a clear separation of protocol logic from application logic. The Core GE contains application logic that can be bound to different protocols (or binding components). Hence the representation of the actual interface instance should be kept separate. Furthermore, by having also the gateway internal APIs as "circles" we ensure that we have published APIs that can be used for any partner to do a proper systems integration activity of a specific protocol. Especially since we do not have ETSI today, this API is important. And it allows us to bind the gateway to any other protocol if so desired at a later stage. Regarding comment below, a circled API also ensures a systems integration point towards legacy or any other protocol (and also a separation of the binding component from application logic southbound). Also, the capabilities exposed by the gateway towards the backend is "richer" than the capabilities exposed by an individual IoT device towards the gateway. This is because the gateway typically host own IoT resources as well (storage, processing, CEP etc are all representing different resources than those by the devices themselves). So, an ETSI M2M interface between the device and the gateway is different from an ETSI M2M interface between the gateway and the backend. Your proposal of an interface with lines going both towards the gateway AND the devices is misleading and also wrong from a functional perspective, I would argue. Lastly, on the device management topic, I am not familiar enough with M2M ETSI capabilities on "device commands" as you call them, but I doubt that ETSI M2M provides the same capabilities as e.g. TR069. Hence, for any deployable "complete" gateway, there will be one IoT interface and one DM interface, e.g. ETSI M2M and TR069. Now, considering legacy devices, as some of these legacy protocols contain bundled capabilities for handling both device level issues (DM) and sensor/atuator capabilities (IoT), I feel that we might need some more discussion on the relation to I2ND wrt Device Management. I don't know if this has been discussed with the I2ND chapter in the past, or if there is an agreement in place. I hope I managed to explain my thinking on this topic. Please provide your comments in return. Best regards, Jan On 25042012 9:45 AM, "Bisztray, Denes (NSN - HU/Budapest)" wrote: >Hi Jan, > >Thanks for your detailed reply, my comments are inline: > > 1. It would be good to add devices below the gw and connected to the >different circles. Devices are more or less out of the scope, but they >should be there. > >BD: Agree, Done. > > 2. I think there should be a direct line between the Backend and a >device - not all devices will connect via a gw. > >BD: Agree, will do ASAP. Needs major rearrange. > > 3. You have arrows between RD and RM in gw, but no other lines inside >the core GE. Either you indicate lines between all boxes, or you remove >all lines inside a GE. > >BD: Agree as well, removed the lines. > > 4. I do not see why there is a line between Interface and southbound >ETSI M2M circle. > >BD: The interface supposed to mean the implementation of the interface. >The circle is "the" interface connection between the elements. The >implementation of south and northbound ETSI M2M is possibly the same >modul. > > 5. I propose to move Security GE to the left or right of the core GE >and not below. > >BD: Agree, Done. > > 6. I suggest to add a line between Protocol Adapter and Plugin >Architecture that contains a circle (i.e. an "open" API). This API is >needed for integration of third party protocol adapters. Perhaps PA >should be in plural, i.e. "Protocol AdapterS"? > >BD: I assumed here that there is an official protocol on the southbound >of the gateway. This is ETSI M2M currently, but may be turn out to be >IETF Core. The protocol adapters will use this protocol to translate to, >and no to another protocol that is not the official, but used within the >system. > > 7. I suggest to add a northbound Protocol Adapter in the gateway >outside the Core GE but within the gateway. This PA should have a circled >line to the backend perhaps stating ETSI M2M (we have no such assets as >we are all painfully aware of unless somebody has some news). This PA >should also have a line to the Core GE containing a circle for the same >reason as in 6 above. > >BD: I believe that is not really an adapter. That is the interface module >within the Core GE. >Apparently, we are close to finishing an ETSI M2M device with important >core functionalities as well as protocol implementation on the >centralized backend/gateway. > > 8. There needs to be a gateway external interface towards DH GE, at >least for setting filters etc in CEP. This should be a line with a circle >interface. I guess the interface will be proprietary. > >BD: Agree completely. Added. > > 9. It can be discussed whether there needs to be an open interface >towards Local Storage and whether LS should be in DH GE or in Core GE. >Disc Conn in the Core GE has to have means for handling off-line devices >which implies various types of storage. This storage is perhaps more of a >system internal cache than an appropriate open data base requiring an >open interface. > >BD: The gateway is based on your, TI and Orange assets. Obviously the >principle is not to tailor the architecture to a specific asset, but >still real-world solution helps to understand the architecture better. I >would like to assume more of a coordinator role in such low-level >discussions, feel free to propose changes and discuss it with TI and >Orange. > > 10. What Advanced Connectivity will be in the first release? > >BD: Nothing :). It is the union of those Service Control GE and >Connectivity Management GE capabilities that I thought not to be core >functionality. It was not assumed to be delivered in the first release. > > 11. How do we view Remote Device Management? Via ETSI M2M or via a >separate interface? The architectural principle of "Separation of >Concerns" would make me argue that it should not be part of ETSI M2M, but >a separate interface. Following this, as RDM is not specific to IoT, I >would also argue that it is not part of the IoT chapter. It should be >part of I2ND, but I haven't checked if that is the case. > >BD: ETSI M2M does provide device commands. I assumed we use it. Feel free >to propose different solution. > >How come there is not CEP or Storage in the Backend? > >BD: that is the task of the Data and Context Management chapter. > >Best, > >D?nes > > >From: "Bisztray, Denes (NSN - HU/Budapest)" >> >Date: Mon, 23 Apr 2012 09:56:04 +0200 >To: "fiware-iot at lists.fi-ware.eu" >> >Cc: Jan H?ller >, >Jakob Saros >, >"thierry.nagellen at orange.com" >>, Ernoe >Kovacs >, Stephan >Haller >, "Farkas, >Lorant (NSN - HU/Budapest)" >>, >"jhierro at tid.es" >>, Fici Gian Piero >>, > Guerra Sabrina >> >Subject: IoT Chapter streamlined architecture > >Dear all, > >As mentioned in the previouw weekly meeting, the architecture is getting >incomprehensible. This is painful for two reasons. > >1. We have to give educational sessions to the UC projects. If we >ourselves don't completely understand the architecture, we can't give a >proper presentation about it. > >2. The open specifications are coming closer. We have way too many >GEs compared to other projects, and there are way too many interfaces >between these GEs. We supposed to give a fully specified description for >every single circle on the FMC diagram. > >As Gian Piero felt right, the architecture does indeed needs >rationalisation. >The current GEs are just modules and are not functional outside their >context. Thus I created a proposal for a more streamlined architecture. >I uploaded to the project svn: >https://forge.fi-ware.eu/scmrepos/svn/iot/trunk/documents/FMC/IoT-Streamli >ned.graphml >Also attached to this message. > >A short presentation on the fundamental changes. We need to discuss this >on the Wednesday session, thus I sent it ASAP for you to be able to have >a detailed look at it. > >The asset selection does not change, as you will see, they will seem more >natural. > >We have only 5 GE: > >1. Core Functionalities > >2. Things Management > >3. Advanced Communications > >4. Security > >5. Protocol Adapter > >Core Functionalities GE >As its name suggests this contains the core functionality of the Backend >or Gateway. It includes device-level resource management. The >implementation of the northbound and southbound device-level interfaces. >Core communication functionality with discontinuous connectivity features >as well as a plugin architecture that allows developers to further >extensions. Important that this is the basic building block of our >system, this is a mandatory component. However if we have this component, >the system is already functional. >On the gateway this is basically "the gateway", i.e. the Ericsson and TI >Gateway. On the Backend this WAS the TID asset, however now I have no >idea who will do this. > >Things Management GE >This deals with everything Things-level. We have the IoT Broker, >Configuration Management, Configuration Repository and Inference Engine >within this GE. It uses the information of the Core Functionalities GE to >optain information on the resources. >Interfaces: only the things-level extension interface that works on the >top of the Core's Resource Management. As a vision this interface should >be generic enough to use the Things Management GE on the top of other >entities that can be uplifted to a things-level functionality. >This supposed to be the NEC and University of Surrey asset. > > >Advanced Communications GE >This GE gives advanced communications capabilities, that are not part of >the Core functionalities. Mobility Management, Session Management, >Traffic Flow management, Quality of Service. This works as an "official" >plugin for the Core's communication plugin architecture. >This has no current asset selected, as there was no asset for this before. > >Security GE: >PEP, and everything security. Since this has one interface, it can use >standards for the security interface. Need to be checked with the >Security WP. > >Protocol Adapter >Same as before. It translates the various device-level protocols to the >official FIWARE IoT device-level protocol, which is ETSI M2M at the >moment. > >I understand the implications of changing the architecture today. But we >need something that we can work with as soon as possible, otherwise we >will not able to deliver anything at all. > >Best, >D?nes -------------- next part -------------- A non-text attachment was scrubbed... Name: IoT-Streamlined.graphml Type: application/octet-stream Size: 85355 bytes Desc: IoT-Streamlined.graphml URL: From lorant.farkas at nsn.com Fri Apr 27 08:41:02 2012 From: lorant.farkas at nsn.com (Farkas, Lorant (NSN - HU/Budapest)) Date: Fri, 27 Apr 2012 09:41:02 +0300 Subject: [Fiware-iot] High-level description of Ericsson Gateway In-Reply-To: <2AAC0B6FF99A064C853BFB1C9295F3CCA59223FA39@EXMB05CMS.surrey.ac.uk> References: <93D28BDF64839C468B848D14227151A2035EB13E@FIESEXC014.nsn-intra.net> <2AAC0B6FF99A064C853BFB1C9295F3CCA59223F92B@EXMB05CMS.surrey.ac.uk> <93D28BDF64839C468B848D14227151A203678934@FIESEXC014.nsn-intra.net> <2AAC0B6FF99A064C853BFB1C9295F3CCA59223FA39@EXMB05CMS.surrey.ac.uk> Message-ID: <93D28BDF64839C468B848D14227151A203678F0E@FIESEXC014.nsn-intra.net> Hi Tarek, Answers inline. Br, Lorant From: ext T.Elsaleh at surrey.ac.uk [mailto:T.Elsaleh at surrey.ac.uk] Sent: Thursday, April 26, 2012 5:55 PM To: Farkas, Lorant (NSN - HU/Budapest); jakob.saros at ericsson.com Cc: fiware-iot at lists.fi-ware.eu Subject: RE: High-level description of Ericsson Gateway Hello Lorant, My initial understanding from "Device Frontend" is that handles interaction between device and gateway. So why should it be in the backend? "FI-WARE IoT compliant" devices should be able to connect directly to the backend. ...Or what is meant by "device" is really the gateway representing the devices...? Yes. Gateways should also be handled by the device frontent in the backend. Is there any reference to what functionalities are expected from a "device frontend" at this moment? All we have is what is described in the Wiki in the architecture specifications deliverable. One final comment: device frontend as a GE might cease to exist, as we are discsussing now about the streamlined architecture. Best regards, Tarek From: Farkas, Lorant (NSN - HU/Budapest) [mailto:lorant.farkas at nsn.com] Sent: 26 April 2012 07:22 To: Elsaleh T Mr (Electronic Eng); jakob.saros at ericsson.com Cc: fiware-iot at lists.fi-ware.eu Subject: RE: High-level description of Ericsson Gateway Hello Tarek, The action item is a bit outdated, device handler as GE will not exist under this name any more (pending on approval, of course). Last week we were discussing the issue that there is no owner for the device handler GE and device frontend GE. Payam volunteered to take a look at one of these GE. The additional issue with the device frontend is that the Ericsson asset (gateway asset) speaks a proprietary REST interface on the northbound, implemented by their http server and http-coap proxy, whereas on the backend there is noone to implement the component (earlier this was called device frontend) that discusses with the gateway over this interface. I think it was wrongly captured in the minutes that Payam volunteered to take a look at the device handler, I think he was meaning device frontend. In the new architecture both device frontend and device handler functionalitites should become part of the backend core functionalities GE, I think. The biggest question now is who will implement/specify backend core functionalities GE and your contribution would be welcome here from the frontend perspective because Telefonica will likely not have an interface that discusses with the Ericsson gateway. FYI we were announced yesterday that there is one person from Telefonica dedicated to IoT and also a team will be set up on their side. We will discuss with them next week Thursday or Friday and it would be good if you Tarek could also participate in this call, if you are interested in/can contribute to this GE. Including the alternative gateway middleware solution from your side requires further discussions, but the first step would be for you to share document describing the features and its availability as an asset. Thanks & Br, Lorant From: ext T.Elsaleh at surrey.ac.uk [mailto:T.Elsaleh at surrey.ac.uk] Sent: Wednesday, April 25, 2012 7:18 PM To: Farkas, Lorant (NSN - HU/Budapest); jakob.saros at ericsson.com Cc: fiware-iot at lists.fi-ware.eu Subject: RE: High-level description of Ericsson Gateway Hello Lorant, Jakob, I would like to follow up on the action point regarding: IoT04_18042012: "AP Payam to look at the GW description and check if USurrey could contribute to the Device Handler in the backend (open specs, implementation)." As I have been away last week, I would like to clarify what exactly is required here. UoS does have an alternative gateway middleware solution, but what is required exactly from us in order to contribute to the "Device Handler"? is it wrt "gateway-to-backend" (northbound) or "gateway-to-device" (southbound)? By the way, isn't the Device Handler GE in the Gateway? In terms of compatibility, is this with respect to CoAP, OSGi, or both? In either case, we currently don't support either of them, but can be considered for near future, as we are interested in using CoAP. Best regards, Tarek Tarek Elsaleh Research Assistant Centre for Commuication Systems Research (CCSR) Department of Electronic Engineering University of Surrey Guildford, GU2 7XH Tel: 01483 689485 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: 18 April 2012 13:06 To: fiware-iot at lists.fi-ware.eu Subject: [Fiware-iot] FW: High-level description of Ericsson Gateway Dear All, FYI (especially Payam/Tarek). Thanks & Br, Lorant From: ext Jakob Saros [mailto:jakob.saros at ericsson.com] Sent: Friday, April 13, 2012 6:15 PM To: Fici Gian Piero; Guerra Sabrina; thierry.nagellen at orange.com; Farkas, Lorant (NSN - HU/Budapest); Bisztray, Denes (NSN - HU/Budapest) Cc: Jan H?ller Subject: High-level description of Ericsson Gateway Hi, Attached is a description of the Ericsson Gateway for further discussions. Please note that this is a DRAFT! The document includes information of gateway components, i.e. OSGi bundles, and interfaces northbound/southbound. I look forward to hearing your comments. BR/Jakob ________________________________ No virus found in this message. Checked by AVG - www.avg.com Version: 2012.0.1913 / Virus Database: 2411/4948 - Release Date: 04/20/12 ________________________________ No virus found in this message. Checked by AVG - www.avg.com Version: 2012.0.1913 / Virus Database: 2411/4958 - Release Date: 04/25/12 -------------- next part -------------- An HTML attachment was scrubbed... URL: From denes.bisztray at nsn.com Fri Apr 27 14:02:44 2012 From: denes.bisztray at nsn.com (Bisztray, Denes (NSN - HU/Budapest)) Date: Fri, 27 Apr 2012 14:02:44 +0200 Subject: [Fiware-iot] IoT Chapter streamlined architecture Message-ID: <3F4C11BC54A36642BFB5875D599F47BD05D9C205@DEMUEXC013.nsn-intra.net> Dear All, We discussed the architecture with Juanjo and came to the conclusion with the attached result. The most important point was not to change agreements that were already discussed. Thus the following changes and observations have been made: - The Data Handling GE exposes an NGSI-10 interface as it did in the previous architecture as well. It is important not to lose such details with the streamlining. This NGSI-10 interface is connected to the Things Management GE making it possible for the things management to get direct NGSI event updates from the gateway. The functionality of the IoT Agent proposed by NEC on the backend seems to be delivered by the Data Handling GE. - The Device Data API will be a translation of ETSI M2M that makes the device data and device updates more useful for the Things Management GE. - All the components in the Things Management GE is untouched. They are simply in one GE. Hence, the previously external interfaces are internal parts from now on. (and thus not part of the Open Specification) - The two Core GEs are renamed to Gateway/Backend Device Management GE. Core GE would suggest that this GE is not replaceable. This is not true however. Official FIWARE does provide these elements, but the point of a GE is to be replacable by specific enablers. In case a UC project wants to replace them with solutions that uses EPC-Global, OGC SWE, etc, they can do it with connecting to the Things Management GE via the Device Data API. - We are not officially support IETF Core. We completely understand that currently the gateway does expose IETF Core and it needs to be translated, however, currently that is an implementation detail, and thus should not be part of the functional architecture. - The Pub/Sub broker from WP6 was missing from the architecture (as also raised by NEC) we added it without any change from the previous architecture. We will start a new branch on the private wiki with the new architecture. It is opened here: https://forge.fi-ware.eu/plugins/mediawiki/wiki/fi-ware-private/index.php/FiwareDeliverableStreamlinedD2.3IoT When the description is complete, we will switch. Best, D?nes From: ext Juanjo Hierro [mailto:jhierro at tid.es] Sent: Friday, April 27, 2012 1:32 PM To: Bisztray, Denes (NSN - HU/Budapest) Cc: Farkas, Lorant (NSN - HU/Budapest); Thierry.nagellen at orange-ftgroup.com; jhierro >> "Juan J. Hierro" Subject: Re: PLEASE READ Re: IoT Chapter streamlined architecture Gentlemen, Thank you for the VERY constructive discussion we have had. It would be great if you can circulate some sort of minutes of the discussion together with an updated version of the Architecture picture asap. It would be rather helpful in order to share with the rest of the IoT team and provide an starting for the necessary update of the Architecture description on the public wiki. Best regards, -- Juanjo ------------- Product Development and Innovation (PDI) - Telefonica Digital website: www.tid.es email: jhierro at tid.es twitter: twitter.com/JuanjoHierro FI-WARE (European Future Internet Core Platform) Chief Architect You can follow FI-WARE at: website: http://www.fi-ware.eu facebook: http://www.facebook.com/pages/FI-WARE/251366491587242 twitter: http://twitter.com/FIware linkedIn: http://www.linkedin.com/groups/FIWARE-4239932 On 27/04/12 11:41, Bisztray, Denes (NSN - HU/Budapest) wrote: We are available from 12:15. Thierry is on holiday so he will not join. Conference details: NSN Voice Conference information 58465 / 1628 Making a conference call France +33 17 061 7813 (PRIMARY) or +33 14 915 1553 Germany +49 89 5159 43800 Spain +349 1187 5929 Sweden +46 85 250 0862 (PRIMARY), +46 84 100 9299 Switzerland +41 44 279 7943 Webex details: Topic: Streamlined Architecture discussion Date: Friday, April 27, 2012 Time: 12:15 pm, Europe Summer Time (Berlin, GMT+02:00) Meeting Number: 709 636 546 Meeting Password: cool ------------------------------------------------------- To start the online meeting ------------------------------------------------------- 1. Go to https://nsn.webex.com/nsn/j.php?ED=210017087&UID=503765542&PW=NZTU4OTFlYWE5&RT=MiMyNQ%3D%3D 2. Log in to your account. 3. Click "Start Now". 4. Follow the instructions that appear on your screen. From: ext Juanjo Hierro [mailto:jhierro at tid.es] Sent: Friday, April 27, 2012 11:34 AM To: Bisztray, Denes (NSN - HU/Budapest) Cc: Farkas, Lorant (NSN - HU/Budapest); Thierry.nagellen at orange-ftgroup.com Subject: Re: PLEASE READ Re: IoT Chapter streamlined architecture Let's have the confcall at 12:00 and try to solve this out. Please circulate the bridge details. Best regards, -- Juanjo ------------- Product Development and Innovation (PDI) - Telefonica Digital website: www.tid.es email: jhierro at tid.es twitter: twitter.com/JuanjoHierro FI-WARE (European Future Internet Core Platform) Chief Architect You can follow FI-WARE at: website: http://www.fi-ware.eu facebook: http://www.facebook.com/pages/FI-WARE/251366491587242 twitter: http://twitter.com/FIware linkedIn: http://www.linkedin.com/groups/FIWARE-4239932 On 27/04/12 09:47, Bisztray, Denes (NSN - HU/Budapest) wrote: Dear Juanjo, Thanks for your long email and also your time for looking at the architecture properly. The topic is complex, if you don't mind I start in medias res. I noted you specific requests on changing names and connections, however these can be implemented only if we come to an agreement on the greater picture. As far as I understand your point (just to make sure we on the same line), you can imagine a backend without IoT resource-level functionality (since you don't think it is core functionality). This would work in such a way, that the gateway is working as a kind of cache, that collects data from the devices and then it publishes it towards the backend via NGSI. Then the backend Thing-level GE processes it. Unfortunately for me this model is not working for two reasons: 1. This possibly works only when there is one gateway and all the sensors of the world is connected to it. When you have multiple gateways, you need operation and management functionality towards the gateway which cannot be done via NGSI. In my opinion core functionality is such functionality that is extremely essential to the system. The scenario of having one gateway proves that the system may work without a resource-level component on the backend, but this extreme case is a bad example. In my opinion this is not what the gateway is designed for. 2. We discussed several times and agreed, and I'm unhappy that this topic comes up again, that the gateway is not a cache. Neither Ericsson, NSN or Orange agrees with this. If you have only NGSI functionality you not only cannot manage the gateways, but also you cannot perform FCAPS functionality on the devices themselves. NGSI cannot do this. - That extension interface is basically used for the Things Management GE to obtain direct resource-level information from the Core GE. Then the Things Management GE processes it. This is result of the original two-level exposure model. - I do not assume the Things Management GE to contain the resource-level resource-management functionality. That would make that GE a big monolith which we could may well call as IoT chapter GE. Also it is problematic that this OGC-gateway topic comes up again. We agreed that the gateway and backend communication should be standardized, and should not have a protocol adapter. We had an agreement for long time, I have no idea why you bring this topic up. We can have a confcall at 12:00, if you agree I send the conference details. Best, D?nes ________________________________ Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra pol?tica de env?o y recepci?n de correo electr?nico en el enlace situado m?s abajo. This message is intended exclusively for its addressee. We only send and receive email on the basis of the terms set out at. http://www.tid.es/ES/PAGINAS/disclaimer.aspx ________________________________ Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra pol?tica de env?o y recepci?n de correo electr?nico en el enlace situado m?s abajo. This message is intended exclusively for its addressee. We only send and receive email on the basis of the terms set out at. http://www.tid.es/ES/PAGINAS/disclaimer.aspx -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: IoT-Streamlined.graphml Type: application/octet-stream Size: 89959 bytes Desc: IoT-Streamlined.graphml URL: From lorant.farkas at nsn.com Fri Apr 27 14:23:35 2012 From: lorant.farkas at nsn.com (Farkas, Lorant (NSN - HU/Budapest)) Date: Fri, 27 Apr 2012 15:23:35 +0300 Subject: [Fiware-iot] IoT Chapter streamlined architecture In-Reply-To: <3F4C11BC54A36642BFB5875D599F47BD05D9C205@DEMUEXC013.nsn-intra.net> References: <3F4C11BC54A36642BFB5875D599F47BD05D9C205@DEMUEXC013.nsn-intra.net> Message-ID: <93D28BDF64839C468B848D14227151A2036C54D8@FIESEXC014.nsn-intra.net> Dear All, I would add that both me and D?nes are away during Monday and Tuesday (official holiday in Hungary). We would like to avoid wasting valuable time that you could contribute to implementing these changes because of lack of information/coordination. We are in a kind of hurry because the deadline of delivering M12 deliverables (Open Specs, Exploitation plans among them) is Monday. So if any of the partners have time/are not on holiday between now and the next weekly meeting, I would kindly ask to please contribute to the: 1. architecture/open specs deliverable: please don't hesitate to edit the new private wiki page (D2.3 streamlined, under the link by D?nes). The process could be the following: -put in the text from the old private wiki page D2.3 and correct in the text things that were updated in the architecture -put in the new graphml (the png generated from it) - we were discussing that we could keep just one diagram instead of the currently shown two and the internal details (connections between functional components inside the GE-s) would be shown only in the GE sub-wiki pages -start editing the GE-s themselves -Ericsson colleagues could start the gateway part, in particular the Gateway/Device Management part, Usurrey/Telecom Italia could also contribute there -NEC could work on the backend in the Things Management GE -Orange could contribute to the Data Handling GE part of the gateway 2. Exploitation deliverable: I created the placeholder for the sections per new GE under https://forge.fi-ware.eu/plugins/mediawiki/wiki/exploitation/index.php/Business_description_GE_Internet_of_Things (you can access this once you are logged in to the exploitation project in forge), the suggestion would be for the partners to take in hands the same GE-s as suggested in the previous point Thanks & Br, Lorant From: Bisztray, Denes (NSN - HU/Budapest) Sent: Friday, April 27, 2012 2:03 PM To: thierry.nagellen at orange.com; Farkas, Lorant (NSN - HU/Budapest); ext Juanjo Hierro; fiware-iot at lists.fi-ware.eu Cc: ext Tobias Jacobs Subject: IoT Chapter streamlined architecture Dear All, We discussed the architecture with Juanjo and came to the conclusion with the attached result. The most important point was not to change agreements that were already discussed. Thus the following changes and observations have been made: - The Data Handling GE exposes an NGSI-10 interface as it did in the previous architecture as well. It is important not to lose such details with the streamlining. This NGSI-10 interface is connected to the Things Management GE making it possible for the things management to get direct NGSI event updates from the gateway. The functionality of the IoT Agent proposed by NEC on the backend seems to be delivered by the Data Handling GE. - The Device Data API will be a translation of ETSI M2M that makes the device data and device updates more useful for the Things Management GE. - All the components in the Things Management GE is untouched. They are simply in one GE. Hence, the previously external interfaces are internal parts from now on. (and thus not part of the Open Specification) - The two Core GEs are renamed to Gateway/Backend Device Management GE. Core GE would suggest that this GE is not replaceable. This is not true however. Official FIWARE does provide these elements, but the point of a GE is to be replacable by specific enablers. In case a UC project wants to replace them with solutions that uses EPC-Global, OGC SWE, etc, they can do it with connecting to the Things Management GE via the Device Data API. - We are not officially support IETF Core. We completely understand that currently the gateway does expose IETF Core and it needs to be translated, however, currently that is an implementation detail, and thus should not be part of the functional architecture. - The Pub/Sub broker from WP6 was missing from the architecture (as also raised by NEC) we added it without any change from the previous architecture. We will start a new branch on the private wiki with the new architecture. It is opened here: https://forge.fi-ware.eu/plugins/mediawiki/wiki/fi-ware-private/index.php/FiwareDeliverableStreamlinedD2.3IoT When the description is complete, we will switch. Best, D?nes From: ext Juanjo Hierro [mailto:jhierro at tid.es] Sent: Friday, April 27, 2012 1:32 PM To: Bisztray, Denes (NSN - HU/Budapest) Cc: Farkas, Lorant (NSN - HU/Budapest); Thierry.nagellen at orange-ftgroup.com; jhierro >> "Juan J. Hierro" Subject: Re: PLEASE READ Re: IoT Chapter streamlined architecture Gentlemen, Thank you for the VERY constructive discussion we have had. It would be great if you can circulate some sort of minutes of the discussion together with an updated version of the Architecture picture asap. It would be rather helpful in order to share with the rest of the IoT team and provide an starting for the necessary update of the Architecture description on the public wiki. Best regards, -- Juanjo ------------- Product Development and Innovation (PDI) - Telefonica Digital website: www.tid.es email: jhierro at tid.es twitter: twitter.com/JuanjoHierro FI-WARE (European Future Internet Core Platform) Chief Architect You can follow FI-WARE at: website: http://www.fi-ware.eu facebook: http://www.facebook.com/pages/FI-WARE/251366491587242 twitter: http://twitter.com/FIware linkedIn: http://www.linkedin.com/groups/FIWARE-4239932 On 27/04/12 11:41, Bisztray, Denes (NSN - HU/Budapest) wrote: We are available from 12:15. Thierry is on holiday so he will not join. Conference details: NSN Voice Conference information 58465 / 1628 Making a conference call France +33 17 061 7813 (PRIMARY) or +33 14 915 1553 Germany +49 89 5159 43800 Spain +349 1187 5929 Sweden +46 85 250 0862 (PRIMARY), +46 84 100 9299 Switzerland +41 44 279 7943 Webex details: Topic: Streamlined Architecture discussion Date: Friday, April 27, 2012 Time: 12:15 pm, Europe Summer Time (Berlin, GMT+02:00) Meeting Number: 709 636 546 Meeting Password: cool ------------------------------------------------------- To start the online meeting ------------------------------------------------------- 1. Go to https://nsn.webex.com/nsn/j.php?ED=210017087&UID=503765542&PW=NZTU4OTFlYWE5&RT=MiMyNQ%3D%3D 2. Log in to your account. 3. Click "Start Now". 4. Follow the instructions that appear on your screen. From: ext Juanjo Hierro [mailto:jhierro at tid.es] Sent: Friday, April 27, 2012 11:34 AM To: Bisztray, Denes (NSN - HU/Budapest) Cc: Farkas, Lorant (NSN - HU/Budapest); Thierry.nagellen at orange-ftgroup.com Subject: Re: PLEASE READ Re: IoT Chapter streamlined architecture Let's have the confcall at 12:00 and try to solve this out. Please circulate the bridge details. Best regards, -- Juanjo ------------- Product Development and Innovation (PDI) - Telefonica Digital website: www.tid.es email: jhierro at tid.es twitter: twitter.com/JuanjoHierro FI-WARE (European Future Internet Core Platform) Chief Architect You can follow FI-WARE at: website: http://www.fi-ware.eu facebook: http://www.facebook.com/pages/FI-WARE/251366491587242 twitter: http://twitter.com/FIware linkedIn: http://www.linkedin.com/groups/FIWARE-4239932 On 27/04/12 09:47, Bisztray, Denes (NSN - HU/Budapest) wrote: Dear Juanjo, Thanks for your long email and also your time for looking at the architecture properly. The topic is complex, if you don't mind I start in medias res. I noted you specific requests on changing names and connections, however these can be implemented only if we come to an agreement on the greater picture. As far as I understand your point (just to make sure we on the same line), you can imagine a backend without IoT resource-level functionality (since you don't think it is core functionality). This would work in such a way, that the gateway is working as a kind of cache, that collects data from the devices and then it publishes it towards the backend via NGSI. Then the backend Thing-level GE processes it. Unfortunately for me this model is not working for two reasons: 1. This possibly works only when there is one gateway and all the sensors of the world is connected to it. When you have multiple gateways, you need operation and management functionality towards the gateway which cannot be done via NGSI. In my opinion core functionality is such functionality that is extremely essential to the system. The scenario of having one gateway proves that the system may work without a resource-level component on the backend, but this extreme case is a bad example. In my opinion this is not what the gateway is designed for. 2. We discussed several times and agreed, and I'm unhappy that this topic comes up again, that the gateway is not a cache. Neither Ericsson, NSN or Orange agrees with this. If you have only NGSI functionality you not only cannot manage the gateways, but also you cannot perform FCAPS functionality on the devices themselves. NGSI cannot do this. - That extension interface is basically used for the Things Management GE to obtain direct resource-level information from the Core GE. Then the Things Management GE processes it. This is result of the original two-level exposure model. - I do not assume the Things Management GE to contain the resource-level resource-management functionality. That would make that GE a big monolith which we could may well call as IoT chapter GE. Also it is problematic that this OGC-gateway topic comes up again. We agreed that the gateway and backend communication should be standardized, and should not have a protocol adapter. We had an agreement for long time, I have no idea why you bring this topic up. We can have a confcall at 12:00, if you agree I send the conference details. Best, D?nes ________________________________ Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra pol?tica de env?o y recepci?n de correo electr?nico en el enlace situado m?s abajo. This message is intended exclusively for its addressee. We only send and receive email on the basis of the terms set out at. http://www.tid.es/ES/PAGINAS/disclaimer.aspx ________________________________ Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra pol?tica de env?o y recepci?n de correo electr?nico en el enlace situado m?s abajo. This message is intended exclusively for its addressee. We only send and receive email on the basis of the terms set out at. http://www.tid.es/ES/PAGINAS/disclaimer.aspx -------------- next part -------------- An HTML attachment was scrubbed... URL: From Tobias.Jacobs at neclab.eu Fri Apr 27 14:48:25 2012 From: Tobias.Jacobs at neclab.eu (Tobias Jacobs) Date: Fri, 27 Apr 2012 12:48:25 +0000 Subject: [Fiware-iot] IoT Chapter streamlined architecture In-Reply-To: <3F4C11BC54A36642BFB5875D599F47BD05D9C205@DEMUEXC013.nsn-intra.net> References: <3F4C11BC54A36642BFB5875D599F47BD05D9C205@DEMUEXC013.nsn-intra.net> Message-ID: <8755F290097BD941865DC4245B335D2D08BCD99E@Polydeuces.office.hd> Hi all, As discussed in this week's phone conference, I added one box called "Thing-level Adapter" to the "things and resource management ge", which accounts for the fact that NGSI is the internal language between the components of the GE. See the attached file. Have a nice weekend! Tobias From: Bisztray, Denes (NSN - HU/Budapest) [mailto:denes.bisztray at nsn.com] Sent: Freitag, 27. April 2012 14:03 To: thierry.nagellen at orange.com; Farkas, Lorant (NSN - HU/Budapest); ext Juanjo Hierro; fiware-iot at lists.fi-ware.eu Cc: Tobias Jacobs Subject: IoT Chapter streamlined architecture Dear All, We discussed the architecture with Juanjo and came to the conclusion with the attached result. The most important point was not to change agreements that were already discussed. Thus the following changes and observations have been made: - The Data Handling GE exposes an NGSI-10 interface as it did in the previous architecture as well. It is important not to lose such details with the streamlining. This NGSI-10 interface is connected to the Things Management GE making it possible for the things management to get direct NGSI event updates from the gateway. The functionality of the IoT Agent proposed by NEC on the backend seems to be delivered by the Data Handling GE. - The Device Data API will be a translation of ETSI M2M that makes the device data and device updates more useful for the Things Management GE. - All the components in the Things Management GE is untouched. They are simply in one GE. Hence, the previously external interfaces are internal parts from now on. (and thus not part of the Open Specification) - The two Core GEs are renamed to Gateway/Backend Device Management GE. Core GE would suggest that this GE is not replaceable. This is not true however. Official FIWARE does provide these elements, but the point of a GE is to be replacable by specific enablers. In case a UC project wants to replace them with solutions that uses EPC-Global, OGC SWE, etc, they can do it with connecting to the Things Management GE via the Device Data API. - We are not officially support IETF Core. We completely understand that currently the gateway does expose IETF Core and it needs to be translated, however, currently that is an implementation detail, and thus should not be part of the functional architecture. - The Pub/Sub broker from WP6 was missing from the architecture (as also raised by NEC) we added it without any change from the previous architecture. We will start a new branch on the private wiki with the new architecture. It is opened here: https://forge.fi-ware.eu/plugins/mediawiki/wiki/fi-ware-private/index.php/FiwareDeliverableStreamlinedD2.3IoT When the description is complete, we will switch. Best, D?nes From: ext Juanjo Hierro [mailto:jhierro at tid.es] Sent: Friday, April 27, 2012 1:32 PM To: Bisztray, Denes (NSN - HU/Budapest) Cc: Farkas, Lorant (NSN - HU/Budapest); Thierry.nagellen at orange-ftgroup.com; jhierro >> "Juan J. Hierro" Subject: Re: PLEASE READ Re: IoT Chapter streamlined architecture Gentlemen, Thank you for the VERY constructive discussion we have had. It would be great if you can circulate some sort of minutes of the discussion together with an updated version of the Architecture picture asap. It would be rather helpful in order to share with the rest of the IoT team and provide an starting for the necessary update of the Architecture description on the public wiki. Best regards, -- Juanjo ------------- Product Development and Innovation (PDI) - Telefonica Digital website: www.tid.es email: jhierro at tid.es twitter: twitter.com/JuanjoHierro FI-WARE (European Future Internet Core Platform) Chief Architect You can follow FI-WARE at: website: http://www.fi-ware.eu facebook: http://www.facebook.com/pages/FI-WARE/251366491587242 twitter: http://twitter.com/FIware linkedIn: http://www.linkedin.com/groups/FIWARE-4239932 On 27/04/12 11:41, Bisztray, Denes (NSN - HU/Budapest) wrote: We are available from 12:15. Thierry is on holiday so he will not join. Conference details: NSN Voice Conference information 58465 / 1628 Making a conference call France +33 17 061 7813 (PRIMARY) or +33 14 915 1553 Germany +49 89 5159 43800 Spain +349 1187 5929 Sweden +46 85 250 0862 (PRIMARY), +46 84 100 9299 Switzerland +41 44 279 7943 Webex details: Topic: Streamlined Architecture discussion Date: Friday, April 27, 2012 Time: 12:15 pm, Europe Summer Time (Berlin, GMT+02:00) Meeting Number: 709 636 546 Meeting Password: cool ------------------------------------------------------- To start the online meeting ------------------------------------------------------- 1. Go to https://nsn.webex.com/nsn/j.php?ED=210017087&UID=503765542&PW=NZTU4OTFlYWE5&RT=MiMyNQ%3D%3D 2. Log in to your account. 3. Click "Start Now". 4. Follow the instructions that appear on your screen. From: ext Juanjo Hierro [mailto:jhierro at tid.es] Sent: Friday, April 27, 2012 11:34 AM To: Bisztray, Denes (NSN - HU/Budapest) Cc: Farkas, Lorant (NSN - HU/Budapest); Thierry.nagellen at orange-ftgroup.com Subject: Re: PLEASE READ Re: IoT Chapter streamlined architecture Let's have the confcall at 12:00 and try to solve this out. Please circulate the bridge details. Best regards, -- Juanjo ------------- Product Development and Innovation (PDI) - Telefonica Digital website: www.tid.es email: jhierro at tid.es twitter: twitter.com/JuanjoHierro FI-WARE (European Future Internet Core Platform) Chief Architect You can follow FI-WARE at: website: http://www.fi-ware.eu facebook: http://www.facebook.com/pages/FI-WARE/251366491587242 twitter: http://twitter.com/FIware linkedIn: http://www.linkedin.com/groups/FIWARE-4239932 On 27/04/12 09:47, Bisztray, Denes (NSN - HU/Budapest) wrote: Dear Juanjo, Thanks for your long email and also your time for looking at the architecture properly. The topic is complex, if you don't mind I start in medias res. I noted you specific requests on changing names and connections, however these can be implemented only if we come to an agreement on the greater picture. As far as I understand your point (just to make sure we on the same line), you can imagine a backend without IoT resource-level functionality (since you don't think it is core functionality). This would work in such a way, that the gateway is working as a kind of cache, that collects data from the devices and then it publishes it towards the backend via NGSI. Then the backend Thing-level GE processes it. Unfortunately for me this model is not working for two reasons: 1. This possibly works only when there is one gateway and all the sensors of the world is connected to it. When you have multiple gateways, you need operation and management functionality towards the gateway which cannot be done via NGSI. In my opinion core functionality is such functionality that is extremely essential to the system. The scenario of having one gateway proves that the system may work without a resource-level component on the backend, but this extreme case is a bad example. In my opinion this is not what the gateway is designed for. 2. We discussed several times and agreed, and I'm unhappy that this topic comes up again, that the gateway is not a cache. Neither Ericsson, NSN or Orange agrees with this. If you have only NGSI functionality you not only cannot manage the gateways, but also you cannot perform FCAPS functionality on the devices themselves. NGSI cannot do this. - That extension interface is basically used for the Things Management GE to obtain direct resource-level information from the Core GE. Then the Things Management GE processes it. This is result of the original two-level exposure model. - I do not assume the Things Management GE to contain the resource-level resource-management functionality. That would make that GE a big monolith which we could may well call as IoT chapter GE. Also it is problematic that this OGC-gateway topic comes up again. We agreed that the gateway and backend communication should be standardized, and should not have a protocol adapter. We had an agreement for long time, I have no idea why you bring this topic up. We can have a confcall at 12:00, if you agree I send the conference details. Best, D?nes ________________________________ Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra pol?tica de env?o y recepci?n de correo electr?nico en el enlace situado m?s abajo. This message is intended exclusively for its addressee. We only send and receive email on the basis of the terms set out at. http://www.tid.es/ES/PAGINAS/disclaimer.aspx ________________________________ Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra pol?tica de env?o y recepci?n de correo electr?nico en el enlace situado m?s abajo. This message is intended exclusively for its addressee. We only send and receive email on the basis of the terms set out at. http://www.tid.es/ES/PAGINAS/disclaimer.aspx -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: IoT-Streamlined_proposal.graphml Type: application/octet-stream Size: 91489 bytes Desc: IoT-Streamlined_proposal.graphml URL: From Tobias.Jacobs at neclab.eu Fri Apr 27 14:54:06 2012 From: Tobias.Jacobs at neclab.eu (Tobias Jacobs) Date: Fri, 27 Apr 2012 12:54:06 +0000 Subject: [Fiware-iot] IoT Chapter streamlined architecture In-Reply-To: <93D28BDF64839C468B848D14227151A2036C54D8@FIESEXC014.nsn-intra.net> References: <3F4C11BC54A36642BFB5875D599F47BD05D9C205@DEMUEXC013.nsn-intra.net> <93D28BDF64839C468B848D14227151A2036C54D8@FIESEXC014.nsn-intra.net> Message-ID: <8755F290097BD941865DC4245B335D2D08BCD9B7@Polydeuces.office.hd> Dear Lorant, all, I can put parts of a description of the Things&Resource Management GE into the wiki. However I do not know what the interface to the Backend Core is - so I do not really feel able to describe that API. Also I could have difficulties describing the aspects coming from Interference Engine - but maybe there are things I can copy and paste from the old descriptions. Best Tobias From: fiware-iot-bounces at lists.fi-ware.eu [mailto:fiware-iot-bounces at lists.fi-ware.eu] On Behalf Of Farkas, Lorant (NSN - HU/Budapest) Sent: Freitag, 27. April 2012 14:24 To: fiware-iot at lists.fi-ware.eu Subject: Re: [Fiware-iot] IoT Chapter streamlined architecture Dear All, I would add that both me and D?nes are away during Monday and Tuesday (official holiday in Hungary). We would like to avoid wasting valuable time that you could contribute to implementing these changes because of lack of information/coordination. We are in a kind of hurry because the deadline of delivering M12 deliverables (Open Specs, Exploitation plans among them) is Monday. So if any of the partners have time/are not on holiday between now and the next weekly meeting, I would kindly ask to please contribute to the: 1. architecture/open specs deliverable: please don't hesitate to edit the new private wiki page (D2.3 streamlined, under the link by D?nes). The process could be the following: -put in the text from the old private wiki page D2.3 and correct in the text things that were updated in the architecture -put in the new graphml (the png generated from it) - we were discussing that we could keep just one diagram instead of the currently shown two and the internal details (connections between functional components inside the GE-s) would be shown only in the GE sub-wiki pages -start editing the GE-s themselves -Ericsson colleagues could start the gateway part, in particular the Gateway/Device Management part, Usurrey/Telecom Italia could also contribute there -NEC could work on the backend in the Things Management GE -Orange could contribute to the Data Handling GE part of the gateway 2. Exploitation deliverable: I created the placeholder for the sections per new GE under https://forge.fi-ware.eu/plugins/mediawiki/wiki/exploitation/index.php/Business_description_GE_Internet_of_Things (you can access this once you are logged in to the exploitation project in forge), the suggestion would be for the partners to take in hands the same GE-s as suggested in the previous point Thanks & Br, Lorant From: Bisztray, Denes (NSN - HU/Budapest) Sent: Friday, April 27, 2012 2:03 PM To: thierry.nagellen at orange.com; Farkas, Lorant (NSN - HU/Budapest); ext Juanjo Hierro; fiware-iot at lists.fi-ware.eu Cc: ext Tobias Jacobs Subject: IoT Chapter streamlined architecture Dear All, We discussed the architecture with Juanjo and came to the conclusion with the attached result. The most important point was not to change agreements that were already discussed. Thus the following changes and observations have been made: - The Data Handling GE exposes an NGSI-10 interface as it did in the previous architecture as well. It is important not to lose such details with the streamlining. This NGSI-10 interface is connected to the Things Management GE making it possible for the things management to get direct NGSI event updates from the gateway. The functionality of the IoT Agent proposed by NEC on the backend seems to be delivered by the Data Handling GE. - The Device Data API will be a translation of ETSI M2M that makes the device data and device updates more useful for the Things Management GE. - All the components in the Things Management GE is untouched. They are simply in one GE. Hence, the previously external interfaces are internal parts from now on. (and thus not part of the Open Specification) - The two Core GEs are renamed to Gateway/Backend Device Management GE. Core GE would suggest that this GE is not replaceable. This is not true however. Official FIWARE does provide these elements, but the point of a GE is to be replacable by specific enablers. In case a UC project wants to replace them with solutions that uses EPC-Global, OGC SWE, etc, they can do it with connecting to the Things Management GE via the Device Data API. - We are not officially support IETF Core. We completely understand that currently the gateway does expose IETF Core and it needs to be translated, however, currently that is an implementation detail, and thus should not be part of the functional architecture. - The Pub/Sub broker from WP6 was missing from the architecture (as also raised by NEC) we added it without any change from the previous architecture. We will start a new branch on the private wiki with the new architecture. It is opened here: https://forge.fi-ware.eu/plugins/mediawiki/wiki/fi-ware-private/index.php/FiwareDeliverableStreamlinedD2.3IoT When the description is complete, we will switch. Best, D?nes From: ext Juanjo Hierro [mailto:jhierro at tid.es] Sent: Friday, April 27, 2012 1:32 PM To: Bisztray, Denes (NSN - HU/Budapest) Cc: Farkas, Lorant (NSN - HU/Budapest); Thierry.nagellen at orange-ftgroup.com; jhierro >> "Juan J. Hierro" Subject: Re: PLEASE READ Re: IoT Chapter streamlined architecture Gentlemen, Thank you for the VERY constructive discussion we have had. It would be great if you can circulate some sort of minutes of the discussion together with an updated version of the Architecture picture asap. It would be rather helpful in order to share with the rest of the IoT team and provide an starting for the necessary update of the Architecture description on the public wiki. Best regards, -- Juanjo ------------- Product Development and Innovation (PDI) - Telefonica Digital website: www.tid.es email: jhierro at tid.es twitter: twitter.com/JuanjoHierro FI-WARE (European Future Internet Core Platform) Chief Architect You can follow FI-WARE at: website: http://www.fi-ware.eu facebook: http://www.facebook.com/pages/FI-WARE/251366491587242 twitter: http://twitter.com/FIware linkedIn: http://www.linkedin.com/groups/FIWARE-4239932 On 27/04/12 11:41, Bisztray, Denes (NSN - HU/Budapest) wrote: We are available from 12:15. Thierry is on holiday so he will not join. Conference details: NSN Voice Conference information 58465 / 1628 Making a conference call France +33 17 061 7813 (PRIMARY) or +33 14 915 1553 Germany +49 89 5159 43800 Spain +349 1187 5929 Sweden +46 85 250 0862 (PRIMARY), +46 84 100 9299 Switzerland +41 44 279 7943 Webex details: Topic: Streamlined Architecture discussion Date: Friday, April 27, 2012 Time: 12:15 pm, Europe Summer Time (Berlin, GMT+02:00) Meeting Number: 709 636 546 Meeting Password: cool ------------------------------------------------------- To start the online meeting ------------------------------------------------------- 1. Go to https://nsn.webex.com/nsn/j.php?ED=210017087&UID=503765542&PW=NZTU4OTFlYWE5&RT=MiMyNQ%3D%3D 2. Log in to your account. 3. Click "Start Now". 4. Follow the instructions that appear on your screen. From: ext Juanjo Hierro [mailto:jhierro at tid.es] Sent: Friday, April 27, 2012 11:34 AM To: Bisztray, Denes (NSN - HU/Budapest) Cc: Farkas, Lorant (NSN - HU/Budapest); Thierry.nagellen at orange-ftgroup.com Subject: Re: PLEASE READ Re: IoT Chapter streamlined architecture Let's have the confcall at 12:00 and try to solve this out. Please circulate the bridge details. Best regards, -- Juanjo ------------- Product Development and Innovation (PDI) - Telefonica Digital website: www.tid.es email: jhierro at tid.es twitter: twitter.com/JuanjoHierro FI-WARE (European Future Internet Core Platform) Chief Architect You can follow FI-WARE at: website: http://www.fi-ware.eu facebook: http://www.facebook.com/pages/FI-WARE/251366491587242 twitter: http://twitter.com/FIware linkedIn: http://www.linkedin.com/groups/FIWARE-4239932 On 27/04/12 09:47, Bisztray, Denes (NSN - HU/Budapest) wrote: Dear Juanjo, Thanks for your long email and also your time for looking at the architecture properly. The topic is complex, if you don't mind I start in medias res. I noted you specific requests on changing names and connections, however these can be implemented only if we come to an agreement on the greater picture. As far as I understand your point (just to make sure we on the same line), you can imagine a backend without IoT resource-level functionality (since you don't think it is core functionality). This would work in such a way, that the gateway is working as a kind of cache, that collects data from the devices and then it publishes it towards the backend via NGSI. Then the backend Thing-level GE processes it. Unfortunately for me this model is not working for two reasons: 1. This possibly works only when there is one gateway and all the sensors of the world is connected to it. When you have multiple gateways, you need operation and management functionality towards the gateway which cannot be done via NGSI. In my opinion core functionality is such functionality that is extremely essential to the system. The scenario of having one gateway proves that the system may work without a resource-level component on the backend, but this extreme case is a bad example. In my opinion this is not what the gateway is designed for. 2. We discussed several times and agreed, and I'm unhappy that this topic comes up again, that the gateway is not a cache. Neither Ericsson, NSN or Orange agrees with this. If you have only NGSI functionality you not only cannot manage the gateways, but also you cannot perform FCAPS functionality on the devices themselves. NGSI cannot do this. - That extension interface is basically used for the Things Management GE to obtain direct resource-level information from the Core GE. Then the Things Management GE processes it. This is result of the original two-level exposure model. - I do not assume the Things Management GE to contain the resource-level resource-management functionality. That would make that GE a big monolith which we could may well call as IoT chapter GE. Also it is problematic that this OGC-gateway topic comes up again. We agreed that the gateway and backend communication should be standardized, and should not have a protocol adapter. We had an agreement for long time, I have no idea why you bring this topic up. We can have a confcall at 12:00, if you agree I send the conference details. Best, D?nes ________________________________ Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra pol?tica de env?o y recepci?n de correo electr?nico en el enlace situado m?s abajo. This message is intended exclusively for its addressee. We only send and receive email on the basis of the terms set out at. http://www.tid.es/ES/PAGINAS/disclaimer.aspx ________________________________ Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra pol?tica de env?o y recepci?n de correo electr?nico en el enlace situado m?s abajo. This message is intended exclusively for its addressee. We only send and receive email on the basis of the terms set out at. http://www.tid.es/ES/PAGINAS/disclaimer.aspx -------------- next part -------------- An HTML attachment was scrubbed... URL: From denes.bisztray at nsn.com Fri Apr 27 14:56:46 2012 From: denes.bisztray at nsn.com (Bisztray, Denes (NSN - HU/Budapest)) Date: Fri, 27 Apr 2012 14:56:46 +0200 Subject: [Fiware-iot] IoT Chapter streamlined architecture In-Reply-To: <8755F290097BD941865DC4245B335D2D08BCD9B7@Polydeuces.office.hd> References: <3F4C11BC54A36642BFB5875D599F47BD05D9C205@DEMUEXC013.nsn-intra.net> <93D28BDF64839C468B848D14227151A2036C54D8@FIESEXC014.nsn-intra.net> <8755F290097BD941865DC4245B335D2D08BCD9B7@Polydeuces.office.hd> Message-ID: <3F4C11BC54A36642BFB5875D599F47BD05D9C255@DEMUEXC013.nsn-intra.net> Yes, copying and organising is fine. If you have time, it would be nice if you could create an FMC for the Things Management GE unified from the previous participant GEs. Best, D?nes From: fiware-iot-bounces at lists.fi-ware.eu [mailto:fiware-iot-bounces at lists.fi-ware.eu] On Behalf Of ext Tobias Jacobs Sent: Friday, April 27, 2012 2:54 PM To: Farkas, Lorant (NSN - HU/Budapest); fiware-iot at lists.fi-ware.eu Subject: Re: [Fiware-iot] IoT Chapter streamlined architecture Dear Lorant, all, I can put parts of a description of the Things&Resource Management GE into the wiki. However I do not know what the interface to the Backend Core is - so I do not really feel able to describe that API. Also I could have difficulties describing the aspects coming from Interference Engine - but maybe there are things I can copy and paste from the old descriptions. Best Tobias From: fiware-iot-bounces at lists.fi-ware.eu [mailto:fiware-iot-bounces at lists.fi-ware.eu] On Behalf Of Farkas, Lorant (NSN - HU/Budapest) Sent: Freitag, 27. April 2012 14:24 To: fiware-iot at lists.fi-ware.eu Subject: Re: [Fiware-iot] IoT Chapter streamlined architecture Dear All, I would add that both me and D?nes are away during Monday and Tuesday (official holiday in Hungary). We would like to avoid wasting valuable time that you could contribute to implementing these changes because of lack of information/coordination. We are in a kind of hurry because the deadline of delivering M12 deliverables (Open Specs, Exploitation plans among them) is Monday. So if any of the partners have time/are not on holiday between now and the next weekly meeting, I would kindly ask to please contribute to the: 1. architecture/open specs deliverable: please don't hesitate to edit the new private wiki page (D2.3 streamlined, under the link by D?nes). The process could be the following: -put in the text from the old private wiki page D2.3 and correct in the text things that were updated in the architecture -put in the new graphml (the png generated from it) - we were discussing that we could keep just one diagram instead of the currently shown two and the internal details (connections between functional components inside the GE-s) would be shown only in the GE sub-wiki pages -start editing the GE-s themselves -Ericsson colleagues could start the gateway part, in particular the Gateway/Device Management part, Usurrey/Telecom Italia could also contribute there -NEC could work on the backend in the Things Management GE -Orange could contribute to the Data Handling GE part of the gateway 2. Exploitation deliverable: I created the placeholder for the sections per new GE under https://forge.fi-ware.eu/plugins/mediawiki/wiki/exploitation/index.php/Business_description_GE_Internet_of_Things (you can access this once you are logged in to the exploitation project in forge), the suggestion would be for the partners to take in hands the same GE-s as suggested in the previous point Thanks & Br, Lorant From: Bisztray, Denes (NSN - HU/Budapest) Sent: Friday, April 27, 2012 2:03 PM To: thierry.nagellen at orange.com; Farkas, Lorant (NSN - HU/Budapest); ext Juanjo Hierro; fiware-iot at lists.fi-ware.eu Cc: ext Tobias Jacobs Subject: IoT Chapter streamlined architecture Dear All, We discussed the architecture with Juanjo and came to the conclusion with the attached result. The most important point was not to change agreements that were already discussed. Thus the following changes and observations have been made: - The Data Handling GE exposes an NGSI-10 interface as it did in the previous architecture as well. It is important not to lose such details with the streamlining. This NGSI-10 interface is connected to the Things Management GE making it possible for the things management to get direct NGSI event updates from the gateway. The functionality of the IoT Agent proposed by NEC on the backend seems to be delivered by the Data Handling GE. - The Device Data API will be a translation of ETSI M2M that makes the device data and device updates more useful for the Things Management GE. - All the components in the Things Management GE is untouched. They are simply in one GE. Hence, the previously external interfaces are internal parts from now on. (and thus not part of the Open Specification) - The two Core GEs are renamed to Gateway/Backend Device Management GE. Core GE would suggest that this GE is not replaceable. This is not true however. Official FIWARE does provide these elements, but the point of a GE is to be replacable by specific enablers. In case a UC project wants to replace them with solutions that uses EPC-Global, OGC SWE, etc, they can do it with connecting to the Things Management GE via the Device Data API. - We are not officially support IETF Core. We completely understand that currently the gateway does expose IETF Core and it needs to be translated, however, currently that is an implementation detail, and thus should not be part of the functional architecture. - The Pub/Sub broker from WP6 was missing from the architecture (as also raised by NEC) we added it without any change from the previous architecture. We will start a new branch on the private wiki with the new architecture. It is opened here: https://forge.fi-ware.eu/plugins/mediawiki/wiki/fi-ware-private/index.php/FiwareDeliverableStreamlinedD2.3IoT When the description is complete, we will switch. Best, D?nes From: ext Juanjo Hierro [mailto:jhierro at tid.es] Sent: Friday, April 27, 2012 1:32 PM To: Bisztray, Denes (NSN - HU/Budapest) Cc: Farkas, Lorant (NSN - HU/Budapest); Thierry.nagellen at orange-ftgroup.com; jhierro >> "Juan J. Hierro" Subject: Re: PLEASE READ Re: IoT Chapter streamlined architecture Gentlemen, Thank you for the VERY constructive discussion we have had. It would be great if you can circulate some sort of minutes of the discussion together with an updated version of the Architecture picture asap. It would be rather helpful in order to share with the rest of the IoT team and provide an starting for the necessary update of the Architecture description on the public wiki. Best regards, -- Juanjo ------------- Product Development and Innovation (PDI) - Telefonica Digital website: www.tid.es email: jhierro at tid.es twitter: twitter.com/JuanjoHierro FI-WARE (European Future Internet Core Platform) Chief Architect You can follow FI-WARE at: website: http://www.fi-ware.eu facebook: http://www.facebook.com/pages/FI-WARE/251366491587242 twitter: http://twitter.com/FIware linkedIn: http://www.linkedin.com/groups/FIWARE-4239932 On 27/04/12 11:41, Bisztray, Denes (NSN - HU/Budapest) wrote: We are available from 12:15. Thierry is on holiday so he will not join. Conference details: NSN Voice Conference information 58465 / 1628 Making a conference call France +33 17 061 7813 (PRIMARY) or +33 14 915 1553 Germany +49 89 5159 43800 Spain +349 1187 5929 Sweden +46 85 250 0862 (PRIMARY), +46 84 100 9299 Switzerland +41 44 279 7943 Webex details: Topic: Streamlined Architecture discussion Date: Friday, April 27, 2012 Time: 12:15 pm, Europe Summer Time (Berlin, GMT+02:00) Meeting Number: 709 636 546 Meeting Password: cool ------------------------------------------------------- To start the online meeting ------------------------------------------------------- 1. Go to https://nsn.webex.com/nsn/j.php?ED=210017087&UID=503765542&PW=NZTU4OTFlYWE5&RT=MiMyNQ%3D%3D 2. Log in to your account. 3. Click "Start Now". 4. Follow the instructions that appear on your screen. From: ext Juanjo Hierro [mailto:jhierro at tid.es] Sent: Friday, April 27, 2012 11:34 AM To: Bisztray, Denes (NSN - HU/Budapest) Cc: Farkas, Lorant (NSN - HU/Budapest); Thierry.nagellen at orange-ftgroup.com Subject: Re: PLEASE READ Re: IoT Chapter streamlined architecture Let's have the confcall at 12:00 and try to solve this out. Please circulate the bridge details. Best regards, -- Juanjo ------------- Product Development and Innovation (PDI) - Telefonica Digital website: www.tid.es email: jhierro at tid.es twitter: twitter.com/JuanjoHierro FI-WARE (European Future Internet Core Platform) Chief Architect You can follow FI-WARE at: website: http://www.fi-ware.eu facebook: http://www.facebook.com/pages/FI-WARE/251366491587242 twitter: http://twitter.com/FIware linkedIn: http://www.linkedin.com/groups/FIWARE-4239932 On 27/04/12 09:47, Bisztray, Denes (NSN - HU/Budapest) wrote: Dear Juanjo, Thanks for your long email and also your time for looking at the architecture properly. The topic is complex, if you don't mind I start in medias res. I noted you specific requests on changing names and connections, however these can be implemented only if we come to an agreement on the greater picture. As far as I understand your point (just to make sure we on the same line), you can imagine a backend without IoT resource-level functionality (since you don't think it is core functionality). This would work in such a way, that the gateway is working as a kind of cache, that collects data from the devices and then it publishes it towards the backend via NGSI. Then the backend Thing-level GE processes it. Unfortunately for me this model is not working for two reasons: 1. This possibly works only when there is one gateway and all the sensors of the world is connected to it. When you have multiple gateways, you need operation and management functionality towards the gateway which cannot be done via NGSI. In my opinion core functionality is such functionality that is extremely essential to the system. The scenario of having one gateway proves that the system may work without a resource-level component on the backend, but this extreme case is a bad example. In my opinion this is not what the gateway is designed for. 2. We discussed several times and agreed, and I'm unhappy that this topic comes up again, that the gateway is not a cache. Neither Ericsson, NSN or Orange agrees with this. If you have only NGSI functionality you not only cannot manage the gateways, but also you cannot perform FCAPS functionality on the devices themselves. NGSI cannot do this. - That extension interface is basically used for the Things Management GE to obtain direct resource-level information from the Core GE. Then the Things Management GE processes it. This is result of the original two-level exposure model. - I do not assume the Things Management GE to contain the resource-level resource-management functionality. That would make that GE a big monolith which we could may well call as IoT chapter GE. Also it is problematic that this OGC-gateway topic comes up again. We agreed that the gateway and backend communication should be standardized, and should not have a protocol adapter. We had an agreement for long time, I have no idea why you bring this topic up. We can have a confcall at 12:00, if you agree I send the conference details. Best, D?nes ________________________________ Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra pol?tica de env?o y recepci?n de correo electr?nico en el enlace situado m?s abajo. This message is intended exclusively for its addressee. We only send and receive email on the basis of the terms set out at. http://www.tid.es/ES/PAGINAS/disclaimer.aspx ________________________________ Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra pol?tica de env?o y recepci?n de correo electr?nico en el enlace situado m?s abajo. This message is intended exclusively for its addressee. We only send and receive email on the basis of the terms set out at. http://www.tid.es/ES/PAGINAS/disclaimer.aspx -------------- next part -------------- An HTML attachment was scrubbed... URL: From lorant.farkas at nsn.com Fri Apr 27 14:57:45 2012 From: lorant.farkas at nsn.com (Farkas, Lorant (NSN - HU/Budapest)) Date: Fri, 27 Apr 2012 15:57:45 +0300 Subject: [Fiware-iot] IoT weekly meeting Message-ID: <93D28BDF64839C468B848D14227151A2036C5524@FIESEXC014.nsn-intra.net> When: 2012. m?jus 2. 10:00-11:30 (GMT+01:00) Belgrade, Bratislava, Budapest, Ljubljana, Prague. Where: telco/webex (new PIN: 1628) Note: The GMT offset above does not reflect daylight saving time adjustments. *~*~*~*~*~*~*~*~*~* Dear All, We propose the following topics for our next meeting: 1. Architecture revisited: final polishing, report on our discussions with the chief architect 2. NGSI: NSN would give you a short demo on the implementation we have and we could have an update on the status of the specifications 3. Educational sessions: start discussing about the content of the presentations 4. M12 deliverables (exploitation plan, open specifications): status update Thanks & Br, Lorant Update on all instances to reflect the change in the PIN code (will change every 6 months, unfortunately). Dear All, Let's resume our weekly meeting starting from next week in the usual day/time, which is Wednesday, 10:00 AM (CET) to 11:30. Either WPL or WPA will be present to host the meeting. In case we find good reason to skip the meeting, then we will skip it, but I propose not to deviate from this slot. Thanks & Br, Lorant Topic: IOT WP weekly Date: Every Wednesday, from Wednesday, 10 August 2011 to Wednesday, 26 March 2014 Time: 10:00, Europe Summer Time (Paris, GMT+02:00) Meeting Number: 709 472 921 Meeting Password: FI-WARE ------------------------------------------------------- To join the online meeting ------------------------------------------------------- 1. Go to https://nsn.webex.com/nsn/j.php?ED=175018962&UID=0&PW=NYzEzYWM0ZTNk&RT=MTgjMjM%3D 2. Enter your name and email address. 3. Enter the meeting password: FI-WARE 4. Click "Join Now". 5. Follow the instructions that appear on your screen. 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 New PIN: 9369002 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 https://inside.nokiasiemensnetworks.com/global/MyServices/IT/Infrastructure_Services/RealTimeCommunication/VoiceService/NSNVoiceConference/MakingaCall/LocalAccessNumbers/Pages/Outofofficenumbers.aspx. 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 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: 10817 bytes Desc: not available URL: From Tobias.Jacobs at neclab.eu Fri Apr 27 14:59:11 2012 From: Tobias.Jacobs at neclab.eu (Tobias Jacobs) Date: Fri, 27 Apr 2012 12:59:11 +0000 Subject: [Fiware-iot] IoT Chapter streamlined architecture In-Reply-To: <3F4C11BC54A36642BFB5875D599F47BD05D9C255@DEMUEXC013.nsn-intra.net> References: <3F4C11BC54A36642BFB5875D599F47BD05D9C205@DEMUEXC013.nsn-intra.net> <93D28BDF64839C468B848D14227151A2036C54D8@FIESEXC014.nsn-intra.net> <8755F290097BD941865DC4245B335D2D08BCD9B7@Polydeuces.office.hd> <3F4C11BC54A36642BFB5875D599F47BD05D9C255@DEMUEXC013.nsn-intra.net> Message-ID: <8755F290097BD941865DC4245B335D2D08BCD9D8@Polydeuces.office.hd> it would be nice if you could create an FMC for the Things Management GE unified from the previous participant GEs. Do you mean an internal architecture of the GE? OK, I can try to do that, although I might have some question marks. Best Tobias From: Bisztray, Denes (NSN - HU/Budapest) [mailto:denes.bisztray at nsn.com] Sent: Freitag, 27. April 2012 14:57 To: Tobias Jacobs; Farkas, Lorant (NSN - HU/Budapest); fiware-iot at lists.fi-ware.eu Subject: RE: [Fiware-iot] IoT Chapter streamlined architecture Yes, copying and organising is fine. If you have time, it would be nice if you could create an FMC for the Things Management GE unified from the previous participant GEs. Best, D?nes From: fiware-iot-bounces at lists.fi-ware.eu [mailto:fiware-iot-bounces at lists.fi-ware.eu] On Behalf Of ext Tobias Jacobs Sent: Friday, April 27, 2012 2:54 PM To: Farkas, Lorant (NSN - HU/Budapest); fiware-iot at lists.fi-ware.eu Subject: Re: [Fiware-iot] IoT Chapter streamlined architecture Dear Lorant, all, I can put parts of a description of the Things&Resource Management GE into the wiki. However I do not know what the interface to the Backend Core is - so I do not really feel able to describe that API. Also I could have difficulties describing the aspects coming from Interference Engine - but maybe there are things I can copy and paste from the old descriptions. Best Tobias From: fiware-iot-bounces at lists.fi-ware.eu [mailto:fiware-iot-bounces at lists.fi-ware.eu] On Behalf Of Farkas, Lorant (NSN - HU/Budapest) Sent: Freitag, 27. April 2012 14:24 To: fiware-iot at lists.fi-ware.eu Subject: Re: [Fiware-iot] IoT Chapter streamlined architecture Dear All, I would add that both me and D?nes are away during Monday and Tuesday (official holiday in Hungary). We would like to avoid wasting valuable time that you could contribute to implementing these changes because of lack of information/coordination. We are in a kind of hurry because the deadline of delivering M12 deliverables (Open Specs, Exploitation plans among them) is Monday. So if any of the partners have time/are not on holiday between now and the next weekly meeting, I would kindly ask to please contribute to the: 1. architecture/open specs deliverable: please don't hesitate to edit the new private wiki page (D2.3 streamlined, under the link by D?nes). The process could be the following: -put in the text from the old private wiki page D2.3 and correct in the text things that were updated in the architecture -put in the new graphml (the png generated from it) - we were discussing that we could keep just one diagram instead of the currently shown two and the internal details (connections between functional components inside the GE-s) would be shown only in the GE sub-wiki pages -start editing the GE-s themselves -Ericsson colleagues could start the gateway part, in particular the Gateway/Device Management part, Usurrey/Telecom Italia could also contribute there -NEC could work on the backend in the Things Management GE -Orange could contribute to the Data Handling GE part of the gateway 2. Exploitation deliverable: I created the placeholder for the sections per new GE under https://forge.fi-ware.eu/plugins/mediawiki/wiki/exploitation/index.php/Business_description_GE_Internet_of_Things (you can access this once you are logged in to the exploitation project in forge), the suggestion would be for the partners to take in hands the same GE-s as suggested in the previous point Thanks & Br, Lorant From: Bisztray, Denes (NSN - HU/Budapest) Sent: Friday, April 27, 2012 2:03 PM To: thierry.nagellen at orange.com; Farkas, Lorant (NSN - HU/Budapest); ext Juanjo Hierro; fiware-iot at lists.fi-ware.eu Cc: ext Tobias Jacobs Subject: IoT Chapter streamlined architecture Dear All, We discussed the architecture with Juanjo and came to the conclusion with the attached result. The most important point was not to change agreements that were already discussed. Thus the following changes and observations have been made: - The Data Handling GE exposes an NGSI-10 interface as it did in the previous architecture as well. It is important not to lose such details with the streamlining. This NGSI-10 interface is connected to the Things Management GE making it possible for the things management to get direct NGSI event updates from the gateway. The functionality of the IoT Agent proposed by NEC on the backend seems to be delivered by the Data Handling GE. - The Device Data API will be a translation of ETSI M2M that makes the device data and device updates more useful for the Things Management GE. - All the components in the Things Management GE is untouched. They are simply in one GE. Hence, the previously external interfaces are internal parts from now on. (and thus not part of the Open Specification) - The two Core GEs are renamed to Gateway/Backend Device Management GE. Core GE would suggest that this GE is not replaceable. This is not true however. Official FIWARE does provide these elements, but the point of a GE is to be replacable by specific enablers. In case a UC project wants to replace them with solutions that uses EPC-Global, OGC SWE, etc, they can do it with connecting to the Things Management GE via the Device Data API. - We are not officially support IETF Core. We completely understand that currently the gateway does expose IETF Core and it needs to be translated, however, currently that is an implementation detail, and thus should not be part of the functional architecture. - The Pub/Sub broker from WP6 was missing from the architecture (as also raised by NEC) we added it without any change from the previous architecture. We will start a new branch on the private wiki with the new architecture. It is opened here: https://forge.fi-ware.eu/plugins/mediawiki/wiki/fi-ware-private/index.php/FiwareDeliverableStreamlinedD2.3IoT When the description is complete, we will switch. Best, D?nes From: ext Juanjo Hierro [mailto:jhierro at tid.es] Sent: Friday, April 27, 2012 1:32 PM To: Bisztray, Denes (NSN - HU/Budapest) Cc: Farkas, Lorant (NSN - HU/Budapest); Thierry.nagellen at orange-ftgroup.com; jhierro >> "Juan J. Hierro" Subject: Re: PLEASE READ Re: IoT Chapter streamlined architecture Gentlemen, Thank you for the VERY constructive discussion we have had. It would be great if you can circulate some sort of minutes of the discussion together with an updated version of the Architecture picture asap. It would be rather helpful in order to share with the rest of the IoT team and provide an starting for the necessary update of the Architecture description on the public wiki. Best regards, -- Juanjo ------------- Product Development and Innovation (PDI) - Telefonica Digital website: www.tid.es email: jhierro at tid.es twitter: twitter.com/JuanjoHierro FI-WARE (European Future Internet Core Platform) Chief Architect You can follow FI-WARE at: website: http://www.fi-ware.eu facebook: http://www.facebook.com/pages/FI-WARE/251366491587242 twitter: http://twitter.com/FIware linkedIn: http://www.linkedin.com/groups/FIWARE-4239932 On 27/04/12 11:41, Bisztray, Denes (NSN - HU/Budapest) wrote: We are available from 12:15. Thierry is on holiday so he will not join. Conference details: NSN Voice Conference information 58465 / 1628 Making a conference call France +33 17 061 7813 (PRIMARY) or +33 14 915 1553 Germany +49 89 5159 43800 Spain +349 1187 5929 Sweden +46 85 250 0862 (PRIMARY), +46 84 100 9299 Switzerland +41 44 279 7943 Webex details: Topic: Streamlined Architecture discussion Date: Friday, April 27, 2012 Time: 12:15 pm, Europe Summer Time (Berlin, GMT+02:00) Meeting Number: 709 636 546 Meeting Password: cool ------------------------------------------------------- To start the online meeting ------------------------------------------------------- 1. Go to https://nsn.webex.com/nsn/j.php?ED=210017087&UID=503765542&PW=NZTU4OTFlYWE5&RT=MiMyNQ%3D%3D 2. Log in to your account. 3. Click "Start Now". 4. Follow the instructions that appear on your screen. From: ext Juanjo Hierro [mailto:jhierro at tid.es] Sent: Friday, April 27, 2012 11:34 AM To: Bisztray, Denes (NSN - HU/Budapest) Cc: Farkas, Lorant (NSN - HU/Budapest); Thierry.nagellen at orange-ftgroup.com Subject: Re: PLEASE READ Re: IoT Chapter streamlined architecture Let's have the confcall at 12:00 and try to solve this out. Please circulate the bridge details. Best regards, -- Juanjo ------------- Product Development and Innovation (PDI) - Telefonica Digital website: www.tid.es email: jhierro at tid.es twitter: twitter.com/JuanjoHierro FI-WARE (European Future Internet Core Platform) Chief Architect You can follow FI-WARE at: website: http://www.fi-ware.eu facebook: http://www.facebook.com/pages/FI-WARE/251366491587242 twitter: http://twitter.com/FIware linkedIn: http://www.linkedin.com/groups/FIWARE-4239932 On 27/04/12 09:47, Bisztray, Denes (NSN - HU/Budapest) wrote: Dear Juanjo, Thanks for your long email and also your time for looking at the architecture properly. The topic is complex, if you don't mind I start in medias res. I noted you specific requests on changing names and connections, however these can be implemented only if we come to an agreement on the greater picture. As far as I understand your point (just to make sure we on the same line), you can imagine a backend without IoT resource-level functionality (since you don't think it is core functionality). This would work in such a way, that the gateway is working as a kind of cache, that collects data from the devices and then it publishes it towards the backend via NGSI. Then the backend Thing-level GE processes it. Unfortunately for me this model is not working for two reasons: 1. This possibly works only when there is one gateway and all the sensors of the world is connected to it. When you have multiple gateways, you need operation and management functionality towards the gateway which cannot be done via NGSI. In my opinion core functionality is such functionality that is extremely essential to the system. The scenario of having one gateway proves that the system may work without a resource-level component on the backend, but this extreme case is a bad example. In my opinion this is not what the gateway is designed for. 2. We discussed several times and agreed, and I'm unhappy that this topic comes up again, that the gateway is not a cache. Neither Ericsson, NSN or Orange agrees with this. If you have only NGSI functionality you not only cannot manage the gateways, but also you cannot perform FCAPS functionality on the devices themselves. NGSI cannot do this. - That extension interface is basically used for the Things Management GE to obtain direct resource-level information from the Core GE. Then the Things Management GE processes it. This is result of the original two-level exposure model. - I do not assume the Things Management GE to contain the resource-level resource-management functionality. That would make that GE a big monolith which we could may well call as IoT chapter GE. Also it is problematic that this OGC-gateway topic comes up again. We agreed that the gateway and backend communication should be standardized, and should not have a protocol adapter. We had an agreement for long time, I have no idea why you bring this topic up. We can have a confcall at 12:00, if you agree I send the conference details. Best, D?nes ________________________________ Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra pol?tica de env?o y recepci?n de correo electr?nico en el enlace situado m?s abajo. This message is intended exclusively for its addressee. We only send and receive email on the basis of the terms set out at. http://www.tid.es/ES/PAGINAS/disclaimer.aspx ________________________________ Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra pol?tica de env?o y recepci?n de correo electr?nico en el enlace situado m?s abajo. This message is intended exclusively for its addressee. We only send and receive email on the basis of the terms set out at. http://www.tid.es/ES/PAGINAS/disclaimer.aspx -------------- next part -------------- An HTML attachment was scrubbed... URL: From denes.bisztray at nsn.com Fri Apr 27 15:00:03 2012 From: denes.bisztray at nsn.com (Bisztray, Denes (NSN - HU/Budapest)) Date: Fri, 27 Apr 2012 15:00:03 +0200 Subject: [Fiware-iot] IoT Chapter streamlined architecture In-Reply-To: <8755F290097BD941865DC4245B335D2D08BCD9D8@Polydeuces.office.hd> References: <3F4C11BC54A36642BFB5875D599F47BD05D9C205@DEMUEXC013.nsn-intra.net> <93D28BDF64839C468B848D14227151A2036C54D8@FIESEXC014.nsn-intra.net> <8755F290097BD941865DC4245B335D2D08BCD9B7@Polydeuces.office.hd> <3F4C11BC54A36642BFB5875D599F47BD05D9C255@DEMUEXC013.nsn-intra.net> <8755F290097BD941865DC4245B335D2D08BCD9D8@Polydeuces.office.hd> Message-ID: <3F4C11BC54A36642BFB5875D599F47BD05D9C25C@DEMUEXC013.nsn-intra.net> Yes, internal indeed. Question marks are not a problem for now. Telefonica hopefully fills those gaps. From: ext Tobias Jacobs [mailto:Tobias.Jacobs at neclab.eu] Sent: Friday, April 27, 2012 2:59 PM To: Bisztray, Denes (NSN - HU/Budapest); Farkas, Lorant (NSN - HU/Budapest); fiware-iot at lists.fi-ware.eu Subject: RE: [Fiware-iot] IoT Chapter streamlined architecture it would be nice if you could create an FMC for the Things Management GE unified from the previous participant GEs. Do you mean an internal architecture of the GE? OK, I can try to do that, although I might have some question marks. Best Tobias From: Bisztray, Denes (NSN - HU/Budapest) [mailto:denes.bisztray at nsn.com] Sent: Freitag, 27. April 2012 14:57 To: Tobias Jacobs; Farkas, Lorant (NSN - HU/Budapest); fiware-iot at lists.fi-ware.eu Subject: RE: [Fiware-iot] IoT Chapter streamlined architecture Yes, copying and organising is fine. If you have time, it would be nice if you could create an FMC for the Things Management GE unified from the previous participant GEs. Best, D?nes From: fiware-iot-bounces at lists.fi-ware.eu [mailto:fiware-iot-bounces at lists.fi-ware.eu] On Behalf Of ext Tobias Jacobs Sent: Friday, April 27, 2012 2:54 PM To: Farkas, Lorant (NSN - HU/Budapest); fiware-iot at lists.fi-ware.eu Subject: Re: [Fiware-iot] IoT Chapter streamlined architecture Dear Lorant, all, I can put parts of a description of the Things&Resource Management GE into the wiki. However I do not know what the interface to the Backend Core is - so I do not really feel able to describe that API. Also I could have difficulties describing the aspects coming from Interference Engine - but maybe there are things I can copy and paste from the old descriptions. Best Tobias From: fiware-iot-bounces at lists.fi-ware.eu [mailto:fiware-iot-bounces at lists.fi-ware.eu] On Behalf Of Farkas, Lorant (NSN - HU/Budapest) Sent: Freitag, 27. April 2012 14:24 To: fiware-iot at lists.fi-ware.eu Subject: Re: [Fiware-iot] IoT Chapter streamlined architecture Dear All, I would add that both me and D?nes are away during Monday and Tuesday (official holiday in Hungary). We would like to avoid wasting valuable time that you could contribute to implementing these changes because of lack of information/coordination. We are in a kind of hurry because the deadline of delivering M12 deliverables (Open Specs, Exploitation plans among them) is Monday. So if any of the partners have time/are not on holiday between now and the next weekly meeting, I would kindly ask to please contribute to the: 1. architecture/open specs deliverable: please don't hesitate to edit the new private wiki page (D2.3 streamlined, under the link by D?nes). The process could be the following: -put in the text from the old private wiki page D2.3 and correct in the text things that were updated in the architecture -put in the new graphml (the png generated from it) - we were discussing that we could keep just one diagram instead of the currently shown two and the internal details (connections between functional components inside the GE-s) would be shown only in the GE sub-wiki pages -start editing the GE-s themselves -Ericsson colleagues could start the gateway part, in particular the Gateway/Device Management part, Usurrey/Telecom Italia could also contribute there -NEC could work on the backend in the Things Management GE -Orange could contribute to the Data Handling GE part of the gateway 2. Exploitation deliverable: I created the placeholder for the sections per new GE under https://forge.fi-ware.eu/plugins/mediawiki/wiki/exploitation/index.php/Business_description_GE_Internet_of_Things (you can access this once you are logged in to the exploitation project in forge), the suggestion would be for the partners to take in hands the same GE-s as suggested in the previous point Thanks & Br, Lorant From: Bisztray, Denes (NSN - HU/Budapest) Sent: Friday, April 27, 2012 2:03 PM To: thierry.nagellen at orange.com; Farkas, Lorant (NSN - HU/Budapest); ext Juanjo Hierro; fiware-iot at lists.fi-ware.eu Cc: ext Tobias Jacobs Subject: IoT Chapter streamlined architecture Dear All, We discussed the architecture with Juanjo and came to the conclusion with the attached result. The most important point was not to change agreements that were already discussed. Thus the following changes and observations have been made: - The Data Handling GE exposes an NGSI-10 interface as it did in the previous architecture as well. It is important not to lose such details with the streamlining. This NGSI-10 interface is connected to the Things Management GE making it possible for the things management to get direct NGSI event updates from the gateway. The functionality of the IoT Agent proposed by NEC on the backend seems to be delivered by the Data Handling GE. - The Device Data API will be a translation of ETSI M2M that makes the device data and device updates more useful for the Things Management GE. - All the components in the Things Management GE is untouched. They are simply in one GE. Hence, the previously external interfaces are internal parts from now on. (and thus not part of the Open Specification) - The two Core GEs are renamed to Gateway/Backend Device Management GE. Core GE would suggest that this GE is not replaceable. This is not true however. Official FIWARE does provide these elements, but the point of a GE is to be replacable by specific enablers. In case a UC project wants to replace them with solutions that uses EPC-Global, OGC SWE, etc, they can do it with connecting to the Things Management GE via the Device Data API. - We are not officially support IETF Core. We completely understand that currently the gateway does expose IETF Core and it needs to be translated, however, currently that is an implementation detail, and thus should not be part of the functional architecture. - The Pub/Sub broker from WP6 was missing from the architecture (as also raised by NEC) we added it without any change from the previous architecture. We will start a new branch on the private wiki with the new architecture. It is opened here: https://forge.fi-ware.eu/plugins/mediawiki/wiki/fi-ware-private/index.php/FiwareDeliverableStreamlinedD2.3IoT When the description is complete, we will switch. Best, D?nes From: ext Juanjo Hierro [mailto:jhierro at tid.es] Sent: Friday, April 27, 2012 1:32 PM To: Bisztray, Denes (NSN - HU/Budapest) Cc: Farkas, Lorant (NSN - HU/Budapest); Thierry.nagellen at orange-ftgroup.com; jhierro >> "Juan J. Hierro" Subject: Re: PLEASE READ Re: IoT Chapter streamlined architecture Gentlemen, Thank you for the VERY constructive discussion we have had. It would be great if you can circulate some sort of minutes of the discussion together with an updated version of the Architecture picture asap. It would be rather helpful in order to share with the rest of the IoT team and provide an starting for the necessary update of the Architecture description on the public wiki. Best regards, -- Juanjo ------------- Product Development and Innovation (PDI) - Telefonica Digital website: www.tid.es email: jhierro at tid.es twitter: twitter.com/JuanjoHierro FI-WARE (European Future Internet Core Platform) Chief Architect You can follow FI-WARE at: website: http://www.fi-ware.eu facebook: http://www.facebook.com/pages/FI-WARE/251366491587242 twitter: http://twitter.com/FIware linkedIn: http://www.linkedin.com/groups/FIWARE-4239932 On 27/04/12 11:41, Bisztray, Denes (NSN - HU/Budapest) wrote: We are available from 12:15. Thierry is on holiday so he will not join. Conference details: NSN Voice Conference information 58465 / 1628 Making a conference call France +33 17 061 7813 (PRIMARY) or +33 14 915 1553 Germany +49 89 5159 43800 Spain +349 1187 5929 Sweden +46 85 250 0862 (PRIMARY), +46 84 100 9299 Switzerland +41 44 279 7943 Webex details: Topic: Streamlined Architecture discussion Date: Friday, April 27, 2012 Time: 12:15 pm, Europe Summer Time (Berlin, GMT+02:00) Meeting Number: 709 636 546 Meeting Password: cool ------------------------------------------------------- To start the online meeting ------------------------------------------------------- 1. Go to https://nsn.webex.com/nsn/j.php?ED=210017087&UID=503765542&PW=NZTU4OTFlYWE5&RT=MiMyNQ%3D%3D 2. Log in to your account. 3. Click "Start Now". 4. Follow the instructions that appear on your screen. From: ext Juanjo Hierro [mailto:jhierro at tid.es] Sent: Friday, April 27, 2012 11:34 AM To: Bisztray, Denes (NSN - HU/Budapest) Cc: Farkas, Lorant (NSN - HU/Budapest); Thierry.nagellen at orange-ftgroup.com Subject: Re: PLEASE READ Re: IoT Chapter streamlined architecture Let's have the confcall at 12:00 and try to solve this out. Please circulate the bridge details. Best regards, -- Juanjo ------------- Product Development and Innovation (PDI) - Telefonica Digital website: www.tid.es email: jhierro at tid.es twitter: twitter.com/JuanjoHierro FI-WARE (European Future Internet Core Platform) Chief Architect You can follow FI-WARE at: website: http://www.fi-ware.eu facebook: http://www.facebook.com/pages/FI-WARE/251366491587242 twitter: http://twitter.com/FIware linkedIn: http://www.linkedin.com/groups/FIWARE-4239932 On 27/04/12 09:47, Bisztray, Denes (NSN - HU/Budapest) wrote: Dear Juanjo, Thanks for your long email and also your time for looking at the architecture properly. The topic is complex, if you don't mind I start in medias res. I noted you specific requests on changing names and connections, however these can be implemented only if we come to an agreement on the greater picture. As far as I understand your point (just to make sure we on the same line), you can imagine a backend without IoT resource-level functionality (since you don't think it is core functionality). This would work in such a way, that the gateway is working as a kind of cache, that collects data from the devices and then it publishes it towards the backend via NGSI. Then the backend Thing-level GE processes it. Unfortunately for me this model is not working for two reasons: 1. This possibly works only when there is one gateway and all the sensors of the world is connected to it. When you have multiple gateways, you need operation and management functionality towards the gateway which cannot be done via NGSI. In my opinion core functionality is such functionality that is extremely essential to the system. The scenario of having one gateway proves that the system may work without a resource-level component on the backend, but this extreme case is a bad example. In my opinion this is not what the gateway is designed for. 2. We discussed several times and agreed, and I'm unhappy that this topic comes up again, that the gateway is not a cache. Neither Ericsson, NSN or Orange agrees with this. If you have only NGSI functionality you not only cannot manage the gateways, but also you cannot perform FCAPS functionality on the devices themselves. NGSI cannot do this. - That extension interface is basically used for the Things Management GE to obtain direct resource-level information from the Core GE. Then the Things Management GE processes it. This is result of the original two-level exposure model. - I do not assume the Things Management GE to contain the resource-level resource-management functionality. That would make that GE a big monolith which we could may well call as IoT chapter GE. Also it is problematic that this OGC-gateway topic comes up again. We agreed that the gateway and backend communication should be standardized, and should not have a protocol adapter. We had an agreement for long time, I have no idea why you bring this topic up. We can have a confcall at 12:00, if you agree I send the conference details. Best, D?nes ________________________________ Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra pol?tica de env?o y recepci?n de correo electr?nico en el enlace situado m?s abajo. This message is intended exclusively for its addressee. We only send and receive email on the basis of the terms set out at. http://www.tid.es/ES/PAGINAS/disclaimer.aspx ________________________________ Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra pol?tica de env?o y recepci?n de correo electr?nico en el enlace situado m?s abajo. This message is intended exclusively for its addressee. We only send and receive email on the basis of the terms set out at. http://www.tid.es/ES/PAGINAS/disclaimer.aspx -------------- next part -------------- An HTML attachment was scrubbed... URL: From Tobias.Jacobs at neclab.eu Mon Apr 30 12:18:09 2012 From: Tobias.Jacobs at neclab.eu (Tobias Jacobs) Date: Mon, 30 Apr 2012 10:18:09 +0000 Subject: [Fiware-iot] IoT Chapter streamlined architecture In-Reply-To: <8755F290097BD941865DC4245B335D2D08BCD99E@Polydeuces.office.hd> References: <3F4C11BC54A36642BFB5875D599F47BD05D9C205@DEMUEXC013.nsn-intra.net> <8755F290097BD941865DC4245B335D2D08BCD99E@Polydeuces.office.hd> Message-ID: <8755F290097BD941865DC4245B335D2D08BCDB3E@Polydeuces.office.hd> Small update: I also added NGSI-9 to the interface between Things Management GE and Data Handling GE, as at least the RegisterContext operation should be supported. The changes are now reflected in the wiki page. Best Tobias From: fiware-iot-bounces at lists.fi-ware.eu [mailto:fiware-iot-bounces at lists.fi-ware.eu] On Behalf Of Tobias Jacobs Sent: Freitag, 27. April 2012 14:48 To: Bisztray, Denes (NSN - HU/Budapest); thierry.nagellen at orange.com; Farkas, Lorant (NSN - HU/Budapest); ext Juanjo Hierro; fiware-iot at lists.fi-ware.eu Subject: Re: [Fiware-iot] IoT Chapter streamlined architecture Hi all, As discussed in this week's phone conference, I added one box called "Thing-level Adapter" to the "things and resource management ge", which accounts for the fact that NGSI is the internal language between the components of the GE. See the attached file. Have a nice weekend! Tobias From: Bisztray, Denes (NSN - HU/Budapest) [mailto:denes.bisztray at nsn.com] Sent: Freitag, 27. April 2012 14:03 To: thierry.nagellen at orange.com; Farkas, Lorant (NSN - HU/Budapest); ext Juanjo Hierro; fiware-iot at lists.fi-ware.eu Cc: Tobias Jacobs Subject: IoT Chapter streamlined architecture Dear All, We discussed the architecture with Juanjo and came to the conclusion with the attached result. The most important point was not to change agreements that were already discussed. Thus the following changes and observations have been made: - The Data Handling GE exposes an NGSI-10 interface as it did in the previous architecture as well. It is important not to lose such details with the streamlining. This NGSI-10 interface is connected to the Things Management GE making it possible for the things management to get direct NGSI event updates from the gateway. The functionality of the IoT Agent proposed by NEC on the backend seems to be delivered by the Data Handling GE. - The Device Data API will be a translation of ETSI M2M that makes the device data and device updates more useful for the Things Management GE. - All the components in the Things Management GE is untouched. They are simply in one GE. Hence, the previously external interfaces are internal parts from now on. (and thus not part of the Open Specification) - The two Core GEs are renamed to Gateway/Backend Device Management GE. Core GE would suggest that this GE is not replaceable. This is not true however. Official FIWARE does provide these elements, but the point of a GE is to be replacable by specific enablers. In case a UC project wants to replace them with solutions that uses EPC-Global, OGC SWE, etc, they can do it with connecting to the Things Management GE via the Device Data API. - We are not officially support IETF Core. We completely understand that currently the gateway does expose IETF Core and it needs to be translated, however, currently that is an implementation detail, and thus should not be part of the functional architecture. - The Pub/Sub broker from WP6 was missing from the architecture (as also raised by NEC) we added it without any change from the previous architecture. We will start a new branch on the private wiki with the new architecture. It is opened here: https://forge.fi-ware.eu/plugins/mediawiki/wiki/fi-ware-private/index.php/FiwareDeliverableStreamlinedD2.3IoT When the description is complete, we will switch. Best, D?nes From: ext Juanjo Hierro [mailto:jhierro at tid.es] Sent: Friday, April 27, 2012 1:32 PM To: Bisztray, Denes (NSN - HU/Budapest) Cc: Farkas, Lorant (NSN - HU/Budapest); Thierry.nagellen at orange-ftgroup.com; jhierro >> "Juan J. Hierro" Subject: Re: PLEASE READ Re: IoT Chapter streamlined architecture Gentlemen, Thank you for the VERY constructive discussion we have had. It would be great if you can circulate some sort of minutes of the discussion together with an updated version of the Architecture picture asap. It would be rather helpful in order to share with the rest of the IoT team and provide an starting for the necessary update of the Architecture description on the public wiki. Best regards, -- Juanjo ------------- Product Development and Innovation (PDI) - Telefonica Digital website: www.tid.es email: jhierro at tid.es twitter: twitter.com/JuanjoHierro FI-WARE (European Future Internet Core Platform) Chief Architect You can follow FI-WARE at: website: http://www.fi-ware.eu facebook: http://www.facebook.com/pages/FI-WARE/251366491587242 twitter: http://twitter.com/FIware linkedIn: http://www.linkedin.com/groups/FIWARE-4239932 On 27/04/12 11:41, Bisztray, Denes (NSN - HU/Budapest) wrote: We are available from 12:15. Thierry is on holiday so he will not join. Conference details: NSN Voice Conference information 58465 / 1628 Making a conference call France +33 17 061 7813 (PRIMARY) or +33 14 915 1553 Germany +49 89 5159 43800 Spain +349 1187 5929 Sweden +46 85 250 0862 (PRIMARY), +46 84 100 9299 Switzerland +41 44 279 7943 Webex details: Topic: Streamlined Architecture discussion Date: Friday, April 27, 2012 Time: 12:15 pm, Europe Summer Time (Berlin, GMT+02:00) Meeting Number: 709 636 546 Meeting Password: cool ------------------------------------------------------- To start the online meeting ------------------------------------------------------- 1. Go to https://nsn.webex.com/nsn/j.php?ED=210017087&UID=503765542&PW=NZTU4OTFlYWE5&RT=MiMyNQ%3D%3D 2. Log in to your account. 3. Click "Start Now". 4. Follow the instructions that appear on your screen. From: ext Juanjo Hierro [mailto:jhierro at tid.es] Sent: Friday, April 27, 2012 11:34 AM To: Bisztray, Denes (NSN - HU/Budapest) Cc: Farkas, Lorant (NSN - HU/Budapest); Thierry.nagellen at orange-ftgroup.com Subject: Re: PLEASE READ Re: IoT Chapter streamlined architecture Let's have the confcall at 12:00 and try to solve this out. Please circulate the bridge details. Best regards, -- Juanjo ------------- Product Development and Innovation (PDI) - Telefonica Digital website: www.tid.es email: jhierro at tid.es twitter: twitter.com/JuanjoHierro FI-WARE (European Future Internet Core Platform) Chief Architect You can follow FI-WARE at: website: http://www.fi-ware.eu facebook: http://www.facebook.com/pages/FI-WARE/251366491587242 twitter: http://twitter.com/FIware linkedIn: http://www.linkedin.com/groups/FIWARE-4239932 On 27/04/12 09:47, Bisztray, Denes (NSN - HU/Budapest) wrote: Dear Juanjo, Thanks for your long email and also your time for looking at the architecture properly. The topic is complex, if you don't mind I start in medias res. I noted you specific requests on changing names and connections, however these can be implemented only if we come to an agreement on the greater picture. As far as I understand your point (just to make sure we on the same line), you can imagine a backend without IoT resource-level functionality (since you don't think it is core functionality). This would work in such a way, that the gateway is working as a kind of cache, that collects data from the devices and then it publishes it towards the backend via NGSI. Then the backend Thing-level GE processes it. Unfortunately for me this model is not working for two reasons: 1. This possibly works only when there is one gateway and all the sensors of the world is connected to it. When you have multiple gateways, you need operation and management functionality towards the gateway which cannot be done via NGSI. In my opinion core functionality is such functionality that is extremely essential to the system. The scenario of having one gateway proves that the system may work without a resource-level component on the backend, but this extreme case is a bad example. In my opinion this is not what the gateway is designed for. 2. We discussed several times and agreed, and I'm unhappy that this topic comes up again, that the gateway is not a cache. Neither Ericsson, NSN or Orange agrees with this. If you have only NGSI functionality you not only cannot manage the gateways, but also you cannot perform FCAPS functionality on the devices themselves. NGSI cannot do this. - That extension interface is basically used for the Things Management GE to obtain direct resource-level information from the Core GE. Then the Things Management GE processes it. This is result of the original two-level exposure model. - I do not assume the Things Management GE to contain the resource-level resource-management functionality. That would make that GE a big monolith which we could may well call as IoT chapter GE. Also it is problematic that this OGC-gateway topic comes up again. We agreed that the gateway and backend communication should be standardized, and should not have a protocol adapter. We had an agreement for long time, I have no idea why you bring this topic up. We can have a confcall at 12:00, if you agree I send the conference details. Best, D?nes ________________________________ Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra pol?tica de env?o y recepci?n de correo electr?nico en el enlace situado m?s abajo. This message is intended exclusively for its addressee. We only send and receive email on the basis of the terms set out at. http://www.tid.es/ES/PAGINAS/disclaimer.aspx ________________________________ Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra pol?tica de env?o y recepci?n de correo electr?nico en el enlace situado m?s abajo. This message is intended exclusively for its addressee. We only send and receive email on the basis of the terms set out at. http://www.tid.es/ES/PAGINAS/disclaimer.aspx -------------- next part -------------- An HTML attachment was scrubbed... URL: From jhierro at tid.es Mon Apr 30 12:57:51 2012 From: jhierro at tid.es (Juanjo Hierro) Date: Mon, 30 Apr 2012 12:57:51 +0200 Subject: [Fiware-iot] IoT Chapter streamlined architecture In-Reply-To: <8755F290097BD941865DC4245B335D2D08BCDB3E@Polydeuces.office.hd> References: <3F4C11BC54A36642BFB5875D599F47BD05D9C205@DEMUEXC013.nsn-intra.net> <8755F290097BD941865DC4245B335D2D08BCD99E@Polydeuces.office.hd> <8755F290097BD941865DC4245B335D2D08BCDB3E@Polydeuces.office.hd> Message-ID: <4F9E702F.4060208@tid.es> Did you update it in the private wiki ? We agreed that we would create first a branch to double-check changes before uploading them into the public wiki ... Cheers, -- Juanjo ------------- Product Development and Innovation (PDI) - Telefonica Digital website: www.tid.es email: jhierro at tid.es twitter: twitter.com/JuanjoHierro FI-WARE (European Future Internet Core Platform) Chief Architect You can follow FI-WARE at: website: http://www.fi-ware.eu facebook: http://www.facebook.com/pages/FI-WARE/251366491587242 twitter: http://twitter.com/FIware linkedIn: http://www.linkedin.com/groups/FIWARE-4239932 On 30/04/12 12:18, Tobias Jacobs wrote: Small update: I also added NGSI-9 to the interface between Things Management GE and Data Handling GE, as at least the RegisterContext operation should be supported. The changes are now reflected in the wiki page. Best Tobias From: fiware-iot-bounces at lists.fi-ware.eu [mailto:fiware-iot-bounces at lists.fi-ware.eu] On Behalf Of Tobias Jacobs Sent: Freitag, 27. April 2012 14:48 To: Bisztray, Denes (NSN - HU/Budapest); thierry.nagellen at orange.com; Farkas, Lorant (NSN - HU/Budapest); ext Juanjo Hierro; fiware-iot at lists.fi-ware.eu Subject: Re: [Fiware-iot] IoT Chapter streamlined architecture Hi all, As discussed in this week?s phone conference, I added one box called ?Thing-level Adapter? to the ?things and resource management ge?, which accounts for the fact that NGSI is the internal language between the components of the GE. See the attached file. Have a nice weekend! Tobias From: Bisztray, Denes (NSN - HU/Budapest) [mailto:denes.bisztray at nsn.com] Sent: Freitag, 27. April 2012 14:03 To: thierry.nagellen at orange.com; Farkas, Lorant (NSN - HU/Budapest); ext Juanjo Hierro; fiware-iot at lists.fi-ware.eu Cc: Tobias Jacobs Subject: IoT Chapter streamlined architecture Dear All, We discussed the architecture with Juanjo and came to the conclusion with the attached result. The most important point was not to change agreements that were already discussed. Thus the following changes and observations have been made: - The Data Handling GE exposes an NGSI-10 interface as it did in the previous architecture as well. It is important not to lose such details with the streamlining. This NGSI-10 interface is connected to the Things Management GE making it possible for the things management to get direct NGSI event updates from the gateway. The functionality of the IoT Agent proposed by NEC on the backend seems to be delivered by the Data Handling GE. - The Device Data API will be a translation of ETSI M2M that makes the device data and device updates more useful for the Things Management GE. - All the components in the Things Management GE is untouched. They are simply in one GE. Hence, the previously external interfaces are internal parts from now on. (and thus not part of the Open Specification) - The two Core GEs are renamed to Gateway/Backend Device Management GE. Core GE would suggest that this GE is not replaceable. This is not true however. Official FIWARE does provide these elements, but the point of a GE is to be replacable by specific enablers. In case a UC project wants to replace them with solutions that uses EPC-Global, OGC SWE, etc, they can do it with connecting to the Things Management GE via the Device Data API. - We are not officially support IETF Core. We completely understand that currently the gateway does expose IETF Core and it needs to be translated, however, currently that is an implementation detail, and thus should not be part of the functional architecture. - The Pub/Sub broker from WP6 was missing from the architecture (as also raised by NEC) we added it without any change from the previous architecture. We will start a new branch on the private wiki with the new architecture. It is opened here: https://forge.fi-ware.eu/plugins/mediawiki/wiki/fi-ware-private/index.php/FiwareDeliverableStreamlinedD2.3IoT When the description is complete, we will switch. Best, D?nes From: ext Juanjo Hierro [mailto:jhierro at tid.es] Sent: Friday, April 27, 2012 1:32 PM To: Bisztray, Denes (NSN - HU/Budapest) Cc: Farkas, Lorant (NSN - HU/Budapest); Thierry.nagellen at orange-ftgroup.com; jhierro >> "Juan J. Hierro" Subject: Re: PLEASE READ Re: IoT Chapter streamlined architecture Gentlemen, Thank you for the VERY constructive discussion we have had. It would be great if you can circulate some sort of minutes of the discussion together with an updated version of the Architecture picture asap. It would be rather helpful in order to share with the rest of the IoT team and provide an starting for the necessary update of the Architecture description on the public wiki. Best regards, -- Juanjo ------------- Product Development and Innovation (PDI) - Telefonica Digital website: www.tid.es email: jhierro at tid.es twitter: twitter.com/JuanjoHierro FI-WARE (European Future Internet Core Platform) Chief Architect You can follow FI-WARE at: website: http://www.fi-ware.eu facebook: http://www.facebook.com/pages/FI-WARE/251366491587242 twitter: http://twitter.com/FIware linkedIn: http://www.linkedin.com/groups/FIWARE-4239932 On 27/04/12 11:41, Bisztray, Denes (NSN - HU/Budapest) wrote: We are available from 12:15. Thierry is on holiday so he will not join. Conference details: NSN Voice Conference information 58465 / 1628 Making a conference call France +33 17 061 7813 (PRIMARY) or +33 14 915 1553 Germany +49 89 5159 43800 Spain +349 1187 5929 Sweden +46 85 250 0862 (PRIMARY), +46 84 100 9299 Switzerland +41 44 279 7943 Webex details: Topic: Streamlined Architecture discussion Date: Friday, April 27, 2012 Time: 12:15 pm, Europe Summer Time (Berlin, GMT+02:00) Meeting Number: 709 636 546 Meeting Password: cool ------------------------------------------------------- To start the online meeting ------------------------------------------------------- 1. Go to https://nsn.webex.com/nsn/j.php?ED=210017087&UID=503765542&PW=NZTU4OTFlYWE5&RT=MiMyNQ%3D%3D 2. Log in to your account. 3. Click "Start Now". 4. Follow the instructions that appear on your screen. From: ext Juanjo Hierro [mailto:jhierro at tid.es] Sent: Friday, April 27, 2012 11:34 AM To: Bisztray, Denes (NSN - HU/Budapest) Cc: Farkas, Lorant (NSN - HU/Budapest); Thierry.nagellen at orange-ftgroup.com Subject: Re: PLEASE READ Re: IoT Chapter streamlined architecture Let's have the confcall at 12:00 and try to solve this out. Please circulate the bridge details. Best regards, -- Juanjo ------------- Product Development and Innovation (PDI) - Telefonica Digital website: www.tid.es email: jhierro at tid.es twitter: twitter.com/JuanjoHierro FI-WARE (European Future Internet Core Platform) Chief Architect You can follow FI-WARE at: website: http://www.fi-ware.eu facebook: http://www.facebook.com/pages/FI-WARE/251366491587242 twitter: http://twitter.com/FIware linkedIn: http://www.linkedin.com/groups/FIWARE-4239932 On 27/04/12 09:47, Bisztray, Denes (NSN - HU/Budapest) wrote: Dear Juanjo, Thanks for your long email and also your time for looking at the architecture properly. The topic is complex, if you don?t mind I start in medias res. I noted you specific requests on changing names and connections, however these can be implemented only if we come to an agreement on the greater picture. As far as I understand your point (just to make sure we on the same line), you can imagine a backend without IoT resource-level functionality (since you don?t think it is core functionality). This would work in such a way, that the gateway is working as a kind of cache, that collects data from the devices and then it publishes it towards the backend via NGSI. Then the backend Thing-level GE processes it. Unfortunately for me this model is not working for two reasons: 1. This possibly works only when there is one gateway and all the sensors of the world is connected to it. When you have multiple gateways, you need operation and management functionality towards the gateway which cannot be done via NGSI. In my opinion core functionality is such functionality that is extremely essential to the system. The scenario of having one gateway proves that the system may work without a resource-level component on the backend, but this extreme case is a bad example. In my opinion this is not what the gateway is designed for. 2. We discussed several times and agreed, and I?m unhappy that this topic comes up again, that the gateway is not a cache. Neither Ericsson, NSN or Orange agrees with this. If you have only NGSI functionality you not only cannot manage the gateways, but also you cannot perform FCAPS functionality on the devices themselves. NGSI cannot do this. - That extension interface is basically used for the Things Management GE to obtain direct resource-level information from the Core GE. Then the Things Management GE processes it. This is result of the original two-level exposure model. - I do not assume the Things Management GE to contain the resource-level resource-management functionality. That would make that GE a big monolith which we could may well call as IoT chapter GE. Also it is problematic that this OGC-gateway topic comes up again. We agreed that the gateway and backend communication should be standardized, and should not have a protocol adapter. We had an agreement for long time, I have no idea why you bring this topic up. We can have a confcall at 12:00, if you agree I send the conference details. Best, D?nes ________________________________ Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra pol?tica de env?o y recepci?n de correo electr?nico en el enlace situado m?s abajo. This message is intended exclusively for its addressee. We only send and receive email on the basis of the terms set out at. http://www.tid.es/ES/PAGINAS/disclaimer.aspx ________________________________ Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra pol?tica de env?o y recepci?n de correo electr?nico en el enlace situado m?s abajo. This message is intended exclusively for its addressee. We only send and receive email on the basis of the terms set out at. http://www.tid.es/ES/PAGINAS/disclaimer.aspx ________________________________ 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 lorant.farkas at nsn.com Mon Apr 30 16:48:22 2012 From: lorant.farkas at nsn.com (Farkas, Lorant (NSN - HU/Budapest)) Date: Mon, 30 Apr 2012 17:48:22 +0300 Subject: [Fiware-iot] IoT Chapter streamlined architecture References: <3F4C11BC54A36642BFB5875D599F47BD05D9C205@DEMUEXC013.nsn-intra.net> <8755F290097BD941865DC4245B335D2D08BCD99E@Polydeuces.office.hd> <8755F290097BD941865DC4245B335D2D08BCDB3E@Polydeuces.office.hd> <4F9E702F.4060208@tid.es> Message-ID: <93D28BDF64839C468B848D14227151A2C53195@FIESEXC014.nsn-intra.net> Hi, On our side the branch was created and disclosed to the iot list on Friday. Br, Lorant -----Original Message----- From: ext Juanjo Hierro [mailto:jhierro at tid.es] Sent: Mon 2012. 04. 30. 12:57 PM To: Tobias Jacobs Cc: Bisztray, Denes (NSN - HU/Budapest); thierry.nagellen at orange.com; Farkas, Lorant (NSN - HU/Budapest); fiware-iot at lists.fi-ware.eu Subject: Re: [Fiware-iot] IoT Chapter streamlined architecture Did you update it in the private wiki ? We agreed that we would create first a branch to double-check changes before uploading them into the public wiki ... Cheers, -- Juanjo ------------- Product Development and Innovation (PDI) - Telefonica Digital website: www.tid.es email: jhierro at tid.es twitter: twitter.com/JuanjoHierro FI-WARE (European Future Internet Core Platform) Chief Architect You can follow FI-WARE at: website: http://www.fi-ware.eu facebook: http://www.facebook.com/pages/FI-WARE/251366491587242 twitter: http://twitter.com/FIware linkedIn: http://www.linkedin.com/groups/FIWARE-4239932 On 30/04/12 12:18, Tobias Jacobs wrote: Small update: I also added NGSI-9 to the interface between Things Management GE and Data Handling GE, as at least the RegisterContext operation should be supported. The changes are now reflected in the wiki page. Best Tobias From: fiware-iot-bounces at lists.fi-ware.eu [mailto:fiware-iot-bounces at lists.fi-ware.eu] On Behalf Of Tobias Jacobs Sent: Freitag, 27. April 2012 14:48 To: Bisztray, Denes (NSN - HU/Budapest); thierry.nagellen at orange.com; Farkas, Lorant (NSN - HU/Budapest); ext Juanjo Hierro; fiware-iot at lists.fi-ware.eu Subject: Re: [Fiware-iot] IoT Chapter streamlined architecture Hi all, As discussed in this week's phone conference, I added one box called "Thing-level Adapter" to the "things and resource management ge", which accounts for the fact that NGSI is the internal language between the components of the GE. See the attached file. Have a nice weekend! Tobias From: Bisztray, Denes (NSN - HU/Budapest) [mailto:denes.bisztray at nsn.com] Sent: Freitag, 27. April 2012 14:03 To: thierry.nagellen at orange.com; Farkas, Lorant (NSN - HU/Budapest); ext Juanjo Hierro; fiware-iot at lists.fi-ware.eu Cc: Tobias Jacobs Subject: IoT Chapter streamlined architecture Dear All, We discussed the architecture with Juanjo and came to the conclusion with the attached result. The most important point was not to change agreements that were already discussed. Thus the following changes and observations have been made: - The Data Handling GE exposes an NGSI-10 interface as it did in the previous architecture as well. It is important not to lose such details with the streamlining. This NGSI-10 interface is connected to the Things Management GE making it possible for the things management to get direct NGSI event updates from the gateway. The functionality of the IoT Agent proposed by NEC on the backend seems to be delivered by the Data Handling GE. - The Device Data API will be a translation of ETSI M2M that makes the device data and device updates more useful for the Things Management GE. - All the components in the Things Management GE is untouched. They are simply in one GE. Hence, the previously external interfaces are internal parts from now on. (and thus not part of the Open Specification) - The two Core GEs are renamed to Gateway/Backend Device Management GE. Core GE would suggest that this GE is not replaceable. This is not true however. Official FIWARE does provide these elements, but the point of a GE is to be replacable by specific enablers. In case a UC project wants to replace them with solutions that uses EPC-Global, OGC SWE, etc, they can do it with connecting to the Things Management GE via the Device Data API. - We are not officially support IETF Core. We completely understand that currently the gateway does expose IETF Core and it needs to be translated, however, currently that is an implementation detail, and thus should not be part of the functional architecture. - The Pub/Sub broker from WP6 was missing from the architecture (as also raised by NEC) we added it without any change from the previous architecture. We will start a new branch on the private wiki with the new architecture. It is opened here: https://forge.fi-ware.eu/plugins/mediawiki/wiki/fi-ware-private/index.php/FiwareDeliverableStreamlinedD2.3IoT When the description is complete, we will switch. Best, D?nes From: ext Juanjo Hierro [mailto:jhierro at tid.es] Sent: Friday, April 27, 2012 1:32 PM To: Bisztray, Denes (NSN - HU/Budapest) Cc: Farkas, Lorant (NSN - HU/Budapest); Thierry.nagellen at orange-ftgroup.com; jhierro >> "Juan J. Hierro" Subject: Re: PLEASE READ Re: IoT Chapter streamlined architecture Gentlemen, Thank you for the VERY constructive discussion we have had. It would be great if you can circulate some sort of minutes of the discussion together with an updated version of the Architecture picture asap. It would be rather helpful in order to share with the rest of the IoT team and provide an starting for the necessary update of the Architecture description on the public wiki. Best regards, -- Juanjo ------------- Product Development and Innovation (PDI) - Telefonica Digital website: www.tid.es email: jhierro at tid.es twitter: twitter.com/JuanjoHierro FI-WARE (European Future Internet Core Platform) Chief Architect You can follow FI-WARE at: website: http://www.fi-ware.eu facebook: http://www.facebook.com/pages/FI-WARE/251366491587242 twitter: http://twitter.com/FIware linkedIn: http://www.linkedin.com/groups/FIWARE-4239932 On 27/04/12 11:41, Bisztray, Denes (NSN - HU/Budapest) wrote: We are available from 12:15. Thierry is on holiday so he will not join. Conference details: NSN Voice Conference information 58465 / 1628 Making a conference call France +33 17 061 7813 (PRIMARY) or +33 14 915 1553 Germany +49 89 5159 43800 Spain +349 1187 5929 Sweden +46 85 250 0862 (PRIMARY), +46 84 100 9299 Switzerland +41 44 279 7943 Webex details: Topic: Streamlined Architecture discussion Date: Friday, April 27, 2012 Time: 12:15 pm, Europe Summer Time (Berlin, GMT+02:00) Meeting Number: 709 636 546 Meeting Password: cool ------------------------------------------------------- To start the online meeting ------------------------------------------------------- 1. Go to https://nsn.webex.com/nsn/j.php?ED=210017087&UID=503765542&PW=NZTU4OTFlYWE5&RT=MiMyNQ%3D%3D 2. Log in to your account. 3. Click "Start Now". 4. Follow the instructions that appear on your screen. From: ext Juanjo Hierro [mailto:jhierro at tid.es] Sent: Friday, April 27, 2012 11:34 AM To: Bisztray, Denes (NSN - HU/Budapest) Cc: Farkas, Lorant (NSN - HU/Budapest); Thierry.nagellen at orange-ftgroup.com Subject: Re: PLEASE READ Re: IoT Chapter streamlined architecture Let's have the confcall at 12:00 and try to solve this out. Please circulate the bridge details. Best regards, -- Juanjo ------------- Product Development and Innovation (PDI) - Telefonica Digital website: www.tid.es email: jhierro at tid.es twitter: twitter.com/JuanjoHierro FI-WARE (European Future Internet Core Platform) Chief Architect You can follow FI-WARE at: website: http://www.fi-ware.eu facebook: http://www.facebook.com/pages/FI-WARE/251366491587242 twitter: http://twitter.com/FIware linkedIn: http://www.linkedin.com/groups/FIWARE-4239932 On 27/04/12 09:47, Bisztray, Denes (NSN - HU/Budapest) wrote: Dear Juanjo, Thanks for your long email and also your time for looking at the architecture properly. The topic is complex, if you don't mind I start in medias res. I noted you specific requests on changing names and connections, however these can be implemented only if we come to an agreement on the greater picture. As far as I understand your point (just to make sure we on the same line), you can imagine a backend without IoT resource-level functionality (since you don't think it is core functionality). This would work in such a way, that the gateway is working as a kind of cache, that collects data from the devices and then it publishes it towards the backend via NGSI. Then the backend Thing-level GE processes it. Unfortunately for me this model is not working for two reasons: 1. This possibly works only when there is one gateway and all the sensors of the world is connected to it. When you have multiple gateways, you need operation and management functionality towards the gateway which cannot be done via NGSI. In my opinion core functionality is such functionality that is extremely essential to the system. The scenario of having one gateway proves that the system may work without a resource-level component on the backend, but this extreme case is a bad example. In my opinion this is not what the gateway is designed for. 2. We discussed several times and agreed, and I'm unhappy that this topic comes up again, that the gateway is not a cache. Neither Ericsson, NSN or Orange agrees with this. If you have only NGSI functionality you not only cannot manage the gateways, but also you cannot perform FCAPS functionality on the devices themselves. NGSI cannot do this. - That extension interface is basically used for the Things Management GE to obtain direct resource-level information from the Core GE. Then the Things Management GE processes it. This is result of the original two-level exposure model. - I do not assume the Things Management GE to contain the resource-level resource-management functionality. That would make that GE a big monolith which we could may well call as IoT chapter GE. Also it is problematic that this OGC-gateway topic comes up again. We agreed that the gateway and backend communication should be standardized, and should not have a protocol adapter. We had an agreement for long time, I have no idea why you bring this topic up. We can have a confcall at 12:00, if you agree I send the conference details. Best, D?nes ________________________________ Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra pol?tica de env?o y recepci?n de correo electr?nico en el enlace situado m?s abajo. This message is intended exclusively for its addressee. We only send and receive email on the basis of the terms set out at. http://www.tid.es/ES/PAGINAS/disclaimer.aspx ________________________________ Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra pol?tica de env?o y recepci?n de correo electr?nico en el enlace situado m?s abajo. This message is intended exclusively for its addressee. We only send and receive email on the basis of the terms set out at. http://www.tid.es/ES/PAGINAS/disclaimer.aspx ________________________________ 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