the fi-ware project – base platform for future service infrastructures fi-ware march 2011 future...

The FI-WARE Project – Base Platform for Future Service Infrastructures

FI-WARE

March 2011

Future Internet PPP Core Platform


Index

2

1. Context

2. Vision

3. FI-WARE Architecture

4. Structure of Activities and Work Plan


Index

3

1. Context

2. Vision




Other Usage areas

eHealth

Tourism

Smart Grid

Transport

E- business

Utilities and environment

FI-WARE platform will serve objectives of usage areas and will have the ambition of fulfilling the

needs of a broader market

What is FI-WARE?. The center of a future ecosystem

The aim of FI-WARE is to be useful for Europe


We are open to the community

Future Internet Core Platform

Provisioning – Hosting – Refactoring – Brokering – Consumption

App/Services ecosystem and delivery framework

Cloud Hosting Interface to NetworksInternet of Things

Suppliers

WholesalersManufacture

r Retailers

GovernmentsConsumers


We are committed to the PPP…and beyond

Working IT and Telcos together to make

New services for everybody Smart applications Innovative business models

Providing

– Tools to avoid fragmentation

– Results from existing research

Our objective: create a solid basis for the Internet of the Future


Index

7

1. Context

2. Vision




The VISION

FI-WARE will be a technological foundation to satisfy the demands of application/services providers and consumers across various usage areas, stimulating and cultivating a sustainable FI service ecosystem

Platform Provider

Apps/Services Provider

People Businesses

Consumers


Elements & Functions of FI Core Platform

9

The FI Core Platform comprises a set of technological “Generic Enablers” which are considered general purpose and common to several current and future “usage areas”

Generic Enablers (therefore, the FI Core Platform) will provide open interfaces for development of Applications

Cloud Hosting

App/Service Delivery

Support Services

Interface to IoT

Interface to Network

Security, Trust

Dev Tools

Cloud Hosting

App/Service Delivery

Support Services

Interface to IoT


Security, Trust

Dev Tools

Usage area projects under the PPP


Core Platform Instances and Use Case Trials

Future Internet Applications run on top of “FI Core Platform Instances” built upon selection and assembly of “Platform Products” implementing “Generic Enablers” of the “FI Core Platform”

Use Case trials will consist on application scenarios running on top of FI Core Platform Instances, involving real users

FI Core Platform

Platform Products

FI Core Platform Instance

10

Use Case Trial

assemble…

GE GE

GE

GE

GE

GE GE


FI-WARE isn’t “Business as Usual”

The PPP focuses in medium-term research (Core Platform ready for trials in 2 years)

The PPP implies a relevant effort integrating existing research results which has never been tackled before in the EU FP

Examples: Reservoir, VISION, 4CaaSt, SENSEI, IoTA, GEYSER, 4WARD, …

Prominent role of industry (both Telco and Service companies)

Platform validation is supported through large scale trials involving real users

11


Index

12

1. Context

2. Vision




FI Core Platform Architecture: main chapters

13

Op

erat

ion

sO

per

atio

ns

Tru

st a

nd

Sec

uri

tyT

rust

an

d S

ecu

rity

Fu

nct

ion

alit

yF

un

ctio

nal

ity

App/Services Ecosystem &

Delivery Framework

Access to Internet of

Things

Core Platform Support Services

Cloud Hosting



Service Delivery framework

14

Enables applications, implementing processes or linked to "things" and contents, to be accessible by end-users: • from any device

• within and across domain-specific Core Platform instances (federated applications catalogs)

Enables applications “mash-up“ and the exploitation of user-driven innovation

Incorporate Open Application/Services Marketplace capabilities and the publication of applications through different channels (Facebook, AppStores, ….)


Cloud hosting

15

Enable application providers to host their applications on a cloud computing infrastructure so that:• ICT resources are elastically

assigned as demand evolves, meeting SLAs and business requirements

• They only pay for actual use or ICT resources

Support both IaaS-oriented and PaaS-oriented provisioning of resources

The cloud computing infrastructure linked to a Core Platform instance can be federated with that of another Core Platform instance or external Clouds, through standard APIs/protocols


Support and Data handling

16

Collection of enablers supporting:• Access to Context Info

(including user profile and preferences) to ease development of context-aware apps

• Storage of large amounts of data

• Processing, correlation and distribution of large amounts of events

• Processing of multi-media contents

Accessible through standard set of APIs


Support and Data handling

17

Collection of enablers supporting:• Access to Context Info

(including user profile and preferences) to ease development of context-aware apps

• Storage of large amounts of data

• Processing, correlation and distribution of large amounts of events

• Processing of multi-media contents

Accessible through standard set of APIs


Access to the Internet of things

18

Enables an uniform access to the “Internet of Things”: • Universal (unique)

identification of “things”

• Standard information model

• Standard management APIs

• Standard APIs for gathering data

Implemented as a common layer which mediates with the different types of sensor and device networks


Security and trust

19

Trust and Security:• Spanning from infrastructure and

“things” all up to the application layer

• Common enablers for identity, authentication and authorization

• User privacy management

Operations• Lifecycle Management Support

• End user usage accounting

• Platform usage accounting

• Support for Analytics


Interface to the network

20

Interfaces wrapping access to network enablers that would be published to application programmers (materializing and further developing efforts in initiatives such as JIL, BONDI, GSMA oneAPI)

Interfaces required for development of Platform components:• Interfaces to control QoS and Network Resources allocation

• Gateway communication middleware and hosting interfaces

• …


Index

21

1. Context

2. Vision




WP Structure

WP1 Management WP1 Management

WP2 Global Technical ActivitiesWP2 Global Technical Activities

WP11 Experimentation and Validation

WP11 Experimentation and Validation

WP12Dissemination and Exploitation

WP12Dissemination and Exploitation

WP3 Apps/ServicesEcosystem and Delivery

WP3 Apps/ServicesEcosystem and Delivery

WP4Cloud HostingWP4Cloud Hosting

WP5 IoTWP5 IoT

WP6 Support Services

WP6 Support Services

WP7Interface to the Network

WP7Interface to the Network

WP8Dev Comm and Tools

WP8Dev Comm and Tools

WP9 Security , WP10 CP Instantiation and Operational SupportWP9 Security , WP10 CP Instantiation and Operational Support


Applying Agile concepts

23

Component Backlog

Component Backlog

Features Backlogs per Usage Area

(Features identified by a given Usage-Area)•Representatives from each Usage-Area project meet regularly with TM and WPLs to review features backlog•Features within each Usage-Area Backlog has a priority assigned

Define, Merge, Extrapolate, Prioritize, …

Following Agile principles, FI-WARE interaction with Usage-Area projects will be rather dynamic

Final priorities in Chapter Backlogs will be assigned according to indicators such as implementation time, number of UAs requiring the feature, support by stakeholders, Impact on overall Architecture, Genericity, …

Results from prioritization will be public and shared with Usage-Areas as part of the overall FI-WARE roadmap

Conflicts will be resolved within PPP Governance Bodies (mainly Architecture Board)

SP1 SP2 SP3 SP4 SP5 SP6 SP7 SP8Vision

….Sprint0


….Sprint0


….Sprint0


….Sprint0

SP1 SP2 SP3 SP4

Vision

Sprint0


….Sprint0

Minor releases

Global Governance

Chapter 1

Single Global Clock

Chapter 2

Component 1

Component 2

Component 3

Major releases

Component 1

Component 2

Component 3

Features Backlogs per Architecture Chapter (WPs 3-9)

(Features in Roadmap of FI-WARE Architecture Chapters)•Each Backlog owned by the corresponding WPL•Planning of Sprints decided within corresponding WPC •and supervised by PCC


Management of Open Calls

We plan to maintain ~30% (12M Euro) of the project budget for distribution among new partners

New partners will be selected through Open Calls to allow for responding to emerging user requires not identified at the start of the project, e.g.,

› due to new usage areas, new technologies, new economic conditions

Specific component of the budget will be reserved for SMEs (aprox 30%) and Research Centers (aprox 30%)

Selection of new partners will be done according to the procedure issued by the Commission

24

European Commission23 October 2009v1a23 October 2009v1a

Guidance note for project coordinators planning a competitive call for additional beneficiaries in an ICT Integrated Project or Network of excellenceGuidance note for project coordinators planning a competitive call for additional beneficiaries in an ICT Integrated Project or Network of excellence


Thank You !!

the fi-ware project – base platform for future service infrastructures fi-ware march 2011 future...

Documents

fiware project base

environment fiware platform

vision fiware

fi core platform instances

fiware architecture

aim of fi

future slide

future ecosystem