[Fiware-iot] R: Overall description of IoT GEs

[Fici Gian Piero]

Hi Sebastian and Carlos,
the description of the GIP capability contained in Sebastian's e-mail does not correspond entirely to the ETSI specifications (see the M2M functional architecture rel. 00002ed121v1111 or 00002ed211v2012).
In the specifications it is stated the GIP provides the functionality of the interworking between non ETSI compliant devices and the GSCL and it is the GIP which communicates via reference point dIa with GSCL (see chapter 5.3.9 in the specification of the first release, or annex X in the one of the second release, and the description of chapter 6.1 in both specifications).
[cid:image004.png at 01CE4275.DDA2BD80][cid:image006.png at 01CE4275.DDA2BD80]
Following the definition of GIP written in the standard, the protocol used for the connection of Legacy devices 'd' (such as the Gateway Protocol Adapter GE) is not dIa  (if only for the fact that in that case the Legacy device would be a compliant ETSI Application and there would be no need of a GIP functionality), therefore it is the task of the GIP to provide the interworking between the 'd' protocol and the GSCL and not of the Gateway Protocol Adapter GE to plug into the gateway directly by means of the ETSI standard.

In the specification of the second release there is also the possibility for the GIP to be an ETSI application external to the GSCL, but we cannot provide it because the implementation of the ETSI M2M standard is not in the roadmap for Telecom Italia.

Currently the ZPA, our implementation of the Gateway Protocol Adapter GE, is providing 2 different northbound interfaces: Generic Device Access API and NGSI. The Generic Device Access API was the interface we developed for the integration with the Gateway Device Management GE by Ericsson. The NGSI interface was discussed and agreed during the recent Paris F2F meeting in order to have an interface with the Data Handling GE and it is currently under development.
In our opinion we should start from these interfaces to discuss a possible integration with the ETSI M2M Gateway through the GIP.

Feel free to ask for further clarifications or details.
Best regards,
Gian Piero and Sabrina



Da: fiware-iot-bounces at lists.fi-ware.eu [mailto:fiware-iot-bounces at lists.fi-ware.eu] Per conto di Wahle, Sebastian
Inviato: giovedì 25 aprile 2013 09:45
A: CARLOS RALLI UCENDO
Cc: fiware-iot at lists.fi-ware.eu
Oggetto: Re: [Fiware-iot] Overall description of IoT GEs

Hi Carlos,

"- GW Protocol Adapter (T.Italia)
   As planned before. Only one modification to be done in the roadmap (new EPIC/feature to come): develop an NGSI northbound interface/connector."

I think that the Protocol Adapter shall support the ETSI interface since ETSI explicitly defines a so called GIP (Gateway Interworking Proxy) to interface with ZigBee, KNX, Wireless M-Bus, Bluetooth etc. It is an inherent design feature of an IoT Gateway to support multiple local area network technologies and connect such devices to a wide area network. Therefore, I see the "GW Protocol Adapter" plugging into the gateway directly by means of the ETSI standard.

Best,
Sebastian

Von: fiware-iot-bounces at lists.fi-ware.eu [mailto:fiware-iot-bounces at lists.fi-ware.eu] Im Auftrag von CARLOS RALLI UCENDO
Gesendet: Mittwoch, 24. April 2013 11:43
An: fiware-iot at lists.fi-ware.eu
Betreff: [Fiware-iot] Overall description of IoT GEs

Dear colleagues,

I was requested by the project coordination to make a summary of all modifications, on-going work and planned/re-planned deliveries of IoT GEs.

I made the following list included below. Please, if you have any major comment, let me know.
Thierry, I think we can use this as basic material for one of the introduction slides of IoT chapter in the forthcoming June review.

*****

- BE Things Management GE

Released in R1 but eliminated later on, as it has been split in two: IoT Broker & Conf.Man,



- IoT Broker GE (NEC)

 "New" one for R2.2 but SW and documents are actually the ones of that subcomponent in R1 BE Things Management



- Configuration Manager GE (TID)

 "New" one for R2.2 but SW and documents are actually the ones of that subcomponent in R1 BE Things Management

A new version will be provided in R2.3 together will all documents.

There will be, in principle, 3 implementations of this GE: TID, NEC (with Geo-discovery) and UoSurrey (with semantic Discovery)




- BE Discovery GE: (UoSurrey).
Originally planned for R2.2 but it has been eliminated as a GE (Roadmap updated accordingly on April 23th)
Functionality will be delivered as part of the Configuration Manager in R2.3 (maybe it will be re-planned to R3.x).
Related features/epics have been moved into the Conf.Man section with a short notice for readers. UoS is performing a review right now and features/EPICs may change in the short term.




- BE Dev Man (TID, previously NSN)

  Planned for major R2 -> R2.3

  It will be the combination of two assets (IDAS + IoT-Agent). Features/Epics to change significantly before R2.3 delivery (on-going task).



- BE Advanced Connectivity:

 Eliminated. Functionalities will be developed as part of the BE Dev.Man. Features/Epics dropped from Roadmap by now.



- BE Security:

 Eliminated. Functionalities are being developed/deployed as part of the overall Fi-WARE Security approach (Sec. chapter GEs).

  Features/Epics dropped from Roadmap by now.





- GW Dev Man (Fraunhofer, previously Ericsson)

    This GE will be significantly updated very soon and maybe even re-planned because of Ericsson withdrawal. Fraunhofer joined us jus 1 week ago...



- GW Data Handling (Orange, ATOS)

   There is only one GE with 2 implementations (Orange and ATOS). Architecture Wiki has been modified accordingly. Roadmap now under revision.




- GW Protocol Adapter (T.Italia)

   As planned before. Only one modification to be done in the roadmap (new EPIC/feature to come): develop an NGSI northbound interface/connector.


- GW Advanced Connectivity:

 Eliminated. Functionalities will be developed as part of the GW Dev.Man. Features/Epics dropped from Roadmap by now.



- GW Security:

 Eliminated. Functionalities will be developed as part of the GW Dev.Man. Features/Epics dropped from Roadmap by now.
*****

Best regards,
--

------------------------------------------------------------------------------------------------------------------------

Carlos Ralli Ucendo (ralli at tid.es<mailto:ralli at tid.es>)

Cell: +34696923588

Twitter: @carlosralli

IPv6 Blog: http://the-internet6.blogspot.com.es

Product Development & Innovation (Telefónica Digital)

Telefónica I+D SAU

Madrid, Spain

------------------------------------------------------------------------------------------------------------------------

Follow FI-WARE project (Future Internet Services Core Platform):

Website:  http://www.fi-ware.eu

Facebook: http://www.facebook.com/pages/FI-WARE/251366491587242

Twitter: @fiware

LinkedIn: http://www.linkedin.com/groups/FIWARE-4239932

------------------------------------------------------------------------------------------------------------------------

________________________________

Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra política de envío y recepción de correo electrónico en el enlace situado más abajo.
This message is intended exclusively for its addressee. We only send and receive email on the basis of the terms set out at:
http://www.tid.es/ES/PAGINAS/disclaimer.aspx
Questo messaggio e i suoi allegati sono indirizzati esclusivamente alle persone indicate. La diffusione, copia o qualsiasi altra azione derivante dalla conoscenza di queste informazioni sono rigorosamente vietate. Qualora abbiate ricevuto questo documento per errore siete cortesemente pregati di darne immediata comunicazione al mittente e di provvedere alla sua distruzione, Grazie.

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

[cid:00000000000000000000000000000003 at TI.Disclaimer]Rispetta l'ambiente. Non stampare questa mail se non è necessario.

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.fiware.org/private/old-fiware-iot/attachments/20130426/a278e662/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image001.emz
Type: application/octet-stream
Size: 3603 bytes
Desc: image001.emz
URL: <https://lists.fiware.org/private/old-fiware-iot/attachments/20130426/a278e662/attachment.obj>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image004.png
Type: image/png
Size: 3644 bytes
Desc: image004.png
URL: <https://lists.fiware.org/private/old-fiware-iot/attachments/20130426/a278e662/attachment.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image006.png
Type: image/png
Size: 41862 bytes
Desc: image006.png
URL: <https://lists.fiware.org/private/old-fiware-iot/attachments/20130426/a278e662/attachment-0001.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: logo Ambiente_foglia2.jpg
Type: image/jpeg
Size: 677 bytes
Desc: logo Ambiente_foglia2.jpg
URL: <https://lists.fiware.org/private/old-fiware-iot/attachments/20130426/a278e662/attachment.jpg>