IP Library Granted Patent US 11,487,889
Granted Patent B2
US 11,487,889 · App. 16/229,623 · Granted Nov 1, 2022

Mobile device management broker

Inventors: Suresh Kumar Batchu (Milpitas, CA); Mansu Kim (San Jose, CA)
Assignee: MOBILE IRON, INC.
G06F21/604G06F21/305G06F21/6218G06F21/88H04W4/50H04W12/08H04W12/37G06F2221/2143G06F2221/2149
View Patent ↗
Loading inventors, assignments & file history…
Monitor This Case
Get email alerts when status or documents change.
Order Certified Copies
Most orders are placed with the USPTO same day — all within 24 business hours.
Order via The Patent Place →
Pre-filled with this patent's details
Quick Facts
Patent No.
US 11,487,889
App. No.
16/229,623
Granted
Nov 1, 2022
Kind
B2
Abstract

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.

Claims (36)

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 management 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.

Assignments (7)
CORRECTIVE ASSIGNMENT TO CORRECT THE PROPERTY 14633493 WHICH WAS ENTERED INCORRECTLY AS 14633793 PREVIOUSLY RECORDED ON REEL 71176 FRAME 315. ASSIGNOR(S) HEREBY CONFIRMS THE FIRST LIEN NEWCO SECURITY AGREEMENT. Recorded Nov 10, 2025
From: PULSE SECURE, LLC; IVANTI, INC.; IVANTI US LLC; IVANTI SECURITY HOLDINGS LLC
To: MORGAN STANLEY SENIOR FUNDING, INC., AS COLLATERAL AGENT
Reel/Frame 073818/0515 →
FIRST LIEN NEWCO SECURITY AGREEMENT Recorded May 5, 2025
From: PULSE SECURE, LLC; IVANTI, INC.; IVANTI US LLC; IVANTI SECURITY HOLDINGS LLC
To: MORGAN STANLEY SENIOR FUNDING, INC., AS COLLATERAL AGENT
Reel/Frame 071176/0315 →
SECURITY INTEREST Recorded May 2, 2025
From: IVANTI, INC.
To: ALTER DOMUS (US) LLC
Reel/Frame 071164/0482 →
NOTICE OF SUCCESSION OF AGENCY FOR SECURITY INTEREST AT REEL/FRAME 054665/0873 Recorded Apr 29, 2025
From: BANK OF AMERICA, N.A., AS RESIGNING AGENT
To: ALTER DOMUS (US) LLC, AS SUCCESSOR AGENT
Reel/Frame 071123/0386 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Aug 25, 2022
From: MOBILEIRON, INC.
To: IVANTI, INC.
Reel/Frame 061327/0751 →
SECURITY INTEREST Recorded Dec 9, 2020
From: CELLSEC, INC.; PULSE SECURE, LLC; INVANTI, INC.; MOBILEIRON, INC.; INVANTI US LLC
To: BANK OF AMERICA, N.A., AS COLLATERAL AGENT
Reel/Frame 054665/0873 →
SECURITY INTEREST Recorded Dec 9, 2020
From: CELLSEC, INC.; PULSE SECURE, LLC; IVANTI, INC.; MOBILEIRON, INC.; IVANTI US LLC
To: MORGAN STANLEY SENIOR FUNDING, INC., AS COLLATERAL AGENT
Reel/Frame 054665/0062 →
Continuity (3)
Continuation 14675469 · Mar 31, 2015
Provisional Application 61973083 · Mar 31, 2014
Related Publication 20190188393A1 · Jun 20, 2019