1 / 15

The Core PLATFORM Project

The Core PLATFORM Project. Thierry Nagellen - Orange. What kind of Core platform?. Future Internet Core Platform Provisioning – Hosting – Brokering – Consumption. Security by Design. What is a FI-WARE Generic Enabler (GE)?.

onslow
Télécharger la présentation

The Core PLATFORM Project

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. The Core PLATFORM Project Thierry Nagellen - Orange

  2. What kind of Core platform? Future Internet Core Platform Provisioning – Hosting – Brokering – Consumption Security by Design

  3. What is a FI-WARE Generic Enabler (GE)? • A FI-WARE Generic Enabler (GE) is a functional building block of FI-WARE • Any implementation of a Generic Enabler (GE) is made up of a set of components which together supports a concrete set of Functions and provides a concrete set of APIs and interoperable interfaces that are in compliance with open specifications published for that GE • There might be multiple compliant implementations of a given GE • Each Architecture Chapter (linked to WP3 until WP9) in FI-WARE will lead to definition of a set of GEs

  4. Definition of FI-Ware GEs Agile SW development Using a common backlog for WPL and Usage area projects

  5. FI Core Platform Architecture: main chapters Functionality Trust and Security Operations Developer tools Service delivery Cloud Hosting Internet of Things Support Services Interface to the Network and devices

  6. Service delivery Objective: Provision, Composition and delivery of services • Application and service ecosystem and delivery framework Multi channel multi service access Composition and mash-up Business Framework Registry and repository

  7. Cloud Hosting Objective: Handle the provison of computation, networks and software resources Cloud hosting PaaS Enablement Network Edge/cloud proxy mgt. PaaS Advanced management SaaS Basic management SaaS Virtualization

  8. Internet of Things Objective: Interaction with “things”, searchable and accessible Internet of Things enablement IoT process automation IoT resource management IoT Data handling IoT Communications

  9. Data and context management Objective: Transform the data into information Data and context management Context management High level intelligent Services Event management Analysis infrastructure Data Storage and core services

  10. Interface to the network and devices Objective: Open and standardized interfaces to network and devices I2ND Context management Interface to connected devices Interface to Network services Interface to open networking entities Data Storage and core services Interface to Cloud proxies

  11. Security privacy and Trust Objective: Develop a security ecosystem, comprising core and generic enablers Security privacy and trust Generic Security Enablers Context based and compliance Optional security services Data Storage and core services Security monitoring

  12. Development tools, testing and exploitation Objective: Support the community of developers DevComE Testing and deployment API IDE support Forge implantation

  13. Testing and exploitation Objective: Integrated testing and validation Objective: Exploitation and standardization Testing Exploitation Support to Usage cases Standards Integration Exploitation Strategy Internaltestbed Market analysis

  14. Our time schedule First year June/September 2011: High level architecture description January 2012: First open call issued May 2012: Reference implementation Second year June 2012: Open call closes September 2012: First FI-WARE testbed January 2013: Second open call issued May 2013: FirstReference implementation Third year June 2013: Open call closes September 2013: second FI-WARE testbed January 2014: Reference implementation May 2014: Fi-Ware final release

  15. Thank you!

More Related