|

InnoPath views MDM success as consisting
of three pillars – the server,
the client, and operational support
to both handset vendors and wireless
operators. IP2, the InnoPath Port
to Production Program, addresses this
third pillar. Wireless operators have
the following requirements:
- Accelerate the time to market
through rapid and efficient launch
of new devices
- Predictably manage the cost of
launching new devices
- Maximize the uptake of new high
ARPU services
At the same time, they, and their
handset partners, face challenges:
- The pace of innovation and complexity
of new devices as demanded by the
market
- Evolving OMA-DM standards that
are open to interpretation by handset
vendors
- Proper handset vendor interpretation
of operator device requirements
To meet the requirements of wireless
operators, handset manufacturers,
and mobile OS platform providers,
InnoPath offers a rich set of device
testing, standards verification, requirements
certification, and database programs.
Combined, they guarantee successful
MDM deployments across CDMA, GSM,
and now WiMAX, reducing time-to-market
and cost. The programs are based on
over five years of experience, a unique
end-to-end client server perspective
and expertise earned through successful
support of tier 1 operators and OEMs.
Port to Production, InnoPath’s
device testing program, offers support
throughout the process of OMA-DM
client porting, OMA-DM compliance
testing, and ensuring successful interoperability
with an operator’s specific
device and network specifications
leading to successful operator technical
acceptance.

Three services are offered depending
upon the requirement of the OEM:
 |
 |
 |
 |
|
 |
 |
|
| • |
A-la-carte
approach to lab and server
access & engineering
services |
| • |
Includes
IOT testing, Server Simulator
and access to public iMDM
server |
| |
|
| |
|
|
 |
 |
|
 |
 |
 |
 |
 |
 |
 |
 |
|
 |
 |
|
| • |
Full
porting services, IOT,
and verification testing |
| • |
Server
Simulators and public
ActiveCare servers are
available to the OEM to
verify basic OMA-DM compliance
as well as access to ActiveCare
server to verify operator
compliance |
| • |
Support
continues until delivery
of the handset to the
operator's lab for technical
acceptance testing |
|
 |
 |
|
 |
 |
 |
 |
 |
 |
 |
 |
|
 |
 |
|
| • |
InnoPath, working with
both the operator and the
OEM, guarantees that each
and every OMA-DM capable
device entering the network
works end-to-end against
our server |
| • |
This
port-to-production program
tier removes all risk
from the operator's MDM
deployment with regards
to time-to-market and
costs and applies to devices
with both InnoPath and
third party OMA-DM clients
up until the time they
enter the operator's labs |
| • |
Includes
full porting services,
verification and IOT testing
against ActiveCare operator-specific
server configurations |
|
 |
 |
|
 |
 |
 |
 |
The diagram below outlines the tiers
of testing, the test environment,
and differences between InnoPath and
3rd party clients.
- The first stage is OMA-DM standards
compliance, applicable to non-InnoPath
clients. This testing will take
place against InnoPath’s Server
Simulator. InnoPath clients bypass
this stage since they are tested
end-to-end against the server as
part of development.
- The next stage is end-to-end network
compliance, also applicable to non-InnoPath
clients. This testing relies on
publically available InnoPath ActiveCare
Servers. InnoPath clients bypass
this stage since they are tested
end-to-end against the server as
part of development.
- The final testing step is operator-specific
compliance, applicable to both InnoPath
and non-InnoPath clients. This testing
takes place against an InnoPath
ActiveCare Server with an operator
specific configuration. Upon passing
this step, the client, both InnoPath
and 3 rd party, is ready for final
operator acceptance leading to device
launch. However, InnoPath’s
support does not end here. We actively
work with both the handset vendor
and the operator to ensure successful
device launch and integration into
ActiveCare. This includes access
to the DCMP, described below.

InnoPath’s testing program
is paired with powerful tools that
facilitate successful MDM deployment.
Server Simulator: Based on
InnoPath’s ActiveCare server
technology, the simulator permits
the operator or device manufacturer
to quickly verify OMA-DM compliance
via both positive and negative test
cases. It incorporates a rich scripting
language adding to its flexibility.
The simulator may be deployed as part
of any of the tiers described above.
DCMP: InnoPath’s Device
Capability Management Program is a
comprehensive offering that includes
in-house testing of new handsets as
well as a Device Capabilities Repository
integrated with the ActiveCare Server
platform. The
InnoPath DCMP is unique, focusing
on both OMA-CP and OMA-DM devices,
critical in matching device capabilities
to the MDM platform. Database
updates are pushed out to wireless
operators on a periodic basis. The DCMP may be deployed by wireless operators,
but may also be used in support of end-to-end testing to ensure that the proper
set of OMA-DM functions are actually verified.
Test Plans and Compliance Matrices: With
real-world experience, InnoPath’s
operations team has developed a comprehensive
set of test plans that detail every
aspect of OMA-DM compliance. The company
also maintains a set of matrices outlining
compliance with operator-specific
device specifications. These are critical
in minimizing time-to-market for new
OMA-DM capable devices. The company
updates these matrices in line with
published updates by the operators.
|