Page 32 - U4SSC Data and API requirements for centralized smart city platforms

5 Use Cases

The following use cases justify the importance and the applicability of the SCHub:

1) Data collection of common property measurements

2) Sensor measurement data discovery
3) Retrieval of sensor measurements

5.1 Data collection of common property measurements

Sensors that are deployed in a SC can measure similar properties/variables (i.e., temperature,
network coverage, battery capacity) regardless their types, manufacturers, and uses (e.g., parking,
electricity consumption, environmental conditions). The SCHub unified API will enable access to
the common measurement properties of any device in a unified way.

5.1.1 Description

The SCHub API provides an abstract method that allows the unified data collection, which is
produced by sensors installed in a SC. Each event measured by a sensor is described in the
SCHub events’ taxonomy with a specific schema. The SCHub layer transforms the messages that
are produced by sensors to SCHub events. When a client of the SCHub API requests access to a
specific event of the taxonomy, the collected data are compliant with the SCHub schema, regardless
the schema that is used by the sensor manufacturer.

In this regard, when a set of devices – regardless their purpose – measures a common property, the
SCHub will provide this data in a standardized way with the use of the unified SCHub API.

5.1.2 Requirements

– the SCHub taxonomy for the requested property has been agreed and standardized.

– the SCHub IoT gateway for the accessed sensors has been implemented according to the
SCHub schema specifications.

5.1.3 Scenario

In this scenario, data about the GSM network coverage is requested from two different sensor
types: a parking sensor and an environmental sensor. The sensors are developed by different
manufacturers, and they are not compatible. Both the sensors are discovered and provide GSM
network coverage data (Figure 13).

22