IP Library Granted Patent US 9,009,243
Granted Patent B2
US 9,009,243 · App. 13/630,775 · Granted Apr 14, 2015

Tracking usage of and sharing data between mobile device applications

Inventors: Anita Anderson (Emeryville, CA); Brian Jenkins (San Francisco, CA)
Assignee: Defy Media, LLC
H04L12/2602H04L29/06H04L29/08072H04L67/22G06F9/445G06F11/3003G06F11/3093G06F2201/865
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,009,243
App. No.
13/630,775
Granted
Apr 14, 2015
Kind
B2
Abstract

Described herein are methods and systems for tracking usage of and sharing data between mobile device applications. A mobile device receives a first application to be installed on the mobile device. The first application includes a first notification module, a content developer identifier, and a first application identifier. The mobile device receives a second application to be installed on the mobile device, the second application including a second notification module, the content developer identifier, and a second application identifier. The mobile device stores a mobile device identifier in a keychain area of the mobile device. The mobile device provides access to the keychain area for applications which include the content developer identifier. The mobile device retrieves the mobile device identifier from the keychain area for use by the first application and the second application.

Claims (51)

1. A method for tracking usage of and sharing data between mobile device applications, the method comprising:

receiving, at a mobile device, a first application to be installed on the mobile device, the first application including a first notification module, a content developer identifier, and a first application identifier;

receiving, at the mobile device, a second application to be installed on the mobile device, the second application including a second notification module, the content developer identifier and a second application identifier;

storing, by the mobile device, a mobile device identifier in a keychain area of the mobile device;

providing access, by the mobile device, to the keychain area for applications which include the content developer identifier; and

retrieving, by the mobile device, the mobile device identifier from the keychain area for use by the first application and the second application.

2. The method of claim 1 , further comprising:

retrieving, by the mobile device, the mobile device identifier from the keychain area when the second application is installed; and

sending, by the mobile device, a message to a remote server when the second application is installed, the message including the second application identifier and the mobile device identifier.

3. The method of claim 1 , further comprising:

storing, by the mobile device, data associated with the first application in the keychain area; and

retrieving, by the mobile device, the stored data.

4. The method of claim 1 , further comprising:

retrieving, by the mobile device, the mobile device identifier from the keychain area when the first application is installed;

sending, by the mobile device, a message to a remote server when the first application is installed, the message including the first application identifier and the mobile device identifier; and

registering, by the remote server, the mobile device, wherein registering includes associating the mobile device identifier with the first application identifier.

5. The method of claim 1 , wherein a notification module separate from the first application and the second application is installed on the mobile device.

6. The method of claim 1 , wherein the keychain area is a memory area on the mobile device that is accessible by the operating system of the mobile device.

7. The method of claim 1 , wherein the content provider identifier is a bundle seed ID.

8. The method of claim 1 , wherein the first application and the second application store data in and retrieve data from the keychain area while disconnected from a network.

9. The method of claim 1 , wherein the first application and the second application store data in and retrieve data from the keychain area while connected to a network.

10. The method of claim 1 , wherein the stored data excludes a MAC address of networking hardware integrated into the mobile device.

11. The method of claim 1 , wherein the stored data excludes personal information of a user associated with the mobile device.

12. The method of claim 1 , wherein the mobile device identifier is generated by the first application.

13. The method of claim 1 , wherein the mobile device identifier is generated by the second application if the second application is launched before the first application.

14. A system for tracking usage of and sharing data between mobile device applications, the system comprising:

a mobile device configured to:

receive a first application to be installed on the mobile device, the first application including a first notification module, a content developer identifier, and a first application identifier;

receive a second application to be installed on the mobile device, the second application including a second notification module, the content developer identifier and a second application identifier;

store a mobile device identifier in a keychain area of the mobile device;

provide access to the keychain area for applications which include the content developer identifier; and

retrieve the mobile device identifier from the keychain area for use by the first application and the second application.

15. The system of claim 14 , the mobile device further configured to:

retrieve the mobile device identifier from the keychain area when the second application is installed; and

send a message to a remote server when the second application is installed, the message including the second application identifier and the mobile device identifier.

16. The system of claim 14 , the mobile device further configured to:

store data associated with the first application in the keychain area; and

retrieve the stored data.

17. The system of claim 14 , the mobile device further configured to:

retrieve the mobile device identifier from the keychain area when the first application is installed;

send a message to a remote server when the first application is installed, the message including the first application identifier and the mobile device identifier,

the remote server configured to register the mobile device, wherein registering includes associating the mobile device identifier with the first application identifier.

18. The system of claim 14 , wherein a notification module separate from the first application and the second application is installed on the mobile device.

19. The system of claim 14 , wherein the keychain area is a memory area on the mobile device that is accessible by the operating system of the mobile device.

20. The system of claim 14 , wherein the content provider identifier is a bundle seed ID.

21. The system of claim 14 , wherein the first application and the second application store data in and retrieve data from the keychain area while disconnected from a network.

22. The system of claim 14 , wherein the first application and the second application store data in and retrieve data from the keychain area while connected to a network.

23. The system of claim 14 , wherein the stored data excludes a MAC address of networking hardware integrated into the mobile device.

24. The system of claim 14 , wherein the stored data excludes personal information of a user associated with the mobile device.

25. The system of claim 14 , wherein the mobile device identifier is generated by the first application.

26. The system of claim 14 , wherein the mobile device identifier is generated by the second application if the second application is launched before the first application.

Assignments (5)
SECURITY AGREEMENT Recorded Nov 2, 2015
From: DEFY MEDIA, LLC
To: ALLY BANK
Reel/Frame 037031/0452 →
TO CORRECT NOTICE OF RECORDATION OF ASSIGNMENT DOCUMENT NO. 502846650,REEL/FRAME:033074/0614,RECORDATION DATE:6/11/14;TO CORRECT THE ASSIGNOR'S DOC DATE TO JUNE 8 2014 Recorded Nov 20, 2014
From: VIACOM INTERNATIONAL INC.
To: ATOM ENTERTAINMENT, INC.
Reel/Frame 034403/0549 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Jul 31, 2014
From: ATOM ENTERTAINMENT, INC.
To: DEFY MEDIA, LLC
Reel/Frame 033450/0021 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Jun 11, 2014
From: VIACOM INTERNATIONAL INC.
To: ATOM ENTERTAINMENT, INC.
Reel/Frame 033074/0614 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Dec 21, 2012
From: ANDERSON, ANITA; JENKINS, BRIAN
To: VIACOM INTERNATIONAL INC.
Reel/Frame 029665/0377 →
Continuity (1)
Related Publication 20140095692A1 · Apr 3, 2014