[英]Fiware: context registration's providingApplication attribute - IDAS UltraLight
Each time that a new device connects to an IoT agent, the IoT agent sends an updateContext to the context broker and a new context entity is created. 每次新设备连接到IoT代理时,IoT代理都会将updateContext发送到上下文代理,并创建一个新的上下文实体。 And if this device has some lazy attribute the IoT agent will send a contextentityRegistration in order to create a context registration, to indicate to the context broker how can connect to the device.
并且,如果此设备具有某些惰性属性,则IoT代理将发送contextentityRegistration以便创建上下文注册,以向上下文代理指示如何连接到该设备。
But when the Context Registration is created, I'm not sure about the value that will be assigned to the providingApplication attribute. 但是,当创建上下文注册时,我不确定将分配给providerApplication属性的值。
Although I'm not sure, I believe the correct one it's the first option, because the device normally won't understand the NGSI protocol, and the IoT agent should translate the request before sending it to the device. 尽管我不确定,但我相信正确的方法是第一个选择,因为设备通常不理解NGSI协议,并且IoT代理应在将请求发送到设备之前转换请求。 If that's the case, then:
如果是这样,那么:
Thanks in advance, any help would be grateful. 在此先感谢您的帮助。
2) The property "commands" is used to define attributes of the ContextBroker entity that will actually tirgger a command to the device if they are updated using the NGSI API. 2)属性“命令”用于定义ContextBroker实体的属性,如果使用NGSI API更新了该命令,则该属性实际上会触发对设备的命令。 This means tahta developers are able to read observations and also send commands just using one API (NGSI) with no knowledge of the specific device technology or protocol.
这意味着tahta开发人员能够在不了解特定设备技术或协议的情况下,仅使用一个API(NGSI)即可读取观察结果并发送命令。
1) In UL2.0 lazy attributes are not supported so far. 1)在UL2.0中,目前尚不支持惰性属性。 Please refer to the other IoT Agents for that.
请参考其他物联网代理。 Normally the IoT Agent IP:Port should be used for that.
通常,应使用IoT代理IP:Port。
Cheers, 干杯,
声明:本站的技术帖子网页,遵循CC BY-SA 4.0协议,如果您需要转载,请注明本站网址或者原文地址。任何问题请咨询:yoyou2525@163.com.