[Fiware-iot] actuation

[CARLOS RALLI UCENDO]

Hi Tobias,

Yes we provide actuation in the pair oT-Agent+ContextBroker in the following way:

- IoT Agents create a per-device entity in the ContextBroker. Observable parameters are attributes of this entity that are fed using NGSI10 updates.
- For commands, IoT Agents make themselves Context Providers of the command related attributes using NGSI9.
- Whenever an update to a command attribute is received at the ContextBroker, it is forwarded to the IoT Agent as long as it is registered as Context provider for that attribute.
- The IoT Agent sends back an OK to the ContextBroker and it triggers a command against the device following the specific southbound IoT attribute.

We are discussing to implement an status parallel attribute to query/subscribe to the command delivery status or result but this is not fixed today.

Currently this is implemented in the IoT Agent of UL2.0 and MQTT and the OMA LWM2M/CoAP IoT Agent.
However, for the first one we've reported a bug to ContextBroker team (we get the command in XML and we expect it in JSON format).
Because of this today we simulate commands sending an NGSI update to the IoT Agent (as if we were the CB).
This bug is expected to be addressed during this sprint so it should be fixed for May 2015.

Cheers,
--

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

Carlos Ralli Ucendo (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

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

De: Tobias Jacobs <Tobias.Jacobs at neclab.eu<mailto:Tobias.Jacobs at neclab.eu>>
Fecha: lunes, 20 de abril de 2015 11:26
Para: "fiware-iot at lists.fi-ware.org<mailto:fiware-iot at lists.fi-ware.org>" <fiware-iot at lists.fi-ware.org<mailto:fiware-iot at lists.fi-ware.org>>
Asunto: [Fiware-iot] actuation

Hi all,

As we have the actuation topic on the agenda of you F2F meeting, maybe we could start discussing about how to realize it. So I would like to ask you guys


-          Whether in your implementations you enable actuation already, and, if yes, what is the protocol/NGSI operations/whatever you use?

-          IF you have any constraints, requirements etc. about how FIWARE IoT actuation should look like

-          If you have any specific concepts you think would be useful to reuse.

Best regards
Tobias

________________________________

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/20150420/cd33e6b8/attachment.html>