System and Method for Handling Restoration Operations on Mobile Devices

• US 20100169979A1
• Filed: 03/11/2010
• Published: 07/01/2010
• Est. Priority Date: 04/30/2004
• Status: Active Grant

• Current Assignee: Malikie Innovations Limited (Key Patent Innovations Limited)
• Original Assignee: Blackberry Limited
• Inventors: Adams, Neil P., Brown, Michael S., Hammell, Jonathan F., Brown, Michael K., Kirkup, Michael G., Little, Herbert A.
• Granted Patent: US 7,986,939 B2
• Time in Patent Office: Days
• US Class Current: 726/26
• CPC Class Codes: G06F 21/57 Certifying or maintaining trusted computer platforms, e.g. secure boots or power-downs, version controls, system software checks, secure updates or assessing vulnerabilities
• CPC Class Codes: G06F 21/88 Detecting or preventing theft or loss
• CPC Class Codes: H04L 67/125 involving control of end-device applications over a network
• CPC Class Codes: H04L 67/34 involving the movement of software or configuration parameters network booting or remote initial program loading [RIPL] G06F9/4416
• CPC Class Codes: H04W 12/082 using revocation of authorisation
• CPC Class Codes: H04W 12/12 Detection or prevention of fraud
• CPC Class Codes: H04W 8/245 from a network towards a terminal

Abstract

Systems and methods for handling restoration operations for a mobile device. A mobile device receives a kill pill command, wherein the command causes some or all data on the mobile device to be wiped. An indicator is stored to indicate that the kill pill command was sent to the mobile device. The indicator is used to determine whether a program should be wiped from the mobile device.

Claims

1. A method for handling removal of applications on a mobile device, comprising:

starting synchronization after detecting a connection originating from a host;

detecting a flag in non-volatile memory that a data wipe has occurred;

determining which applications are to be removed based on the presence of the flag; and

removing any application from the device that is one of the determined applications.

2. The method of claim 1 where the detected connection comprises one of:

a hardwired connection,

a short range wireless connection, and,

an over-the-air wireless connection.

3. The method of claim 1 where the starting synchronization comprises

receiving input at the user interface to start synchronizing.

4. The method of claim 1 where the starting synchronization comprises

starting synchronization by the device upon detecting the connection.

5. The method of claim 1 where the determining which applications are to be removed comprises

referencing data in non-volatile memory which indicates which applications are to be removed.

6. The method of claim 5 where the applications to be removed comprises

all applications not installed by the device'"'"'s manufacturer.

7. The method of claim 5 where the applications to be removed comprises

all applications not authorized by the device'"'"'s manufacturer.

8. The method of claim 5 where the applications to be removed comprises

a list of applications originated from the device'"'"'s manufacturer.

9. The method of claim 1 where the determining which applications are to be removed comprises:

receiving, through the connection, indications of which applications are to be removed.

10. The method of claim 9 where the applications to be removed comprise at least one of:

all applications not installed by the device'"'"'s manufacturer;

all applications not authorized by the device'"'"'s manufacturer; and

a list of applications originated from the device'"'"'s manufacturer.

11. A method for handling removal of applications and data on a mobile device, comprising:

starting synchronization after detecting a connection originating from a host;

detecting a flag in non-volatile memory that a kill pill has previously been received;

determining if any data wipe operations are needed based on the presence of the flag;

determining which applications are to be removed based on the presence of the flag; and

removing any application from the device that is one of the determined applications, and,

conducting a data wipe operation as determined.

12. The method of claim 11 where the detected connection comprises one of:

a hardwired connection,

a short range wireless connection, and,

an over-the-air wireless connection.

13. The method of claim 11 where the starting synchronization comprises

receiving input at the user interface to start synchronizing.

14. The method of claim 11 where the starting synchronization comprises

starting synchronization by the device upon detecting the connection.

15. The method of claim 11 where the determining which applications are to be removed and if a data wipe operation needs to be done comprises

referencing data in non-volatile memory which indicates which applications are to be removed, and, if a data wipe operation should be done.

16. The method of claim 15 where the applications to be removed comprises at least one of:

all applications not installed by the device'"'"'s manufacturer;

all applications not authorized by the device'"'"'s manufacturer; and

,

a list of applications originated from the device'"'"'s manufacturer.

17. The method of claim 15 where the data wipe comprises at least one of:

no further data wipe needed;

data wipe of all volatile memory; and

,

data wipe of one or more specified sections of volatile memory.

18. The method of claim 11 where the determining which applications are to be removed and if a data wipe should be done comprises

receiving, through the connection, indications of which applications are to be removed and data wipe instructions.

19. The method of claim 18 where the applications to be removed comprise at least one of:

all applications not installed by the device'"'"'s manufacturer;

all applications not authorized by the device'"'"'s manufacturer; and

,

a list of applications originated from the device'"'"'s manufacturer.

20. The method of claim 18 where the data wipe instructions comprises at least one of:

no further data wipe needed;

data wipe of all volatile memory; and

,

data wipe of one or more specified sections of volatile memory.