HP mProveHP mProve is a comprehensive client-side software suite that provides reliable over-the-air management of mobile devices. The HP mProve suite is comprised of two software components the mProve Firmware Over-the-Air (FOTA) and Device Management (DM) Agents.

HP mProve Firmware Over the Air (FOTA)HP mProve FOTA is a commercially proven client-side software suite, designed to be embedded in a mobile device to enable over-the-air firmware and software updates supporting proprietary and open operating systems including Symbian, Microsoft Windows Mobile™, Linux, and support is planned for more recently launched operating systems on the roadmap.

HP mProve FOTA Generator. This PC-based software application uses advanced binary comparison and compression algorithms to generate small Update Packages that are optimized for over-the-air delivery.

HP mProve FOTA Agent. This agent resides on the mobile device and contains the algorithms to decrypt, validate, and process the incoming Update Package.

HP mProve Device Management (DM)The HP mProve DM agent handles communication with an OMA standards-based server for device management and supports these industry standards:

OMA DM versions 1.1.2 and 1.2•OMA DL (Download) version 1.0•OMA DM FUMO (Firmware Update Management •Object) version 1.0OMA DM LAWMO (Lock and Wipe Management •Object) candidate specOMA DM SCOMO (Software Component •Management Object) candidate spe

HP mProve has been commercially

deployed by leading manufacturers

worldwide, as well as across multiple

reference platforms.

Industry Challenge

Limited Bandwidth. The wireless data channel has small throughput capacity limiting the size of updates.

Available Memory. There islimitedflashmemoryforUpdate Package storage, thefirmwareupdateprocess, and the software client.

Power Failure. During the software update process if power is lost due to battery failure or other means, the device will be unusable or a “brick”.

Complex Architectures. Today’s device architectures include multiple processors, compressedimages,filesystems, and software usingvarioustypesoffiles. Limited CPU Power. To preserve battery life, processing power of CPUs in mobile devices is much more limited than the power found in PCs and notebooks.

HP mProve Solution

Small Update Packages. Advanced compression algorithms minimize Update Package size to streamline the distribution of updates.

Low Memory Requirements. mProve’s unique optimization techniques enable devices to make the best use of memory for fast updates and efficientstorageofrevenuegenerating applications.

100% Fault Tolerance. mProve’s update process recover from interruptions such as power loss, network failure, or unpredictable user behavior with complete fault tolerance, ensuring a positive update experience.

Platform Agnostic. mProve’s patented algorithms are designedspecificallyforcomplex environments and are optimized to update fileshavingvarioustypes,architecturesorfileformats.

Mach 1x. HP’s Mach 1x update technology minimizes computational requirements and significantlyreducestheoverallfirmwareupdatetime.

Operating System Microsoft Windows XP Service Pack 2 or greaterMicrosoft Windows Server 2003Red Hat Linux AS4

CPU Intel CPU 2.8 GHz or faster processor

Physical Memory At least 2 GB RAM

Disk Space Minimum 40 MB for installationMinimum 2 GB for storage

OS Language English (Also certified on simplified Chinese OS)

© Copyright 2009 Hewlett-Packard Development Company, L.P. The information contained herein is subject to change without notice. The only warranties for HP products and services are set forth in the express warranty statements accompanying such products and services. Nothing herein should be construed as constituting an additional warranty. HP shall not be liable for technical or editorial errors or omissions contained herein.

March 2009

HP mProve Update Agent Architecture HP provides the mProve SDK library to an OEM to perform integration into their device environment. The mProve SDK library comprises the core parts of the mProve Update Agent executable code required to perform a fault tolerant firmware update.

The wrapper code acts as an interface to the underlying device capabilities and drivers – such as reading and writing to flash, or displaying update progress information on the device display. The controlling code is essentially defined by changes that are required in the bootloader and the addition of other status information that enables mProve to perform an update.

HP mProve DM Agent Architecture The integration of the mProve DM client differs from the mProve Update Agent in that it depends to a great extent on the underlying real time operating system of the device.

The mProve DM Manager Module processes SMS messages, parses external events and delivers them to either the download (DL) or device management (DM) modules for processing. The DM Module consists of OMA DM-compliant libraries to support the Discovery and Notification phases required to enable FOTA and other capabilities according to the OMA DM 1.2 specification. The DL Module facilitates the transport/download of the Update Package Descriptor and associated Update Package, and is compliant to the OMA DL 1.0 specification.

Device Agent Integration and Verification ToolsmProve includes a extensive suite of applications to streamline and simplify the integration, verification, and validation process comprised of:

Device Management Tree (DMT) Wizard. • A development tool that automatically creates callback APIs and plug-in modules for the addition of new objects and functionality.OMA DM Simulator. • This PC-based simulator provides a working reference of an OMA DM implementation, enabling debugging of the implementation prior to installation on the handset. In addition, the tool supports IOP testing against third party OMA DM servers.Validation Agent. • A PC-based application that analyzes the Update Package to ensure validity and optimal performance.SMS Generator. • The generator replicates the messages, such as bootstrap and notification, sent from a carrier’s SMSC, eliminating the dependency for SMSC connectivity at the time of integration.

Fig 1. Main Update Agent Components

Fig 2. Device Management Agent Architecture

HP mProve Generator System Requirements

For more informationTo read more about mProve, go to www.hp.com/go/mProve.