Hi Carlos and Marc, what Marc writes makes technical a lot of sense in my opinion. A gateway could even download its configuration information on-demand (e.g. when receiving a subscription). Instead of using NGSI-10 context entities for this configuration information, could you also imagine to use NGSI-9 ContextRegistration information? NEC does it already like this in the IoT Broker when dealing with associations (assembling entities from other entities). The workflow here is like this: - IoT Broker receives e.g. a query for entity "ConferenceRoom" and attribute "temperature" - IoT Broker asks IoT Discovery for ContextRegistrations related to this entity/attribute combination - IoT Discovery returns a ContextRegistration which does not provide any context providers, but instead in the metadata contains information how to assemble the "temperature" attribute value as an average from attributes of two entities "Sensor_A" and "Sensor_B". - IoT Broker then tries to retrieve information about these two sensor entities, computes the average, and returns it to the requesting client. So here the information on how to create entity information is contained in the context registration and, in the IoT Backend, maintained by the IoT Discovery GE. Best regards Tobias From: fiware-iot-bounces at lists.fiware.org [mailto:fiware-iot-bounces at lists.fiware.org] On Behalf Of marc.capdevielle at orange.com Sent: Donnerstag, 10. September 2015 17:28 To: fiware-iot at lists.fi-ware.org Subject: Re: [Fiware-iot] IoT Gateway Characterization Dear Carlos, What I had in mind at the F2F meeting in Heidelberg was that an IoT Gateway could subscribe to the Broker for configuration management and provisioning. For our work in the Gateway Data Handling GE, we now have two gateway-level components (a small forwarding broker and a CEP) each of them requiring some custom configuration/provisioning. Currently this provisioning is done in custom property files and a specific HTTP configuration API (this is also how the IoT Agent does it). A much unified and simpler approach, would be for the Fiware project to define a common way for all IoT gateway services to access (subscribe to ?) these configuration resources on the broker. Each gateway could therefore have: 1 - a NGSI registration process for discovery/availability like Tobias proposes, 2 - a dedicated Context Entity updated by the gateway itself to expose some gateway/services specific data, like you propose, 3 - and one or more NGSI subscriptions to various services-related Context Entities for configuration/management. The first would let the NGSI network know about the availability of a gateway, the second about its current capabilities/reachability and the later would allow management of the gateway services simply by updating the configuration resources on the broker. The gateway would then need a single initial information to interact with a NGSI network: the address of the broker. Did you have something similar in mind ? Best regards, Marc Capdevielle Le 19/08/2015 10:59, CARLOS RALLI UCENDO a écrit : 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.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 _______________________________________________ Fiware-iot mailing list Fiware-iot at lists.fi-ware.org<mailto:Fiware-iot at lists.fi-ware.org> https://lists.fi-ware.org/listinfo/fiware-iot _________________________________________________________________________________________________________________________ Ce message et ses pieces jointes peuvent contenir des informations confidentielles ou privilegiees et ne doivent donc pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce message par erreur, veuillez le signaler a l'expediteur et le detruire ainsi que les pieces jointes. Les messages electroniques etant susceptibles d'alteration, Orange decline toute responsabilite si ce message a ete altere, deforme ou falsifie. Merci. This message and its attachments may contain confidential or privileged information that may be protected by law; they should not be distributed, used or copied without authorisation. If you have received this email in error, please notify the sender and delete this message and its attachments. As emails may be altered, Orange is not liable for messages that have been modified, changed or falsified. Thank you. -------------- next part -------------- An HTML attachment was scrubbed... URL: <https://lists.fiware.org/private/fiware-iot/attachments/20150911/3fd74173/attachment.html>
You can get more information about our cookies and privacy policies clicking on the following links: Privacy policy Cookies policy