Page 30 - U4SSC Data and API requirements for centralized smart city platforms
P. 30

5)  Portability between platforms and cities (8.4, ITU-T Y.4201, 2018).
            6)  Representational state transfer (REST) API compliant (8.4, ITU-T Y.4201, 2018).

            7)  Interoperability of data flows through standardized interfaces (8.2, ITU-T Y.4200, 2018).

            8)  Open interfaces handling data acquisition, service interactions and interoperability (8, ITU-T
                Y.4200, 2018).

            The SCHub is aiming to provide an open standard in these areas as required by the overall
            Recommendation ITU-T Y.4201.



            4.3.2  SCHub and FIWARE/SAREF

            Initiatives like the FIWARE Smart Data Models and SAREF4CITY ontologies provide the guidelines
            for the data models used by a SCP APIs in order to simplify the integration of services at the data
            layer. Compliance with these initiates is alignment with the SCHub architecture as any SCHub
            client that has been using these data models will be able to seamlessly integrate with the SCHub.
            However, the SCHub is data model agnostic and is capable of supporting additional data models
            or representations that are used currently in regions outside Europe or will appear in the future and
            may be more widely adopted or even standardized. The goal of the SCHub northbound interfaces
            is to make is as seamless as possible for its users to consume the data from any connected data
            source.



            4.3.3  SCHub and IDS / Gaia-X

            The architecture and goals of IDS and Gaia-X are orthogonal to those of SCHub. As SCHub does not
            require any special compliance or interoperability of the southbound interface, data providers can
            be compliant with IDS, Gaia-X or any other similar initiative. In the SCHub context, this is abstracted
            by the telemetry gateways, which take care of communicating using the protocol and data models
            specified by each data provider. The use of standardized data and infrastructure providers does
            however make the integration with the SCHub easier as the communication gateways that support
            these protocols can be re-used.


            4.4     Connecting people and materials: an innovation and supply chain hub


            The existence of such an SC Hub can also serve additional roles. For example, cities are meeting
            spaces for people and in this regard, the SC Hub could connect people who can co-create with their
            local governments, and people who want to innovate and launch their own startups. The SC Hub
            concept could play this role: it can bring together people and governments, while it can simulate a
            typical innovation hub via offering access to third-party virtual spaces for mentoring and coaching.
            Additionally, the involved partners could have access to startup cloud-based services via the SC
            Hub, such as CRM, e-mail, portal, and so on. Cities also enable material flows between companies
            and citizens. In this regard, the SC Hub could control the entire supply chain in means that could



             20
   25   26   27   28   29   30   31   32   33   34   35