R & D Laboratory

This line of research is inspired by the ongoing projects FSO middleware from freesmartphone.org and the brand new oFono.org API. Proteus Middleware Framework coincides with both projects in the main goal, building a software stack providing a consistent API for application programmers, so they should be able to concentrate on their business logic, and avoid to handle multitude of libraries or interprocess communication interfaces.

Proteus Middleware Framework, from now on PMF, can be considered as a generalization of FSO or oFono middlewares, because it is focused in a more widespread variety of embedded devices, rather than only telephone devices.

As FSO or oFono do it, PMF is built on D-Bus (Desktop Bus) as a simple and consistent inter-process communication system, so D-Bus is the entry point of communication with the operative system resources (drivers), and other high level applications registered in the framework.

With PMF we go beyond D-Bus iter-proccess communication nature, we extend the local (within the same device) nature of D-Bus to the network scope: by means of this concept, a remote application could invoke remote procedures, actually remote D-Bus services, using the same API as it would be in the local scope.

In order to make a bridge betwen the local D-Bus system and remote applications, we merge our Proteus Middleware Framework with the Internet Communication Engine from Zeroc for embedded devices (ICE-E).

The following is a stack architecture layout of our BSP concept based on Proteus Middleware Framework:

You may check out a read-only working copy anonymously over HTTP. Use this command to anonymously check out the latest project source code:

svn checkout http://amebasystems.googlecode.com/svn/research/proteus proteus