[Fiware-iot] Relationship between the IoT Gateway and the I2ND Cloud Edge

[thierry.nagellen at orange.com]

Hi all,

 

Regarding Cloud Edge, as I've understood they would propose a linux foundation where IoT gateway GEs could be hosted with a dedicated profile but no Virtual Machine. We could consider that the cloud edge could host without any changes IoT Gateways GEs which could interact with IoT Backend GEs. In this way there is no direct impact for our GEs and no impact for Cloud Edge GE itself.

 

But the critical point would be which kind devices could be reachable in the home environment and what kind of protocol adapters are required, especially because Cloud Edge is also associated to an hardware and this hardware should not have the IoT interface (no drivers for Zigbee, Ogc or other additional hardware). 

What we can demonstrate is that Cloud Edge could host the IoT Gateway without any concrete dedicated  technical interface which could be provide in the future by 3rd parties.

 

In this scenario I do not see any NGSI/ETSI M2M  impact on Cloud Edge.

 

The Ericsson gateway is another instantiation and as there is also an hardware implementation, we will e able to show how home gateway or network gateway in a city, or a mobile android gateway could support the same GEs and exchanges data and share the same IoT resources management model.

 

BR

 

THierry

 

De : fiware-iot-bounces at lists.fi-ware.eu [mailto:fiware-iot-bounces at lists.fi-ware.eu] De la part de Fici Gian Piero
Envoyé : mercredi 14 mars 2012 12:51
À : fiware-iot at lists.fi-ware.eu
Objet : [Fiware-iot] Relationship between the IoT Gateway and the I2ND Cloud Edge

 

Hi Thierry and all,

I would like to raise a point that we may overlooked lately, that is the interaction between the IoT chapter and the I2ND chapter.

Since the introduction in our reference architecture of the Gateway we did not considered the relationship between the IoT Gateway and the Cloud Edge defined in the I2ND chapter.

 

One aspect to clarify is the scope of the two elements. The CE is intended for domestic use (and it is implemented by the Technicolor asset Cloud Proxy). Is the Ericsson gateway more for a network use? Or is it another type of home gateway? In the latter case there is an overlapping between the two architectural elements that we may want to explain.

 

Another aspect is the network protocol used by these two elements to connect to the Backend. Last year we discussed with I2ND about the connection between the Cloud Edge and the IoT Services Enablement platform and we reached an agreement to use the TI ZigBee implementation since TI is involved both in the IoT and in the I2ND chapters. In the Madrid GA though the architectural requirements became more tight and it was decided the Backend has only two interfaces exposed by its Device Frontend GE, that is ETSI M2M and NGSI. This has an impact on the I2ND architecture too, since it means either the Cloud Edge has to implement the ETSI M2M specification or it has to connect to the Device Frontend GE of the IoT Gateway instead of the Backend.

 

What do you think about these two points? Especially Ericsson I think may have something to say about them.

 

Best regards,

Gian Piero Fici and Sabrina Guerra

Questo messaggio e i suoi allegati sono indirizzati esclusivamente alle persone indicate. La diffusione, copia o qualsiasi altra azione derivante dalla conoscenza di queste informazioni sono rigorosamente vietate. Qualora abbiate ricevuto questo documento per errore siete cortesemente pregati di darne immediata comunicazione al mittente e di provvedere alla sua distruzione, Grazie. 

This e-mail and any attachments is confidential and may contain privileged information intended for the addressee(s) only. Dissemination, copying, printing or use by anybody else is unauthorised. If you are not the intended recipient, please delete this message and any attachments and advise the sender by return e-mail, Thanks. 

 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/20120314/a88990aa/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/20120314/a88990aa/attachment.gif>