TC2.8 - IOT Protocol Inquiries

×

Warning message

  • You can't delete this newsletter because it has not been sent to all its subscribers.
  • You can't delete this newsletter because it has not been sent to all its subscribers.

Test Case Title

TC2.8 - IOT Protocol Inquiries

Goal

The Inquires modality of communication consists in the fact IOT Devices can call all its subscribers (IOT Brokers typically) to get some instruction. This protocol can be also applied at level of IOT Broker, or at level of IOT Directory, the Inquires modality of communication consists in the fact that it would provide the list of registered IoT devices according to a given parameter

Prerequisites

Using a PC or Mobile with a web browser. You need a Snap4City account. Sensors and actuators for reading.

The following functionalities are available only for a specific Snap4City account with specific privileges.

Expected successful result

Generation of a flow for querying the Context Broker about devices of a given type

Steps

 

 

The Inquires modality of communication consists in the fact that each single IOT Device can call all its subscribers (IOT Brokers typically) to get some instruction. This protocol is implemented not in all IOT devices. On the other hand, this protocol can be also applied at level of IOT Broker, or at level of IOT Directory, the Inquires modality of communication consists in the fact that it would provide the list of registered IoT devices according to a given parameter.

In the following test, you can start testing this requirement by following the sequence of action for IOT Broker. So that a Snap4City Application ask to the IOT broker to get the list of IOT devices registered:

  • Flow: IOT device/application requests to the IOT Directory of all its subscribers [of a given type] →  get list → send the inquire to all of them
  • Flow: IOT device perform an inquire to all its subscribers [of a given type] →  get list → send the inquire to all of them