Mobile device management broker

US11487889B2 · US · B2

Patent metadata
FieldValue
Publication numberUS-11487889-B2
Application numberUS-201816229623-A
CountryUS
Kind codeB2
Filing dateDec 21, 2018
Priority dateMar 31, 2014
Publication dateNov 1, 2022
Grant dateNov 1, 2022

How to read this patent

A practical reading order for non-experts. Skip the full description unless you need deep technical detail.

  1. Title

    What the patent document calls the invention.

  2. Abstract

    A short plain-language summary of the technical disclosure.

  3. Assignees and inventors

    Who owns or filed the patent and who is credited as inventor.

  4. Key dates

    Filing, priority, publication, and grant dates set the timeline.

  5. First independent claim

    The legal scope of protection — read this for what is actually claimed.

  6. CPC / IPC classifications

    Technology tags used to group this patent with similar filings.

  7. Citations and related patents

    Prior art links and similar publications in this corpus.

Abstract

Official abstract text for this publication.

Techniques to manage mobile devices are disclosed. In various embodiments, a request to perform a management action with respect to a mobile device is received from a mobile device management (MDM) authority. A scope of authority of the MDM authority with respect to the mobile device is determined. The management action is caused to be performed with respect to the mobile device based at least in part on the determined scope of authority of the MDM authority with respect to the mobile device.

First claim

Opening claim text (preview).

What is claimed is: 1. A method of managing a mobile device, comprising: receiving from a mobile device management (MDM) authority a request to perform a management action with respect to the mobile device; determining a scope of authority of the MDM authority with respect to the mobile device, wherein determining the scope of authority comprises performing a look up in a table or other data structure in which data reflecting grants of authority to one or more MDM authorities are stored, wherein performing the look up in the table or other data structure includes identifying a scope of authority that has been granted to the MDM authority; in response to determining that a scope of authority needed to perform the requested management action does not match the scope of authority that has been granted to the MDM authority that is specified in the table or other data structure for the MDM authority, determining a different management action that is specified in the table or other data structure for the MDM authority, wherein the determined different management action is specified for the MDM authority in the table or other data structure; modifying a scope of the requested management action to match the scope of authority that has been granted to the MDM authority by translating the requested management action to be the different management action that is specified in the table or other data structure for the MDM authority; and causing the different management action that is within the scope of authority that has been granted to the MDM to be performed with respect to the mobile device. 2. The method of claim 1 , wherein a request is received at a management broker configured to facilitate management of the mobile device by the one or more MDM authorities, each within a corresponding scope of authority that has been granted to that MDM authority. 3. The method of claim 2 , wherein the management broker comprises an app or other software entity installed on the mobile device. 4. The method of claim 2 , wherein the management broker is configured to manage the mobile device on behalf of the one or more MDM authorities at least in part via interactions with an MDM agent installed on the mobile device. 5. The method of claim 4 , wherein the MDM agent comprises a native MDM agent associated with an operating system of the mobile device. 6. The method of claim 2 , wherein the management broker comprises a cloud-based management proxy or other server. 7. The method of claim 1 , wherein the scope of authority of a second MDM authority is defined by an owner or other user of the mobile device. 8. The method of claim 7 , wherein the MDM authority comprises a personal domain of authority reserved to the owner or other user of the mobile device and the scope of authority of the second MDM authority represents a scope of authority reserved by the owner or other user to him/herself personally. 9. The method of claim 1 , wherein causing the different management action to be performed with respect to the mobile device based at least in part on the determined scope of authority of the MDM authority with respect to the mobile device includes causing the different management action to be performed to an extent indicated by the scope of authority that has been granted to the MDM authority. 10. The method of claim 1 , wherein causing the different management action to be performed with respect to the mobile device based at least in part on the determined scope of authority of the MDM authority with respect to the mobile device includes causing the different management action to be performed with respect to a subset of data on the mobile device as indicated by the scope of authority that has been granted to the MDM authority. 11. The method of claim 1 , wherein the mobile device is associated with a plurality of MDM authorities, wherein each of the plurality of MDM authorities has a corresponding scope of authority. 12. The method of claim 1 , wherein causing the different management action to be performed with respect to the mobile device based at least in part on the scope of authority that has been granted to the MDM authority with respect to the mobile device includes filtering a result data provided by the mobile device in response to the request to filter out data that is not within the scope of authority of the MDM authority. 13. A system, comprising: a storage device; and a processor coupled to the storage device and configured to: receive from a mobile device management (MDM) authority a request to perform a management action with respect to a mobile device; determine a scope of authority of the MDM authority with respect to the mobile device, wherein determining the scope of authority comprises performing a look up in a table or other data structure in which data reflecting grants of authority to one or more MDM authorities are stored, wherein performing the look up in the table or other data structure includes identifying a scope of authority that has been granted to the MDM authority; in response to a determination that a scope of authority needed to perform the requested management action does not match the scope of authority that has been granted to the MDM authority that is specified in the table or other data structure for the MDM authority determine a different management action that is specified in the table or other data structure for the MDM authority, wherein the determined different management action is specified for the MDM authority in the table or other data structure; modify a scope of the requested management action to match the determined scope of authority by translating the requested management action to be the different management action that is specified in the table or other data structure for the MDM authority; and cause the different management action that is within the scope of authority that has been granted to the MDM to be performed with respect to the mobile device. 14. The system of claim 13 , wherein the request is received at a management broker configured to facilitate management of the mobile device by one or more MDM authorities, each within a corresponding scope of authority that has been granted to that MDM authority. 15. The system of claim 14 , wherein the management broker comprises an app or other software entity installed on the mobile device. 16. The system of claim 14 , wherein the management broker is configured to manage the mobile device on behalf of the one or more MDM authorities at least in part via interactions with an MDM agent installed on the mobile device. 17. The system of claim 14 , wherein the scope of authority of a second MDM authority is defined by an owner or other user of the mobile device. 18. The system of claim 14 , wherein causing the different management action to be performed with respect to the mobile device based at least in part on the determined scope of authority of the MDM authority with respect to the mobile device includes causing the different management action to be performed with respect to a subset of data on the mobile device as indicated by the scope of authority that has been granted to the MDM authority. 19. A computer program product to manage a mobile device, the computer program product being embodied in a non-transitory computer readable storage medium and comprising computer instructions for: receiving from a mobile device management (MDM) authority a request to perform a management action with respect to the mobile device; determining a scope of authority of a m

Assignees

Inventors

Classifications

  • Service provisioning or reconfiguring · CPC title

  • by remotely controlling device operation · CPC title

  • Detecting or preventing theft or loss · CPC title

  • Access security · CPC title

  • Clearing memory, e.g. to prevent the data from being stolen · CPC title

Patent family

Related publications grouped by family.

External sources

Frequently asked questions

Answers are generated from the same data shown on this page.

What does patent US11487889B2 cover?
Techniques to manage mobile devices are disclosed. In various embodiments, a request to perform a management action with respect to a mobile device is received from a mobile device management (MDM) authority. A scope of authority of the MDM authority with respect to the mobile device is determined. The management action is caused to be performed with respect to the mobile device based at least …
Who is the assignee on this patent?
Mobile Iron Inc
What technology area does this patent fall under?
Primary CPC classification G06F21/604. Mapped technology areas include Physics.
When was this patent published?
Publication date Tue Nov 01 2022 00:00:00 GMT+0000 (Coordinated Universal Time) (B2). Legal status and post-grant events are not shown on this page.
What related patents are in patentsdb?
We list 3 related publications on this page (citations in our corpus or others sharing the same primary CPC).