d3.4 prototype refined after st user test … · d3.4 prototype refined after 1st user test and...

D3.4

PROTOTYPE REFINED AFTER 1ST USER TEST AND FURTHER PLATFORM FOR USER TEST

2ND ITERATION June 2014

ABSTRACT

This document is a technical description of the “Smart City Platform” for user test (2nd iteration).

© FI-CONTENT 2 consortium 2014

D3.4 V1.0 – June 2014

of 35

This document is a deliverable of the FI-CONTENT 2 integrated project supported by the European Commission under its FP7 research funding programme, and contributes to the FI-PPP (Future Internet Public Private Partnership) initiative.


D3.4 V1.0 – June 2014

of 35

DISCLAIMER

All intellectual property rights are owned by the FI-CONTENT2 consortium members and are protected by the applicable laws. Except where otherwise specified, all document contents are: “© FI-CONTENT2 project - All rights reserved”. Reproduction is not authorised without prior written agreement. All FI-CONTENT2 consortium members have agreed to full publication of this document. All FI-CONTENT2 consortium members are also committed to publish accurate and up to date information and take the greatest care to do so. However, the FI-CONTENT2 consortium members cannot accept liability for any inaccuracies or omissions nor do they accept liability for any direct, indirect, special, consequential or other losses or damages of any kind arising out of the use of this information.

DELIVERABLE DETAILS

[Full project title]: Future media Internet for large-scale CONTent experimENTation 2 [Short project title]: FI-CONTENT 2 [Contract number]: 603662 [WP n°]: WP3: City guide platform [WP leader]: Olivier DUVOID, EBIZ [Deliverable n°]: D3.4 [Deliverable title]: Prototype refined after 1st user test and further platform for user test 2nd iteration [Deliverable nature]: Prototype (P) [Dissemination level]: Public (PU) [Contractual delivery date]: M15 - June 2014 [Actual delivery date]: 25th of July 2014 [Editor]: Olivier DUVOID, EBIZ [Internal Reviewers]: Dirk Krause, PIX / Farid Benbadis, TCF [Suggested readers]: Executives in Internet services companies [Keywords]: City Guide, Services, Enablers [File name]: FI-CONTENT 2_WP3-006_D3.4_V1.0.docx


D3.4 V1.0 – June 2014

of 35

EXECUTIVE SUMMARY

This document aims to technically describe the “Smart City Guide” platform (SCG). The “Smart City Guide” (SCG) platform is a portfolio of functions, designed to foster the development and uptake of smart of city applications based on future internet technologies. This portfolio consists of a set of technical functionalities provided by specific enablers (from FI-CONTENT) and generic enablers (FI-WARE).


D3.4 V1.0 – June 2014

of 35

LIST OF AUTHORS

Organisation Author

Orange Arnaud Brun

ImaginLab Pierre François

FhG / FOKUS Robert Seeliger Miggi Zwicklbauer Christopher Krauß

Thales Farid Benbadis

DFKI Stefan Lemme

Pixelpark Dirk Krause

eBiz Olivier Duvoid Loïc Ortola


D3.4 V1.0 – June 2014

of 35

TABLE OF CONTENTS

EXECUTIVE SUMMARY .............................................................................................................. 4�LIST OF AUTHORS .................................................................................................................... 5�TABLE OF CONTENTS ............................................................................................................... 6�LIST OF FIGURES ..................................................................................................................... 9�ABBREVIATIONS .................................................................................................................... 10�1 - INTRODUCTION ................................................................................................................. 11�

1.1 - Overview .......................................................................................................................................... 11�

1.2 - Terminology ...................................................................................................................................... 11�

2 - SMART CITY PLATFORM ARCHITECTURE ........................................................................... 13�2.1 - Architecture Description ................................................................................................................... 14�

2.1.1 - App Generation ......................................................................................................................... 14�2.1.2 - Feature Building Blocks ............................................................................................................. 15�2.1.3 - Data, Media and Content .......................................................................................................... 15�

2.2 - Specific Enablers .............................................................................................................................. 15�

2.3 - Generic Enablers .............................................................................................................................. 16�

3 - SMART CITY PLATFORM - RELEASE 06/14 ......................................................................... 17�3.1 - App Generator [NEW] ....................................................................................................................... 17�

3.1.1 - What you get ............................................................................................................................. 17�3.1.2 - Why to get it .............................................................................................................................. 17�3.1.3 - Documentation .......................................................................................................................... 17�

3.2 - Recommendation as a Service [NEW] .............................................................................................. 17�


3.3 - Open City Database ......................................................................................................................... 18�


3.4 - 3D-Map Tiles [NEW] ......................................................................................................................... 18�


3.5 - POI Storage [NEW] .......................................................................................................................... 18�

3.5.1 - What you get ............................................................................................................................. 18�3.5.2 - Why to get it .............................................................................................................................. 18�


D3.4 V1.0 – June 2014

of 35

3.5.3 - Documentation .......................................................................................................................... 19�

3.6 - Social Network ................................................................................................................................. 19�


3.7 - Content Enrichment .......................................................................................................................... 19�


4 - FICONTENT DESIGNMYAPP PORTAL ................................................................................. 20�4.1 - Screenshots ..................................................................................................................................... 20�

5 - SMART CITY SERVICES PLATFORM PROTOTYPES AND APPLICATIONS .................................. 21�5.1 - Smart City Guide Web App ............................................................................................................... 21�

5.1.1 - Screenshots – Open City Database & Content Enrichment ....................................................... 21�

5.2 - FIContent DesignMyApp Sample Apps ............................................................................................ 22�

5.2.1.1 - DesignMyTrace ........................................................................................................................................ 22�

5.2.1.2 - OpenCyclo ............................................................................................................................................... 22�

5.2.1.3 - ILoveNY ................................................................................................................................................... 22�

5.2.1.4 - OpenParis ................................................................................................................................................ 22�

5.2.1.5 - Paris Beer Week ...................................................................................................................................... 22�

5.2.1.6 - Zoo Parc de Beauval ............................................................................................................................... 23�

5.2.2 - Screenshots .............................................................................................................................. 23�

6 - INTERACTION AND COOPERATION WITH OTHER FICONTENT PLATFORMS .............................. 24�7 - SMART CITY PLATFORM - UPCOMING RELEASES................................................................ 25�

7.1 - POI Explorer ..................................................................................................................................... 25�

7.2 - OpenDataSoft (ODS-DP) ................................................................................................................. 25�

7.3 - New SEs and new prototypes by Open Call partners ....................................................................... 25�

7.3.1 - La Citadelle Inzenjering (LCI) situation and context aware PoI recommendation and SCG (Smart City Guide) map adaptation SE ............................................................................................................ 25�7.3.2 - Metropolitano de Tenerife S.A. (MTSA) - Content and Experience Server based in BLE (Bluetooth Low Energy) beacons localization ....................................................................................... 26�7.3.3 - POIProxy ................................................................................................................................... 27�7.3.4 - Fusion Engine (FE) ................................................................................................................... 28�

7.4 - Other Previously Planned Enablers .................................................................................................. 29�

7.4.1 - Virtual/Mixed Reality.................................................................................................................. 29�

8 - DEPLOYMENT OF THE SMART CITY PLATFORM ................................................................... 30�8.1 - Client Side Enablers ......................................................................................................................... 30�

8.2 - Server Side Enablers with a Shared Instance ................................................................................... 31�


D3.4 V1.0 – June 2014

of 35

8.3 - Server Side Enablers with a Global Instance .................................................................................... 31�

8.4 - Enablers on Both Client and Server Sides ........................................................................................ 31�

8.5 - Infrastructure used in the 1st Experimentation Cycle ........................................................................ 31�

8.6 - Berlin XIFI architecture ..................................................................................................................... 32�

8.6.1 - Openstack ................................................................................................................................. 32�8.6.2 - Virtual Machines ........................................................................................................................ 33�

9 - CONCLUSION .................................................................................................................... 34�REFERENCES ........................................................................................................................ 35�


D3.4 V1.0 – June 2014

of 35

LIST OF FIGURES

LIST OF FIGURES

Figure 1 - High-level architecture of the Smart City Platform ........................................................................ 13�Figure 2 Architecture of the Smart City Platform including the interaction of SEs with GEs from FI-WARE .. 14�Figure 3 ........................................................................................................................................................ 20�Figure 4 ........................................................................................................................................................ 20�Figure 5, Figure 6, Figure 7 .......................................................................................................................... 21�Figure 8, Figure 9, Figure 10 ........................................................................................................................ 21�Figure 11, Figure 12, Figure 13..................................................................................................................... 23�Figure 14, Figure 15, Figure 16..................................................................................................................... 23�Figure 17 ...................................................................................................................................................... 27�Figure 18 ...................................................................................................................................................... 27�Figure 19 ...................................................................................................................................................... 28�Figure 20 ...................................................................................................................................................... 30�Figure 21 ...................................................................................................................................................... 31�Figure 22 ...................................................................................................................................................... 32�Figure 23 ...................................................................................................................................................... 33�


D3.4 V1.0 – June 2014

of 35

ABBREVIATIONS

API Application Programming Interface

AR Augmented Reality

FTP File Transfer Protocol

GE Generic Enabler

HTTP HyperText Transfer Protocol

IMS IP Multimedia Subsystem

LAN Local Area Network

POI Point Of Interest

QoS Quality of Service

QoE Quality of Experience

R1 Release 1 of the Smart City Guide Platform (available in September-October 2013)

R2 Release 2 of the Smart City Guide Platform (available in June.2014)

R3) Release 3 of the Smart City Guide Platform (available in March 2015)

SE Specific Enabler

SCG Smart City Guide

SDK Software Development Kit

TCP Transmission Control Protocol

UML Unified Modeling Language

WAN Wide Area Network

XML Extensible Markup Language


D3.4 V1.0 – June 2014

of 35

1 - INTRODUCTION

1.1 - Overview

The Smart City Platform is a portfolio of functions, designed to foster the development and uptake of smart city applications based on future internet technologies.

This portfolio consists of a set of technical functionalities provided by specific enablers (from FI-CONTENT) and generic enablers (FI-WARE).

1.2 - Terminology

The following table contains terms, which are used in multiple deliverables. Therefore, we provide their shared definitions to ensure consistency across several documents.

Term Definition

Application or Application software

Software layered on top of one or several platforms for realizing various useful tasks for end-users

Architecture A structure of functional elements organized in a given way and presenting well defined interfaces

Capability The ability of a component to satisfy a requirement

Conceptual Model A set of view with written description of the organization of the FIcontent infrastructure to offer services

Enabler Software Module or web service providing well-specified functionality, accessible and usable by application developers through clearly-described APIs (Application Programming Interfaces)

Experiment or Experimentation

Concrete test with actual users of one scenario in one of the experimentation sites in a given time frame

FI-WARE Tools The tools put in place by FI-WARE to send requests for Generic Enablers are based on a backlog list in the frame of an agile methodology

Functional requirement

Either calculations, technical details, data manipulation, processing or other specific functionality that define what a system is intended to accomplish

Generic Enabler An enabler realized by the FI-WARE project or its follow-up sustainability project

Platform A comprehensive combination of technology infrastructure and Generic Enablers as well as Specific Enablers capable to host and to support development of application software

Point of Interest A POI is a place, an area or a journey (short distance) which are geo-located. For example: a place (a restaurant, etc.), an area: a public garden, a journey (a hiking trail, etc.). A POI has possibly features such as : static features (opening hours, address, name description, etc.), dynamic features (price, menu, number of available places, the delay before the next bus, etc.), event features (a beginning and an end)

Scenario Description of foreseeable interactions of users with one or several applications

Specific Enabler An enabler realized by the FIcontent project. Specific Enablers may be layered on top of, or otherwise make use of, Generic Enablers. Please refer to the definition of


D3.4 V1.0 – June 2014

of 35

a FIcontent Specific Enabler from deliverable D6.1 Architecture specification [1]

Interface The connections between domains (or sub domain or functional elements) serving the actor’s actions by exchanging information

Interoperability The capability of two or more networks, devices, applications to exchange and use information

Technology A standard or industry specification that has the capability of addressing requirements


D3.4 V1.0 – June 2014

of 35

2 - SMART CITY PLATFORM ARCHITECTURE The Smart City Platform enables creative people to generate, share and combine assets, objects and stories to develop mobility city services and new social experiences. Furthermore, it offers contextualization, recommendation, live information, mixed reality, 3D, sharing capabilities, and real-time communication. Moreover, the Smart City Platform contains a social interaction dimension where people can connect and build communities to exchange information via social networks.

The Smart City Platform is accessible for web and application developers and provides dedicated features to easily create Smart City Services with well-known and established technologies. In addition to that, the platform takes advantage of eBiz services, such as the Design My App Portal together with the App Generator SE (see Section 3.1), to support non-developers by allowing them to create use-case-specific applications with their content and according to their needs. Thereby, we introduce a shortcut for creative people realizing their ideas without requiring programming skill.

Figure 1 - High-level architecture of the Smart City Platform

The Smart City Platform acts as an intermediate layer between the Generic Enablers provided by FI-WARE and the applications built on top of the platform. Further, it exposes the APIs of the Specific Enablers shipped with the platform to the application developers. A selection of applications showcase specific features or Enablers of the platform as illustrated in the figure above. Each application is dedicated to one scenario of the Smart City Platform as described in detail in deliverable D3.1. Moreover, we expose through the Design My App (DMA) Portal an additional service for 3rd-parties to take advantage of supported SEs within a few clicks by generating their own application based on our SEs.

Due to changes in the consortium, the focus of the Smart City Platform shifted slightly and the platform architecture was realigned during M12. In this context, we introduced several new concept in particular regarding the use-case-specific app generation and additional Specific Enablers as partial replacements. Thus, please treat this architecture description as a first draft that will be concreted before the next platform release in June 2014 (M18).

For previous versions of the Smart City Platform, please refer to previous versions of deliverables, such as D6.1 and D3.2. Moreover, the previous architecture description [2] is available in the FIcontent Wiki.


D3.4 V1.0 – June 2014

of 35

2.1 - Architecture Description

The Smart City Platform is built around the idea that users need easy and direct access to the services provided by FIcontent platforms. Consequently, we provide a portal to enable the user to choose from a set of Enablers and create apps and web apps directly from there. As such, the user can experience the novel functionalities of the services immediately and without needing to overcome a barrier of development effort. If the user needs more functionality that is not yet available by the service use cases, open APIs are provided to make it easy to access their interfaces and utilize the Enablers through programming.

Figure 2 Architecture of the Smart City Platform including the interaction of SEs with GEs from FI-WARE

This architecture also addresses the needs of the different participant types. On one hand the end user can use the portal and create apps directly from the different enablers without development knowledge. Additionally, event organizers can enrich their applications with their own or third-party data from preconfigured formats. Since most of the Enablers have an open API, developers can dive deeper into the functionalities provided, and build their own feature sets on top of them. Last but not least, platform developers and maintainers can build rich web services with them and even add features to the app building platform, which makes it easy for Phase 3 parties to join the Smart City Platform.

2.1.1 - App Generation

To be able to create Smart City applications in a fast and convenient way, the architecture of the Smart City Platform has the app generation process as one of its core components. In its center works the App Generator SE (see Section 3.1) that creates apps and web apps. The interface to the user is driven by the Design My App Portal. The A-CDI GE provides a common API across a range of web-based runtime environments for mobile devices. Once the application is configured by the user, the DCRM GE spawns the server-sided services virtualized into the FI-Lab data center, for instance.


D3.4 V1.0 – June 2014

of 35

2.1.2 - Feature Building Blocks

On the lower left side of the diagram, the concrete services and functionalities are shown. For instance, the social interaction block consists of the Social Network SE [3] to create private, non-proprietary networks between end-users where they can share text and images. If the application does not have its own authentication system, we utilize the IDM-Keyrock GE to provide a ready to use OAuth2 compatible user management. If desired, the Stream-Oriented GE provides live video streaming between end users.

To enhance the visual experience of the Smart City Guide applications, we provide a 3D/Augmented Reality module. XML3D in the shape of the 3D-UI GE provides the capability to use 3D artifacts within your application. Moreover, these can be placed into the camera view by the Augmented Reality GE to turn your application into a full augmented reality experience.

2.1.3 - Data, Media and Content

Beside the functional components on the left side, we have possible data sources on the lower right side. Starting with the Data/Media/Content module, we have four main data sources to provide the capabilities of geo–localized services. The POI Data Provider GE and the Open City Database SE [4] are turn-key solutions to store and retrieve Points of Interest in the vicinity of the user. Furthermore, the OpenDataSoft (ODS-DP) SE (see Section 7) accumulates open data sources and turns them into structured, harmonized data sets. Including these and other possible data sources, the Content Enrichment SE [5] can create video annotations to enhance the multimedia experience of the applications. In addition, the Recommendation as a Service SE [6] provides a layer above the data sources to mine recommendations derived from the user behavior.

To be able to share data between multiple clients and enable real-time applications, we provide a Synchronization module. The Synchronization GE and Content Sharing SE [7] are able to share positioning details and generic data and replicate this data among different hardware. In addition, we use the Object Storage GE to store large-scale structured data into the virtualized cloud services of FI-LAB.

Overall, the app generation process supports the creation of virtualized Data Storage and App Storage instances that are orchestrated by the Design My App portal and is thereby a key feature of the Smart City Platform.

2.2 - Specific Enablers

We will provide the following list of Specific Enablers through the Smart City Platform.

• Open City Database SE [4] • Recommendation as a Service SE (see Section 7) • App Gen SE (see Section 7) • OpenDataSoft (ODS-DP) SE (see Section 7) • POI Explorer SE (see Section 7)

We will utilize the following list of common Specific Enablers for the Smart City Platform.

• Social Network SE [3] (Release 09/13) • Content Enrichment SE [5] (Release 09/13) • Content Sharing SE [7] (Release 09/13) • 3D-Map Tiles SE [8] (Release 06/14) • POI Storage SE [9] (Release 06/14)

As a result of previous work from Orange on the Smart City Platform, two additional Specific Enablers are available, but no longer considered for the realigned architecture of the Smart City Platform.

• Recommendation Services SE [10] (Release 09/13) • Virtual/Mixed Reality SE [11]


D3.4 V1.0 – June 2014

of 35

2.3 - Generic Enablers

We will take advantage of the following Generic Enablers from FI-WARE within the Smart City Platform. The specifications of some of them are in a very early stage. Thus, the actual functionality or the identifier may differ once the specification of the respective GEs is finalized.

• Stream-oriented GE [12] • GIS Data Provider GE [13] • Augmented Reality GE [14] • Synchronization GE [15] • Advanced Middleware GE [16] • DataCenter Resource Management (DCRM) GE [17]

We already actively use the following Generic Enablers as part of the Smart City Platform.

• Identity Management GE [18] • Object Storage GE [19] • Connected Device Interfacing (CDI) GE [20] • POI Data Provider GE [21] • 3D User Interface (3D-UI) GE [22]


D3.4 V1.0 – June 2014

of 35

3 - SMART CITY PLATFORM - RELEASE 06/14 The Smart City Platform was at the 09/13 milestone a portfolio of functions, designed to foster the development and uptake of Smart City Services based on Future Internet technologies.

Now, the Release 06/14 of the Smart City Platform is at the crossroads of a portfolio of technical assets and an app-generation portal. It aims to show that on one hand, Enablers are fully operational, bringing state-of-the-art answers to real use cases and on the other hand a proof of the main concept of the redesigned WP3: “even non-technical people can build an App” with the newly introduced App Generator SE.

3.1 - App Generator [NEW]

3.1.1 - What you get

The App Generator SE is a set of services able to dynamically generate a custom mobile application with custom content (app name, icons, data...) to create test-flights of enablers without development efforts. Today, the backend has an API accessed only through one portal [23]. The aim of this portal is to allow App Generator SE to be used by non-technical users. The kind of app generated depends on which template is chosen. For now, the template supported by the SE is a map enriched with different data sources (OpenData, Webservices, Spreadsheets, CSV, JSON, Images...) and related POIs.

3.1.2 - Why to get it

This enabler allows to quickly generate powerful apps around a custom use. It provides a very intuitive way of valuing data by being able to show it on a map. Also, it demonstrates the technical ability to generate apps on the fly, targeting non-technical users.

3.1.3 - Documentation

• FIContent DesignMyApp portal description (see Section 4) • NB: the technical documentation won't be released along with the Enabler and the portal. The main

reason is that the API is still work in progress.

3.2 - Recommendation as a Service [NEW]


The Recommendations as a Service (RaaS) SE provides the ability to create a professional recommendation engine with just a few mouse-clicks and no programming skills. This platform can persist your item and user data and will host your recommendation engine as a service in the cloud or on your own server infrastructure. Thereby, decision makers can choose whether to use ratings, likes, check-ins or implicit feedback, such as clicks or consumption time. In addition, they can adjust the way, the personalization works by selecting from a wide range of well-explained algorithms.


Use an automatically-offered example user interface or connect your custom application via dynamically generated APIs to the engine. After following these steps, you can analyse your success by retrieving visual illustrations of usage data and customer statistics.


• Technical Documentation of the Recommendation as a Service SE [6]


D3.4 V1.0 – June 2014

of 35

3.3 - Open City Database


The Open City Database gives you back a JSON structure of a city or Points of Interests. The cities JSON object includes information such as country, image, name, id, POIs, location. The POI JSON object includes more detailed information such as name, image, description, id, location, rating, check ins, opening hours, entry, public transport and contact information's. The users generate the content. Therefore, more and more POIs created by user generated content.


Through the use of user generated content the Open City Database is always up to date, and is constantly expanding. By using the REST API, everyone can create and update POIs and cities inside the Database.


• Technical Documentation of the Open City Database SE [4]

3.4 - 3D-Map Tiles [NEW]


The 3D-Map Tiles SE supplies in an OpenStreetMap-like manner map tiles of the ground. These tiles are a 3D representation of the scene ground in contrast to usual image tiles of OSM. Moreover, the 3D-Map Tiles SE supports different backend data providers to offer different kinds of tiles, such as projected OSM-tiles and laser-scanned elevation data with textures. Therefore, the 3D-Map Tiles SE incorporates the GIS-DP GE from FI-WARE.


When moving from traditional 2D-map applications towards geo-referenced interactive 3D-applications, a representation of the environmental ground (i.e. terrain) is needed. The 3D-Map Tiles SE addresses this requirement in a flexible approach and easy-to-use way for web-based application. It seamlessly incorporates with the 3D-UI GE from FI-WARE and thereby preserves full control over rendering to the client application.


• Technical Documentation of the 3D-Map Tiles SE [8]

3.5 - POI Storage [NEW]


The POI Storage SE provides a flexible, lightweight webservice to store POI-related data. Furthermore, it is a GE-compliant implementation of the POI-DP GE from FI-WARE and amends the use of this GE with additional features, such as storing and retrieving of custom data components, importing sample data (e.g. geonames.org), and daisy chaining of POI-DP instances.


Realizing geo-referenced applications often relies on POIs. The POI Storage SE enables these type of applications to store and retrieve POI-related data. Due to the support of custom data components, it nicely fits any kind of application requirements while maintaining compatibility with POI-DP GE to interface other public well-established POI data sources.


D3.4 V1.0 – June 2014

of 35


• Technical Documentation of the POI Storage SE [9]

3.6 - Social Network


The Social Network SE is a federated social network. It features user and profile management and the ability of creating status updates, uploading assets (text, pictures, etc.) and social functions (liking, commenting, etc.) with real-time updates to your peer group (i.e. followers).


The Social Network SE is one way of 'glueing' the different enablers and components into a full-fledged social network. Users of these components can communicate, share, comment and like assets. This is especially relevant if the business model and the use cases of the SME services needs a community and the management thereof.


• Technical Documentation of the Social Network SE [3]

3.7 - Content Enrichment


The Content Enrichment enabler provides the following capabilities

• Media & Text Annotation - allows any type of media (e.g. video, audio, photos or text) to be enriched with user-generated video content, add or edit comments, notes, enrich the media with custom drawings. Also to create custom mash-ups of media content and enable the retrieval of related information (e.g. via access to external resources, location & content sensitive metadata, object tracking etc.)

• Object-based Media Discovery - enriched media content contains metadata information on available objects within the media. Referenced information on available objects can be used to discover other object-related media content

• Cross-Video Navigation - Allows user interaction to jump back and forth in-between video content


To create, distribute and play interactive content video content across platforms and devices. It provides interfaces to incorporate web 2.0 capabilities and community functionalities as well. Thus the enabler acts as a common building block in future video and multimedia infrastructures, to allow seamless, platform independent and convenient enrichment of any type of video content using any type of device for a plurality of application cases covering UGC, professional content as well as edutainment.


• Technical Documentation of the Content Enrichment SE [5]


D3.4 V1.0 – June 2014

of 35

4 - FICONTENT DESIGNMYAPP PORTAL The ficontent.designmyapp portal [24] aims to show how easy it is for anyone to build an app through the Smart City Platform.The portal addresses the non-technical users enabling them to build real mobile apps in just a few minutes with very few skills.

This first version of the portal is built upon two SEs: ODS and App Generator enablers.

The ODS enabler prototype provides specific FIContent datasets [25]. The AppGenerator enabler uses a generic template focused on displaying geolocalized data.

4.1 - Screenshots

Figure 3

Figure 4


D3.4 V1.0 – June 2014

of 35

5 - SMART CITY SERVICES PLATFORM PROTOTYPES AND APPLICATIONS Based on the Smart City Services platform and their enablers, the following set of prototype applications have been build to demonstrate the capabilities of the platform:

5.1 - Smart City Guide Web App

This demo shows the capabilities of a web based smart city guide. Using a standard web browser on a smart phone or tablet a user can access, edit and enhance information about a city. As the app incorporates several enablers developed in the FI-PPP programme it offers users several options. Information on places of interest comes from an open city database enabler, this means any user can add a location as a new point of interest or complete information about an existing POI. The content enrichment enabler means that users can enhance a POI description with enriched video content and thanks to the FI-WARE Object Storage enabler, this enriched video content can be stored in the cloud. The app has an intuitive user interface that also offers the user various ways to view data – as lists, galleries or a map.

5.1.1 - Screenshots – Open City Database & Content Enrichment

Figure 5, Figure 6, Figure 7



D3.4 V1.0 – June 2014

of 35

5.2 - FIContent DesignMyApp Sample Apps The following sample apps have all been generated from the original generic template, or a slightly evolved version with extra features not published on the FIContent DesignMyApp portal

5.2.1.1 - DesignMyTrace With Design My Trace, you can create your own and personnal Trace.Start the application and your travel will be save by creating Points of Interest (POI). You can freely edit each POI by : adding : -one or more picture taken by your device-a description of the POI-a phone number or a web link.-the POIs to be more accurate

Then you can export the data of your travel (POIs and/or trace). By exporting datas, you can re-use them to create custom applications with www.designmyapp.mobi

This application is available on the Google Store.

5.2.1.2 - OpenCyclo OpenCyclo shows the availability and status of all bike stations managed by JC Decaux in over 20 locations around the world.OpenCyclo regularly updates the status of each bikes stations by showing you the number of bike and parking places available.For each stations, you can consult the StreetView and the distance by foot or by bike between you and the selected stations.Manage your favorite places-to-be by adding the nearest bike stations to your favorite list.OpenCyclo supports more than 10 cities in France including Paris, Marseille, Nantes, Toulouse… and more than a dozen cities in others countries including Bruxelles (Belgium), Seville (Spain), Vilnius (Lithuania), Toyama (Japan).

This application is available on the Google Store and the AppStore.

5.2.1.3 - ILoveNY I Love New York contains more than 1400 Points of interest (POIs) about attractives places through New York City.You want to find your way to the People’s Improv Theater or just the Simpson Street ? Just use the research bar to find the place and start the navigation. I Love New York provides some informations about each POI on the interactive map based on a datasource on the web updated frequently

5.2.1.4 - OpenParis Who has not faced a strike or an incident while waiting the subway. Moreover, in this situation, your internet connection is slow and you cannot find an alternative.Why take the subway with several changes when you can take a direct tram or bus?OpenParis offers an interactive map of all available means of transportation around : Metro, Bus, Train, Tram, Velib’ …A touch on the base station and the arrival point and check on the layout of the lines that will help you reach your destination.You can also discover all the bus lines which stop near your favorite place.

This application is available on the Google Store

5.2.1.5 - Paris Beer Week The Paris Beer Week is a French Event gathered bar and brewery offering multiple activity during a week at the end of May.Plan your route through Paris via the App Paris Beer Week.Consult the list of all the events proposed by each places participating to this event.Find the best brewery corresponding to your expectations by consulting a short description and a picture of each place integrated in the App

This application is available on the Google Store


D3.4 V1.0 – June 2014

of 35

5.2.1.6 - Zoo Parc de Beauval You want to visit the Zoo of Beauval but you do not have a plan ? Zoo Beauval provides you an interactive map of this Zoo. Use the Search bar to find the animal you want to see and find their exact location marked by a Point of Interest (POI).You want to go back in the Zoo and find your favorite species ? Add some POI to your favorite list and find your way up to them more easily.

5.2.2 - Screenshots




D3.4 V1.0 – June 2014

of 35

6 - INTERACTION AND COOPERATION WITH OTHER FICONTENT PLATFORMS Some Specific Enablers used by the Smart City Platform are common with other FI-Content Platforms:

• Social Network SE [3], provided by Pixelpark (Release 10/13) • Content Enrichment SE [5], provided by Fokus (Release 09/13) • Content Sharing SE [7], provided by Thales Communications (Release 12/13)


D3.4 V1.0 – June 2014

of 35

7 - SMART CITY PLATFORM - UPCOMING RELEASES For the upcoming releases of the Smart City Platform we will in particular focus on augmented reality aspects of the platform. We will try to integrate mixed reality concepts and an interactive way to augment POIs with user generated content. Thus, the following Specific Enablers are planned to be integrated into upcoming releases of the Smart City Platform.

7.1 - POI Explorer

This Specific Enabler will provide advanced interaction techniques with Points of Interest (POIs) based on Augmented Reality and Mixed Reality applications. It will utilize multiple tracking methods to improve the accuracy for outdoor AR applications. Moreover, it will handle user generated content (i.e. pictures, videos, 3D-content) in order to augment POIs with this.

7.2 - OpenDataSoft (ODS-DP)

The ODS-DP SE will serve as a powerful data management platform aiming at providing structured and normalized content through APIs for any user facing application and exposing project data through a state of the art data portal, allowing for data reuse and data visualizations integration into third party sites.

Being available through a SaaS approach, on the Cloud, the ODS-DP SE will be available for any number of experimentations and support an unlimited number of users.

The ODS-DP SE will be able to process and transform data coming from multiple sources: static content (upload of CSV, XLS, GIS exports ...), real time data, crowd sourcing.

7.3 - New SEs and new prototypes by Open Call partners

7.3.1 - La Citadelle Inzenjering (LCI) situation and context aware PoI recommendation and SCG (Smart City Guide) map adaptation SE

LCI will bring situation and context awareness to DMA (Design My App) platform through combination of application enablers and back end services. To this end, LCI will develop and integrate the following enablers:

• DMA template/enabler which enables situational presentation of geolocation information through adaptation of SCG maps and creation of context and situation aware overlays with PoI recommendation.

• DMA template/enabler that will instrument contextual/sensory information gathering through designed custom applications relying on the SCG service. This enabler will be based on LCI’s ContextSENSE service. The ContextSENSE sensor will be integrated into the designed mobile application and it will enable gathering of contextual data related to:

• User’s habits related to utilization of the designed custom application. • User’s habits in utilizing internet access service and status of network connection. • User location. • Mobile device characteristics and installed applications. • Status of mobile device sensors. • DMA template/enabler that will enable companion wearable devices to be part of the designed

custom application and integrated into the context gathering process in order to pinpoint user’s current activity. This enabler will also be based on LCI’s ContextSENSE service.

• Backend enabler for context formatting, analysis and pattern derivation necessary for realization of the map adaptation recommender service. This enabler will be based on:

• The ContextSENSE server which is cloud based and which collects and formats contextual data gathered from ContextSENSE sensors. Also, the ContextSENSE server utilizes standard APIs for accessing contextual data from 3rd parties (web portals, social networks, open databases).


D3.4 V1.0 – June 2014

of 35

• The VizLore data analytics and machine learning cloud platform (developed on the Google App Engine) comprising:

• Cloud database for storing contextual data and derived patterns. • Set of functions and modules for performing custom data analysis tasks. • Set of modules for training custom machine learning models. • Set of modules for result presentation. • Set of modules for building custom DA and ML frameworks and context sensing/analysis schedulers. • Customizable dashboards for presenting data and results.

The solution for context gathering through the designed mobile application will be developed and utilized in line with privacy by design principles and the revised Directive 95/46/EC on Data Protection and Privacy which will come into force during the lifetime of the project.Through utilization of these enablers LCI will build the following services which will be utilized by designed mobile applications:

• Recommendation on how to present SCG service maps to end users (this should be based on situation awareness, current user context and personal preferences).

• Recommendation on which SCG map geo-location enrichment is adequate for the given situation and user context.

LCI will work on specification of user scenarios related to utilization of DMA platform and enablers for SCG map recommendations during the La Merce festival. These user scenarios will be based on provision of map adaptation recommendation services to festival visitors and organizers. Festival visitors will be able to receive various PoI recommendations and guidelines (presented as customized SCG map overlays and adapted map representation) for participating in festivities based on their personal preferences, their current context (activity, used device, location etc.) and the wider situational context (weather, status of important city services like transportation, changes in festival program, other city events related to the festival). The festival organizers will receive a platform for engaging visitors with various recommendations related to the festival and the city. This will open new possibilities for attracting more sponsors and provide local service providers with proper channel for promoting their offerings to the audience who will appreciate it.

7.3.2 - Metropolitano de Tenerife S.A. (MTSA) - Content and Experience Server based in BLE (Bluetooth Low Energy) beacons localization

The platform will provide a very accurate location service using small wireless devices that broadcasts its presence over Bluetooth 4.0. This allows to send contents, notifications, specific information, campaings, etc.. through an APP when the user is near. The smaller targeting radius further increases the relevance of the information.The platform will use simple and cheap BLE devices (run for two years on a AA battery) and also smart devices which can include additional information using BLE.The system provides:

• Backend Platform: general management (beacons, contents, apps, profiles, security..) and analytics • Simple and smart BLE devices to be installed at specific points • A SDK targeted to app developers willing to add Beacon-awareness to their apps and deploy

proximity experiences.

The next block diagram shows the system and its functionalities:


D3.4 V1.0 – June 2014

of 35

Figure 17

In addition, MTSA will be a use case using its current app (VIA-MOVIL) in a real transport environment. VIA-MOVIL manage at this moment 6.000 trips per day:

Figure 18

This upcoming release is not configured as an Specific Enabler but a use case of how smart city services can be provided in a real transit environment.

7.3.3 - POIProxy

POIProxy is a service to retrieve Points of Interest from almost any public remote service that exposes geolocated data through a REST API.

Currently there is a heterogeneus ecosystem of services including geolocated data providing each one their own request and response APIs. POIProxy solves that problem by identifying common patterns in the request and response APIs and providing a common and well defined REST API with a single output format.


D3.4 V1.0 – June 2014

of 35

POIProxy handles requests to any REST service that provide geolocated data and serves GeoJSON as output format to easily put the results on a dynamic web mapping application.

POIProxy uses a generic parsing engine that allows adding support to new remote services by configuration. As remote services that provide geolocated data have a set of common features: REST API, plain and almost human-readable formats (JSON, XML, CSV, …), etc. It is possible to support a wide range of remote services by identifying the specific parameters needed on their APIs and declaring the attributes to be parsed in their output formats.

Some examples of the kind of services that POIProxy can interact with:

• Open data portals: Static files (CSV, KML, XML, JSON), OData APIs, REST APIs... • Social networks: Flickr, Panoramio, Instagram, 500px, Twitter, Facebook, Foursquare... • Event services: LastFM, Nvivo, SongKick, Meetup, Eventbrite, ... • Other services, including real time services: Wikilocation, Geonames, OpenWeatherMap, CityBikes,

...

POIProxy overview:

Figure 19

Finally, POIProxy can be easily extended by configuration, so new services or open data resources can be added at runtime by describing the properties of the service in a configuration file.

This SE will provide a single endpoint to access to a wide variety of POI resources.

7.3.4 - Fusion Engine (FE)

The fusion consists in achieving the same POI from different data sources and joining their properties in a smart and ordered way. For this, the Fusion Engine (FE) requires a configuration file where the specific fusion rules are established to create an OCD.Starting from a POI, the fusion engine gets all POIs and relevant information (images, videos, etc.) from other sources indicated in the Fusion Rules file (FR), through the Common POI API. This file also indicates the order of priority for searching POIs or when two POIs have a repeated field.Once a fused POI is obtained, it is stored in a georeferenced database or OCD. Each OCD stores all POIs in a city or region, and users have a service to create their own custom OCD, where they can choose data sources, types of POIs or places.In order to access the data stored in any of the OCDs, the Fusion Engine implements the Common POI API, so they can easily obtain POIs following the standard W3C-POI WG.The process is depicted in Figure below:

• The Fusion Engine access to a series of data sources (OSM, DBPedia, POIProxy) through a common POI API

• Depending on the selected data sources and the fusion rules, several OCDs can be created. Typically there will be at least one OCD per experimental site. However, in order to make the FE more flexible and powerful, it is envisioned that one (user or administrator) may select its own city with specific data sources or even categories within the data sources. For example, one may be


D3.4 V1.0 – June 2014

of 35

interested in creating its own OCD for a particular city (e.g. Barcelona) but only for hotels and restaurants (the other POIs are irrelevant for the user)

FE overview:{{ :ficontent:smartcity:roadmap:fic2_fe.png?300 |}}

7.4 - Other Previously Planned Enablers

A number of planned Specific Enablers were postponed or will not provided by FIcontent, as the scenarios and the feasibility of planned large-scale scenarios after WP3 redesign is not yet clear. Moreover, the expertise from the new partners is now known.

7.4.1 - Virtual/Mixed Reality

Mixed reality combines the real world with virtual objects, characters and information. The Virtual/Mixed Reality SE is the core component of a mixed reality service, managing a large number of geo-localized moving objects in real-time, with a distributed architecture allowing almost unlimited scalability.

This SE provides neighboring moving objects (either real of virtual) according to the user's position. The position can be computed either using antennas or cameras with AR marker databases or in case of markerless image tracking, natural marker databases.

This Specific Enabler will be provided by Orange, but is no longer considered by FIcontent due to the withdrawal of Orange.


D3.4 V1.0 – June 2014

of 35

8 - DEPLOYMENT OF THE SMART CITY PLATFORM Infrastructure for the 1st experimentation (1st version of the SMart City Platform) is built on Specific Enablers only. These Specifics Enablers are hosted in several data centers (more information available in the "Infrastructure used in the 1st Experimentation Cycle" section).

For the coming versions of the Smart City Platform, the Generic and Specifics Enablers will be distributed in the XIFI data centers of Britany, Berlin and Séville/Malaga (see figure below).

Figure 20

8.1 - Client Side Enablers

On client side, two Smart City Guide applications are available: an Android Native Application and a HTML5 Web application.

• “Smart City Guide” Android Native Application:

The “Smart City Guide” Android Native Application was developed using the standard Android SDK (use of standard Android components).It is optimized for the Samsung Galaxy S3 Titanium 4G handset.

• “Smart City Guide” HTML5 Web Application:

The “Smart City Guide” HTML5 Web Application can be used by all Smartphones, Tablets and PCs with an HTML5 enabled browser. This application is not bounded to specific opertaing systems (e.g. iOS, Android. Windows phone). It is a web application which gives each user the opportunity to use it with his mobile device or PC. The App is developed in the programming languages HTML5, CSS3, JavaScript and utilizes the Open City Database. In Release 1, the HTML5 Web Application is optimized for the Samsung Galaxy S4 with Chrome.


D3.4 V1.0 – June 2014

of 35

8.2 - Server Side Enablers with a Shared Instance

Not Applicable in first version of the Smart City Platform.

8.3 - Server Side Enablers with a Global Instance

The 1st Experimentation Cycle is built on Specific Enablers only (no use of Generic Enablers).Those Specifics Enablers are hosted in several data centers:

• 2 of them in the ImaginLab data center in Lannion: Local Information (“Ma Vie Locale”, Orange product), Recommendations Services (“Reperio”, Orange produc)

• 1 in the Orange data center in Issy-les-Moulineaux: Virtual/mixed Reality (“Kiwano” Orange product) • 2 in the Fraunhofer Fokus data center in Berlin: Content Enrichment • 1 in the FI-LAB node: Social Network

8.4 - Enablers on Both Client and Server Sides Not Applicable in first version of the Smart City Platform.

8.5 - Infrastructure used in the 1st Experimentation Cycle

The infrastructure for the 1st Experimentation Cycle is built on Specific Enablers only (no use of Generic Enablers) :

Figure 21

ImaginLab data center infrastructure:

VMware: VMWare ESX 4.1 is installed on a HP server in order to use several Virtual Machines.


D3.4 V1.0 – June 2014

of 35

Virtual Machines:In order to fulfill the project needs, 6 VMs are installed on the ESX server. 3 of them are pre-production platforms (ppp) and the other 3 are production platforms (pp). Changes have to be made on pre-production platforms, and then once confirmed, are reproduced on the production platform. So there are 3 main "services", each of them installed both on a pre-production and on a production platform. All those 3 services are developed by Orange:

- "mvl" stands for "Ma vie locale" (Local Information Specific Enabler). Providing information from external contents.

- "reperio": (Recommendation Services Specific Enabler) - indexation, requests.

- "solr": Solr Search Engine.

Access to contents (from local and remote experimentation sites):

Figure 22

8.6 - Berlin XIFI architecture

8.6.1 - Openstack

The Generic Enabler “Object Storage” ist hosted on the OpenStack at Berlin XIFI. All user generated videos and photos will be located there. The Object Storage GE is divided in two sections. The OpenStack


D3.4 V1.0 – June 2014

of 35

Keystone provides identity, token, catalog and policy service, the OpenStack Swift provides high available and distributed Object Store.

Figure 23

In the SCG scenario, enrichment of video content uses the enabler Content Enrichment SE deployed at Fraunhofer FOKUS and the Object Storage GE deployed at XIFI Node Berlin. The user generated video, uploaded on the server, will be split off and pushed in smaller steps to the Object Storage. After the video is uploaded the user can enrich the video. This metadata will be pushed to the Content Enrichment SE API. Every time a video is viewed, the video is loaded from the Object Storage and the enriched content is loaded from the Content Enrichment API.

8.6.2 - Virtual Machines

The Smart City Guide Web App is located on a virtual machine at Fraunhofer FOKUS.

• Ubuntu 64-bit 12.04 LTS • 8GB Ram 40GB HDD • 4* Intel XEON E7540 2.0Ghz • on a VMWare VCenter-Server 5.50


D3.4 V1.0 – June 2014

of 35

9 - CONCLUSION In this document, we have presented a technical description of the Smart City Platform. First, we have presented the overall architecture of the platform, listing the groups of Specific Enablers and Generic Enablers that are involved, as well as how they interact with each other. In addition, we have indicated the external development tools that are currently integrated in the platform and how this integration works.

Second, we have presented the development roadmap, including a description of what will be available in the first platform release and in upcoming releases. This includes a high-level description of the Specific Enablers provided by the partners behind the Smart City Platform. For a detailed description of Specific Enablers, please refer to FIcontent Wiki [26]. Description of FI-WARE GEs is referred to the FI-WARE catalogue.

Finally, we have discussed the deployment of the platform and pointed out the diversity of environments hosting the utilized enablers between client devices and server instances.


D3.4 V1.0 – June 2014

of 35

REFERENCES

[1] http://wiki.mediafi.org/doku.php/ficontent.deliverables.d61#definition_of_a_ficontent_specific_enabler

[2] http://wiki.mediafi.org/doku.php/ficontent.smartcity.architecture?rev=1388411732

[3] http://wiki.mediafi.org/doku.php/ficontent.common.enabler.socialnetwork

[4] http://wiki.mediafi.org/doku.php/ficontent.smartcity.enabler.opencitydatabase

[5] http://wiki.mediafi.org/doku.php/ficontent.common.enabler.contentenrichment

[6] http://wiki.mediafi.org/doku.php/ficontent.smartcity.enabler.recommendationasaservice

[7] http://wiki.mediafi.org/doku.php/ficontent.common.enabler.contentsharing

[8] http://wiki.mediafi.org/doku.php/ficontent.common.enabler.3dmaptiles

[9] http://wiki.mediafi.org/doku.php/ficontent.common.enabler.poistorage

[10] http://wiki.mediafi.org/doku.php/ficontent.smartcity.enabler.recommendationservices

[11] http://wiki.mediafi.org/doku.php/ficontent.smartcity.enabler.virtualmixedreality

[12] http://wiki.mediafi.org/doku.php/ficontent.fiware.ge_usage#stream-oriented_ge

[13] http://wiki.mediafi.org/doku.php/ficontent.fiware.ge_usage#gis_data_provider_ge

[14] http://wiki.mediafi.org/doku.php/ficontent.fiware.ge_usage#augmented_reality_ge

[15] http://wiki.mediafi.org/doku.php/ficontent.fiware.ge_usage#synchronization_ge

[16] http://wiki.mediafi.org/doku.php/ficontent.fiware.ge_usage#advanced_middleware_ge

[17] http://wiki.mediafi.org/doku.php/ficontent.fiware.ge_usage#datacenter_resource_management_dcrm_ge

[18] http://wiki.mediafi.org/doku.php/ficontent.fiware.ge_usage#identity_management_ge

[19] http://wiki.mediafi.org/doku.php/ficontent.fiware.ge_usage#object_storage_ge

[20] http://wiki.mediafi.org/doku.php/ficontent.fiware.ge_usage#connected_device_interfacing_cdi_ge

[21] http://wiki.mediafi.org/doku.php/ficontent.fiware.ge_usage#poi_data_provider_ge

[22] http://wiki.mediafi.org/doku.php/ficontent.fiware.ge_usage#d_user_interface_3d-ui_ge

[23] http://ficontent.designmyapp.mobi

[24] http://ficontent.designmyapp.mobi/

[25] http://ficontent.opendatasoft.com/explore/

[26] http://wiki.mediafi.org/doku.php/ficontent:private:deliverables:d34:ficontent:private:start

d3.4 prototype refined after st user test … · d3.4 prototype refined after 1st user test and...

Documents