System and method for restricting system and application software available for installation on a managed mobile device

• US 10,379,829 B2
• Filed: 02/26/2015
• Issued: 08/13/2019
• Est. Priority Date: 02/26/2015
• Status: Active Grant

• Current Assignee: Malikie Innovations Limited (Key Patent Innovations Limited)
• Original Assignee: Blackberry Limited
• Inventors: Smith, Andrew Christopher, Parry, Thomas Owen, Dikic, Srdan, Quin, Spencer Leavitt George, MacDonald, Christopher Donald, Loosemore, Michael William, Carter, Jason Lee
• Primary Examiner(s): Puente, Emerson C
• Assistant Examiner(s): Chen, Sen Thong
• Application Number:
  US14/632,939
• Publication Number:
  US 20160253159A1
• Time in Patent Office: 1,629 Days
• Field of Search: 717172
• CPC Class Codes: G06F 8/61 Installation
• CPC Class Codes: G06F 8/65 Updates security arrangements therefor G06F21/57
• CPC Class Codes: H04W 88/02 Terminal devices

Abstract

A method for managing software on a device is provided. The method comprises: receiving, from a third party associated with the device, by a software administrator of an organization different from the third party, release information regarding software versions for the device; creating, by the software administrator, a profile that specifies whether or not at least one of the software versions is allowed on the device; and transmitting the profile, by the software administrator to a server computer associated with the third or other parties, to promote enforcement of the profile for the device.

Claims

1. A method for managing software on a device and implemented by an external administrator, the method comprising:

receiving, from a server at a customer site and associated with the device, release information regarding software versions for the device and originating from a software loading service of a software management entity;

creating, using the release information and using user and device data describing characteristics of the device and a user of the device, a profile that specifies whether or not at least one of the software versions is allowed on the device, wherein the user and device data are based on at least one of a model of the device or a service provider associated with the device, and wherein the profile further specifies that a particular one of the software versions is to be installed on the device based on an amount of memory currently available on the device; and

transmitting profile information to the server to promote enforcement of the profile information for the device, wherein the profile information comprises the profile,

wherein the external administrator is external to a network of the customer site and external to the software management entity.

2. The method of claim 1, wherein the enforcement comprises the server, in response to receiving the profile information, transmitting a payload towards the software loading service to cause the software loading service to enforce the profile on the device, wherein the payload is based on the profile information.

3. The method of claim 1, wherein the enforcement comprises at least one of:

allowing installation of at least one software version on the device;

preventing installation of at least one software version on the device;

providing an alert on the device that at least one software version is available for installation on the device; and

providing an alert on the device that at least one software version is not available for installation on the device.

4. The method of claim 1, further comprising transmitting to the server a request for the release information, wherein the receiving the release information is in response to the request.

5. The method of claim 1, further comprising further creating the profile via an interface that allows selection of at least one software version and selection of at least one action to be performed on the software version, wherein the action is one of installing the software version on the device or following a rule that prohibits installing the software version on the device, and wherein the interface further allows specification of a condition under which the action is to be taken, the condition being related to at least one of:

a location of the device;

a location in which the action is to be taken;

a time when the action is to be taken;

a roaming status of the device;

the software version, wherein a most recent available software version is to be mandatorily installed on the device;

a hardware characteristic of the device;

a software characteristic of the device;

a radio access technology in use by the device; and

a radio access network in use by the device.

7. The method of claim 1, wherein the profile further specifies that a particular one of the software versions is to be installed on the device only at a particular time.

19. The method of claim 1, wherein the profile further specifies that a particular one of the software versions is to be installed on the device based on a roaming status of the device.

6. A server at a customer site, the server comprising:

a memory; and

a processor coupled to the memory and configured to;

receive, from a software loading service of a software management entity, release information regarding software versions for a device;

cause the memory to store the release information;

transmit the release information to an external administrator;

receive, from the external administrator, profile information to promote enforcement of the profile information for the device, wherein the profile information comprises a profile created using the release information and using user and device data describing characteristics of the device and a user of the device, wherein the user and device data are based on at least one of a model of the device or a service provider associated with the device, wherein the profile specifies whether at least one of the software versions is allowed on the device or is prohibited on the device;

transmit a payload towards the software loading service to cause the software loading service to make a specified software version available for installation on the device or to cause the software loading service to prevent installation of the specified software version on the device, wherein the payload is based on the profile information; and

when the server receives more than one profile for the device, perform a reconciliation procedure to determine which of the profiles is to be enforced on the device, wherein the server performs the reconciliation procedure based on a ranking that specifies which of the profiles are to take precedence over others,

wherein the external administrator is external to a network of the customer site and external to the software management entity.

14. The server of claim 6, wherein the software versions are based on at least one of:

a hardware characteristic of the device;

a software characteristic of the device;

a radio access technology in use by the device; and

a radio access network in use by the device.

15. The server of claim 6, wherein the processor is further configured to further transmit the release information in response to receiving a request for the release information from the external administrator.

16. The server of claim 14, wherein the software loading service is external to the device.

17. The server of claim 6, wherein the processor is further configured to further transmit the payload to the device to cause the device to forward to the software loading service a device policy based on the payload.

18. The server of claim 6, wherein, when a first software installed on the device does not correspond to a second software specified in the profile, the processor is further configured to perform:

sending the external administrator a first message informing the external administrator that the first software does not correspond to the second software;

sending the device a second message informing the device that the first software does not correspond to the second software; and

taking an action to impair functioning of the device.

8. A method for managing software on a device and implemented by a server at a customer site, the method comprising:

receiving, from a software loading service of a software management entity, release information regarding software versions for the device;

transmitting the release information to an external administrator;

receiving, from the external administrator, profile information to promote enforcement of the profile information for the device, wherein the profile information comprises a profile created using the release information and using user and device data describing characteristics of the device and a user of the device, wherein the user and device data are based on at least one of a model of the device or a service provider associated with the device, wherein the profile specifies whether at least one of the software versions is allowed on the device or is prohibited on the device;

transmitting a payload towards the software loading service to cause the software loading service to make a specified software version available for installation on the device or to cause the software loading service to prevent installation of the specified software version on the device, wherein the payload is based on the profile information; and

when the server receives more than one profile for the device, performing a reconciliation procedure to determine which of the profiles is to be enforced on the device, wherein the server performs the reconciliation procedure based on a ranking that specifies which of the profiles are to take precedence over others,

wherein the external administrator is external to a network of the customer site and external to the software management entity.

9. The method of claim 8, further comprising further transmitting the release information in response to receiving a request for the release information from the external administrator.

10. The method of claim 8, further comprising storing the release information in a data storage component accessible to the server, wherein the software loading service is external to the device.

11. The method of claim 8, further comprising further transmitting the payload to the device to cause the device to forward to the software loading service a device policy based on the payload.

12. The method of claim 8, wherein, when a first software installed on the device does not correspond to a second software specified in the profile, the method further comprises:

sending the external administrator a first message informing the external administrator that the first software does not correspond to the second software;

sending the device a second message informing the device that the first software does not correspond to the second software; and

taking an action to impair functioning of the device.

13. The method of claim 8, wherein the software versions are based on at least one of:

a hardware characteristic of the device;

a software characteristic of the device;

a radio access technology in use by the device; and

a radio access network in use by the device.