Thierry, all, Let me slightly refine what you said. (a) M2M Gateway I think you pointed especially at the functionality of a 3GPP device to act as an M2M Gateway towards a M2M Area Network. Rightfully you pointed out that this needs device specific interfaces. IMHO, this plays well with the Communication Abstraction Layer in 5.1 which should provide the means to talk to the device specific interfaces. If this is the same as the ones provided by I2ND, we have a clear synergy and advantage. But it might be very specific and going through just another abstraction layer might be contraproductive. (b) M2M Device 3GPP devices have their own sensors, so they can be M2M Devices. I2ND would then provide the interfaces to the sensor API. Same argumentation as in (a) applies... Our abstraction alyer and their abstraction layer need to be cross checked. Maybe simple plugin architectures might be more simple? (c) Hosting / Dynamic Resource Creation IMHO, the level of granularity for a complete VM is not good enough for the kind of processing we expect for IoT. I expect that we want to create very dynamically new resource functions on the devices/gateway, e.g. for smart filtering. Always sending sown a VM will not help ;-) Maybe I misunderstood Cloud proxy, but if it is just VM hosting, then this is not good enough. I expect Dynamic Resource Creation on the level of OSGi bundles. (d) Reachability IMHO, it is not yet granted that a 3GPP device can be reached from the network side. Usually it is behind Firewalls/NATs. So it can reach out, but not be called back. So I expect mechanisms on the level of WebSockets (or the like) for clean functions calls and eventing. (e) 3GPP network mechanism 3GPP is defining MTC (Machine Type Communications) extension, so we should expect the enabler to make these functionality available to us. This is really low-level communication and management of the devices, e.g. when to wake up, Firmware updates, Configurations, ... Hope this helps ? Where to we collect this requirements? - Ernö From: fiware-iot-bounces at lists.fi-ware.eu [mailto:fiware-iot-bounces at lists.fi-ware.eu] On Behalf Of thierry.nagellen at orange.com Sent: Montag, 17. Oktober 2011 22:07 To: Martin Bauer; sabrina.guerra at telecomitalia.it; rheras at tid.es Cc: fiware-iot at lists.fi-ware.eu Subject: Re: [Fiware-iot] R: R: weekly meeting minutes, 14 Oct 2011 Hi Sabrina, I fully agree with the Martin's point of view. Basically, we have 2 interactions with I2ND: 1- How to reach 3GPP devices: here we expect a clear interface that T5.1 could use as for other devices (Zigbee, etc...) As I2ND has a dedicated GE for 3GPP devices maybe the first approach is to ask them what kind of API they will propose and what parameters of 3GPP devices would be available to send/receive data. If we have a SOAP interface we would be able to host in 3GPP devices part of the gateway, so some smart features from T5.2, T5.3 & T5.4 but we have to be able to manage the first step of connectivity to enable the SOAP session. 2- Cloud proxy: beyond Linux proxy, how could we host the gateway in this cloud proxy? What would be the capabilities (and performance) of this cloud proxy to host gateway services and smart things connectivity. This connectivity should include dedicated communication cards with different standards (wifi, zigbee, blutooth...) Are these cards available in the cloud proxy, how many? And do we have a VM per card as a VM for the gateway? Is it possible to host in this cloud proxy our database services (local database + synchronization with database in the cloud + discovery services)? One of the main concern, as I have understood the cloud proxy, is that there are at least 2 firewalls so how would it be possible to go through these firewalls for IoT services? Best regards Thierry De : fiware-iot-bounces at lists.fi-ware.eu<mailto:fiware-iot-bounces at lists.fi-ware.eu> [mailto:fiware-iot-bounces at lists.fi-ware.eu]<mailto:[mailto:fiware-iot-bounces at lists.fi-ware.eu]> De la part de Martin Bauer Envoyé : lundi 17 octobre 2011 17:49 À : Guerra Sabrina; 'Ricardo de las Heras' Cc : 'fiware-iot at lists.fi-ware.eu' Objet : Re: [Fiware-iot] R: R: weekly meeting minutes, 14 Oct 2011 Hi Sabrina, I am not sure, if the interfaces being discussed are all on the same level. The OMA NGSI interface would rather be between WP5 and WP6 (Data / context management services) , rather than I2ND. Regarding OGC and especially ETSI M2M I'm not 100% sure, but we are more looking at the T5.4/5.2 related interfaces than T5.1. I would see I2ND rather on the lower level communication-related interfaces, but maybe I'm mistaken there. 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<mailto: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> [mailto:fiware-iot-bounces at lists.fi-ware.eu]<mailto:[mailto:fiware-iot-bounces at lists.fi-ware.eu]> On Behalf Of Guerra Sabrina Sent: Montag, 17. Oktober 2011 17:33 To: 'Ricardo de las Heras' Cc: 'fiware-iot at lists.fi-ware.eu' Subject: [Fiware-iot] R: R: weekly meeting minutes, 14 Oct 2011 Hi Ricardo, Thank you for your answer but our doubt is that there are 2 running activities (cross-work between I2ND and IoT and task-force on standards) that have the same objective (defining the interfaces from IoT SE Platform and Cloud Proxy) and we wouldn't want to create an overlap. 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: Ricardo de las Heras [mailto:rheras at tid.es]<mailto:[mailto:rheras at tid.es]> Inviato: Monday, October 17, 2011 5:06 PM A: Guerra Sabrina Cc: 'fiware-iot at lists.fi-ware.eu'; 'Martin Bauer' Oggetto: Re: R: [Fiware-iot] weekly meeting minutes, 14 Oct 2011 HI Sabrina, SensorAPI is the standard used between the concentrator/Gateway and the platform, this is the way used for example in IDAS, so I understand NGSI could apply in the same scope, but out of the scope of the sensors' protocols at the low level (Zigbee, Bluetooth, etc.) layer within T5.1 OK? br, Ricardo. Guerra Sabrina wrote: Hi all, currently it's starting a cross-work between I2ND and IoT to define the interfaces/protocols between IoT SE Platform and Cloud Proxies. In your opinion which are the interactions between this cross-work and task-force you are proposing? 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> [mailto:fiware-iot-bounces at lists.fi-ware.eu] Per conto di Ricardo de las Heras Inviato: Monday, October 17, 2011 11:49 AM A: Martin Bauer Cc: fiware-iot at lists.fi-ware.eu<mailto:fiware-iot at lists.fi-ware.eu> Oggetto: Re: [Fiware-iot] weekly meeting minutes, 14 Oct 2011 Dear Martin, just for clarifying this issue, what I proposed was to create a 'Task force' for defining in the short term how we can make compatible the OGC SensorAPI and OMA NGSI standards, in the same way we followed to present (Dénes) NGSI vs ETSI M2M last Friday on the call. Indeed I proposed this work can be led by NEC and TID at least, so I understand you welcome this proposal;) thanks, br, Ricardo. Martin Bauer wrote: Dear Dénes, all, I slightly updated the minutes from last week's telco. Apparently my voice was not recognized in a few places and some comments were attributed to me that I did not make (maybe they were made by Maarten Los, please check). Sorry for not introducing myself when making a comment. https://forge.fi-ware.eu/docman/view.php/11/492/IoT-Minutes-Telco-10142011.docx Another question: regarding the different standards - it seems that a task force has been established, but this does not become clear from the minutes. We think that NEC, as co-author of the OMA NGSI context management interface, should participate - we also have some knowledge on ETSI M2M and to a lesser degree on the OGC standards. 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<mailto: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> [mailto:fiware-iot-bounces at lists.fi-ware.eu] On Behalf Of Bisztray, Denes (NSN - HU/Budapest) Sent: Freitag, 14. Oktober 2011 14:11 To: fiware-iot at lists.fi-ware.eu<mailto:fiware-iot at lists.fi-ware.eu> Subject: [Fiware-iot] weekly meeting minutes, 14 Oct 2011 Dear All, Please find the meeting minutes under the following link: https://forge.fi-ware.eu/docman/view.php/11/492/IoT-Minutes-Telco-10142011.docx Best, Dénes -- ------------------------------------- Ricardo de las Heras M2M Research Project Manager E-mail:<mailto:rheras at tid.es> rheras at tid.es<mailto:rheras at tid.es> Phone1: (+34) 983 367625 Phone2 OCS: (+34) 91 31 29511 Telefónica I+D<http://www.tid.es> ------------------------------------- ________________________________ 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 Questo messaggio e i suoi allegati sono indirizzati esclusivamente alle persone indicate. La diffusione, copia o qualsiasi altra azione derivante dalla conoscenza di queste informazioni sono rigorosamente vietate. Qualora abbiate ricevuto questo documento per errore siete cortesemente pregati di darne immediata comunicazione al mittente e di provvedere alla sua distruzione, Grazie. This e-mail and any attachments is confidential and may contain privileged information intended for the addressee(s) only. Dissemination, copying, printing or use by anybody else is unauthorised. If you are not the intended recipient, please delete this message and any attachments and advise the sender by return e-mail, Thanks. [rispetta l'ambiente]Rispetta l'ambiente. Non stampare questa mail se non è necessario. -- ------------------------------------- Ricardo de las Heras M2M Research Project Manager E-mail:<mailto:rheras at tid.es> rheras at tid.es<mailto:rheras at tid.es> Phone1: (+34) 983 367625 Phone2 OCS: (+34) 91 31 29511 Telefónica I+D<http://www.tid.es> ------------------------------------- ________________________________ 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 Questo messaggio e i suoi allegati sono indirizzati esclusivamente alle persone indicate. La diffusione, copia o qualsiasi altra azione derivante dalla conoscenza di queste informazioni sono rigorosamente vietate. Qualora abbiate ricevuto questo documento per errore siete cortesemente pregati di darne immediata comunicazione al mittente e di provvedere alla sua distruzione, Grazie. This e-mail and any attachments is confidential and may contain privileged information intended for the addressee(s) only. Dissemination, copying, printing or use by anybody else is unauthorised. If you are not the intended recipient, please delete this message and any attachments and advise the sender by return e-mail, Thanks. [rispetta l'ambiente]Rispetta l'ambiente. Non stampare questa mail se non è necessario. -------------- next part -------------- An HTML attachment was scrubbed... URL: <https://lists.fiware.org/private/old-fiware-iot/attachments/20111017/d91d8eb1/attachment.html> -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.gif Type: image/gif Size: 677 bytes Desc: image001.gif URL: <https://lists.fiware.org/private/old-fiware-iot/attachments/20111017/d91d8eb1/attachment.gif>
You can get more information about our cookies and privacy policies clicking on the following links: Privacy policy Cookies policy