[Fiware-iot] IoT Gateway Characterization

[Tobias Jacobs]

Hi Carlos,

welcome back; I hope you had great vacations!

I have two questions/comments on the approach you describe below:


1)
As far as I understand your approach below is to handle the IoT Gateway like an NGSI entity, but you write at the same time that the goal is to register it.

In the NGSI-world, registering does not include specifying attribute values (because the registerContext operation was designed to register NGSI data sources where the actual attribute values can be retrieved).

So for publishing the information below, you would need to do an updateContext operation, and then the gateway will be then represented as an NGSI data entity, not as an NGSI data source.

Alternatively, if the goal is to register the gateway using the registerContext operation, the information like GATEWAY_ID etc. will rather have to be provided as registration metadata instead.



2)
Have there been any discussions about the usage of more canonical type names, e.g. to use something like "org.fiware.entitytype.iotgateway" instead of "IoT_Gateway". After all, types are by NGSI intended to be URIs (but I know that up to now in fiware this has not played such a big role).

Best regards
Tobias

From: fiware-iot-bounces at lists.fi-ware.org [mailto:fiware-iot-bounces at lists.fi-ware.org] On Behalf Of CARLOS RALLI UCENDO
Sent: Mittwoch, 19. August 2015 10:59
To: fiware-iot at lists.fi-ware.org
Subject: [Fiware-iot] IoT Gateway Characterization

Dear colleagues,

This sprint (4.4.2 - August) I am starting to explore how to handle edge network topology in FIWARE.
Related userstory/JIRA ticket:  https://jira.fiware.org/browse/IOT-373

In our F2F meeting at Heidelberg, we agreed to use the same NGSI model/APIs/components etc so we easy its access by developers and integrators and we also "eat our own dog food".

Initially, I am developing a simple python script to register IoT Gateways that I will include as part of the FIGWAY suite that we deliver together with IDAS (we use it to simulate or connect sensors/actuators at RaspberryPI or nay other python-capable gateway/laptop/desktop):
  https://github.com/telefonicaid/fiware-figway/tree/master/python-IDAS4

I did not find any good resource to characterize IoT Gateways so I will go the way proposed below.
If you guys know any other resource to consider or have comments/amendments, just let me know.


***************

For the Gateway characterization we will use the following description:

Entity ID: [GATEWAY_ID]
Entity Type: IoT_Gateway

Attributes: Recommendation: Fill in all the ones listed below (use N/A, 0 or NONE, if necessary)

GATEWAY_NAME: Name of this gateway.
GATEWAY_ID: Unique identifier within at least a FIWARE Service.
GATEWAY_TYPE: Type of physical Device. E.g: RaspberryPI, ArduinoYUN, iphone5, samsumgGalaxy4, etc.
COMM_INTERFACES: Number of Internet communication interfaces (not inlcuing interfaces to IoT devices, normally 1).
COMM_INTERFACE1_TYPE: Layer2/Layer1 Technology of an Internet interface (wifi, ethernet, 2G, 3G, 4G/LTE, etc).
COMM_INTERFACE1_IPv4: IPv4 address of an Internet interface.
COMM_INTERFACE1_IPv6: IPv6 address of an Internet interface (if any).
IOT_TECHNOLOGIES: Number of IoT Interfaces
IOT_TECHNOLOGY1_TYPE: Type of an IoT interface (Z-wave, Zigbee, 6LowPAN/IEEE802.15.4, Wifi, Bluetooth4.0, etc)
IOT_TECHNOLOGY1_DEVICES: Number of connected devices to an IoT interface (can be aprox or set to the maximum expectec if unknown)
IOT_AGENTS: Number of IoT Agents installed in the gateway
IOT_AGENT1_NAME: IoT Agent Name
IOT_AGENT1_ID: IoT Agent ID
***************



Cheers,
--

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

Carlos Ralli Ucendo (carlos.ralliucendo at telefonica.com<mailto:carlos.ralliucendo at telefonica.com>)

Cell: +34696923588

Twitter: @carlosralli

Blog: http://the-internet6.blogspot.com.es<http://the-internet6.blogspot.com.es/>

Telefónica I+D SAU

Madrid, Spain

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

Follow FIWARE project (Future Internet Services Core Platform):

Website:  http://www.fi-ware.<http://www.fi-ware.eu/>org

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

Twitter: @fiware

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

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

________________________________

Este mensaje y sus adjuntos se dirigen exclusivamente a su destinatario, puede contener información privilegiada o confidencial y es para uso exclusivo de la persona o entidad de destino. Si no es usted. el destinatario indicado, queda notificado de que la lectura, utilización, divulgación y/o copia sin autorización puede estar prohibida en virtud de la legislación vigente. Si ha recibido este mensaje por error, le rogamos que nos lo comunique inmediatamente por esta misma vía y proceda a su destrucción.

The information contained in this transmission is privileged and confidential information intended only for the use of the individual or entity named above. If the reader of this message is not the intended recipient, you are hereby notified that any dissemination, distribution or copying of this communication is strictly prohibited. If you have received this transmission in error, do not read it. Please immediately reply to the sender that you have received this communication in error and then delete it.

Esta mensagem e seus anexos se dirigem exclusivamente ao seu destinatário, pode conter informação privilegiada ou confidencial e é para uso exclusivo da pessoa ou entidade de destino. Se não é vossa senhoria o destinatário indicado, fica notificado de que a leitura, utilização, divulgação e/ou cópia sem autorização pode estar proibida em virtude da legislação vigente. Se recebeu esta mensagem por erro, rogamos-lhe que nos o comunique imediatamente por esta mesma via e proceda a sua destruição
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.fiware.org/private/fiware-iot/attachments/20150819/646294e4/attachment.html>