Successfully reported this slideshow.
We use your LinkedIn profile and activity data to personalize ads and to show you more relevant ads. You can change your ad preferences anytime.

Fiware overview3

135 views

Published on

FIWARE overview for FIWARE Madrid meeting

Published in: Engineering
  • Be the first to comment

  • Be the first to like this

Fiware overview3

  1. 1. FIWARE : el camino a la industria 4.0 Joaquin Salvachua FIWARE Evangelist && FIWARE TSC member @jsalvachua, @FIWARE
  2. 2. 1 e-business Web 2.0 Smart Life Presence of business on Internet (B2C, B2B) Presence of people on Internet (Social Networks) Improving daily life of people and businesses (Smart X) We are in front of a new Digital revolution which will transform the daily life of people and businesses: everything that can be connected will be connected, for the sake of a more smart life
  3. 3. 2 The new Digital Life will gravitate around context data. Context data which describes what is going on, where, when, why …
  4. 4. 3 Context creates a digital continuum, blurring the frontiers between application domains Breaking the current silos of information
  5. 5. 4 e-business Web 2.0 Smart Life Presence of business on Internet (B2C, B2B) Presence of people on Internet (Social Networks) Improving daily life of people and businesses (Smart X)
  6. 6. 5 How we want the next phase to be?
  7. 7. 6 FIWARE: The Open Source platform of choice for building smart solutions Smart Solutions gather data from many different sources (including but not limited to IoT) to build a “picture” of the real world and then process and analyze that information in order to implement the desired intelligent behavior (which may imply changing the real world) Data = Context Information Capture Actuate Process
  8. 8. 7 … in Cities Bus • Location • No. passengers • Driver • Licence plate Citizen • Birthday • Preferences • Location • ToDo list Shop • Location • Business name • Franchise • offerings
  9. 9. 8 Tractor • Location • Speed • Direction Crop • Humidity • Leaf area • Age Drone • Location • Battery level • Speed • Direction … in Agrifood
  10. 10. 9 Tanker • Driver • Location • Max Volume • Current Level • Speed • Direction Gas Tank • Station • Max Volume • Current Level • Min Threshold • Temperature Station • Location • Owner • SLA … in Industry
  11. 11. 10 What if ... for accessing context information? a standard API there were
  12. 12. 11 Users will enjoy portable solutions City of Santander City of Porto
  13. 13. 12 Context Broker Standard API GET <Oauth token> http://<endpoint>/V2/entities/lamp1/attrs/presenceSensor/value Reading the value provided by a sensor should be as easy as reading an attribute of an entity “I don’t care what low-level IoT protocol is used” “I should not need to handle connectivity with IoT devices” IoT would be an enabler, no barriers because of complexity
  14. 14. Actuation on a device should come as a side effect derived from updating the attribute of an entity PUT <Oauth token> http://<endpoint>/V2/entities/crop1/attrs/watering/value “on” IoT would be an enabler, no barriers because of complexity 13 Context Broker Standard API “I don’t care what low-level IoT protocol is used” “I should not need to handle connectivity with IoT devices”
  15. 15. Shared context information would boost innovative services and the development of a Data Economy ▪ Organizations in different domains could interchange data based on a common Context Information Management layer ▪ Authorization and Access Control Policies govern who can access what, when (Sovereign of Data) ▪ Organizations may monetize the data they offer (Economy of Data) 14 Smart Factory Smart Bank Smart Retail Smart Home Smart City Virtual Shared Data Space Smart Servicesstandard API FIWARE NGSI and Context Broker Technology has been selected to become a CEF (Connecting Europe Facility) Building Block
  16. 16. FIWARE case example: enriching car navigation through front-runner smart cities using third-party data 15 • Car navigators can display context information about available parking slots published by cities or other data from third parties it has acquired the right to access to • The car can share speed info with the city if the drivers agree and both get something in return City of Santander City of Porto • Users can receive recommendations from smart home systems (“do you want me to switch on the heat before you arrive?”) • Users may have paid for apps developed around data and recommendations used from the car (discount restaurants around)
  17. 17. Entrepreneurs will benefit the opportunities of a larger market 16 “We can invest on development of solutions we don’t have to adapt for each and every customer”
  18. 18. FIWARE: Driving the standard for Context Information Management ▪ The FIWARE Context Broker technology implements the FIWARE NGSI API: a simple yet powerful public, royalty-free standard API for Context Information Management ▪ Simple: A RESTful API using JSON which any web programmer learns how to use in one day ▪ Yet powerful: FIWARE NGSI supports geo-queries, soon Linked Data (JSON-LD) 17 Application/Service Bus • Location • No. passengers • Driver • Licence plate Citizen • Name-Surname • Birthday • Preferences • Location • ToDo list Shop • Location • Business name • Franchise • offerings Context Information FIWARE NGSI API
  19. 19. CEF Building Blocks ▪ https://ec.europa.eu/cefdigital/wiki/display/CEFDIGITAL/Building+Blocks ▪ https://ec.europa.eu/cefdigital/wiki/display/CEFDIGITAL/Context+Broker 18
  20. 20. Driving de-facto standards: cross domains 19 The FIWARE Context Broker Technology has been selected as a new CEF (Connecting Europe Facility) Building Block Enabling public and private sector solutions regarding publication of right-time data The European Data portal will evolve to incorporate ability to publish right-time Open Data ETSI created Jan 2017 a new Industry Specification Group on cross-sector Context Information Management (ISG CIM) for smart cities applications and beyond. FIWARE NGSIv2 was the starting point for the CIM API to be specified: NGSI-LD FIWARE Context Broker to support NGSI-LD in the future The GSMA has published a Reference Architecture for IoT Big Data Ecosystem which recommends to mobile operators FIWARE NGSIv2 should be supported by implementers delivering the IoT Big Data ecosystem
  21. 21. Involving 117+ cities in 24+ countries. All of them agree to foster adoption of common principles: • Common API: FIWARE NGSIv2 • Compatible Open Data Publication platforms • Collaboration in definition of data models Identified as one of the most relevant Smart Cities Platform initiatives with a global footprint within the IES-City (IoT-Enabled Smart City) Framework TM Forum is working with FIWARE to deliver the key building blocks for enabling and connecting Smart City ecosystems TM Forum supports FIWARE NGSIv2 for real-time access to context information in cities TM Forum and FIWARE collaborate towards development of data marketplace platform components Driving de-facto standards: Smart Cities 20
  22. 22. Driving de-facto standards: Smart Industry 21 FIWARE Foundation and IDSA signed a MoU under which both organizations will collaborate towards delivery of a first open source implementation of the IDS Reference Architecture using FIWARE Technologies FIWARE Context Broker is the core of IDS Connectors in proposed implementation A first version of an OPC-UA Agent has been developed enabling integration of systems exporting an OPC-UA interface with the FIWARE Context Broker The Fast RTPS technology, integrated as Generic Enabler of FIWARE has been adopted as default communication middleware in ROS2 The FIWARE Community is working towards providing a Fast RTPS interface of the FIWARE Context Broker
  23. 23. FIWARE Platform Architecture overview ▪ FIWARE components can be assembled together and with other 3rd-party platform components to accelerate the development of Smart Solutions ▪ The core and only mandatory component of any “Powered by FIWARE” platform or solution is the FIWARE Orion Context Broker ▪ FIWARE is not about take it all or nothing: you are not forced to use complementary FIWARE components but other 3rd-party platform components to design the hybrid platform of your choice 22 Data/APIManagement PublicationMonetization Core Context Management (Context Broker) Context Processing, Analysis, Visualization Interface to IoT, Robotics and third party systems Deploymenttools
  24. 24. Data/APIManagement PublicationMonetization Core Context Management (Context Broker) Context Processing, Analysis, Visualization Interface to IoT, Robotics and third party systems Deploymenttools Mapping of FIWARE GEs 23 Development of Context-aware applications (Orion, STH-Comet, Cygnus, QuantumLeap, Draco) Connection to the Internet of Things (IDAS, OpenMTC) Real-time processing of context events (Perseo) Handling authorization and access control to APIs (Keyrock, Wilma, AuthZForce, APInf ) Publication and Monetization of Context Information (CKAN extensions, Data/API Biz Framework, IDRA) Creation of Application Dashboards (Wirecloud) Real-time Processing of media streams (Kurento) Business Intelligence (Knowage) Connection to robots (Fast RTPS) Big Data Context Analysis (Cosmos) Cloud Edge (FogFlow) Documents exchange (Domibus) Full Member in White Incubated GEs in Yellow
  25. 25. Cosmos BigData ▪ The Cosmos BigData Analysis GE is intended to bring tools enabling analysis of both batch and stream context information ▪ Batch analysis relies on Hadoop (which may be based on OpenStack’s Sahara or be a customized Hadoop deployment) and Cosmos brings some added features: ▪ User Accounts Management ▪ OAuth2 authorization and access control support ▪ REST APIs for MapReduce jobs submission and management ▪ Stream analysis relies on Storm and Cosmos brings an intuitive graphical interface for: ▪ programming analysis algorithms ▪ management of Storm clusters 24
  26. 26. Cygnus and STH Comet ▪ Cygnus enable to persist historic context information into: ▪ HDFS, the Hadoop distributed file system. ▪ MySQL and PostgreSQL, the well-know relational database managers. ▪ CKAN, an Open Data platform. ▪ MongoDB and STH (Short-Term Historic) ▪ Kafka queues ▪ DynamoDB, the cloud-based NoSQL database ▪ CartoDB, the geolocated platform ▪ STH Comet provides a MongoDB context data storage for short-term context information history ▪ Fast response for queries on short-term context information history 25
  27. 27. Big Data analytics 26
  28. 28. Draco ● The Draco Generic Enabler takes care of the data ingestion and persistence. Is a is an easy to use, powerful, and reliable system for processing and distributing data. Internally, Draco is based on Apache NiFi. ● NiFi is a dataflow system based on the concepts of flow-based programming. It supports powerful and scalable directed graphs of data routing, transformation, and system mediation logic. It was built to automate the flow of data between systems. 27
  29. 29. Fiware Draco MiniNiFI (low profile version) 28
  30. 30. Key part for Fiware Big Data ecosystem ● Intended for Big Data Streaming analysis. 29
  31. 31. 30
  32. 32. 31
  33. 33. Features ● Currently ○ Based on Apache NiFi. ○ NGSI 2 Support both for ingestion and serialization to have full integration with the Orion Context bróker. ○ Several persistant backend : ■ MySQL, the well-know relational database manager. ■ MongoDB, the NoSQL document-oriented database. ■ PostgreSQL, the well-know relational database manager. ○ Templates for some common scenarios ○ Rest API ● Getting started : https://fiware-draco.readthedocs.io/en/latest/quick_start_guide/index.html 32
  34. 34. IDAS ▪ FIWARE NGSI is capable to deal with the wide variety of IoT protocols today ▪ Rather than trying to solve the battle of standards at IoT level, it brings a standard where no standard exists today: context information management 33 FIWARE Context Broker FIWARE NGSI API (northbound interface) IoT Agent-1 IoT Agent-2 IoT Agent-n IoT Agent Manager create/monitor IDAS (southbound interfaces) OPC UA MQTTIETF CoAP OMA LWM2M FIWARE IoT platform components or alternative IoT platform supporting connection to Context Broker technology
  35. 35. Kurento ▪ Kurento is a WebRTC media server and a set of client APIs making simple the development of advanced video applications ▪ Kurento Media Server features include group communications, transcoding, recording, mixing, broadcasting and routing of audiovisual flows 34
  36. 36. WireCloud - Dashboards ▪ Fully customizable and extendable by the development of new widgets and operators ▪ Ready-to-use support for the FIWARE’s data models ▪ Share your dashboards with specific users or make them public. Moreover, your can embed your dashboards on third-party web pages 35
  37. 37. Knowage ▪ Knowage is a Business Intelligence suite bringing innovative themes and engines. ▪ Knowage offers a wide range of analytical tools: ▪ Reporting ▪ Multidimensional analysis (OLAP) ▪ Charts ▪ KPIs ▪ Interactive cockpits ▪ Geo-based business Intelligence analysis ▪ Free Inquiry ▪ masterdata management ▪ Data mining and network analysis ▪ Execution of external processes ▪ ETL ▪ … 36
  38. 38. Extended CKAN and Data/API BIZ Framework ▪ CKAN is a data management platform that makes data accessible by enabling the publication, search, and consumption of datasets ▪ CKAN is probably the most widely open data publication platform used today ▪ CKAN extensions has been developed in FIWARE to enable: ▪ Managing NGSI API queries as “dynamic” datasets ▪ Assignment of Access Rights Policies to datasets ▪ Managing Access Rights acquisition ▪ Binding pricing to datasets (acquisition and access) ▪ FIWARE Biz Framework components rely on TM Forum Business Open APIs 37 Open APIs • Catalog • Product offering • Product inventory • Billing • Party/Customer
  39. 39. Pay per use monetization of data in FIWARE 38
  40. 40. Access Control in FIWARE 39
  41. 41. FIWARE Ecosystem ▪ A framework of open source platform components which can be assembled together and with other third-party components to accelerate the development of Smart Solutions. Access Control
  42. 42. IAM Generic Enablers Identity & Access Control Management ▪ Keyrock – Identity Management ▪ Wilma – PEP Proxy ▪ AuthZForce – Authorization PDP
  43. 43. Keyrock Main features Web Interface and Rest API for managing Identity ▪ Users, devices and groups management ▪ OAuth 2.0 - based Single Sign On ▪ Application - scoped roles and permissions management ▪ Support for local and remote PAP/PDP ▪ JSON Web Tokens (JWT) and Permanent Tokens support ▪ European eID authentication compatibility (CEF eIDAS)
  44. 44. PEP Proxy for securing service backends ▪ Basic and complex AC policies support ▪ OAuth 2.0 Access Tokens support ▪ JSON Web Tokens (JWT) support ▪ Custom PDP configuration ▪ Integrated with API Management tools • APInf & API Umbrella • KONG Wilma Main features
  45. 45. PAP and PDP Server for managing complex AC policies ▪ XACML-3.0 standard-compliant ▪ Cloud-ready RESTful ABAC framework with XML optimization ▪ Multi-tenant REST API for PDP and PAP ▪ Standards: ▪ OASIS: XACML 3.0 + Profiles (REST, RBAC, Multiple Decision) ▪ ISO: Fast Infoset ▪ Extensible to attribute providers (PIP), functions, etc. AuthZForce Main features
  46. 46. Identity and AC Management Accessing GEs and services IAM Infrastructure IdM PAP Policies DB PDP Service Applica8on Service Backend PEP OAuth2 flow Request + token Check auth
  47. 47. Identity and AC Management Level 1: Authentication IAM Infrastructure IdM Service Application Service Backend PEP OAuth2 flow Request + token Check token
  48. 48. Identity and AC Management Level 2: Basic Authorization IAM Infrastructure Service Application Service Backend PEP OAuth2 flow Request + token IdM PAP PDP Check token & authorization
  49. 49. Identity and AC Management Level 3: Advanced Authorization IAM Infrastructure IdP Service Application Service Backend PEP OAuth2 flow Request + token Check token PAP Policies DB PDP Check auth
  50. 50. API Management APInf & PEP Proxy Back-end Request+ APIKey Web App Back-end Back-end Back-end
  51. 51. API Management APInf & PEP Proxy Back end App IAM Infrastruture Request+ access-token Web App OauthLibrary PEP Proxy access-token OK + user info (roles) Oauth2 flows access_token Back end App Back end App Back end App
  52. 52. eID Integration CEF eIDAS ▪ eIDAS (electronic IDentification, Authentication and trust Services) is an EU regulation to enable secure and seamless electronic interactions between businesses, citizens and public authorities. ▪ Access to European services by national eID eIDAS country 1 eIDAS country 2 eIDAS country 3 Service User country 2 eID
  53. 53. eID Integration FIWARE Identity Gateway IAM Infrastructure IdP Service Application Oauth 2.0 requests access-token User info request eIDAS eIDAS node 1 IdP 1 eIDAS node 2 IdP 2 … SAML flow Authentication
  54. 54. Checkout http://developer.fiware.org ! 53
  55. 55. Simple Smart solutions: Generic Reference Architecture ▪ Four major layers: ▪ Data acquisition ▪ Data management ▪ Data processing ▪ Application layer ▪ Cross-layer vertical Identity Management and Access Control ▪ Data adquired from sensors or third systems (e.g., weather service) ▪ More or less sophisticated data processing and visualization functions 54
  56. 56. Smart solution: Reference Architecture (FIWARE) ▪ Context Information Management layer based using FIWARE Context Broker technology ▪ Ability to integrate third IoT platforms or use FIWARE IoT agents developed as part of the IDAS NGSI Agent Framework ▪ Integration of FIWARE Context Broker technology with most popular Apache processing engines (Spark, Flink, Hadoop) ▪ Advanced web mashup and Business Intelligent components 55
  57. 57. FIWARE: supporting a system of systems architecture ▪ Organizations (cities, farm, factories, hospitals, etc) facing transformation into Smart organizations have to cope with the integration of multiple smart vertical solutions coming from multiple parties ▪ There is a need to integrate data to build a holistic picture of what is going on in right-time (context data) on top of which smart management systems can be developed at overall organization-level ▪ A Reference Architecture for such organizations will look like a “System of Systems” ▪ Key properties in “System of Systems” architectures: ▪ Replaceability (systems can be replaced) ▪ Extensibility (new systems can be added easily) ▪ Loose coupling (systems can evolve independently) ▪ Low intrusiveness (systems do not need to change) 56
  58. 58. Smart City Reference Architecture 57
  59. 59. Smart Farm Management Reference Architecture 58
  60. 60. Smart Factory Reference Architecture 59
  61. 61. Industrial Data Spaces 60
  62. 62. Industrial Data Spaces 61
  63. 63. 62
  64. 64. 63
  65. 65. 64 But we are not creating just technology …. … but a sustainable open innovation ecosystem
  66. 66. 65 #Community #Ecosystem
  67. 67. 66
  68. 68. 67
  69. 69. 68
  70. 70. 69
  71. 71. 70 EasingExperimentation#
  72. 72. Thank you! http://fiware.org Follow @FIWARE on Twitter 71 ThinkingGlobal# #
  73. 73. Thank you! http://fiware.org Follow @FIWARE on Twitter 72 ActingLocal#
  74. 74. Thank you! http://fiware.org Follow @FIWARE on Twitter 73 AcceleratingBusinesses#
  75. 75. FIWARE: Technology but much more ▪ Mission: build an open sustainable ecosystem around public, royalty-free and implementation-driven software platform standards that will ease the development of new Smart Applications in multiple sectors ▪ Pillars: 74 eHealth tourism Transport, Mobility and Logistics e-government Smart Energy Grid … the open source platform of choice for developing smart applications a meeting point where innovation happens and users can experiment with the technology activate funds and accelerate the business of entrepreneurs using the technology reach a global footprint, opening to regions that share the same vision and ambition support development of the community at local level, bringing support, training, certification
  76. 76. 75
  77. 77. 76 http://www.fiware.org
  78. 78. Thank you! http://fiware.org Follow @FIWARE on Twitter Juanjo Hierro FIWARE Foundation CTO juanjose.hierro@fiware.org www.slideshare.net/JuanjoHierro
  79. 79. 78 ▪ Goal: Noise monitoring and sound event detection and identification ▪ Target customers: smart cities, smart spaces, security companies ▪ Main features: ▪ advanced and innovative analysis using 3D audio captures ▪ monthly and daily readings and statistics
  80. 80. 79 ▪ Goal: Turning Fleet Maintenance into an exact science ▪ Target customers: transport sector, field service fleets, … ▪ Main features: ▪ Simple installation ▪ Continuous mechanical analysis in real time ▪ Advanced Artificial Intelligence Techniques for predictions ▪ Real-time notification to management and workshops
  81. 81. ▪ Goal: Free livestock monitoring ▪ Target customers: livestock farms ▪ Main features: ▪ Monitor free livestock using IoT collars weared by each animal ▪ Position, activity, inventory, anomalies ▪ Ecosystem with veterinarians, livestock markets, etc. ▪ Save money by early detection of sick animals ▪ SIGFox / LORA / 3G 80
  82. 82. ▪ Goal: Remote monitoring and optimized replenishment of silos in farms ▪ Target customers: farms and feed suppliers ▪ Main features: ▪ patented 3D scanning ▪ easy installation (5 mins) ▪ no batteries (solar panel) ▪ collaborative platform for farmers and feed suppliers 81
  83. 83. ▪ Goal: Non invasive osteoporosis prevention ▪ Target customers: Osteoporosis concerned population ▪ Main features: ▪ Measurement of indicators for bone mass creation (exercise, UV radiation, calcium ingest…) ▪ Daily monitoring of exercises ▪ Bluetooth LTE ▪ Attractive design ▪ Gamification and engagement 82
  84. 84. IoT would be an enabler, no barriers because of complexity 83 Context Broker Standard API GET <Oauth token> /V1/contextEntities/crop1/attributes/humidity Reading the value provided by a sensor should be as easy as reading an attribute of an entity “I don’t care what low-level IoT protocol is used” “I should not need to handle connectivity with IoT devices”
  85. 85. Actuation on a device should come as a side effect derived from updating the attribute of an entity PUT <Oauth token> /V1/contextEntities/crop1/attributes/watering “on” IoT would be an enabler, no barriers because of complexity 84 Context Broker Standard API “I don’t care what low-level IoT protocol is used” “I should not need to handle connectivity with IoT devices”
  86. 86. Open data publication Once context information is gathered, other useful FIWARE enablers can be used 85 Advanced Web-based UI (AR, 3D) Data/Apps visualization Big Data AnalysisComplex Event Processing Multimedia processing IoT-enabled Context Information Management
  87. 87. FIWARE as basis for a “System of Systems” Architecture ▪ No single company can provide the best solution for all challenges ▪ Need to integrate solutions coming from multiple parties 86 Smart Public Transport Citizen • Birthday • Preferences • Location • ToDo list Shop • Location • Business name • Franchise • offerings

×