From rheras at tid.es Thu Dec 1 11:55:10 2011 From: rheras at tid.es (Ricardo de las Heras) Date: Thu, 01 Dec 2011 11:55:10 +0100 Subject: [Fiware-iot] Basic examples OGC- ETSI.M2M Message-ID: <4ED75D0E.1080506@tid.es> An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: OGC-Example-TID.pptx Type: application/vnd.openxmlformats-officedocument.presentationml.presentation Size: 751597 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: ETSI-M2M-Example-TID.pptx Type: application/vnd.openxmlformats-officedocument.presentationml.presentation Size: 553193 bytes Desc: not available URL: From thierry.nagellen at orange.com Thu Dec 1 14:02:42 2011 From: thierry.nagellen at orange.com (thierry.nagellen at orange.com) Date: Thu, 1 Dec 2011 14:02:42 +0100 Subject: [Fiware-iot] Basic examples OGC- ETSI.M2M In-Reply-To: <4ED75D0E.1080506@tid.es> References: <4ED75D0E.1080506@tid.es> Message-ID: Hi all, Some comments about our decisions and next steps : 1 - Based on the collective work done in October we have decided to use for the time being OMA-NGSI and ETSI M2M for northbound and southbound API and to establish relationships with OGC but also with IoT-A and ETSI M2M to evaluate further improvements 2 - We are working on Future Internet and it is not so risky to choose ETSI M2M based on ETSI M2M community which is very large and because this community has reached a first stable version of technical specifications. 3 - Focusing today on OGC should be also a bad signal for UC projects which are not using OGC but some other standards. Typically, the existing structure in OGC is like the EPC Global structure and the 3 related projects would not adopt our GE if we have to encapsulate EPC in OGC, and this is the same concern for ONVIF regarding OGC. We have to provide an agnostic approach regarding existing standards. 4 - OMA-NGSI provides a very high level description and we have to explain/comment this description to find a generic format valuable for all the other standards description (OGC, ONVIF, EPC...) which will provide this agnostic layer. 5 - Some partners interested in some dedicated standards have to demonstrate, through NGSI and ETSI M2M implementation that the related standards could provide advanced features and and could propose NGSI and ETSI M2M improvements. 6 - In the same way, we could push improvements to the other standards for dedicated issues as security or nomadic things So at the end of November, we have to define these NGSI details (so provide your feedback regarding your knowledge in several standards) and to implement the first functions for ETSI M2M on the selected assets as provided by the task leaders. BR Thierry De : fiware-iot-bounces at lists.fi-ware.eu [mailto:fiware-iot-bounces at lists.fi-ware.eu] De la part de Ricardo de las Heras Envoy? : jeudi 1 d?cembre 2011 11:55 ? : fiware-iot at lists.fi-ware.eu Objet : [Fiware-iot] Basic examples OGC- ETSI.M2M Dear partners, as we agreed in the last conf. call, TID have prepared some examples about how we use the OGC standard (SensorML+ O&M) within the IDAS platform. Additionally I attach you a simple example about how the ETSI standard could work as a container of an OGC descriptive XML document, but this option is not implemented yet in the IDAS platform, although we are considering to include it in the medium-long term roadmap. Our main concert in this way is about how the industry will accept it, at this time we don't know any sensor/device ETSI compliant manufacturer, this is a critical point for the final success of the ETSI standard, so at present I think this would be a risky bet. Please provide any type of additional information you have about this issue. thanks, best regards, RHer at s. -- ------------------------------------- Ricardo de las Heras M2M Research Technological Specialist E-mail: rheras at tid.es Phone1: (+34) 983 367625 Phone2 OCS: (+34) 91 31 29511 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 Fri Dec 2 14:26:54 2011 From: lorant.farkas at nsn.com (Farkas, Lorant (NSN - HU/Budapest)) Date: Fri, 2 Dec 2011 15:26:54 +0200 Subject: [Fiware-iot] Work item status Message-ID: <93D28BDF64839C468B848D14227151A202B1874D@FIESEXC014.nsn-intra.net> Dear Ricardo, Can you update the status of the 2 work items belonging to you? https://forge.fi-ware.eu/tracker/index.php?func=detail&aid=960&group_id=11&atid=193 - was there any progress with the asset selection? Whom are you discussing this with currently and what is the status? https://forge.fi-ware.eu/tracker/index.php?func=detail&aid=959&group_id=11&atid=193 - was there any progress for the directory interface definition? In my view (see new arch figure from D?nes): <> -there should be activity dealing with NGSI-based thing level API, dealt with by Tobias (https://forge.fi-ware.eu/tracker/index.php?func=detail&aid=964&group_id=11&atid=193) - therefore this work item does not contain that part, the progress should not be marked here -there should be activity dealing with the interface between template handler and directory handler - this is between TID and SAP - the progress on this should be marked Thanks & Br, Lorant -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: ole0.bmp Type: image/bmp Size: 774054 bytes Desc: Picture (Enhanced Metafile) URL: From denes.bisztray at nsn.com Tue Dec 6 14:48:38 2011 From: denes.bisztray at nsn.com (Bisztray, Denes (NSN - HU/Budapest)) Date: Tue, 6 Dec 2011 14:48:38 +0100 Subject: [Fiware-iot] gateway architecture Message-ID: <3F4C11BC54A36642BFB5875D599F47BD053E0124@DEMUEXC013.nsn-intra.net> Dear all, Although the asset selection is still questionably finished, it would good to clarify the architecture around the gateways as well as the internal APIs. 1. Where do we have the gateway functionality? (i.e. microDB, instantaneous and real-time data, data aggregation filter, etc. ) - every asset implements the gateway functionality on its own, and provides an API that the gateway-northbound interface and application implementation can harness. - the assets only do protocol adaptation, the gateway functionality comes from outside (possibly one of the assetes) 2. We need to provide two interfaces within a gateway. One is the ETSI M2M interface that communicates with the backend, and another interface for the application layer within the gateway. How will they communicate with the assets? 3. Backend API problems. The IDAS which seems to be selected for all GEs within resources management (is it?). It needs to have an internal interface for communicating with both the northbound and southbound interface. When will it be public? Or have a service bus? This one needs to be worked out. 4. Who implements the ETSI M2M interfaces? Best, D?nes -------------- next part -------------- A non-text attachment was scrubbed... Name: Gateway Architecture.pptx Type: application/octet-stream Size: 78645 bytes Desc: Gateway Architecture.pptx URL: From stephan.haller at sap.com Tue Dec 6 18:00:38 2011 From: stephan.haller at sap.com (Haller, Stephan) Date: Tue, 6 Dec 2011 18:00:38 +0100 Subject: [Fiware-iot] Implementation of NGSI Interfaces Message-ID: <0D2446AEB6CAED48BB046223733964A54C4903E376@DEWDFECCR01.wdf.sap.corp> All, As indicated in my earlier mails, I support to have several implementations of NGSI interface around the different assets. Also, in order to do component as well as interoperability testing, we need a test-client as well as test cases, as summarized in the attached slide. As the SENSEI assets were not selected, but in order to still provide something useful to the project, we would focus on the test client and the test cases (while also implementing a wrapper for the SENSEI Entity Directory for internal testing). We can discuss in the call tomorrow. [cid:image001.png at 01CCB440.F5B46A50] Regards, -Stephan Stephan Haller Development Architect - Internet of Things, SAP Research SAP (Schweiz) AG, 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: image001.png Type: image/png Size: 22394 bytes Desc: image001.png URL: From T.Elsaleh at surrey.ac.uk Tue Dec 6 18:33:49 2011 From: T.Elsaleh at surrey.ac.uk (T.Elsaleh at surrey.ac.uk) Date: Tue, 6 Dec 2011 17:33:49 +0000 Subject: [Fiware-iot] Basic examples OGC- ETSI.M2M In-Reply-To: References: <4ED75D0E.1080506@tid.es> Message-ID: <2AAC0B6FF99A064C853BFB1C9295F3CCA58AA54558@EXMB05CMS.surrey.ac.uk> Hello All, I would like to describe the asset proposed by UniS and the activities we are currently conducting. We are working on developing an RDF representation of OMA-NGSI for IoT entities and resources. This will be done according to the information models that we have developed for the IoTA project. The following is a list of the planned and ongoing activities: ? Creating entity/resource templates in RDF format based on OMA-NGSI representation. ? Providing a repository for the RDF data based on our Linked Sensor Data Platform. ? Developing RESTful interfaces for publish/access/query ? Supporting SPARQL query over the representations ? We can also work with other partners to demonstrate mapping with other description models e.g. SensorML, by annotating SensorML using OMA-NGSI based RDF data. Please let us know if you have any concerns and comments. Best regards, Tarek Elsaleh Research Assistant Department of Electronic Engineering University of Surrey Guildford, GU2 7XH Tel: 01483 689485 From: fiware-iot-bounces at lists.fi-ware.eu [mailto:fiware-iot-bounces at lists.fi-ware.eu] On Behalf Of thierry.nagellen at orange.com Sent: 01 December 2011 13:03 To: rheras at tid.es; fiware-iot at lists.fi-ware.eu Subject: Re: [Fiware-iot] Basic examples OGC- ETSI.M2M Hi all, Some comments about our decisions and next steps : 1 - Based on the collective work done in October we have decided to use for the time being OMA-NGSI and ETSI M2M for northbound and southbound API and to establish relationships with OGC but also with IoT-A and ETSI M2M to evaluate further improvements 2 - We are working on Future Internet and it is not so risky to choose ETSI M2M based on ETSI M2M community which is very large and because this community has reached a first stable version of technical specifications. 3 - Focusing today on OGC should be also a bad signal for UC projects which are not using OGC but some other standards. Typically, the existing structure in OGC is like the EPC Global structure and the 3 related projects would not adopt our GE if we have to encapsulate EPC in OGC, and this is the same concern for ONVIF regarding OGC. We have to provide an agnostic approach regarding existing standards. 4 - OMA-NGSI provides a very high level description and we have to explain/comment this description to find a generic format valuable for all the other standards description (OGC, ONVIF, EPC...) which will provide this agnostic layer. 5 - Some partners interested in some dedicated standards have to demonstrate, through NGSI and ETSI M2M implementation that the related standards could provide advanced features and and could propose NGSI and ETSI M2M improvements. 6 - In the same way, we could push improvements to the other standards for dedicated issues as security or nomadic things So at the end of November, we have to define these NGSI details (so provide your feedback regarding your knowledge in several standards) and to implement the first functions for ETSI M2M on the selected assets as provided by the task leaders. BR Thierry De : fiware-iot-bounces at lists.fi-ware.eu [mailto:fiware-iot-bounces at lists.fi-ware.eu] De la part de Ricardo de las Heras Envoy? : jeudi 1 d?cembre 2011 11:55 ? : fiware-iot at lists.fi-ware.eu Objet : [Fiware-iot] Basic examples OGC- ETSI.M2M Dear partners, as we agreed in the last conf. call, TID have prepared some examples about how we use the OGC standard (SensorML+ O&M) within the IDAS platform. Additionally I attach you a simple example about how the ETSI standard could work as a container of an OGC descriptive XML document, but this option is not implemented yet in the IDAS platform, although we are considering to include it in the medium-long term roadmap. Our main concert in this way is about how the industry will accept it, at this time we don't know any sensor/device ETSI compliant manufacturer, this is a critical point for the final success of the ETSI standard, so at present I think this would be a risky bet. Please provide any type of additional information you have about this issue. thanks, best regards, RHer at s. -- ------------------------------------- Ricardo de las Heras M2M Research Technological Specialist E-mail: rheras at tid.es Phone1: (+34) 983 367625 Phone2 OCS: (+34) 91 31 29511 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 ________________________________ No virus found in this message. Checked by AVG - www.avg.com Version: 2012.0.1873 / Virus Database: 2102/4650 - Release Date: 12/01/11 -------------- next part -------------- An HTML attachment was scrubbed... URL: From rheras at tid.es Wed Dec 7 07:42:36 2011 From: rheras at tid.es (Ricardo de las Heras) Date: Wed, 07 Dec 2011 07:42:36 +0100 Subject: [Fiware-iot] Work item status In-Reply-To: <93D28BDF64839C468B848D14227151A202B1874D@FIESEXC014.nsn-intra.net> References: <93D28BDF64839C468B848D14227151A202B1874D@FIESEXC014.nsn-intra.net> Message-ID: <4EDF0ADC.1040809@tid.es> An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: image/bmp Size: 774054 bytes Desc: not available URL: From lorant.farkas at nsn.com Wed Dec 7 09:16:07 2011 From: lorant.farkas at nsn.com (Farkas, Lorant (NSN - HU/Budapest)) Date: Wed, 7 Dec 2011 10:16:07 +0200 Subject: [Fiware-iot] IoT weekly meeting Message-ID: <93D28BDF64839C468B848D14227151A202B19448@FIESEXC014.nsn-intra.net> When: 2011. december 7. 10:00-11:30 (GMT+01:00) Belgrade, Bratislava, Budapest, Ljubljana, Prague. Where: telco/webex Note: The GMT offset above does not reflect daylight saving time adjustments. *~*~*~*~*~*~*~*~*~* Dear All, We propose the following agenda for today: 1. Progress on the NGSI work item 2. Status on the Ericsson discussion on their asset 3. D?nes' topic: what is a gateway + architecture figure 4. GE interface specifications - we should start doing this, ownership by task leaders 5. Update on asset selection status per task - task leaders On our side only D?nes will participate, I am caught in a customer meeting unfortunately. Minutes taker volunteers are welcome, if noone, then D?nes will take the minutes. 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: 11095 bytes Desc: not available URL: From sabrina.guerra at telecomitalia.it Wed Dec 7 09:35:32 2011 From: sabrina.guerra at telecomitalia.it (Guerra Sabrina) Date: Wed, 7 Dec 2011 09:35:32 +0100 Subject: [Fiware-iot] R: IoT weekly meeting In-Reply-To: <93D28BDF64839C468B848D14227151A202B19448@FIESEXC014.nsn-intra.net> References: <93D28BDF64839C468B848D14227151A202B19448@FIESEXC014.nsn-intra.net> Message-ID: <36A93B31228D3B49B691AD31652BCAE9A564DDA5CB@GRFMBX702BA020.griffon.local> Hi, today we're forced to skip the IoT weekly meeting because we're busy due to other work meetings. 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, December 07, 2011 9:16 AM A: fiware-iot at lists.fi-ware.eu Oggetto: [Fiware-iot] IoT weekly meeting When: 2011. december 7. 10:00-11:30 (GMT+01:00) Belgrade, Bratislava, Budapest, Ljubljana, Prague. Where: telco/webex Note: The GMT offset above does not reflect daylight saving time adjustments. *~*~*~*~*~*~*~*~*~* Dear All, We propose the following agenda for today: 1. Progress on the NGSI work item 2. Status on the Ericsson discussion on their asset 3. D?nes' topic: what is a gateway + architecture figure 4. GE interface specifications - we should start doing this, ownership by task leaders 5. Update on asset selection status per task - task leaders On our side only D?nes will participate, I am caught in a customer meeting unfortunately. Minutes taker volunteers are welcome, if noone, then D?nes will take the minutes. 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 P.Barnaghi at surrey.ac.uk Wed Dec 7 10:04:14 2011 From: P.Barnaghi at surrey.ac.uk (P.Barnaghi at surrey.ac.uk) Date: Wed, 7 Dec 2011 09:04:14 +0000 Subject: [Fiware-iot] IoT weekly meeting In-Reply-To: <36A93B31228D3B49B691AD31652BCAE9A564DDA5CB@GRFMBX702BA020.griffon.local> References: <93D28BDF64839C468B848D14227151A202B19448@FIESEXC014.nsn-intra.net> <36A93B31228D3B49B691AD31652BCAE9A564DDA5CB@GRFMBX702BA020.griffon.local> Message-ID: Hi, sorry; I won't be also able to join today. Best regards, Payam ________________________________ From: fiware-iot-bounces at lists.fi-ware.eu [mailto:fiware-iot-bounces at lists.fi-ware.eu] On Behalf Of Guerra Sabrina Sent: 07 December 2011 08:36 To: 'Farkas, Lorant (NSN - HU/Budapest)' Cc: 'fiware-iot at lists.fi-ware.eu' Subject: [Fiware-iot] R: IoT weekly meeting Hi, today we're forced to skip the IoT weekly meeting because we're busy due to other work meetings. 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, December 07, 2011 9:16 AM A: fiware-iot at lists.fi-ware.eu Oggetto: [Fiware-iot] IoT weekly meeting When: 2011. december 7. 10:00-11:30 (GMT+01:00) Belgrade, Bratislava, Budapest, Ljubljana, Prague. Where: telco/webex Note: The GMT offset above does not reflect daylight saving time adjustments. *~*~*~*~*~*~*~*~*~* Dear All, We propose the following agenda for today: 1. Progress on the NGSI work item 2. Status on the Ericsson discussion on their asset 3. D?nes' topic: what is a gateway + architecture figure 4. GE interface specifications - we should start doing this, ownership by task leaders 5. Update on asset selection status per task - task leaders On our side only D?nes will participate, I am caught in a customer meeting unfortunately. Minutes taker volunteers are welcome, if noone, then D?nes will take the minutes. 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:image001.gif at 01CCB4BF.31480B20]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 jhierro at tid.es Wed Dec 7 10:58:12 2011 From: jhierro at tid.es (Juanjo Hierro) Date: Wed, 07 Dec 2011 10:58:12 +0100 Subject: [Fiware-iot] Basic examples OGC- ETSI.M2M In-Reply-To: <2AAC0B6FF99A064C853BFB1C9295F3CCA58AA54558@EXMB05CMS.surrey.ac.uk> References: <4ED75D0E.1080506@tid.es> <2AAC0B6FF99A064C853BFB1C9295F3CCA58AA54558@EXMB05CMS.surrey.ac.uk> Message-ID: <4EDF38B4.4080202@tid.es> Hi Tarek, The partners involved in development of the Publish/Subscribe Broker GE within the Data/Context Management chapter (Telecom Italia and Orange) are trying to deal with incorporation of semantic meta-data linked to events (context elements) and published through the Publish/Subscribe Broker GE. I copy Boris Moltchanov from Telecom Italia who is dealing with coordination of the developments linked to this GE. While I guess that having two implementations of the NGSI spec may be Ok (though we have to find out how to justify it) what certainly has to be achieved is that the final APIs finally offered to the application developer are the same, so that applications are not programmed in a different way depending on what Publish/Subscriber Broker GE it connects to. And this doesn't only affect number and name of operations but structure of data (which certainly affects the signature of operations). I would suggest that we setup a dedicated thread of discussion over the email where each can explain its respective approach and we can reach the necessary alignment. Would you believe that we should link that thread of discussion through both the fiware-data and fiware-iot mailing lists ? I guess not all members in that list want to get spammed ;-) My current thinking would be that of creating a dedicated mailing list for discussion about the NGSI interface implementation were partners involved in trying to implement this interface in both the FI-WARE IoT and FI-WARE Data chapters would be members, besides the respective WPLs, WPAs, the deputy chief architect of FI-WARE and myself. Your feedback is welcome. Best regards, -- Juanjo On 06/12/11 18:33, T.Elsaleh at surrey.ac.uk wrote: Hello All, I would like to describe the asset proposed by UniS and the activities we are currently conducting. We are working on developing an RDF representation of OMA-NGSI for IoT entities and resources. This will be done according to the information models that we have developed for the IoTA project. The following is a list of the planned and ongoing activities: ? Creating entity/resource templates in RDF format based on OMA-NGSI representation. ? Providing a repository for the RDF data based on our Linked Sensor Data Platform. ? Developing RESTful interfaces for publish/access/query ? Supporting SPARQL query over the representations ? We can also work with other partners to demonstrate mapping with other description models e.g. SensorML, by annotating SensorML using OMA-NGSI based RDF data. Please let us know if you have any concerns and comments. Best regards, Tarek Elsaleh Research Assistant Department of Electronic Engineering University of Surrey Guildford, GU2 7XH Tel: 01483 689485 From: fiware-iot-bounces at lists.fi-ware.eu [mailto:fiware-iot-bounces at lists.fi-ware.eu] On Behalf Of thierry.nagellen at orange.com Sent: 01 December 2011 13:03 To: rheras at tid.es; fiware-iot at lists.fi-ware.eu Subject: Re: [Fiware-iot] Basic examples OGC- ETSI.M2M Hi all, Some comments about our decisions and next steps : 1 ? Based on the collective work done in October we have decided to use for the time being OMA-NGSI and ETSI M2M for northbound and southbound API and to establish relationships with OGC but also with IoT-A and ETSI M2M to evaluate further improvements 2 ? We are working on Future Internet and it is not so risky to choose ETSI M2M based on ETSI M2M community which is very large and because this community has reached a first stable version of technical specifications. 3 ? Focusing today on OGC should be also a bad signal for UC projects which are not using OGC but some other standards. Typically, the existing structure in OGC is like the EPC Global structure and the 3 related projects would not adopt our GE if we have to encapsulate EPC in OGC, and this is the same concern for ONVIF regarding OGC. We have to provide an agnostic approach regarding existing standards. 4 ? OMA-NGSI provides a very high level description and we have to explain/comment this description to find a generic format valuable for all the other standards description (OGC, ONVIF, EPC?) which will provide this agnostic layer. 5 ? Some partners interested in some dedicated standards have to demonstrate, through NGSI and ETSI M2M implementation that the related standards could provide advanced features and and could propose NGSI and ETSI M2M improvements. 6 - In the same way, we could push improvements to the other standards for dedicated issues as security or nomadic things So at the end of November, we have to define these NGSI details (so provide your feedback regarding your knowledge in several standards) and to implement the first functions for ETSI M2M on the selected assets as provided by the task leaders. BR Thierry De : fiware-iot-bounces at lists.fi-ware.eu [mailto:fiware-iot-bounces at lists.fi-ware.eu] De la part de Ricardo de las Heras Envoy? : jeudi 1 d?cembre 2011 11:55 ? : fiware-iot at lists.fi-ware.eu Objet : [Fiware-iot] Basic examples OGC- ETSI.M2M Dear partners, as we agreed in the last conf. call, TID have prepared some examples about how we use the OGC standard (SensorML+ O&M) within the IDAS platform. Additionally I attach you a simple example about how the ETSI standard could work as a container of an OGC descriptive XML document, but this option is not implemented yet in the IDAS platform, although we are considering to include it in the medium-long term roadmap. Our main concert in this way is about how the industry will accept it, at this time we don't know any sensor/device ETSI compliant manufacturer, this is a critical point for the final success of the ETSI standard, so at present I think this would be a risky bet. Please provide any type of additional information you have about this issue. thanks, best regards, RHer at s. -- ------------------------------------- Ricardo de las Heras M2M Research Technological Specialist E-mail: rheras at tid.es Phone1: (+34) 983 367625 Phone2 OCS: (+34) 91 31 29511 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 ________________________________ No virus found in this message. Checked by AVG - www.avg.com Version: 2012.0.1873 / Virus Database: 2102/4650 - Release Date: 12/01/11 ________________________________ Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra pol?tica de env?o y recepci?n de correo electr?nico en el enlace situado m?s abajo. This message is intended exclusively for its addressee. We only send and receive email on the basis of the terms set out at. http://www.tid.es/ES/PAGINAS/disclaimer.aspx -------------- next part -------------- An HTML attachment was scrubbed... URL: From denes.bisztray at nsn.com Wed Dec 7 13:00:45 2011 From: denes.bisztray at nsn.com (Bisztray, Denes (NSN - HU/Budapest)) Date: Wed, 7 Dec 2011 13:00:45 +0100 Subject: [Fiware-iot] IoT Weekly Meeting Minutes - 07/12/2011 Message-ID: <3F4C11BC54A36642BFB5875D599F47BD053E0732@DEMUEXC013.nsn-intra.net> Dear All, Under this link please find the minutes from this week. https://forge.fi-ware.eu/docman/view.php/11/673/IoT-Minutes-Telco-07122011.docx Best, D?nes From rheras at tid.es Fri Dec 9 17:03:14 2011 From: rheras at tid.es (Ricardo de las Heras) Date: Fri, 09 Dec 2011 17:03:14 +0100 Subject: [Fiware-iot] gateway architecture In-Reply-To: <3F4C11BC54A36642BFB5875D599F47BD053E0124@DEMUEXC013.nsn-intra.net> References: <3F4C11BC54A36642BFB5875D599F47BD053E0124@DEMUEXC013.nsn-intra.net> Message-ID: <4EE23142.7060109@tid.es> An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: Arquit_Bloques_func-IDAS.jpg Type: image/jpeg Size: 264652 bytes Desc: not available URL: From Martin.Bauer at neclab.eu Fri Dec 9 17:33:37 2011 From: Martin.Bauer at neclab.eu (Martin Bauer) Date: Fri, 9 Dec 2011 16:33:37 +0000 Subject: [Fiware-iot] gateway architecture In-Reply-To: <3F4C11BC54A36642BFB5875D599F47BD053E0124@DEMUEXC013.nsn-intra.net> References: <3F4C11BC54A36642BFB5875D599F47BD053E0124@DEMUEXC013.nsn-intra.net> Message-ID: Hi Denes, all, > 3. Backend API problems. The IDAS which seems to be selected for all GEs within resources management (is it?). Our working assumption is that for the "Discovery and Resolution of Things GE", (our) IoT-A assets are selected. We need these assets when implementing the NGSI-level interface in T5.4. As far as I know IDAS currently does not have the required functionality. 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 -----Original Message----- From: fiware-iot-bounces at lists.fi-ware.eu [mailto:fiware-iot-bounces at lists.fi-ware.eu] On Behalf Of Bisztray, Denes (NSN - HU/Budapest) Sent: Dienstag, 6. Dezember 2011 14:49 To: fiware-iot at lists.fi-ware.eu Subject: [Fiware-iot] gateway architecture Dear all, Although the asset selection is still questionably finished, it would good to clarify the architecture around the gateways as well as the internal APIs. 1. Where do we have the gateway functionality? (i.e. microDB, instantaneous and real-time data, data aggregation filter, etc. ) - every asset implements the gateway functionality on its own, and provides an API that the gateway-northbound interface and application implementation can harness. - the assets only do protocol adaptation, the gateway functionality comes from outside (possibly one of the assetes) 2. We need to provide two interfaces within a gateway. One is the ETSI M2M interface that communicates with the backend, and another interface for the application layer within the gateway. How will they communicate with the assets? 3. Backend API problems. The IDAS which seems to be selected for all GEs within resources management (is it?). It needs to have an internal interface for communicating with both the northbound and southbound interface. When will it be public? Or have a service bus? This one needs to be worked out. 4. Who implements the ETSI M2M interfaces? Best, D?nes From denes.bisztray at nsn.com Mon Dec 12 08:22:39 2011 From: denes.bisztray at nsn.com (Bisztray, Denes (NSN - HU/Budapest)) Date: Mon, 12 Dec 2011 08:22:39 +0100 Subject: [Fiware-iot] gateway architecture In-Reply-To: <4EE23142.7060109@tid.es> References: <3F4C11BC54A36642BFB5875D599F47BD053E0124@DEMUEXC013.nsn-intra.net> <4EE23142.7060109@tid.es> Message-ID: <3F4C11BC54A36642BFB5875D599F47BD0541EAF0@DEMUEXC013.nsn-intra.net> Hi Ricardo, Sorry for mixing up the order, but it makes more sense this way: 2) We assume to have an application layer within the gateway as well as the device itself, not just at the backend-level. In order to have applications on the gateway, we need to have an interface for that. This is the functionality that IDAS seems to lack (at least as far as I understood). And OGC SWE altogether. 1)This seems problematic. You support only OGC SWE functionality, i.e. sensor measurement gathering and sensor tasking. When asked on the weekly IoT meeting you said IDAS supports the buffering of sensorial data in an offline case. But if we look back at the previous point, this is far from satisfactory, an autonomous application layer on the gateway would be necessary. 3) What are these interface capable of? Best, D?nes From: ext Ricardo de las Heras [mailto:rheras at tid.es] Sent: Friday, December 09, 2011 5:03 PM To: Bisztray, Denes (NSN - HU/Budapest) Cc: fiware-iot at lists.fi-ware.eu; gianpiero.fici at telecomitalia.it; sabrina.guerra at telecomitalia.it; thierry.nagellen at orange.com Subject: Re: gateway architecture Dear D?nes, interesting questions here, in our case from IDAS: 1) Tthe gateways provides translation capabilities from the broad range of protocols, unifying them to a SensorAPI (OGC SensorML + O&M). I attach you a picture with this concept. So the gateway is out of the platform. 2) I don't understand your exposition, why you speak about an interface between the Gateway and the application layer? I don't agree this interface. 3) Yes, we have interfaces from IDAS to the botton layers (Gateway) and with the upper layers (applications). Interfaces are public of course. 4) Good question, indeed I had already made this question. From my point of view that would be the T5.1 scope, isn't it? Are you asking about name of partners too:) ? have a nice weekend, RHer at s. Bisztray, Denes (NSN - HU/Budapest) wrote: Dear all, Although the asset selection is still questionably finished, it would good to clarify the architecture around the gateways as well as the internal APIs. 1. Where do we have the gateway functionality? (i.e. microDB, instantaneous and real-time data, data aggregation filter, etc. ) - every asset implements the gateway functionality on its own, and provides an API that the gateway-northbound interface and application implementation can harness. - the assets only do protocol adaptation, the gateway functionality comes from outside (possibly one of the assetes) 2. We need to provide two interfaces within a gateway. One is the ETSI M2M interface that communicates with the backend, and another interface for the application layer within the gateway. How will they communicate with the assets? 3. Backend API problems. The IDAS which seems to be selected for all GEs within resources management (is it?). It needs to have an internal interface for communicating with both the northbound and southbound interface. When will it be public? Or have a service bus? This one needs to be worked out. 4. Who implements the ETSI M2M interfaces? Best, D?nes -- ------------------------------------- Ricardo de las Heras M2M Research Technological Specialist E-mail: rheras at tid.es Phone1: (+34) 983 367625 Phone2 OCS: (+34) 91 31 29511 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 denes.bisztray at nsn.com Mon Dec 12 08:24:42 2011 From: denes.bisztray at nsn.com (Bisztray, Denes (NSN - HU/Budapest)) Date: Mon, 12 Dec 2011 08:24:42 +0100 Subject: [Fiware-iot] gateway architecture In-Reply-To: References: <3F4C11BC54A36642BFB5875D599F47BD053E0124@DEMUEXC013.nsn-intra.net> Message-ID: <3F4C11BC54A36642BFB5875D599F47BD0541EAF6@DEMUEXC013.nsn-intra.net> Hi Martin, Ricardo, Ricardo: can you confirm this? (i.e. IoT-A is responsible for the Discovery and Resolution of Things) Best, D?nes -----Original Message----- From: ext Martin Bauer [mailto:Martin.Bauer at neclab.eu] Sent: Friday, December 09, 2011 5:34 PM To: Bisztray, Denes (NSN - HU/Budapest); fiware-iot at lists.fi-ware.eu Subject: RE: gateway architecture Hi Denes, all, > 3. Backend API problems. The IDAS which seems to be selected for all GEs within resources management (is it?). Our working assumption is that for the "Discovery and Resolution of Things GE", (our) IoT-A assets are selected. We need these assets when implementing the NGSI-level interface in T5.4. As far as I know IDAS currently does not have the required functionality. 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 -----Original Message----- From: fiware-iot-bounces at lists.fi-ware.eu [mailto:fiware-iot-bounces at lists.fi-ware.eu] On Behalf Of Bisztray, Denes (NSN - HU/Budapest) Sent: Dienstag, 6. Dezember 2011 14:49 To: fiware-iot at lists.fi-ware.eu Subject: [Fiware-iot] gateway architecture Dear all, Although the asset selection is still questionably finished, it would good to clarify the architecture around the gateways as well as the internal APIs. 1. Where do we have the gateway functionality? (i.e. microDB, instantaneous and real-time data, data aggregation filter, etc. ) - every asset implements the gateway functionality on its own, and provides an API that the gateway-northbound interface and application implementation can harness. - the assets only do protocol adaptation, the gateway functionality comes from outside (possibly one of the assetes) 2. We need to provide two interfaces within a gateway. One is the ETSI M2M interface that communicates with the backend, and another interface for the application layer within the gateway. How will they communicate with the assets? 3. Backend API problems. The IDAS which seems to be selected for all GEs within resources management (is it?). It needs to have an internal interface for communicating with both the northbound and southbound interface. When will it be public? Or have a service bus? This one needs to be worked out. 4. Who implements the ETSI M2M interfaces? Best, D?nes From rheras at tid.es Mon Dec 12 12:20:59 2011 From: rheras at tid.es (Ricardo de las Heras) Date: Mon, 12 Dec 2011 12:20:59 +0100 Subject: [Fiware-iot] gateway architecture In-Reply-To: <3F4C11BC54A36642BFB5875D599F47BD0541EAF0@DEMUEXC013.nsn-intra.net> References: <3F4C11BC54A36642BFB5875D599F47BD053E0124@DEMUEXC013.nsn-intra.net> <4EE23142.7060109@tid.es> <3F4C11BC54A36642BFB5875D599F47BD0541EAF0@DEMUEXC013.nsn-intra.net> Message-ID: <4EE5E39B.3050301@tid.es> An HTML attachment was scrubbed... URL: From P.Barnaghi at surrey.ac.uk Mon Dec 12 12:53:12 2011 From: P.Barnaghi at surrey.ac.uk (P.Barnaghi at surrey.ac.uk) Date: Mon, 12 Dec 2011 11:53:12 +0000 Subject: [Fiware-iot] gateway architecture In-Reply-To: <4EE5E39B.3050301@tid.es> References: <3F4C11BC54A36642BFB5875D599F47BD053E0124@DEMUEXC013.nsn-intra.net> <4EE23142.7060109@tid.es> <3F4C11BC54A36642BFB5875D599F47BD0541EAF0@DEMUEXC013.nsn-intra.net> <4EE5E39B.3050301@tid.es> Message-ID: Hi all, My reply is only related to the last part of Ricardo's email: Discovery and Resolution of Things from IOT-A. We are involved in this task in IoT-A and I would like to add some clarifications to this: Discovery and Resolution of Things in IoT-A is planned based on the proposed information model for entities and resources in IoT-A. The entity and resource descriptions are in RDF format and are represented according to the IoT-A model. A software agent parses these descriptions and extracts the information for indexing. A machine learning method then applies probabilistic machine learning based on LDA approach to create a low-dimensional specification of data that is transformed in vector-space model and similarities are measured based on a vector similarity measure between query vector (again encoded using a similar method) and transformed descriptions. However, if the resources are stored and/or represented differently with different format and different set of attributes, the parser won't be able to extract the required information and I am also not sure even adapting a new parser could still help extracting the required features. The repository and description format will also affect this. Again, this is related to the work that we do in IoT-A discovery and perhaps other IoT-A partners can provide more information. Thanks, 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: 12 December 2011 11:21 To: Bisztray, Denes (NSN - HU/Budapest) Cc: fiware-iot at lists.fi-ware.eu Subject: Re: [Fiware-iot] gateway architecture HI D?nes, 2) I don't understand why we assume to have an application layer within the gateway, of course it is feasible if you increase the complexity of it, for us in Telef?nica it is out of the scope of our platform IDAS and so far we don't have any type of requirement that implies these type of decisions, so that's the main reason. And in this way you know our platform is for example included at this time in several important projects like SmartSantander. You referenced too in the last call the possibility of providing direct communication at the Gateway level between resources. From my point of view this is the same thing, you can even include a more complex HUB (device's concentrator, as previous step to the gateway) and to manage everything there. But for example maybe you should have to manage different protocols, different standards, security issues, etc. that obviously increase the complexity and costs of those elements. 1) We support any type of sensor measurement technology and underlying communication protocols, but obviously we unify them to a common language at the gateway level, and this is the well known OGC, currently well supported by the IoT community. 3) Basically as I have already explained: a data format adaptation: to translate device specific Messages into SensorML-based Messages and vice versa. This provides an abstraction level to the platform making it suitable for integrating different sensor technologies. So, an especific adaptor module is needed for including new protocols. And second: Also it allows sending commands to Actuators. Finally, answering you to another email, YES, IoT-A is responsible for the Discovery and Resolution of Things. Anyway, if you have any other question or additional clarification please let me know, thanks, best, RHer at s. Bisztray, Denes (NSN - HU/Budapest) wrote: Hi Ricardo, ? Sorry for mixing up the order, but it makes more sense this way: ? 2) We assume to have an application layer within the gateway as well as the device itself, not just at the backend-level. In order to have applications on the gateway, we need to have an interface for that. This is the functionality that IDAS seems to lack (at least as far as I understood). And OGC SWE altogether. ? 1)This seems problematic. You support only OGC SWE functionality, i.e. sensor measurement gathering and sensor tasking. When asked on the weekly IoT meeting you said IDAS supports the buffering of sensorial data in an offline case. But if we look back at the previous point, this is far from satisfactory, an autonomous application layer on the gateway would be necessary. ? 3) What are these interface capable of? ? Best, D?nes ? From: ext Ricardo de las Heras [mailto:rheras at tid.es] Sent: Friday, December 09, 2011 5:03 PM To: Bisztray, Denes (NSN - HU/Budapest) Cc: fiware-iot at lists.fi-ware.eu; gianpiero.fici at telecomitalia.it; sabrina.guerra at telecomitalia.it; thierry.nagellen at orange.com Subject: Re: gateway architecture ? Dear D?nes, interesting questions here, in our case from IDAS: 1) Tthe gateways provides translation capabilities from the broad range of protocols, unifying them to a SensorAPI (OGC SensorML + O&M). I attach you a picture with this concept. So the gateway is out of the platform. 2) I don't understand your exposition, why you speak about an interface between the Gateway and the application layer? I don't agree this interface. 3) Yes, we have interfaces from IDAS to the botton layers (Gateway) and with the upper layers (applications). Interfaces are public of course. 4)? Good question, indeed I had already made this question. From my point of view that would be the T5.1 scope, isn't it? Are you asking about name of partners too:) ? have a nice weekend, RHer at s. Bisztray, Denes (NSN - HU/Budapest) wrote: Dear all, ? Although the asset selection is still questionably finished, it would good to clarify the architecture around the gateways as well as the internal APIs. ? 1. Where do we have the gateway functionality?? (i.e. microDB, instantaneous and real-time data, data aggregation filter, etc. ) ??????? - every asset implements the gateway functionality on its own, and provides an API that the gateway-northbound interface and application implementation can harness. ? ??????? - the assets only do protocol adaptation, the gateway functionality comes from outside (possibly one of the assetes) ? 2. We need to provide two interfaces within a gateway. One is the ETSI M2M interface that communicates with the backend, and another interface for the application layer within the gateway. How will they communicate with the assets? ? 3. Backend API problems. The IDAS which seems to be selected for all GEs within resources management (is it?). It needs to have an internal interface for communicating with both the northbound and southbound interface. When will it be public? Or have a service bus? This one needs to be worked out. ? 4. Who implements the ETSI M2M interfaces? ? Best, D?nes ? -- ------------------------------------- Ricardo de las Heras M2M Research Technological Specialist E-mail: rheras at tid.es Phone1: (+34) 983 367625 Phone2 OCS: (+34) 91 31 29511 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 -- ------------------------------------- Ricardo de las Heras M2M Research Technological Specialist E-mail: rheras at tid.es Phone1: (+34) 983 367625 Phone2 OCS: (+34) 91 31 29511 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 From rheras at tid.es Mon Dec 12 13:59:18 2011 From: rheras at tid.es (Ricardo de las Heras) Date: Mon, 12 Dec 2011 13:59:18 +0100 Subject: [Fiware-iot] gateway architecture In-Reply-To: References: <3F4C11BC54A36642BFB5875D599F47BD053E0124@DEMUEXC013.nsn-intra.net> <4EE23142.7060109@tid.es> <3F4C11BC54A36642BFB5875D599F47BD0541EAF0@DEMUEXC013.nsn-intra.net> <4EE5E39B.3050301@tid.es> Message-ID: <4EE5FAA6.3050302@tid.es> An HTML attachment was scrubbed... URL: From jan.holler at ericsson.com Mon Dec 12 13:59:19 2011 From: jan.holler at ericsson.com (=?iso-8859-1?Q?Jan_H=F6ller?=) Date: Mon, 12 Dec 2011 13:59:19 +0100 Subject: [Fiware-iot] gateway architecture In-Reply-To: <4EE5E39B.3050301@tid.es> Message-ID: Hello Ricardo, 2) We cannot only view a gateway as a protocol translator. Gateways are generally deployed for several reasons. If considering legacy protocols (e.g. ZigBee HA), this is a complete protocol stack including the application layer. A gateway can handle this in two basic ways, either the gateway terminates up to the networking layer and ships the payload (app level stuff) transparently to the backend for further processing (e.g. the HA app level profile in the case of ZigBee), or you terminate the entire stack in the gateway and provides the necessary app level "interworking" inside the gateway. Another reason for deploying gateways is to shield sensor/actuator devices that operate under constraints, e.g. battery powered. Asynchronous communication with the devices are then provided by the gateway which necessarily means that sensor data is cached locally in the gateway, and potentially also providing more metadata or contextual data to the actual sensor reading. Furthermore, in certain deployment scenarios, a gateway is even more of a local "semi-autonomous" application server that can execute localized services e.g. data aggregation, local sensor-actuator control loops etc. A typical example is building automation where services execute locally and not always means that every event needs to be sent to the backend for consultation. So, I see that there are a number of reasons why a gateway generally speaking is more than just providing protocol interworking on the communications layer. When it comes to protocol translation/adaptation, this too is needed on different places in the topology. Gateways are traditionally the term used for doing this in localized environments, and from an IoT perspective typically operating out of WSAN environments running on top of 802.15.4. In these gateways, protocol adaptation is needed. Furthermore, protocol adaptation can also be taking place in the backend/cloud environment. Now, do we use the same assets depending on where in the topology we look at this functionality to take place? In FI-ware IoT, I have not seen this being discussed. Secondly, will the IoT backend in Fi-ware do any more termination than the ETSI M2M mId southbound (on the "lower" level)? Best regards, Jan From: Ricardo de las Heras > Date: Mon, 12 Dec 2011 12:20:59 +0100 To: "Bisztray, Denes (NSN - HU/Budapest)" > Cc: "fiware-iot at lists.fi-ware.eu" > Subject: Re: [Fiware-iot] gateway architecture HI D?nes, 2) I don't understand why we assume to have an application layer within the gateway, of course it is feasible if you increase the complexity of it, for us in Telef?nica it is out of the scope of our platform IDAS and so far we don't have any type of requirement that implies these type of decisions, so that's the main reason. And in this way you know our platform is for example included at this time in several important projects like SmartSantander. You referenced too in the last call the possibility of providing direct communication at the Gateway level between resources. From my point of view this is the same thing, you can even include a more complex HUB (device's concentrator, as previous step to the gateway) and to manage everything there. But for example maybe you should have to manage different protocols, different standards, security issues, etc. that obviously increase the complexity and costs of those elements. 1) We support any type of sensor measurement technology and underlying communication protocols, but obviously we unify them to a common language at the gateway level, and this is the well known OGC, currently well supported by the IoT community. 3) Basically as I have already explained: a data format adaptation: to translate device specific Messages into SensorML-based Messages and vice versa. This provides an abstraction level to the platform making it suitable for integrating different sensor technologies. So, an especific adaptor module is needed for including new protocols. And second: Also it allows sending commands to Actuators. Finally, answering you to another email, YES, IoT-A is responsible for the Discovery and Resolution of Things. Anyway, if you have any other question or additional clarification please let me know, thanks, best, RHer at s. Bisztray, Denes (NSN - HU/Budapest) wrote: Hi Ricardo, Sorry for mixing up the order, but it makes more sense this way: 2) We assume to have an application layer within the gateway as well as the device itself, not just at the backend-level. In order to have applications on the gateway, we need to have an interface for that. This is the functionality that IDAS seems to lack (at least as far as I understood). And OGC SWE altogether. 1)This seems problematic. You support only OGC SWE functionality, i.e. sensor measurement gathering and sensor tasking. When asked on the weekly IoT meeting you said IDAS supports the buffering of sensorial data in an offline case. But if we look back at the previous point, this is far from satisfactory, an autonomous application layer on the gateway would be necessary. 3) What are these interface capable of? Best, D?nes From: ext Ricardo de las Heras [mailto:rheras at tid.es] Sent: Friday, December 09, 2011 5:03 PM To: Bisztray, Denes (NSN - HU/Budapest) Cc: fiware-iot at lists.fi-ware.eu; gianpiero.fici at telecomitalia.it; sabrina.guerra at telecomitalia.it; thierry.nagellen at orange.com Subject: Re: gateway architecture Dear D?nes, interesting questions here, in our case from IDAS: 1) Tthe gateways provides translation capabilities from the broad range of protocols, unifying them to a SensorAPI (OGC SensorML + O&M). I attach you a picture with this concept. So the gateway is out of the platform. 2) I don't understand your exposition, why you speak about an interface between the Gateway and the application layer? I don't agree this interface. 3) Yes, we have interfaces from IDAS to the botton layers (Gateway) and with the upper layers (applications). Interfaces are public of course. 4) Good question, indeed I had already made this question. From my point of view that would be the T5.1 scope, isn't it? Are you asking about name of partners too:) ? have a nice weekend, RHer at s. Bisztray, Denes (NSN - HU/Budapest) wrote: Dear all, Although the asset selection is still questionably finished, it would good to clarify the architecture around the gateways as well as the internal APIs. 1. Where do we have the gateway functionality? (i.e. microDB, instantaneous and real-time data, data aggregation filter, etc. ) - every asset implements the gateway functionality on its own, and provides an API that the gateway-northbound interface and application implementation can harness. - the assets only do protocol adaptation, the gateway functionality comes from outside (possibly one of the assetes) 2. We need to provide two interfaces within a gateway. One is the ETSI M2M interface that communicates with the backend, and another interface for the application layer within the gateway. How will they communicate with the assets? 3. Backend API problems. The IDAS which seems to be selected for all GEs within resources management (is it?). It needs to have an internal interface for communicating with both the northbound and southbound interface. When will it be public? Or have a service bus? This one needs to be worked out. 4. Who implements the ETSI M2M interfaces? Best, D?nes -- ------------------------------------- Ricardo de las Heras M2M Research Technological Specialist E-mail: rheras at tid.es Phone1: (+34) 983 367625 Phone2 OCS: (+34) 91 31 29511 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 -- ------------------------------------- Ricardo de las Heras M2M Research Technological Specialist E-mail: rheras at tid.es Phone1: (+34) 983 367625 Phone2 OCS: (+34) 91 31 29511 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 From P.Barnaghi at surrey.ac.uk Mon Dec 12 14:02:51 2011 From: P.Barnaghi at surrey.ac.uk (P.Barnaghi at surrey.ac.uk) Date: Mon, 12 Dec 2011 13:02:51 +0000 Subject: [Fiware-iot] gateway architecture In-Reply-To: <4EE5FAA6.3050302@tid.es> References: <3F4C11BC54A36642BFB5875D599F47BD053E0124@DEMUEXC013.nsn-intra.net> <4EE23142.7060109@tid.es> <3F4C11BC54A36642BFB5875D599F47BD0541EAF0@DEMUEXC013.nsn-intra.net> <4EE5E39B.3050301@tid.es> <4EE5FAA6.3050302@tid.es> Message-ID: Thanks Ricardo. As I mentioned I am still not sure if a new parser will solve the issues; - Payam ________________________________ From: Ricardo de las Heras [mailto:rheras at tid.es] Sent: 12 December 2011 12:59 To: Barnaghi P Dr (Electronic Eng) Cc: denes.bisztray at nsn.com; fiware-iot at lists.fi-ware.eu Subject: Re: [Fiware-iot] gateway architecture OK Payam, thanks for your clarifications, we had already discussed it in a previous threads of emails, the option of a new parser sounds good but we have to go more in deep with it, clarifying the different options we have. br, Ricardo. P.Barnaghi at surrey.ac.uk wrote: Hi all, My reply is only related to the last part of Ricardo's email: Discovery and Resolution of Things from IOT-A. We are involved in this task in IoT-A and I would like to add some clarifications to this: Discovery and Resolution of Things in IoT-A is planned based on the proposed information model for entities and resources in IoT-A. The entity and resource descriptions are in RDF format and are represented according to the IoT-A model. A software agent parses these descriptions and extracts the information for indexing. A machine learning method then applies probabilistic machine learning based on LDA approach to create a low-dimensional specification of data that is transformed in vector-space model and similarities are measured based on a vector similarity measure between query vector (again encoded using a similar method) and transformed descriptions. However, if the resources are stored and/or represented differently with different format and different set of attributes, the parser won't be able to extract the required information and I am also not sure even adapting a new parser could still help extracting the required features. The repository and description format will also affect this. Again, this is related to the work that we do in IoT-A discovery and perhaps other IoT-A partners can provide more information. Thanks, 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: 12 December 2011 11:21 To: Bisztray, Denes (NSN - HU/Budapest) Cc: fiware-iot at lists.fi-ware.eu Subject: Re: [Fiware-iot] gateway architecture HI D?nes, 2) I don't understand why we assume to have an application layer within the gateway, of course it is feasible if you increase the complexity of it, for us in Telef?nica it is out of the scope of our platform IDAS and so far we don't have any type of requirement that implies these type of decisions, so that's the main reason. And in this way you know our platform is for example included at this time in several important projects like SmartSantander. You referenced too in the last call the possibility of providing direct communication at the Gateway level between resources. From my point of view this is the same thing, you can even include a more complex HUB (device's concentrator, as previous step to the gateway) and to manage everything there. But for example maybe you should have to manage different protocols, different standards, security issues, etc. that obviously increase the complexity and costs of those elements. 1) We support any type of sensor measurement technology and underlying communication protocols, but obviously we unify them to a common language at the gateway level, and this is the well known OGC, currently well supported by the IoT community. 3) Basically as I have already explained: a data format adaptation: to translate device specific Messages into SensorML-based Messages and vice versa. This provides an abstraction level to the platform making it suitable for integrating different sensor technologies. So, an especific adaptor module is needed for including new protocols. And second: Also it allows sending commands to Actuators. Finally, answering you to another email, YES, IoT-A is responsible for the Discovery and Resolution of Things. Anyway, if you have any other question or additional clarification please let me know, thanks, best, RHer at s. Bisztray, Denes (NSN - HU/Budapest) wrote: Hi Ricardo, Sorry for mixing up the order, but it makes more sense this way: 2) We assume to have an application layer within the gateway as well as the device itself, not just at the backend-level. In order to have applications on the gateway, we need to have an interface for that. This is the functionality that IDAS seems to lack (at least as far as I understood). And OGC SWE altogether. 1)This seems problematic. You support only OGC SWE functionality, i.e. sensor measurement gathering and sensor tasking. When asked on the weekly IoT meeting you said IDAS supports the buffering of sensorial data in an offline case. But if we look back at the previous point, this is far from satisfactory, an autonomous application layer on the gateway would be necessary. 3) What are these interface capable of? Best, D?nes From: ext Ricardo de las Heras [mailto:rheras at tid.es] Sent: Friday, December 09, 2011 5:03 PM To: Bisztray, Denes (NSN - HU/Budapest) Cc: fiware-iot at lists.fi-ware.eu; gianpiero.fici at telecomitalia.it; sabrina.guerra at telecomitalia.it; thierry.nagellen at orange.com Subject: Re: gateway architecture Dear D?nes, interesting questions here, in our case from IDAS: 1) Tthe gateways provides translation capabilities from the broad range of protocols, unifying them to a SensorAPI (OGC SensorML + O&M). I attach you a picture with this concept. So the gateway is out of the platform. 2) I don't understand your exposition, why you speak about an interface between the Gateway and the application layer? I don't agree this interface. 3) Yes, we have interfaces from IDAS to the botton layers (Gateway) and with the upper layers (applications). Interfaces are public of course. 4) Good question, indeed I had already made this question. From my point of view that would be the T5.1 scope, isn't it? Are you asking about name of partners too:) ? have a nice weekend, RHer at s. Bisztray, Denes (NSN - HU/Budapest) wrote: Dear all, Although the asset selection is still questionably finished, it would good to clarify the architecture around the gateways as well as the internal APIs. 1. Where do we have the gateway functionality? (i.e. microDB, instantaneous and real-time data, data aggregation filter, etc. ) - every asset implements the gateway functionality on its own, and provides an API that the gateway-northbound interface and application implementation can harness. - the assets only do protocol adaptation, the gateway functionality comes from outside (possibly one of the assetes) 2. We need to provide two interfaces within a gateway. One is the ETSI M2M interface that communicates with the backend, and another interface for the application layer within the gateway. How will they communicate with the assets? 3. Backend API problems. The IDAS which seems to be selected for all GEs within resources management (is it?). It needs to have an internal interface for communicating with both the northbound and southbound interface. When will it be public? Or have a service bus? This one needs to be worked out. 4. Who implements the ETSI M2M interfaces? Best, D?nes -- ------------------------------------- Ricardo de las Heras M2M Research Technological Specialist E-mail: rheras at tid.es Phone1: (+34) 983 367625 Phone2 OCS: (+34) 91 31 29511 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 denes.bisztray at nsn.com Tue Dec 13 14:50:15 2011 From: denes.bisztray at nsn.com (Bisztray, Denes (NSN - HU/Budapest)) Date: Tue, 13 Dec 2011 14:50:15 +0100 Subject: [Fiware-iot] Work item status In-Reply-To: <4EDF0ADC.1040809@tid.es> References: <93D28BDF64839C468B848D14227151A202B1874D@FIESEXC014.nsn-intra.net> <4EDF0ADC.1040809@tid.es> Message-ID: <3F4C11BC54A36642BFB5875D599F47BD05467572@DEMUEXC013.nsn-intra.net> Hi Ricardo, The slide you are looking for is on the forge since the 8th of November. FYI the mail below. I welcome all comments. Currently it is a bit outdated, I'm incorporating some changes at the moment. Best, D?nes _____________________________________________ From: Bisztray, Denes (NSN - HU/Budapest) Sent: Tuesday, November 08, 2011 9:44 AM To: 'fiware-iot at lists.fi-ware.eu' Cc: rheras at tid.es; Guerra Sabrina; 'ext Fici Gian Piero'; thierry.nagellen at orange.com Subject: IoT SE Complete Architecture Dear All, I created a component-level overview of the IoT SE architecture. I recommend the task leaders to have a look at it. It would be nice to make clear where the various GEs may run. https://forge.fi-ware.eu/docman/view.php/11/570/v01-CompleteArchitecture.pptx Please comment and correct it. As a second step it would be nice to put the selected assets to the components to see how the various things interact with each other. From: fiware-iot-bounces at lists.fi-ware.eu [mailto:fiware-iot-bounces at lists.fi-ware.eu] On Behalf Of ext Ricardo de las Heras Sent: Wednesday, December 07, 2011 7:43 AM To: Farkas, Lorant (NSN - HU/Budapest) Cc: fiware-iot at lists.fi-ware.eu Subject: Re: [Fiware-iot] Work item status Dear Lorant, please can you send us the slides corresponding to the architecture figure below, it will be more easy to read. Having a first look to it, I would like to stress that ETSI-M2M defines a complete communication platform, not only a protocol, so I miss some blocks in that architecture providing its support for the ETSI's architecture functional blocks. Sorry for delaying my answer but this is an special week in Spain, we have two bank holidays (6th and 8th) and I was out of the office since Friday. There are not relevant progress with those two tasks, I'll read and answer your last emails this week asap and next I'll start working with the interface definition, as you have proposed. Do they have any type of draft for the template handler definition? thanks, br, RHer at s. Farkas, Lorant (NSN - HU/Budapest) wrote: Dear Ricardo, Can you update the status of the 2 work items belonging to you? https://forge.fi-ware.eu/tracker/index.php?func=detail&aid=960&group_id=11&atid=193 - was there any progress with the asset selection? Whom are you discussing this with currently and what is the status? https://forge.fi-ware.eu/tracker/index.php?func=detail&aid=959&group_id=11&atid=193 - was there any progress for the directory interface definition? In my view (see new arch figure from D?nes): -there should be activity dealing with NGSI-based thing level API, dealt with by Tobias (https://forge.fi-ware.eu/tracker/index.php?func=detail&aid=964&group_id=11&atid=193 ) - therefore this work item does not contain that part, the progress should not be marked here -there should be activity dealing with the interface between template handler and directory handler - this is between TID and SAP - the progress on this should be marked Thanks & Br, Lorant -- ------------------------------------- Ricardo de las Heras M2M Research Technological Specialist E-mail: rheras at tid.es Phone1: (+34) 983 367625 Phone2 OCS: (+34) 91 31 29511 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.png Type: image/png Size: 57850 bytes Desc: image001.png URL: From denes.bisztray at nsn.com Tue Dec 13 15:23:07 2011 From: denes.bisztray at nsn.com (Bisztray, Denes (NSN - HU/Budapest)) Date: Tue, 13 Dec 2011 15:23:07 +0100 Subject: [Fiware-iot] Work item status In-Reply-To: <3F4C11BC54A36642BFB5875D599F47BD05467572@DEMUEXC013.nsn-intra.net> References: <93D28BDF64839C468B848D14227151A202B1874D@FIESEXC014.nsn-intra.net> <4EDF0ADC.1040809@tid.es> <3F4C11BC54A36642BFB5875D599F47BD05467572@DEMUEXC013.nsn-intra.net> Message-ID: <3F4C11BC54A36642BFB5875D599F47BD054675EB@DEMUEXC013.nsn-intra.net> Here the updated version of the architecture diagram in a quite large slide: https://forge.fi-ware.eu/docman/view.php/11/683/v03-CompleteArchitecture.pptx Feel free to comment. It would be good to put the various assets to all the boxes J. Best, D?nes From: fiware-iot-bounces at lists.fi-ware.eu [mailto:fiware-iot-bounces at lists.fi-ware.eu] On Behalf Of Bisztray, Denes (NSN - HU/Budapest) Sent: Tuesday, December 13, 2011 2:50 PM To: ext Ricardo de las Heras Cc: fiware-iot at lists.fi-ware.eu Subject: Re: [Fiware-iot] Work item status Hi Ricardo, The slide you are looking for is on the forge since the 8th of November. FYI the mail below. I welcome all comments. Currently it is a bit outdated, I'm incorporating some changes at the moment. Best, D?nes _____________________________________________ From: Bisztray, Denes (NSN - HU/Budapest) Sent: Tuesday, November 08, 2011 9:44 AM To: 'fiware-iot at lists.fi-ware.eu' Cc: rheras at tid.es; Guerra Sabrina; 'ext Fici Gian Piero'; thierry.nagellen at orange.com Subject: IoT SE Complete Architecture Dear All, I created a component-level overview of the IoT SE architecture. I recommend the task leaders to have a look at it. It would be nice to make clear where the various GEs may run. https://forge.fi-ware.eu/docman/view.php/11/570/v01-CompleteArchitecture.pptx Please comment and correct it. As a second step it would be nice to put the selected assets to the components to see how the various things interact with each other. From: fiware-iot-bounces at lists.fi-ware.eu [mailto:fiware-iot-bounces at lists.fi-ware.eu] On Behalf Of ext Ricardo de las Heras Sent: Wednesday, December 07, 2011 7:43 AM To: Farkas, Lorant (NSN - HU/Budapest) Cc: fiware-iot at lists.fi-ware.eu Subject: Re: [Fiware-iot] Work item status Dear Lorant, please can you send us the slides corresponding to the architecture figure below, it will be more easy to read. Having a first look to it, I would like to stress that ETSI-M2M defines a complete communication platform, not only a protocol, so I miss some blocks in that architecture providing its support for the ETSI's architecture functional blocks. Sorry for delaying my answer but this is an special week in Spain, we have two bank holidays (6th and 8th) and I was out of the office since Friday. There are not relevant progress with those two tasks, I'll read and answer your last emails this week asap and next I'll start working with the interface definition, as you have proposed. Do they have any type of draft for the template handler definition? thanks, br, RHer at s. Farkas, Lorant (NSN - HU/Budapest) wrote: Dear Ricardo, Can you update the status of the 2 work items belonging to you? https://forge.fi-ware.eu/tracker/index.php?func=detail&aid=960&group_id=11&atid=193 - was there any progress with the asset selection? Whom are you discussing this with currently and what is the status? https://forge.fi-ware.eu/tracker/index.php?func=detail&aid=959&group_id=11&atid=193 - was there any progress for the directory interface definition? In my view (see new arch figure from D?nes): -there should be activity dealing with NGSI-based thing level API, dealt with by Tobias (https://forge.fi-ware.eu/tracker/index.php?func=detail&aid=964&group_id=11&atid=193 ) - therefore this work item does not contain that part, the progress should not be marked here -there should be activity dealing with the interface between template handler and directory handler - this is between TID and SAP - the progress on this should be marked Thanks & Br, Lorant -- ------------------------------------- Ricardo de las Heras M2M Research Technological Specialist E-mail: rheras at tid.es Phone1: (+34) 983 367625 Phone2 OCS: (+34) 91 31 29511 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.png Type: image/png Size: 57850 bytes Desc: image001.png URL: From jan.holler at ericsson.com Wed Dec 14 09:54:42 2011 From: jan.holler at ericsson.com (=?iso-8859-1?Q?Jan_H=F6ller?=) Date: Wed, 14 Dec 2011 09:54:42 +0100 Subject: [Fiware-iot] Updated: IoT weekly meeting In-Reply-To: <93D28BDF64839C468B848D14227151A202A9C031@FIESEXC014.nsn-intra.net> Message-ID: Hello Lorant, Any meeting today 14 December? Jan From: "Farkas, Lorant (NSN - HU/Budapest)" > Date: Tue, 29 Nov 2011 09:55:00 +0100 To: "fiware-iot at lists.fi-ware.eu" > Subject: [Fiware-iot] Updated: IoT weekly meeting When: 2011. november 30. 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, The meeting tomorrow is cancelled. Task leaders should now focus on the planning of the 2nd sprint and interact with the asset owners from their respective tasks. 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) From denes.bisztray at nsn.com Wed Dec 14 09:57:39 2011 From: denes.bisztray at nsn.com (Bisztray, Denes (NSN - HU/Budapest)) Date: Wed, 14 Dec 2011 09:57:39 +0100 Subject: [Fiware-iot] Updated: IoT weekly meeting In-Reply-To: References: <93D28BDF64839C468B848D14227151A202A9C031@FIESEXC014.nsn-intra.net> Message-ID: <3F4C11BC54A36642BFB5875D599F47BD05467968@DEMUEXC013.nsn-intra.net> Yes -----Original Message----- From: fiware-iot-bounces at lists.fi-ware.eu [mailto:fiware-iot-bounces at lists.fi-ware.eu] On Behalf Of ext Jan H?ller Sent: Wednesday, December 14, 2011 9:55 AM To: Farkas, Lorant (NSN - HU/Budapest); fiware-iot at lists.fi-ware.eu Subject: Re: [Fiware-iot] Updated: IoT weekly meeting Hello Lorant, Any meeting today 14 December? Jan From: "Farkas, Lorant (NSN - HU/Budapest)" > Date: Tue, 29 Nov 2011 09:55:00 +0100 To: "fiware-iot at lists.fi-ware.eu" > Subject: [Fiware-iot] Updated: IoT weekly meeting When: 2011. november 30. 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, The meeting tomorrow is cancelled. Task leaders should now focus on the planning of the 2nd sprint and interact with the asset owners from their respective tasks. 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) _______________________________________________ Fiware-iot mailing list Fiware-iot at lists.fi-ware.eu http://lists.fi-ware.eu/listinfo/fiware-iot From denes.bisztray at nsn.com Thu Dec 15 08:40:02 2011 From: denes.bisztray at nsn.com (Bisztray, Denes (NSN - HU/Budapest)) Date: Thu, 15 Dec 2011 08:40:02 +0100 Subject: [Fiware-iot] [Fiware-Iot] IoT Weekly Meeting Minutes - 14/12/2011 In-Reply-To: <3F4C11BC54A36642BFB5875D599F47BD053E0732@DEMUEXC013.nsn-intra.net> References: <3F4C11BC54A36642BFB5875D599F47BD053E0732@DEMUEXC013.nsn-intra.net> Message-ID: <3F4C11BC54A36642BFB5875D599F47BD054A479F@DEMUEXC013.nsn-intra.net> Dear All, Under this link please find the minutes from this week. https://forge.fi-ware.eu/docman/view.php/11/685/FI-WARE+IoT+Minutes+14-12-11.doc Best, D?nes _______________________________________________ Fiware-iot mailing list Fiware-iot at lists.fi-ware.eu http://lists.fi-ware.eu/listinfo/fiware-iot From rheras at tid.es Thu Dec 15 15:34:19 2011 From: rheras at tid.es (Ricardo de las Heras) Date: Thu, 15 Dec 2011 15:34:19 +0100 Subject: [Fiware-iot] [Fiware-Iot] IoT Weekly Meeting Minutes - 14/12/2011 In-Reply-To: <3F4C11BC54A36642BFB5875D599F47BD054A479F@DEMUEXC013.nsn-intra.net> References: <3F4C11BC54A36642BFB5875D599F47BD053E0732@DEMUEXC013.nsn-intra.net> <3F4C11BC54A36642BFB5875D599F47BD054A479F@DEMUEXC013.nsn-intra.net> Message-ID: <4EEA056B.5040003@tid.es> An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: Fiware-T5.2-Assets-matching-v1.pptx Type: application/vnd.openxmlformats-officedocument.presentationml.presentation Size: 283658 bytes Desc: not available URL: From Martin.Bauer at neclab.eu Thu Dec 15 18:09:56 2011 From: Martin.Bauer at neclab.eu (Martin Bauer) Date: Thu, 15 Dec 2011 17:09:56 +0000 Subject: [Fiware-iot] [Fiware-Iot] IoT Weekly Meeting Minutes - 14/12/2011 In-Reply-To: <4EEA056B.5040003@tid.es> References: <3F4C11BC54A36642BFB5875D599F47BD053E0732@DEMUEXC013.nsn-intra.net> <3F4C11BC54A36642BFB5875D599F47BD054A479F@DEMUEXC013.nsn-intra.net> <4EEA056B.5040003@tid.es> Message-ID: Hi Ricardo, My understanding regarding the Asset selection for T5.2 was the following: - Some components need to interwork so closely that it does not make sense to use different assets to implement them. This is true for: a) [Directory Handler], [Resource Directory] and [IoT Resource and Service Discovery] b) [Things Manager] and [Discovery and Resolution of Things] - IDAS was the candidate for a) and (NEC's) IoT-A component for b) - b) will be required for NGSI functionality - from my point of view the only realistic competitor for b) would be SENSEI Entity Directory - under the assumption of the asset not being selected, SAP has looked for an alternative activity, i.e. testing components - Regarding [Thing & IoT Service Monitoring] I do not see a contender to a yet to be developed IoT-A component, SENSEI did not provide this functionality and as far as I know the other assets currently do not support the Thing/Entity concept - [IoT Catalog and Location] could in principle be handled by a different component as it may not have to be so closely integrated with the components in a) Do you agree with my assessment above? If not, could you please explain what you see differently and why? I do not understand most of the arrows that have been added to slide 3, especially the configuration arrow between Things Manager and IoT Resource Directory is unclear to me. I think NGSI would interact with Thing Resolution only. Then there needs to be some management interface providing input to the Things Manager - for symmetry reasons with the service/resource layer, we could add another handler component, even though the integration will be so close that this will not be a truly independent component. Best regards, Martin ------------------------------------------ Dr. Martin Bauer Senior Researcher NEC Europe Ltd. NEC Laboratories Europe Software & Services Research Division Kurf?rsten-Anlage 36 D-69115 Heidelberg Tel: +49/ (0)6221/4342-168 Fax: +49/ (0)6221/4342-155 E-Mail: Martin.Bauer at neclab.eu http://www.nw.neclab.eu From: fiware-iot-bounces at lists.fi-ware.eu [mailto:fiware-iot-bounces at lists.fi-ware.eu] On Behalf Of Ricardo de las Heras Sent: Donnerstag, 15. Dezember 2011 15:34 To: fiware-iot at lists.fi-ware.eu Subject: Re: [Fiware-iot] [Fiware-Iot] IoT Weekly Meeting Minutes - 14/12/2011 Dear partners involved into T5.2, following the discussion you had yesterday during the weekly call, I attach you a new couple of slides describing the high level blocks we have in the architecture and the new low level approach (v3) to the WP5 architecture provided by D?nes last week. Maybe we need a further discussion for completing that low level schema of the architecture, we can do it later according as we continue our discussions, but I would like a this time to have a new and quick round now with all of you in order to describe where you see located your assets, matching those blocks of the architecture with your interest within T5.2. Additionally to our assets (TID) I've included some others that I consider at this time clear enough (NEC, Univ.Surrey, ...), please complete/correct it if needed. Please feel free for adding new blocks or additional details if needed for clarifying your contributions/interest, in fact I've added the 'Things manager' orange block, because I miss it (please D?nes you can clarify it for me, maybe it was already included there in some way). Summarizing from our side TID, we would like to provide / to be involved in: - Resource management Directory (from IDAS), including the catalog of the registered resources (from SensorML, Register Sensor). - Things management Directory (from IoT-A). - Configuration/management relations Things-Resources (IoT-A). We explicitly reject at this time to be involved in developing the M2M-ETSI standard inclusion, although it doesn't meant that other partners may provide it if they consider it interesting. Alternatively as you know we offer our involvement for including OGC-SWE, suggesting to include finally both alternatives in the bottom side of the architecture, I consider it feasible and compatible. This is our proposal, feedback is welcomed, I think is quite clear and now provide yours ASAP. Please send me your modifications for integrating them over the attached couple of slides and a text describing those points in the same way. thanks! best regards, Ricardo. Bisztray, Denes (NSN - HU/Budapest) wrote: Dear All, Under this link please find the minutes from this week. https://forge.fi-ware.eu/docman/view.php/11/685/FI-WARE+IoT+Minutes+14-12-11.doc Best, D?nes _______________________________________________ Fiware-iot mailing list Fiware-iot at lists.fi-ware.eu http://lists.fi-ware.eu/listinfo/fiware-iot _______________________________________________ Fiware-iot mailing list Fiware-iot at lists.fi-ware.eu http://lists.fi-ware.eu/listinfo/fiware-iot -- ------------------------------------- Ricardo de las Heras M2M Research Technological Specialist E-mail: rheras at tid.es Phone1: (+34) 983 367625 Phone2 OCS: (+34) 91 31 29511 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 T.Elsaleh at surrey.ac.uk Fri Dec 16 20:52:31 2011 From: T.Elsaleh at surrey.ac.uk (T.Elsaleh at surrey.ac.uk) Date: Fri, 16 Dec 2011 19:52:31 +0000 Subject: [Fiware-iot] [Fiware-Iot] IoT Weekly Meeting Minutes - 14/12/2011 In-Reply-To: <4EEA056B.5040003@tid.es> References: <3F4C11BC54A36642BFB5875D599F47BD053E0732@DEMUEXC013.nsn-intra.net> <3F4C11BC54A36642BFB5875D599F47BD054A479F@DEMUEXC013.nsn-intra.net> <4EEA056B.5040003@tid.es> Message-ID: <2AAC0B6FF99A064C853BFB1C9295F3CCA58EA39D48@EXMB05CMS.surrey.ac.uk> Hello Ricardo, All, The slides attached does reflect what UniS will contribute towards but not completely. From the latest PhC, it was understood that multiple implementations of the assets are expected. From the point of view of UniS, we will provide a discovery mechanism for resources and services. Based on this we will also provide an alternative Pub/Sub repository that will be directly compatible with this discovery mechanism... and can be used as a backup in case of future integration issues. The Pub/Sub repository will store IoTA-based description models, and will also integrate IoTA resource/entity/services models with the OMA-NGSI information models, if required. Best regards, Tarek Elsaleh Research Assistant Department of Electronic Engineering University of Surrey Guildford, GU2 7XH Tel: 01483 689485 From: fiware-iot-bounces at lists.fi-ware.eu [mailto:fiware-iot-bounces at lists.fi-ware.eu] On Behalf Of Ricardo de las Heras Sent: 15 December 2011 14:34 To: fiware-iot at lists.fi-ware.eu Subject: Re: [Fiware-iot] [Fiware-Iot] IoT Weekly Meeting Minutes - 14/12/2011 Dear partners involved into T5.2, following the discussion you had yesterday during the weekly call, I attach you a new couple of slides describing the high level blocks we have in the architecture and the new low level approach (v3) to the WP5 architecture provided by D?nes last week. Maybe we need a further discussion for completing that low level schema of the architecture, we can do it later according as we continue our discussions, but I would like a this time to have a new and quick round now with all of you in order to describe where you see located your assets, matching those blocks of the architecture with your interest within T5.2. Additionally to our assets (TID) I've included some others that I consider at this time clear enough (NEC, Univ.Surrey, ...), please complete/correct it if needed. Please feel free for adding new blocks or additional details if needed for clarifying your contributions/interest, in fact I've added the 'Things manager' orange block, because I miss it (please D?nes you can clarify it for me, maybe it was already included there in some way). Summarizing from our side TID, we would like to provide / to be involved in: - Resource management Directory (from IDAS), including the catalog of the registered resources (from SensorML, Register Sensor). - Things management Directory (from IoT-A). - Configuration/management relations Things-Resources (IoT-A). We explicitly reject at this time to be involved in developing the M2M-ETSI standard inclusion, although it doesn't meant that other partners may provide it if they consider it interesting. Alternatively as you know we offer our involvement for including OGC-SWE, suggesting to include finally both alternatives in the bottom side of the architecture, I consider it feasible and compatible. This is our proposal, feedback is welcomed, I think is quite clear and now provide yours ASAP. Please send me your modifications for integrating them over the attached couple of slides and a text describing those points in the same way. thanks! best regards, Ricardo. Bisztray, Denes (NSN - HU/Budapest) wrote: Dear All, Under this link please find the minutes from this week. https://forge.fi-ware.eu/docman/view.php/11/685/FI-WARE+IoT+Minutes+14-12-11.doc Best, D?nes _______________________________________________ Fiware-iot mailing list Fiware-iot at lists.fi-ware.eu http://lists.fi-ware.eu/listinfo/fiware-iot _______________________________________________ Fiware-iot mailing list Fiware-iot at lists.fi-ware.eu http://lists.fi-ware.eu/listinfo/fiware-iot -- ------------------------------------- Ricardo de las Heras M2M Research Technological Specialist E-mail: rheras at tid.es Phone1: (+34) 983 367625 Phone2 OCS: (+34) 91 31 29511 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 ________________________________ No virus found in this message. Checked by AVG - www.avg.com Version: 2012.0.1890 / Virus Database: 2108/4681 - Release Date: 12/14/11 -------------- next part -------------- An HTML attachment was scrubbed... URL: From rheras at tid.es Tue Dec 20 11:36:25 2011 From: rheras at tid.es (Ricardo de las Heras) Date: Tue, 20 Dec 2011 11:36:25 +0100 Subject: [Fiware-iot] [Fiware-Iot] IoT Weekly Meeting Minutes - 14/12/2011 In-Reply-To: References: <3F4C11BC54A36642BFB5875D599F47BD053E0732@DEMUEXC013.nsn-intra.net> <3F4C11BC54A36642BFB5875D599F47BD054A479F@DEMUEXC013.nsn-intra.net> <4EEA056B.5040003@tid.es> Message-ID: <4EF06529.8010207@tid.es> An HTML attachment was scrubbed... URL: From denes.bisztray at nsn.com Tue Dec 20 15:08:00 2011 From: denes.bisztray at nsn.com (Bisztray, Denes (NSN - HU/Budapest)) Date: Tue, 20 Dec 2011 15:08:00 +0100 Subject: [Fiware-iot] weekly meeting tomorrow cancelled Message-ID: <3F4C11BC54A36642BFB5875D599F47BD054EBD13@DEMUEXC013.nsn-intra.net> Dear All, Since most people are on holiday, I advise we cancel the weekly meeting tomorrow. Best, D?nes -------------- next part -------------- An HTML attachment was scrubbed... URL: From jan.holler at ericsson.com Wed Dec 21 07:40:39 2011 From: jan.holler at ericsson.com (=?iso-8859-1?Q?Jan_H=F6ller?=) Date: Wed, 21 Dec 2011 07:40:39 +0100 Subject: [Fiware-iot] IoT planning for GA in January? Re: weekly meeting tomorrow cancelled In-Reply-To: <3F4C11BC54A36642BFB5875D599F47BD054EBD13@DEMUEXC013.nsn-intra.net> Message-ID: Hello, Since the GA has been announced for 23 Jan, do we know any overall planning of the week? It would be very good if we could get a rough IoT WP planning in place before the holidays so necessary travel arrangements can be made. Regards, Jan From: "Bisztray, Denes (NSN - HU/Budapest)" > Date: Tue, 20 Dec 2011 15:08:00 +0100 To: "fiware-iot at lists.fi-ware.eu" > Subject: [Fiware-iot] weekly meeting tomorrow cancelled Dear All, Since most people are on holiday, I advise we cancel the weekly meeting tomorrow. Best, D?nes From denes.bisztray at nsn.com Wed Dec 21 09:19:46 2011 From: denes.bisztray at nsn.com (Bisztray, Denes (NSN - HU/Budapest)) Date: Wed, 21 Dec 2011 09:19:46 +0100 Subject: [Fiware-iot] IoT planning for GA in January? Re: weekly meeting tomorrow cancelled In-Reply-To: References: <3F4C11BC54A36642BFB5875D599F47BD054EBD13@DEMUEXC013.nsn-intra.net> Message-ID: <3F4C11BC54A36642BFB5875D599F47BD054EBF45@DEMUEXC013.nsn-intra.net> Hello Jan, I completely agree. However, there is no agenda for the GA yet. And also I wonder, how many of us is on holiday already. Best, D?nes -----Original Message----- From: ext Jan H?ller [mailto:jan.holler at ericsson.com] Sent: Wednesday, December 21, 2011 7:41 AM To: Bisztray, Denes (NSN - HU/Budapest); fiware-iot at lists.fi-ware.eu Subject: IoT planning for GA in January? Re: [Fiware-iot] weekly meeting tomorrow cancelled Hello, Since the GA has been announced for 23 Jan, do we know any overall planning of the week? It would be very good if we could get a rough IoT WP planning in place before the holidays so necessary travel arrangements can be made. Regards, Jan From: "Bisztray, Denes (NSN - HU/Budapest)" > Date: Tue, 20 Dec 2011 15:08:00 +0100 To: "fiware-iot at lists.fi-ware.eu" > Subject: [Fiware-iot] weekly meeting tomorrow cancelled Dear All, Since most people are on holiday, I advise we cancel the weekly meeting tomorrow. Best, D?nes From denes.bisztray at nsn.com Wed Dec 21 09:57:31 2011 From: denes.bisztray at nsn.com (Bisztray, Denes (NSN - HU/Budapest)) Date: Wed, 21 Dec 2011 09:57:31 +0100 Subject: [Fiware-iot] Cross-chapter taskforces Message-ID: <3F4C11BC54A36642BFB5875D599F47BD054EBFAA@DEMUEXC013.nsn-intra.net> Dear All, New cross-chapter taskforces are set up in several topics. We have to delegate people to three of these taskforces. I would like to introduce the taskforces and give some advice on project members to include in them. 1. Generalized Thing-level Event Management model. The thing-level abstraction of event management used in IoT and DCM need to be consistent. Also, this model can be generalised to "Monitoring Agents" and "Monitoring Resources" so that Cloud Monitoring and Security Event Monitoring can use it. The task force should work on the adoption of the IoT Event Management Model. I would like to delegate someone from NEC, either Tobias, Martin or Salvatore. The mailing list will be: fiware-monitoring 2. Middleware Interfaces We need a common way to specify interfaces between GEs. (use a common interface technology, or maybe interface definition language that can translate to various technologies to remain future-proof) The delegation here is not obvious, but should include: Olaf Renner (NSN), Gian Piero Fici (TI), Tobias or Martin (NEC), Laurent or Laurence (Orange), Ricardo (TID) The mailing list will be: fiware-middleware 3. Semantic Web Infrastructure Several chapters addressing development of GEs whose implementation relies on Semantic Web technologies. We should go for the selection of a single technology for this (mostly RDF storage and SPARQL support). I would like to delegate someone from UoS, possibly Payam. The mailing list will be: fiware-semantic-platform Best, D?nes -------------- next part -------------- An HTML attachment was scrubbed... URL: From armin.zamani.farahani at sap.com Wed Dec 21 11:16:20 2011 From: armin.zamani.farahani at sap.com (Zamani Farahani, Armin) Date: Wed, 21 Dec 2011 11:16:20 +0100 Subject: [Fiware-iot] Test cases for NGSI-10 Message-ID: Dear all, we have worked out several test cases for the OMA NGSI-10 Context Management operations, based on the NGSI-10 specification at http://www.openmobilealliance.org/Technical/release_program/docs/NGSI/V1_0-20101207-C/OMA-TS-NGSI_Context_Management-V1_0-20100803-C.pdf. These test cases are a first draft and can be found at: https://forge.fi-ware.eu/plugins/mediawiki/wiki/iot/index.php/NGSI_10_TestCases Please have a look at them and tell us, if there is something missing or has to be improved. We are looking forward to get feedback from you. If there are any questions, please do not hesitate to contact us. Merry Christmas and a happy new year to all of you and your families! Best, Fabian Tschirschnitz and Armin Zamani -------------- next part -------------- An HTML attachment was scrubbed... URL: From Tobias.Jacobs at neclab.eu Thu Dec 22 12:21:05 2011 From: Tobias.Jacobs at neclab.eu (Tobias Jacobs) Date: Thu, 22 Dec 2011 11:21:05 +0000 Subject: [Fiware-iot] Test cases for NGSI-10 In-Reply-To: References: Message-ID: <8755F290097BD941865DC4245B335D2D08B89003@PALLENE.office.hd> Dear Armin, Thanks a lot for writing the test cases. This helps a lot to check whether we have a common understanding of the NGSI-10 functionality. I have two general remarks: - to our understanding, a query for {entity-list},{attribute-list} reads as "for all context elements in {entity-list} give me all available values of the attributes in {attribute-list}", rather than "give me all information about the entities in {entity-list} where information about all attributes in {attribute-list} is available". This applies in particular to test case 4,5,6,8,9 of queryContext. Some examples: o A query for the temperature of room2 should return only the temperature, not the humidity. The latter attribute simply does not appear in the result. o A query for the temperature and humidity of room1 should return the temperature of room1 (as the humidity of room1 is not known). o A query for the humidity of room1 and room2 should return an error for room1 and the humidity of room2. - In the subscribeContext operations as you describe it, the context entities are subscribing to each other. However, in general the reference of a subscription is a generic web resource and has nothing to do with the Context Entities. For example, one could request a subscription for temperature of room_1 with the recipient http://john.nicepeople.org/notify, so that John will get information updates about the room_1 temperature. Of course in principle the reference can also be a resource representing again a context entity, but this mixture of different roles is confusing in my opinion. By the way, the originator of a subscription does not have to be identical with the reference, e.g., Peter could request a subscription of John. Best regards Tobias From: fiware-iot-bounces at lists.fi-ware.eu [mailto:fiware-iot-bounces at lists.fi-ware.eu] On Behalf Of Zamani Farahani, Armin Sent: Mittwoch, 21. Dezember 2011 11:16 To: fiware-iot at lists.fi-ware.eu Subject: [Fiware-iot] Test cases for NGSI-10 Dear all, we have worked out several test cases for the OMA NGSI-10 Context Management operations, based on the NGSI-10 specification at http://www.openmobilealliance.org/Technical/release_program/docs/NGSI/V1_0-20101207-C/OMA-TS-NGSI_Context_Management-V1_0-20100803-C.pdf. These test cases are a first draft and can be found at: https://forge.fi-ware.eu/plugins/mediawiki/wiki/iot/index.php/NGSI_10_TestCases Please have a look at them and tell us, if the re is so be improved. We are looking forward to get feedback from you. If there are any questions, please do not hesitate to contact us. Merry Christmas and a happy new year to all of you and your families! Best, Fabia n Tschir o:p> -------------- next part -------------- An HTML attachment was scrubbed... URL: From Tobias.Jacobs at neclab.eu Thu Dec 22 14:12:22 2011 From: Tobias.Jacobs at neclab.eu (Tobias Jacobs) Date: Thu, 22 Dec 2011 13:12:22 +0000 Subject: [Fiware-iot] NGSI binding documents Message-ID: <8755F290097BD941865DC4245B335D2D08B8A05E@PALLENE.office.hd> Dear all, please find attached two contributions to the OMA NGSI binding discussion: - a first version of a RESTful binding spec for NGSI-10, which could serve as a basis for further discussion. - a new version of an XML schema description document for the NGSI-10 operations and data structures- it is a modified version of the xsd sent by Orange some weeks ago. In the current version I tried to stay as close to the original NGSI-10 v1.0 standard as possible. Best regards Tobias -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: binding_doc_v08.docx Type: application/vnd.openxmlformats-officedocument.wordprocessingml.document Size: 61731 bytes Desc: binding_doc_v08.docx URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: Ngsi10_schema1_v02-nec.xsd Type: text/xml Size: 9794 bytes Desc: Ngsi10_schema1_v02-nec.xsd URL: