Centrally managed solution for all device management activities

• US 9,332,424 B2
• Filed: 08/07/2006
• Issued: 05/03/2016
• Est. Priority Date: 08/05/2005
• Status: Active Grant

• Current Assignee: Qualcomm, Inc.
• Original Assignee: Qualcomm, Inc.
• Inventors: Rao, Bindu Rama, Logan, Will K.
• Primary Examiner(s): Casca, Fred
• Application Number:
  US11/500,734
• Publication Number:
  US 20070169093A1
• Time in Patent Office: 3,557 Days
• Field of Search: 455/419, 455/418, 455/550.1, 455/420, 455/557, 455/517, 455/410, 455/414.1, 717/173, 717/172, 717/168, 717/178, 717/170, 717/171, 717/174, 717/176, 709/224, 709/220, 709/203, 709/221, 709/223, 709/204
• US Class Current: 1/1
• CPC Class Codes: G06F 8/60 Software deployment
• CPC Class Codes: G06F 8/654 using techniques specially adapted for alterable solid state memories, e.g. for EEPROM or flash memories
• CPC Class Codes: G06F 9/44505 Configuring for program initiating, e.g. using registry, configuration files
• CPC Class Codes: H04W 12/08 Access security
• CPC Class Codes: H04W 12/35 Protecting application or service provisioning, e.g. securing SIM application provisioning
• CPC Class Codes: H04W 12/71 Hardware identity
• CPC Class Codes: H04W 36/04 Reselecting a cell layer in multi-layered cells
• CPC Class Codes: H04W 8/245 from a network towards a terminal
• CPC Class Codes: H04W 88/18 Service support devices; Network management devices

Abstract

A centrally managed solution for all device management activities. This includes a set of device and subscriber registries, which are being constantly updated as new terminals, and subscribers are added to the system. It also includes support for legacy CDMA specific device management standards such as OTASP and OTAPA and support for remote handset configuration via SMS, using the latest standards from the Open Mobile Alliance Client Provisioning. In one embodiment, it includes support for remote handset configuration over IP, using the latest Open Mobile Alliance Client Provisioning and IOTA device management standards.

Claims

1. A method of conducting device management of a mobile device, the method comprising:

receiving a request for an update from the mobile device at a mobile device management platform, the mobile device management platform being a centralized platform separate from the mobile device, the mobile device management platform comprising a customer profile database;

determining the availability of an update package, for installation on the mobile device, by

looking up device capability by the mobile device management platform based on an Electronic Serial Number (ESN) or mobile equipment identifier (MEID); and

preparing for a Firmware Over-the-Air (FOTA) session by registering a pending FOTA session with one of an IP (Internet Protocol) based Over-The-Air (IOTA) component or an Open Mobile Alliance Device Management (OMA-DM) component based on the device capability;

sending the update package to the mobile device;

facilitating installation of the update package in response to user permission to install the update package; and

automatically purging old data corresponding to at least one old device from the customer profile database after a configurable period, the customer profile database serving as a central repository for customer settings.

2. The method of conducting device management from claim 1 wherein receiving the request comprises:

receiving, from the mobile device, using a client-initiated Firmware Over-the Air (FOTA) URL, device specific information comprising an Electronic Serial Number (ESN) or a mobile equipment identifier (MEID) of the mobile device.

3. The method of conducting device management from claim 1 wherein determining the availability of the update package further comprises:

responding back to the mobile device with a Hypertext Transfer Protocol (HTTP) redirect referring to the pending FOTA session on either the IOTA component or the OMA-DM component depending on the device capability;

querying, by the mobile device management platform, for a make, model and version of the mobile device;

receiving, from by the mobile device, its make, model and version; and

identifying, by the mobile device management platform, an appropriate firmware update package, based on the make, model and version.

4. The method of conducting device management from claim 1 wherein sending the update package to the mobile device comprises:

instructing, by the mobile device management platform, the mobile device to employ a specific Universal Resource Locator (URL) for an appropriate firmware update package.

5. The method of conducting device management from claim 1 further comprising:

causing, the mobile device, to prompt a user to install the update package that has been sent to the mobile device, using an update prompt;

causing, the mobile device to display update package information and release notes sent with the update package;

causing the mobile device to show a legal disclaimer stating that the mobile device may be unavailable during an update and that the user will be unable to make 911 calls; and

causing the mobile device to accept a user response to the update prompt.

6. The method of conducting device management from claim 1 wherein the old data is purged to an off-line data store.

12. The method of claim 1, wherein the at least one old device is a deactivated device.

7. A mobile device management platform in a network for managing a mobile device, the mobile device management platform communicatively coupled to the mobile device and comprising:

a centralized device management server; and

a customer profile database,

wherein the centralized device management server is configured to receive a request for an update from the mobile device, determine the availability of an update package for installation on the mobile device, send the update package to the mobile device, facilitate installation of the update package in response to user permission to install the update package, and automatically purge old data corresponding to at least one old device from the customer profile database after a configurable period;

wherein the customer profile database serves as a central repository for customer settings;

wherein the centralized device management server is configured to determine the availability of the update package by looking up device capability based on an Electronic Serial Number (ESN) or mobile equipment identifier (MEID); and

wherein the centralized device management server is further configured to determine the availability of the update package by preparing for a Firmware Over-the-Air (FOTA) session by registering pending FOTA session with one of an IP (Internet Protocol) based Over-The-Air (IOTA) component or an Open Mobile Alliance Device Management (OMA-DM) component based on the device capability.

8. The mobile device management platform of claim 7 wherein the centralized device management server is configured to receive the request

by receiving, from by the mobile device, using a client-initiated Firmware Over-the Air (FOTA) URL, device specific information comprising an Electronic Serial Number (ESN) or a mobile equipment identifier (MEID) of the mobile device.

9. The mobile device management platform of claim 7 wherein the centralized device management server is further configured to determine the availability of the update package by:

responding back to the mobile device with a Hypertext Transfer Protocol (HTTP) redirect referring to the pending FOTA session on either the IOTA component or the OMA-DM component depending on the device capability;

querying for a make, model and version of the mobile device;

receiving, from the mobile device, its make, model and version; and

identifying an appropriate firmware update package, based on the make, model and version.

10. The mobile device management platform of claim 7 wherein the centralized device management server is further configured to send the update package to the mobile device by instructing the mobile device to employ a specific Universal Resource Locator (URL) for an appropriate firmware update package.

11. The mobile device management platform of claim 7 wherein the old data is purged to an off-line data store.