Creating powerful value-chains

The FlexibleWareTM technology transforms embedded software in a set of components. Components can be generated automatically from any type of software - typically standard object code written in C or C++, JAVA, assembly, etc....

After code transformation, a component represents a set of well-defined services to the rest of the system's software and is handled in a homogeneous way, whatever the level of functions it implements (drivers, OS native, applications ...).

Open-Plug’s provides a range of tools allowing easy integration of components in a completed embedded system for mobile phones. At run-time the components dependencies are resolved in a controlled way through a patented mechanism which is part of the embedded real time system.

Consequently Open-Plug's mobile phone software technology becomes much more manageable, e.g. embedded system functionality changes becomes a straightforward process, as simple as adding a file into a directory. Now supporting multiple hardware platforms with the same software, or a last minute product specification change requiring an additional functional component is handled by a simple click.

Today the FlexibleWareTM technology is integrated in Open-Plug’s ELIPS product offering.

Three steps: generate, integrate, update

Step 1 - Generate software components
Open-Plug technology breaks down any complex software system into components based on the system integrator or software developer requirements. Components are automatically generated from the initial code. Security and access rights are applied independently per components and specified in the components connector. In a few days, a complete system can be divided into a robust, modular, component based system, easy to support and to update. Once in component form, software components can be tested easily against handset-specific or generic handset functionality.

2 - Integrate and validate the system
The Component Integration is performed as a simple drag & drop exercise of the different components. Each component dependency and resource requirement it has with the rest of the system is specified in its connector. The OP-Engine, running on the embedded platform and providing the components communication media via the SoftBus, provides access to the resource of the system, when needed and authorized. The Validation task can be performed automatically with minimal intervention and can be naturally divided between developers and integrators. The end result is a robust new image of the device software which can be developed and validated in a few days.

Step 3 – Update the software components
As in the re-arranged system the firmware consists of a collection of homogenous and independent software components, the product function can easily be modified. In the event of bug fixes or upgrade needs, any component can be independently updated, or new components can be added based on operator's needs or end-user demand for new service offerings.