From sabrina.guerra at telecomitalia.it Thu Sep 1 15:55:50 2011 From: sabrina.guerra at telecomitalia.it (Guerra Sabrina) Date: Thu, 1 Sep 2011 15:55:50 +0200 Subject: [Fiware-iot] IoT Assets mapping In-Reply-To: References: Message-ID: <36A93B31228D3B49B691AD31652BCAE9A5359561B7@GRFMBX702BA020.griffon.local> Hi, we submit into FI-WARE Forge Telecom Italia contribution for the assets list. Here there is the link to V10 version. https://forge.fi-ware.eu/docman/view.php/11/336/v10_IoT-Architecture-mapping.xlsx Best regards 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 thierry.nagellen at orange-ftgroup.com Inviato: Tuesday, August 30, 2011 3:14 PM A: fiware-iot at lists.fi-ware.eu Oggetto: [Fiware-iot] IoT Assets mapping Dear partners, Some contributions are missing (Thales, Telecom Italia, Ericsson) so we will continue with the available content and try to add later the new contributions. For Task Leaders, we have to provide a first analysis per task how we could cover the main features. The next step is also to provide user stories in the Excel sheet provided by TID and define MosCoW priorities for further development. Feel free to improve your assets descriptions. Doors are not closed but we have to propose a consistent view for the end of September of our expected achievements for the next 6 months. BR Thierry Nagellen Orange Labs Networks & Carriers 905 rue Albert Einstein 06921 Sophia Antipolis Cedex +33 492 94 52 84 +33 679 85 08 44 Questo messaggio e i suoi allegati sono indirizzati esclusivamente alle persone indicate. La diffusione, copia o qualsiasi altra azione derivante dalla conoscenza di queste informazioni sono rigorosamente vietate. Qualora abbiate ricevuto questo documento per errore siete cortesemente pregati di darne immediata comunicazione al mittente e di provvedere alla sua distruzione, Grazie. This e-mail and any attachments is confidential and may contain privileged information intended for the addressee(s) only. Dissemination, copying, printing or use by anybody else is unauthorised. If you are not the intended recipient, please delete this message and any attachments and advise the sender by return e-mail, Thanks. [cid:00000000000000000000000000000001 at TI.Disclaimer]Rispetta l'ambiente. Non stampare questa mail se non ? necessario. -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: logo Ambiente_foglia.jpg Type: image/jpeg Size: 677 bytes Desc: logo Ambiente_foglia.jpg URL: From gianpiero.fici at telecomitalia.it Thu Sep 1 20:26:06 2011 From: gianpiero.fici at telecomitalia.it (Fici Gian Piero) Date: Thu, 1 Sep 2011 20:26:06 +0200 Subject: [Fiware-iot] Features backlog example by TI Message-ID: Hi, Here it is our take at a backlog example of a theme (for a GE), an epic (for a component), and a user story (for the implementation of a component). These examples reflects our understanding of the guidelines for the backlog we got until now, let us know your thoughts on this, comments or suggestions. I tried to upload the document into Forge but I got a "pending state (need validation)" (probably I made something wrong, damn :)), so since it is quite light I am attaching the Excel file directly to this e-mail. Sorry for the inconvenience. Ciao, Gian Piero P.S. Thierry, I hope our examples can be useful for your discussion tomorrow morning with the other WP leaders. Gian Piero Fici __________________________________ Telecom Italia Strategia ed Innovazione Research & Trends Future Internet Technologies & Research Questo messaggio e i suoi allegati sono indirizzati esclusivamente alle persone indicate. La diffusione, copia o qualsiasi altra azione derivante dalla conoscenza di queste informazioni sono rigorosamente vietate. Qualora abbiate ricevuto questo documento per errore siete cortesemente pregati di darne immediata comunicazione al mittente e di provvedere alla sua distruzione, Grazie. This e-mail and any attachments is confidential and may contain privileged information intended for the addressee(s) only. Dissemination, copying, printing or use by anybody else is unauthorised. If you are not the intended recipient, please delete this message and any attachments and advise the sender by return e-mail, Thanks. [cid:00000000000000000000000000000001 at TI.Disclaimer]Rispetta l'ambiente. Non stampare questa mail se non ? necessario. -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: Backlog+entries+examples+by+TI+11-09-01.xls Type: application/vnd.ms-excel Size: 51712 bytes Desc: Backlog+entries+examples+by+TI+11-09-01.xls URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: logo Ambiente_foglia.jpg Type: image/jpeg Size: 677 bytes Desc: logo Ambiente_foglia.jpg URL: From lorant.farkas at nsn.com Fri Sep 2 09:43:14 2011 From: lorant.farkas at nsn.com (Farkas, Lorant (NSN - HU/Budapest)) Date: Fri, 2 Sep 2011 10:43:14 +0300 Subject: [Fiware-iot] Features backlog example by TI In-Reply-To: A References: A Message-ID: <93D28BDF64839C468B848D14227151A2023A5399@FIESEXC014.nsn-intra.net> Hi Gian Piero, Thanks for the contribution. You always have to log in at the top right hand side of the page. It is not very eye catching, one usually gets aware of this when the document he submitted gets automatically to "pending" state. I set it (and 2 other docs I discovered now to be in pending state) to active. Thanks & Br, Lorant ________________________________ From: fiware-iot-bounces at lists.fi-ware.eu [mailto:fiware-iot-bounces at lists.fi-ware.eu] On Behalf Of ext Fici Gian Piero Sent: Thursday, September 01, 2011 8:26 PM To: 'fiware-iot at lists.fi-ware.eu' Subject: [Fiware-iot] Features backlog example by TI Hi, Here it is our take at a backlog example of a theme (for a GE), an epic (for a component), and a user story (for the implementation of a component). These examples reflects our understanding of the guidelines for the backlog we got until now, let us know your thoughts on this, comments or suggestions. I tried to upload the document into Forge but I got a "pending state (need validation)" (probably I made something wrong, damn J), so since it is quite light I am attaching the Excel file directly to this e-mail. Sorry for the inconvenience. Ciao, Gian Piero P.S. Thierry, I hope our examples can be useful for your discussion tomorrow morning with the other WP leaders. Gian Piero Fici __________________________________ Telecom Italia Strategia ed Innovazione Research & Trends Future Internet Technologies & Research Questo messaggio e i suoi allegati sono indirizzati esclusivamente alle persone indicate. La diffusione, copia o qualsiasi altra azione derivante dalla conoscenza di queste informazioni sono rigorosamente vietate. Qualora abbiate ricevuto questo documento per errore siete cortesemente pregati di darne immediata comunicazione al mittente e di provvedere alla sua distruzione, Grazie. This e-mail and any attachments is confidential and may contain privileged information intended for the addressee(s) only. Dissemination, copying, printing or use by anybody else is unauthorised. If you are not the intended recipient, please delete this message and any attachments and advise the sender by return e-mail, Thanks. Rispetta l'ambiente. Non stampare questa mail se non ? necessario. -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: logo Ambiente_foglia.jpg Type: image/jpeg Size: 677 bytes Desc: logo Ambiente_foglia.jpg URL: From sabrina.guerra at telecomitalia.it Mon Sep 5 13:21:00 2011 From: sabrina.guerra at telecomitalia.it (Guerra Sabrina) Date: Mon, 5 Sep 2011 13:21:00 +0200 Subject: [Fiware-iot] First initial analysis of the IoT Assets mapping for the task 5.1 IoT Communications In-Reply-To: <36A93B31228D3B49B691AD31652BCAE9A5356033D7@GRFMBX702BA020.griffon.local> References: <36A93B31228D3B49B691AD31652BCAE9A5356033D7@GRFMBX702BA020.griffon.local> Message-ID: <36A93B31228D3B49B691AD31652BCAE9A53595673F@GRFMBX702BA020.griffon.local> Hi, we've begun to analyze the list of assets related to the "IoT Communication" task submitted by the FI-WARE partners. Some initial considerations for the components are: * Component Connection Protocol Adapter - the better solution is that as many as possible protocols are supported by the IoT Services Enablement Platform, for this reason all the assets presented can be included into the implementation of the IoT SE Platform, provided that it's possible to translate them in a common internal form through the component Communication Protocol Abstraction Definition. * Component Communication Protocol Abstraction Definition - the epic for this component is different from the description included in the document "FI-WARE High-level Description". Our goal was to introduce a layer that allows an abstraction level for all Connection Protocol Adapters in order to communicate with the IoT SE Platform Core using a common internal language. The "templates", we are referring to in the document, are a kind of rules to translate any specific protocol into the common internal language and not a mechanism to generate Connection Protocol Adapters. This mechanism to automatically generate Connection Protocol Adapters is in any case very interesting and we could add it to the architecture document, if needed. * Component Access Policy Control - The second point of the epic for this component treats the access as a matter of payment (e.g. access only free services), while we intend the access as a matter of permissions to access resources. In our opinion these are different levels and they don't belong to the same component. * Component Quality of Service Control - From the grid it looks like that no asset has this functionality readily available, but since this component is not fundamental for a prototype of the IoT SE Platform, it can be left out or postponed in the future. For the other components we don't have specific considerations for the moment, but it looks like that Pangoo/M2MPlanet (by Orange) and Cumulocity (by NSN) are the assets that are more in line with our requirements. What do you think of this initial analysis of the assets? Are there any comments on these considerations? If you agree we could proceed with a more detailed analysis of the two proposed assets. Best regards, Sabrina Guerra __________________________________ Telecom Italia S.p.a. Strategia e Innovazione, Research & Trends Telefono +39 011 228 8359 Cellulare +39 331 600 1349 Questo messaggio e i suoi allegati sono indirizzati esclusivamente alle persone indicate. La diffusione, copia o qualsiasi altra azione derivante dalla conoscenza di queste informazioni sono rigorosamente vietate. Qualora abbiate ricevuto questo documento per errore siete cortesemente pregati di darne immediata comunicazione al mittente e di provvedere alla sua distruzione, Grazie. This e-mail and any attachments is confidential and may contain privileged information intended for the addressee(s) only. Dissemination, copying, printing or use by anybody else is unauthorised. If you are not the intended recipient, please delete this message and any attachments and advise the sender by return e-mail, Thanks. [cid:00000000000000000000000000000001 at TI.Disclaimer]Rispetta l'ambiente. Non stampare questa mail se non ? necessario. -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: logo Ambiente_foglia.jpg Type: image/jpeg Size: 677 bytes Desc: logo Ambiente_foglia.jpg URL: From thierry.nagellen at orange-ftgroup.com Mon Sep 5 16:40:53 2011 From: thierry.nagellen at orange-ftgroup.com (thierry.nagellen at orange-ftgroup.com) Date: Mon, 5 Sep 2011 16:40:53 +0200 Subject: [Fiware-iot] First initial analysis of the IoT Assets mapping for the task 5.1 IoT Communications In-Reply-To: <36A93B31228D3B49B691AD31652BCAE9A53595673F@GRFMBX702BA020.griffon.local> References: <36A93B31228D3B49B691AD31652BCAE9A5356033D7@GRFMBX702BA020.griffon.local> <36A93B31228D3B49B691AD31652BCAE9A53595673F@GRFMBX702BA020.griffon.local> Message-ID: Hi Sabrina Thanks for your first analysis. We had slightly discussed the point of protocols IoT SE has to support to deal with different kind of things. I fully support your approach that the optimal way for us is to integrate the protocols through the assets we have because to implement all protocols will take lots of time and the main topic is how we can provide a common access. But in this case, partners would have to develop a dedicated interface to be integrated in the component "Connection Protocol Adapter". This should be a good point for the Open Specification and to target different Use Cases. Regarding EPICs which are different from the description of HLD deliverable, feel free to add a new EPIC to be in line with the deliverable and we would be able to discuss which one is the more critical and how we can put some priorities. We can have "several" EPIC per component and we can discuss which are the most valuable and how we could implement them regarding the assets. So at this moment, this is really fully open to add details and to improve these descriptions. Component Access Policy Control: I think the EPIC would not focus on payment matter but try to explain that as an owner of devices and IoT resources, I can define some criteria to give access right. In this case this could be a Social Network or Open Source Community approach to share devices and things with no commercial ASP, as you could provide access rights only for SMEs, or for eHealth applications despite your IoT Resources are not tagged as eHealth resources. Maybe you can refine this EPIC to describe that several criteria could be used to define access rights. This point should be discussed with the Security team during Turin meeting to check what kind of features they can provide. Quality of service control: this feature is clearly not included in any assets. Based on some comments from UA projects this point should be fundamental (to Instant Mobility project, this quality of service is expected for emergency concerns in a city, or to Safecity project to reach in the proper time some video resources in the city). But as we do not have any asset we can put the priority on "Should" and manage this issue later on (2nd round of FI-Ware backlog, or through the open calls if we know some other partners who could have this kind of asset). We have also holes in Process Automation or Data Handling, so we will not do everything now and if all IoT partners agree, we can delay it. But I think that Thales could have an asset to fulfill this requirement. We would wait one more week for their contributions to decide it. BR Thierry De : fiware-iot-bounces at lists.fi-ware.eu [mailto:fiware-iot-bounces at lists.fi-ware.eu] De la part de Guerra Sabrina Envoy? : lundi 5 septembre 2011 13:21 ? : 'fiware-iot at lists.fi-ware.eu' Cc : Bellifemine Fabio Luigi; Borean Claudio Objet : [Fiware-iot] First initial analysis of the IoT Assets mapping for the task 5.1 IoT Communications Hi, we've begun to analyze the list of assets related to the "IoT Communication" task submitted by the FI-WARE partners. Some initial considerations for the components are: * Component Connection Protocol Adapter - the better solution is that as many as possible protocols are supported by the IoT Services Enablement Platform, for this reason all the assets presented can be included into the implementation of the IoT SE Platform, provided that it's possible to translate them in a common internal form through the component Communication Protocol Abstraction Definition. * Component Communication Protocol Abstraction Definition - the epic for this component is different from the description included in the document "FI-WARE High-level Description". Our goal was to introduce a layer that allows an abstraction level for all Connection Protocol Adapters in order to communicate with the IoT SE Platform Core using a common internal language. The "templates", we are referring to in the document, are a kind of rules to translate any specific protocol into the common internal language and not a mechanism to generate Connection Protocol Adapters. This mechanism to automatically generate Connection Protocol Adapters is in any case very interesting and we could add it to the architecture document, if needed. * Component Access Policy Control - The second point of the epic for this component treats the access as a matter of payment (e.g. access only free services), while we intend the access as a matter of permissions to access resources. In our opinion these are different levels and they don't belong to the same component. * Component Quality of Service Control - From the grid it looks like that no asset has this functionality readily available, but since this component is not fundamental for a prototype of the IoT SE Platform, it can be left out or postponed in the future. For the other components we don't have specific considerations for the moment, but it looks like that Pangoo/M2MPlanet (by Orange) and Cumulocity (by NSN) are the assets that are more in line with our requirements. What do you think of this initial analysis of the assets? Are there any comments on these considerations? If you agree we could proceed with a more detailed analysis of the two proposed assets. Best regards, Sabrina Guerra __________________________________ Telecom Italia S.p.a. Strategia e Innovazione, Research & Trends Telefono +39 011 228 8359 Cellulare +39 331 600 1349 Questo messaggio e i suoi allegati sono indirizzati esclusivamente alle persone indicate. La diffusione, copia o qualsiasi altra azione derivante dalla conoscenza di queste informazioni sono rigorosamente vietate. Qualora abbiate ricevuto questo documento per errore siete cortesemente pregati di darne immediata comunicazione al mittente e di provvedere alla sua distruzione, Grazie. This e-mail and any attachments is confidential and may contain privileged information intended for the addressee(s) only. Dissemination, copying, printing or use by anybody else is unauthorised. If you are not the intended recipient, please delete this message and any attachments and advise the sender by return e-mail, Thanks. 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: image001.gif Type: image/gif Size: 677 bytes Desc: image001.gif URL: From lorant.farkas at nsn.com Tue Sep 6 12:10:08 2011 From: lorant.farkas at nsn.com (Farkas, Lorant (NSN - HU/Budapest)) Date: Tue, 6 Sep 2011 13:10:08 +0300 Subject: [Fiware-iot] IoT weekly meeting Message-ID: <93D28BDF64839C468B848D14227151A2023EE696@FIESEXC014.nsn-intra.net> When: 2011. szeptember 9. 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, Let's have our weekly meeting this time on Friday, because then we will have more information on the agenda for the GA. I propose the following topics: 1. Asset mapping - status update and feedback from the coordinator 2. Themes, epics, user stories - status update and feedback from the coordinator 3. Agenda for the GA and preparations we should make -we expect to have f2f meeting with DCM, ASE WP-s, I would initially make the recommendation to please read these chapters through until next week (we expect especially for DCM the concepts related to context elements, the publish/subscribe broker to generate discussions) -we expect to have f2f meeting with Security and I2ND WP-s Thanks & Br, Lorant Topic: FI-WARE IOT weekly Date: Friday, 9 September 2011 Time: 10:00, Europe Summer Time (Paris, GMT+02:00) Meeting Number: 707 203 206 Password: cool ------------------------------------------------------- To join the meeting online(Now from mobile devices!) ------------------------------------------------------- 1. Go to https://nsn.webex.com/nsn/j.php?ED=186331242&UID=483150557&PW=NYWFhZTNmZTFl&RT=MTgjMjM%3D 2. If requested, enter your name and email address. 3. If a password is required, enter the meeting password: cool 4. Click "Join". 5. If the meeting includes a teleconference, follow the instructions that appear on your screen. ------------------------------------------------------- To join the audio conference only ------------------------------------------------------- 58465 / 9369002 Argentina - Buenos Aires +54 11 5983 9400 (PRIMARY) or +54 11 4814 9373 Argentina - Cordoba +54 35 1568 2208 Australia - Sydney +61 28 014 7189 (PRIMARY) or +61 29 429 9664 Australia - Melbourne +61 38 739 4333 Austria +43 72 088 0245 Bahrain +97 31 619 9028 Belgium - Generic +32 1448 0116 Belgium - Diegem-Machelen +32 2710 3300 Brazil - Belo Horizonte +55 31 3956 0546 Brazil - Brazil +55 61 3717 2043 Brazil - Curitiba +55 41 3906 0826 Brazil - Manaus +55 92 3652 7576 Brazil - Rio De Janeiro +55 21 3958 0804 (PRIMARY) or +55 21 3431 1999 Brazil - Salvador +55 71 3717 5351 Brazil - Sao Paolo +55 11 5508 0630 Bulgaria +359 2491 7085 Canada - Ajax +1 90 5619 4346 Canada - Burnaby +1 60 4456 5897 Canada - Hamilton +1 905 581 0212 Canada - Mississauga +1 289 360 3950 Canada - Montreal +1 51 4789 9125 Canada - Ottawa +1 61 3800 0568 Chile - Santiago +56 2350 6485 China - Mainland +86 10 8405 5000 ext 1870 China - Beijing +86 10 8405 5000 ext 1870 China - Chengdu +86 28 8689 0188 ext 1870 China - Dongguan +86 0769 2240 2844 ext 1870 China - Guangzhou +86 20 8755 6190 ext 1870 China - Hangzhou +86 571 8722 0877 ext 1870 China - Hong Kong +852 259 70220 ext 1870 China - Kunming +86 871 362 2880 ext 1870 China - Shanghai +86 21 6101 1870 ext 1870 China - ShenZhen +86 755 8613 3688 ext 1870 China - Suzhou +86 512 6761 6166 ext 1870 China - Zhengzhou +86 371 6566 9768 ext 1870 Colombia +57 1640 7979 ext 444 Croatia +38 51 777 6122 Czech Republic +42 02 460 19300 Denmark +45 699 18450 (PRIMARY) or +45 3329 2882 Egypt +97 31 619 9028 (Bahrain nbr) Estonia +37 266 67297 Finland +358 7180 71870 France +33 17 061 7813 (PRIMARY) or +33 14 915 1553 Germany +49 89 5159 43800 Greece +30 21 1176 8207 (PRIMARY) or +30 21 1120 3677 Hungary - Budapest +36 17 009 888 Hungary - Kom?rom +36 20 884 2499 India 000 800 100 7777 Indonesia - Jakarta (Menara Mulia/Plaza Kuningan +62 21 2557 9102 Indonesia - Bandung +62 22 8427 5992 Indonesia - Medan +62 61 3001 2702 Indonesia - Semarang +62 24 3300 0702 Ireland +353 1526 2862 Israel +97 29 775 1700 Italy - Milan +39 024 004 2007 Italy - Rome +39 069 481 6656 Japan +81 3 4578 0230 (PRIMARY) or +81 3 5474 7979 Kuwait +97 31 619 9028 (Bahrain nbr) Latvia +37 16 765 2510 Lithuania +37 0 5205 8994 Luxembourg +352 2088 0106 Malaysia +60 323 029 009 Mexico - Mexico City +52 55 3686 9759 (PRIMARY) or +52 55 5261 7245 Mexico - Reynosa +52 89 9909 1555 Netherlands +31 79 346 5225 New Zealand +64 9306 6933 Norway - Oslo +47 21 548 223 Oman +97 31 619 9028 (Bahrain nbr) Pakistan +92 512 092 444 Panama +507 832 7981 Peru +51 1708 5370 (PRIMARY) or +51 1215 7650 Philippines +63 2754 1700 Poland - Warsaw +48 22 398 8116 Poland - Wroclaw +48 71 718 1215 Portugal +351 21 044 4698 Qatar +97 31 619 9028 (Bahrain nbr) Romania +40 36 440 3799 Russia +74 95 725 2706 Saudi Arabia +97 31 619 9028 (Bahrain nbr) Singapore +65 3103 1065 (PRIMARY) or +65 6723 2582 Slovakia +42 12 3300 6924 Slovenia +38 61 600 2713 South Africa - Johannesburg +27 1 0500 2221 South Africa - Pretoria +27 1 2004 2334 South Korea - Masan +82 5 5290 7690 South Korea - Seoul +82 2 2186 5088 Spain +349 1187 5929 Sweden +46 85 250 0862 (PRIMARY), +46 84 100 9299 Switzerland +41 44 279 7943 Taiwan +88 62 8175 9298 Thailand +66 2762 6750 Turkey +90 216 570 2345 Ukraine +38 044 520 2272 UK +44 12 5275 8334 UK - Camberley +44 12 5286 5849 UK - Church Crookham +44 12 5261 1100 UK - Huntingdon +44 14 8087 8220 (PRIMARY), +44 14 8044 4206 UK - London +44 20 3318 1924 United Arab Emirates +97 31 619 9028 (Bahrain nbr) USA - Alpharetta +1 770 871 3050 USA - Arizona +1 480 588 3748 USA - Atlanta +1 404 236 4550 USA - Atlanta Notheast +1 678 317 3165 USA - Austin/Round Rock +1 512 600 2027 USA - Belleville +1 973 547 7982 USA - Boca Raton +1 561 910 2843 USA - Boston +1 617 963 8320 (PRIMARY) or +1 781 993 4850 USA - Burlington +1 781 993 4850 USA - Calabasas +1 818 914 0215 USA - Canoga Park +1 818 914 0215 USA - Cary +1 919 655 1388 USA - Chelmsford/Littleton +1 978 679 0233 USA - Chicago +1 773 303 4710 USA - Dallas +1 214 269 7626 USA - Dallas/Fort Worth +1 214 270 0352 USA - Greenville, NC +1 252 329 1677 USA - Herndon +1 703 483 4485 USA - Johnson City +1 423 952 1545 USA - Kirkland +1 425 242 3113 USA - Miami +1 786 388 4150 or +1 786 329 7177 USA - Naperville +1 630 596 2203 USA - New Brunswick +1 732 579 6483 USA - New Century, KS +1 913 254 5900 USA - New York White Plains +1 914 368 0650 USA - New York Peekskill, White Plains +1 914 293 1885 USA - Palo Alto +1 650 644 1349 USA - Redmond +1 425 242 3113 USA - San Diego +1 858 769 5309 or +1 619 330 9699 USA - Sunnyvale +1 408 419 1750 USA - Washington D.C +1 202 552 4781 Vietnam +84 4 3724 6110 Yemen +97 31 619 9028 (Bahrain nbr) -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: meeting.ics Type: text/calendar Size: 9049 bytes Desc: not available URL: From rheras at tid.es Tue Sep 6 12:52:18 2011 From: rheras at tid.es (Ricardo de las Heras) Date: Tue, 06 Sep 2011 12:52:18 +0200 Subject: [Fiware-iot] First initial analysis of the IoT Assets mapping for the task 5.1 IoT Communications In-Reply-To: References: <36A93B31228D3B49B691AD31652BCAE9A5356033D7@GRFMBX702BA020.griffon.local> <36A93B31228D3B49B691AD31652BCAE9A53595673F@GRFMBX702BA020.griffon.local> Message-ID: <4E65FB62.5060502@tid.es> An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: image/gif Size: 677 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: OMA-TS-NGSI_Context_Management-V1_0-20100803-C.pdf Type: application/pdf Size: 393388 bytes Desc: not available URL: From thierry.nagellen at orange-ftgroup.com Tue Sep 6 13:46:36 2011 From: thierry.nagellen at orange-ftgroup.com (thierry.nagellen at orange-ftgroup.com) Date: Tue, 6 Sep 2011 13:46:36 +0200 Subject: [Fiware-iot] First initial analysis of the IoT Assets mapping for the task 5.1 IoT Communications In-Reply-To: <4E65FB62.5060502@tid.es> References: <36A93B31228D3B49B691AD31652BCAE9A5356033D7@GRFMBX702BA020.griffon.local> <36A93B31228D3B49B691AD31652BCAE9A53595673F@GRFMBX702BA020.griffon.local> <4E65FB62.5060502@tid.es> Message-ID: Dear Ricardo Maybe I missed a point or there is a misunderstanding. We have to deal here with communication protocols as NFC which could use different frequencies, 6LowPan or Zigbee, Bluetooth, etc... and NGSI try to formalize a standard to exchange context information with applications. In the case of the "component connection Protocol Adapter" the main issue is that lots of communication protocols are used by different devices and if we do not have this component we will not provide a common access to different types of devices, which deal with one or more IoT resources. As I understand NGSI, but I'm not an expert, it provides a common model with dedicated functionalities to define a context element. This is quite relevant for DCM to manage context but less useful for events description for example. But maybe my understanding of NGSI is too limited. Best regards Thierry De : Ricardo de las Heras [mailto:rheras at tid.es] Envoy? : mardi 6 septembre 2011 12:52 ? : NAGELLEN Thierry RD-BIZZ-SOP; sabrina.guerra at telecomitalia.it Cc : fiware-iot at lists.fi-ware.eu; fabioluigi.bellifemine at telecomitalia.it; claudio.borean at telecomitalia.it Objet : Re: [Fiware-iot] First initial analysis of the IoT Assets mapping for the task 5.1 IoT Communications Dear Sabrina, Thierry, regarding your first point: "Component Connection Protocol Adapter - the better solution is that as many as possible protocols are supported by the IoT Services Enablement Platform, for this reason all the assets presented can be included into the implementation of the IoT SE Platform, provided that it's possible to translate them in a common internal form through the component Communication Protocol Abstraction Definition." I'm not an expert on these type of protocols, but as far as I know within the WP6 (Contextual) they are going to use an the OMA standard TS-NGSI for the Context_Management. (http://www.openmobilealliance.org/technical/release_program/ose_archive.aspx) You can find attached a pdf with the NGSI specification. Indeed TI and NEC were very active on the definition of this standard, so it would be fine if we define it as the common language within WP5, maybe mapping the protocols used in the assets to NGSI, having clear advantages in order to communicate us with the rest of WPs, mainly with WP6. Furthermore, the WAC initiative (http://en.wikipedia.org/wiki/Wholesale_Applications_Community) fully support NGSI as well, so it is again a new point for reinforce this decision, with clear advantages for Fiware using this important OMA standard. I don't know what's your point of view, maybe Thierry you can discuss it with Juanjo Hierro, thanks, regards, Ricardo. -- ------------------------------------- Ricardo de las Heras M2M Research Project Manager E-mail: rheras at tid.es Phone1: (+34) 983 367625 Phone2 OCS: (+34) 91 31 29511 Phone3 Skype: (+34) 91 1878107 + Ext: 327 Telef?nica I+D ------------------------------------- thierry.nagellen at orange-ftgroup.com wrote: Hi Sabrina Thanks for your first analysis. We had slightly discussed the point of protocols IoT SE has to support to deal with different kind of things. I fully support your approach that the optimal way for us is to integrate the protocols through the assets we have because to implement all protocols will take lots of time and the main topic is how we can provide a common access. But in this case, partners would have to develop a dedicated interface to be integrated in the component "Connection Protocol Adapter". This should be a good point for the Open Specification and to target different Use Cases. Regarding EPICs which are different from the description of HLD deliverable, feel free to add a new EPIC to be in line with the deliverable and we would be able to discuss which one is the more critical and how we can put some priorities. We can have "several" EPIC per component and we can discuss which are the most valuable and how we could implement them regarding the assets. So at this moment, this is really fully open to add details and to improve these descriptions. Component Access Policy Control: I think the EPIC would not focus on payment matter but try to explain that as an owner of devices and IoT resources, I can define some criteria to give access right. In this case this could be a Social Network or Open Source Community approach to share devices and things with no commercial ASP, as you could provide access rights only for SMEs, or for eHealth applications despite your IoT Resources are not tagged as eHealth resources. Maybe you can refine this EPIC to describe that several criteria could be used to define access rights. This point should be discussed with the Security team during Turin meeting to check what kind of features they can provide. Quality of service control: this feature is clearly not included in any assets. Based on some comments from UA projects this point should be fundamental (to Instant Mobility project, this quality of service is expected for emergency concerns in a city, or to Safecity project to reach in the proper time some video resources in the city). But as we do not have any asset we can put the priority on "Should" and manage this issue later on (2nd round of FI-Ware backlog, or through the open calls if we know some other partners who could have this kind of asset). We have also holes in Process Automation or Data Handling, so we will not do everything now and if all IoT partners agree, we can delay it. But I think that Thales could have an asset to fulfill this requirement. We would wait one more week for their contributions to decide it. BR Thierry De : fiware-iot-bounces at lists.fi-ware.eu [mailto:fiware-iot-bounces at lists.fi-ware.eu] De la part de Guerra Sabrina Envoy? : lundi 5 septembre 2011 13:21 ? : 'fiware-iot at lists.fi-ware.eu' Cc : Bellifemine Fabio Luigi; Borean Claudio Objet : [Fiware-iot] First initial analysis of the IoT Assets mapping for the task 5.1 IoT Communications Hi, we've begun to analyze the list of assets related to the "IoT Communication" task submitted by the FI-WARE partners. Some initial considerations for the components are: * Component Connection Protocol Adapter - the better solution is that as many as possible protocols are supported by the IoT Services Enablement Platform, for this reason all the assets presented can be included into the implementation of the IoT SE Platform, provided that it's possible to translate them in a common internal form through the component Communication Protocol Abstraction Definition. * Component Communication Protocol Abstraction Definition - the epic for this component is different from the description included in the document "FI-WARE High-level Description". Our goal was to introduce a layer that allows an abstraction level for all Connection Protocol Adapters in order to communicate with the IoT SE Platform Core using a common internal language. The "templates", we are referring to in the document, are a kind of rules to translate any specific protocol into the common internal language and not a mechanism to generate Connection Protocol Adapters. This mechanism to automatically generate Connection Protocol Adapters is in any case very interesting and we could add it to the architecture document, if needed. * Component Access Policy Control - The second point of the epic for this component treats the access as a matter of payment (e.g. access only free services), while we intend the access as a matter of permissions to access resources. In our opinion these are different levels and they don't belong to the same component. * Component Quality of Service Control - From the grid it looks like that no asset has this functionality readily available, but since this component is not fundamental for a prototype of the IoT SE Platform, it can be left out or postponed in the future. For the other components we don't have specific considerations for the moment, but it looks like that Pangoo/M2MPlanet (by Orange) and Cumulocity (by NSN) are the assets that are more in line with our requirements. What do you think of this initial analysis of the assets? Are there any comments on these considerations? If you agree we could proceed with a more detailed analysis of the two proposed assets. Best regards, Sabrina Guerra __________________________________ Telecom Italia S.p.a. Strategia e Innovazione, Research & Trends Telefono +39 011 228 8359 Cellulare +39 331 600 1349 Questo messaggio e i suoi allegati sono indirizzati esclusivamente alle persone indicate. La diffusione, copia o qualsiasi altra azione derivante dalla conoscenza di queste informazioni sono rigorosamente vietate. Qualora abbiate ricevuto questo documento per errore siete cortesemente pregati di darne immediata comunicazione al mittente e di provvedere alla sua distruzione, Grazie. This e-mail and any attachments is confidential and may contain privileged information intended for the addressee(s) only. Dissemination, copying, printing or use by anybody else is unauthorised. If you are not the intended recipient, please delete this message and any attachments and advise the sender by return e-mail, Thanks. Rispetta l'ambiente. Non stampare questa mail se non ? necessario. ________________________________ Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra pol?tica de env?o y recepci?n de correo electr?nico en el enlace situado m?s abajo. This message is intended exclusively for its addressee. We only send and receive email on the basis of the terms set out at. http://www.tid.es/ES/PAGINAS/disclaimer.aspx -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.gif Type: image/gif Size: 677 bytes Desc: image001.gif URL: From rheras at tid.es Tue Sep 6 14:01:04 2011 From: rheras at tid.es (Ricardo de las Heras) Date: Tue, 06 Sep 2011 14:01:04 +0200 Subject: [Fiware-iot] First initial analysis of the IoT Assets mapping for the task 5.1 IoT Communications In-Reply-To: References: <36A93B31228D3B49B691AD31652BCAE9A5356033D7@GRFMBX702BA020.griffon.local> <36A93B31228D3B49B691AD31652BCAE9A53595673F@GRFMBX702BA020.griffon.local> <4E65FB62.5060502@tid.es> Message-ID: <4E660B80.4080406@tid.es> An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: image/gif Size: 677 bytes Desc: not available URL: From thierry.nagellen at orange-ftgroup.com Tue Sep 6 14:13:22 2011 From: thierry.nagellen at orange-ftgroup.com (thierry.nagellen at orange-ftgroup.com) Date: Tue, 6 Sep 2011 14:13:22 +0200 Subject: [Fiware-iot] First initial analysis of the IoT Assets mapping for the task 5.1 IoT Communications In-Reply-To: <4E660B80.4080406@tid.es> References: <36A93B31228D3B49B691AD31652BCAE9A5356033D7@GRFMBX702BA020.griffon.local> <36A93B31228D3B49B691AD31652BCAE9A53595673F@GRFMBX702BA020.griffon.local> <4E65FB62.5060502@tid.es> <4E660B80.4080406@tid.es> Message-ID: Hi Ricardo I fully agree with this approach and especially if our colleagues are implementing NSGI in DCM, this is a requirement for us to be compliant and to be able to exchange context information with any other FI-Ware GE. Somewhere the point target more IoT Data Handling components than the previous one "connection protocol adapter". We should have this kind of discussion with DCM during Turin meeting, as soon as the agenda will be frozen, we would be able to define the right contributors (maybe subset of DCM partners and IoT partners). BR Thierry De : Ricardo de las Heras [mailto:rheras at tid.es] Envoy? : mardi 6 septembre 2011 14:01 ? : NAGELLEN Thierry RD-BIZZ-SOP Cc : sabrina.guerra at telecomitalia.it; fiware-iot at lists.fi-ware.eu; fabioluigi.bellifemine at telecomitalia.it; claudio.borean at telecomitalia.it Objet : Re: [Fiware-iot] First initial analysis of the IoT Assets mapping for the task 5.1 IoT Communications Dear Thierry, yes, you're right regarding the issue that we have to deal with a broad type of protocols in order to communicate sensors, actuators, devices with a gateway. But my question was beyond this step, when we have to specify a protocol for interchanging data between every gateway and the IoT platform (using SensorAPI for example in the case of IDAS asset). At this level and for interchanging data with context awareness system or other external applications, then is where I tried to explain that could be useful to include the protocol NGSI as a reference protocol of the IoT WP5. Maybe some of our colleagues from NEC or TI can provide us more background with it, but NGSI seems to be quite flexible and direct in order to allow us to map the existent protocols in every asset to the NGSI standard. Sorry if there is any mistake in the details of my explaination. ISIS asset (NEC) for example provides an API interface based on NGSI. So this could be a perfect example of it. cheers, Ricardo. thierry.nagellen at orange-ftgroup.com wrote: Dear Ricardo Maybe I missed a point or there is a misunderstanding. We have to deal here with communication protocols as NFC which could use different frequencies, 6LowPan or Zigbee, Bluetooth, etc... and NGSI try to formalize a standard to exchange context information with applications. In the case of the "component connection Protocol Adapter" the main issue is that lots of communication protocols are used by different devices and if we do not have this component we will not provide a common access to different types of devices, which deal with one or more IoT resources. As I understand NGSI, but I'm not an expert, it provides a common model with dedicated functionalities to define a context element. This is quite relevant for DCM to manage context but less useful for events description for example. But maybe my understanding of NGSI is too limited. Best regards Thierry De : Ricardo de las Heras [mailto:rheras at tid.es] Envoy? : mardi 6 septembre 2011 12:52 ? : NAGELLEN Thierry RD-BIZZ-SOP; sabrina.guerra at telecomitalia.it Cc : fiware-iot at lists.fi-ware.eu; fabioluigi.bellifemine at telecomitalia.it; claudio.borean at telecomitalia.it Objet : Re: [Fiware-iot] First initial analysis of the IoT Assets mapping for the task 5.1 IoT Communications Dear Sabrina, Thierry, regarding your first point: "Component Connection Protocol Adapter - the better solution is that as many as possible protocols are supported by the IoT Services Enablement Platform, for this reason all the assets presented can be included into the implementation of the IoT SE Platform, provided that it's possible to translate them in a common internal form through the component Communication Protocol Abstraction Definition." I'm not an expert on these type of protocols, but as far as I know within the WP6 (Contextual) they are going to use an the OMA standard TS-NGSI for the Context_Management. (http://www.openmobilealliance.org/technical/release_program/ose_archive.aspx) You can find attached a pdf with the NGSI specification. Indeed TI and NEC were very active on the definition of this standard, so it would be fine if we define it as the common language within WP5, maybe mapping the protocols used in the assets to NGSI, having clear advantages in order to communicate us with the rest of WPs, mainly with WP6. Furthermore, the WAC initiative (http://en.wikipedia.org/wiki/Wholesale_Applications_Community) fully support NGSI as well, so it is again a new point for reinforce this decision, with clear advantages for Fiware using this important OMA standard. I don't know what's your point of view, maybe Thierry you can discuss it with Juanjo Hierro, thanks, regards, Ricardo. -- ------------------------------------- Ricardo de las Heras M2M Research Project Manager E-mail: rheras at tid.es Phone1: (+34) 983 367625 Phone2 OCS: (+34) 91 31 29511 Phone3 Skype: (+34) 91 1878107 + Ext: 327 Telef?nica I+D ------------------------------------- thierry.nagellen at orange-ftgroup.com wrote: Hi Sabrina Thanks for your first analysis. We had slightly discussed the point of protocols IoT SE has to support to deal with different kind of things. I fully support your approach that the optimal way for us is to integrate the protocols through the assets we have because to implement all protocols will take lots of time and the main topic is how we can provide a common access. But in this case, partners would have to develop a dedicated interface to be integrated in the component "Connection Protocol Adapter". This should be a good point for the Open Specification and to target different Use Cases. Regarding EPICs which are different from the description of HLD deliverable, feel free to add a new EPIC to be in line with the deliverable and we would be able to discuss which one is the more critical and how we can put some priorities. We can have "several" EPIC per component and we can discuss which are the most valuable and how we could implement them regarding the assets. So at this moment, this is really fully open to add details and to improve these descriptions. Component Access Policy Control: I think the EPIC would not focus on payment matter but try to explain that as an owner of devices and IoT resources, I can define some criteria to give access right. In this case this could be a Social Network or Open Source Community approach to share devices and things with no commercial ASP, as you could provide access rights only for SMEs, or for eHealth applications despite your IoT Resources are not tagged as eHealth resources. Maybe you can refine this EPIC to describe that several criteria could be used to define access rights. This point should be discussed with the Security team during Turin meeting to check what kind of features they can provide. Quality of service control: this feature is clearly not included in any assets. Based on some comments from UA projects this point should be fundamental (to Instant Mobility project, this quality of service is expected for emergency concerns in a city, or to Safecity project to reach in the proper time some video resources in the city). But as we do not have any asset we can put the priority on "Should" and manage this issue later on (2nd round of FI-Ware backlog, or through the open calls if we know some other partners who could have this kind of asset). We have also holes in Process Automation or Data Handling, so we will not do everything now and if all IoT partners agree, we can delay it. But I think that Thales could have an asset to fulfill this requirement. We would wait one more week for their contributions to decide it. BR Thierry De : fiware-iot-bounces at lists.fi-ware.eu [mailto:fiware-iot-bounces at lists.fi-ware.eu] De la part de Guerra Sabrina Envoy? : lundi 5 septembre 2011 13:21 ? : 'fiware-iot at lists.fi-ware.eu' Cc : Bellifemine Fabio Luigi; Borean Claudio Objet : [Fiware-iot] First initial analysis of the IoT Assets mapping for the task 5.1 IoT Communications Hi, we've begun to analyze the list of assets related to the "IoT Communication" task submitted by the FI-WARE partners. Some initial considerations for the components are: * Component Connection Protocol Adapter - the better solution is that as many as possible protocols are supported by the IoT Services Enablement Platform, for this reason all the assets presented can be included into the implementation of the IoT SE Platform, provided that it's possible to translate them in a common internal form through the component Communication Protocol Abstraction Definition. * Component Communication Protocol Abstraction Definition - the epic for this component is different from the description included in the document "FI-WARE High-level Description". Our goal was to introduce a layer that allows an abstraction level for all Connection Protocol Adapters in order to communicate with the IoT SE Platform Core using a common internal language. The "templates", we are referring to in the document, are a kind of rules to translate any specific protocol into the common internal language and not a mechanism to generate Connection Protocol Adapters. This mechanism to automatically generate Connection Protocol Adapters is in any case very interesting and we could add it to the architecture document, if needed. * Component Access Policy Control - The second point of the epic for this component treats the access as a matter of payment (e.g. access only free services), while we intend the access as a matter of permissions to access resources. In our opinion these are different levels and they don't belong to the same component. * Component Quality of Service Control - From the grid it looks like that no asset has this functionality readily available, but since this component is not fundamental for a prototype of the IoT SE Platform, it can be left out or postponed in the future. For the other components we don't have specific considerations for the moment, but it looks like that Pangoo/M2MPlanet (by Orange) and Cumulocity (by NSN) are the assets that are more in line with our requirements. What do you think of this initial analysis of the assets? Are there any comments on these considerations? If you agree we could proceed with a more detailed analysis of the two proposed assets. Best regards, Sabrina Guerra __________________________________ Telecom Italia S.p.a. Strategia e Innovazione, Research & Trends Telefono +39 011 228 8359 Cellulare +39 331 600 1349 Questo messaggio e i suoi allegati sono indirizzati esclusivamente alle persone indicate. La diffusione, copia o qualsiasi altra azione derivante dalla conoscenza di queste informazioni sono rigorosamente vietate. Qualora abbiate ricevuto questo documento per errore siete cortesemente pregati di darne immediata comunicazione al mittente e di provvedere alla sua distruzione, Grazie. This e-mail and any attachments is confidential and may contain privileged information intended for the addressee(s) only. Dissemination, copying, printing or use by anybody else is unauthorised. If you are not the intended recipient, please delete this message and any attachments and advise the sender by return e-mail, Thanks. Rispetta l'ambiente. Non stampare questa mail se non ? necessario. ________________________________ 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 -- ------------------------------------- Ricardo de las Heras M2M Research Project Manager E-mail: rheras at tid.es Phone1: (+34) 983 367625 Phone2 OCS: (+34) 91 31 29511 Phone3 Skype: (+34) 91 1878107 + Ext: 327 Telef?nica I+D ------------------------------------- ________________________________ Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra pol?tica de env?o y recepci?n de correo electr?nico en el enlace situado m?s abajo. This message is intended exclusively for its addressee. We only send and receive email on the basis of the terms set out at. http://www.tid.es/ES/PAGINAS/disclaimer.aspx -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.gif Type: image/gif Size: 677 bytes Desc: image001.gif URL: From lorant.farkas at nsn.com Tue Sep 6 15:18:12 2011 From: lorant.farkas at nsn.com (Farkas, Lorant (NSN - HU/Budapest)) Date: Tue, 6 Sep 2011 16:18:12 +0300 Subject: [Fiware-iot] Updated: IoT weekly meeting Message-ID: <93D28BDF64839C468B848D14227151A2023EE899@FIESEXC014.nsn-intra.net> When: 2011. szeptember 8. 11:00-12:00 (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 modification of the date and time. Webex, bridge details and proposed agenda items are unchanged. Thanks & Br, Lorant Dear All, Let's have our weekly meeting this time on Friday, because then we will have more information on the agenda for the GA. I propose the following topics: 1. Asset mapping - status update and feedback from the coordinator 2. Themes, epics, user stories - status update and feedback from the coordinator 3. Agenda for the GA and preparations we should make -we expect to have f2f meeting with DCM, ASE WP-s, I would initially make the recommendation to please read these chapters through until next week (we expect especially for DCM the concepts related to context elements, the publish/subscribe broker to generate discussions) -we expect to have f2f meeting with Security and I2ND WP-s Thanks & Br, Lorant Topic: FI-WARE IOT weekly Date: Thursday, 8 September 2011 Time: 11:00, Europe Summer Time (Paris, GMT+02:00) Meeting Number: 707 203 206 Password: cool ------------------------------------------------------- To join the meeting online(Now from mobile devices!) ------------------------------------------------------- 1. Go to https://nsn.webex.com/nsn/j.php?ED=186331242&UID=483150557&PW=NYWFhZTNmZTFl&RT=MTgjMjM%3D 2. If requested, enter your name and email address. 3. If a password is required, enter the meeting password: cool 4. Click "Join". 5. If the meeting includes a teleconference, follow the instructions that appear on your screen. ------------------------------------------------------- To join the audio conference only ------------------------------------------------------- 58465 / 9369002 Argentina - Buenos Aires +54 11 5983 9400 (PRIMARY) or +54 11 4814 9373 Argentina - Cordoba +54 35 1568 2208 Australia - Sydney +61 28 014 7189 (PRIMARY) or +61 29 429 9664 Australia - Melbourne +61 38 739 4333 Austria +43 72 088 0245 Bahrain +97 31 619 9028 Belgium - Generic +32 1448 0116 Belgium - Diegem-Machelen +32 2710 3300 Brazil - Belo Horizonte +55 31 3956 0546 Brazil - Brazil +55 61 3717 2043 Brazil - Curitiba +55 41 3906 0826 Brazil - Manaus +55 92 3652 7576 Brazil - Rio De Janeiro +55 21 3958 0804 (PRIMARY) or +55 21 3431 1999 Brazil - Salvador +55 71 3717 5351 Brazil - Sao Paolo +55 11 5508 0630 Bulgaria +359 2491 7085 Canada - Ajax +1 90 5619 4346 Canada - Burnaby +1 60 4456 5897 Canada - Hamilton +1 905 581 0212 Canada - Mississauga +1 289 360 3950 Canada - Montreal +1 51 4789 9125 Canada - Ottawa +1 61 3800 0568 Chile - Santiago +56 2350 6485 China - Mainland +86 10 8405 5000 ext 1870 China - Beijing +86 10 8405 5000 ext 1870 China - Chengdu +86 28 8689 0188 ext 1870 China - Dongguan +86 0769 2240 2844 ext 1870 China - Guangzhou +86 20 8755 6190 ext 1870 China - Hangzhou +86 571 8722 0877 ext 1870 China - Hong Kong +852 259 70220 ext 1870 China - Kunming +86 871 362 2880 ext 1870 China - Shanghai +86 21 6101 1870 ext 1870 China - ShenZhen +86 755 8613 3688 ext 1870 China - Suzhou +86 512 6761 6166 ext 1870 China - Zhengzhou +86 371 6566 9768 ext 1870 Colombia +57 1640 7979 ext 444 Croatia +38 51 777 6122 Czech Republic +42 02 460 19300 Denmark +45 699 18450 (PRIMARY) or +45 3329 2882 Egypt +97 31 619 9028 (Bahrain nbr) Estonia +37 266 67297 Finland +358 7180 71870 France +33 17 061 7813 (PRIMARY) or +33 14 915 1553 Germany +49 89 5159 43800 Greece +30 21 1176 8207 (PRIMARY) or +30 21 1120 3677 Hungary - Budapest +36 17 009 888 Hungary - Kom?rom +36 20 884 2499 India 000 800 100 7777 Indonesia - Jakarta (Menara Mulia/Plaza Kuningan +62 21 2557 9102 Indonesia - Bandung +62 22 8427 5992 Indonesia - Medan +62 61 3001 2702 Indonesia - Semarang +62 24 3300 0702 Ireland +353 1526 2862 Israel +97 29 775 1700 Italy - Milan +39 024 004 2007 Italy - Rome +39 069 481 6656 Japan +81 3 4578 0230 (PRIMARY) or +81 3 5474 7979 Kuwait +97 31 619 9028 (Bahrain nbr) Latvia +37 16 765 2510 Lithuania +37 0 5205 8994 Luxembourg +352 2088 0106 Malaysia +60 323 029 009 Mexico - Mexico City +52 55 3686 9759 (PRIMARY) or +52 55 5261 7245 Mexico - Reynosa +52 89 9909 1555 Netherlands +31 79 346 5225 New Zealand +64 9306 6933 Norway - Oslo +47 21 548 223 Oman +97 31 619 9028 (Bahrain nbr) Pakistan +92 512 092 444 Panama +507 832 7981 Peru +51 1708 5370 (PRIMARY) or +51 1215 7650 Philippines +63 2754 1700 Poland - Warsaw +48 22 398 8116 Poland - Wroclaw +48 71 718 1215 Portugal +351 21 044 4698 Qatar +97 31 619 9028 (Bahrain nbr) Romania +40 36 440 3799 Russia +74 95 725 2706 Saudi Arabia +97 31 619 9028 (Bahrain nbr) Singapore +65 3103 1065 (PRIMARY) or +65 6723 2582 Slovakia +42 12 3300 6924 Slovenia +38 61 600 2713 South Africa - Johannesburg +27 1 0500 2221 South Africa - Pretoria +27 1 2004 2334 South Korea - Masan +82 5 5290 7690 South Korea - Seoul +82 2 2186 5088 Spain +349 1187 5929 Sweden +46 85 250 0862 (PRIMARY), +46 84 100 9299 Switzerland +41 44 279 7943 Taiwan +88 62 8175 9298 Thailand +66 2762 6750 Turkey +90 216 570 2345 Ukraine +38 044 520 2272 UK +44 12 5275 8334 UK - Camberley +44 12 5286 5849 UK - Church Crookham +44 12 5261 1100 UK - Huntingdon +44 14 8087 8220 (PRIMARY), +44 14 8044 4206 UK - London +44 20 3318 1924 United Arab Emirates +97 31 619 9028 (Bahrain nbr) USA - Alpharetta +1 770 871 3050 USA - Arizona +1 480 588 3748 USA - Atlanta +1 404 236 4550 USA - Atlanta Notheast +1 678 317 3165 USA - Austin/Round Rock +1 512 600 2027 USA - Belleville +1 973 547 7982 USA - Boca Raton +1 561 910 2843 USA - Boston +1 617 963 8320 (PRIMARY) or +1 781 993 4850 USA - Burlington +1 781 993 4850 USA - Calabasas +1 818 914 0215 USA - Canoga Park +1 818 914 0215 USA - Cary +1 919 655 1388 USA - Chelmsford/Littleton +1 978 679 0233 USA - Chicago +1 773 303 4710 USA - Dallas +1 214 269 7626 USA - Dallas/Fort Worth +1 214 270 0352 USA - Greenville, NC +1 252 329 1677 USA - Herndon +1 703 483 4485 USA - Johnson City +1 423 952 1545 USA - Kirkland +1 425 242 3113 USA - Miami +1 786 388 4150 or +1 786 329 7177 USA - Naperville +1 630 596 2203 USA - New Brunswick +1 732 579 6483 USA - New Century, KS +1 913 254 5900 USA - New York White Plains +1 914 368 0650 USA - New York Peekskill, White Plains +1 914 293 1885 USA - Palo Alto +1 650 644 1349 USA - Redmond +1 425 242 3113 USA - San Diego +1 858 769 5309 or +1 619 330 9699 USA - Sunnyvale +1 408 419 1750 USA - Washington D.C +1 202 552 4781 Vietnam +84 4 3724 6110 Yemen +97 31 619 9028 (Bahrain nbr) -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: meeting.ics Type: text/calendar Size: 9225 bytes Desc: not available URL: From Ernoe.Kovacs at neclab.eu Tue Sep 6 16:03:02 2011 From: Ernoe.Kovacs at neclab.eu (Ernoe Kovacs) Date: Tue, 6 Sep 2011 14:03:02 +0000 Subject: [Fiware-iot] First initial analysis of the IoT Assets mapping for the task 5.1 IoT Communications In-Reply-To: <4E660B80.4080406@tid.es> References: <36A93B31228D3B49B691AD31652BCAE9A5356033D7@GRFMBX702BA020.griffon.local> <36A93B31228D3B49B691AD31652BCAE9A53595673F@GRFMBX702BA020.griffon.local> <4E65FB62.5060502@tid.es> <4E660B80.4080406@tid.es> Message-ID: <8152E2132B13FB488CFD1947E2DEF19C1CFA4B92@DAPHNIS.office.hd> Hi all, fast reply here, I provide more background information to study later on. (a) Original discussion "Connection Protocol Adapter" or "component connection Protocol Adapter" I think we are all sharing the same idea here. We have very heterogeneous M2M area network protocols including very different data models. We need to map this into a common protocol model and common data model. Let me go one step deeper: Sensor support very different kind of interactions. Some are waiting to be queried. Some send their information periodically, some send the information when a substantial change has happened, some have a management interface to configure their behavior, etc. etc. Some needs sessions, some only have one shot queries that include authentication each time they are called. I fear you find anything that can be imagined on that level An abstraction layer needs to map all these protocols into a single one. This single one is the language to talk inside of the systems. The "Connection Protocol Adapter" are the software modules that - map between the real protocol on the M2M Area network and the high-level protocol. - fill the gap between what the sensor offers and what the high-level protocol requests. For example, if the high level protocol supports subscriptions and the lwo level one not, either the "connection protocol adapter" or the "Abstraction layer" need to provide the needed functionality... (b) OMA NGSI In the sense of the discussion under (a), OMA NGSI can be the higher level protocol that the abstraction layer supports. OMA NGSI supports updates, queries, subscriptions, and notifications. (c) OMA NGSI as Exposure API For interacting with external systems like WP6, OMA NGSI is a standardized API with comparable rich set of operation. So we can use it as an exposure API towards applications. It also has a data model based on entities, attributes and meta-data about them. Note: The exposure API can be used on the IoT Device, on the IoT Gateway or on the IoT Core. (d) OMA NGSI and IoT Gateways-2-IoT Core Communication Besides the data flow services (update, query, subscribe, notify), OMA NGSI has a small set of primitives that enables two systems to exchange meta-data about the contained objects. So a IoT gateway can register with the IoT Core and inform them that e.g it is currently managing 1 RFID readers, will sent information about "hasSeen RFID Tags" and has a GPS receiver. Yes, OMA NGSI can be used for that as well. I am expecting that we might extend the information exchanged between IoT GW and IoT Core, but OMA NGSI is a starting point. Our ISIS system implements large parts of the OMA NGSI features. @Thierry: You are right this is different to the NFC protocol , 6LowPAN, ZigBee. The Connection Protocol Adapter can handle this heterogenity. I am reasonable sure that FIWare will not try to overcome the heterogeneity on Layer 1 (Radio) or L2 (Data Link). IMHO, the approach cannot be to map either directly into each other (nightmare, n x m) or into a higher level protocol ( n x 1). The alter approach is what we are suggesting. In our ISIS system we have shown it can work... - Ern? From: fiware-iot-bounces at lists.fi-ware.eu [mailto:fiware-iot-bounces at lists.fi-ware.eu] On Behalf Of Ricardo de las Heras Sent: Dienstag, 6. September 2011 14:01 To: thierry.nagellen at orange-ftgroup.com Cc: fabioluigi.bellifemine at telecomitalia.it; claudio.borean at telecomitalia.it; fiware-iot at lists.fi-ware.eu Subject: Re: [Fiware-iot] First initial analysis of the IoT Assets mapping for the task 5.1 IoT Communications Dear Thierry, yes, you're right regarding the issue that we have to deal with a broad type of protocols in order to communicate sensors, actuators, devices with a gateway. But my question was beyond this step, when we have to specify a protocol for interchanging data between every gateway and the IoT platform (using SensorAPI for example in the case of IDAS asset). At this level and for interchanging data with context awareness system or other external applications, then is where I tried to explain that could be useful to include the protocol NGSI as a reference protocol of the IoT WP5. Maybe some of our colleagues from NEC or TI can provide us more background with it, but NGSI seems to be quite flexible and direct in order to allow us to map the existent protocols in every asset to the NGSI standard. Sorry if there is any mistake in the details of my explaination. ISIS asset (NEC) for example provides an API interface based on NGSI. So this could be a perfect example of it. cheers, Ricardo. thierry.nagellen at orange-ftgroup.com wrote: Dear Ricardo Maybe I missed a point or there is a misunderstanding. We have to deal here with communication protocols as NFC which could use different frequencies, 6LowPan or Zigbee, Bluetooth, etc... and NGSI try to formalize a standard to exchange context information with applications. In the case of the "component connection Protocol Adapter" the main issue is that lots of communication protocols are used by different devices and if we do not have this component we will not provide a common access to different types of devices, which deal with one or more IoT resources. As I understand NGSI, but I'm not an expert, it provides a common model with dedicated functionalities to define a context element. This is quite relevant for DCM to manage context but less useful for events description for example. But maybe my understanding of NGSI is too limited. Best regards Thierry De : Ricardo de las Heras [mailto:rheras at tid.es] Envoy? : mardi 6 septembre 2011 12:52 ? : NAGELLEN Thierry RD-BIZZ-SOP; sabrina.guerra at telecomitalia.it Cc : fiware-iot at lists.fi-ware.eu; fabioluigi.bellifemine at telecomitalia.it; claudio.borean at telecomitalia.it Objet : Re: [Fiware-iot] First initial analysis of the IoT Assets mapping for the task 5.1 IoT Communications Dear Sabrina, Thierry, regarding your first point: "Component Connection Protocol Adapter - the better solution is that as many as possible protocols are supported by the IoT Services Enablement Platform, for this reason all the assets presented can be included into the implementation of the IoT SE Platform, provided that it's possible to translate them in a common internal form through the component Communication Protocol Abstraction Definition." I'm not an expert on these type of protocols, but as far as I know within the WP6 (Contextual) they are going to use an the OMA standard TS-NGSI for the Context_Management. (http://www.openmobilealliance.org/technical/release_program/ose_archive.aspx) You can find attached a pdf with the NGSI specification. Indeed TI and NEC were very active on the definition of this standard, so it would be fine if we define it as the common language within WP5, maybe mapping the protocols used in the assets to NGSI, having clear advantages in order to communicate us with the rest of WPs, mainly with WP6. Furthermore, the WAC initiative (http://en.wikipedia.org/wiki/Wholesale_Applications_Community) fully support NGSI as well, so it is again a new point for reinforce this decision, with clear advantages for Fiware using this important OMA standard. I don't know what's your point of view, maybe Thierry you can discuss it with Juanjo Hierro, thanks, regards, Ricardo. -- ------------------------------------- Ricardo de las Heras M2M Research Project Manager E-mail: rheras at tid.es Phone1: (+34) 983 367625 Phone2 OCS: (+34) 91 31 29511 Phone3 Skype: (+34) 91 1878107 + Ext: 327 Telef?nica I+D ------------------------------------- thierry.nagellen at orange-ftgroup.com wrote: Hi Sabrina Thanks for your first analysis. We had slightly discussed the point of protocols IoT SE has to support to deal with different kind of things. I fully support your approach that the optimal way for us is to integrate the protocols through the assets we have because to implement all protocols will take lots of time and the main topic is how we can provide a common access. But in this case, partners would have to develop a dedicated interface to be integrated in the component "Connection Protocol Adapter". This should be a good point for the Open Specification and to target different Use Cases. Regarding EPICs which are different from the description of HLD deliverable, feel free to add a new EPIC to be in line with the deliverable and we would be able to discuss which one is the more critical and how we can put some priorities. We can have "several" EPIC per component and we can discuss which are the most valuable and how we could implement them regarding the assets. So at this moment, this is really fully open to add details and to improve these descriptions. Component Access Policy Control: I think the EPIC would not focus on payment matter but try to explain that as an owner of devices and IoT resources, I can define some criteria to give access right. In this case this could be a Social Network or Open Source Community approach to share devices and things with no commercial ASP, as you could provide access rights only for SMEs, or for eHealth applications despite your IoT Resources are not tagged as eHealth resources. Maybe you can refine this EPIC to describe that several criteria could be used to define access rights. This point should be discussed with the Security team during Turin meeting to check what kind of features they can provide. Quality of service control: this feature is clearly not included in any assets. Based on some comments from UA projects this point should be fundamental (to Instant Mobility project, this quality of service is expected for emergency concerns in a city, or to Safecity project to reach in the proper time some video resources in the city). But as we do not have any asset we can put the priority on "Should" and manage this issue later on (2nd round of FI-Ware backlog, or through the open calls if we know some other partners who could have this kind of asset). We have also holes in Process Automation or Data Handling, so we will not do everything now and if all IoT partners agree, we can delay it. But I think that Thales could have an asset to fulfill this requirement. We would wait one more week for their contributions to decide it. BR Thierry De : fiware-iot-bounces at lists.fi-ware.eu [mailto:fiware-iot-bounces at lists.fi-ware.eu] De la part de Guerra Sabrina Envoy? : lundi 5 septembre 2011 13:21 ? : 'fiware-iot at lists.fi-ware.eu' Cc : Bellifemine Fabio Luigi; Borean Claudio Objet : [Fiware-iot] First initial analysis of the IoT Assets mapping for the task 5.1 IoT Communications Hi, we've begun to analyze the list of assets related to the "IoT Communication" task submitted by the FI-WARE partners. Some initial considerations for the components are: * Component Connection Protocol Adapter - the better solution is that as many as possible protocols are supported by the IoT Services Enablement Platform, for this reason all the assets presented can be included into the implementation of the IoT SE Platform, provided that it's possible to translate them in a common internal form through the component Communication Protocol Abstraction Definition. * Component Communication Protocol Abstraction Definition - the epic for this component is different from the description included in the document "FI-WARE High-level Description". Our goal was to introduce a layer that allows an abstraction level for all Connection Protocol Adapters in order to communicate with the IoT SE Platform Core using a common internal language. The "templates", we are referring to in the document, are a kind of rules to translate any specific protocol into the common internal language and not a mechanism to generate Connection Protocol Adapters. This mechanism to automatically generate Connection Protocol Adapters is in any case very interesting and we could add it to the architecture document, if needed. * Component Access Policy Control - The second point of the epic for this component treats the access as a matter of payment (e.g. access only free services), while we intend the access as a matter of permissions to access resources. In our opinion these are different levels and they don't belong to the same component. * Component Quality of Service Control - From the grid it looks like that no asset has this functionality readily available, but since this component is not fundamental for a prototype of the IoT SE Platform, it can be left out or postponed in the future. For the other components we don't have specific considerations for the moment, but it looks like that Pangoo/M2MPlanet (by Orange) and Cumulocity (by NSN) are the assets that are more in line with our requirements. What do you think of this initial analysis of the assets? Are there any comments on these considerations? If you agree we could proceed with a more detailed analysis of the two proposed assets. Best regards, Sabrina Guerra __________________________________ Telecom Italia S.p.a. Strategia e Innovazione, Research & Trends Telefono +39 011 228 8359 Cellulare +39 331 600 1349 Questo messaggio e i suoi allegati sono indirizzati esclusivamente alle persone indicate. La diffusione, copia o qualsiasi altra azione derivante dalla conoscenza di queste informazioni sono rigorosamente vietate. Qualora abbiate ricevuto questo documento per errore siete cortesemente pregati di darne immediata comunicazione al mittente e di provvedere alla sua distruzione, Grazie. This e-mail and any attachments is confidential and may contain privileged information intended for the addressee(s) only. Dissemination, copying, printing or use by anybody else is unauthorised. If you are not the intended recipient, please delete this message and any attachments and advise the sender by return e-mail, Thanks. [rispetta l'ambiente]Rispetta l'ambiente. Non stampare questa mail se non ? necessario. ________________________________ 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 -- ------------------------------------- Ricardo de las Heras M2M Research Project Manager E-mail: rheras at tid.es Phone1: (+34) 983 367625 Phone2 OCS: (+34) 91 31 29511 Phone3 Skype: (+34) 91 1878107 + Ext: 327 Telef?nica I+D ------------------------------------- ________________________________ Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra pol?tica de env?o y recepci?n de correo electr?nico en el enlace situado m?s abajo. This message is intended exclusively for its addressee. We only send and receive email on the basis of the terms set out at. http://www.tid.es/ES/PAGINAS/disclaimer.aspx -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.gif Type: image/gif Size: 677 bytes Desc: image001.gif URL: From Ernoe.Kovacs at neclab.eu Thu Sep 8 09:06:16 2011 From: Ernoe.Kovacs at neclab.eu (Ernoe Kovacs) Date: Thu, 8 Sep 2011 07:06:16 +0000 Subject: [Fiware-iot] OMA NGSI API Message-ID: <8152E2132B13FB488CFD1947E2DEF19C1CFA6ABB@DAPHNIS.office.hd> Dear all, yesterday I promised some more information on the OMA NGSI APIs. You can now find here FI-Ware IoT -> Docs -> Uncategorized Submissions https://forge.fi-ware.eu/docman/?group_id=11 (a) OMA NGSI Info - Document with links to the standard documents and related information There is a good OMA NGSI overview presentation referenced. I recommend to read this. (b) Paper and presentation at ICIN'2010 Gives more insights into the Ctx API which we think is relevant for IoT - Ern? From: fiware-iot-bounces at lists.fi-ware.eu [mailto:fiware-iot-bounces at lists.fi-ware.eu] On Behalf Of Ernoe Kovacs Sent: Dienstag, 6. September 2011 16:03 To: Ricardo de las Heras; thierry.nagellen at orange-ftgroup.com Cc: fiware-iot at lists.fi-ware.eu; fabioluigi.bellifemine at telecomitalia.it; claudio.borean at telecomitalia.it Subject: Re: [Fiware-iot] First initial analysis of the IoT Assets mapping for the task 5.1 IoT Communications Hi all, fast reply here, I provide more background information to study later on. (a) Original discussion "Connection Protocol Adapter" or "component connection Protocol Adapter" I think we are all sharing the same idea here. We have very heterogeneous M2M area network protocols including very different data models. We need to map this into a common protocol model and common data model. Let me go one step deeper: Sensor support very different kind of interactions. Some are waiting to be queried. Some send their information periodically, some send the information when a substantial change has happened, some have a management interface to configure their behavior, etc. etc. Some needs sessions, some only have one shot queries that include authentication each time they are called. I fear you find anything that can be imagined on that level An abstraction layer needs to map all these protocols into a single one. This single one is the language to talk inside of the systems. The "Connection Protocol Adapter" are the software modules that - map between the real protocol on the M2M Area network and the high-level protocol. - fill the gap between what the sensor offers and what the high-level protocol requests. For example, if the high level protocol supports subscriptions and the lwo level one not, either the "connection protocol adapter" or the "Abstraction layer" need to provide the needed functionality... (b) OMA NGSI In the sense of the discussion under (a), OMA NGSI can be the higher level protocol that the abstraction layer supports. OMA NGSI supports updates, queries, subscriptions, and notifications. (c) OMA NGSI as Exposure API For interacting with external systems like WP6, OMA NGSI is a standardized API with comparable rich set of operation. So we can use it as an exposure API towards applications. It also has a data model based on entities, attributes and meta-data about them. Note: The exposure API can be used on the IoT Device, on the IoT Gateway or on the IoT Core. (d) OMA NGSI and IoT Gateways-2-IoT Core Communication Besides the data flow services (update, query, subscribe, notify), OMA NGSI has a small set of primitives that enables two systems to exchange meta-data about the contained objects. So a IoT gateway can register with the IoT Core and inform them that e.g it is currently managing 1 RFID readers, will sent information about "hasSeen RFID Tags" and has a GPS receiver. Yes, OMA NGSI can be used for that as well. I am expecting that we might extend the information exchanged between IoT GW and IoT Core, but OMA NGSI is a starting point. Our ISIS system implements large parts of the OMA NGSI features. @Thierry: You are right this is different to the NFC protocol , 6LowPAN, ZigBee. The Connection Protocol Adapter can handle this heterogenity. I am reasonable sure that FIWare will not try to overcome the heterogeneity on Layer 1 (Radio) or L2 (Data Link). IMHO, the approach cannot be to map either directly into each other (nightmare, n x m) or into a higher level protocol ( n x 1). The alter approach is what we are suggesting. In our ISIS system we have shown it can work... - Ern? From: fiware-iot-bounces at lists.fi-ware.eu [mailto:fiware-iot-bounces at lists.fi-ware.eu] On Behalf Of Ricardo de las Heras Sent: Dienstag, 6. September 2011 14:01 To: thierry.nagellen at orange-ftgroup.com Cc: fabioluigi.bellifemine at telecomitalia.it; claudio.borean at telecomitalia.it; fiware-iot at lists.fi-ware.eu Subject: Re: [Fiware-iot] First initial analysis of the IoT Assets mapping for the task 5.1 IoT Communications Dear Thierry, yes, you're right regarding the issue that we have to deal with a broad type of protocols in order to communicate sensors, actuators, devices with a gateway. But my question was beyond this step, when we have to specify a protocol for interchanging data between every gateway and the IoT platform (using SensorAPI for example in the case of IDAS asset). At this level and for interchanging data with context awareness system or other external applications, then is where I tried to explain that could be useful to include the protocol NGSI as a reference protocol of the IoT WP5. Maybe some of our colleagues from NEC or TI can provide us more background with it, but NGSI seems to be quite flexible and direct in order to allow us to map the existent protocols in every asset to the NGSI standard. Sorry if there is any mistake in the details of my explaination. ISIS asset (NEC) for example provides an API interface based on NGSI. So this could be a perfect example of it. cheers, Ricardo. thierry.nagellen at orange-ftgroup.com wrote: Dear Ricardo Maybe I missed a point or there is a misunderstanding. We have to deal here with communication protocols as NFC which could use different frequencies, 6LowPan or Zigbee, Bluetooth, etc... and NGSI try to formalize a standard to exchange context information with applications. In the case of the "component connection Protocol Adapter" the main issue is that lots of communication protocols are used by different devices and if we do not have this component we will not provide a common access to different types of devices, which deal with one or more IoT resources. As I understand NGSI, but I'm not an expert, it provides a common model with dedicated functionalities to define a context element. This is quite relevant for DCM to manage context but less useful for events description for example. But maybe my understanding of NGSI is too limited. Best regards Thierry De : Ricardo de las Heras [mailto:rheras at tid.es] Envoy? : mardi 6 septembre 2011 12:52 ? : NAGELLEN Thierry RD-BIZZ-SOP; sabrina.guerra at telecomitalia.it Cc : fiware-iot at lists.fi-ware.eu; fabioluigi.bellifemine at telecomitalia.it; claudio.borean at telecomitalia.it Objet : Re: [Fiware-iot] First initial analysis of the IoT Assets mapping for the task 5.1 IoT Communications Dear Sabrina, Thierry, regarding your first point: "Component Connection Protocol Adapter - the better solution is that as many as possible protocols are supported by the IoT Services Enablement Platform, for this reason all the assets presented can be included into the implementation of the IoT SE Platform, provided that it's possible to translate them in a common internal form through the component Communication Protocol Abstraction Definition." I'm not an expert on these type of protocols, but as far as I know within the WP6 (Contextual) they are going to use an the OMA standard TS-NGSI for the Context_Management. (http://www.openmobilealliance.org/technical/release_program/ose_archive.aspx) You can find attached a pdf with the NGSI specification. Indeed TI and NEC were very active on the definition of this standard, so it would be fine if we define it as the common language within WP5, maybe mapping the protocols used in the assets to NGSI, having clear advantages in order to communicate us with the rest of WPs, mainly with WP6. Furthermore, the WAC initiative (http://en.wikipedia.org/wiki/Wholesale_Applications_Community) fully support NGSI as well, so it is again a new point for reinforce this decision, with clear advantages for Fiware using this important OMA standard. I don't know what's your point of view, maybe Thierry you can discuss it with Juanjo Hierro, thanks, regards, Ricardo. -- ------------------------------------- Ricardo de las Heras M2M Research Project Manager E-mail: rheras at tid.es Phone1: (+34) 983 367625 Phone2 OCS: (+34) 91 31 29511 Phone3 Skype: (+34) 91 1878107 + Ext: 327 Telef?nica I+D ------------------------------------- thierry.nagellen at orange-ftgroup.com wrote: Hi Sabrina Thanks for your first analysis. We had slightly discussed the point of protocols IoT SE has to support to deal with different kind of things. I fully support your approach that the optimal way for us is to integrate the protocols through the assets we have because to implement all protocols will take lots of time and the main topic is how we can provide a common access. But in this case, partners would have to develop a dedicated interface to be integrated in the component "Connection Protocol Adapter". This should be a good point for the Open Specification and to target different Use Cases. Regarding EPICs which are different from the description of HLD deliverable, feel free to add a new EPIC to be in line with the deliverable and we would be able to discuss which one is the more critical and how we can put some priorities. We can have "several" EPIC per component and we can discuss which are the most valuable and how we could implement them regarding the assets. So at this moment, this is really fully open to add details and to improve these descriptions. Component Access Policy Control: I think the EPIC would not focus on payment matter but try to explain that as an owner of devices and IoT resources, I can define some criteria to give access right. In this case this could be a Social Network or Open Source Community approach to share devices and things with no commercial ASP, as you could provide access rights only for SMEs, or for eHealth applications despite your IoT Resources are not tagged as eHealth resources. Maybe you can refine this EPIC to describe that several criteria could be used to define access rights. This point should be discussed with the Security team during Turin meeting to check what kind of features they can provide. Quality of service control: this feature is clearly not included in any assets. Based on some comments from UA projects this point should be fundamental (to Instant Mobility project, this quality of service is expected for emergency concerns in a city, or to Safecity project to reach in the proper time some video resources in the city). But as we do not have any asset we can put the priority on "Should" and manage this issue later on (2nd round of FI-Ware backlog, or through the open calls if we know some other partners who could have this kind of asset). We have also holes in Process Automation or Data Handling, so we will not do everything now and if all IoT partners agree, we can delay it. But I think that Thales could have an asset to fulfill this requirement. We would wait one more week for their contributions to decide it. BR Thierry De : fiware-iot-bounces at lists.fi-ware.eu [mailto:fiware-iot-bounces at lists.fi-ware.eu] De la part de Guerra Sabrina Envoy? : lundi 5 septembre 2011 13:21 ? : 'fiware-iot at lists.fi-ware.eu' Cc : Bellifemine Fabio Luigi; Borean Claudio Objet : [Fiware-iot] First initial analysis of the IoT Assets mapping for the task 5.1 IoT Communications Hi, we've begun to analyze the list of assets related to the "IoT Communication" task submitted by the FI-WARE partners. Some initial considerations for the components are: * Component Connection Protocol Adapter - the better solution is that as many as possible protocols are supported by the IoT Services Enablement Platform, for this reason all the assets presented can be included into the implementation of the IoT SE Platform, provided that it's possible to translate them in a common internal form through the component Communication Protocol Abstraction Definition. * Component Communication Protocol Abstraction Definition - the epic for this component is different from the description included in the document "FI-WARE High-level Description". Our goal was to introduce a layer that allows an abstraction level for all Connection Protocol Adapters in order to communicate with the IoT SE Platform Core using a common internal language. The "templates", we are referring to in the document, are a kind of rules to translate any specific protocol into the common internal language and not a mechanism to generate Connection Protocol Adapters. This mechanism to automatically generate Connection Protocol Adapters is in any case very interesting and we could add it to the architecture document, if needed. * Component Access Policy Control - The second point of the epic for this component treats the access as a matter of payment (e.g. access only free services), while we intend the access as a matter of permissions to access resources. In our opinion these are different levels and they don't belong to the same component. * Component Quality of Service Control - From the grid it looks like that no asset has this functionality readily available, but since this component is not fundamental for a prototype of the IoT SE Platform, it can be left out or postponed in the future. For the other components we don't have specific considerations for the moment, but it looks like that Pangoo/M2MPlanet (by Orange) and Cumulocity (by NSN) are the assets that are more in line with our requirements. What do you think of this initial analysis of the assets? Are there any comments on these considerations? If you agree we could proceed with a more detailed analysis of the two proposed assets. Best regards, Sabrina Guerra __________________________________ Telecom Italia S.p.a. Strategia e Innovazione, Research & Trends Telefono +39 011 228 8359 Cellulare +39 331 600 1349 Questo messaggio e i suoi allegati sono indirizzati esclusivamente alle persone indicate. La diffusione, copia o qualsiasi altra azione derivante dalla conoscenza di queste informazioni sono rigorosamente vietate. Qualora abbiate ricevuto questo documento per errore siete cortesemente pregati di darne immediata comunicazione al mittente e di provvedere alla sua distruzione, Grazie. This e-mail and any attachments is confidential and may contain privileged information intended for the addressee(s) only. Dissemination, copying, printing or use by anybody else is unauthorised. If you are not the intended recipient, please delete this message and any attachments and advise the sender by return e-mail, Thanks. [rispetta l'ambiente]Rispetta l'ambiente. Non stampare questa mail se non ? necessario. ________________________________ 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 -- ------------------------------------- Ricardo de las Heras M2M Research Project Manager E-mail: rheras at tid.es Phone1: (+34) 983 367625 Phone2 OCS: (+34) 91 31 29511 Phone3 Skype: (+34) 91 1878107 + Ext: 327 Telef?nica I+D ------------------------------------- ________________________________ Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra pol?tica de env?o y recepci?n de correo electr?nico en el enlace situado m?s abajo. This message is intended exclusively for its addressee. We only send and receive email on the basis of the terms set out at. http://www.tid.es/ES/PAGINAS/disclaimer.aspx -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.gif Type: image/gif Size: 677 bytes Desc: image001.gif URL: From Ernoe.Kovacs at neclab.eu Thu Sep 8 09:08:19 2011 From: Ernoe.Kovacs at neclab.eu (Ernoe Kovacs) Date: Thu, 8 Sep 2011 07:08:19 +0000 Subject: [Fiware-iot] [FusionForge Problems with] OMA NGSI API Message-ID: <8152E2132B13FB488CFD1947E2DEF19C1CFA6B43@DAPHNIS.office.hd> Hi Thierry, all, when adding the OMA NGSI documents, I had the following problem: I actually wanted to have a top-level directory Background and a subdirectory OMA-NGSI. Somehow I could create them, but they were not visible in the default view under Docs. I moved the directories to "Uncategorized Submissions", but they are still not visible. They can be seen in the Admin page. ? I assume a problem of rights. Thierry, can you try to handle? Currently, I have the OMA NGSI documents directly in "Uncategorized Submissions", but this Is not the right place. Suggestions and help welcome. - Ern? From: Ernoe Kovacs Sent: Donnerstag, 8. September 2011 09:06 To: Ernoe Kovacs; Ricardo de las Heras; thierry.nagellen at orange-ftgroup.com Cc: fiware-iot at lists.fi-ware.eu; fabioluigi.bellifemine at telecomitalia.it; claudio.borean at telecomitalia.it Subject: OMA NGSI API Dear all, yesterday I promised some more information on the OMA NGSI APIs. You can now find here FI-Ware IoT -> Docs -> Uncategorized Submissions https://forge.fi-ware.eu/docman/?group_id=11 (a) OMA NGSI Info - Document with links to the standard documents and related information There is a good OMA NGSI overview presentation referenced. I recommend to read this. (b) Paper and presentation at ICIN'2010 Gives more insights into the Ctx API which we think is relevant for IoT - Ern? From: fiware-iot-bounces at lists.fi-ware.eu [mailto:fiware-iot-bounces at lists.fi-ware.eu] On Behalf Of Ernoe Kovacs Sent: Dienstag, 6. September 2011 16:03 To: Ricardo de las Heras; thierry.nagellen at orange-ftgroup.com Cc: fiware-iot at lists.fi-ware.eu; fabioluigi.bellifemine at telecomitalia.it; claudio.borean at telecomitalia.it Subject: Re: [Fiware-iot] First initial analysis of the IoT Assets mapping for the task 5.1 IoT Communications Hi all, fast reply here, I provide more background information to study later on. (a) Original discussion "Connection Protocol Adapter" or "component connection Protocol Adapter" I think we are all sharing the same idea here. We have very heterogeneous M2M area network protocols including very different data models. We need to map this into a common protocol model and common data model. Let me go one step deeper: Sensor support very different kind of interactions. Some are waiting to be queried. Some send their information periodically, some send the information when a substantial change has happened, some have a management interface to configure their behavior, etc. etc. Some needs sessions, some only have one shot queries that include authentication each time they are called. I fear you find anything that can be imagined on that level An abstraction layer needs to map all these protocols into a single one. This single one is the language to talk inside of the systems. The "Connection Protocol Adapter" are the software modules that - map between the real protocol on the M2M Area network and the high-level protocol. - fill the gap between what the sensor offers and what the high-level protocol requests. For example, if the high level protocol supports subscriptions and the lwo level one not, either the "connection protocol adapter" or the "Abstraction layer" need to provide the needed functionality... (b) OMA NGSI In the sense of the discussion under (a), OMA NGSI can be the higher level protocol that the abstraction layer supports. OMA NGSI supports updates, queries, subscriptions, and notifications. (c) OMA NGSI as Exposure API For interacting with external systems like WP6, OMA NGSI is a standardized API with comparable rich set of operation. So we can use it as an exposure API towards applications. It also has a data model based on entities, attributes and meta-data about them. Note: The exposure API can be used on the IoT Device, on the IoT Gateway or on the IoT Core. (d) OMA NGSI and IoT Gateways-2-IoT Core Communication Besides the data flow services (update, query, subscribe, notify), OMA NGSI has a small set of primitives that enables two systems to exchange meta-data about the contained objects. So a IoT gateway can register with the IoT Core and inform them that e.g it is currently managing 1 RFID readers, will sent information about "hasSeen RFID Tags" and has a GPS receiver. Yes, OMA NGSI can be used for that as well. I am expecting that we might extend the information exchanged between IoT GW and IoT Core, but OMA NGSI is a starting point. Our ISIS system implements large parts of the OMA NGSI features. @Thierry: You are right this is different to the NFC protocol , 6LowPAN, ZigBee. The Connection Protocol Adapter can handle this heterogenity. I am reasonable sure that FIWare will not try to overcome the heterogeneity on Layer 1 (Radio) or L2 (Data Link). IMHO, the approach cannot be to map either directly into each other (nightmare, n x m) or into a higher level protocol ( n x 1). The alter approach is what we are suggesting. In our ISIS system we have shown it can work... - Ern? From: fiware-iot-bounces at lists.fi-ware.eu [mailto:fiware-iot-bounces at lists.fi-ware.eu] On Behalf Of Ricardo de las Heras Sent: Dienstag, 6. September 2011 14:01 To: thierry.nagellen at orange-ftgroup.com Cc: fabioluigi.bellifemine at telecomitalia.it; claudio.borean at telecomitalia.it; fiware-iot at lists.fi-ware.eu Subject: Re: [Fiware-iot] First initial analysis of the IoT Assets mapping for the task 5.1 IoT Communications Dear Thierry, yes, you're right regarding the issue that we have to deal with a broad type of protocols in order to communicate sensors, actuators, devices with a gateway. But my question was beyond this step, when we have to specify a protocol for interchanging data between every gateway and the IoT platform (using SensorAPI for example in the case of IDAS asset). At this level and for interchanging data with context awareness system or other external applications, then is where I tried to explain that could be useful to include the protocol NGSI as a reference protocol of the IoT WP5. Maybe some of our colleagues from NEC or TI can provide us more background with it, but NGSI seems to be quite flexible and direct in order to allow us to map the existent protocols in every asset to the NGSI standard. Sorry if there is any mistake in the details of my explaination. ISIS asset (NEC) for example provides an API interface based on NGSI. So this could be a perfect example of it. cheers, Ricardo. thierry.nagellen at orange-ftgroup.com wrote: Dear Ricardo Maybe I missed a point or there is a misunderstanding. We have to deal here with communication protocols as NFC which could use different frequencies, 6LowPan or Zigbee, Bluetooth, etc... and NGSI try to formalize a standard to exchange context information with applications. In the case of the "component connection Protocol Adapter" the main issue is that lots of communication protocols are used by different devices and if we do not have this component we will not provide a common access to different types of devices, which deal with one or more IoT resources. As I understand NGSI, but I'm not an expert, it provides a common model with dedicated functionalities to define a context element. This is quite relevant for DCM to manage context but less useful for events description for example. But maybe my understanding of NGSI is too limited. Best regards Thierry De : Ricardo de las Heras [mailto:rheras at tid.es] Envoy? : mardi 6 septembre 2011 12:52 ? : NAGELLEN Thierry RD-BIZZ-SOP; sabrina.guerra at telecomitalia.it Cc : fiware-iot at lists.fi-ware.eu; fabioluigi.bellifemine at telecomitalia.it; claudio.borean at telecomitalia.it Objet : Re: [Fiware-iot] First initial analysis of the IoT Assets mapping for the task 5.1 IoT Communications Dear Sabrina, Thierry, regarding your first point: "Component Connection Protocol Adapter - the better solution is that as many as possible protocols are supported by the IoT Services Enablement Platform, for this reason all the assets presented can be included into the implementation of the IoT SE Platform, provided that it's possible to translate them in a common internal form through the component Communication Protocol Abstraction Definition." I'm not an expert on these type of protocols, but as far as I know within the WP6 (Contextual) they are going to use an the OMA standard TS-NGSI for the Context_Management. (http://www.openmobilealliance.org/technical/release_program/ose_archive.aspx) You can find attached a pdf with the NGSI specification. Indeed TI and NEC were very active on the definition of this standard, so it would be fine if we define it as the common language within WP5, maybe mapping the protocols used in the assets to NGSI, having clear advantages in order to communicate us with the rest of WPs, mainly with WP6. Furthermore, the WAC initiative (http://en.wikipedia.org/wiki/Wholesale_Applications_Community) fully support NGSI as well, so it is again a new point for reinforce this decision, with clear advantages for Fiware using this important OMA standard. I don't know what's your point of view, maybe Thierry you can discuss it with Juanjo Hierro, thanks, regards, Ricardo. -- ------------------------------------- Ricardo de las Heras M2M Research Project Manager E-mail: rheras at tid.es Phone1: (+34) 983 367625 Phone2 OCS: (+34) 91 31 29511 Phone3 Skype: (+34) 91 1878107 + Ext: 327 Telef?nica I+D ------------------------------------- thierry.nagellen at orange-ftgroup.com wrote: Hi Sabrina Thanks for your first analysis. We had slightly discussed the point of protocols IoT SE has to support to deal with different kind of things. I fully support your approach that the optimal way for us is to integrate the protocols through the assets we have because to implement all protocols will take lots of time and the main topic is how we can provide a common access. But in this case, partners would have to develop a dedicated interface to be integrated in the component "Connection Protocol Adapter". This should be a good point for the Open Specification and to target different Use Cases. Regarding EPICs which are different from the description of HLD deliverable, feel free to add a new EPIC to be in line with the deliverable and we would be able to discuss which one is the more critical and how we can put some priorities. We can have "several" EPIC per component and we can discuss which are the most valuable and how we could implement them regarding the assets. So at this moment, this is really fully open to add details and to improve these descriptions. Component Access Policy Control: I think the EPIC would not focus on payment matter but try to explain that as an owner of devices and IoT resources, I can define some criteria to give access right. In this case this could be a Social Network or Open Source Community approach to share devices and things with no commercial ASP, as you could provide access rights only for SMEs, or for eHealth applications despite your IoT Resources are not tagged as eHealth resources. Maybe you can refine this EPIC to describe that several criteria could be used to define access rights. This point should be discussed with the Security team during Turin meeting to check what kind of features they can provide. Quality of service control: this feature is clearly not included in any assets. Based on some comments from UA projects this point should be fundamental (to Instant Mobility project, this quality of service is expected for emergency concerns in a city, or to Safecity project to reach in the proper time some video resources in the city). But as we do not have any asset we can put the priority on "Should" and manage this issue later on (2nd round of FI-Ware backlog, or through the open calls if we know some other partners who could have this kind of asset). We have also holes in Process Automation or Data Handling, so we will not do everything now and if all IoT partners agree, we can delay it. But I think that Thales could have an asset to fulfill this requirement. We would wait one more week for their contributions to decide it. BR Thierry De : fiware-iot-bounces at lists.fi-ware.eu [mailto:fiware-iot-bounces at lists.fi-ware.eu] De la part de Guerra Sabrina Envoy? : lundi 5 septembre 2011 13:21 ? : 'fiware-iot at lists.fi-ware.eu' Cc : Bellifemine Fabio Luigi; Borean Claudio Objet : [Fiware-iot] First initial analysis of the IoT Assets mapping for the task 5.1 IoT Communications Hi, we've begun to analyze the list of assets related to the "IoT Communication" task submitted by the FI-WARE partners. Some initial considerations for the components are: * Component Connection Protocol Adapter - the better solution is that as many as possible protocols are supported by the IoT Services Enablement Platform, for this reason all the assets presented can be included into the implementation of the IoT SE Platform, provided that it's possible to translate them in a common internal form through the component Communication Protocol Abstraction Definition. * Component Communication Protocol Abstraction Definition - the epic for this component is different from the description included in the document "FI-WARE High-level Description". Our goal was to introduce a layer that allows an abstraction level for all Connection Protocol Adapters in order to communicate with the IoT SE Platform Core using a common internal language. The "templates", we are referring to in the document, are a kind of rules to translate any specific protocol into the common internal language and not a mechanism to generate Connection Protocol Adapters. This mechanism to automatically generate Connection Protocol Adapters is in any case very interesting and we could add it to the architecture document, if needed. * Component Access Policy Control - The second point of the epic for this component treats the access as a matter of payment (e.g. access only free services), while we intend the access as a matter of permissions to access resources. In our opinion these are different levels and they don't belong to the same component. * Component Quality of Service Control - From the grid it looks like that no asset has this functionality readily available, but since this component is not fundamental for a prototype of the IoT SE Platform, it can be left out or postponed in the future. For the other components we don't have specific considerations for the moment, but it looks like that Pangoo/M2MPlanet (by Orange) and Cumulocity (by NSN) are the assets that are more in line with our requirements. What do you think of this initial analysis of the assets? Are there any comments on these considerations? If you agree we could proceed with a more detailed analysis of the two proposed assets. Best regards, Sabrina Guerra __________________________________ Telecom Italia S.p.a. Strategia e Innovazione, Research & Trends Telefono +39 011 228 8359 Cellulare +39 331 600 1349 Questo messaggio e i suoi allegati sono indirizzati esclusivamente alle persone indicate. La diffusione, copia o qualsiasi altra azione derivante dalla conoscenza di queste informazioni sono rigorosamente vietate. Qualora abbiate ricevuto questo documento per errore siete cortesemente pregati di darne immediata comunicazione al mittente e di provvedere alla sua distruzione, Grazie. This e-mail and any attachments is confidential and may contain privileged information intended for the addressee(s) only. Dissemination, copying, printing or use by anybody else is unauthorised. If you are not the intended recipient, please delete this message and any attachments and advise the sender by return e-mail, Thanks. [rispetta l'ambiente]Rispetta l'ambiente. Non stampare questa mail se non ? necessario. ________________________________ 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 -- ------------------------------------- Ricardo de las Heras M2M Research Project Manager E-mail: rheras at tid.es Phone1: (+34) 983 367625 Phone2 OCS: (+34) 91 31 29511 Phone3 Skype: (+34) 91 1878107 + Ext: 327 Telef?nica I+D ------------------------------------- ________________________________ Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra pol?tica de env?o y recepci?n de correo electr?nico en el enlace situado m?s abajo. This message is intended exclusively for its addressee. We only send and receive email on the basis of the terms set out at. http://www.tid.es/ES/PAGINAS/disclaimer.aspx -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.gif Type: image/gif Size: 677 bytes Desc: image001.gif URL: From Ernoe.Kovacs at neclab.eu Thu Sep 8 09:11:06 2011 From: Ernoe.Kovacs at neclab.eu (Ernoe Kovacs) Date: Thu, 8 Sep 2011 07:11:06 +0000 Subject: [Fiware-iot] [FusionForge Problems]: Wiki Message-ID: <8152E2132B13FB488CFD1947E2DEF19C1CFA6BC2@DAPHNIS.office.hd> Hi Thierry, (a) when trying to add the OMA NGSI docs, I was searching for a Wiki function. According to the doc, there is one, but I cannot find it. I saw it on other FusionForge installations as an additional tab on the level of Docs, Tasks, Lists, .... I assume there is a respective pljugin that needs to be installed... (b) SVN Support Is the SVN support installed and activated? Thanks for the help and for forwarding to PCC and Technical Support Ern? From: Ernoe Kovacs Sent: Donnerstag, 8. September 2011 09:06 To: Ernoe Kovacs; Ricardo de las Heras; thierry.nagellen at orange-ftgroup.com Cc: fiware-iot at lists.fi-ware.eu; fabioluigi.bellifemine at telecomitalia.it; claudio.borean at telecomitalia.it Subject: OMA NGSI API Dear all, yesterday I promised some more information on the OMA NGSI APIs. You can now find here FI-Ware IoT -> Docs -> Uncategorized Submissions https://forge.fi-ware.eu/docman/?group_id=11 (a) OMA NGSI Info - Document with links to the standard documents and related information There is a good OMA NGSI overview presentation referenced. I recommend to read this. (b) Paper and presentation at ICIN'2010 Gives more insights into the Ctx API which we think is relevant for IoT - Ern? From: fiware-iot-bounces at lists.fi-ware.eu [mailto:fiware-iot-bounces at lists.fi-ware.eu] On Behalf Of Ernoe Kovacs Sent: Dienstag, 6. September 2011 16:03 To: Ricardo de las Heras; thierry.nagellen at orange-ftgroup.com Cc: fiware-iot at lists.fi-ware.eu; fabioluigi.bellifemine at telecomitalia.it; claudio.borean at telecomitalia.it Subject: Re: [Fiware-iot] First initial analysis of the IoT Assets mapping for the task 5.1 IoT Communications Hi all, fast reply here, I provide more background information to study later on. (a) Original discussion "Connection Protocol Adapter" or "component connection Protocol Adapter" I think we are all sharing the same idea here. We have very heterogeneous M2M area network protocols including very different data models. We need to map this into a common protocol model and common data model. Let me go one step deeper: Sensor support very different kind of interactions. Some are waiting to be queried. Some send their information periodically, some send the information when a substantial change has happened, some have a management interface to configure their behavior, etc. etc. Some needs sessions, some only have one shot queries that include authentication each time they are called. I fear you find anything that can be imagined on that level An abstraction layer needs to map all these protocols into a single one. This single one is the language to talk inside of the systems. The "Connection Protocol Adapter" are the software modules that - map between the real protocol on the M2M Area network and the high-level protocol. - fill the gap between what the sensor offers and what the high-level protocol requests. For example, if the high level protocol supports subscriptions and the lwo level one not, either the "connection protocol adapter" or the "Abstraction layer" need to provide the needed functionality... (b) OMA NGSI In the sense of the discussion under (a), OMA NGSI can be the higher level protocol that the abstraction layer supports. OMA NGSI supports updates, queries, subscriptions, and notifications. (c) OMA NGSI as Exposure API For interacting with external systems like WP6, OMA NGSI is a standardized API with comparable rich set of operation. So we can use it as an exposure API towards applications. It also has a data model based on entities, attributes and meta-data about them. Note: The exposure API can be used on the IoT Device, on the IoT Gateway or on the IoT Core. (d) OMA NGSI and IoT Gateways-2-IoT Core Communication Besides the data flow services (update, query, subscribe, notify), OMA NGSI has a small set of primitives that enables two systems to exchange meta-data about the contained objects. So a IoT gateway can register with the IoT Core and inform them that e.g it is currently managing 1 RFID readers, will sent information about "hasSeen RFID Tags" and has a GPS receiver. Yes, OMA NGSI can be used for that as well. I am expecting that we might extend the information exchanged between IoT GW and IoT Core, but OMA NGSI is a starting point. Our ISIS system implements large parts of the OMA NGSI features. @Thierry: You are right this is different to the NFC protocol , 6LowPAN, ZigBee. The Connection Protocol Adapter can handle this heterogenity. I am reasonable sure that FIWare will not try to overcome the heterogeneity on Layer 1 (Radio) or L2 (Data Link). IMHO, the approach cannot be to map either directly into each other (nightmare, n x m) or into a higher level protocol ( n x 1). The alter approach is what we are suggesting. In our ISIS system we have shown it can work... - Ern? From: fiware-iot-bounces at lists.fi-ware.eu [mailto:fiware-iot-bounces at lists.fi-ware.eu] On Behalf Of Ricardo de las Heras Sent: Dienstag, 6. September 2011 14:01 To: thierry.nagellen at orange-ftgroup.com Cc: fabioluigi.bellifemine at telecomitalia.it; claudio.borean at telecomitalia.it; fiware-iot at lists.fi-ware.eu Subject: Re: [Fiware-iot] First initial analysis of the IoT Assets mapping for the task 5.1 IoT Communications Dear Thierry, yes, you're right regarding the issue that we have to deal with a broad type of protocols in order to communicate sensors, actuators, devices with a gateway. But my question was beyond this step, when we have to specify a protocol for interchanging data between every gateway and the IoT platform (using SensorAPI for example in the case of IDAS asset). At this level and for interchanging data with context awareness system or other external applications, then is where I tried to explain that could be useful to include the protocol NGSI as a reference protocol of the IoT WP5. Maybe some of our colleagues from NEC or TI can provide us more background with it, but NGSI seems to be quite flexible and direct in order to allow us to map the existent protocols in every asset to the NGSI standard. Sorry if there is any mistake in the details of my explaination. ISIS asset (NEC) for example provides an API interface based on NGSI. So this could be a perfect example of it. cheers, Ricardo. thierry.nagellen at orange-ftgroup.com wrote: Dear Ricardo Maybe I missed a point or there is a misunderstanding. We have to deal here with communication protocols as NFC which could use different frequencies, 6LowPan or Zigbee, Bluetooth, etc... and NGSI try to formalize a standard to exchange context information with applications. In the case of the "component connection Protocol Adapter" the main issue is that lots of communication protocols are used by different devices and if we do not have this component we will not provide a common access to different types of devices, which deal with one or more IoT resources. As I understand NGSI, but I'm not an expert, it provides a common model with dedicated functionalities to define a context element. This is quite relevant for DCM to manage context but less useful for events description for example. But maybe my understanding of NGSI is too limited. Best regards Thierry De : Ricardo de las Heras [mailto:rheras at tid.es] Envoy? : mardi 6 septembre 2011 12:52 ? : NAGELLEN Thierry RD-BIZZ-SOP; sabrina.guerra at telecomitalia.it Cc : fiware-iot at lists.fi-ware.eu; fabioluigi.bellifemine at telecomitalia.it; claudio.borean at telecomitalia.it Objet : Re: [Fiware-iot] First initial analysis of the IoT Assets mapping for the task 5.1 IoT Communications Dear Sabrina, Thierry, regarding your first point: "Component Connection Protocol Adapter - the better solution is that as many as possible protocols are supported by the IoT Services Enablement Platform, for this reason all the assets presented can be included into the implementation of the IoT SE Platform, provided that it's possible to translate them in a common internal form through the component Communication Protocol Abstraction Definition." I'm not an expert on these type of protocols, but as far as I know within the WP6 (Contextual) they are going to use an the OMA standard TS-NGSI for the Context_Management. (http://www.openmobilealliance.org/technical/release_program/ose_archive.aspx) You can find attached a pdf with the NGSI specification. Indeed TI and NEC were very active on the definition of this standard, so it would be fine if we define it as the common language within WP5, maybe mapping the protocols used in the assets to NGSI, having clear advantages in order to communicate us with the rest of WPs, mainly with WP6. Furthermore, the WAC initiative (http://en.wikipedia.org/wiki/Wholesale_Applications_Community) fully support NGSI as well, so it is again a new point for reinforce this decision, with clear advantages for Fiware using this important OMA standard. I don't know what's your point of view, maybe Thierry you can discuss it with Juanjo Hierro, thanks, regards, Ricardo. -- ------------------------------------- Ricardo de las Heras M2M Research Project Manager E-mail: rheras at tid.es Phone1: (+34) 983 367625 Phone2 OCS: (+34) 91 31 29511 Phone3 Skype: (+34) 91 1878107 + Ext: 327 Telef?nica I+D ------------------------------------- thierry.nagellen at orange-ftgroup.com wrote: Hi Sabrina Thanks for your first analysis. We had slightly discussed the point of protocols IoT SE has to support to deal with different kind of things. I fully support your approach that the optimal way for us is to integrate the protocols through the assets we have because to implement all protocols will take lots of time and the main topic is how we can provide a common access. But in this case, partners would have to develop a dedicated interface to be integrated in the component "Connection Protocol Adapter". This should be a good point for the Open Specification and to target different Use Cases. Regarding EPICs which are different from the description of HLD deliverable, feel free to add a new EPIC to be in line with the deliverable and we would be able to discuss which one is the more critical and how we can put some priorities. We can have "several" EPIC per component and we can discuss which are the most valuable and how we could implement them regarding the assets. So at this moment, this is really fully open to add details and to improve these descriptions. Component Access Policy Control: I think the EPIC would not focus on payment matter but try to explain that as an owner of devices and IoT resources, I can define some criteria to give access right. In this case this could be a Social Network or Open Source Community approach to share devices and things with no commercial ASP, as you could provide access rights only for SMEs, or for eHealth applications despite your IoT Resources are not tagged as eHealth resources. Maybe you can refine this EPIC to describe that several criteria could be used to define access rights. This point should be discussed with the Security team during Turin meeting to check what kind of features they can provide. Quality of service control: this feature is clearly not included in any assets. Based on some comments from UA projects this point should be fundamental (to Instant Mobility project, this quality of service is expected for emergency concerns in a city, or to Safecity project to reach in the proper time some video resources in the city). But as we do not have any asset we can put the priority on "Should" and manage this issue later on (2nd round of FI-Ware backlog, or through the open calls if we know some other partners who could have this kind of asset). We have also holes in Process Automation or Data Handling, so we will not do everything now and if all IoT partners agree, we can delay it. But I think that Thales could have an asset to fulfill this requirement. We would wait one more week for their contributions to decide it. BR Thierry De : fiware-iot-bounces at lists.fi-ware.eu [mailto:fiware-iot-bounces at lists.fi-ware.eu] De la part de Guerra Sabrina Envoy? : lundi 5 septembre 2011 13:21 ? : 'fiware-iot at lists.fi-ware.eu' Cc : Bellifemine Fabio Luigi; Borean Claudio Objet : [Fiware-iot] First initial analysis of the IoT Assets mapping for the task 5.1 IoT Communications Hi, we've begun to analyze the list of assets related to the "IoT Communication" task submitted by the FI-WARE partners. Some initial considerations for the components are: * Component Connection Protocol Adapter - the better solution is that as many as possible protocols are supported by the IoT Services Enablement Platform, for this reason all the assets presented can be included into the implementation of the IoT SE Platform, provided that it's possible to translate them in a common internal form through the component Communication Protocol Abstraction Definition. * Component Communication Protocol Abstraction Definition - the epic for this component is different from the description included in the document "FI-WARE High-level Description". Our goal was to introduce a layer that allows an abstraction level for all Connection Protocol Adapters in order to communicate with the IoT SE Platform Core using a common internal language. The "templates", we are referring to in the document, are a kind of rules to translate any specific protocol into the common internal language and not a mechanism to generate Connection Protocol Adapters. This mechanism to automatically generate Connection Protocol Adapters is in any case very interesting and we could add it to the architecture document, if needed. * Component Access Policy Control - The second point of the epic for this component treats the access as a matter of payment (e.g. access only free services), while we intend the access as a matter of permissions to access resources. In our opinion these are different levels and they don't belong to the same component. * Component Quality of Service Control - From the grid it looks like that no asset has this functionality readily available, but since this component is not fundamental for a prototype of the IoT SE Platform, it can be left out or postponed in the future. For the other components we don't have specific considerations for the moment, but it looks like that Pangoo/M2MPlanet (by Orange) and Cumulocity (by NSN) are the assets that are more in line with our requirements. What do you think of this initial analysis of the assets? Are there any comments on these considerations? If you agree we could proceed with a more detailed analysis of the two proposed assets. Best regards, Sabrina Guerra __________________________________ Telecom Italia S.p.a. Strategia e Innovazione, Research & Trends Telefono +39 011 228 8359 Cellulare +39 331 600 1349 Questo messaggio e i suoi allegati sono indirizzati esclusivamente alle persone indicate. La diffusione, copia o qualsiasi altra azione derivante dalla conoscenza di queste informazioni sono rigorosamente vietate. Qualora abbiate ricevuto questo documento per errore siete cortesemente pregati di darne immediata comunicazione al mittente e di provvedere alla sua distruzione, Grazie. This e-mail and any attachments is confidential and may contain privileged information intended for the addressee(s) only. Dissemination, copying, printing or use by anybody else is unauthorised. If you are not the intended recipient, please delete this message and any attachments and advise the sender by return e-mail, Thanks. [rispetta l'ambiente]Rispetta l'ambiente. Non stampare questa mail se non ? necessario. ________________________________ 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 -- ------------------------------------- Ricardo de las Heras M2M Research Project Manager E-mail: rheras at tid.es Phone1: (+34) 983 367625 Phone2 OCS: (+34) 91 31 29511 Phone3 Skype: (+34) 91 1878107 + Ext: 327 Telef?nica I+D ------------------------------------- ________________________________ Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra pol?tica de env?o y recepci?n de correo electr?nico en el enlace situado m?s abajo. This message is intended exclusively for its addressee. We only send and receive email on the basis of the terms set out at. http://www.tid.es/ES/PAGINAS/disclaimer.aspx -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.gif Type: image/gif Size: 677 bytes Desc: image001.gif URL: From lorant.farkas at nsn.com Thu Sep 8 12:31:57 2011 From: lorant.farkas at nsn.com (Farkas, Lorant (NSN - HU/Budapest)) Date: Thu, 8 Sep 2011 13:31:57 +0300 Subject: [Fiware-iot] weekly meeting minutes, 31 August 2011 Message-ID: <93D28BDF64839C468B848D14227151A2023EF3FA@FIESEXC014.nsn-intra.net> Dear All, Please find the meeting minutes under the following link: https://forge.fi-ware.eu/docman/view.php/11/357/IoT-Minutes-Telco-090820 11.doc Thanks & Br, Lorant -------------- next part -------------- An HTML attachment was scrubbed... URL: From lorant.farkas at nsn.com Mon Sep 12 08:16:22 2011 From: lorant.farkas at nsn.com (Farkas, Lorant (NSN - HU/Budapest)) Date: Mon, 12 Sep 2011 09:16:22 +0300 Subject: [Fiware-iot] [FusionForge Problems]: Wiki In-Reply-To: <8152E2132B13FB488CFD1947E2DEF19C1CFA6BC2@DAPHNIS.office.hd> References: <8152E2132B13FB488CFD1947E2DEF19C1CFA6BC2@DAPHNIS.office.hd> Message-ID: <93D28BDF64839C468B848D14227151A20243450E@FIESEXC014.nsn-intra.net> Dear All, I moved these docs to the "Standardization" category. Br, Lorant ________________________________ From: fiware-iot-bounces at lists.fi-ware.eu [mailto:fiware-iot-bounces at lists.fi-ware.eu] On Behalf Of ext Ernoe Kovacs Sent: Thursday, September 08, 2011 9:11 AM To: Ricardo de las Heras; thierry.nagellen at orange-ftgroup.com Cc: fiware-iot at lists.fi-ware.eu Subject: [Fiware-iot] [FusionForge Problems]: Wiki Hi Thierry, (a) when trying to add the OMA NGSI docs, I was searching for a Wiki function. According to the doc, there is one, but I cannot find it. I saw it on other FusionForge installations as an additional tab on the level of Docs, Tasks, Lists, .... I assume there is a respective pljugin that needs to be installed... (b) SVN Support Is the SVN support installed and activated? Thanks for the help and for forwarding to PCC and Technical Support Ern? From: Ernoe Kovacs Sent: Donnerstag, 8. September 2011 09:06 To: Ernoe Kovacs; Ricardo de las Heras; thierry.nagellen at orange-ftgroup.com Cc: fiware-iot at lists.fi-ware.eu; fabioluigi.bellifemine at telecomitalia.it; claudio.borean at telecomitalia.it Subject: OMA NGSI API Dear all, yesterday I promised some more information on the OMA NGSI APIs. You can now find here FI-Ware IoT -> Docs -> Uncategorized Submissions https://forge.fi-ware.eu/docman/?group_id=11 (a) OMA NGSI Info - Document with links to the standard documents and related information There is a good OMA NGSI overview presentation referenced. I recommend to read this. (b) Paper and presentation at ICIN'2010 Gives more insights into the Ctx API which we think is relevant for IoT - Ern? From: fiware-iot-bounces at lists.fi-ware.eu [mailto:fiware-iot-bounces at lists.fi-ware.eu] On Behalf Of Ernoe Kovacs Sent: Dienstag, 6. September 2011 16:03 To: Ricardo de las Heras; thierry.nagellen at orange-ftgroup.com Cc: fiware-iot at lists.fi-ware.eu; fabioluigi.bellifemine at telecomitalia.it; claudio.borean at telecomitalia.it Subject: Re: [Fiware-iot] First initial analysis of the IoT Assets mapping for the task 5.1 IoT Communications Hi all, fast reply here, I provide more background information to study later on. (a) Original discussion "Connection Protocol Adapter" or "component connection Protocol Adapter" I think we are all sharing the same idea here. We have very heterogeneous M2M area network protocols including very different data models. We need to map this into a common protocol model and common data model. Let me go one step deeper: Sensor support very different kind of interactions. Some are waiting to be queried. Some send their information periodically, some send the information when a substantial change has happened, some have a management interface to configure their behavior, etc. etc. Some needs sessions, some only have one shot queries that include authentication each time they are called. I fear you find anything that can be imagined on that level An abstraction layer needs to map all these protocols into a single one. This single one is the language to talk inside of the systems. The "Connection Protocol Adapter" are the software modules that - map between the real protocol on the M2M Area network and the high-level protocol. - fill the gap between what the sensor offers and what the high-level protocol requests. For example, if the high level protocol supports subscriptions and the lwo level one not, either the "connection protocol adapter" or the "Abstraction layer" need to provide the needed functionality... (b) OMA NGSI In the sense of the discussion under (a), OMA NGSI can be the higher level protocol that the abstraction layer supports. OMA NGSI supports updates, queries, subscriptions, and notifications. (c) OMA NGSI as Exposure API For interacting with external systems like WP6, OMA NGSI is a standardized API with comparable rich set of operation. So we can use it as an exposure API towards applications. It also has a data model based on entities, attributes and meta-data about them. Note: The exposure API can be used on the IoT Device, on the IoT Gateway or on the IoT Core. (d) OMA NGSI and IoT Gateways-2-IoT Core Communication Besides the data flow services (update, query, subscribe, notify), OMA NGSI has a small set of primitives that enables two systems to exchange meta-data about the contained objects. So a IoT gateway can register with the IoT Core and inform them that e.g it is currently managing 1 RFID readers, will sent information about "hasSeen RFID Tags" and has a GPS receiver. Yes, OMA NGSI can be used for that as well. I am expecting that we might extend the information exchanged between IoT GW and IoT Core, but OMA NGSI is a starting point. Our ISIS system implements large parts of the OMA NGSI features. @Thierry: You are right this is different to the NFC protocol , 6LowPAN, ZigBee. The Connection Protocol Adapter can handle this heterogenity. I am reasonable sure that FIWare will not try to overcome the heterogeneity on Layer 1 (Radio) or L2 (Data Link). IMHO, the approach cannot be to map either directly into each other (nightmare, n x m) or into a higher level protocol ( n x 1). The alter approach is what we are suggesting. In our ISIS system we have shown it can work... - Ern? From: fiware-iot-bounces at lists.fi-ware.eu [mailto:fiware-iot-bounces at lists.fi-ware.eu] On Behalf Of Ricardo de las Heras Sent: Dienstag, 6. September 2011 14:01 To: thierry.nagellen at orange-ftgroup.com Cc: fabioluigi.bellifemine at telecomitalia.it; claudio.borean at telecomitalia.it; fiware-iot at lists.fi-ware.eu Subject: Re: [Fiware-iot] First initial analysis of the IoT Assets mapping for the task 5.1 IoT Communications Dear Thierry, yes, you're right regarding the issue that we have to deal with a broad type of protocols in order to communicate sensors, actuators, devices with a gateway. But my question was beyond this step, when we have to specify a protocol for interchanging data between every gateway and the IoT platform (using SensorAPI for example in the case of IDAS asset). At this level and for interchanging data with context awareness system or other external applications, then is where I tried to explain that could be useful to include the protocol NGSI as a reference protocol of the IoT WP5. Maybe some of our colleagues from NEC or TI can provide us more background with it, but NGSI seems to be quite flexible and direct in order to allow us to map the existent protocols in every asset to the NGSI standard. Sorry if there is any mistake in the details of my explaination. ISIS asset (NEC) for example provides an API interface based on NGSI. So this could be a perfect example of it. cheers, Ricardo. thierry.nagellen at orange-ftgroup.com wrote: Dear Ricardo Maybe I missed a point or there is a misunderstanding. We have to deal here with communication protocols as NFC which could use different frequencies, 6LowPan or Zigbee, Bluetooth, etc... and NGSI try to formalize a standard to exchange context information with applications. In the case of the "component connection Protocol Adapter" the main issue is that lots of communication protocols are used by different devices and if we do not have this component we will not provide a common access to different types of devices, which deal with one or more IoT resources. As I understand NGSI, but I'm not an expert, it provides a common model with dedicated functionalities to define a context element. This is quite relevant for DCM to manage context but less useful for events description for example. But maybe my understanding of NGSI is too limited. Best regards Thierry De : Ricardo de las Heras [mailto:rheras at tid.es] Envoy? : mardi 6 septembre 2011 12:52 ? : NAGELLEN Thierry RD-BIZZ-SOP; sabrina.guerra at telecomitalia.it Cc : fiware-iot at lists.fi-ware.eu; fabioluigi.bellifemine at telecomitalia.it; claudio.borean at telecomitalia.it Objet : Re: [Fiware-iot] First initial analysis of the IoT Assets mapping for the task 5.1 IoT Communications Dear Sabrina, Thierry, regarding your first point: "Component Connection Protocol Adapter - the better solution is that as many as possible protocols are supported by the IoT Services Enablement Platform, for this reason all the assets presented can be included into the implementation of the IoT SE Platform, provided that it's possible to translate them in a common internal form through the component Communication Protocol Abstraction Definition." I'm not an expert on these type of protocols, but as far as I know within the WP6 (Contextual) they are going to use an the OMA standard TS-NGSI for the Context_Management. (http://www.openmobilealliance.org/technical/release_program/ose_archive.aspx) You can find attached a pdf with the NGSI specification. Indeed TI and NEC were very active on the definition of this standard, so it would be fine if we define it as the common language within WP5, maybe mapping the protocols used in the assets to NGSI, having clear advantages in order to communicate us with the rest of WPs, mainly with WP6. Furthermore, the WAC initiative (http://en.wikipedia.org/wiki/Wholesale_Applications_Community) fully support NGSI as well, so it is again a new point for reinforce this decision, with clear advantages for Fiware using this important OMA standard. I don't know what's your point of view, maybe Thierry you can discuss it with Juanjo Hierro, thanks, regards, Ricardo. -- ------------------------------------- Ricardo de las Heras M2M Research Project Manager E-mail: rheras at tid.es Phone1: (+34) 983 367625 Phone2 OCS: (+34) 91 31 29511 Phone3 Skype: (+34) 91 1878107 + Ext: 327 Telef?nica I+D ------------------------------------- thierry.nagellen at orange-ftgroup.com wrote: Hi Sabrina Thanks for your first analysis. We had slightly discussed the point of protocols IoT SE has to support to deal with different kind of things. I fully support your approach that the optimal way for us is to integrate the protocols through the assets we have because to implement all protocols will take lots of time and the main topic is how we can provide a common access. But in this case, partners would have to develop a dedicated interface to be integrated in the component "Connection Protocol Adapter". This should be a good point for the Open Specification and to target different Use Cases. Regarding EPICs which are different from the description of HLD deliverable, feel free to add a new EPIC to be in line with the deliverable and we would be able to discuss which one is the more critical and how we can put some priorities. We can have "several" EPIC per component and we can discuss which are the most valuable and how we could implement them regarding the assets. So at this moment, this is really fully open to add details and to improve these descriptions. Component Access Policy Control: I think the EPIC would not focus on payment matter but try to explain that as an owner of devices and IoT resources, I can define some criteria to give access right. In this case this could be a Social Network or Open Source Community approach to share devices and things with no commercial ASP, as you could provide access rights only for SMEs, or for eHealth applications despite your IoT Resources are not tagged as eHealth resources. Maybe you can refine this EPIC to describe that several criteria could be used to define access rights. This point should be discussed with the Security team during Turin meeting to check what kind of features they can provide. Quality of service control: this feature is clearly not included in any assets. Based on some comments from UA projects this point should be fundamental (to Instant Mobility project, this quality of service is expected for emergency concerns in a city, or to Safecity project to reach in the proper time some video resources in the city). But as we do not have any asset we can put the priority on "Should" and manage this issue later on (2nd round of FI-Ware backlog, or through the open calls if we know some other partners who could have this kind of asset). We have also holes in Process Automation or Data Handling, so we will not do everything now and if all IoT partners agree, we can delay it. But I think that Thales could have an asset to fulfill this requirement. We would wait one more week for their contributions to decide it. BR Thierry De : fiware-iot-bounces at lists.fi-ware.eu [mailto:fiware-iot-bounces at lists.fi-ware.eu] De la part de Guerra Sabrina Envoy? : lundi 5 septembre 2011 13:21 ? : 'fiware-iot at lists.fi-ware.eu' Cc : Bellifemine Fabio Luigi; Borean Claudio Objet : [Fiware-iot] First initial analysis of the IoT Assets mapping for the task 5.1 IoT Communications Hi, we've begun to analyze the list of assets related to the "IoT Communication" task submitted by the FI-WARE partners. Some initial considerations for the components are: * Component Connection Protocol Adapter - the better solution is that as many as possible protocols are supported by the IoT Services Enablement Platform, for this reason all the assets presented can be included into the implementation of the IoT SE Platform, provided that it's possible to translate them in a common internal form through the component Communication Protocol Abstraction Definition. * Component Communication Protocol Abstraction Definition - the epic for this component is different from the description included in the document "FI-WARE High-level Description". Our goal was to introduce a layer that allows an abstraction level for all Connection Protocol Adapters in order to communicate with the IoT SE Platform Core using a common internal language. The "templates", we are referring to in the document, are a kind of rules to translate any specific protocol into the common internal language and not a mechanism to generate Connection Protocol Adapters. This mechanism to automatically generate Connection Protocol Adapters is in any case very interesting and we could add it to the architecture document, if needed. * Component Access Policy Control - The second point of the epic for this component treats the access as a matter of payment (e.g. access only free services), while we intend the access as a matter of permissions to access resources. In our opinion these are different levels and they don't belong to the same component. * Component Quality of Service Control - From the grid it looks like that no asset has this functionality readily available, but since this component is not fundamental for a prototype of the IoT SE Platform, it can be left out or postponed in the future. For the other components we don't have specific considerations for the moment, but it looks like that Pangoo/M2MPlanet (by Orange) and Cumulocity (by NSN) are the assets that are more in line with our requirements. What do you think of this initial analysis of the assets? Are there any comments on these considerations? If you agree we could proceed with a more detailed analysis of the two proposed assets. Best regards, Sabrina Guerra __________________________________ Telecom Italia S.p.a. Strategia e Innovazione, Research & Trends Telefono +39 011 228 8359 Cellulare +39 331 600 1349 Questo messaggio e i suoi allegati sono indirizzati esclusivamente alle persone indicate. La diffusione, copia o qualsiasi altra azione derivante dalla conoscenza di queste informazioni sono rigorosamente vietate. Qualora abbiate ricevuto questo documento per errore siete cortesemente pregati di darne immediata comunicazione al mittente e di provvedere alla sua distruzione, Grazie. This e-mail and any attachments is confidential and may contain privileged information intended for the addressee(s) only. Dissemination, copying, printing or use by anybody else is unauthorised. If you are not the intended recipient, please delete this message and any attachments and advise the sender by return e-mail, Thanks. Rispetta l'ambiente. Non stampare questa mail se non ? necessario. ________________________________ 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 -- ------------------------------------- Ricardo de las Heras M2M Research Project Manager E-mail: rheras at tid.es Phone1: (+34) 983 367625 Phone2 OCS: (+34) 91 31 29511 Phone3 Skype: (+34) 91 1878107 + Ext: 327 Telef?nica I+D ------------------------------------- ________________________________ Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra pol?tica de env?o y recepci?n de correo electr?nico en el enlace situado m?s abajo. This message is intended exclusively for its addressee. We only send and receive email on the basis of the terms set out at. http://www.tid.es/ES/PAGINAS/disclaimer.aspx -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.gif Type: image/gif Size: 677 bytes Desc: image001.gif URL: From Ernoe.Kovacs at neclab.eu Mon Sep 12 08:39:06 2011 From: Ernoe.Kovacs at neclab.eu (Ernoe Kovacs) Date: Mon, 12 Sep 2011 06:39:06 +0000 Subject: [Fiware-iot] [FusionForge Problems]: Wiki In-Reply-To: <93D28BDF64839C468B848D14227151A20243450E@FIESEXC014.nsn-intra.net> References: <8152E2132B13FB488CFD1947E2DEF19C1CFA6BC2@DAPHNIS.office.hd> <93D28BDF64839C468B848D14227151A20243450E@FIESEXC014.nsn-intra.net> Message-ID: <8152E2132B13FB488CFD1947E2DEF19C1CFA9F8D@DAPHNIS.office.hd> Lorant, thanks a lot. I did some small editing and removed the [Temporary] marker, as this could be the place where the document might be stored. Any idea why I was not able to do this kind of editing (creating a directory)? - Ern? From: Farkas, Lorant (NSN - HU/Budapest) [mailto:lorant.farkas at nsn.com] Sent: Montag, 12. September 2011 08:16 To: Ernoe Kovacs; Ricardo de las Heras; thierry.nagellen at orange-ftgroup.com Cc: fiware-iot at lists.fi-ware.eu Subject: RE: [Fiware-iot] [FusionForge Problems]: Wiki Dear All, I moved these docs to the "Standardization" category. Br, Lorant ________________________________ From: fiware-iot-bounces at lists.fi-ware.eu [mailto:fiware-iot-bounces at lists.fi-ware.eu] On Behalf Of ext Ernoe Kovacs Sent: Thursday, September 08, 2011 9:11 AM To: Ricardo de las Heras; thierry.nagellen at orange-ftgroup.com Cc: fiware-iot at lists.fi-ware.eu Subject: [Fiware-iot] [FusionForge Problems]: Wiki Hi Thierry, (a) when trying to add the OMA NGSI docs, I was searching for a Wiki function. According to the doc, there is one, but I cannot find it. I saw it on other FusionForge installations as an additional tab on the level of Docs, Tasks, Lists, .... I assume there is a respective pljugin that needs to be installed... (b) SVN Support Is the SVN support installed and activated? Thanks for the help and for forwarding to PCC and Technical Support Ern? From: Ernoe Kovacs Sent: Donnerstag, 8. September 2011 09:06 To: Ernoe Kovacs; Ricardo de las Heras; thierry.nagellen at orange-ftgroup.com Cc: fiware-iot at lists.fi-ware.eu; fabioluigi.bellifemine at telecomitalia.it; claudio.borean at telecomitalia.it Subject: OMA NGSI API Dear all, yesterday I promised some more information on the OMA NGSI APIs. You can now find here FI-Ware IoT -> Docs -> Uncategorized Submissions https://forge.fi-ware.eu/docman/?group_id=11 (a) OMA NGSI Info - Document with links to the standard documents and related information There is a good OMA NGSI overview presentation referenced. I recommend to read this. (b) Paper and presentation at ICIN'2010 Gives more insights into the Ctx API which we think is relevant for IoT - Ern? From: fiware-iot-bounces at lists.fi-ware.eu [mailto:fiware-iot-bounces at lists.fi-ware.eu] On Behalf Of Ernoe Kovacs Sent: Dienstag, 6. September 2011 16:03 To: Ricardo de las Heras; thierry.nagellen at orange-ftgroup.com Cc: fiware-iot at lists.fi-ware.eu; fabioluigi.bellifemine at telecomitalia.it; claudio.borean at telecomitalia.it Subject: Re: [Fiware-iot] First initial analysis of the IoT Assets mapping for the task 5.1 IoT Communications Hi all, fast reply here, I provide more background information to study later on. (a) Original discussion "Connection Protocol Adapter" or "component connection Protocol Adapter" I think we are all sharing the same idea here. We have very heterogeneous M2M area network protocols including very different data models. We need to map this into a common protocol model and common data model. Let me go one step deeper: Sensor support very different kind of interactions. Some are waiting to be queried. Some send their information periodically, some send the information when a substantial change has happened, some have a management interface to configure their behavior, etc. etc. Some needs sessions, some only have one shot queries that include authentication each time they are called. I fear you find anything that can be imagined on that level An abstraction layer needs to map all these protocols into a single one. This single one is the language to talk inside of the systems. The "Connection Protocol Adapter" are the software modules that - map between the real protocol on the M2M Area network and the high-level protocol. - fill the gap between what the sensor offers and what the high-level protocol requests. For example, if the high level protocol supports subscriptions and the lwo level one not, either the "connection protocol adapter" or the "Abstraction layer" need to provide the needed functionality... (b) OMA NGSI In the sense of the discussion under (a), OMA NGSI can be the higher level protocol that the abstraction layer supports. OMA NGSI supports updates, queries, subscriptions, and notifications. (c) OMA NGSI as Exposure API For interacting with external systems like WP6, OMA NGSI is a standardized API with comparable rich set of operation. So we can use it as an exposure API towards applications. It also has a data model based on entities, attributes and meta-data about them. Note: The exposure API can be used on the IoT Device, on the IoT Gateway or on the IoT Core. (d) OMA NGSI and IoT Gateways-2-IoT Core Communication Besides the data flow services (update, query, subscribe, notify), OMA NGSI has a small set of primitives that enables two systems to exchange meta-data about the contained objects. So a IoT gateway can register with the IoT Core and inform them that e.g it is currently managing 1 RFID readers, will sent information about "hasSeen RFID Tags" and has a GPS receiver. Yes, OMA NGSI can be used for that as well. I am expecting that we might extend the information exchanged between IoT GW and IoT Core, but OMA NGSI is a starting point. Our ISIS system implements large parts of the OMA NGSI features. @Thierry: You are right this is different to the NFC protocol , 6LowPAN, ZigBee. The Connection Protocol Adapter can handle this heterogenity. I am reasonable sure that FIWare will not try to overcome the heterogeneity on Layer 1 (Radio) or L2 (Data Link). IMHO, the approach cannot be to map either directly into each other (nightmare, n x m) or into a higher level protocol ( n x 1). The alter approach is what we are suggesting. In our ISIS system we have shown it can work... - Ern? From: fiware-iot-bounces at lists.fi-ware.eu [mailto:fiware-iot-bounces at lists.fi-ware.eu] On Behalf Of Ricardo de las Heras Sent: Dienstag, 6. September 2011 14:01 To: thierry.nagellen at orange-ftgroup.com Cc: fabioluigi.bellifemine at telecomitalia.it; claudio.borean at telecomitalia.it; fiware-iot at lists.fi-ware.eu Subject: Re: [Fiware-iot] First initial analysis of the IoT Assets mapping for the task 5.1 IoT Communications Dear Thierry, yes, you're right regarding the issue that we have to deal with a broad type of protocols in order to communicate sensors, actuators, devices with a gateway. But my question was beyond this step, when we have to specify a protocol for interchanging data between every gateway and the IoT platform (using SensorAPI for example in the case of IDAS asset). At this level and for interchanging data with context awareness system or other external applications, then is where I tried to explain that could be useful to include the protocol NGSI as a reference protocol of the IoT WP5. Maybe some of our colleagues from NEC or TI can provide us more background with it, but NGSI seems to be quite flexible and direct in order to allow us to map the existent protocols in every asset to the NGSI standard. Sorry if there is any mistake in the details of my explaination. ISIS asset (NEC) for example provides an API interface based on NGSI. So this could be a perfect example of it. cheers, Ricardo. thierry.nagellen at orange-ftgroup.com wrote: Dear Ricardo Maybe I missed a point or there is a misunderstanding. We have to deal here with communication protocols as NFC which could use different frequencies, 6LowPan or Zigbee, Bluetooth, etc... and NGSI try to formalize a standard to exchange context information with applications. In the case of the "component connection Protocol Adapter" the main issue is that lots of communication protocols are used by different devices and if we do not have this component we will not provide a common access to different types of devices, which deal with one or more IoT resources. As I understand NGSI, but I'm not an expert, it provides a common model with dedicated functionalities to define a context element. This is quite relevant for DCM to manage context but less useful for events description for example. But maybe my understanding of NGSI is too limited. Best regards Thierry De : Ricardo de las Heras [mailto:rheras at tid.es] Envoy? : mardi 6 septembre 2011 12:52 ? : NAGELLEN Thierry RD-BIZZ-SOP; sabrina.guerra at telecomitalia.it Cc : fiware-iot at lists.fi-ware.eu; fabioluigi.bellifemine at telecomitalia.it; claudio.borean at telecomitalia.it Objet : Re: [Fiware-iot] First initial analysis of the IoT Assets mapping for the task 5.1 IoT Communications Dear Sabrina, Thierry, regarding your first point: "Component Connection Protocol Adapter - the better solution is that as many as possible protocols are supported by the IoT Services Enablement Platform, for this reason all the assets presented can be included into the implementation of the IoT SE Platform, provided that it's possible to translate them in a common internal form through the component Communication Protocol Abstraction Definition." I'm not an expert on these type of protocols, but as far as I know within the WP6 (Contextual) they are going to use an the OMA standard TS-NGSI for the Context_Management. (http://www.openmobilealliance.org/technical/release_program/ose_archive.aspx) You can find attached a pdf with the NGSI specification. Indeed TI and NEC were very active on the definition of this standard, so it would be fine if we define it as the common language within WP5, maybe mapping the protocols used in the assets to NGSI, having clear advantages in order to communicate us with the rest of WPs, mainly with WP6. Furthermore, the WAC initiative (http://en.wikipedia.org/wiki/Wholesale_Applications_Community) fully support NGSI as well, so it is again a new point for reinforce this decision, with clear advantages for Fiware using this important OMA standard. I don't know what's your point of view, maybe Thierry you can discuss it with Juanjo Hierro, thanks, regards, Ricardo. -- ------------------------------------- Ricardo de las Heras M2M Research Project Manager E-mail: rheras at tid.es Phone1: (+34) 983 367625 Phone2 OCS: (+34) 91 31 29511 Phone3 Skype: (+34) 91 1878107 + Ext: 327 Telef?nica I+D ------------------------------------- thierry.nagellen at orange-ftgroup.com wrote: Hi Sabrina Thanks for your first analysis. We had slightly discussed the point of protocols IoT SE has to support to deal with different kind of things. I fully support your approach that the optimal way for us is to integrate the protocols through the assets we have because to implement all protocols will take lots of time and the main topic is how we can provide a common access. But in this case, partners would have to develop a dedicated interface to be integrated in the component "Connection Protocol Adapter". This should be a good point for the Open Specification and to target different Use Cases. Regarding EPICs which are different from the description of HLD deliverable, feel free to add a new EPIC to be in line with the deliverable and we would be able to discuss which one is the more critical and how we can put some priorities. We can have "several" EPIC per component and we can discuss which are the most valuable and how we could implement them regarding the assets. So at this moment, this is really fully open to add details and to improve these descriptions. Component Access Policy Control: I think the EPIC would not focus on payment matter but try to explain that as an owner of devices and IoT resources, I can define some criteria to give access right. In this case this could be a Social Network or Open Source Community approach to share devices and things with no commercial ASP, as you could provide access rights only for SMEs, or for eHealth applications despite your IoT Resources are not tagged as eHealth resources. Maybe you can refine this EPIC to describe that several criteria could be used to define access rights. This point should be discussed with the Security team during Turin meeting to check what kind of features they can provide. Quality of service control: this feature is clearly not included in any assets. Based on some comments from UA projects this point should be fundamental (to Instant Mobility project, this quality of service is expected for emergency concerns in a city, or to Safecity project to reach in the proper time some video resources in the city). But as we do not have any asset we can put the priority on "Should" and manage this issue later on (2nd round of FI-Ware backlog, or through the open calls if we know some other partners who could have this kind of asset). We have also holes in Process Automation or Data Handling, so we will not do everything now and if all IoT partners agree, we can delay it. But I think that Thales could have an asset to fulfill this requirement. We would wait one more week for their contributions to decide it. BR Thierry De : fiware-iot-bounces at lists.fi-ware.eu [mailto:fiware-iot-bounces at lists.fi-ware.eu] De la part de Guerra Sabrina Envoy? : lundi 5 septembre 2011 13:21 ? : 'fiware-iot at lists.fi-ware.eu' Cc : Bellifemine Fabio Luigi; Borean Claudio Objet : [Fiware-iot] First initial analysis of the IoT Assets mapping for the task 5.1 IoT Communications Hi, we've begun to analyze the list of assets related to the "IoT Communication" task submitted by the FI-WARE partners. Some initial considerations for the components are: * Component Connection Protocol Adapter - the better solution is that as many as possible protocols are supported by the IoT Services Enablement Platform, for this reason all the assets presented can be included into the implementation of the IoT SE Platform, provided that it's possible to translate them in a common internal form through the component Communication Protocol Abstraction Definition. * Component Communication Protocol Abstraction Definition - the epic for this component is different from the description included in the document "FI-WARE High-level Description". Our goal was to introduce a layer that allows an abstraction level for all Connection Protocol Adapters in order to communicate with the IoT SE Platform Core using a common internal language. The "templates", we are referring to in the document, are a kind of rules to translate any specific protocol into the common internal language and not a mechanism to generate Connection Protocol Adapters. This mechanism to automatically generate Connection Protocol Adapters is in any case very interesting and we could add it to the architecture document, if needed. * Component Access Policy Control - The second point of the epic for this component treats the access as a matter of payment (e.g. access only free services), while we intend the access as a matter of permissions to access resources. In our opinion these are different levels and they don't belong to the same component. * Component Quality of Service Control - From the grid it looks like that no asset has this functionality readily available, but since this component is not fundamental for a prototype of the IoT SE Platform, it can be left out or postponed in the future. For the other components we don't have specific considerations for the moment, but it looks like that Pangoo/M2MPlanet (by Orange) and Cumulocity (by NSN) are the assets that are more in line with our requirements. What do you think of this initial analysis of the assets? Are there any comments on these considerations? If you agree we could proceed with a more detailed analysis of the two proposed assets. Best regards, Sabrina Guerra __________________________________ Telecom Italia S.p.a. Strategia e Innovazione, Research & Trends Telefono +39 011 228 8359 Cellulare +39 331 600 1349 Questo messaggio e i suoi allegati sono indirizzati esclusivamente alle persone indicate. La diffusione, copia o qualsiasi altra azione derivante dalla conoscenza di queste informazioni sono rigorosamente vietate. Qualora abbiate ricevuto questo documento per errore siete cortesemente pregati di darne immediata comunicazione al mittente e di provvedere alla sua distruzione, Grazie. This e-mail and any attachments is confidential and may contain privileged information intended for the addressee(s) only. Dissemination, copying, printing or use by anybody else is unauthorised. If you are not the intended recipient, please delete this message and any attachments and advise the sender by return e-mail, Thanks. [rispetta l'ambiente]Rispetta l'ambiente. Non stampare questa mail se non ? necessario. ________________________________ 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 -- ------------------------------------- Ricardo de las Heras M2M Research Project Manager E-mail: rheras at tid.es Phone1: (+34) 983 367625 Phone2 OCS: (+34) 91 31 29511 Phone3 Skype: (+34) 91 1878107 + Ext: 327 Telef?nica I+D ------------------------------------- ________________________________ Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra pol?tica de env?o y recepci?n de correo electr?nico en el enlace situado m?s abajo. This message is intended exclusively for its addressee. We only send and receive email on the basis of the terms set out at. http://www.tid.es/ES/PAGINAS/disclaimer.aspx -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.gif Type: image/gif Size: 677 bytes Desc: image001.gif URL: From lorant.farkas at nsn.com Mon Sep 12 08:57:00 2011 From: lorant.farkas at nsn.com (Farkas, Lorant (NSN - HU/Budapest)) Date: Mon, 12 Sep 2011 09:57:00 +0300 Subject: [Fiware-iot] [FusionForge Problems]: Wiki In-Reply-To: <8152E2132B13FB488CFD1947E2DEF19C1CFA9F8D@DAPHNIS.office.hd> References: <8152E2132B13FB488CFD1947E2DEF19C1CFA6BC2@DAPHNIS.office.hd> <93D28BDF64839C468B848D14227151A20243450E@FIESEXC014.nsn-intra.net> <8152E2132B13FB488CFD1947E2DEF19C1CFA9F8D@DAPHNIS.office.hd> Message-ID: <93D28BDF64839C468B848D14227151A202434574@FIESEXC014.nsn-intra.net> Hi Ern?, I can see 2 reasons: 1. The directory is not visible until you don't store something in it 2. You might not have logged in, visible in the top right hand corner of the browser window. Then the document gets automatically to "pending". It happened to me already several times Br, Lorant ________________________________ From: ext Ernoe Kovacs [mailto:Ernoe.Kovacs at neclab.eu] Sent: Monday, September 12, 2011 8:39 AM To: Farkas, Lorant (NSN - HU/Budapest); Ricardo de las Heras; thierry.nagellen at orange-ftgroup.com Cc: fiware-iot at lists.fi-ware.eu Subject: RE: [Fiware-iot] [FusionForge Problems]: Wiki Lorant, thanks a lot. I did some small editing and removed the [Temporary] marker, as this could be the place where the document might be stored. Any idea why I was not able to do this kind of editing (creating a directory)? - Ern? From: Farkas, Lorant (NSN - HU/Budapest) [mailto:lorant.farkas at nsn.com] Sent: Montag, 12. September 2011 08:16 To: Ernoe Kovacs; Ricardo de las Heras; thierry.nagellen at orange-ftgroup.com Cc: fiware-iot at lists.fi-ware.eu Subject: RE: [Fiware-iot] [FusionForge Problems]: Wiki Dear All, I moved these docs to the "Standardization" category. Br, Lorant ________________________________ From: fiware-iot-bounces at lists.fi-ware.eu [mailto:fiware-iot-bounces at lists.fi-ware.eu] On Behalf Of ext Ernoe Kovacs Sent: Thursday, September 08, 2011 9:11 AM To: Ricardo de las Heras; thierry.nagellen at orange-ftgroup.com Cc: fiware-iot at lists.fi-ware.eu Subject: [Fiware-iot] [FusionForge Problems]: Wiki Hi Thierry, (a) when trying to add the OMA NGSI docs, I was searching for a Wiki function. According to the doc, there is one, but I cannot find it. I saw it on other FusionForge installations as an additional tab on the level of Docs, Tasks, Lists, .... I assume there is a respective pljugin that needs to be installed... (b) SVN Support Is the SVN support installed and activated? Thanks for the help and for forwarding to PCC and Technical Support Ern? From: Ernoe Kovacs Sent: Donnerstag, 8. September 2011 09:06 To: Ernoe Kovacs; Ricardo de las Heras; thierry.nagellen at orange-ftgroup.com Cc: fiware-iot at lists.fi-ware.eu; fabioluigi.bellifemine at telecomitalia.it; claudio.borean at telecomitalia.it Subject: OMA NGSI API Dear all, yesterday I promised some more information on the OMA NGSI APIs. You can now find here FI-Ware IoT -> Docs -> Uncategorized Submissions https://forge.fi-ware.eu/docman/?group_id=11 (a) OMA NGSI Info - Document with links to the standard documents and related information There is a good OMA NGSI overview presentation referenced. I recommend to read this. (b) Paper and presentation at ICIN'2010 Gives more insights into the Ctx API which we think is relevant for IoT - Ern? From: fiware-iot-bounces at lists.fi-ware.eu [mailto:fiware-iot-bounces at lists.fi-ware.eu] On Behalf Of Ernoe Kovacs Sent: Dienstag, 6. September 2011 16:03 To: Ricardo de las Heras; thierry.nagellen at orange-ftgroup.com Cc: fiware-iot at lists.fi-ware.eu; fabioluigi.bellifemine at telecomitalia.it; claudio.borean at telecomitalia.it Subject: Re: [Fiware-iot] First initial analysis of the IoT Assets mapping for the task 5.1 IoT Communications Hi all, fast reply here, I provide more background information to study later on. (a) Original discussion "Connection Protocol Adapter" or "component connection Protocol Adapter" I think we are all sharing the same idea here. We have very heterogeneous M2M area network protocols including very different data models. We need to map this into a common protocol model and common data model. Let me go one step deeper: Sensor support very different kind of interactions. Some are waiting to be queried. Some send their information periodically, some send the information when a substantial change has happened, some have a management interface to configure their behavior, etc. etc. Some needs sessions, some only have one shot queries that include authentication each time they are called. I fear you find anything that can be imagined on that level An abstraction layer needs to map all these protocols into a single one. This single one is the language to talk inside of the systems. The "Connection Protocol Adapter" are the software modules that - map between the real protocol on the M2M Area network and the high-level protocol. - fill the gap between what the sensor offers and what the high-level protocol requests. For example, if the high level protocol supports subscriptions and the lwo level one not, either the "connection protocol adapter" or the "Abstraction layer" need to provide the needed functionality... (b) OMA NGSI In the sense of the discussion under (a), OMA NGSI can be the higher level protocol that the abstraction layer supports. OMA NGSI supports updates, queries, subscriptions, and notifications. (c) OMA NGSI as Exposure API For interacting with external systems like WP6, OMA NGSI is a standardized API with comparable rich set of operation. So we can use it as an exposure API towards applications. It also has a data model based on entities, attributes and meta-data about them. Note: The exposure API can be used on the IoT Device, on the IoT Gateway or on the IoT Core. (d) OMA NGSI and IoT Gateways-2-IoT Core Communication Besides the data flow services (update, query, subscribe, notify), OMA NGSI has a small set of primitives that enables two systems to exchange meta-data about the contained objects. So a IoT gateway can register with the IoT Core and inform them that e.g it is currently managing 1 RFID readers, will sent information about "hasSeen RFID Tags" and has a GPS receiver. Yes, OMA NGSI can be used for that as well. I am expecting that we might extend the information exchanged between IoT GW and IoT Core, but OMA NGSI is a starting point. Our ISIS system implements large parts of the OMA NGSI features. @Thierry: You are right this is different to the NFC protocol , 6LowPAN, ZigBee. The Connection Protocol Adapter can handle this heterogenity. I am reasonable sure that FIWare will not try to overcome the heterogeneity on Layer 1 (Radio) or L2 (Data Link). IMHO, the approach cannot be to map either directly into each other (nightmare, n x m) or into a higher level protocol ( n x 1). The alter approach is what we are suggesting. In our ISIS system we have shown it can work... - Ern? From: fiware-iot-bounces at lists.fi-ware.eu [mailto:fiware-iot-bounces at lists.fi-ware.eu] On Behalf Of Ricardo de las Heras Sent: Dienstag, 6. September 2011 14:01 To: thierry.nagellen at orange-ftgroup.com Cc: fabioluigi.bellifemine at telecomitalia.it; claudio.borean at telecomitalia.it; fiware-iot at lists.fi-ware.eu Subject: Re: [Fiware-iot] First initial analysis of the IoT Assets mapping for the task 5.1 IoT Communications Dear Thierry, yes, you're right regarding the issue that we have to deal with a broad type of protocols in order to communicate sensors, actuators, devices with a gateway. But my question was beyond this step, when we have to specify a protocol for interchanging data between every gateway and the IoT platform (using SensorAPI for example in the case of IDAS asset). At this level and for interchanging data with context awareness system or other external applications, then is where I tried to explain that could be useful to include the protocol NGSI as a reference protocol of the IoT WP5. Maybe some of our colleagues from NEC or TI can provide us more background with it, but NGSI seems to be quite flexible and direct in order to allow us to map the existent protocols in every asset to the NGSI standard. Sorry if there is any mistake in the details of my explaination. ISIS asset (NEC) for example provides an API interface based on NGSI. So this could be a perfect example of it. cheers, Ricardo. thierry.nagellen at orange-ftgroup.com wrote: Dear Ricardo Maybe I missed a point or there is a misunderstanding. We have to deal here with communication protocols as NFC which could use different frequencies, 6LowPan or Zigbee, Bluetooth, etc... and NGSI try to formalize a standard to exchange context information with applications. In the case of the "component connection Protocol Adapter" the main issue is that lots of communication protocols are used by different devices and if we do not have this component we will not provide a common access to different types of devices, which deal with one or more IoT resources. As I understand NGSI, but I'm not an expert, it provides a common model with dedicated functionalities to define a context element. This is quite relevant for DCM to manage context but less useful for events description for example. But maybe my understanding of NGSI is too limited. Best regards Thierry De : Ricardo de las Heras [mailto:rheras at tid.es] Envoy? : mardi 6 septembre 2011 12:52 ? : NAGELLEN Thierry RD-BIZZ-SOP; sabrina.guerra at telecomitalia.it Cc : fiware-iot at lists.fi-ware.eu; fabioluigi.bellifemine at telecomitalia.it; claudio.borean at telecomitalia.it Objet : Re: [Fiware-iot] First initial analysis of the IoT Assets mapping for the task 5.1 IoT Communications Dear Sabrina, Thierry, regarding your first point: "Component Connection Protocol Adapter - the better solution is that as many as possible protocols are supported by the IoT Services Enablement Platform, for this reason all the assets presented can be included into the implementation of the IoT SE Platform, provided that it's possible to translate them in a common internal form through the component Communication Protocol Abstraction Definition." I'm not an expert on these type of protocols, but as far as I know within the WP6 (Contextual) they are going to use an the OMA standard TS-NGSI for the Context_Management. (http://www.openmobilealliance.org/technical/release_program/ose_archive.aspx) You can find attached a pdf with the NGSI specification. Indeed TI and NEC were very active on the definition of this standard, so it would be fine if we define it as the common language within WP5, maybe mapping the protocols used in the assets to NGSI, having clear advantages in order to communicate us with the rest of WPs, mainly with WP6. Furthermore, the WAC initiative (http://en.wikipedia.org/wiki/Wholesale_Applications_Community) fully support NGSI as well, so it is again a new point for reinforce this decision, with clear advantages for Fiware using this important OMA standard. I don't know what's your point of view, maybe Thierry you can discuss it with Juanjo Hierro, thanks, regards, Ricardo. -- ------------------------------------- Ricardo de las Heras M2M Research Project Manager E-mail: rheras at tid.es Phone1: (+34) 983 367625 Phone2 OCS: (+34) 91 31 29511 Phone3 Skype: (+34) 91 1878107 + Ext: 327 Telef?nica I+D ------------------------------------- thierry.nagellen at orange-ftgroup.com wrote: Hi Sabrina Thanks for your first analysis. We had slightly discussed the point of protocols IoT SE has to support to deal with different kind of things. I fully support your approach that the optimal way for us is to integrate the protocols through the assets we have because to implement all protocols will take lots of time and the main topic is how we can provide a common access. But in this case, partners would have to develop a dedicated interface to be integrated in the component "Connection Protocol Adapter". This should be a good point for the Open Specification and to target different Use Cases. Regarding EPICs which are different from the description of HLD deliverable, feel free to add a new EPIC to be in line with the deliverable and we would be able to discuss which one is the more critical and how we can put some priorities. We can have "several" EPIC per component and we can discuss which are the most valuable and how we could implement them regarding the assets. So at this moment, this is really fully open to add details and to improve these descriptions. Component Access Policy Control: I think the EPIC would not focus on payment matter but try to explain that as an owner of devices and IoT resources, I can define some criteria to give access right. In this case this could be a Social Network or Open Source Community approach to share devices and things with no commercial ASP, as you could provide access rights only for SMEs, or for eHealth applications despite your IoT Resources are not tagged as eHealth resources. Maybe you can refine this EPIC to describe that several criteria could be used to define access rights. This point should be discussed with the Security team during Turin meeting to check what kind of features they can provide. Quality of service control: this feature is clearly not included in any assets. Based on some comments from UA projects this point should be fundamental (to Instant Mobility project, this quality of service is expected for emergency concerns in a city, or to Safecity project to reach in the proper time some video resources in the city). But as we do not have any asset we can put the priority on "Should" and manage this issue later on (2nd round of FI-Ware backlog, or through the open calls if we know some other partners who could have this kind of asset). We have also holes in Process Automation or Data Handling, so we will not do everything now and if all IoT partners agree, we can delay it. But I think that Thales could have an asset to fulfill this requirement. We would wait one more week for their contributions to decide it. BR Thierry De : fiware-iot-bounces at lists.fi-ware.eu [mailto:fiware-iot-bounces at lists.fi-ware.eu] De la part de Guerra Sabrina Envoy? : lundi 5 septembre 2011 13:21 ? : 'fiware-iot at lists.fi-ware.eu' Cc : Bellifemine Fabio Luigi; Borean Claudio Objet : [Fiware-iot] First initial analysis of the IoT Assets mapping for the task 5.1 IoT Communications Hi, we've begun to analyze the list of assets related to the "IoT Communication" task submitted by the FI-WARE partners. Some initial considerations for the components are: * Component Connection Protocol Adapter - the better solution is that as many as possible protocols are supported by the IoT Services Enablement Platform, for this reason all the assets presented can be included into the implementation of the IoT SE Platform, provided that it's possible to translate them in a common internal form through the component Communication Protocol Abstraction Definition. * Component Communication Protocol Abstraction Definition - the epic for this component is different from the description included in the document "FI-WARE High-level Description". Our goal was to introduce a layer that allows an abstraction level for all Connection Protocol Adapters in order to communicate with the IoT SE Platform Core using a common internal language. The "templates", we are referring to in the document, are a kind of rules to translate any specific protocol into the common internal language and not a mechanism to generate Connection Protocol Adapters. This mechanism to automatically generate Connection Protocol Adapters is in any case very interesting and we could add it to the architecture document, if needed. * Component Access Policy Control - The second point of the epic for this component treats the access as a matter of payment (e.g. access only free services), while we intend the access as a matter of permissions to access resources. In our opinion these are different levels and they don't belong to the same component. * Component Quality of Service Control - From the grid it looks like that no asset has this functionality readily available, but since this component is not fundamental for a prototype of the IoT SE Platform, it can be left out or postponed in the future. For the other components we don't have specific considerations for the moment, but it looks like that Pangoo/M2MPlanet (by Orange) and Cumulocity (by NSN) are the assets that are more in line with our requirements. What do you think of this initial analysis of the assets? Are there any comments on these considerations? If you agree we could proceed with a more detailed analysis of the two proposed assets. Best regards, Sabrina Guerra __________________________________ Telecom Italia S.p.a. Strategia e Innovazione, Research & Trends Telefono +39 011 228 8359 Cellulare +39 331 600 1349 Questo messaggio e i suoi allegati sono indirizzati esclusivamente alle persone indicate. La diffusione, copia o qualsiasi altra azione derivante dalla conoscenza di queste informazioni sono rigorosamente vietate. Qualora abbiate ricevuto questo documento per errore siete cortesemente pregati di darne immediata comunicazione al mittente e di provvedere alla sua distruzione, Grazie. This e-mail and any attachments is confidential and may contain privileged information intended for the addressee(s) only. Dissemination, copying, printing or use by anybody else is unauthorised. If you are not the intended recipient, please delete this message and any attachments and advise the sender by return e-mail, Thanks. Rispetta l'ambiente. Non stampare questa mail se non ? necessario. ________________________________ 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 -- ------------------------------------- Ricardo de las Heras M2M Research Project Manager E-mail: rheras at tid.es Phone1: (+34) 983 367625 Phone2 OCS: (+34) 91 31 29511 Phone3 Skype: (+34) 91 1878107 + Ext: 327 Telef?nica I+D ------------------------------------- ________________________________ Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra pol?tica de env?o y recepci?n de correo electr?nico en el enlace situado m?s abajo. This message is intended exclusively for its addressee. We only send and receive email on the basis of the terms set out at. http://www.tid.es/ES/PAGINAS/disclaimer.aspx -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.gif Type: image/gif Size: 677 bytes Desc: image001.gif URL: From thierry.nagellen at orange-ftgroup.com Mon Sep 12 08:49:09 2011 From: thierry.nagellen at orange-ftgroup.com (thierry.nagellen at orange-ftgroup.com) Date: Mon, 12 Sep 2011 08:49:09 +0200 Subject: [Fiware-iot] [FusionForge Problems]: Wiki In-Reply-To: <8152E2132B13FB488CFD1947E2DEF19C1CFA9F8D@DAPHNIS.office.hd> References: <8152E2132B13FB488CFD1947E2DEF19C1CFA6BC2@DAPHNIS.office.hd> <93D28BDF64839C468B848D14227151A20243450E@FIESEXC014.nsn-intra.net> <8152E2132B13FB488CFD1947E2DEF19C1CFA9F8D@DAPHNIS.office.hd> Message-ID: Hi Ern?, We have to check with Juanjo if the associated rights to your profile, which is simply not "admin", provide rights to create folders or if only admins have these rights. If this is the case we could ask to have more freedom, for example not new folders at root level (level 1) but some rights other levels. Best regards Thierry De : Ernoe Kovacs [mailto:Ernoe.Kovacs at neclab.eu] Envoy? : lundi 12 septembre 2011 08:39 ? : Farkas, Lorant (NSN - HU/Budapest); Ricardo de las Heras; NAGELLEN Thierry RD-BIZZ-SOP Cc : fiware-iot at lists.fi-ware.eu Objet : RE: [Fiware-iot] [FusionForge Problems]: Wiki Lorant, thanks a lot. I did some small editing and removed the [Temporary] marker, as this could be the place where the document might be stored. Any idea why I was not able to do this kind of editing (creating a directory)? - Ern? From: Farkas, Lorant (NSN - HU/Budapest) [mailto:lorant.farkas at nsn.com] Sent: Montag, 12. September 2011 08:16 To: Ernoe Kovacs; Ricardo de las Heras; thierry.nagellen at orange-ftgroup.com Cc: fiware-iot at lists.fi-ware.eu Subject: RE: [Fiware-iot] [FusionForge Problems]: Wiki Dear All, I moved these docs to the "Standardization" category. Br, Lorant ________________________________ From: fiware-iot-bounces at lists.fi-ware.eu [mailto:fiware-iot-bounces at lists.fi-ware.eu] On Behalf Of ext Ernoe Kovacs Sent: Thursday, September 08, 2011 9:11 AM To: Ricardo de las Heras; thierry.nagellen at orange-ftgroup.com Cc: fiware-iot at lists.fi-ware.eu Subject: [Fiware-iot] [FusionForge Problems]: Wiki Hi Thierry, (a) when trying to add the OMA NGSI docs, I was searching for a Wiki function. According to the doc, there is one, but I cannot find it. I saw it on other FusionForge installations as an additional tab on the level of Docs, Tasks, Lists, .... I assume there is a respective pljugin that needs to be installed... (b) SVN Support Is the SVN support installed and activated? Thanks for the help and for forwarding to PCC and Technical Support Ern? From: Ernoe Kovacs Sent: Donnerstag, 8. September 2011 09:06 To: Ernoe Kovacs; Ricardo de las Heras; thierry.nagellen at orange-ftgroup.com Cc: fiware-iot at lists.fi-ware.eu; fabioluigi.bellifemine at telecomitalia.it; claudio.borean at telecomitalia.it Subject: OMA NGSI API Dear all, yesterday I promised some more information on the OMA NGSI APIs. You can now find here FI-Ware IoT -> Docs -> Uncategorized Submissions https://forge.fi-ware.eu/docman/?group_id=11 (a) OMA NGSI Info - Document with links to the standard documents and related information There is a good OMA NGSI overview presentation referenced. I recommend to read this. (b) Paper and presentation at ICIN'2010 Gives more insights into the Ctx API which we think is relevant for IoT - Ern? From: fiware-iot-bounces at lists.fi-ware.eu [mailto:fiware-iot-bounces at lists.fi-ware.eu] On Behalf Of Ernoe Kovacs Sent: Dienstag, 6. September 2011 16:03 To: Ricardo de las Heras; thierry.nagellen at orange-ftgroup.com Cc: fiware-iot at lists.fi-ware.eu; fabioluigi.bellifemine at telecomitalia.it; claudio.borean at telecomitalia.it Subject: Re: [Fiware-iot] First initial analysis of the IoT Assets mapping for the task 5.1 IoT Communications Hi all, fast reply here, I provide more background information to study later on. (a) Original discussion "Connection Protocol Adapter" or "component connection Protocol Adapter" I think we are all sharing the same idea here. We have very heterogeneous M2M area network protocols including very different data models. We need to map this into a common protocol model and common data model. Let me go one step deeper: Sensor support very different kind of interactions. Some are waiting to be queried. Some send their information periodically, some send the information when a substantial change has happened, some have a management interface to configure their behavior, etc. etc. Some needs sessions, some only have one shot queries that include authentication each time they are called. I fear you find anything that can be imagined on that level An abstraction layer needs to map all these protocols into a single one. This single one is the language to talk inside of the systems. The "Connection Protocol Adapter" are the software modules that - map between the real protocol on the M2M Area network and the high-level protocol. - fill the gap between what the sensor offers and what the high-level protocol requests. For example, if the high level protocol supports subscriptions and the lwo level one not, either the "connection protocol adapter" or the "Abstraction layer" need to provide the needed functionality... (b) OMA NGSI In the sense of the discussion under (a), OMA NGSI can be the higher level protocol that the abstraction layer supports. OMA NGSI supports updates, queries, subscriptions, and notifications. (c) OMA NGSI as Exposure API For interacting with external systems like WP6, OMA NGSI is a standardized API with comparable rich set of operation. So we can use it as an exposure API towards applications. It also has a data model based on entities, attributes and meta-data about them. Note: The exposure API can be used on the IoT Device, on the IoT Gateway or on the IoT Core. (d) OMA NGSI and IoT Gateways-2-IoT Core Communication Besides the data flow services (update, query, subscribe, notify), OMA NGSI has a small set of primitives that enables two systems to exchange meta-data about the contained objects. So a IoT gateway can register with the IoT Core and inform them that e.g it is currently managing 1 RFID readers, will sent information about "hasSeen RFID Tags" and has a GPS receiver. Yes, OMA NGSI can be used for that as well. I am expecting that we might extend the information exchanged between IoT GW and IoT Core, but OMA NGSI is a starting point. Our ISIS system implements large parts of the OMA NGSI features. @Thierry: You are right this is different to the NFC protocol , 6LowPAN, ZigBee. The Connection Protocol Adapter can handle this heterogenity. I am reasonable sure that FIWare will not try to overcome the heterogeneity on Layer 1 (Radio) or L2 (Data Link). IMHO, the approach cannot be to map either directly into each other (nightmare, n x m) or into a higher level protocol ( n x 1). The alter approach is what we are suggesting. In our ISIS system we have shown it can work... - Ern? From: fiware-iot-bounces at lists.fi-ware.eu [mailto:fiware-iot-bounces at lists.fi-ware.eu] On Behalf Of Ricardo de las Heras Sent: Dienstag, 6. September 2011 14:01 To: thierry.nagellen at orange-ftgroup.com Cc: fabioluigi.bellifemine at telecomitalia.it; claudio.borean at telecomitalia.it; fiware-iot at lists.fi-ware.eu Subject: Re: [Fiware-iot] First initial analysis of the IoT Assets mapping for the task 5.1 IoT Communications Dear Thierry, yes, you're right regarding the issue that we have to deal with a broad type of protocols in order to communicate sensors, actuators, devices with a gateway. But my question was beyond this step, when we have to specify a protocol for interchanging data between every gateway and the IoT platform (using SensorAPI for example in the case of IDAS asset). At this level and for interchanging data with context awareness system or other external applications, then is where I tried to explain that could be useful to include the protocol NGSI as a reference protocol of the IoT WP5. Maybe some of our colleagues from NEC or TI can provide us more background with it, but NGSI seems to be quite flexible and direct in order to allow us to map the existent protocols in every asset to the NGSI standard. Sorry if there is any mistake in the details of my explaination. ISIS asset (NEC) for example provides an API interface based on NGSI. So this could be a perfect example of it. cheers, Ricardo. thierry.nagellen at orange-ftgroup.com wrote: Dear Ricardo Maybe I missed a point or there is a misunderstanding. We have to deal here with communication protocols as NFC which could use different frequencies, 6LowPan or Zigbee, Bluetooth, etc... and NGSI try to formalize a standard to exchange context information with applications. In the case of the "component connection Protocol Adapter" the main issue is that lots of communication protocols are used by different devices and if we do not have this component we will not provide a common access to different types of devices, which deal with one or more IoT resources. As I understand NGSI, but I'm not an expert, it provides a common model with dedicated functionalities to define a context element. This is quite relevant for DCM to manage context but less useful for events description for example. But maybe my understanding of NGSI is too limited. Best regards Thierry De : Ricardo de las Heras [mailto:rheras at tid.es] Envoy? : mardi 6 septembre 2011 12:52 ? : NAGELLEN Thierry RD-BIZZ-SOP; sabrina.guerra at telecomitalia.it Cc : fiware-iot at lists.fi-ware.eu; fabioluigi.bellifemine at telecomitalia.it; claudio.borean at telecomitalia.it Objet : Re: [Fiware-iot] First initial analysis of the IoT Assets mapping for the task 5.1 IoT Communications Dear Sabrina, Thierry, regarding your first point: "Component Connection Protocol Adapter - the better solution is that as many as possible protocols are supported by the IoT Services Enablement Platform, for this reason all the assets presented can be included into the implementation of the IoT SE Platform, provided that it's possible to translate them in a common internal form through the component Communication Protocol Abstraction Definition." I'm not an expert on these type of protocols, but as far as I know within the WP6 (Contextual) they are going to use an the OMA standard TS-NGSI for the Context_Management. (http://www.openmobilealliance.org/technical/release_program/ose_archive.aspx) You can find attached a pdf with the NGSI specification. Indeed TI and NEC were very active on the definition of this standard, so it would be fine if we define it as the common language within WP5, maybe mapping the protocols used in the assets to NGSI, having clear advantages in order to communicate us with the rest of WPs, mainly with WP6. Furthermore, the WAC initiative (http://en.wikipedia.org/wiki/Wholesale_Applications_Community) fully support NGSI as well, so it is again a new point for reinforce this decision, with clear advantages for Fiware using this important OMA standard. I don't know what's your point of view, maybe Thierry you can discuss it with Juanjo Hierro, thanks, regards, Ricardo. -- ------------------------------------- Ricardo de las Heras M2M Research Project Manager E-mail: rheras at tid.es Phone1: (+34) 983 367625 Phone2 OCS: (+34) 91 31 29511 Phone3 Skype: (+34) 91 1878107 + Ext: 327 Telef?nica I+D ------------------------------------- thierry.nagellen at orange-ftgroup.com wrote: Hi Sabrina Thanks for your first analysis. We had slightly discussed the point of protocols IoT SE has to support to deal with different kind of things. I fully support your approach that the optimal way for us is to integrate the protocols through the assets we have because to implement all protocols will take lots of time and the main topic is how we can provide a common access. But in this case, partners would have to develop a dedicated interface to be integrated in the component "Connection Protocol Adapter". This should be a good point for the Open Specification and to target different Use Cases. Regarding EPICs which are different from the description of HLD deliverable, feel free to add a new EPIC to be in line with the deliverable and we would be able to discuss which one is the more critical and how we can put some priorities. We can have "several" EPIC per component and we can discuss which are the most valuable and how we could implement them regarding the assets. So at this moment, this is really fully open to add details and to improve these descriptions. Component Access Policy Control: I think the EPIC would not focus on payment matter but try to explain that as an owner of devices and IoT resources, I can define some criteria to give access right. In this case this could be a Social Network or Open Source Community approach to share devices and things with no commercial ASP, as you could provide access rights only for SMEs, or for eHealth applications despite your IoT Resources are not tagged as eHealth resources. Maybe you can refine this EPIC to describe that several criteria could be used to define access rights. This point should be discussed with the Security team during Turin meeting to check what kind of features they can provide. Quality of service control: this feature is clearly not included in any assets. Based on some comments from UA projects this point should be fundamental (to Instant Mobility project, this quality of service is expected for emergency concerns in a city, or to Safecity project to reach in the proper time some video resources in the city). But as we do not have any asset we can put the priority on "Should" and manage this issue later on (2nd round of FI-Ware backlog, or through the open calls if we know some other partners who could have this kind of asset). We have also holes in Process Automation or Data Handling, so we will not do everything now and if all IoT partners agree, we can delay it. But I think that Thales could have an asset to fulfill this requirement. We would wait one more week for their contributions to decide it. BR Thierry De : fiware-iot-bounces at lists.fi-ware.eu [mailto:fiware-iot-bounces at lists.fi-ware.eu] De la part de Guerra Sabrina Envoy? : lundi 5 septembre 2011 13:21 ? : 'fiware-iot at lists.fi-ware.eu' Cc : Bellifemine Fabio Luigi; Borean Claudio Objet : [Fiware-iot] First initial analysis of the IoT Assets mapping for the task 5.1 IoT Communications Hi, we've begun to analyze the list of assets related to the "IoT Communication" task submitted by the FI-WARE partners. Some initial considerations for the components are: * Component Connection Protocol Adapter - the better solution is that as many as possible protocols are supported by the IoT Services Enablement Platform, for this reason all the assets presented can be included into the implementation of the IoT SE Platform, provided that it's possible to translate them in a common internal form through the component Communication Protocol Abstraction Definition. * Component Communication Protocol Abstraction Definition - the epic for this component is different from the description included in the document "FI-WARE High-level Description". Our goal was to introduce a layer that allows an abstraction level for all Connection Protocol Adapters in order to communicate with the IoT SE Platform Core using a common internal language. The "templates", we are referring to in the document, are a kind of rules to translate any specific protocol into the common internal language and not a mechanism to generate Connection Protocol Adapters. This mechanism to automatically generate Connection Protocol Adapters is in any case very interesting and we could add it to the architecture document, if needed. * Component Access Policy Control - The second point of the epic for this component treats the access as a matter of payment (e.g. access only free services), while we intend the access as a matter of permissions to access resources. In our opinion these are different levels and they don't belong to the same component. * Component Quality of Service Control - From the grid it looks like that no asset has this functionality readily available, but since this component is not fundamental for a prototype of the IoT SE Platform, it can be left out or postponed in the future. For the other components we don't have specific considerations for the moment, but it looks like that Pangoo/M2MPlanet (by Orange) and Cumulocity (by NSN) are the assets that are more in line with our requirements. What do you think of this initial analysis of the assets? Are there any comments on these considerations? If you agree we could proceed with a more detailed analysis of the two proposed assets. Best regards, Sabrina Guerra __________________________________ Telecom Italia S.p.a. Strategia e Innovazione, Research & Trends Telefono +39 011 228 8359 Cellulare +39 331 600 1349 Questo messaggio e i suoi allegati sono indirizzati esclusivamente alle persone indicate. La diffusione, copia o qualsiasi altra azione derivante dalla conoscenza di queste informazioni sono rigorosamente vietate. Qualora abbiate ricevuto questo documento per errore siete cortesemente pregati di darne immediata comunicazione al mittente e di provvedere alla sua distruzione, Grazie. This e-mail and any attachments is confidential and may contain privileged information intended for the addressee(s) only. Dissemination, copying, printing or use by anybody else is unauthorised. If you are not the intended recipient, please delete this message and any attachments and advise the sender by return e-mail, Thanks. Rispetta l'ambiente. Non stampare questa mail se non ? necessario. ________________________________ 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 -- ------------------------------------- Ricardo de las Heras M2M Research Project Manager E-mail: rheras at tid.es Phone1: (+34) 983 367625 Phone2 OCS: (+34) 91 31 29511 Phone3 Skype: (+34) 91 1878107 + Ext: 327 Telef?nica I+D ------------------------------------- ________________________________ Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra pol?tica de env?o y recepci?n de correo electr?nico en el enlace situado m?s abajo. This message is intended exclusively for its addressee. We only send and receive email on the basis of the terms set out at. http://www.tid.es/ES/PAGINAS/disclaimer.aspx -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.gif Type: image/gif Size: 677 bytes Desc: image001.gif URL: From stephan.haller at sap.com Mon Sep 12 09:51:25 2011 From: stephan.haller at sap.com (Haller, Stephan) Date: Mon, 12 Sep 2011 09:51:25 +0200 Subject: [Fiware-iot] [FusionForge Problems with] OMA NGSI API In-Reply-To: <8152E2132B13FB488CFD1947E2DEF19C1CFA6B43@DAPHNIS.office.hd> References: <8152E2132B13FB488CFD1947E2DEF19C1CFA6B43@DAPHNIS.office.hd> Message-ID: <0D2446AEB6CAED48BB046223733964A54C3EA9A44E@DEWDFECCR01.wdf.sap.corp> All, I have started to write up some user stories for the area where IoT and Apps&Services meet. This is also where our core interest lies and where we will bring in some assets (from the IoT-A project). This is just a first draft, far from complete. But I wanted to provide this as an input for the meetings in Torino. Regards, -Stephan Stephan Haller Development Architect - Internet of Things, SAP Research SAP (Schweiz) AG, Kreuzplatz, Kreuzplatz 20, CH-8008 Z?rich, Switzerland T +41 58 871 78 45, F +41 58 871 78 12 mailto:stephan.haller at sap.com Please consider the impact on the environment before printing this e-mail. -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: FI IoT User Stories.docx Type: application/vnd.openxmlformats-officedocument.wordprocessingml.document Size: 13348 bytes Desc: FI IoT User Stories.docx URL: From lorant.farkas at nsn.com Mon Sep 12 10:05:54 2011 From: lorant.farkas at nsn.com (Farkas, Lorant (NSN - HU/Budapest)) Date: Mon, 12 Sep 2011 11:05:54 +0300 Subject: [Fiware-iot] FI-WARE joint session at the meeting In-Reply-To: References: Message-ID: <93D28BDF64839C468B848D14227151A202434657@FIESEXC014.nsn-intra.net> Dear Pier, We agree. If possible we would like to plan it for Thu morning, say 1 hour or 1.5 hours, from 9 AM. The parts of common interest we identified are: -cloud proxy, CE vs IoT gateway -device concept in I2ND (CDI) vs IoT device in IoT -points of contact/interfaces between I2ND and IoT So as a tentativa agenda I would propose the following: * I2ND elaborates on CDI and cloud proxy concepts + interfaces 1+2 (20 minutes) * IoT elaborates on IoT device and IoT gateway concepts + the IoT communications task (20 minutes) * Brainstorming discussion (10-20 minutes) * Conclusions, action items (10-20 minutes) Any feedback from any side is welcome. Thanks & Br, Lorant ________________________________ From: ext Garino Pierangelo [mailto:pierangelo.garino at telecomitalia.it] Sent: Friday, September 09, 2011 3:29 PM To: 'thierry.nagellen at orange-ftgroup.com'; Farkas, Lorant (NSN - HU/Budapest) Cc: hans.einsiedler at telekom.de Subject: FI-WARE joint session at the meeting Dear Thierry and Lorant, I propose that we schedule a joint session between IoT and I2ND chapters during the parallel session days at the meeting next week, as I believe topics which put in close relationship the GEs of the two chapters are several (e.g. interfacing to the cloud proxy/edge to access 'things', interfacing to the network and network services). We might plan one session either Wed afternoon or Thu morning. What do you think about this proposal? BR Pier ------------------------------------------------------------------ Telecom Italia Pierangelo Garino Innovation & Industry Relations - Research & Prototyping Via G. Reiss Romoli 274, I-10148 TORINO Tel: +39 011 228 7142 Questo messaggio e i suoi allegati sono indirizzati esclusivamente alle persone indicate. La diffusione, copia o qualsiasi altra azione derivante dalla conoscenza di queste informazioni sono rigorosamente vietate. Qualora abbiate ricevuto questo documento per errore siete cortesemente pregati di darne immediata comunicazione al mittente e di provvedere alla sua distruzione, Grazie. This e-mail and any attachments is confidential and may contain privileged information intended for the addressee(s) only. Dissemination, copying, printing or use by anybody else is unauthorised. If you are not the intended recipient, please delete this message and any attachments and advise the sender by return e-mail, Thanks. Rispetta l'ambiente. Non stampare questa mail se non ? necessario. -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: logo Ambiente_foglia.jpg Type: image/jpeg Size: 677 bytes Desc: logo Ambiente_foglia.jpg URL: From pierangelo.garino at telecomitalia.it Mon Sep 12 10:12:37 2011 From: pierangelo.garino at telecomitalia.it (Garino Pierangelo) Date: Mon, 12 Sep 2011 10:12:37 +0200 Subject: [Fiware-iot] R: FI-WARE joint session at the meeting In-Reply-To: <93D28BDF64839C468B848D14227151A202434657@FIESEXC014.nsn-intra.net> References: <93D28BDF64839C468B848D14227151A202434657@FIESEXC014.nsn-intra.net> Message-ID: Dear Lorant, that's fine to me. Let's start proposing the allocation of the session slot as you mention (i.e. Thu morning), then if more suggestions come for the agenda we'll refine it. BR Pier Da: Farkas, Lorant (NSN - HU/Budapest) [mailto:lorant.farkas at nsn.com] Inviato: luned? 12 settembre 2011 10:06 A: Garino Pierangelo; thierry.nagellen at orange-ftgroup.com Cc: hans.einsiedler at telekom.de; fiware-iot at lists.fi-ware.eu Oggetto: RE: FI-WARE joint session at the meeting Dear Pier, We agree. If possible we would like to plan it for Thu morning, say 1 hour or 1.5 hours, from 9 AM. The parts of common interest we identified are: -cloud proxy, CE vs IoT gateway -device concept in I2ND (CDI) vs IoT device in IoT -points of contact/interfaces between I2ND and IoT So as a tentativa agenda I would propose the following: * I2ND elaborates on CDI and cloud proxy concepts + interfaces 1+2 (20 minutes) * IoT elaborates on IoT device and IoT gateway concepts + the IoT communications task (20 minutes) * Brainstorming discussion (10-20 minutes) * Conclusions, action items (10-20 minutes) Any feedback from any side is welcome. Thanks & Br, Lorant ________________________________ From: ext Garino Pierangelo [mailto:pierangelo.garino at telecomitalia.it] Sent: Friday, September 09, 2011 3:29 PM To: 'thierry.nagellen at orange-ftgroup.com'; Farkas, Lorant (NSN - HU/Budapest) Cc: hans.einsiedler at telekom.de Subject: FI-WARE joint session at the meeting Dear Thierry and Lorant, I propose that we schedule a joint session between IoT and I2ND chapters during the parallel session days at the meeting next week, as I believe topics which put in close relationship the GEs of the two chapters are several (e.g. interfacing to the cloud proxy/edge to access 'things', interfacing to the network and network services). We might plan one session either Wed afternoon or Thu morning. What do you think about this proposal? BR Pier ------------------------------------------------------------------ Telecom Italia Pierangelo Garino Innovation & Industry Relations - Research & Prototyping Via G. Reiss Romoli 274, I-10148 TORINO Tel: +39 011 228 7142 Questo messaggio e i suoi allegati sono indirizzati esclusivamente alle persone indicate. La diffusione, copia o qualsiasi altra azione derivante dalla conoscenza di queste informazioni sono rigorosamente vietate. Qualora abbiate ricevuto questo documento per errore siete cortesemente pregati di darne immediata comunicazione al mittente e di provvedere alla sua distruzione, Grazie. This e-mail and any attachments is confidential and may contain privileged information intended for the addressee(s) only. Dissemination, copying, printing or use by anybody else is unauthorised. If you are not the intended recipient, please delete this message and any attachments and advise the sender by return e-mail, Thanks. [cid:image001.gif at 01CC7134.7F0A20B0]Rispetta l'ambiente. Non stampare questa mail se non ? necessario. Questo messaggio e i suoi allegati sono indirizzati esclusivamente alle persone indicate. La diffusione, copia o qualsiasi altra azione derivante dalla conoscenza di queste informazioni sono rigorosamente vietate. Qualora abbiate ricevuto questo documento per errore siete cortesemente pregati di darne immediata comunicazione al mittente e di provvedere alla sua distruzione, Grazie. This e-mail and any attachments is confidential and may contain privileged information intended for the addressee(s) only. Dissemination, copying, printing or use by anybody else is unauthorised. If you are not the intended recipient, please delete this message and any attachments and advise the sender by return e-mail, Thanks. [cid:00000000000000000000000000000001 at TI.Disclaimer]Rispetta l'ambiente. Non stampare questa mail se non ? necessario. -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.gif Type: image/gif Size: 677 bytes Desc: image001.gif URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: logo Ambiente_foglia.jpg Type: image/jpeg Size: 677 bytes Desc: logo Ambiente_foglia.jpg URL: From thierry.nagellen at orange-ftgroup.com Mon Sep 12 22:17:58 2011 From: thierry.nagellen at orange-ftgroup.com (thierry.nagellen at orange-ftgroup.com) Date: Mon, 12 Sep 2011 22:17:58 +0200 Subject: [Fiware-iot] [FusionForge Problems with] OMA NGSI API In-Reply-To: <0D2446AEB6CAED48BB046223733964A54C3EA9A44E@DEWDFECCR01.wdf.sap.corp> References: <8152E2132B13FB488CFD1947E2DEF19C1CFA6B43@DAPHNIS.office.hd> <0D2446AEB6CAED48BB046223733964A54C3EA9A44E@DEWDFECCR01.wdf.sap.corp> Message-ID: <23052_1315858707_4E6E6913_23052_397275_1_BAF83494CE653943A97B9F755016A066098203DF@ftrdmel1> HI Stefan Thanks a lot for your contribution. We will discuss all content during Torino meeting and try to find the best way for User stories description. Regarding IoT-A project, could you - with Ern? as your companies are partners of this project - share some expected deadlines and what kind of results could be used (if this information is public of course). Maybe we should also planned a meeting between WP IoT and IoT-A project to exchange about this issue, to improve some architecture elements and also to share the vision of UA projects because we should have more details at the end of September (first requirements, detailed presentation during Architecture Board 21-22/09). Do you think this join meeting could happen in Poznan (end of October, during the FI week?) BR Thierry De : Haller, Stephan [mailto:stephan.haller at sap.com] Envoy? : lundi 12 septembre 2011 09:51 ? : NAGELLEN Thierry RD-BIZZ-SOP; Bohnert, Thomas Michael; Magerkurth, Carsten; Leidig, Torsten; Friesen, Andreas Cc : fiware-iot at lists.fi-ware.eu; Sperner, Klaus; Meyer, Sonja Objet : RE: [FusionForge Problems with] OMA NGSI API All, I have started to write up some user stories for the area where IoT and Apps&Services meet. This is also where our core interest lies and where we will bring in some assets (from the IoT-A project). This is just a first draft, far from complete. But I wanted to provide this as an input for the meetings in Torino. Regards, -Stephan Stephan Haller Development Architect - Internet of Things, SAP Research SAP (Schweiz) AG, Kreuzplatz, Kreuzplatz 20, CH-8008 Z?rich, Switzerland T +41 58 871 78 45, F +41 58 871 78 12 mailto:stephan.haller at sap.com Please consider the impact on the environment before printing this e-mail. ******************************************************************************** IMPORTANT.Les informations contenues dans ce message electronique y compris les fichiers attaches sont strictement confidentielles et peuvent etre protegees par la loi. Ce message electronique est destine exclusivement au(x) destinataire(s) mentionne(s) ci-dessus. Si vous avez recu ce message par erreur ou s il ne vous est pas destine, veuillez immediatement le signaler a l expediteur et effacer ce message et tous les fichiers eventuellement attaches. Toute lecture, exploitation ou transmission des informations contenues dans ce message est interdite. Tout message electronique est susceptible d alteration. A ce titre, le Groupe France Telecom decline toute responsabilite notamment s il a ete altere, deforme ou falsifie. De meme, il appartient au destinataire de s assurer de l absence de tout virus. IMPORTANT.This e-mail message and any attachments are strictly confidential and may be protected by law. This message is intended only for the named recipient(s) above. If you have received this message in error, or are not the named recipient(s), please immediately notify the sender and delete this e-mail message. Any unauthorized view, usage or disclosure ofthis message is prohibited. Since e-mail messages may not be reliable, France Telecom Group shall not be liable for any message if modified, changed or falsified. Additionally the recipient should ensure they are actually virus free. ******************************************************************************** -------------- next part -------------- An HTML attachment was scrubbed... URL: From Martin.Bauer at neclab.eu Tue Sep 13 09:23:23 2011 From: Martin.Bauer at neclab.eu (Martin Bauer) Date: Tue, 13 Sep 2011 07:23:23 +0000 Subject: [Fiware-iot] [FusionForge Problems with] OMA NGSI API In-Reply-To: <23052_1315858707_4E6E6913_23052_397275_1_BAF83494CE653943A97B9F755016A066098203DF@ftrdmel1> References: <8152E2132B13FB488CFD1947E2DEF19C1CFA6B43@DAPHNIS.office.hd> <0D2446AEB6CAED48BB046223733964A54C3EA9A44E@DEWDFECCR01.wdf.sap.corp> <23052_1315858707_4E6E6913_23052_397275_1_BAF83494CE653943A97B9F755016A066098203DF@ftrdmel1> Message-ID: Hi Thierry, Stephan, all, The partners involved in both IoT-A and FI-WARE WP5 are SAP, NEC, University of Surrey and Telefonica I+D. We can start discussing with the people involved during the Torino meeting. Apart from the Application side, which is the SAP focus, there is also the Resolution and Discovery infrastructure from IoT-A WP4. I am the WP leader and TID (Ricardo), Surrey, and NEC are three of the four task leaders, so there is quite some overlap that could be utilized. I will also be in Poznan end of October. Best regards, Martin ------------------------------------------ Dr. Martin Bauer Senior Researcher NEC Europe Ltd. NEC Laboratories Europe Software & Services Research Division Kurf?rsten-Anlage 36 D-69115 Heidelberg Tel: +49/ (0)6221/4342-168 Fax: +49/ (0)6221/4342-155 E-Mail: Martin.Bauer at neclab.eu http://www.nw.neclab.eu From: fiware-iot-bounces at lists.fi-ware.eu [mailto:fiware-iot-bounces at lists.fi-ware.eu] On Behalf Of thierry.nagellen at orange-ftgroup.com Sent: Montag, 12. September 2011 22:18 To: stephan.haller at sap.com; thomas.michael.bohnert at sap.com; carsten.magerkurth at sap.com; torsten.leidig at sap.com; andreas.friesen at sap.com Cc: fiware-iot at lists.fi-ware.eu Subject: Re: [Fiware-iot] [FusionForge Problems with] OMA NGSI API HI Stefan Thanks a lot for your contribution. We will discuss all content during Torino meeting and try to find the best way for User stories description. Regarding IoT-A project, could you - with Ern? as your companies are partners of this project - share some expected deadlines and what kind of results could be used (if this information is public of course). Maybe we should also planned a meeting between WP IoT and IoT-A project to exchange about this issue, to improve some architecture elements and also to share the vision of UA projects because we should have more details at the end of September (first requirements, detailed presentation during Architecture Board 21-22/09). Do you think this join meeting could happen in Poznan (end of October, during the FI week?) BR Thierry De : Haller, Stephan [mailto:stephan.haller at sap.com] Envoy? : lundi 12 septembre 2011 09:51 ? : NAGELLEN Thierry RD-BIZZ-SOP; Bohnert, Thomas Michael; Magerkurth, Carsten; Leidig, Torsten; Friesen, Andreas Cc : fiware-iot at lists.fi-ware.eu; Sperner, Klaus; Meyer, Sonja Objet : RE: [FusionForge Problems with] OMA NGSI API All, I have started to write up some user stories for the area where IoT and Apps&Services meet. This is also where our core interest lies and where we will bring in some assets (from the IoT-A project). This is just a first draft, far from complete. But I wanted to provide this as an input for the meetings in Torino. Regards, -Stephan Stephan Haller Development Architect - Internet of Things, SAP Research SAP (Schweiz) AG, Kreuzplatz, Kreuzplatz 20, CH-8008 Z?rich, Switzerland T +41 58 871 78 45, F +41 58 871 78 12 mailto:stephan.haller at sap.com Please consider the impact on the environment before printing this e-mail. ******************************************************************************** IMPORTANT.Les informations contenues dans ce message electronique y compris les fichiers attaches sont strictement confidentielles et peuvent etre protegees par la loi. Ce message electronique est destine exclusivement au(x) destinataire(s) mentionne(s) ci-dessus. Si vous avez recu ce message par erreur ou s il ne vous est pas destine, veuillez immediatement le signaler a l expediteur et effacer ce message et tous les fichiers eventuellement attaches. Toute lecture, exploitation ou transmission des informations contenues dans ce message est interdite. Tout message electronique est susceptible d alteration. A ce titre, le Groupe France Telecom decline toute responsabilite notamment s il a ete altere, deforme ou falsifie. De meme, il appartient au destinataire de s assurer de l absence de tout virus. IMPORTANT.This e-mail message and any attachments are strictly confidential and may be protected by law. This message is intended only for the named recipient(s) above. If you have received this message in error, or are not the named recipient(s), please immediately notify the sender and delete this e-mail message. Any unauthorized view, usage or disclosure ofthis message is prohibited. Since e-mail messages may not be reliable, France Telecom Group shall not be liable for any message if modified, changed or falsified. Additionally the recipient should ensure they are actually virus free. ******************************************************************************** -------------- next part -------------- An HTML attachment was scrubbed... URL: From stephan.haller at sap.com Tue Sep 13 09:51:05 2011 From: stephan.haller at sap.com (Haller, Stephan) Date: Tue, 13 Sep 2011 09:51:05 +0200 Subject: [Fiware-iot] [FusionForge Problems with] OMA NGSI API In-Reply-To: <23052_1315858707_4E6E6913_23052_397275_1_BAF83494CE653943A97B9F755016A066098203DF@ftrdmel1> References: <8152E2132B13FB488CFD1947E2DEF19C1CFA6B43@DAPHNIS.office.hd> <0D2446AEB6CAED48BB046223733964A54C3EA9A44E@DEWDFECCR01.wdf.sap.corp> <23052_1315858707_4E6E6913_23052_397275_1_BAF83494CE653943A97B9F755016A066098203DF@ftrdmel1> Message-ID: <0D2446AEB6CAED48BB046223733964A54C3EDDD5A6@DEWDFECCR01.wdf.sap.corp> Thierry, Please find the information attached regarding what kind of results and what deadlines we intend to deliver from SAP's side (IoT-A WP2). It is not public information, but it can be shared within this group (and other members of FIWARE). Regards, -Stephan From: thierry.nagellen at orange-ftgroup.com [mailto:thierry.nagellen at orange-ftgroup.com] Sent: Montag, 12. September 2011 22:18 To: Haller, Stephan; Bohnert, Thomas Michael; Magerkurth, Carsten; Leidig, Torsten; Friesen, Andreas Cc: fiware-iot at lists.fi-ware.eu; Sperner, Klaus; Meyer, Sonja Subject: RE: [FusionForge Problems with] OMA NGSI API HI Stefan Thanks a lot for your contribution. We will discuss all content during Torino meeting and try to find the best way for User stories description. Regarding IoT-A project, could you - with Ern? as your companies are partners of this project - share some expected deadlines and what kind of results could be used (if this information is public of course). Maybe we should also planned a meeting between WP IoT and IoT-A project to exchange about this issue, to improve some architecture elements and also to share the vision of UA projects because we should have more details at the end of September (first requirements, detailed presentation during Architecture Board 21-22/09). Do you think this join meeting could happen in Poznan (end of October, during the FI week?) BR Thierry De : Haller, Stephan [mailto:stephan.haller at sap.com] Envoy? : lundi 12 septembre 2011 09:51 ? : NAGELLEN Thierry RD-BIZZ-SOP; Bohnert, Thomas Michael; Magerkurth, Carsten; Leidig, Torsten; Friesen, Andreas Cc : fiware-iot at lists.fi-ware.eu; Sperner, Klaus; Meyer, Sonja Objet : RE: [FusionForge Problems with] OMA NGSI API All, I have started to write up some user stories for the area where IoT and Apps&Services meet. This is also where our core interest lies and where we will bring in some assets (from the IoT-A project). This is just a first draft, far from complete. But I wanted to provide this as an input for the meetings in Torino. Regards, -Stephan Stephan Haller Development Architect - Internet of Things, SAP Research SAP (Schweiz) AG, Kreuzplatz, Kreuzplatz 20, CH-8008 Z?rich, Switzerland T +41 58 871 78 45, F +41 58 871 78 12 mailto:stephan.haller at sap.com Please consider the impact on the environment before printing this e-mail. ******************************************************************************** IMPORTANT.Les informations contenues dans ce message electronique y compris les fichiers attaches sont strictement confidentielles et peuvent etre protegees par la loi. Ce message electronique est destine exclusivement au(x) destinataire(s) mentionne(s) ci-dessus. Si vous avez recu ce message par erreur ou s il ne vous est pas destine, veuillez immediatement le signaler a l expediteur et effacer ce message et tous les fichiers eventuellement attaches. Toute lecture, exploitation ou transmission des informations contenues dans ce message est interdite. Tout message electronique est susceptible d alteration. A ce titre, le Groupe France Telecom decline toute responsabilite notamment s il a ete altere, deforme ou falsifie. De meme, il appartient au destinataire de s assurer de l absence de tout virus. IMPORTANT.This e-mail message and any attachments are strictly confidential and may be protected by law. This message is intended only for the named recipient(s) above. If you have received this message in error, or are not the named recipient(s), please immediately notify the sender and delete this e-mail message. Any unauthorized view, usage or disclosure ofthis message is prohibited. Since e-mail messages may not be reliable, France Telecom Group shall not be liable for any message if modified, changed or falsified. Additionally the recipient should ensure they are actually virus free. ******************************************************************************** -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: SAP_Assets_IoT_v2.pptx Type: application/vnd.openxmlformats-officedocument.presentationml.presentation Size: 3684226 bytes Desc: SAP_Assets_IoT_v2.pptx URL: From lorant.farkas at nsn.com Tue Sep 13 16:55:04 2011 From: lorant.farkas at nsn.com (Farkas, Lorant (NSN - HU/Budapest)) Date: Tue, 13 Sep 2011 17:55:04 +0300 Subject: [Fiware-iot] Cross-WP meetings Message-ID: <93D28BDF64839C468B848D14227151A202498020@FIESEXC014.nsn-intra.net> Dear All, An update on the proposed cross-WP meetings during the GA where IoT will participate: -We will have a cross WP meeting with ASE and DCM Wednesday on the 14th between 9-12 AM -We will have a cross WP meeting with Security, Privacy and Trust the end of afternoon of Wednesday the 14th -We will have a cross WP meeting with I2ND between 9 AM - 10:30 AM Thursday on the 15th Br, Lorant -------------- next part -------------- An HTML attachment was scrubbed... URL: From P.Barnaghi at surrey.ac.uk Tue Sep 13 22:36:36 2011 From: P.Barnaghi at surrey.ac.uk (P.Barnaghi at surrey.ac.uk) Date: Tue, 13 Sep 2011 21:36:36 +0100 Subject: [Fiware-iot] [FusionForge Problems with] OMA NGSI API In-Reply-To: <0D2446AEB6CAED48BB046223733964A54C3EDDD5A6@DEWDFECCR01.wdf.sap.corp> References: <8152E2132B13FB488CFD1947E2DEF19C1CFA6B43@DAPHNIS.office.hd> <0D2446AEB6CAED48BB046223733964A54C3EA9A44E@DEWDFECCR01.wdf.sap.corp> <23052_1315858707_4E6E6913_23052_397275_1_BAF83494CE653943A97B9F755016A066098203DF@ftrdmel1> <0D2446AEB6CAED48BB046223733964A54C3EDDD5A6@DEWDFECCR01.wdf.sap.corp> Message-ID: Hi all, Following Stephan's practice, I have created a few slides regarding University of Surrey's results that potentially can be delivered. As you can see there is an overlap between other IoT-A and Sensei partners and in particular with the results from SAP and NEC. Regards, Payam From: fiware-iot-bounces at lists.fi-ware.eu [mailto:fiware-iot-bounces at lists.fi-ware.eu] On Behalf Of Haller, Stephan Sent: 13 September 2011 8:51 AM To: thierry.nagellen at orange-ftgroup.com; Bohnert, Thomas Michael; Magerkurth, Carsten; Leidig, Torsten; Friesen, Andreas Cc: fiware-iot at lists.fi-ware.eu Subject: Re: [Fiware-iot] [FusionForge Problems with] OMA NGSI API Thierry, Please find the information attached regarding what kind of results and what deadlines we intend to deliver from SAP's side (IoT-A WP2). It is not public information, but it can be shared within this group (and other members of FIWARE). Regards, -Stephan From: thierry.nagellen at orange-ftgroup.com [mailto:thierry.nagellen at orange-ftgroup.com] Sent: Montag, 12. September 2011 22:18 To: Haller, Stephan; Bohnert, Thomas Michael; Magerkurth, Carsten; Leidig, Torsten; Friesen, Andreas Cc: fiware-iot at lists.fi-ware.eu; Sperner, Klaus; Meyer, Sonja Subject: RE: [FusionForge Problems with] OMA NGSI API HI Stefan Thanks a lot for your contribution. We will discuss all content during Torino meeting and try to find the best way for User stories description. Regarding IoT-A project, could you - with Ern? as your companies are partners of this project - share some expected deadlines and what kind of results could be used (if this information is public of course). Maybe we should also planned a meeting between WP IoT and IoT-A project to exchange about this issue, to improve some architecture elements and also to share the vision of UA projects because we should have more details at the end of September (first requirements, detailed presentation during Architecture Board 21-22/09). Do you think this join meeting could happen in Poznan (end of October, during the FI week?) BR Thierry De : Haller, Stephan [mailto:stephan.haller at sap.com] Envoy? : lundi 12 septembre 2011 09:51 ? : NAGELLEN Thierry RD-BIZZ-SOP; Bohnert, Thomas Michael; Magerkurth, Carsten; Leidig, Torsten; Friesen, Andreas Cc : fiware-iot at lists.fi-ware.eu; Sperner, Klaus; Meyer, Sonja Objet : RE: [FusionForge Problems with] OMA NGSI API All, I have started to write up some user stories for the area where IoT and Apps&Services meet. This is also where our core interest lies and where we will bring in some assets (from the IoT-A project). This is just a first draft, far from complete. But I wanted to provide this as an input for the meetings in Torino. Regards, -Stephan Stephan Haller Development Architect - Internet of Things, SAP Research SAP (Schweiz) AG, Kreuzplatz, Kreuzplatz 20, CH-8008 Z?rich, Switzerland T +41 58 871 78 45, F +41 58 871 78 12 mailto:stephan.haller at sap.com Please consider the impact on the environment before printing this e-mail. ******************************************************************************** IMPORTANT.Les informations contenues dans ce message electronique y compris les fichiers attaches sont strictement confidentielles et peuvent etre protegees par la loi. Ce message electronique est destine exclusivement au(x) destinataire(s) mentionne(s) ci-dessus. Si vous avez recu ce message par erreur ou s il ne vous est pas destine, veuillez immediatement le signaler a l expediteur et effacer ce message et tous les fichiers eventuellement attaches. Toute lecture, exploitation ou transmission des informations contenues dans ce message est interdite. Tout message electronique est susceptible d alteration. A ce titre, le Groupe France Telecom decline toute responsabilite notamment s il a ete altere, deforme ou falsifie. De meme, il appartient au destinataire de s assurer de l absence de tout virus. IMPORTANT.This e-mail message and any attachments are strictly confidential and may be protected by law. This message is intended only for the named recipient(s) above. If you have received this message in error, or are not the named recipient(s), please immediately notify the sender and delete this e-mail message. Any unauthorized view, usage or disclosure ofthis message is prohibited. Since e-mail messages may not be reliable, France Telecom Group shall not be liable for any message if modified, changed or falsified. Additionally the recipient should ensure they are actually virus free. ******************************************************************************** ________________________________ No virus found in this message. Checked by AVG - www.avg.com Version: 10.0.1392 / Virus Database: 1520/3892 - Release Date: 09/12/11 -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: FI-Ware_UNiS_Assets.ppt Type: application/vnd.ms-powerpoint Size: 1545216 bytes Desc: FI-Ware_UNiS_Assets.ppt URL: From Martin.Bauer at neclab.eu Wed Sep 14 23:01:35 2011 From: Martin.Bauer at neclab.eu (Martin Bauer) Date: Wed, 14 Sep 2011 21:01:35 +0000 Subject: [Fiware-iot] NEC's IoT Assets Message-ID: Hi IoT people in FI-Ware, After SAP and Surrey, we also want to give a slide-based overview of our assets and some information how these are related to the ones from the other SENSEI or IoT-A partners that are also in FI-Ware. Best regards, Martin ------------------------------------------ Dr. Martin Bauer Senior Researcher NEC Europe Ltd. NEC Laboratories Europe Software & Services Research Division Kurf?rsten-Anlage 36 D-69115 Heidelberg Tel: +49/ (0)6221/4342-168 Fax: +49/ (0)6221/4342-155 E-Mail: Martin.Bauer at neclab.eu http://www.nw.neclab.eu From: fiware-iot-bounces at lists.fi-ware.eu [mailto:fiware-iot-bounces at lists.fi-ware.eu] On Behalf Of P.Barnaghi at surrey.ac.uk Sent: Dienstag, 13. September 2011 22:37 To: stephan.haller at sap.com; thierry.nagellen at orange-ftgroup.com; thomas.michael.bohnert at sap.com; carsten.magerkurth at sap.com; torsten.leidig at sap.com; andreas.friesen at sap.com Cc: fiware-iot at lists.fi-ware.eu Subject: Re: [Fiware-iot] [FusionForge Problems with] OMA NGSI API Hi all, Following Stephan's practice, I have created a few slides regarding University of Surrey's results that potentially can be delivered. As you can see there is an overlap between other IoT-A and Sensei partners and in particular with the results from SAP and NEC. Regards, Payam From: fiware-iot-bounces at lists.fi-ware.eu [mailto:fiware-iot-bounces at lists.fi-ware.eu] On Behalf Of Haller, Stephan Sent: 13 September 2011 8:51 AM To: thierry.nagellen at orange-ftgroup.com; Bohnert, Thomas Michael; Magerkurth, Carsten; Leidig, Torsten; Friesen, Andreas Cc: fiware-iot at lists.fi-ware.eu Subject: Re: [Fiware-iot] [FusionForge Problems with] OMA NGSI API Thierry, Please find the information attached regarding what kind of results and what deadlines we intend to deliver from SAP's side (IoT-A WP2). It is not public information, but it can be shared within this group (and other members of FIWARE). Regards, -Stephan From: thierry.nagellen at orange-ftgroup.com [mailto:thierry.nagellen at orange-ftgroup.com] Sent: Montag, 12. September 2011 22:18 To: Haller, Stephan; Bohnert, Thomas Michael; Magerkurth, Carsten; Leidig, Torsten; Friesen, Andreas Cc: fiware-iot at lists.fi-ware.eu; Sperner, Klaus; Meyer, Sonja Subject: RE: [FusionForge Problems with] OMA NGSI API HI Stefan Thanks a lot for your contribution. We will discuss all content during Torino meeting and try to find the best way for User stories description. Regarding IoT-A project, could you - with Ern? as your companies are partners of this project - share some expected deadlines and what kind of results could be used (if this information is public of course). Maybe we should also planned a meeting between WP IoT and IoT-A project to exchange about this issue, to improve some architecture elements and also to share the vision of UA projects because we should have more details at the end of September (first requirements, detailed presentation during Architecture Board 21-22/09). Do you think this join meeting could happen in Poznan (end of October, during the FI week?) BR Thierry De : Haller, Stephan [mailto:stephan.haller at sap.com] Envoy? : lundi 12 septembre 2011 09:51 ? : NAGELLEN Thierry RD-BIZZ-SOP; Bohnert, Thomas Michael; Magerkurth, Carsten; Leidig, Torsten; Friesen, Andreas Cc : fiware-iot at lists.fi-ware.eu; Sperner, Klaus; Meyer, Sonja Objet : RE: [FusionForge Problems with] OMA NGSI API All, I have started to write up some user stories for the area where IoT and Apps&Services meet. This is also where our core interest lies and where we will bring in some assets (from the IoT-A project). This is just a first draft, far from complete. But I wanted to provide this as an input for the meetings in Torino. Regards, -Stephan Stephan Haller Development Architect - Internet of Things, SAP Research SAP (Schweiz) AG, Kreuzplatz, Kreuzplatz 20, CH-8008 Z?rich, Switzerland T +41 58 871 78 45, F +41 58 871 78 12 mailto:stephan.haller at sap.com Please consider the impact on the environment before printing this e-mail. ******************************************************************************** IMPORTANT.Les informations contenues dans ce message electronique y compris les fichiers attaches sont strictement confidentielles et peuvent etre protegees par la loi. Ce message electronique est destine exclusivement au(x) destinataire(s) mentionne(s) ci-dessus. Si vous avez recu ce message par erreur ou s il ne vous est pas destine, veuillez immediatement le signaler a l expediteur et effacer ce message et tous les fichiers eventuellement attaches. Toute lecture, exploitation ou transmission des informations contenues dans ce message est interdite. Tout message electronique est susceptible d alteration. A ce titre, le Groupe France Telecom decline toute responsabilite notamment s il a ete altere, deforme ou falsifie. De meme, il appartient au destinataire de s assurer de l absence de tout virus. IMPORTANT.This e-mail message and any attachments are strictly confidential and may be protected by law. This message is intended only for the named recipient(s) above. If you have received this message in error, or are not the named recipient(s), please immediately notify the sender and delete this e-mail message. Any unauthorized view, usage or disclosure ofthis message is prohibited. Since e-mail messages may not be reliable, France Telecom Group shall not be liable for any message if modified, changed or falsified. Additionally the recipient should ensure they are actually virus free. ******************************************************************************** ________________________________ No virus found in this message. Checked by AVG - www.avg.com Version: 10.0.1392 / Virus Database: 1520/3892 - Release Date: 09/12/11 -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: NECs IoT Assets.pdf Type: application/pdf Size: 687428 bytes Desc: NECs IoT Assets.pdf URL: From rheras at tid.es Thu Sep 15 07:38:18 2011 From: rheras at tid.es (Ricardo de las Heras) Date: Thu, 15 Sep 2011 07:38:18 +0200 Subject: [Fiware-iot] NEC's IoT Assets In-Reply-To: References: Message-ID: <4E718F4A.9070908@tid.es> An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: TID-WP5-IDAS-IoT-A.pdf Type: application/pdf Size: 755875 bytes Desc: not available URL: From P.Barnaghi at surrey.ac.uk Thu Sep 15 17:11:55 2011 From: P.Barnaghi at surrey.ac.uk (P.Barnaghi at surrey.ac.uk) Date: Thu, 15 Sep 2011 16:11:55 +0100 Subject: [Fiware-iot] NEC's IoT Assets In-Reply-To: References: Message-ID: Hi all, Attachment is an updated version of our asset slides. Best regards. Payam From: fiware-iot-bounces at lists.fi-ware.eu [mailto:fiware-iot-bounces at lists.fi-ware.eu] On Behalf Of Martin Bauer Sent: 14 September 2011 10:02 PM To: fiware-iot at lists.fi-ware.eu Cc: andreas.friesen at sap.com Subject: [Fiware-iot] NEC's IoT Assets Hi IoT people in FI-Ware, After SAP and Surrey, we also want to give a slide-based overview of our assets and some information how these are related to the ones from the other SENSEI or IoT-A partners that are also in FI-Ware. Best regards, Martin ------------------------------------------ Dr. Martin Bauer Senior Researcher NEC Europe Ltd. NEC Laboratories Europe Software & Services Research Division Kurf?rsten-Anlage 36 D-69115 Heidelberg Tel: +49/ (0)6221/4342-168 Fax: +49/ (0)6221/4342-155 E-Mail: Martin.Bauer at neclab.eu http://www.nw.neclab.eu From: fiware-iot-bounces at lists.fi-ware.eu [mailto:fiware-iot-bounces at lists.fi-ware.eu] On Behalf Of P.Barnaghi at surrey.ac.uk Sent: Dienstag, 13. September 2011 22:37 To: stephan.haller at sap.com; thierry.nagellen at orange-ftgroup.com; thomas.michael.bohnert at sap.com; carsten.magerkurth at sap.com; torsten.leidig at sap.com; andreas.friesen at sap.com Cc: fiware-iot at lists.fi-ware.eu Subject: Re: [Fiware-iot] [FusionForge Problems with] OMA NGSI API Hi all, Following Stephan's practice, I have created a few slides regarding University of Surrey's results that potentially can be delivered. As you can see there is an overlap between other IoT-A and Sensei partners and in particular with the results from SAP and NEC. Regards, Payam From: fiware-iot-bounces at lists.fi-ware.eu [mailto:fiware-iot-bounces at lists.fi-ware.eu] On Behalf Of Haller, Stephan Sent: 13 September 2011 8:51 AM To: thierry.nagellen at orange-ftgroup.com; Bohnert, Thomas Michael; Magerkurth, Carsten; Leidig, Torsten; Friesen, Andreas Cc: fiware-iot at lists.fi-ware.eu Subject: Re: [Fiware-iot] [FusionForge Problems with] OMA NGSI API Thierry, Please find the information attached regarding what kind of results and what deadlines we intend to deliver from SAP's side (IoT-A WP2). It is not public information, but it can be shared within this group (and other members of FIWARE). Regards, -Stephan From: thierry.nagellen at orange-ftgroup.com [mailto:thierry.nagellen at orange-ftgroup.com] Sent: Montag, 12. September 2011 22:18 To: Haller, Stephan; Bohnert, Thomas Michael; Magerkurth, Carsten; Leidig, Torsten; Friesen, Andreas Cc: fiware-iot at lists.fi-ware.eu; Sperner, Klaus; Meyer, Sonja Subject: RE: [FusionForge Problems with] OMA NGSI API HI Stefan Thanks a lot for your contribution. We will discuss all content during Torino meeting and try to find the best way for User stories description. Regarding IoT-A project, could you - with Ern? as your companies are partners of this project - share some expected deadlines and what kind of results could be used (if this information is public of course). Maybe we should also planned a meeting between WP IoT and IoT-A project to exchange about this issue, to improve some architecture elements and also to share the vision of UA projects because we should have more details at the end of September (first requirements, detailed presentation during Architecture Board 21-22/09). Do you think this join meeting could happen in Poznan (end of October, during the FI week?) BR Thierry De : Haller, Stephan [mailto:stephan.haller at sap.com] Envoy? : lundi 12 septembre 2011 09:51 ? : NAGELLEN Thierry RD-BIZZ-SOP; Bohnert, Thomas Michael; Magerkurth, Carsten; Leidig, Torsten; Friesen, Andreas Cc : fiware-iot at lists.fi-ware.eu; Sperner, Klaus; Meyer, Sonja Objet : RE: [FusionForge Problems with] OMA NGSI API All, I have started to write up some user stories for the area where IoT and Apps&Services meet. This is also where our core interest lies and where we will bring in some assets (from the IoT-A project). This is just a first draft, far from complete. But I wanted to provide this as an input for the meetings in Torino. Regards, -Stephan Stephan Haller Development Architect - Internet of Things, SAP Research SAP (Schweiz) AG, Kreuzplatz, Kreuzplatz 20, CH-8008 Z?rich, Switzerland T +41 58 871 78 45, F +41 58 871 78 12 mailto:stephan.haller at sap.com Please consider the impact on the environment before printing this e-mail. ******************************************************************************** IMPORTANT.Les informations contenues dans ce message electronique y compris les fichiers attaches sont strictement confidentielles et peuvent etre protegees par la loi. Ce message electronique est destine exclusivement au(x) destinataire(s) mentionne(s) ci-dessus. Si vous avez recu ce message par erreur ou s il ne vous est pas destine, veuillez immediatement le signaler a l expediteur et effacer ce message et tous les fichiers eventuellement attaches. Toute lecture, exploitation ou transmission des informations contenues dans ce message est interdite. Tout message electronique est susceptible d alteration. A ce titre, le Groupe France Telecom decline toute responsabilite notamment s il a ete altere, deforme ou falsifie. De meme, il appartient au destinataire de s assurer de l absence de tout virus. IMPORTANT.This e-mail message and any attachments are strictly confidential and may be protected by law. This message is intended only for the named recipient(s) above. If you have received this message in error, or are not the named recipient(s), please immediately notify the sender and delete this e-mail message. Any unauthorized view, usage or disclosure ofthis message is prohibited. Since e-mail messages may not be reliable, France Telecom Group shall not be liable for any message if modified, changed or falsified. Additionally the recipient should ensure they are actually virus free. ******************************************************************************** ________________________________ No virus found in this message. Checked by AVG - www.avg.com Version: 10.0.1392 / Virus Database: 1520/3892 - Release Date: 09/12/11 ________________________________ No virus found in this message. Checked by AVG - www.avg.com Version: 10.0.1392 / Virus Database: 1520/3896 - Release Date: 09/14/11 -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: FI-Ware_UNiS_Assets.ppt Type: application/vnd.ms-powerpoint Size: 2073600 bytes Desc: FI-Ware_UNiS_Assets.ppt URL: From lorant.farkas at nsn.com Mon Sep 19 07:44:20 2011 From: lorant.farkas at nsn.com (Farkas, Lorant (NSN - HU/Budapest)) Date: Mon, 19 Sep 2011 08:44:20 +0300 Subject: [Fiware-iot] IoT next steps after the GA Message-ID: <93D28BDF64839C468B848D14227151A2024D7823@FIESEXC014.nsn-intra.net> Dear All, Please find attached my notes from the "IoT plenary" session, with action items/deadlines in it. Please start acting accordingly. In case of unclarities don't hesitate to contact me. <> Before uploading anything to forge please wait for clarifications about the issues we faced on Thursday. I will send an e-mail about this later on today. Thanks & Br, Lorant -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: IoT_WP_plenary.ppt Type: application/vnd.ms-powerpoint Size: 104448 bytes Desc: IoT_WP_plenary.ppt URL: From lorant.farkas at nsn.com Mon Sep 19 10:16:33 2011 From: lorant.farkas at nsn.com (Farkas, Lorant (NSN - HU/Budapest)) Date: Mon, 19 Sep 2011 11:16:33 +0300 Subject: [Fiware-iot] Mailing list + forge issues Message-ID: <93D28BDF64839C468B848D14227151A2024D7A14@FIESEXC014.nsn-intra.net> Dear All, I can report I solved both issues: -only those persons can subscribe who confirm via e-mail that the request came from their e-mail address and who is authorized by the list admin (Juanjo, Thierry, Thomas, myself). I thought the default setting was OK, but it was not, basically everyone could register without the admins even getting notified of it. I changed now the settings. I also checked that there are no unknown/suspicious e-mail addresses registered -one should post files to forge using "private", not "active", otherwise the whole world will see them. I now (painstakingly) converted every (potentially) sensitive contribution to private, but you should make sure whenever submitting something to forge not to forget to set this field So please continue using the mailing list and forge as previously, now they are safe. Br, Lorant > _____________________________________________ > From: Farkas, Lorant (NSN - HU/Budapest) > Sent: Monday, September 19, 2011 7:44 AM > To: 'fiware-iot at lists.fi-ware.eu' > Subject: IoT next steps after the GA > > Dear All, > > Please find attached my notes from the "IoT plenary" session, with > action items/deadlines in it. Please start acting accordingly. In case > of unclarities don't hesitate to contact me. > << File: IoT_WP_plenary.ppt >> > Before uploading anything to forge please wait for clarifications > about the issues we faced on Thursday. I will send an e-mail about > this later on today. > > > Thanks & Br, > > Lorant -------------- next part -------------- An HTML attachment was scrubbed... URL: From lorant.farkas at nsn.com Mon Sep 19 14:28:07 2011 From: lorant.farkas at nsn.com (Farkas, Lorant (NSN - HU/Budapest)) Date: Mon, 19 Sep 2011 15:28:07 +0300 Subject: [Fiware-iot] IoT weekly meeting Message-ID: <93D28BDF64839C468B848D14227151A2024D7D36@FIESEXC014.nsn-intra.net> When: 2011. szeptember 23. 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, Because of Thierry's OoO I would like to organize our next weekly IoT weekly meeting on Friday, 23/09, 10 AM. Proposed agenda items: 1. Progress on the action items from the GA (see the ppt that I sent around this morning) -I would expect here both status-related and technical discussions 2. Progress on the tools (Lorant, Thierry) -We would try to set up forge in the way showed by Thomas in the plenary, to be used in the subsequent for the backlog entry creation Thanks & Br, Lorant Topic: FI-WARE IoT Date: Friday, 23 September 2011 Time: 10:00, Europe Summer Time (Paris, GMT+02:00) Meeting Number: 702 911 496 Meeting Password: cool Host Key: 607899 (use this to reclaim host privileges) ------------------------------------------------------- To start the online meeting ------------------------------------------------------- 1. Go to https://nsn.webex.com/nsn/j.php?ED=187643537&UID=483150557&PW=NYTgwZjYzZWNl&RT=MTgjMjM%3D 2. Log in to your account. 3. Click "Start Now". 4. Follow the instructions that appear on your screen. ------------------------------------------------------- NSN Voice Conference information 58465 / 9369002 Making a conference call When joining NVC call, please always use the global access number 8071870 when possible or local number(s) listed in page: https://inside.nokiasiemensnetworks.com/accessnumbers 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". To add this meeting to your calendar program (for example Microsoft Outlook), click this link: https://nsn.webex.com/nsn/j.php?ED=187643537&UID=483150557&ICS=MS&LD=1&RD=18&ST=1&SHA2=9Juqqb0PAo4dB0BPsSu6xFCFw342Vnjxea-ku2VnCcc= 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: 9434 bytes Desc: not available URL: From sabrina.guerra at telecomitalia.it Mon Sep 19 17:05:14 2011 From: sabrina.guerra at telecomitalia.it (Guerra Sabrina) Date: Mon, 19 Sep 2011 17:05:14 +0200 Subject: [Fiware-iot] Telecom Italia's IoT Assets In-Reply-To: References: Message-ID: <36A93B31228D3B49B691AD31652BCAE9A56341FF32@GRFMBX702BA020.griffon.local> Hi all, We attach an updated version of Telecom Italia asset slides. Best regards. Sabrina Guerra __________________________________ Telecom Italia S.p.a. Strategia e Innovazione, Research & Trends Telefono +39 011 228 8359 Cellulare +39 331 600 1349 Questo messaggio e i suoi allegati sono indirizzati esclusivamente alle persone indicate. La diffusione, copia o qualsiasi altra azione derivante dalla conoscenza di queste informazioni sono rigorosamente vietate. Qualora abbiate ricevuto questo documento per errore siete cortesemente pregati di darne immediata comunicazione al mittente e di provvedere alla sua distruzione, Grazie. This e-mail and any attachments is confidential and may contain privileged information intended for the addressee(s) only. Dissemination, copying, printing or use by anybody else is unauthorised. If you are not the intended recipient, please delete this message and any attachments and advise the sender by return e-mail, Thanks. [cid:00000000000000000000000000000001 at TI.Disclaimer]Rispetta l'ambiente. Non stampare questa mail se non ? necessario. -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: TI_WP5_IoT_Assets_V1.ppt Type: application/vnd.ms-powerpoint Size: 514048 bytes Desc: TI_WP5_IoT_Assets_V1.ppt URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: logo Ambiente_foglia.jpg Type: image/jpeg Size: 677 bytes Desc: logo Ambiente_foglia.jpg URL: From Ernoe.Kovacs at neclab.eu Mon Sep 19 20:02:41 2011 From: Ernoe.Kovacs at neclab.eu (Ernoe Kovacs) Date: Mon, 19 Sep 2011 18:02:41 +0000 Subject: [Fiware-iot] IoT weekly meeting In-Reply-To: <93D28BDF64839C468B848D14227151A2024D7D36@FIESEXC014.nsn-intra.net> References: <93D28BDF64839C468B848D14227151A2024D7D36@FIESEXC014.nsn-intra.net> Message-ID: <8152E2132B13FB488CFD1947E2DEF19C1CFB2D1E@DAPHNIS.office.hd> Hi all, early warning. We have a regular meeting on Friday 10:30 8-( Plus this Friday visitors. So iwill not attend. -Ern? 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: Montag, 19. September 2011 14:28 To: fiware-iot at lists.fi-ware.eu Subject: [Fiware-iot] IoT weekly meeting When: 2011. szeptember 23. 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, Because of Thierry's OoO I would like to organize our next weekly IoT weekly meeting on Friday, 23/09, 10 AM. Proposed agenda items: 1. Progress on the action items from the GA (see the ppt that I sent around this morning) -I would expect here both status-related and technical discussions 2. Progress on the tools (Lorant, Thierry) -We would try to set up forge in the way showed by Thomas in the plenary, to be used in the subsequent for the backlog entry creation Thanks & Br, Lorant Topic: FI-WARE IoT Date: Friday, 23 September 2011 Time: 10:00, Europe Summer Time (Paris, GMT+02:00) Meeting Number: 702 911 496 Meeting Password: cool Host Key: 607899 (use this to reclaim host privileges) ------------------------------------------------------- To start the online meeting ------------------------------------------------------- 1. Go to https://nsn.webex.com/nsn/j.php?ED=187643537&UID=483150557&PW=NYTgwZjYzZWNl&RT=MTgjMjM%3D 2. Log in to your account. 3. Click "Start Now". 4. Follow the instructions that appear on your screen. ------------------------------------------------------- NSN Voice Conference information 58465 / 9369002 Making a conference call When joining NVC call, please always use the global access number 8071870 when possible or local number(s) listed in page: https://inside.nokiasiemensnetworks.com/accessnumbers 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". To add this meeting to your calendar program (for example Microsoft Outlook), click this link: https://nsn.webex.com/nsn/j.php?ED=187643537&UID=483150557&ICS=MS&LD=1&RD=18&ST=1&SHA2=9Juqqb0PAo4dB0BPsSu6xFCFw342Vnjxea-ku2VnCcc= 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 Ernoe.Kovacs at neclab.eu Mon Sep 19 20:46:39 2011 From: Ernoe.Kovacs at neclab.eu (Ernoe Kovacs) Date: Mon, 19 Sep 2011 18:46:39 +0000 Subject: [Fiware-iot] IoT next steps after the GA In-Reply-To: <93D28BDF64839C468B848D14227151A2024D7823@FIESEXC014.nsn-intra.net> References: <93D28BDF64839C468B848D14227151A2024D7823@FIESEXC014.nsn-intra.net> Message-ID: <8152E2132B13FB488CFD1947E2DEF19C1CFB2E18@DAPHNIS.office.hd> Hi all, I had the action item to upload the Epics and User Stories which we discussed in the F2F meeting. Please find it here... https://forge.fi-ware.eu/docman/view.php/11/393/FI+IoT+Epics%26User+Stories.docx Note 1: Right Place ? - Ern? 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: Montag, 19. September 2011 07:44 To: fiware-iot at lists.fi-ware.eu Subject: [Fiware-iot] IoT next steps after the GA Dear All, Please find attached my notes from the "IoT plenary" session, with action items/deadlines in it. Please start acting accordingly. In case of unclarities don't hesitate to contact me. <> Before uploading anything to forge please wait for clarifications about the issues we faced on Thursday. I will send an e-mail about this later on today. Thanks & Br, Lorant -------------- next part -------------- An HTML attachment was scrubbed... URL: From rheras at tid.es Mon Sep 19 22:33:48 2011 From: rheras at tid.es (Ricardo de las Heras) Date: Mon, 19 Sep 2011 22:33:48 +0200 Subject: [Fiware-iot] IoT weekly meeting In-Reply-To: <8152E2132B13FB488CFD1947E2DEF19C1CFB2D1E@DAPHNIS.office.hd> References: <93D28BDF64839C468B848D14227151A2024D7D36@FIESEXC014.nsn-intra.net> <8152E2132B13FB488CFD1947E2DEF19C1CFB2D1E@DAPHNIS.office.hd> Message-ID: <4E77A72C.3020303@tid.es> An HTML attachment was scrubbed... URL: From lorant.farkas at nsn.com Tue Sep 20 08:41:39 2011 From: lorant.farkas at nsn.com (Farkas, Lorant (NSN - HU/Budapest)) Date: Tue, 20 Sep 2011 09:41:39 +0300 Subject: [Fiware-iot] Canceled: IoT weekly meeting Message-ID: <93D28BDF64839C468B848D14227151A20251ADC8@FIESEXC014.nsn-intra.net> When: 2011. szeptember 23. 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, My colleague will send soon a new invitation for the usual time on Wednesday, as this date/time was not good for several colleagues. Br, Lorant Dear All, Because of Thierry's OoO I would like to organize our next weekly IoT weekly meeting on Friday, 23/09, 10 AM. Proposed agenda items: 1. Progress on the action items from the GA (see the ppt that I sent around this morning) -I would expect here both status-related and technical discussions 2. Progress on the tools (Lorant, Thierry) -We would try to set up forge in the way showed by Thomas in the plenary, to be used in the subsequent for the backlog entry creation Thanks & Br, Lorant Topic: FI-WARE IoT Date: Friday, 23 September 2011 Time: 10:00, Europe Summer Time (Paris, GMT+02:00) Meeting Number: 702 911 496 Meeting Password: cool Host Key: 607899 (use this to reclaim host privileges) ------------------------------------------------------- To start the online meeting ------------------------------------------------------- 1. Go to https://nsn.webex.com/nsn/j.php?ED=187643537&UID=483150557&PW=NYTgwZjYzZWNl&RT=MTgjMjM%3D 2. Log in to your account. 3. Click "Start Now". 4. Follow the instructions that appear on your screen. ------------------------------------------------------- NSN Voice Conference information 58465 / 9369002 Making a conference call When joining NVC call, please always use the global access number 8071870 when possible or local number(s) listed in page: https://inside.nokiasiemensnetworks.com/accessnumbers 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". To add this meeting to your calendar program (for example Microsoft Outlook), click this link: https://nsn.webex.com/nsn/j.php?ED=187643537&UID=483150557&ICS=MS&LD=1&RD=18&ST=1&SHA2=9Juqqb0PAo4dB0BPsSu6xFCFw342Vnjxea-ku2VnCcc= 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: 9782 bytes Desc: not available URL: From messenger at webex.com Tue Sep 20 08:57:31 2011 From: messenger at webex.com (=?UTF-8?B?QmlzenRyYXlE77+9bmVz?=) Date: Tue, 20 Sep 2011 06:57:31 +0000 (GMT) Subject: [Fiware-iot] Meeting invitation: IoT weekly meeting Message-ID: <227515862.1316501851325.JavaMail.nobody@jln1wl013.webex.com> Hello , BisztrayD?nes invites you to attend this online meeting. Topic: IoT weekly meeting Date: Wednesday, September 21, 2011 Time: 10:00 am, Northern Europe Summer Time (Helsinki, GMT+03:00) Meeting Number: 701 499 639 Meeting Password: cool ------------------------------------------------------- To join the online meeting ------------------------------------------------------- 1. Go to https://nsn.webex.com/nsn/j.php?ED=187720462&UID=1267571947&PW=NOGMxYmJlY2U1&RT=MiMzMA%3D%3D 2. Enter your name and email address. 3. Enter the meeting password: cool 4. Click "Join Now". To view in other time zones or languages, please click the link: https://nsn.webex.com/nsn/j.php?ED=187720462&UID=1267571947&PW=NOGMxYmJlY2U1&ORT=MiMzMA%3D%3D ------------------------------------------------------- NSN Voice Conference information 58465 / 9369002 Making a conference call When joining NVC call, please always use the global access number 8071870 when possible or local number(s) listed in page: https://inside.nokiasiemensnetworks.com/accessnumbers 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: denes.bisztray at nsn.com To add this meeting to your calendar program (for example Microsoft Outlook), click this link: https://nsn.webex.com/nsn/j.php?ED=187720462&UID=1267571947&ICS=MI&LD=1&RD=2&ST=1&SHA2=VlRGJ8Gmfs1QBEj5Z/qwMu/fgzh2WqjcxOCQdPUfKDw=&RT=MiMzMA%3D%3D . -------------- next part -------------- An HTML attachment was scrubbed... URL: From denes.bisztray at nsn.com Tue Sep 20 09:19:56 2011 From: denes.bisztray at nsn.com (Bisztray, Denes (NSN - HU/Budapest)) Date: Tue, 20 Sep 2011 09:19:56 +0200 Subject: [Fiware-iot] IoT weekly meeting update Message-ID: <3F4C11BC54A36642BFB5875D599F47BD04D4F498@DEMUEXC013.nsn-intra.net> When: 2011. szeptember 21. 10:00-11:00 (UTC+01:00) Belgrade, Bratislava, Budapest, Ljubljana, Prague. Where: Telco/Webex Note: The GMT offset above does not reflect daylight saving time adjustments. *~*~*~*~*~*~*~*~*~* Dear All, Because several participants are unavailable, I would like to organize our next weekly IoT weekly meeting on Wednesday, 21/09, 10 AM. Proposed agenda items: 1. Progress on the action items from the GA (see the ppt that I sent around this morning) * I would expect here both status-related and technical discussions 2. Progress on the tools (Lorant, Thierry) * We would try to set up forge in the way showed by Thomas in the plenary, to be used in the subsequent for the backlog entry creation Best regards, D?nes Topic: IoT weekly meeting Date: Wednesday, September 21, 2011 Time: 10:00 am, Europe Summer Time (Paris, GMT+02:00) Meeting Number: 701 499 639 Meeting Password: cool ------------------------------------------------------- To join the online meeting ------------------------------------------------------- 1. Go to https://nsn.webex.com/nsn/j.php?ED=187720462&UID=0&PW=NOGMxYmJlY2U1&RT=MiMyMw%3D%3D 2. Enter your name and email address. 3. Enter the meeting password: cool 4. Click "Join Now". To view in other time zones or languages, please click the link: https://nsn.webex.com/nsn/j.php?ED=187720462&UID=0&PW=NOGMxYmJlY2U1&ORT=MiMyMw%3D%3D ------------------------------------------------------- NSN Voice Conference (NVC) information 58465 / 9369002 Making a conference call When joining NVC call, please always use the global access number 8071870 when possible or local number(s) listed in page: https://inside.nokiasiemensnetworks.com/accessnumbers 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: denes.bisztray 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: 9477 bytes Desc: not available URL: From P.Barnaghi at surrey.ac.uk Tue Sep 20 13:45:52 2011 From: P.Barnaghi at surrey.ac.uk (P.Barnaghi at surrey.ac.uk) Date: Tue, 20 Sep 2011 12:45:52 +0100 Subject: [Fiware-iot] Declined: IoT weekly meeting update Message-ID: sorry; I am traveling and won't be able to join the call. Best regards, Payam -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: text/calendar Size: 1320 bytes Desc: not available URL: From Ernoe.Kovacs at neclab.eu Tue Sep 20 15:02:02 2011 From: Ernoe.Kovacs at neclab.eu (Ernoe Kovacs) Date: Tue, 20 Sep 2011 13:02:02 +0000 Subject: [Fiware-iot] IoT weekly meeting update In-Reply-To: References: Message-ID: <8152E2132B13FB488CFD1947E2DEF19C1CFB3E2C@DAPHNIS.office.hd> Hi all, seems I am a trouble maker. Just got the feedback that I am planned to present to another visitor tomorrow. Chances are that I am going to miss the call. I try to work ahead and provide some input? - Ern? -----Original Appointment----- From: fiware-iot-bounces at lists.fi-ware.eu [mailto:fiware-iot-bounces at lists.fi-ware.eu] On Behalf Of P.Barnaghi at surrey.ac.uk Sent: Dienstag, 20. September 2011 13:46 To: denes.bisztray at nsn.com Cc: fiware-iot at lists.fi-ware.eu Subject: [Fiware-iot] Declined: IoT weekly meeting update When: Mittwoch, 21. September 2011 09:00-10:00 (UTC+01:00) Amsterdam, Berlin, Bern, Rome, Stockholm, Vienna. Where: Telco/Webex sorry; I am traveling and won't be able to join the call. Best regards, Payam << File: ATT00001.txt >> -------------- next part -------------- An HTML attachment was scrubbed... URL: From Martin.Bauer at neclab.eu Tue Sep 20 15:26:17 2011 From: Martin.Bauer at neclab.eu (Martin Bauer) Date: Tue, 20 Sep 2011 13:26:17 +0000 Subject: [Fiware-iot] IoT weekly meeting update In-Reply-To: <8152E2132B13FB488CFD1947E2DEF19C1CFB3E2C@DAPHNIS.office.hd> References: <8152E2132B13FB488CFD1947E2DEF19C1CFB3E2C@DAPHNIS.office.hd> Message-ID: Hi all, I am at a project meeting, so I will also not be able to participate. Best regards, Martin ------------------------------------------ Dr. Martin Bauer Senior Researcher NEC Europe Ltd. NEC Laboratories Europe Software & Services Research Division Kurf?rsten-Anlage 36 D-69115 Heidelberg Tel: +49/ (0)6221/4342-168 Fax: +49/ (0)6221/4342-155 E-Mail: Martin.Bauer at neclab.eu http://www.nw.neclab.eu From: fiware-iot-bounces at lists.fi-ware.eu [mailto:fiware-iot-bounces at lists.fi-ware.eu] On Behalf Of Ernoe Kovacs Sent: Dienstag, 20. September 2011 15:02 To: P.Barnaghi at surrey.ac.uk; denes.bisztray at nsn.com Cc: fiware-iot at lists.fi-ware.eu Subject: Re: [Fiware-iot] IoT weekly meeting update Hi all, seems I am a trouble maker. Just got the feedback that I am planned to present to another visitor tomorrow. Chances are that I am going to miss the call. I try to work ahead and provide some input? ? Ern? -----Original Appointment----- From: fiware-iot-bounces at lists.fi-ware.eu [mailto:fiware-iot-bounces at lists.fi-ware.eu] On Behalf Of P.Barnaghi at surrey.ac.uk Sent: Dienstag, 20. September 2011 13:46 To: denes.bisztray at nsn.com Cc: fiware-iot at lists.fi-ware.eu Subject: [Fiware-iot] Declined: IoT weekly meeting update When: Mittwoch, 21. September 2011 09:00-10:00 (UTC+01:00) Amsterdam, Berlin, Bern, Rome, Stockholm, Vienna. Where: Telco/Webex sorry; I am traveling and won't be able to join the call. Best regards, Payam << File: ATT00001.txt >> -------------- next part -------------- An HTML attachment was scrubbed... URL: From lorant.farkas at nsn.com Tue Sep 20 16:37:34 2011 From: lorant.farkas at nsn.com (Farkas, Lorant (NSN - HU/Budapest)) Date: Tue, 20 Sep 2011 17:37:34 +0300 Subject: [Fiware-iot] Tomorrow - cancelled? Message-ID: <93D28BDF64839C468B848D14227151A20251B35B@FIESEXC014.nsn-intra.net> Dear All, As Payam, Ern?, Martin, Thierry, Stephan are unavailable, I propose to skip this occasion. Any opinion? I will contact you one by one in e-mail for the next steps. If I receive no feedback by 18:00, I will cancel the meeting. Thanks & Br, Lorant -------------- next part -------------- An HTML attachment was scrubbed... URL: From denes.bisztray at nsn.com Wed Sep 21 08:19:35 2011 From: denes.bisztray at nsn.com (Bisztray, Denes (NSN - HU/Budapest)) Date: Wed, 21 Sep 2011 08:19:35 +0200 Subject: [Fiware-iot] Canceled: IoT weekly meeting update Message-ID: <3F4C11BC54A36642BFB5875D599F47BD04D4FBF6@DEMUEXC013.nsn-intra.net> When: 2011. szeptember 21. 10:00-11:00 (UTC+01:00) Belgrade, Bratislava, Budapest, Ljubljana, Prague. Where: Telco/Webex Note: The GMT offset above does not reflect daylight saving time adjustments. *~*~*~*~*~*~*~*~*~* Dear All, Because several participants are unavailable, I would like to organize our next weekly IoT weekly meeting on Wednesday, 21/09, 10 AM. Proposed agenda items: 1. Progress on the action items from the GA (see the ppt that I sent around this morning) * I would expect here both status-related and technical discussions 2. Progress on the tools (Lorant, Thierry) * We would try to set up forge in the way showed by Thomas in the plenary, to be used in the subsequent for the backlog entry creation Best regards, D?nes Topic: IoT weekly meeting Date: Wednesday, September 21, 2011 Time: 10:00 am, Europe Summer Time (Paris, GMT+02:00) Meeting Number: 701 499 639 Meeting Password: cool ------------------------------------------------------- To join the online meeting ------------------------------------------------------- 1. Go to https://nsn.webex.com/nsn/j.php?ED=187720462&UID=0&PW=NOGMxYmJlY2U1&RT=MiMyMw%3D%3D 2. Enter your name and email address. 3. Enter the meeting password: cool 4. Click "Join Now". To view in other time zones or languages, please click the link: https://nsn.webex.com/nsn/j.php?ED=187720462&UID=0&PW=NOGMxYmJlY2U1&ORT=MiMyMw%3D%3D ------------------------------------------------------- NSN Voice Conference (NVC) information 58465 / 9369002 Making a conference call When joining NVC call, please always use the global access number 8071870 when possible or local number(s) listed in page: https://inside.nokiasiemensnetworks.com/accessnumbers 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: denes.bisztray 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: 9714 bytes Desc: not available URL: From lorant.farkas at nsn.com Wed Sep 21 08:26:53 2011 From: lorant.farkas at nsn.com (Farkas, Lorant (NSN - HU/Budapest)) Date: Wed, 21 Sep 2011 09:26:53 +0300 Subject: [Fiware-iot] IoT weekly meeting Message-ID: <93D28BDF64839C468B848D14227151A20251B51B@FIESEXC014.nsn-intra.net> When: Occurs every szerda effective 2011. 09. 28. until 2014. 03. 26. from 10:00 to 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, 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: 9682 bytes Desc: not available URL: From lorant.farkas at nsn.com Wed Sep 21 16:43:59 2011 From: lorant.farkas at nsn.com (Farkas, Lorant (NSN - HU/Budapest)) Date: Wed, 21 Sep 2011 17:43:59 +0300 Subject: [Fiware-iot] Partner assets Message-ID: <93D28BDF64839C468B848D14227151A2025594A1@FIESEXC014.nsn-intra.net> Dear All, FYI, I uploaded to forge the company asset presentations I saw so far. With the private field set, of course. https://forge.fi-ware.eu/docman/?group_id=11# Thanks & Br, Lorant -------------- next part -------------- An HTML attachment was scrubbed... URL: From rheras at tid.es Wed Sep 21 17:20:47 2011 From: rheras at tid.es (Ricardo de las Heras) Date: Wed, 21 Sep 2011 17:20:47 +0200 Subject: [Fiware-iot] Partner assets In-Reply-To: <93D28BDF64839C468B848D14227151A2025594A1@FIESEXC014.nsn-intra.net> References: <93D28BDF64839C468B848D14227151A2025594A1@FIESEXC014.nsn-intra.net> Message-ID: <4E7A00CF.3080406@tid.es> An HTML attachment was scrubbed... URL: From lorant.farkas at nsn.com Thu Sep 22 07:56:09 2011 From: lorant.farkas at nsn.com (Farkas, Lorant (NSN - HU/Budapest)) Date: Thu, 22 Sep 2011 08:56:09 +0300 Subject: [Fiware-iot] Partner assets In-Reply-To: <4E7A00CF.3080406@tid.es> References: <93D28BDF64839C468B848D14227151A2025594A1@FIESEXC014.nsn-intra.net> <4E7A00CF.3080406@tid.es> Message-ID: <93D28BDF64839C468B848D14227151A2025595EC@FIESEXC014.nsn-intra.net> Dear Ricardo, I fully agree, the morning session was OK, the afternoon session was not OK. I also think if we had more time to discuss among ourselves, we could have done more. I will try to compile a minimum set of requirements for the asset description and allocate a task to each asset owner where I don't see these. The minimum would be: -licensing conditions (open source, closed source, partially open source etc) -which GE functionality is covered to which extent Alternatively I think it would be better for the task leaders could start this exercise of clearing the picture, starting from the Excel sheet as a first input, which gives at least a filter which assets can be dropped right from the beginning. Thanks & Br, Lorant ________________________________ From: ext Ricardo de las Heras [mailto:rheras at tid.es] Sent: Wednesday, September 21, 2011 5:21 PM To: Farkas, Lorant (NSN - HU/Budapest) Cc: fiware-iot at lists.fi-ware.eu Subject: Re: [Fiware-iot] Partner assets Dear Lorant, all, first thank you for compilling there all the information related with the assets. I think we still have a hard work to do in order to clarify the list of assets that finally will compose the functional blocks of every task, the steps done so far seems to be not decisive enough. First I miss to have a document including a clear description of every asset (some literature paragraphs in Word), describing its key capabilities that would be provided to Fiware IoT, and how those capabilities are mapped to every of the tasks and its main functionalities. IMHO some of the slides are very nice but don't describe clearly which functionalities described in the Word document 'High level Architecture description' are fulfilled or not. Really I'm a little bit dissappointed after the Turin meeting, because I though we were going to come back home with a clear map of the assets, having a clear picture by task and the most suitable candidate in every case, but this is not the real case I think, at least for me :( I don't know if this is the best way to proceed, but I'd propose you to take actions in this way in the short term, otherwise I think we have a puzzle that we will not able to solve. thanks, br, Ricardo. Farkas, Lorant (NSN - HU/Budapest) wrote: Dear All, FYI, I uploaded to forge the company asset presentations I saw so far. With the private field set, of course. https://forge.fi-ware.eu/docman/?group_id=11# Thanks & Br, Lorant -- ------------------------------------- Ricardo de las Heras M2M Research Project Manager E-mail: rheras at tid.es Phone1: (+34) 983 367625 Phone2 OCS: (+34) 91 31 29511 Phone3 Skype: (+34) 91 1878107 + Ext: 327 Telef?nica I+D ------------------------------------- ________________________________ Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra pol?tica de env?o y recepci?n de correo electr?nico en el enlace situado m?s abajo. This message is intended exclusively for its addressee. We only send and receive email on the basis of the terms set out at. http://www.tid.es/ES/PAGINAS/disclaimer.aspx -------------- next part -------------- An HTML attachment was scrubbed... URL: From lorant.farkas at nsn.com Thu Sep 22 08:02:21 2011 From: lorant.farkas at nsn.com (Farkas, Lorant (NSN - HU/Budapest)) Date: Thu, 22 Sep 2011 09:02:21 +0300 Subject: [Fiware-iot] FW: [Fiware-support] Forge document to private Message-ID: <93D28BDF64839C468B848D14227151A2025595F6@FIESEXC014.nsn-intra.net> FYI, documents will always be public if forge. We have to set them manually to private with this process: -you upload the document in the desired folder/subfolder -then you need to go to admin -find the just uploaded document in the "active" part -click on the document -change the state from "active" to "private" Br, Lorant -----Original Message----- From: randradas at gmail.com [mailto:randradas at gmail.com] On Behalf Of ext Roberto Andradas Izquierdo Sent: Wednesday, September 21, 2011 5:47 PM To: Farkas, Lorant (NSN - HU/Budapest) Cc: fiware-support at lists.fi-ware.eu; Bisztray, Denes (NSN - HU/Budapest) Subject: Re: [Fiware-support] Forge document to private Dear Lorant, it's a feature that can not be changed. You should change it manually. FusionForge is designed to maintain the software and the documentation free. Usually this kind of platforms are used to develop free software projects. kind regards! On 21 September 2011 13:49, Farkas, Lorant (NSN - HU/Budapest) wrote: > Dear Support team, > > When uploading a document to forge it automatically gets in the "active" > status, meaning open for the whole world. It would be helpful if on the > submission screen we had an option to set "private" as attribute for the > newly submitted document. Otherwise we have to go to admin, find the > respective document in the "active" category and set it manually to > "private". > > Is there any way to make this possible in forge? > > Thanks & Br, > > Lorant > > _______________________________________________ > Fiware-support mailing list > Fiware-support at lists.fi-ware.eu > http://lists.fi-ware.eu/listinfo/fiware-support > > From sabrina.guerra at telecomitalia.it Fri Sep 23 12:59:42 2011 From: sabrina.guerra at telecomitalia.it (Guerra Sabrina) Date: Fri, 23 Sep 2011 12:59:42 +0200 Subject: [Fiware-iot] R: Partner assets In-Reply-To: <93D28BDF64839C468B848D14227151A2025594A1@FIESEXC014.nsn-intra.net> References: <93D28BDF64839C468B848D14227151A2025594A1@FIESEXC014.nsn-intra.net> Message-ID: <36A93B31228D3B49B691AD31652BCAE9A563420B8E@GRFMBX702BA020.griffon.local> Dear All, I uploaded to forge the document Clarify-TI-asset-description.doc ("Clarify company asset description") with the private field set. Here there is the link to https://forge.fi-ware.eu/docman/index.php?group_id=11 Best regards, 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: Wednesday, September 21, 2011 4:44 PM A: fiware-iot at lists.fi-ware.eu Oggetto: [Fiware-iot] Partner assets Dear All, FYI, I uploaded to forge the company asset presentations I saw so far. With the private field set, of course. https://forge.fi-ware.eu/docman/?group_id=11# 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:00000000000000000000000000000001 at TI.Disclaimer]Rispetta l'ambiente. Non stampare questa mail se non ? necessario. -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: logo Ambiente_foglia.jpg Type: image/jpeg Size: 677 bytes Desc: logo Ambiente_foglia.jpg URL: From rheras at tid.es Fri Sep 23 14:08:11 2011 From: rheras at tid.es (Ricardo de las Heras) Date: Fri, 23 Sep 2011 14:08:11 +0200 Subject: [Fiware-iot] R: Partner assets In-Reply-To: <36A93B31228D3B49B691AD31652BCAE9A563420B8E@GRFMBX702BA020.griffon.local> References: <93D28BDF64839C468B848D14227151A2025594A1@FIESEXC014.nsn-intra.net> <36A93B31228D3B49B691AD31652BCAE9A563420B8E@GRFMBX702BA020.griffon.local> Message-ID: <4E7C76AB.7030700@tid.es> An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: image/jpeg Size: 677 bytes Desc: not available URL: From lorant.farkas at nsn.com Fri Sep 23 15:07:55 2011 From: lorant.farkas at nsn.com (Farkas, Lorant (NSN - HU/Budapest)) Date: Fri, 23 Sep 2011 16:07:55 +0300 Subject: [Fiware-iot] FW: private documents visible Message-ID: <93D28BDF64839C468B848D14227151A20255A10B@FIESEXC014.nsn-intra.net> FYI, careful with the uploads... Setting private does not help. Br, Lorant > ______________________________________________ > From: Bisztray, Denes (NSN - HU/Budapest) > Sent: Friday, September 23, 2011 3:07 PM > To: fiware-support at lists.fi-ware.eu > Cc: Farkas, Lorant (NSN - HU/Budapest) > Subject: private documents visible > > Hi, > > The supposedly private documents are still reachable from outside. If you search google for keywords from the docs, it finds them and gives you the link. I believe this is a SERIOUS security problem, please resolve it ASAP. > > Evidence: > > 1. Search for Cumulocity NSN: > http://www.google.fi/#sclient=psy-ab&hl=hu&source=hp&q=Cumulocity+NSN&pbx=1&oq=Cumulocity+NSN&aq=f&aqi=&aql=1&gs_sm=e&gs_upl=4279l4899l2l5159l4l3l0l0l0l0l224l428l2-2l3l0&bav=on.2,or.r_gc.r_pw.&fp=9a24604d477dfd8&biw=1373&bih=728 > > The third from the bottom is the PRIVATE supposedly not visible Architecture document. > > 2. Trying it with IDAS Telef?nica its even worse: > http://www.google.fi/#sclient=psy-ab&hl=hu&source=hp&q=IDAS+Telef%C3%B3nica&pbx=1&oq=IDAS+Telef%C3%B3nica&aq=f&aqi=&aql=1&gs_sm=e&gs_upl=49626l52101l0l52294l15l12l0l0l0l0l303l2660l0.1.9.1l11l0&bav=on.2,or.r_gc.r_pw.&fp=9a24604d477dfd8&biw=1373&bih=728 > It> '> s the third from the top. > > Best, > D?nes Bisztray > -------------- next part -------------- An HTML attachment was scrubbed... URL: From stephan.haller at sap.com Fri Sep 23 15:13:31 2011 From: stephan.haller at sap.com (Haller, Stephan) Date: Fri, 23 Sep 2011 15:13:31 +0200 Subject: [Fiware-iot] private documents visible In-Reply-To: <93D28BDF64839C468B848D14227151A20255A10B@FIESEXC014.nsn-intra.net> References: <93D28BDF64839C468B848D14227151A20255A10B@FIESEXC014.nsn-intra.net> Message-ID: <0D2446AEB6CAED48BB046223733964A54C407503BA@DEWDFECCR01.wdf.sap.corp> Who is taking care of this? If this cannot be resolved, we need to switch to another tool. Regards, -Stephan From: fiware-iot-bounces at lists.fi-ware.eu [mailto:fiware-iot-bounces at lists.fi-ware.eu] On Behalf Of Farkas, Lorant (NSN - HU/Budapest) Sent: Freitag, 23. September 2011 15:08 To: fiware-iot at lists.fi-ware.eu Subject: [Fiware-iot] FW: private documents visible FYI, careful with the uploads... Setting private does not help. Br, Lorant ______________________________________________ From: Bisztray, Denes (NSN - HU/Budapest) Sent: Friday, September 23, 2011 3:07 PM To: fiware-support at lists.fi-ware.eu Cc: Farkas, Lorant (NSN - HU/Budapest) Subject: private documents visible Hi, The supposedly private documents are still reachable from outside. If you search google for keywords from the docs, it finds them and gives you the link. I believe this is a SERIOUS security problem, please resolve it ASAP. Evidence: * Search for Cumulocity NSN: http://www.google.fi/#sclient=psy-ab&hl=hu&source=hp&q=Cumulocity+NSN&pbx=1&oq=Cumulocity+NSN&aq=f&aqi=&aql=1&gs_sm=e&gs_upl=4279l4899l2l5159l4l3l0l0l0l0l224l428l2-2l3l0&bav=on.2,or.r_gc.r_pw.&fp=9a24604d477dfd8&biw=1373&bih=728 The third from the bottom is the PRIVATE supposedly not visible Architecture document. 2. Trying it with IDAS Telef?nica its even worse: http://www.google.fi/#sclient=psy-ab&hl=hu&source=hp&q=IDAS+Telef%C3%B3nica&pbx=1&oq=IDAS+Telef%C3%B3nica&aq=f&aqi=&aql=1&gs_sm=e&gs_upl=49626l52101l0l52294l15l12l0l0l0l0l303l2660l0.1.9.1l11l0&bav=on.2,or.r_gc.r_pw.&fp=9a24604d477dfd8&biw=1373&bih=728 It's the third from the top. Best, D?nes Bisztray -------------- next part -------------- An HTML attachment was scrubbed... URL: From lorant.farkas at nsn.com Fri Sep 23 15:15:42 2011 From: lorant.farkas at nsn.com (Farkas, Lorant (NSN - HU/Budapest)) Date: Fri, 23 Sep 2011 16:15:42 +0300 Subject: [Fiware-iot] private documents visible In-Reply-To: <0D2446AEB6CAED48BB046223733964A54C407503BA@DEWDFECCR01.wdf.sap.corp> References: <93D28BDF64839C468B848D14227151A20255A10B@FIESEXC014.nsn-intra.net> <0D2446AEB6CAED48BB046223733964A54C407503BA@DEWDFECCR01.wdf.sap.corp> Message-ID: <93D28BDF64839C468B848D14227151A20255A120@FIESEXC014.nsn-intra.net> Support should say something. Juanjo and Thomas should be on that list. Br, Lorant ________________________________ From: ext Haller, Stephan [mailto:stephan.haller at sap.com] Sent: Friday, September 23, 2011 3:14 PM To: Farkas, Lorant (NSN - HU/Budapest); fiware-iot at lists.fi-ware.eu Subject: RE: private documents visible Who is taking care of this? If this cannot be resolved, we need to switch to another tool. Regards, -Stephan From: fiware-iot-bounces at lists.fi-ware.eu [mailto:fiware-iot-bounces at lists.fi-ware.eu] On Behalf Of Farkas, Lorant (NSN - HU/Budapest) Sent: Freitag, 23. September 2011 15:08 To: fiware-iot at lists.fi-ware.eu Subject: [Fiware-iot] FW: private documents visible FYI, careful with the uploads... Setting private does not help. Br, Lorant ______________________________________________ From: Bisztray, Denes (NSN - HU/Budapest) Sent: Friday, September 23, 2011 3:07 PM To: fiware-support at lists.fi-ware.eu Cc: Farkas, Lorant (NSN - HU/Budapest) Subject: private documents visible Hi, The supposedly private documents are still reachable from outside. If you search google for keywords from the docs, it finds them and gives you the link. I believe this is a SERIOUS security problem, please resolve it ASAP. Evidence: 1. Search for Cumulocity NSN: http://www.google.fi/#sclient=psy-ab&hl=hu&source=hp&q=Cumulocity+NSN&pbx=1&oq=Cumulocity+NSN&aq=f&aqi=&aql=1&gs_sm=e&gs_upl=4279l4899l2l5159l4l3l0l0l0l0l224l428l2-2l3l0&bav=on.2,or.r_gc.r_pw.&fp=9a24604d477dfd8&biw=1373&bih=728 The third from the bottom is the PRIVATE supposedly not visible Architecture document. 2. Trying it with IDAS Telef?nica its even worse: http://www.google.fi/#sclient=psy-ab&hl=hu&source=hp&q=IDAS+Telef%C3%B3nica&pbx=1&oq=IDAS+Telef%C3%B3nica&aq=f&aqi=&aql=1&gs_sm=e&gs_upl=49626l52101l0l52294l15l12l0l0l0l0l303l2660l0.1.9.1l11l0&bav=on.2,or.r_gc.r_pw.&fp=9a24604d477dfd8&biw=1373&bih=728 It's the third from the top. Best, D?nes Bisztray -------------- next part -------------- An HTML attachment was scrubbed... URL: From P.Barnaghi at surrey.ac.uk Fri Sep 23 16:44:22 2011 From: P.Barnaghi at surrey.ac.uk (P.Barnaghi at surrey.ac.uk) Date: Fri, 23 Sep 2011 15:44:22 +0100 Subject: [Fiware-iot] R: Partner assets In-Reply-To: <4E7C76AB.7030700@tid.es> References: <93D28BDF64839C468B848D14227151A2025594A1@FIESEXC014.nsn-intra.net> <36A93B31228D3B49B691AD31652BCAE9A563420B8E@GRFMBX702BA020.griffon.local> <4E7C76AB.7030700@tid.es> Message-ID: Dear all, Details of the University of Surrey assets and descriptions regarding possible integration of the components is uploaded on Forge. https://forge.fi-ware.eu/docman/view.php/11/428/FIWare_University_of_Surrey_assets_description.doc p.s. I uploaded as public by mistake at first (apparently I can't delete it after upload); and later I uploaded a different copy as private. But, I can see both of them without being logged in. Best regards, Payam ________________________________ From: fiware-iot-bounces at lists.fi-ware.eu [mailto:fiware-iot-bounces at lists.fi-ware.eu] On Behalf Of Ricardo de las Heras Sent: 23 September 2011 13:08 To: 'fiware-iot at lists.fi-ware.eu' Subject: Re: [Fiware-iot] R: Partner assets Dear all, More details about IDAS platform were also uploaded there: https://forge.fi-ware.eu/docman/view.php/11/425/IDAS-Telefonica.asset.T5.2-Details.docx have a nice week-end, Ricardo. Guerra Sabrina wrote: Dear All, I uploaded to forge the document Clarify-TI-asset-description.doc ("Clarify company asset description") with the private field set. Here there is the link to https://forge.fi-ware.eu/docman/index.php?group_id=11 Best regards, 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: Wednesday, September 21, 2011 4:44 PM A: fiware-iot at lists.fi-ware.eu Oggetto: [Fiware-iot] Partner assets Dear All, FYI, I uploaded to forge the company asset presentations I saw so far. With the private field set, of course. https://forge.fi-ware.eu/docman/?group_id=11# 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:image001.gif at 01CC7A07.AA0B2A80]Rispetta l'ambiente. Non stampare questa mail se non ? necessario. -- ------------------------------------- Ricardo de las Heras M2M Research Project Manager E-mail: rheras at tid.es Phone1: (+34) 983 367625 Phone2 OCS: (+34) 91 31 29511 Phone3 Skype: (+34) 91 1878107 + Ext: 327 Telef?nica I+D ------------------------------------- ________________________________ Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra pol?tica de env?o y recepci?n de correo electr?nico en el enlace situado m?s abajo. This message is intended exclusively for its addressee. We only send and receive email on the basis of the terms set out at. http://www.tid.es/ES/PAGINAS/disclaimer.aspx -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.gif Type: image/gif Size: 677 bytes Desc: image001.gif URL: From Ernoe.Kovacs at neclab.eu Sun Sep 25 21:41:00 2011 From: Ernoe.Kovacs at neclab.eu (Ernoe Kovacs) Date: Sun, 25 Sep 2011 19:41:00 +0000 Subject: [Fiware-iot] private documents visible In-Reply-To: <93D28BDF64839C468B848D14227151A20255A120@FIESEXC014.nsn-intra.net> References: <93D28BDF64839C468B848D14227151A20255A10B@FIESEXC014.nsn-intra.net> <0D2446AEB6CAED48BB046223733964A54C407503BA@DEWDFECCR01.wdf.sap.corp> <93D28BDF64839C468B848D14227151A20255A120@FIESEXC014.nsn-intra.net> Message-ID: <8152E2132B13FB488CFD1947E2DEF19C1CFBDD29@DAPHNIS.office.hd> Small feedback from our side... ... when I explained to some people here working on FI-Ware, they immediately said this is against the CA. Didn't escalated it yet, but it is an issue that needs solving. Swithcing to another tool is fine. Please be aware, this is an issue ! - Ern? 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, 23. September 2011 15:16 To: ext Haller, Stephan; fiware-iot at lists.fi-ware.eu Subject: Re: [Fiware-iot] private documents visible Support should say something. Juanjo and Thomas should be on that list. Br, Lorant ________________________________ From: ext Haller, Stephan [mailto:stephan.haller at sap.com] Sent: Friday, September 23, 2011 3:14 PM To: Farkas, Lorant (NSN - HU/Budapest); fiware-iot at lists.fi-ware.eu Subject: RE: private documents visible Who is taking care of this? If this cannot be resolved, we need to switch to another tool. Regards, -Stephan From: fiware-iot-bounces at lists.fi-ware.eu [mailto:fiware-iot-bounces at lists.fi-ware.eu] On Behalf Of Farkas, Lorant (NSN - HU/Budapest) Sent: Freitag, 23. September 2011 15:08 To: fiware-iot at lists.fi-ware.eu Subject: [Fiware-iot] FW: private documents visible FYI, careful with the uploads... Setting private does not help. Br, Lorant ______________________________________________ From: Bisztray, Denes (NSN - HU/Budapest) Sent: Friday, September 23, 2011 3:07 PM To: fiware-support at lists.fi-ware.eu Cc: Farkas, Lorant (NSN - HU/Budapest) Subject: private documents visible Hi, The supposedly private documents are still reachable from outside. If you search google for keywords from the docs, it finds them and gives you the link. I believe this is a SERIOUS security problem, please resolve it ASAP. Evidence: * Search for Cumulocity NSN: http://www.google.fi/#sclient=psy-ab&hl=hu&source=hp&q=Cumulocity+NSN&pbx=1&oq=Cumulocity+NSN&aq=f&aqi=&aql=1&gs_sm=e&gs_upl=4279l4899l2l5159l4l3l0l0l0l0l224l428l2-2l3l0&bav=on.2,or.r_gc.r_pw.&fp=9a24604d477dfd8&biw=1373&bih=728 The third from the bottom is the PRIVATE supposedly not visible Architecture document. 2. Trying it with IDAS Telef?nica its even worse: http://www.google.fi/#sclient=psy-ab&hl=hu&source=hp&q=IDAS+Telef%C3%B3nica&pbx=1&oq=IDAS+Telef%C3%B3nica&aq=f&aqi=&aql=1&gs_sm=e&gs_upl=49626l52101l0l52294l15l12l0l0l0l0l303l2660l0.1.9.1l11l0&bav=on.2,or.r_gc.r_pw.&fp=9a24604d477dfd8&biw=1373&bih=728 It's the third from the top. Best, D?nes Bisztray -------------- next part -------------- An HTML attachment was scrubbed... URL: From jhierro at tid.es Sun Sep 25 23:22:16 2011 From: jhierro at tid.es (Juanjo Hierro) Date: Sun, 25 Sep 2011 23:22:16 +0200 Subject: [Fiware-iot] private documents visible In-Reply-To: <8152E2132B13FB488CFD1947E2DEF19C1CFBDD29@DAPHNIS.office.hd> References: <93D28BDF64839C468B848D14227151A20255A10B@FIESEXC014.nsn-intra.net> <0D2446AEB6CAED48BB046223733964A54C407503BA@DEWDFECCR01.wdf.sap.corp> <93D28BDF64839C468B848D14227151A20255A120@FIESEXC014.nsn-intra.net> <8152E2132B13FB488CFD1947E2DEF19C1CFBDD29@DAPHNIS.office.hd> Message-ID: <4E7F9B88.6030506@tid.es> Hi, I have taken a look at this issue. Apparently, the access to the documents you mention is restricted. Maybe you were clicking on the links above and it worked because you had logged previously to FusionForge and the session was still open. I tested the access myself for the first document (Cumulocity NSN), first without being logged in FusionForge and second once I had logged in. The document was only accessible when I was logged in. Without being logged in FusionForge, a "Permission denied" message is returned. What seems to be happening is that private documents are indexed by the Google crawlers (although at the end of the day, they remain inaccessible). This is an issue we should fix. However, let me make the point that no private document has become publicly accessible, which is what really matters. We should fix this asap, but let me say it doesn't seem as critical as it appeared to be. Best regards, -- Juanjo On 25/09/11 21:41, Ernoe Kovacs wrote: Small feedback from our side... ... when I explained to some people here working on FI-Ware, they immediately said this is against the CA. Didn't escalated it yet, but it is an issue that needs solving. Swithcing to another tool is fine. Please be aware, this is an issue ! - Ern? 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, 23. September 2011 15:16 To: ext Haller, Stephan; fiware-iot at lists.fi-ware.eu Subject: Re: [Fiware-iot] private documents visible Support should say something. Juanjo and Thomas should be on that list. Br, Lorant ________________________________ From: ext Haller, Stephan [mailto:stephan.haller at sap.com] Sent: Friday, September 23, 2011 3:14 PM To: Farkas, Lorant (NSN - HU/Budapest); fiware-iot at lists.fi-ware.eu Subject: RE: private documents visible Who is taking care of this? If this cannot be resolved, we need to switch to another tool. Regards, -Stephan From: fiware-iot-bounces at lists.fi-ware.eu [mailto:fiware-iot-bounces at lists.fi-ware.eu] On Behalf Of Farkas, Lorant (NSN - HU/Budapest) Sent: Freitag, 23. September 2011 15:08 To: fiware-iot at lists.fi-ware.eu Subject: [Fiware-iot] FW: private documents visible FYI, careful with the uploads... Setting private does not help. Br, Lorant ______________________________________________ From: Bisztray, Denes (NSN - HU/Budapest) Sent: Friday, September 23, 2011 3:07 PM To: fiware-support at lists.fi-ware.eu Cc: Farkas, Lorant (NSN - HU/Budapest) Subject: private documents visible Hi, The supposedly private documents are still reachable from outside. If you search google for keywords from the docs, it finds them and gives you the link. I believe this is a SERIOUS security problem, please resolve it ASAP. Evidence: * Search for Cumulocity NSN: http://www.google.fi/#sclient=psy-ab&hl=hu&source=hp&q=Cumulocity+NSN&pbx=1&oq=Cumulocity+NSN&aq=f&aqi=&aql=1&gs_sm=e&gs_upl=4279l4899l2l5159l4l3l0l0l0l0l224l428l2-2l3l0&bav=on.2,or.r_gc.r_pw.&fp=9a24604d477dfd8&biw=1373&bih=728 The third from the bottom is the PRIVATE supposedly not visible Architecture document. 2. Trying it with IDAS Telef?nica its even worse: http://www.google.fi/#sclient=psy-ab&hl=hu&source=hp&q=IDAS+Telef%C3%B3nica&pbx=1&oq=IDAS+Telef%C3%B3nica&aq=f&aqi=&aql=1&gs_sm=e&gs_upl=49626l52101l0l52294l15l12l0l0l0l0l303l2660l0.1.9.1l11l0&bav=on.2,or.r_gc.r_pw.&fp=9a24604d477dfd8&biw=1373&bih=728 It's the third from the top. Best, D?nes Bisztray ________________________________ 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 Sep 26 09:27:16 2011 From: lorant.farkas at nsn.com (Farkas, Lorant (NSN - HU/Budapest)) Date: Mon, 26 Sep 2011 10:27:16 +0300 Subject: [Fiware-iot] Please set submissions to "private" Message-ID: <93D28BDF64839C468B848D14227151A20259DE95@FIESEXC014.nsn-intra.net> Dear All, May I kindly remind you that after submitting something to forge, you need to go to admin, look for the document you submitted in the "Active" part, click on it and set it to "private", unless you want google to find it. There were some contributions this morning that were public, I took care of them now. Thanks & Br, Lorant -------------- next part -------------- An HTML attachment was scrubbed... URL: From Ernoe.Kovacs at neclab.eu Mon Sep 26 21:29:42 2011 From: Ernoe.Kovacs at neclab.eu (Ernoe Kovacs) Date: Mon, 26 Sep 2011 19:29:42 +0000 Subject: [Fiware-iot] private documents visible In-Reply-To: <4E7F9B88.6030506@tid.es> References: <93D28BDF64839C468B848D14227151A20255A10B@FIESEXC014.nsn-intra.net> <0D2446AEB6CAED48BB046223733964A54C407503BA@DEWDFECCR01.wdf.sap.corp> <93D28BDF64839C468B848D14227151A20255A120@FIESEXC014.nsn-intra.net> <8152E2132B13FB488CFD1947E2DEF19C1CFBDD29@DAPHNIS.office.hd> <4E7F9B88.6030506@tid.es> Message-ID: <8152E2132B13FB488CFD1947E2DEF19C1CFC070B@DAPHNIS.office.hd> Juanjo, thanks for looking into the issue and give it the priority it needs. I have trust we solve the issue to all our satisfaction. Damned tools, never do like they should ;-) - Ern? From: Juanjo Hierro [mailto:jhierro at tid.es] Sent: Sonntag, 25. September 2011 23:22 To: Ernoe Kovacs Cc: Farkas, Lorant (NSN - HU/Budapest); ext Haller, Stephan; fiware-iot at lists.fi-ware.eu Subject: Re: [Fiware-iot] private documents visible Hi, I have taken a look at this issue. Apparently, the access to the documents you mention is restricted. Maybe you were clicking on the links above and it worked because you had logged previously to FusionForge and the session was still open. I tested the access myself for the first document (Cumulocity NSN), first without being logged in FusionForge and second once I had logged in. The document was only accessible when I was logged in. Without being logged in FusionForge, a "Permission denied" message is returned. What seems to be happening is that private documents are indexed by the Google crawlers (although at the end of the day, they remain inaccessible). This is an issue we should fix. However, let me make the point that no private document has become publicly accessible, which is what really matters. We should fix this asap, but let me say it doesn't seem as critical as it appeared to be. Best regards, -- Juanjo On 25/09/11 21:41, Ernoe Kovacs wrote: Small feedback from our side... ... when I explained to some people here working on FI-Ware, they immediately said this is against the CA. Didn't escalated it yet, but it is an issue that needs solving. Swithcing to another tool is fine. Please be aware, this is an issue ! - Ern? 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, 23. September 2011 15:16 To: ext Haller, Stephan; fiware-iot at lists.fi-ware.eu Subject: Re: [Fiware-iot] private documents visible Support should say something. Juanjo and Thomas should be on that list. Br, Lorant ________________________________ From: ext Haller, Stephan [mailto:stephan.haller at sap.com] Sent: Friday, September 23, 2011 3:14 PM To: Farkas, Lorant (NSN - HU/Budapest); fiware-iot at lists.fi-ware.eu Subject: RE: private documents visible Who is taking care of this? If this cannot be resolved, we need to switch to another tool. Regards, -Stephan From: fiware-iot-bounces at lists.fi-ware.eu [mailto:fiware-iot-bounces at lists.fi-ware.eu] On Behalf Of Farkas, Lorant (NSN - HU/Budapest) Sent: Freitag, 23. September 2011 15:08 To: fiware-iot at lists.fi-ware.eu Subject: [Fiware-iot] FW: private documents visible FYI, careful with the uploads... Setting private does not help. Br, Lorant ______________________________________________ From: Bisztray, Denes (NSN - HU/Budapest) Sent: Friday, September 23, 2011 3:07 PM To: fiware-support at lists.fi-ware.eu Cc: Farkas, Lorant (NSN - HU/Budapest) Subject: private documents visible Hi, The supposedly private documents are still reachable from outside. If you search google for keywords from the docs, it finds them and gives you the link. I believe this is a SERIOUS security problem, please resolve it ASAP. Evidence: * Search for Cumulocity NSN: http://www.google.fi/#sclient=psy-ab&hl=hu&source=hp&q=Cumulocity+NSN&pbx=1&oq=Cumulocity+NSN&aq=f&aqi=&aql=1&gs_sm=e&gs_upl=4279l4899l2l5159l4l3l0l0l0l0l224l428l2-2l3l0&bav=on.2,or.r_gc.r_pw.&fp=9a24604d477dfd8&biw=1373&bih=728 The third from the bottom is the PRIVATE supposedly not visible Architecture document. 2. Trying it with IDAS Telef?nica its even worse: http://www.google.fi/#sclient=psy-ab&hl=hu&source=hp&q=IDAS+Telef%C3%B3nica&pbx=1&oq=IDAS+Telef%C3%B3nica&aq=f&aqi=&aql=1&gs_sm=e&gs_upl=49626l52101l0l52294l15l12l0l0l0l0l303l2660l0.1.9.1l11l0&bav=on.2,or.r_gc.r_pw.&fp=9a24604d477dfd8&biw=1373&bih=728 It's the third from the top. Best, D?nes Bisztray ________________________________ 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 Tue Sep 27 09:14:25 2011 From: lorant.farkas at nsn.com (Farkas, Lorant (NSN - HU/Budapest)) Date: Tue, 27 Sep 2011 10:14:25 +0300 Subject: [Fiware-iot] Updated: IoT weekly meeting Message-ID: <93D28BDF64839C468B848D14227151A20259E567@FIESEXC014.nsn-intra.net> When: 2011. szeptember 28. 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. *~*~*~*~*~*~*~*~*~* Proposed agenda for tomorrow: 1. Short update from the WPA/WPL meeting from 26/09 (10-20 minutes) -what is missing for the 2nd version of the HLD from our perspective -work to be done during October 2. Go through the partner asset selection analysis documents and create a tentative first list of baseline assets (1 hour) -Task leaders are expected to provide the analysis doc in the following folder: https://forge.fi-ware.eu/docman/index.php?group_id=11# -There should be 4 docs for the 4 tasks -You will find already one for process automation that you could use as a model. We expect still to update this doc during the day https://forge.fi-ware.eu/docman/view.php/11/438/ProcessAutomation-AssetSelection.docx -And the final version of the asset mapping xls cleared from epics you could use as starting point for your analysis https://forge.fi-ware.eu/docman/view.php/11/437/v16_IoT-Architecture-mapping.xls 3. Discuss the next steps for the selected assets (10-20 minutes): -1-2 pages description and link to more detailed description -integration aspects -licensing aspects -who and how will put these into the HLD 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: 11888 bytes Desc: not available URL: From sabrina.guerra at telecomitalia.it Tue Sep 27 11:14:44 2011 From: sabrina.guerra at telecomitalia.it (Guerra Sabrina) Date: Tue, 27 Sep 2011 11:14:44 +0200 Subject: [Fiware-iot] R: IoT weekly meeting In-Reply-To: <93D28BDF64839C468B848D14227151A20259E567@FIESEXC014.nsn-intra.net> References: <93D28BDF64839C468B848D14227151A20259E567@FIESEXC014.nsn-intra.net> Message-ID: <36A93B31228D3B49B691AD31652BCAE9A56397F5A8@GRFMBX702BA020.griffon.local> Hi all, excuse me but tomorrow I won't be able to join the call. Is it possible to skip this session? Thanks. Best regards, 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: Tuesday, September 27, 2011 9:14 AM A: fiware-iot at lists.fi-ware.eu Oggetto: [Fiware-iot] Updated: IoT weekly meeting When: 2011. szeptember 28. 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. *~*~*~*~*~*~*~*~*~* Proposed agenda for tomorrow: 1. Short update from the WPA/WPL meeting from 26/09 (10-20 minutes) -what is missing for the 2nd version of the HLD from our perspective -work to be done during October 2. Go through the partner asset selection analysis documents and create a tentative first list of baseline assets (1 hour) -Task leaders are expected to provide the analysis doc in the following folder: https://forge.fi-ware.eu/docman/index.php?group_id=11# -There should be 4 docs for the 4 tasks -You will find already one for process automation that you could use as a model. We expect still to update this doc during the day https://forge.fi-ware.eu/docman/view.php/11/438/ProcessAutomation-AssetSelection.docx -And the final version of the asset mapping xls cleared from epics you could use as starting point for your analysis https://forge.fi-ware.eu/docman/view.php/11/437/v16_IoT-Architecture-mapping.xls 3. Discuss the next steps for the selected assets (10-20 minutes): -1-2 pages description and link to more detailed description -integration aspects -licensing aspects -who and how will put these into the HLD 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) Questo messaggio e i suoi allegati sono indirizzati esclusivamente alle persone indicate. La diffusione, copia o qualsiasi altra azione derivante dalla conoscenza di queste informazioni sono rigorosamente vietate. Qualora abbiate ricevuto questo documento per errore siete cortesemente pregati di darne immediata comunicazione al mittente e di provvedere alla sua distruzione, Grazie. This e-mail and any attachments is confidential and may contain privileged information intended for the addressee(s) only. Dissemination, copying, printing or use by anybody else is unauthorised. If you are not the intended recipient, please delete this message and any attachments and advise the sender by return e-mail, Thanks. [cid:00000000000000000000000000000001 at TI.Disclaimer]Rispetta l'ambiente. Non stampare questa mail se non ? necessario. -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: logo Ambiente_foglia.jpg Type: image/jpeg Size: 677 bytes Desc: logo Ambiente_foglia.jpg URL: From lorant.farkas at nsn.com Tue Sep 27 12:03:15 2011 From: lorant.farkas at nsn.com (Farkas, Lorant (NSN - HU/Budapest)) Date: Tue, 27 Sep 2011 13:03:15 +0300 Subject: [Fiware-iot] IoT weekly meeting In-Reply-To: <36A93B31228D3B49B691AD31652BCAE9A56397F5A8@GRFMBX702BA020.griffon.local> References: <93D28BDF64839C468B848D14227151A20259E567@FIESEXC014.nsn-intra.net> <36A93B31228D3B49B691AD31652BCAE9A56397F5A8@GRFMBX702BA020.griffon.local> Message-ID: <93D28BDF64839C468B848D14227151A20259E7D6@FIESEXC014.nsn-intra.net> Hi Sabrina, I'm afraid it is not possible, we have to meet the deadline of 30 Sept will all the topics I listed. Thanks & Br, Lorant ________________________________ From: ext Guerra Sabrina [mailto:sabrina.guerra at telecomitalia.it] Sent: Tuesday, September 27, 2011 11:15 AM To: Farkas, Lorant (NSN - HU/Budapest); 'fiware-iot at lists.fi-ware.eu' Subject: R: IoT weekly meeting Hi all, excuse me but tomorrow I won't be able to join the call. Is it possible to skip this session? Thanks. Best regards, 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: Tuesday, September 27, 2011 9:14 AM A: fiware-iot at lists.fi-ware.eu Oggetto: [Fiware-iot] Updated: IoT weekly meeting When: 2011. szeptember 28. 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. *~*~*~*~*~*~*~*~*~* Proposed agenda for tomorrow: 1. Short update from the WPA/WPL meeting from 26/09 (10-20 minutes) -what is missing for the 2nd version of the HLD from our perspective -work to be done during October 2. Go through the partner asset selection analysis documents and create a tentative first list of baseline assets (1 hour) -Task leaders are expected to provide the analysis doc in the following folder: https://forge.fi-ware.eu/docman/index.php?group_id=11# -There should be 4 docs for the 4 tasks -You will find already one for process automation that you could use as a model. We expect still to update this doc during the day https://forge.fi-ware.eu/docman/view.php/11/438/ProcessAutomation-AssetSelection.docx -And the final version of the asset mapping xls cleared from epics you could use as starting point for your analysis https://forge.fi-ware.eu/docman/view.php/11/437/v16_IoT-Architecture-mapping.xls 3. Discuss the next steps for the selected assets (10-20 minutes): -1-2 pages description and link to more detailed description -integration aspects -licensing aspects -who and how will put these into the HLD 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) Questo messaggio e i suoi allegati sono indirizzati esclusivamente alle persone indicate. La diffusione, copia o qualsiasi altra azione derivante dalla conoscenza di queste informazioni sono rigorosamente vietate. Qualora abbiate ricevuto questo documento per errore siete cortesemente pregati di darne immediata comunicazione al mittente e di provvedere alla sua distruzione, Grazie. This e-mail and any attachments is confidential and may contain privileged information intended for the addressee(s) only. Dissemination, copying, printing or use by anybody else is unauthorised. If you are not the intended recipient, please delete this message and any attachments and advise the sender by return e-mail, Thanks. Rispetta l'ambiente. Non stampare questa mail se non ? necessario. -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: logo Ambiente_foglia.jpg Type: image/jpeg Size: 677 bytes Desc: logo Ambiente_foglia.jpg URL: From fano.ramparany at orange.com Tue Sep 27 13:41:09 2011 From: fano.ramparany at orange.com (fano.ramparany at orange.com) Date: Tue, 27 Sep 2011 13:41:09 +0200 Subject: [Fiware-iot] [FusionForge Problems with] OMA NGSI API In-Reply-To: References: <8152E2132B13FB488CFD1947E2DEF19C1CFA6B43@DAPHNIS.office.hd> <0D2446AEB6CAED48BB046223733964A54C3EA9A44E@DEWDFECCR01.wdf.sap.corp> <23052_1315858707_4E6E6913_23052_397275_1_BAF83494CE653943A97B9F755016A066098203DF@ftrdmel1> Message-ID: Hi Carsten, Nice to know that you're involved in FIware. I'm involved in WP6 Data and Context Management and also in the UA project Outsmart on Utilities and Environment. By the way could you give me the email of your colleague Michael Stollberg. I met him at the PPP FI Architecture Board. Kind regards, Fano De : fiware-iot-bounces at lists.fi-ware.eu [mailto:fiware-iot-bounces at lists.fi-ware.eu] De la part de Martin Bauer Envoy? : mardi 13 septembre 2011 09:23 ? : NAGELLEN Thierry RD-BIZZ-SOP; stephan.haller at sap.com; thomas.michael.bohnert at sap.com; carsten.magerkurth at sap.com; torsten.leidig at sap.com; andreas.friesen at sap.com Cc : fiware-iot at lists.fi-ware.eu Objet : Re: [Fiware-iot] [FusionForge Problems with] OMA NGSI API Hi Thierry, Stephan, all, The partners involved in both IoT-A and FI-WARE WP5 are SAP, NEC, University of Surrey and Telefonica I+D. We can start discussing with the people involved during the Torino meeting. Apart from the Application side, which is the SAP focus, there is also the Resolution and Discovery infrastructure from IoT-A WP4. I am the WP leader and TID (Ricardo), Surrey, and NEC are three of the four task leaders, so there is quite some overlap that could be utilized. I will also be in Poznan end of October. Best regards, Martin ------------------------------------------ Dr. Martin Bauer Senior Researcher NEC Europe Ltd. NEC Laboratories Europe Software & Services Research Division Kurf?rsten-Anlage 36 D-69115 Heidelberg Tel: +49/ (0)6221/4342-168 Fax: +49/ (0)6221/4342-155 E-Mail: Martin.Bauer at neclab.eu http://www.nw.neclab.eu From: fiware-iot-bounces at lists.fi-ware.eu [mailto:fiware-iot-bounces at lists.fi-ware.eu] On Behalf Of thierry.nagellen at orange-ftgroup.com Sent: Montag, 12. September 2011 22:18 To: stephan.haller at sap.com; thomas.michael.bohnert at sap.com; carsten.magerkurth at sap.com; torsten.leidig at sap.com; andreas.friesen at sap.com Cc: fiware-iot at lists.fi-ware.eu Subject: Re: [Fiware-iot] [FusionForge Problems with] OMA NGSI API HI Stefan Thanks a lot for your contribution. We will discuss all content during Torino meeting and try to find the best way for User stories description. Regarding IoT-A project, could you - with Ern? as your companies are partners of this project - share some expected deadlines and what kind of results could be used (if this information is public of course). Maybe we should also planned a meeting between WP IoT and IoT-A project to exchange about this issue, to improve some architecture elements and also to share the vision of UA projects because we should have more details at the end of September (first requirements, detailed presentation during Architecture Board 21-22/09). Do you think this join meeting could happen in Poznan (end of October, during the FI week?) BR Thierry De : Haller, Stephan [mailto:stephan.haller at sap.com] Envoy? : lundi 12 septembre 2011 09:51 ? : NAGELLEN Thierry RD-BIZZ-SOP; Bohnert, Thomas Michael; Magerkurth, Carsten; Leidig, Torsten; Friesen, Andreas Cc : fiware-iot at lists.fi-ware.eu; Sperner, Klaus; Meyer, Sonja Objet : RE: [FusionForge Problems with] OMA NGSI API All, I have started to write up some user stories for the area where IoT and Apps&Services meet. This is also where our core interest lies and where we will bring in some assets (from the IoT-A project). This is just a first draft, far from complete. But I wanted to provide this as an input for the meetings in Torino. Regards, -Stephan Stephan Haller Development Architect - Internet of Things, SAP Research SAP (Schweiz) AG, Kreuzplatz, Kreuzplatz 20, CH-8008 Z?rich, Switzerland T +41 58 871 78 45, F +41 58 871 78 12 mailto:stephan.haller at sap.com Please consider the impact on the environment before printing this e-mail. ******************************************************************************** IMPORTANT.Les informations contenues dans ce message electronique y compris les fichiers attaches sont strictement confidentielles et peuvent etre protegees par la loi. Ce message electronique est destine exclusivement au(x) destinataire(s) mentionne(s) ci-dessus. Si vous avez recu ce message par erreur ou s il ne vous est pas destine, veuillez immediatement le signaler a l expediteur et effacer ce message et tous les fichiers eventuellement attaches. Toute lecture, exploitation ou transmission des informations contenues dans ce message est interdite. Tout message electronique est susceptible d alteration. A ce titre, le Groupe France Telecom decline toute responsabilite notamment s il a ete altere, deforme ou falsifie. De meme, il appartient au destinataire de s assurer de l absence de tout virus. IMPORTANT.This e-mail message and any attachments are strictly confidential and may be protected by law. This message is intended only for the named recipient(s) above. If you have received this message in error, or are not the named recipient(s), please immediately notify the sender and delete this e-mail message. Any unauthorized view, usage or disclosure ofthis message is prohibited. Since e-mail messages may not be reliable, France Telecom Group shall not be liable for any message if modified, changed or falsified. Additionally the recipient should ensure they are actually virus free. ******************************************************************************** -------------- next part -------------- An HTML attachment was scrubbed... URL: From Ernoe.Kovacs at neclab.eu Wed Sep 28 09:31:37 2011 From: Ernoe.Kovacs at neclab.eu (Ernoe Kovacs) Date: Wed, 28 Sep 2011 07:31:37 +0000 Subject: [Fiware-iot] FI-Ware: IoT: Simplified View on our Architecture Message-ID: <8152E2132B13FB488CFD1947E2DEF19C1CFC4A16@DAPHNIS.office.hd> Hi all, I try to formulate a simplified view on our architecture. Basic idea is to have something that is easy to understand and allows to see the big picture. After that we can flesh out the details and map work in the tasks to the simplified architecture. In general, I see T5.1 mapping to the communication layer, T5.2 and 5.3 mapping to the enabler/service implementation and pre-defined APIs layer, and T5.4 mapping to the dynamic processes and respective exposed APIs. Yes, this is mainly the backend side, but actually you can recursively apply the same archtitecture to an generic IoT Agent on the a Gateway. I hope this helps in thinking about the WP5 IoT architecture. Kind regards Ern? From: fiware-iot-bounces at lists.fi-ware.eu [mailto:fiware-iot-bounces at lists.fi-ware.eu] On Behalf Of fano.ramparany at orange.com Sent: Dienstag, 27. September 2011 13:41 To: carsten.magerkurth at sap.com Cc: fiware-iot at lists.fi-ware.eu Subject: Re: [Fiware-iot] [FusionForge Problems with] OMA NGSI API Hi Carsten, Nice to know that you're involved in FIware. I'm involved in WP6 Data and Context Management and also in the UA project Outsmart on Utilities and Environment. By the way could you give me the email of your colleague Michael Stollberg. I met him at the PPP FI Architecture Board. Kind regards, Fano De : fiware-iot-bounces at lists.fi-ware.eu [mailto:fiware-iot-bounces at lists.fi-ware.eu] De la part de Martin Bauer Envoy? : mardi 13 septembre 2011 09:23 ? : NAGELLEN Thierry RD-BIZZ-SOP; stephan.haller at sap.com; thomas.michael.bohnert at sap.com; carsten.magerkurth at sap.com; torsten.leidig at sap.com; andreas.friesen at sap.com Cc : fiware-iot at lists.fi-ware.eu Objet : Re: [Fiware-iot] [FusionForge Problems with] OMA NGSI API Hi Thierry, Stephan, all, The partners involved in both IoT-A and FI-WARE WP5 are SAP, NEC, University of Surrey and Telefonica I+D. We can start discussing with the people involved during the Torino meeting. Apart from the Application side, which is the SAP focus, there is also the Resolution and Discovery infrastructure from IoT-A WP4. I am the WP leader and TID (Ricardo), Surrey, and NEC are three of the four task leaders, so there is quite some overlap that could be utilized. I will also be in Poznan end of October. Best regards, Martin ------------------------------------------ Dr. Martin Bauer Senior Researcher NEC Europe Ltd. NEC Laboratories Europe Software & Services Research Division Kurf?rsten-Anlage 36 D-69115 Heidelberg Tel: +49/ (0)6221/4342-168 Fax: +49/ (0)6221/4342-155 E-Mail: Martin.Bauer at neclab.eu http://www.nw.neclab.eu From: fiware-iot-bounces at lists.fi-ware.eu [mailto:fiware-iot-bounces at lists.fi-ware.eu] On Behalf Of thierry.nagellen at orange-ftgroup.com Sent: Montag, 12. September 2011 22:18 To: stephan.haller at sap.com; thomas.michael.bohnert at sap.com; carsten.magerkurth at sap.com; torsten.leidig at sap.com; andreas.friesen at sap.com Cc: fiware-iot at lists.fi-ware.eu Subject: Re: [Fiware-iot] [FusionForge Problems with] OMA NGSI API HI Stefan Thanks a lot for your contribution. We will discuss all content during Torino meeting and try to find the best way for User stories description. Regarding IoT-A project, could you - with Ern? as your companies are partners of this project - share some expected deadlines and what kind of results could be used (if this information is public of course). Maybe we should also planned a meeting between WP IoT and IoT-A project to exchange about this issue, to improve some architecture elements and also to share the vision of UA projects because we should have more details at the end of September (first requirements, detailed presentation during Architecture Board 21-22/09). Do you think this join meeting could happen in Poznan (end of October, during the FI week?) BR Thierry De : Haller, Stephan [mailto:stephan.haller at sap.com] Envoy? : lundi 12 septembre 2011 09:51 ? : NAGELLEN Thierry RD-BIZZ-SOP; Bohnert, Thomas Michael; Magerkurth, Carsten; Leidig, Torsten; Friesen, Andreas Cc : fiware-iot at lists.fi-ware.eu; Sperner, Klaus; Meyer, Sonja Objet : RE: [FusionForge Problems with] OMA NGSI API All, I have started to write up some user stories for the area where IoT and Apps&Services meet. This is also where our core interest lies and where we will bring in some assets (from the IoT-A project). This is just a first draft, far from complete. But I wanted to provide this as an input for the meetings in Torino. Regards, -Stephan Stephan Haller Development Architect - Internet of Things, SAP Research SAP (Schweiz) AG, Kreuzplatz, Kreuzplatz 20, CH-8008 Z?rich, Switzerland T +41 58 871 78 45, F +41 58 871 78 12 mailto:stephan.haller at sap.com Please consider the impact on the environment before printing this e-mail. ******************************************************************************** IMPORTANT.Les informations contenues dans ce message electronique y compris les fichiers attaches sont strictement confidentielles et peuvent etre protegees par la loi. Ce message electronique est destine exclusivement au(x) destinataire(s) mentionne(s) ci-dessus. Si vous avez recu ce message par erreur ou s il ne vous est pas destine, veuillez immediatement le signaler a l expediteur et effacer ce message et tous les fichiers eventuellement attaches. Toute lecture, exploitation ou transmission des informations contenues dans ce message est interdite. Tout message electronique est susceptible d alteration. A ce titre, le Groupe France Telecom decline toute responsabilite notamment s il a ete altere, deforme ou falsifie. De meme, il appartient au destinataire de s assurer de l absence de tout virus. IMPORTANT.This e-mail message and any attachments are strictly confidential and may be protected by law. This message is intended only for the named recipient(s) above. If you have received this message in error, or are not the named recipient(s), please immediately notify the sender and delete this e-mail message. Any unauthorized view, usage or disclosure ofthis message is prohibited. Since e-mail messages may not be reliable, France Telecom Group shall not be liable for any message if modified, changed or falsified. Additionally the recipient should ensure they are actually virus free. ******************************************************************************** -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: 2011-09-28 FI-WARE IoT Simplified Architecture_v0.1.pptx Type: application/vnd.openxmlformats-officedocument.presentationml.presentation Size: 382351 bytes Desc: 2011-09-28 FI-WARE IoT Simplified Architecture_v0.1.pptx URL: From lorant.farkas at nsn.com Wed Sep 28 12:43:38 2011 From: lorant.farkas at nsn.com (Farkas, Lorant (NSN - HU/Budapest)) Date: Wed, 28 Sep 2011 13:43:38 +0300 Subject: [Fiware-iot] weekly meeting minutes, 28 Sept 2011 Message-ID: <93D28BDF64839C468B848D14227151A2025F4EC8@FIESEXC014.nsn-intra.net> Dear All, Please find the meeting minutes under the following link: https://forge.fi-ware.eu/docman/view.php/11/444/IoT-Minutes-Telco-092820 11.doc Thanks & Br, Lorant -------------- next part -------------- An HTML attachment was scrubbed... URL: From denes.bisztray at nsn.com Wed Sep 28 16:27:07 2011 From: denes.bisztray at nsn.com (Bisztray, Denes (NSN - HU/Budapest)) Date: Wed, 28 Sep 2011 16:27:07 +0200 Subject: [Fiware-iot] user stories and epics summary Message-ID: <3F4C11BC54A36642BFB5875D599F47BD04DF9749@DEMUEXC013.nsn-intra.net> Dear All, I just uploaded a summary of all current user stories and epics here: https://forge.fi-ware.eu/docman/view.php/11/446/User+Stories+Summary.docx Best, D?nes -------------- next part -------------- An HTML attachment was scrubbed... URL: From stephan.haller at sap.com Wed Sep 28 17:56:27 2011 From: stephan.haller at sap.com (Haller, Stephan) Date: Wed, 28 Sep 2011 17:56:27 +0200 Subject: [Fiware-iot] Differences between IoT and IoS Services Message-ID: <0D2446AEB6CAED48BB046223733964A54C40C53DA9@DEWDFECCR01.wdf.sap.corp> All, In today's phone call I promised to send you two links to documents that highlight the differences between IoT Services and "regular" enterprise services as well as how this affects Business Process Modeling. The documents are: 1. S.Haller, C.Magerkurth: "The Real-Time Enterprise: IoT-enabled Business Processes". Position paper at the IETF Interconnecting Smart Objects with the Internet Workshop, Prague, March 2011. http://www.iab.org/wp-content/IAB-uploads/2011/03/Haller.pdf 2. S.Meyer, K.Sperner, C.Magerkurth, J.Pasquier: "Towards Modeling Real-World Aware Business Processes". 2nd International Workshop on the Web of Things (WoT 2011), San Francisco, June 2011. http://www.webofthings.com/wot/2011/papers/Pervasive2011.Workshop09.Paper08.pdf Regards, -Stephan Stephan Haller Development Architect - Internet of Things, SAP Research SAP (Schweiz) AG, Kreuzplatz, Kreuzplatz 20, CH-8008 Z?rich, Switzerland T +41 58 871 78 45, F +41 58 871 78 12 mailto:stephan.haller at sap.com Please consider the impact on the environment before printing this e-mail. -------------- next part -------------- An HTML attachment was scrubbed... URL: From stephan.haller at sap.com Wed Sep 28 18:22:41 2011 From: stephan.haller at sap.com (Haller, Stephan) Date: Wed, 28 Sep 2011 18:22:41 +0200 Subject: [Fiware-iot] Process Automation Message-ID: <0D2446AEB6CAED48BB046223733964A54C40C53E2A@DEWDFECCR01.wdf.sap.corp> All, Please find some additions to the process automation task including a rough description how the assets being developed by IoT-A can cover these. Regards, -Stephan Stephan Haller Development Architect - Internet of Things, SAP Research SAP (Schweiz) AG, Kreuzplatz, Kreuzplatz 20, CH-8008 Z?rich, Switzerland T +41 58 871 78 45, F +41 58 871 78 12 mailto:stephan.haller at sap.com Please consider the impact on the environment before printing this e-mail. -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: PA_arch (2).docx Type: application/vnd.openxmlformats-officedocument.wordprocessingml.document Size: 19789 bytes Desc: PA_arch (2).docx URL: From rheras at tid.es Thu Sep 29 11:59:21 2011 From: rheras at tid.es (Ricardo de las Heras) Date: Thu, 29 Sep 2011 11:59:21 +0200 Subject: [Fiware-iot] Partner assets involved in T5.2 - Resources management - In-Reply-To: <93D28BDF64839C468B848D14227151A2025595EC@FIESEXC014.nsn-intra.net> References: <93D28BDF64839C468B848D14227151A2025594A1@FIESEXC014.nsn-intra.net> <4E7A00CF.3080406@tid.es> <93D28BDF64839C468B848D14227151A2025595EC@FIESEXC014.nsn-intra.net> Message-ID: <4E844179.4020707@tid.es> An HTML attachment was scrubbed... URL: From sabrina.guerra at telecomitalia.it Fri Sep 30 21:57:47 2011 From: sabrina.guerra at telecomitalia.it (Guerra Sabrina) Date: Fri, 30 Sep 2011 21:57:47 +0200 Subject: [Fiware-iot] Partner asset mapping Message-ID: <36A93B31228D3B49B691AD31652BCAE9A5635E2865@GRFMBX702BA020.griffon.local> Hi all, In order to choose the best available asset for each GE we ask you to add the additional information contained in this document: https://forge.fi-ware.eu/docman/view.php/11/448/v18_IoT-Architecture-mapping.xlsx In this file I added a new sheet only for the task 5.1 ?IoT Communication? and if you agree we could proceed, for each functional block, the viewpoints indicating in the following section: ?It would be important to gather information on the asset that belongs to your task. The assets should be analysed from certain viewpoints: - Licensing conditions (open source, closed source) - How mature the software is? Can the asset be used right now, or substantial further development is necessary? - Does it use open standards for collaboration purposes? Can it be easily connected to other assets, or a proprietary ecosystem needs to be mastered by the other stakeholders to connect? - Is it easy to map the various components of the asset onto GEs? What can be done about the unnecessary features?? Best regards, Sabrina Guerra 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.