SYSTEMS AND METHODS FOR MANAGING LOST DEVICES OF MULTIPLE TYPES WITH MULTIPLE POLICIES USING MELDED PROFILES ASSOCIATED WITH GROUPS

• US 20170085593A1
• Filed: 05/09/2016
• Published: 03/23/2017
• Est. Priority Date: 08/01/2013
• Status: Active Grant

• Current Assignee: ConnectWise, LLC
• Original Assignee: ConnectWise, LLC
• Inventors: Buerk, Gregory Francis, Logan, Scott
• Granted Patent: US 9,800,617 B2
• Time in Patent Office: Days
• CPC Class Codes: G06F 21/60 Protecting data
• CPC Class Codes: G06F 21/6245 Protecting personal data, e.g. for financial or medical purposes
• CPC Class Codes: G06F 21/88 Detecting or preventing theft or loss
• CPC Class Codes: G06F 2221/2143 Clearing memory, e.g. to prevent the data from being stolen
• CPC Class Codes: G06F 2221/2149 Restricted operating environment
• CPC Class Codes: H04L 63/20 for managing network security; network security policies in general filtering policies H04L63/0227
• CPC Class Codes: H04W 12/126 Anti-theft arrangements, e.g. protection against subscriber identity module [SIM] cloning

Abstract

This disclosure facilitates managing lost devices. In some embodiments, a system receives a first device type from a first agent on a first device, and a different second device type from a second agent on a second device. The system receives a first group associated with the first device and a different second group associated with the second device. The system determines that the first device and the second device are lost and accesses a database storing first and second configuration classes associated with the first and second devices, respectively. The system creates first and second device-dependent classes based on the first and second device types and the first and second configuration classes, respectively. The system melds the first device-dependent class into a first melded profile and the second device-dependent class into a second melded profile, using the respective groups, and applies the melded profiles to the corresponding device.

Claims

1. A method for managing lost devices via a computer network, comprising:

receiving, by a server from a first agent executing on a first device, a first device type;

receiving, by the server from a second agent executing on a second device, a second device type, the second device type different from the first device type;

receiving, by the server from a user interface, a first group associated with the first device and a second group associated with the second device, the second group different from the first group;

determining, by the server, that the first device is lost;

determining, by the server, that the second device is lost;

accessing, by the server responsive to determining that at least one of the first device and second device is lost, a database storing, in memory, a first configuration class associated with the first device and a second configuration class associated with the second device;

creating, by the server, based on the first device type and the first configuration class, a first device-dependent class;

creating, by the server, based on the second device type and the second configuration class, a second device-dependent class;

melding, by the server based on the first group, the first device-dependent class into a first melded profile;

melding, by the server based on the second group, the second device-dependent class into a second melded profile; and

applying, by the server, the first melded profile to the first device that is lost and the second melded profile to the second device that is lost.

2. The method of claim 1, further comprising:

receiving, by the server from a second user interface, an indication that the first device is lost.

3. The method of claim 1, wherein the first configuration class comprises:

a first setting operable to control a first aspect of a third device; and

a second setting operable to control a second aspect of a fourth device;

wherein the first aspect and the second aspect are associated with a management function.

4. The method of claim 3, wherein the first device-dependent class comprises:

a first device setting determined based on the first setting and the first device type, the third device type same as the first device type; and

a second device setting determined based on the first setting and the first device type, the fourth device type same as the first device type and the first aspect different from the second aspect.

5. The method of claim 4, wherein the first melded profile comprises:

the first device-dependent class, the first-device dependent class associated with the first group; and

a third device-dependent class associated with the first group and the first aspect;

wherein;

the first device is associated with the first group; and

the first device setting of the first device-dependent class is combined with the first device setting of the third device-dependent class by selecting at least one of;

a priority of the first device setting;

a list of the first device setting; and

a computation based on the first device setting.

6. The method of claim 1, further comprising:

accessing, by the server from the database, a translation mapping a plurality of input strings into a plurality of output strings;

selecting, by the server from the first melded profile, a variable string;

mapping, by the server, based on the translation, the variable string to a variable value; and

replacing, by the server in the first melded profile, the variable string with the variable value.

7. The method of claim 1, further comprising:

receiving, by the server from the first agent, a configuration of the first device;

selecting, by the server responsive to the receiving of the configuration, based on the configuration, a third group; and

associating, by the server responsive to the selection, the first device with the third group.

8. The method of claim 1, further comprising:

receiving, by the server from the first agent, a configuration of the first device;

creating, by the server responsive to the receiving of the configuration, based on the first device type, the first configuration class, and the configuration, a third device-dependent class;

melding, by the server, responsive to the creating, based on the first group, the third device-dependent class into a third melded profile; and

applying, by the server, responsive to the third melded profile being different from the first melded profile, the third melded profile to the first device.

9. The method of claim 1, further comprising:

sending, by the server to the first agent, responsive to the indication that the first device is lost, an instruction indicating that the first device is lost.

10. The method of claim 9, further comprising:

receiving, by the first agent, the indication that the first device is lost; and

modifying, by the first agent responsive to the receiving, a frequency of contacting the server to be more frequent.

11. The method of claim of claim 9, further comprising:

receiving, by the first agent, the indication that the first device is lost;

determining, by the first agent responsive to the receiving, an indication of an activity on the first device, the indication based on a detection of one condition selected from;

an unlocking of the first device;

a movement of the first device; and

a starting of an application on the first device;

acquiring, by the first agent responsive to the indication of the activity, an image from a camera on the first device; and

transmitting, by the first agent to the server responsive to the acquiring, the image.

12. The method of claim 1, further comprising

receiving, by the server from the first agent, a record of cellular data usage on the first device;

accessing, by the server responsive to receiving the record of cellular data usage, a third configuration class associated with the first device, the third configuration class including one configuration selected from;

an enabling of data roaming;

a setting of maximum utilized bandwidth; and

an enabling of cellular data based on time of day;

creating, by the server, based on the first device type and the third configuration class, a third device-dependent class;

melding, by the server based on the first group, the third device-dependent class into a third melded profile; and

applying, by the server, responsive to the melding, the third melded profile to the first device.

13. The method of claim 1, further comprising:

accessing, by the server, the first configuration class including a first plurality of device-independent settings;

using, by the server, the first configuration class including the plurality of first device-independent settings to create a plurality of first device-dependent classes for the first device; and

melding, by the server based on the first group, the first plurality of device-dependent classes into the first melded profile.

14. The method of claim 1, further comprising:

using, by the server, a priority of each of the first plurality of device-dependent classes to generate the first melded profile.

15. The method of claim 1, further comprising:

accessing, by the server, the first configuration class including a first device-independent setting for at least one of an application on the first device and an operating system of the first device; and

using, by the server, the first configuration class including the first device-independent setting to create a first device-dependent class for the first device.

16. A system for managing lost devices via a computer network, comprising:

a server including a processor and memory configured to;

receive, from a first agent executing on a first device, a first device type;

receive, from a second agent executing on a second device, a second device type, the second device type different from the first device type;

receive, from a user interface, a first group associated with the first device and a second group associated with the second device, the second group different from the first group;

determine that the first device is lost;

determine that the second device is lost;

access, responsive to determining that at least one of the first device and second device is lost, a database storing a first configuration class associated with the first device and a second configuration class associated with the second device;

create, based on the first device type and the first configuration class, a first device-dependent class;

create, based on the second device type and the second configuration class, a second device-dependent class;

meld, based on the first group, the first device-dependent class into a first melded profile;

meld, based on the second group, the second device-dependent class into a second melded profile; and

apply the first melded profile to the first device that is lost and the second melded profile to the second device that is lost.

17. The system of claim 16, the server further configured to:

receive, from a second user interface, an indication that the first device is lost.

18. The system of claim 16, wherein the first configuration class comprises:

a first setting operable to control a first aspect of a third device; and

a second setting operable to control a second aspect of a fourth device;

wherein the first aspect and the second aspect are associated with a management function.

19. The system of claim 18, wherein the first device-dependent class comprises:

a first device setting determined based on the first setting and the first device type, the third device type same as the first device type; and

a second device setting determined based on the first setting and the first device type, the fourth device type same as the first device type and the first aspect different from the second aspect.

20. The system of claim 19, wherein the first melded profile comprises:

the first device-dependent class, the first-device dependent class associated with the first group; and

a third device-dependent class associated with the first group and the first aspect;

wherein;

the first device is associated with the first group; and

the first device setting of the first device-dependent class is combined with the first device setting of the third device-dependent class by selecting at least one of;

a priority of the first device setting;

a list of the first device setting; and

a computation based on the first device setting.

21-30. -30. (canceled)