We use proprietary and third party's cookies to improve your experience and our services, identifying your Internet Browsing preferences on our website; develop analytic activities and display advertising based on your preferences. If you keep browsing, you accept its use. You can get more information on our Cookie Policy
Cookies Policy
Materializing the Interface to Networks and Devices (I2ND) in FI-WARE - FIWARE Forge Wiki

Materializing the Interface to Networks and Devices (I2ND) in FI-WARE

From FIWARE Forge Wiki

Jump to: navigation, search

Introduction

Contents

Following is a description of the assets that have been adopted as baseline for building a reference implementations of the GEs in the Interface to Networks and Devices (I2ND) chapter of FI-WARE. The reference implementation of a Generic Enabler is typically based on the evolution and integration of a number of assets, some being open source, therefore publicly available, while others being provided by partners of the FI-WARE project. A Backlog of Themes, Epics, Features and User-Stories followed for the evolution and integration of assets linked to the reference implementation of a Generic Enabler is also included.

Finally, a list of topics still being addressed at a high level follows the description of assets in this chapter. They are mapped into Themes and Epics in the Chapter Backlog. Features and User-Stories, derived from refined of these Theme and Epics will be allocated to Backlogs linked to GEs in the future.

For a comprehensive vision on the I2ND (Interface to Networks and Devices) chapter architecture, you can go here. We highly recommend you to read it before analyzing how reference implementations of GEs are being materialized.

The Roadmap of the I2ND chapter presents a description of the Technical Roadmap planned for the chapter, which will be developed through subsequent Releases of the FI-WARE Platform. Please also check the Releases and Sprints numbering, with mapping to calendar dates.

Network Information and Control - OFNIC

Baseline Assets

Epics

Features

Unit Testing Plan

Product guides

Advanced Middleware - Kiara

Baseline Assets

Epics

Features

Unit Testing Plan

Product guides


Robotics

Baseline Assets

Epics

Features

Unit Testing Plan

Product guides

Netfloc

Baseline Assets

Epics

Features

Unit Testing Plan

Product guides

Connected Device Interfacing [DEPRECATED]

Baseline Assets

  • WEB Runtime Engine is an environment to host widgets exploiting interfaces to connected device capabilities. it is based on WAC APIs, and it is developed for Android platforms.
  • Meego is a operating system designed for mobile devices, and can be extended to provide the necessary programming interfaces for WAC / PhoneGap APIs.
  • Web API is an implementation and framework for providing access to low level device functionality from inside a web browser. Such functionality is provided via a Javascript interface to hosted websites.
  • Reinforcement Learning is an algortihm for end-user QoE evaluation.

Epics

Features

Unit Testing Plan

Product Guides


Cloud Edge [DEPRECATED]

Note that the Cloud Proxy GE is shared between the "Cloud" and the "I2ND" (Interface to the Network) workpackages.


Link to the Cloud Proxy / Cloud Edge page in the "Cloud" WP: Materializing_Cloud_Hosting_in_FI-WARE#Cloud_Proxy


Baseline Assets

  • The ZigBee GAL (Gateway Abstraction Layer) is a C++ software which implements the specifications of the ZigBee Gateway and provides a proper abstraction of ZigBee devices and ZigBee networks.
  • The Cloud Proxy is a SW running on a device located at the edge of the network (between the WAN and the LAN) and that provides the required features to execute applications in the user's premises

Epics

Features

User Stories

Unit Testing Plan

Product Guides


Network Information and Control [DEPRECATED]

Baseline Assets

Epics

Features







Unit Testing Plan

Product Guides


Service, Capability, Connectivity and Control [DEPRECATED]

Baseline Assets

  • OpenEPC Platform is a software implementation inspired by the innovative all-IP aspects of the 3GPP Evolved Packet Core (EPC) enabling the prototyping of features like QoS and charging, mobility management, access and security for 3GPP and non-3GPP wireless technologies.
  • API mediation The API mediation component provides a set of APIs to several actors interacting API providers. It deals with non functional properties of API exposure, such as authorization and accounting.
  • Web Sharing Content It makes it possible to have personalized information sent to user by public devices or friends devices, even further allowing user to use its phone to interact with other device..
  • Voicemail enabler It makes it possible for a service provider to create voice based services.
  • Intelligent Network Identity Management enables intelligent ID management for multiple devices belongig to a user.
  • Network-centric Resource Management enables technology-independent control over network resources both in wireless and wired network domains.
  • Seamless Network Connectivity enables best connectivity for multi interface terminals incl. interface selection per flow and reservation of resources within the network.
  • Positioning Enabler enables Location-based Services (LBS), utilizing device position information. Computes the position fix of devices based on network-centric positioning methods functioning over the Evolved Packet Core (EPC). Implements various location management techniques based on cellular positioning technologies such as WiFi, Cell-Id etc. for provision of mobile and wireless applications and services.

Epics

Features

Unit Testing Plan

Product Guides


Personal tools
Create a book