The Mobile Platform consists of
- the high performance message passing service (The Core)
- device recognition and rendering toolkit (WapWriter)
- reference services
- our state based logic controller (The Logic)
- the Context Engine.
These components are independent and pluggable, see the Figure below.
Components in Detail
The Mobile Platform uses message passing and queuing semantics. The high performance message parsing service (The Core) sits behind and interacts with the server farm infrastructure, and plugs into existing CMS, CRM or other domain level components. The Core manages the session and state on the user's handset. These sessions can be created on different machines, providing scalability.
The Core has a Logic module. This module contains all the information relating the availability of services to a user, and the user's state. A change in the state of the handset or a back-end service is communicated to the Logic, which then notifies dependent services.
Back End Services We provide reference blocks for the back-end services. We can automate any back-end service to work with The Core.
In addition to choreographing back-end services, there is another component(the WapWriter ) this formats the content to work well on the mobile phone browser. We call this formatted to fit. Our device recognition is based on WURFL. We use either our own implementation of the API, or an Apache Perl module or PHP library.
The fifth component of the Mobile Platform and a game-changing function is the use of a Context Engine (user identity, location, time, etc) to personalise and add improve the user experience (UX). This is because although the user wants personalised information, they do not want to spend time configuring filters. They want seamless and autonomous integration with their services.
Click to view magnified.