Application Deployment Engine

Sending Mobile Applications or Mobile Content (e.g. wallpapers) to a mobile handset can be a complicated process. Mobile content typically comes in many different versions for all the different handsets available, and different handsets support different download processes. The VISION Application Deployment Engine (ADE) streamlines this process by automatically determining the handset and appropriate Application or Content for the handset.

The VISION ADE attempts to automatically determine the target mobile handset. This results in one of three possible outcomes:

Handset Status	Application Version	Result
Recognised	Available	Application downloaded to handset
Recognised	Unavailable	“Handset not supported” message send to handset
Unrecognised	N/A	Handset is presented with a list of all supported handsets for the target application for the user to choose from.

Within ADE, an “Application” represents either a Mobile Application (e.g. a B2B application or mobile game) or some other distributable content (e.g. a Wallpaper). If both the target device and “Application” support DRM1 then the “Application” is Forward-Locked to prevent copying to other devices.

An “Application” has one or many “Versions”. Each “Version” is used to represent the target platform, e.g. there may be one “Application” with a Nokia Series 40 “Version” and a Nokia Series 60 “Version”.

Each “Version” in turn will have multiple “Revisions” assigned to it. These “Revisions” represent the development cycles, e.g. Revision 1.0, Revision 1.1, etc... When the Mobile Application is requested, the latest “Revision” is automatically sent.

This separation allows for detailed reporting on the deployment of the “Application”. It is possible to see which “Version” is being downloaded most often, and which “Revisions” are currently active.

Back to VISION