IP Library Granted Patent US 9,537,835
Granted Patent B2
US 9,537,835 · App. 14/690,311 · Granted Jan 3, 2017

Secure mobile app connection bus

Inventors: Mansu Kim (Cupertino, CA); Joshua Sirota (Los Altos, CA); Suresh Kumar Batchu (Milpitas, CA)
Assignee: MOBILE IRON, INC.
H04L63/0428G06F9/54G06F21/6281H04L9/08H04W12/04
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 9,537,835
App. No.
14/690,311
Granted
Jan 3, 2017
Kind
B2
Abstract

A secure mobile application connection bus is disclosed. First encryption information and an identifier associated with a data storage location on a mobile device are provided from a first application to a second application. Second encryption information associated with the second mobile application is retrieved from the data storage location. The second mobile application is configured to provide data to the data storage location. Data is transferred securely between the first mobile application and the second mobile application via the data storage location.

Claims (31)

1. A method of secure communication between mobile applications, comprising:

providing, from a first mobile application on a mobile device to a second mobile application on the mobile device, a first encryption information and an identifier associated with a data storage location on the mobile device, wherein a library associated with the second mobile application validates an identifier associated with the first mobile application and wherein the data storage location comprises a shared keychain location;

retrieving, from the data storage location, a second encryption information associated with the second mobile application, wherein the second mobile application is configured to provide the second encryption information to the data storage location at least in part in response to receiving the first encryption information, the identifier associated with the data storage location, and the first mobile application being validated, and wherein the second mobile application is configured to generate and include in the second encryption information an application identifier associated with the second mobile application;

validating an identity of the second mobile application based at least in part on the application identifier included in the second encryption information; and transferring data securely between the first mobile application and the second mobile application via the data storage location, including by encrypting the data using a second encryption key included in the second encryption information.

2. The method of claim 1 , wherein the first mobile application comprises a management agent.

3. The method of claim 1 , wherein the second mobile application is configured to provide the second encryption information to the data storage location at least in part by including in the second mobile application a mobile app management library.

4. The method of claim 1 , wherein the data storage location comprises a paste board.

5. The method of claim 1 , wherein the first encryption information comprises a public key associated with the first mobile application.

6. The method of claim 1 , wherein the second encryption information comprises a public key and the second mobile application is configured to retrieve encrypted data stored in the data storage location by the first mobile application and use a private key associated with the second mobile application to decrypt the encrypted data.

7. The method of claim 1 , wherein the second mobile application is configured to transfer data to the first mobile application at least in part by using the first encryption information to encrypt data to be transferred, and storing the encrypted data in the data storage location.

8. The method of claim 1 , wherein the first encryption information is received by the first mobile application from a security management platform external to the mobile device.

9. The method of claim 1 , wherein the first mobile application is configured to generate the identifier associated with the data storage location.

10. A mobile device, comprising:

a storage device; and

a processor coupled to the storage device and configured to:

provide, from a first mobile application on a mobile device to a second mobile application on the mobile device, a first encryption information and an identifier associated with a data storage location on the storage device, wherein a library associated with the second mobile application validates an identifier associated with the first mobile application and wherein the data storage location comprises a paste board;

retrieve, from the data storage location, a second encryption information associated with the second mobile application, wherein the second mobile application is configured to provide the second encryption information to the data storage location at least in part in response to receiving the first encryption information, the identifier associated with the data storage location, and the first mobile application being validated, and wherein the second mobile application is configured to generate and include in the second encryption information an application identifier associated with the second mobile application;

validate an identity of the second mobile application based at least in part on the application identifier included in the second encryption information; and

transfer data securely between the first mobile application and the second mobile application via the data storage location, including by encrypting the data using a second encryption key included in the second encryption information.

11. The system of claim 10 , wherein the first mobile application comprises a management agent.

12. The system of claim 10 , wherein the second mobile application is configured to provide the second encryption information to the data storage location at least in part by including in the second mobile application a mobile app management library.

13. The system of claim 10 , wherein the data storage location comprises a paste board.

14. The system of claim 10 , wherein the first encryption information comprises a public key associated with the first mobile application.

15. The system of claim 10 , wherein the second encryption information comprises a public key and the second mobile application is configured to retrieve encrypted data stored in the data storage location by the first mobile application and use a private key associated with the second mobile application to decrypt the encrypted data.

16. The system of claim 10 , wherein the second mobile application is configured to transfer data to the first mobile application at least in part by using the first encryption information to encrypt data to be transferred, and storing the encrypted data in the data storage location.

17. The system of claim 10 , wherein the first encryption information is received by the first mobile application from a security management platform external to the mobile device.

18. A computer program product to provide secure communication between mobile applications, the computer program product being embodied in a non-transitory computer readable medium and comprising computer instructions for: providing, from a first mobile application on a mobile device to a second mobile application on the mobile device, a first encryption information and an identifier associated with a data storage location on the mobile device, wherein a library associated with the second mobile application validates an identifier associated with the first mobile application and wherein the data storage location comprises a paste board;

retrieving, from the data storage location, a second encryption information associated with the second mobile application, wherein the second mobile application is configured to provide the second encryption information to the data storage location at least in part in response to receiving the first encryption information, the identifier associated with the data storage location, and the first mobile application being validated, and wherein the second mobile application is configured to generate and include in the second encryption information an application identifier associated with the second mobile application;

validating an identity of the second mobile application based at least in part on the application identifier included in the second encryption information; and transferring data securely between the first mobile application and the second mobile application via the data storage location, including by encrypting the data using a second encryption key included in the second encryption information.

19. The method of claim 1 , wherein the library includes a list of trusted application and the library validates the first mobile application based on whether the identifier associated with the first mobile application is on the list of trusted applications.

20. The method of claim 1 , wherein the library modifies code associated with the second application to modify a behavior of the second application.

Assignments (4)
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; IVANTI, INC.; MOBILEIRON, INC.; IVANTI US LLC
To: MORGAN STANLEY SENIOR FUNDING, INC., AS COLLATERAL AGENT
Reel/Frame 054665/0062 →
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 →
Continuity (3)
Continuation 14137745 · Dec 20, 2013
Provisional Application 61745052 · Dec 21, 2012
Related Publication 20150319143A1 · Nov 5, 2015