|
| |
Several
service providers have identified backup of phone
data as being a top customer issue. As phones offer
more functionality, the data that they store grows
more important. Beyond the all-important address book,
phones today store other kinds of data such as photographs,
videos, messages, and downloaded content. Thus, as
the phones grow in their capacity to store and manage
data, the value of the phone grows. This makes it
even more important to safeguard the phone. If the
phone is lost, the damage done is more than the expense
of a replacement: it is the loss of irreplaceable
data that causes greater pain. In the UK alone, over
700,000 phones go missing (lost or stolen) each year.
In addition to being a
pressing customer issue, the loss of a handset has
a revenue impact on the service provider if it is
a mobile operator. After all, it provides a pre-paid
subscriber with an opportunity to churn. Even if the
subscriber does not churn, it results in a significant
drop in call volume as the subscriber builds the contact
list again. An Asian operator measured an ARPU drop
of 70% in the first month alone, for subscribers who
reported lost phones. This makes address book backup
an even more valuable service for operators.
|
| |
The
main issue to deal with is solution fragmentation.
A plethora of available techniques exist: SyncML,
Nokia/SE/Samsung/Motorola PC-based software, and STK
applications that reside on the SIM card. Ripple Vault
is the only comprehensive solution to the backup problem.
It approaches the problem from all angles, and focuses
on delivering an optimal user experience, taking into
account the device and the situation.
Users with smart phones can experience
unattended backup. The backup experience is integrated
with the native applications on the device, and runs
in the background. Without the user having to press
a single key, Vault ripples data between the handset
and the web store. The service is delivered non-intrusive
to the user, but the user can request to be prompted
before the data transfer takes place for select items
such as photos, or videos. This gives the user flexibility
in choosing what data is more important to them.
|
| |
Users
with SyncML phones can have their data synchronized
with the web store via SyncML. Phones that do not
support SyncML can have the data archived by walking
into a retail store and connecting their device to
the Vault PC-suite, or by forwarding their data via
the SMSC/MMSC to a short code that is connected to
the web store. In short, each user has the ideal user
experience that can be provided based on the device
in hand, and the situation the user is in (At the
retail store? It may be simpler to connect to the
PC suite).
Positioned as an entry-level
data services offering, or as an add-on to phone insurance
plans, Ripple Vault ensures that your customers return
to you when they lose their phone. In addition, Ripple
also generates revenue from the service, through subscription
fees and usage charges. Our experience is that users
are willing to pay for a backup service that is easy
to use. Some customers ask to include ‘content
sharing’ options in order that they generate
additional revenue, and we invite you to keep this
in mind.
|
| |
In order to achieve high availability/reliability,
data consistency, scalability, and pluggable framework
architecture, Vault has been built on the J2EE 1.3/1.4
standards for application server frameworks, using
a classic n-tier client-server architecture. An MVC-II
design pattern is used in order to provide for quick
deployments especially in a managed service environment.
For more information on the architecture and integration
with existing systems within the service provider
environment, please contact us.
View
architecture of Ripple Vault.
Download
a marketing brochure on Ripple Vault.
|
| |
|
|
| |
|
|
|
|
|
|