Mobile device management: Difference between revisions
Line 29: | Line 29: | ||
[[de:Mobile Device Management]] |
[[de:Mobile Device Management]] |
||
###[http://www.devicemanagement.org/content/view/20754/152/ Good overview of mobile device management] |
Revision as of 03:14, 4 February 2008
Mobile device management (MDM) refers to tools intended to distribute applications, data and configuration settings to mobile devices such as mobile phones. The intent of MDM is to optimize the functionality and security of a mobile communications network, while minimizing cost and downtime. [1]
Typically solutions include a server component, which sends out the management commands to the mobile devices, and a client command, which runs on the handset and receives and implements the management commands. In some cases, a single vendor may provide both the client and the server, in others client and server will come from different sources.
The management of mobile devices has evolved over time. At first it was necessary to either connect to the handset or install a SIM in order to make changes and updates. Scalability was obviously a problem.
One of the next steps was to allow a client initiated update, similar to when a user requests a Windows Update.
Central remote management, using commands sent over the air, is the next step. An administrator at the mobile operator, an enterprise IT data center or a handset OEM can use an administrative console to update or configure any one handset, group or groups of handsets. This obviously provides scalability benefits particularly useful when the fleet of managed devices is large in size.
Central functionality includes:[2]
- FOTA - Firmware over the air updates
- Diagnostics
- Remote Configuration and Provisioning
- Security
- Backup/Restore