We will extend the architecture displayed in the
third example
to include the option to update MIDlet state by sending
so called Blue SMS messages.
The user's mobile phone must support
MIDP2 profile.
The user download a MIDlet which already include the service moAccount and moCheers.
You can run this example on your mobile phone by visiting the WAP site
lemonade.e-marson.com and choosing 'BlueSMS moBank'.
Additionally, the same site provides an application called "BlueSMS sender"
which can be used to send Blue SMS messages that update the moAccount service.
You can install it on another mobile phone and use it to control the "BlueSMS
moBank" application installed on the first phone.
SCENARIO
The user downloaded and installed "BlueSMS mobank": the
"moAccount" and "moCheers" services are immediately available.
Upon each transfer,
the service provider (moBank) sends a special binary SMS message (we call it
Blue SMS message) to the user's mobile phone number. This message updates
the application state and notifies the user about a transfer.
The "BlueSMS moBank" application does not have to be running on the
mobile phone. When the Blue SMS arrives, the phone rings and
displays a notification - just like when a text message arrives.
When the user "opens" the Blue SMS, the "BlueSMS moBank" application
is automatically launched and the user sees a message about an
update.
The "moAccount" service state is updated - this way the user
always sees the current account balance and transfer history
even though the application never connects to the Internet.
Unlike text SMS messages that some banks send to their clients,
Blue SMS messages do not clutter the phone's inbox. They are handled
by the "moBank" application and disappear once the transfer history
is updated in the application.
FUNCTIONAL DIAGRAM
Functional diagrams are identical to those in the
third example.
LOCATION DIAGRAM
Location diagrams are identical to those in the
third example.
We need one installer which will be wrapped in a MIDlet.
The installer writes 1 to the UpdateNo node at "permanent" location
to indicate that the services "moAccount" and "moCheers" are already
installed. Additionally, an instruction that displays an update info
screen is written to UpdateMessage node at "permanent".
