FINODEX introduces FIWARE
1 like1,619 views
The document outlines training materials for the FIWARE platform, detailing its various technological enablers spread across seven macro areas including cloud hosting, data management, middleware, user interfaces, security, IoT services, and application delivery. Each area includes specific implementations designed to support functionalities such as resource management, data analysis, real-time event processing, security management, and device communication. The text describes various components and their roles in enabling cloud infrastructure and smart applications, emphasizing the integration of open-source standards and technologies.
FINODEX introduces FIWARE
- 1. This project is co‐ funded by the European Union Page 1 of 9 Part of the FI‐PPP FINODEX INTRODUCES TECHNOLOGIES
- 2. Deliverable 3.1v2 FI‐PPP Technologies training materials TECHNOLOGIES TRAINING MATERIALS The Technologies training materials is divided in seven macro area: 1. Cloud Hosting 2. Data/Context Management 3. Advanced middleware and interfaces to Network and Devices (I2ND) 4. Advanced Web‐based User Interface 5. Security 6. Internet of Things Services Enablement 7. Applications/Services and Data Delivery The figure shows the chapters and for each chapters the Generic Enablers. 1. CLOUD HOSTING The Generic Enablers for Cloud Hosting chapter are: 1.1. IaaS Resource Management GE ‐ FIWARE Implementation This GE provides the facilities to provision virtual machines, as well as to associated compute, storage and network resources. The implementation is based on OpenStack ‐ the rapidly emerging open source project providing cloud infrastructure middleware, being adopted by the wide ecosystem of organizations across the various industry sectors.
- 3. Deliverable 3.1v2 FI‐PPP Technologies training materials 1.2. Monitoring GE ‐ FIWARE Implementation Monitoring GE ‐ TID Implementation is the key component to allow incorporating monitoring and metering mechanisms in order be able to constantly check the performance of the system, but the architecture should be easily extended to collect data for other required needs. Monitoring involves gathering operational data in a running system. 1.3. Object Storage GE ‐ FIWARE Implementation This Generic Enabler Implementation provides robust, scalable object storage functionality based on OpenStack Swift. The OpenStack Swift API provides a standardised mechanism to manipulate both the binary objects that are stored, and the hierarchy of containers in which they are organised. This RESTful API can be accessed from any client technology that can communicate over HTTP. By leveraging OpenStack Swift, all the benefits of this rapidly maturing open‐source cloud storage solution can be realised. The highly‐available, distributed, and scalable features of swift can be exposed using commodity hardware. 1.4. PaaS Manager ‐ Pegasus Pegasus orchestrates the provisioning of the required virtual resources at IaaS level and the installation and configuration of the whole software stack of the application, taking into account the underlying virtual infrastructure. It provides a flexible mechanism to perform the deployment, enabling multiple deployment architectures: everything in a single server, several servers, or elastic architectures based on load balancers and different software tiers. Pegasus is a easy way to deploy your applications in the FIWARE Cloud. 1.5. Policy Manager ‐ Bosun The Policy Manager GE provides the basic management of cloud resources based on rules, as well as management of the corresponding resources within the FIWARE Cloud Instance like actions based on physical monitoring or infrastructure, security monitoring of resources and services or whatever that could be defined by a facts, actions and rules. Policy Manager is a easy rule engine designed to be used in the OpenStack ecosystem and of course inside the FIWARE Cloud. 1.6. Self‐Service Interfaces ‐ Cloud Portal The Self Service Interfaces provide a support for the users of the cloud infrastructure and platform to manage their services and resources deployed in cloud. For the moment it consist of open source implementation of a User Portal and Scripts. 1.7. Software Deployment & Configuration ‐ Sagitta Sagitta (the Software Deployment and Configuration ‐ SDC ‐ GE), which is the key enabler used to support automated deployment (installation and configuration) of software on running virtual machines. As part of the complete process of deployment of applications, the aim of Sagitta is to deploy software product instances upon request of the user using the API or through the Cloud Portal. 2. DATA/CONTEXT MANAGEMENT The Generic Enablers for Data/Context Management chapter are: 2.1. BigData Analysis ‐ Cosmos Cosmos is an implementation of the Big Data GE, allowing the deployment of private computing clusters based on Hadoop ecosystem. Current version of Cosmos allows users to: • I/O operations regarding Infinity, a persistent storage cluster based on HDFS. • Creation, usage and deletion of private computing clusters based on MapReduce and SQL‐like querying systems such as Hive or Pig. • Manage the platform, in many aspects such as services, users, clusters, etc, from the Cosmos API or the Cosmos CLI
- 4. Deliverable 3.1v2 FI‐PPP Technologies training materials 2.2. Complex Event Processing (CEP) ‐ Proactive Technology Online The CEP GE analyses event data in real‐time, generates immediate insight and enables instant response to changing conditions. While standard reactive applications are based on reactions to single events, the CEP GE reacts to situations rather than to single events. A situation is a condition that is based on a series of events that have occurred within a dynamic time window called processing context. Situations include composite events (e.g., sequence), counting operators on events (e.g., aggregation) and absence operators. The Proactive Technology Online is an implementation of the FIWARE CEP (Complex Event Processing) GE. 2.3. Publish/Subscribe Context Broker ‐ Orion Context Broker The Orion Context Broker is an implementation of the Publish/Subscribe Context Broker GE, providing the NGSI9 and NGSI10 interfaces. Using these interfaces, clients can do several operations: • Register context producer applications, e.g. a temperature sensor within a room • Update context information, e.g. send updates of temperature • Being notified when changes on context information take place (e.g. the temperature has changed) or with a given frequency (e.g. get the temperature each minute) • Query context information. The Orion Context Broker stores context information updated from applications, so queries are resolved based on that information. 2.4. Stream‐oriented ‐ Kurento The Stream Oriented GE is a development framework that provides an abstraction layer for multimedia capabilities, allowing non‐expert developers to include interactive media components to their applications. At the heart of this enabler there is the Open API. A REST‐like API, based on JSON RPC 2.0, exposing a toolbox of Media Elements that can be chained to create complex media processing pipelines. The Stream Oriented GE provides several client implementations of the Open API. The Java client allows developers to include media capabilities to Java or JEE applications. There is also a Javascript client ready to be used with NodeJS or directly in browser applications. Thanks to these, the Stream Oriented GE provides developers with a set of robust end‐to‐end interoperable multimedia communication capabilities to deal with the complexity of transport, encoding/decoding, processing and rendering tasks in an easy and efficient way. 3. ADVANCED MIDDLEWARE AND INTERFACES TO NETWORK AND DEVICES The Generic Enablers for I2ND chapter are: 3.1. Network Information and Control ‐ OFNIC OFNIC is a reliable and distributed Software Defined Network (SDN) controller for enterprises’ OpenFlow‐enabled network. It enables the abstraction and virtualization of network resources and functionalities. OFNIC also monitors the status of the network and provides near real‐time data about network statistics with different levels of granularity (flow, node, port). 4. ADVANCED WEB‐BASED USER INTERFACE The Generic Enablers for Advanced Web‐based UI chapter are: 4.1. 2D‐UI A JavaScript library that handles generic web user interface input events like keyboard and mouse. This GE provides means to dynamically add existing input devices input events such as touch pads and gamepad, and input event abstraction to handle keyboard key and mouse button combinations. The goal is to provide support for advanced, Web‐based, highly dynamic, and potential 3D user interfaces. 4.2. 2D/3D Capture 2D 3D Capturing is capture contextual information related a 2D 3D scene of the surrounding so that the data can be used to provided to or as services. Location information, lighting information, device orientation, heading direction
- 5. Deliverable 3.1v2 FI‐PPP Technologies training materials are the necessary contextual information and based on the service these other information available to the browser can be used. 4.3. 3D‐UI‐XML3D XML3D is an extension to HTML5 for declarative 3D content represented as a scene graph like structure inside the DOM. All nodes within this graph are also nodes in the web sites DOM tree representation and can be accessed and changed via JavaScript like any other common DOM elements as well. On these DOM nodes, HTML events can be registered similar to known HTML elements. 4.4. 3DUI ‐ WebTundra WebTundra is the Web client for taking realXtend 3D virtual worlds into modern web browsers. The provided TundraSDK and TundraClient can connect to a realXtend Tundra server. Implementing the Tundra network protocol via WebSocket and rendering with WebGL. For networked multiuser usage requires a Tundra server (Synchronization GE server side). 4.5. Augmented Reality Augmented Reality Generic Enabler is a high‐level application programming interface for HTML5 Augmented Reality applications. Required run‐time environment is the JavaScript support of a suitable web browser. No plug‐ins are required. These applications may rely on the functionality of the other GEs, like XML3D Technology, POI Data Provider, etc. 4.6. Cloud Rendering The goal of this GE is to provide a generic way to request, receive and control a video stream of a remote 3D application. The complexity and usual heavy performance requirements for a 3D application can be offloaded to a server, from a low end device that could not handle the rendering otherwise. Cloud Rendering GE provides a web service that can be used to implement your own 3D application rendering and interactions with the web client. Also provided are accompanying web client that shows how to talk to the web service and a renderer for the realXtend Tundra 3D application SDK and the end user Meshmoon Rocket client. 4.7. GIS Data Provider ‐ Geoserver/3D This GE is able to host geographical data and serve it in 3D form (where applicable) to both mobile and web clients. The GE implementation is based on open source Geoserver project (GPL licensed) and W3DS extension. 4.8. Interface Designer The goal is to provide an easy‐to‐use full manipulator / editor of 3D objects within a scene. An in‐browser world editor that allows users to easily create, remove, and manipulate scene objects through variety of tools. This editor in particular utilizes Scene and EC model, in other words, manipulates entities, components and attributes. Manipulations can be done through GUI that consist of three parts: scene tree, EC editor, and additional toolbar, or directly into the scene via 3D manipulation helper objects such as transform gizmo / axis tripods, and grids. The GUI provides extensive editing of entities that cannot be otherwise done via a 3D manipulation helper, and also in most of the cases serves for fine‐tuning of values. 4.9. POI Data Provider POI (Points of interest) Generic Enabler is a web server kit that supports • storing information related to locations • serving queries by location and other criteria • can be configured to meet your data needs POI Generic Enabler makes it relatively easy to • Relate any information to places, e.g.
- 6. Deliverable 3.1v2 FI‐PPP Technologies training materials o Tourist attractions / services o Photos, videos, 3D content o Special location data of your business o Imaginary items of an outdoor game o ... • Search information by location and other criteria • Store information by location • Develop an application that utilizes those capabilities 4.10. Real Virtual Interaction A key aspect of Augmented Reality is that virtual content is not just presented embedded within the context of the real world, but that it should also allow users to interact actively with real objects and the objects to provide input to the user. Real Virtual Interaction generic enabler (GE) provides means for connecting real world devices consisting of sensors and actuators in to augmented or virtual reality applications. Since the real world sensors and actuators are not complex enough to contain necessary logic to publish themselves outside their immediate domain there needs to be a external service that is able to access these devices and to be able to share the access to other services and also directly to end‐users. This service provides security, data base for storing history and offline data, scalability and other cloud‐like features that make it easier for application and service developers to make use of the devices in various purposes. This GE also provides a practical prototype for publishing sensor and actuator information application developers derived from NGSI 9/10 format developed earlier in FIWARE. 4.11. Synchronization The Synchronization Generic Enabler presents a lightweight and generic network‐synchronized dynamic scene data model, and two communication protocols to interact with the model: SceneAPI, a RESTful HTTP API for non‐realtime querying and modification of the scene, and a WebSocket‐based bidirectional protocol for connected Web clients to receive continuous real‐time scene updates, and to post their real‐time changes to the scene. It includes a server reference implementation based on the realXtend Tundra SDK, and a JavaScript client library. The scene data model is based on a hierarchy of Entities, Components and Attributes. A typical use case would be the implementation of a dynamic multi‐user virtual world, but as the data model is completely generic, it is by no means limited to that use case. 4.12. Virtual Characters This GE consists of an open standard and reference implementation for virtual characters on the Web. Web applications will be able to create, display and animate virtual characters. The characters can be composed of multiple mesh parts, to eg. allow easily swappable parts like upper or lower bodies, and attached objects such as clothing. The virtual character functionality is implemented as a JavaScript library, and is part of the WebTundra codebase, which also contains the 3D‐UI and Synchronization (client part) GE's. The 3D‐UI GE (which in turn uses the WebGL API through the three.js rendering library) is utilized for the Entity‐Component‐Attribute based scene model, the hierarchical transformation graph and implementing the actual rendering: a virtual character becomes part of the scene hierarchy and can be manipulated using the scene model's functions. 5. SECURITY The Generic Enablers for Security chapter are: 5.1. Authorization PDP ‐ AuthZForce You get the reference implementation of the Authorization PDP Generic Enabler (formerly called Access Control GE). Indeed, as mandated by the GE specification, this implementation provides an API to get authorization decisions based on authorization policies, and authorization requests from PEPs. The API follows the REST architecture style, and complies with XACML v3.0. XACML (eXtensible Access Control Markup Language) is a OASIS standard for authorization policy format and evaluation logic, as well as for the authorization decision request/response format.
- 7. Deliverable 3.1v2 FI‐PPP Technologies training materials The PDP (Policy Decision Point) and the PEP (Policy Enforcement Point) terms are defined in the XACML standard. This GEri plays the role of a PDP. To fulfill the XACML architecture, you may need a PEP (Policy Enforcement Point) to protect your application, which is not provided here. However, the PEP Proxy by UPM ‐ soon to be found on this catalogue ‐ provides such a component for protecting RESTful APIs in particular. 5.2. Identity Management ‐ KeyRock Identity Management covers a number of aspects involving users' access to networks, services and applications, including secure and private authentication from users to devices, networks and services, authorization & trust management, user profile management, privacy‐preserving disposition of personal data, Single Sign‐On (SSO) to service domains and Identity Federation towards applications. The Identity Manager is the central component that provides a bridge between IdM systems at connectivity‐level and application‐level. Furthermore, Identity Management is used for authorising foreign services to access personal data stored in a secure environment. Hereby usually the owner of the data must give consent to access the data; the consent‐giving procedure also implies certain user authentication. 5.3. PEP Proxy ‐ Wilma You get the reference implementation of PEP Proxy Generic Enabler. Thanks to this component and together with Identity Management and Authorization PDP GEs, you will add authentication and authorization security to your backend applications. Thus, only FIWARE users will be able to access your GEs or REST services. But you will be able also to manage specific permissions and policies to your resources allowing different access levels to your users. 5.4. Security Monitoring The Security Monitoring GE is part of the overall Security Management System in FIWARE and as such is part of each and every FIWARE instance. The Security Monitoring GE was designed to be offered as a services suite. The services provided, even if they can be used in isolation offer their most when used conjointly to cover the whole & primary usage pattern. Hereafter is the list of services offered by the Security Monitoring • MulVAL Attack Paths Engine • Scored Attack Paths • Remediation 6. INTERNET OF THINGS SERVICES ENABLEMENT The Generic Enablers for IoT chapter are: 6.1. Backend Device Management ‐ IDAS IDAS is an implementation of the BE Device Management GE, providing: • an ADMIN REST API for M2M application developers. • a DEVICE COMMUNICATION API for devices (sensor/actuators/gateways) communication. Currently it implements the following protocols: SensorML, Lightweight SensorML. • an NGSI9/NGSI10 interface towards NGSI enabled brokers, implemented by the "IoT Agent" component. • an opensource Reference Gateway for RaspberryPI and Z‐wave devices, called "FIGWAY". IoT integrators may port this software to their own gateway/devices hardware in order to easily interact with FIWARE IoT Backend. 6.2. Configuration Manager ‐ IoT Discovery IoT Discovery is an implementation of the Configuration Management GE, which focuses on semantically‐annotated IoT descriptions. The API provides two main modules: • Sense2Web Linked‐data platform • NGSI‐9 Server
- 8. Deliverable 3.1v2 FI‐PPP Technologies training materials 6.3. Configuration Manager ‐ Orion Context Broker The Orion Context Broker is an implementation of the Configuration Manager GE, providing the NGSI9 interfaces. Within the IoT chapter, it is aimed to be used in combination with IoT Broker GE (so the IoTBroker deals with NGSI10 in a stateless fashion, relying in Orion as persistent storage for NGSI9 registrations) although it can be also used as a stand alone component. Using the NGSI9 interface, clients can do several operations: • Register context producer applications, e.g. a temperature sensor within a room • Discover context producers information, e.g. which sensors are providing temperature for a given entity • Being notified when changes on context information availability 6.4. Gateway Data Handling GE ‐ EspR4FastData The Data Handling GE addresses the need to process data in real time. Frequently implemented features include filtering, aggregating and merging real‐time data from different sources. Thanks to Complex Event Processing (CEP), it is easy for applications to only subscribe to value‐added data which is relevant to them. CEP technology is sometimes also referred to as event stream analysis, or real time event correlation. EspR4FastData is a simple deployable servlet application. It features a dedicated REST management API, and a partial implementation of the standardized NGSI API. 6.5. IoT Broker The IoT Broker Generic Enabler is specified as a lightweight and scalable middleware component that separates IoT applications from the underlying device installations. The IoT Broker implementation available through the FIWARE Catalogue is the reference implementation of this Generic Enabler by NEC. 6.6. Protocol Adapter ‐ MR CoAP The MR CoaP Protocol Adapter allows you to plug devices using on CoaP over 6LowPan protocol within the IoT Architecture of FIWARE. The protocol adapter is designed to work with IBMs Moterunner platform and communicates via 6LoWPAN and uses CoAP as application layer protocol. The MR CoAP adapter is designed to use IBMs Mote Runner operating system. Moterunner is a run‐time platform running on the mote hardware that provides a virtual machine to execute device independent code. 7. APPLICATIONS/SERVICES AND DATA DELIVERY The Generic Enablers for Applications/Services and Data Delivery Framework chapter are: 7.1. Application Mashup ‐ Wirecloud Wirecloud builds on cutting‐edge end‐user development, RIA (Rich Internet Application) and semantic technologies to offer a next‐generation end‐user centred web application mashup platform aimed at leveraging the long tail of the Internet of Services. Web application mashups integrate heterogeneous data, application logic, and UI components (widgets/gadgets) sourced from the Web to create new coherent and value‐adding composite applications. 7.2. Marketplace ‐ WMarket The Marketplace provides functionality necessary for bringing together offering and demand for making business. These functions include basic services for registering business entities, publishing and retrieving offerings and demands, search and discover offerings according to specific consumer requirements as well as lateral functions like review, rating and recommendation. 7.3. Repository ‐ Repository RI The Repository is a core enabler of the FIWARE Business Framework. The repository provides a consistent uniform API to USDL service descriptions and associated media files for applications of the business framework. A service provider can use the Repository to publish the description of various aspects of the service according to a uniform description language.
- 9. Deliverable 3.1v2 FI‐PPP Technologies training materials 7.4. Revenue Settlement and Sharing System ‐ RSS RI The Revenue Sharing System (RSS) GE is in charge of distributing the revenues originated by the usage of a given service among the involved stakeholders. In particular, it focuses on distributing part of the revenue generated by a service between the Marketplace Provider and the Service Provider(s) responsible for the service. With the term "service" we refer to both final applications and backend application services (typically exposed through an API). Note that, in the case of composite services, more than one service provider may have to receive a share of the revenues. 7.5. Store ‐ WStore Store is the GE for selling services to both consumers and developers of Future Internet applications and services and for end‐to‐end managing of offerings and sales. While a marketplace is a platform for many stores to place their offerings to a broader audience and consumers to search and compare services and find the store where to buy, a store is owned by a store owner who has full control over a specific service/app portfolio and offerings. The final business transaction (buying) is done at the store and the whole back office process (end‐to‐end managing of offerings and sales) is handled by the store. Service Business Frameworks (SBFs) represent one of the cornerstones of service ecosystems. The key objective of a SBF is to build and support an ecosystem of applications and services that is sustainable and fosters innovation as well as cross‐fertilization. In particular, it consists of a number of interrelated components that support managing services in the business framework across the whole service lifecycle: from creation and composition of services to monetization and revenue sharing.