Page 133 - Reference framework for integrated management of an SSC - A U4SSC deliverable on city platforms

• Support real-time treatment of the data received from the Acquisition Layer through modules
such as Complex Event Processor engines.
• Support Batch processing of data received through ETL processes machine learning.

• Support analytical treatment of data through, for example, BI processes.

• Support GIS treatment of the data received, allowing georeferencing, making geographical
queries, etc.

• Security in data access, which user/role is accessing each data set is controlled.

6.3.8.3.3 Interoperability Layer

The Interoperability Layer facilitates the provision of services in the field of the Smart City by offering
interfaces and functionalities such as the Development Kit and Open Data, which will be used to
implement the services that will be delivered to customers:

• Publish APIs that can be consumed from the Service Layer; it would be interesting to include
the concept of API Manager.

• Ability to interconnect between applications and between platforms.
• Access from the Platform to external services.

• Publish open data through an Open Data Portal/Repository.

• A Development Kit that includes SDKs and APIs allows Services to be built within the Service
Layer.

• All this is with the security integrated into APIs, Development Kit, and Open Data access.

• Based on a set of standards-based APIs, the Interoperability Layer must guarantee the portability
of applications between cities and between platforms so that a true ecosystem of applications
with critical mass is created, which lowers the barrier of access to application developers.
• The APIs exposed by the Interoperability Layer will be accessible for the developer community
to use, so following the general trend, it should be a REST API.

• APIs must support different data access modes, including Push mode (subscription and
notification) and Pull method (request and response). Georeferenced queries should also be
supported.

• The data access model offered by the API will be agnostic for the particular data model; however,
to enable interoperability, it must use a transport format compatible with any existing model.
It is recommended to follow the OneM2M model for reference.

Reference framework for integrated management of an SSC | June 2023 119