 |
|
The Adoption of OMA Enablers over
Time
|
| (Click for a larger image) |
InnoPath’s
ActiveCare solution is fully compliant with Open
Mobile Alliance – Device Management (OMA-DM)
standards, while extending upon these as required
based on service providers’ unique requirements.
Over the last half decade, InnoPath has served
in a variety of key roles in the development
and adoption of OMA-DM standards, and has been
responsible for over 250 submissions as well
as donations of source code.
InnoPath’s products have successfully
demonstrated interoperability at OMA-DM sponsored ‘test
fests” covering the basic DM protocol as
well as many of the enablers, and in Summer,
2009, InnoPath was the only OTA management company
invited to demo its products at an OMA plenary
meeting, documented here.
The company’s standards support permits
deployment of its ActiveCare server in conjunction
with 3 rd party DM clients, such as those supporting
Firmware Updates, or, deployment of our clients
against 3 rd party servers. Compliance is reflected
in the three components of the company’s
ActiveCare portfolio:
- Frontline Care: The ActiveCare server
communicates to the ActiveCare client via DM
1.2. The client implements
a set of libraries that control various aspects
of the phone. Where a standard exists, such
as with Lock and Wipe or Device Control, the
client implements to the latest enabler. Where
a standard is still in draft, such as with
Mobile Check or Check and Correct, the client
implements to the DM framework using InnoPath
or service provider defined management objects.
The ActiveCare frontline care solution relies
on both the InnoPath server and client to derive
maximum benefit, though some capabilities have
been demonstrated with 3 rd party DM clients.
- Mobile Update: The server communicates
with an InnoPath or 3rd party client that
implements DM as well as the FUMO enabler (for
Firmware Updates). InnoPath also offers an
update client, embedded on the phone and
interoperable with 3 rd party DM servers. When
Mobile Update is deployed in support of Open
OS devices, a special client is also offered
that is designed to be deployed in conjunction
with the company’s server to optimize
the user experience.
- Mobile Activate: The server communicates
with an InnoPath or 3 rd party client that
implements DM or CP. Here, the solution is
designed to interoperate with the greatest
number of open market handsets. Where DM is
available, the data provisioning is more reliable
and the user experience is enhanced.
|
