[Fiware-iot] gateway architecture

[Bisztray, Denes (NSN - HU/Budapest)]

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