FIWARE Based Application Development

Transcription

1 FIWARE Based Application Development 1

2 The Future Internet Public- Private Partnership (FI-PPP) Goal: capture new opportunities derived from Future Internet technology trends Broadband connectivity, IoT, Cloud, Big Data, etc Approach: boost innovation by fostering industrydriven ecosystem Generic Platform (FIWARE) Industry-specific platforms and trials ( Use-Cases ) Broader community of developers and entrepreneurs EC provides half of the funding: Transport, Mobility and Logistics Smart Energy Grid Smart Cities ehealth e-government Industry driven, major industry players involved FIWARE Based Application 2 Development Pan-european dimension

3 FIWARE: Targeting developers needs What Connect apps to the physical world IoT-M2M Enablers How Manage open data at large scale and transform it into knowledge Benefit from open innovation (crowd-sourcing, apps composition) Data/Context Enablers Integration and Composition Enablers Built-in APIs & tools Reach target users, monetize Business & Delivery Framework (revenue-share, cross-selling, ) Ensuring Privacy, Security and Trust Security Enablers Take the most of infrastructures while keeping costs lower and under control access from everywhere, adapt to devices Advanced Cloud Enablers Enablers easing interface to Network and Devices

4 FIWARE: Major Technical Chapters How Technical Chapters IoT-M2M Enablers IoT Services Enablement Built-in APIs & tools Data/Context Enablers Data/Context Management Integration and Composition Enablers Business & Delivery Framework (revenue-share, cross-selling, ) Apps/Services Ecosystem & Delivery Security Enablers Security Advanced Cloud Enablers Cloud Enablers easing interface to Network and Devices I2ND FIWARE Based Application 4 Development

5 FIWARE Generic Enablers (GEs) A FIWARE Generic Enabler (GE): set of general-purpose platform functions available through APIs Building with other GEs a FIWARE Reference Architecture FIWARE GE Specifications are open (public and royalty-free) FIWARE GE implementation (FIWARE GEi): Platform product that implements a given GE Open Spec There might be multiple compliant GEis of each GE Open Spec Available FIWARE GEis published on the FIWARE Catalogue The FIWARE project will deliver at least one reference implementation of FIWARE GEs: Based upon results of previous R&D projects Publicly available Technical Roadmap updated in every release Licensed with no costs within the FI-PPP program Commercialized under FRAND conditions or license as open source 5

6 FIWARE Instances Future Internet Applications run on top of FIWARE Instances that are built by FIWARE Instance Providers upon: selection of FIWARE GEis (products) from the FIWARE Catalogue assembly of selected FIWARE GEis with proprietary added-value products FIWARE Catalogue Future Internet App FIWARE Instance assemble FIWARE GE implementations 6 propietary product

7 FIWARE major differential features Cloud Data IoT Apps MiWi Security I2ND Federation of infrastructures (private/public regions) Automated GE deployment Complete Context Management Platform Integration of Data and Media Content Easy plug&play of devices using multiple protocols Automated Measurements/Action Context updates Visualization of data (operation dashboards) Publication of data sets/services 3D and AR visualization of context Advanced middleware Security Monitoring Built-in Identity/Access/Privacy Management QoS across datacenters (OpenFlow) FIWARE Based Application 7 Development

8 FIWARE Partners Some project partners 8

9 FIWARE Objectives (to UFU and USP) Create the conditions, at each region where the FIILAB is deployed, to support the development of innovative services and applications by local entrepreneurs Explore FIWARE Generic Enablers (GE), and Specific Enablers (SE) in order to reduce the time to market of these new services and applications Deploy FI-Lab Nodes in Brazil, creating the conditions for entrepreneurs to reach the market Collaborate with Future Internet initiatives fostering the use of technology that may help to provide a better living 9

10 Dissemination Model Focus on the region s potential business models, according the local context and ecosystem Each FIILAB will have the participation of four stakeholders of the innovation process: Higher Education Institutes (HEI) Start-ups and Small and Medium Enterprises (SMEs); Incubators and Accelerators Funding agencies and financing entities. Explore opportunities regarding Smart Cities, Internet of things, Mobile devices and Applications

11 FIWARE Architecture 11

12 Envisioned target Smart City platform RULES DEFINITION TOOL OPERATIONAL DASHBOARD KPI GOVERNANCE OPEN DATA PORTALS Real-time processing Data Quering/Action, Publish/Subscr BI ETL BigData Processing Open Data publishing City Services Inventory GIS CEP Service orchestrator Context Adapters Smart city platform as a Data/Knowledge Hub Non-intrusive, open to third parties Real Time Media Stream Processing Media streams Short-term historic data Context Broker Big Data IoT Broker & Config Management (from sensors to things) IoT Backend Device Management actuators measures / command s IoT / Sensor CKAN Open Data IDM & Auth Accounting & Payment & Billing Specific Enablers Generic Enablers

13 FIWARE IoT-M2M & Context/Management altogether Applications FIWARE NGSI-9/10 (entities: things, other) Other sources Context Broker CEP BigData Analysis IoT-enabled Context Management (entities: things) Backend FIWARE NGSI-9/10 IoT Broker IoT ConfigMan FIWARE NGSI-9/10 NGSI IoT Adapter IoT Backend Device Management Device-level Management API Backend Native NGSI IoT Agent Gateway/Devic e Platform GEs Native NGSI IoT Agent Gateway/Devic e Platform GEs Gateway/Devic e Platform GEs Gateway/Devic e Platform GEs 13

14 FIWARE Applications Reasoning 14

15 FIWARE Based Applications Based on challenges to developers, FIWARE fosters the creation of new services and applications that uses FIWARE architecture Some example of applications that are based on FIWARE enablers

16 Sample Application FI-GUARDIAN Monitor for adverse events Created by VM9, an SME from Nova Friburgo, Brazil Short Presentation Winner at the FIWARE contest held at Campus Party 2014 in the Smart Cities category. Prize 75K 16

17 FI-GUARDIAN Building Blocks Based on several generic enablers 17

18 FI-GUARDIAN Architecture Overview 18

19 FIWARE Resources Base Site FIWARE Enablers Catalog FIWARE E-Learning Platform FIWARE LAB 19

20 Publish/Subscribe Context Broker - Orion Context Broker Catalog Documentation E-Learning Platform Long video tutorial Programmers Guide er_-_orion_context_broker_-_user_and_programmers_guide Quick Start er_-_orion_context_broker_-_quick_start_for_programmers 20

21 Context management Context Management in FIWARE is about management of Context data (aka Context Information) Context Information is always relevant to entities, although entities can be anything (applications, users, things, ) Orion Context Broker intermediates between context producers and context consumers Orion Context Broker Applications 21 Slides prepared by Fermín Galán Márquez ([email protected]) Telefónica I+D

22 Orion Context Broker in a nutshell Context Producers Orion Context Broker subscriptions 1026 query Context Consumers update notify update update 1026 notify DB

23 NGSI API Based on Next Generation Services Interface (NGSI), published by Open Mobile Alliance (OMA) REST API (XML & JSON rendering) Additional convenience operations to ease some operations Context Availability Management (NGSI9) Register context sources (registercontext) Search for context sources (discovercontextavailability) Subscribe to context sources availability notifications (subscribecontextavailability, updatecontextavailabilitysubcription & unsubscribecontextavailability) Context Management (NGSI10) Update context information (updatecontext) Query context information (querycontext) Subscribe to context information notifications (subscribecontext, updatecontextsubcription & unsubscribecontext) 23

24 The NGSI information model Orion metadata: ID, location Custom metadata Context Element EntityId EntityType Context Element attributes Name has has Type 1 n Value 1 n Meta-data Name Type Value Electrical Regulator severity batterycharg e electricpotential Issues presence location TimeInstant illuminance Node Lamps Vans Technicians

25 Entity Creation (Request) Using an updatecontext 25

26 Entity Creation (Response) Using an updatecontext 26

27 Query Context (request) 27

28 Query Context (response) 28

29 FIWARE Context/Data Management Platform Applications OMA NGSI-9/10 Processing/Analysis Algorithms Gathered data is injected for processing/analysis Data generated either by CEP or BigData is published Distributed Context Sources Programming of rules Gathered data injected for CEP-like processing Complex Event Processing (PROTON) Context/Data Management Platform BigData (COSMOS) Processed data is injected for processing/analy sis Direct bigdata injection

30 How Orion fits in the FIWARE overall platform RULES DEFINITION TOOL Real-time processing OPERATIONAL DASHBOARD Data Quering/Action, Publish/Subscr KPI GOVERNANCE BI ETL BigData Processing OPEN DATA Open Data publishing PORTAL S City Services GIS CEP Service orchestrator Context Adapters Media Streams Processing media content Short-term historic data Context Broker measures / commands Big Data IoT Broker & Config Management (from sensors to things) IoT Backend Device Management CKAN IDM & Auth Accounting & Payment & Billing Media actuators IoT/Sensor Open Data 30

31 Orion in LiveDemo application Browser widgets Object Storage Wirecloud (javascript runtime) Wirecloud (server) Ticket Management Context Broker History Location Cosmos CEP NGSI IoT Adapter IoT Backend Device Management 31

32 Application Mashup - Wirecloud End-user UI development by using Widget and Mashups Widget A small application or piece of dynamic content that can be easily placed into a web page Often encapsulate a Web API (directly or through an operator) Can be easily embedded into webpages (HTML snippets) "Mashable" widgets generate/consume events, so that they can be wired together to create a lightweight application mashup This requires a widget platform Mashup Lightweight application combining data, services and UIs from multiple sources Developed by either IT or business staff, as well as by end users Created in hours or days, not months Uses a Web Oriented Architecture (WOA) Often relies on internal + external web services (Web APIs) Done at data, logic and/or presentation layers 32

33 Widgets and Mashups Widgets Mashups 33

34 Mashups and Operators Operators represents functionality managed at the presentation layer Empower the user to create data mashups (Access + Transform data sources) by piping + Web API wrapping Enhance widget functionality by wiring them each other 34

35 Application Mashup Wirecloud Resources Catalog Documentation E-Learning Platform Short video tutorial 35

36 Setting up your virtual infrastructure using FI-LAB Cloud Introduction to FI-LAB Cloud Hosting Deploying your first VM Deploying components for your application Object Storage API Reference Information FIWARE Based Application 36 Development

37 FI-LAB Cloud Hosting FIWARE Based Application 37 Development

38 FI-LAB Cloud Hosting Create your account in lab.fiware.eu Enter in the Cloud Portal Create your keypair (private/private key) Deploy your instance Add a public IP Open ports to the VM FIWARE Based Application 38 Development

39 Enter your and password to access to the FI-LAB. If you do not have it or forgot it, sign up or request for a new one. FIWARE Based Application 39 Development

40 You must create a keypair to access to the servers. FIWARE Based Application 40 Development

41 FIWARE Based Application 41 Development Choose the VM and click Lanch.

42 FIWARE Based Application 42 Development Allocate new IP

43 FIWARE Based Application 43 Development Open ports in your VM.

44 FIWARE Based Application 44 Development

45 Deploying components for your application Deploying applications and not only Servers. Ad hoc installation (not template usage). Managing applications in Servers (install, uninstall, configure, snapshot Deploying different environments for that applications. FIWARE Based Application 45 Development

46 Deploy example Blueprint template: fiware1 Servers: 2-5 Tier 1: Tomcat Blueprint Template: platform specification to be deployed. Tier: Each kind of software and server to be deployed. Each Tier can be deployed in one or several servers (e.g. tomcat, 2-5 servers). Server: 1 Context Broker Server: 1 Blueprint Instance: Deployed in the testbed. Tier 2: Context Broker Tier 3: MongoDB Context Broker 46

47 Demo You can open the Catalog of Blueprint Template or create one from the scratch. Press the option Blueprint Templates from menu FIWARE Based Application 47 Development

48 Demo You should introduce the Name and the Description. FIWARE Based Application 48 Development

49 Demo To add new Tier, press DemoSantander name. FIWARE Based Application 49 Development

50 Demo After press Add Tier you see this windows to define the servers of this tier. You must define a Keypair to access to those servers. Install software pressing the mouse right click. FIWARE Based Application 50 Development

51 Demo You should specify the maximum, minimum and current number of servers FIWARE Based Application 51 Development

52 Demo Press Action and select Press Action and select Lauch Template to launch the Instance. FIWARE Based Application 52 Development

53 Demo You should specify the Name You should specify the Name and Description for your blueprint. FIWARE Based Application 53 Development

54 Demo Firstly, we need to instantiate Firstly, we need to instantiate The servers. FIWARE Based Application 54 Development

55 Demo Secondly, the installation Secondly, the installation of the software. FIWARE Based Application 55 Development

56 Demo Pressing the name you can see the tiers of this blueprint. Finally, if all was ok. FIWARE Based Application 56 Development

57 Demo Press it to get information Press it to get information of your server. FIWARE Based Application 57 Development

58 Demo FIWARE Based Application 58 Development

59 Demo FIWARE Based Application 59 Development

60 Demo FIWARE Based Application 60 Development

61 Big Data Analysis - Cosmos Catalog Documentation E-Learning Platform Long video tutorial Programmers Guide _User_and_Programmer_Guide Quick Start _Quick_Start_for_Programmers 61

62 Complex Event Processing (CEP) 62

63 Stream and Multimedia - Kurento

64 CKAN CKAN is an open data management platform helps publishers make their data accessible and findable by potential users. Publisher: Data + Metadata Consumer: Browse, Search, Access CKAN Tour CKAN Features Overview FIWARE ecturedescription.data.ckan Cygnus conector 64

65 CKAN WireCloud Integration Cygnus Connector 65

66 CKAN Architecture Application Layer Data Layer 66

67 Security OAuth Course (OAuth in FI-LAB) OAuth Sample 67

68 Prova de Conceito MyBUS Aplicação baseada em Open Data (SETTRAN) Utiliza os Generic Enablers da Arquitetura FIWARE Baseada no conceito de Smart City com foco mobilidade urbana PUBLIC DATA BUSES INFORMATION Integration Controller UpdateContext CKAN Cygnus OrionCKANSink MyBus Front Controller NotifyContext Orion Context Broker NotifyContext Fi LAB Regional Center Infrastructure FI WARE FUTURE INTERNET INNOVATION LABORATORY (FIILAB) FIWARE Based Application 68 Development

69 Prova de Conceito MyBUS FIWARE Based Application 69 Development

70 PUBLIC DATA BUSES INFORMATION - Generator Open data from the municipality of Uberlandia For the workshop we will use sample data Data Generation com.br.control.linha131 Rest Web @Produces(MediaType.APPLICATION_JSON) 70

71 Integration Controller Standard Java console base application Main Calls the generator WebService Post data to Orion Get data from the Generator Serivce and Post Data to Orion GetInfoWebGen. GetBus GET - public void getbus() POST - public void sendtoorion() 71

72 Configure Orion to Notify MyBusFrontController { } "entities": [ { "type": "BusCar", "ispattern": "false", "id": "1" } ], "attributes": ["Latitude","Longitude"], "reference": " "duration": "P1M", "notifyconditions": [ { "type": "ONCHANGE", "condvalues": [ "Latitude","Longitude" ] } ], "throttling": "PT1S" 72

73 Configure Orion to Notify Cygnus { } "entities": [ { "type": "BusCar", "ispattern": "false", "id": "1" } ], "attributes": ["Latitude","Longitude"], "reference": " "duration": "P1M", "notifyconditions": [ { "type": "ONCHANGE", "condvalues": [ "Latitude","Longitude" ] } ], "throttling": "PT1S" 73

74 MyBusFrontController Receive Orion Notification Offers an interface for the Mobile App to get new information from a bus br.com.webbus.controller.orioncontroller Receives a notification from method=requestmethod.post) String getbusorion Deserialize to a Java Data object Stores new Data object in memory br.com.webbus.controller.busroutecontroller Offers buses position to the method=requestmethod.get) List<Bus> getlistbus 74

75 Bus Mobile App Activity responsible to get buses positions br.com.busapp.findbusactivity 75