Using Mobile Communication Facility Device Data Within a Monetization Platform

• US 20100076994A1
• Filed: 06/17/2009
• Published: 03/25/2010
• Est. Priority Date: 11/05/2005
• Status: Abandoned Application

• Current Assignee: Jumptap Incorporated (Apollo Global Management, Inc.)
• Original Assignee: Jumptap Incorporated (Apollo Global Management, Inc.)
• Inventors: Soroca, Adam, Karasic, Neal J.
• Application Number:
  US12/486,502
• Publication Number:
  US 20100076994A1
• Time in Patent Office: Days
• US Class Current: 707/769
• CPC Class Codes: G06F 16/635 Filtering based on additional data, e.g. user or group profiles
• CPC Class Codes: G06F 16/68 Retrieval characterised by using metadata, e.g. metadata not derived from the content or metadata generated manually
• CPC Class Codes: G06F 16/9577 Optimising the visualization of content, e.g. distillation of HTML documents

Abstract

In embodiments of the present invention improved capabilities are described for using a monetization platform to receive, analyze, select, aggregate, and deliver data relating to mobile communication facilities'"'"' devices characteristics, to store this data in a mobile communication facilities characteristics database, and use this data, in part, to select content that is relevant to a content request received from a publisher, and appropriate for delivery to the mobile communication facility of the user whose behavior prompted the request.

Claims

1. A method, comprising:

storing a plurality of device characteristics that are associated with a plurality of mobile communication facility models in a mobile communication facility device characteristics database;

receiving a content request from a publisher, wherein the content request originates from a behavior associated with an identified user of a mobile communication facility;

sending the content request and at least one datum from the mobile communication facility device characteristics database that relates to the mobile communication facility to a content inventory in response to the content request;

receiving a content from the content inventory, wherein the content relates to the content request, and conforms to a requirement that is associated with the at least one datum sent from the mobile communication facility device characteristics database; and

sending the received content to the publisher.

2. The method of claim 1 wherein the at least one datum from the mobile communication facility database that relates to the mobile communication facility is determined based at least in part on a user agent string associated with a navigation request.

3. The method of claim 1 wherein one of the plurality of mobile communication facility device characteristics is a mobile communication facility manufacturer.

4. The method of claim 1 wherein one of the plurality of mobile communication facility device characteristics is a mobile communication facility model.

5. The method of claim 1 wherein one of the plurality of mobile communication facility device characteristics is a mobile communication facility capability.

6. The method of claim 5 wherein the capability is a display resolution.

7. The method of claim 5 wherein the capability is a memory capacity.

8. The method of claim 1 wherein one of the plurality of mobile communication facility device characteristics is derived from a wireless operator.

9. The method of claim 1 wherein the mobile communication facility device characteristics database is associated with a wireless carrier.

10. The method of claim 1 wherein the publisher is a wireless operator.

11. The method of claim 1 wherein the publisher is a website owner.

12. The method of claim 1 wherein the publisher is a content producer.

13. The method of claim 1 wherein the publisher is a game developer.

14. The method of claim 1 wherein the publisher is an application developer.

15. The method of claim 1 wherein the publisher is a videographer.

16. The method of claim 1 wherein the publisher is a blogger.

17. The method of claim 1 wherein the advertisement server is not mobile enabled.

18. The method of claim 1 wherein the content request derives from a search request.

19. The method of claim 1 wherein the content request derives from a browse behavior.

20. The method of claim 1 wherein the content request derives from a navigation request.

21. The method of claim 1 wherein the content request derives from an SMS behavior.

22. The method of claim 1 wherein the content request derives from an MMS behavior.

23. The method of claim 1 wherein the content request derives from a gaming application behavior.

24. The method of claim 1 wherein the content request derives from a mobile communication facility application behavior.

25. The method of claim 1 wherein the content request derives from a video displayed on the mobile communication facility.

26. The method of claim 1 wherein the content request derives from a TV content displayed on the mobile communication facility device.

27. The method of claim 1 wherein the content request derives from contextual data relating to an SMS.

28. The method of claim 1 wherein the content request derives from contextual data relating to an MMS.

29. The method of claim 1 wherein the content request derives from contextual data relating to a game.

30. The method of claim 1 wherein the content request derives from contextual data relating to a software application.

31. The method of claim 1 wherein the content request derives from contextual data relating to video content.

32. The method of claim 1 wherein the content request derives from contextual data relating to TV content.

33. The method of claim 1 wherein the received content is mobile web content.

34. The method of claim 1 wherein the received content is non-mobile web content.

35. A method, comprising:

storing a plurality of device characteristics that are associated with a plurality of mobile communication facility models in a mobile communication facility device characteristics database;

receiving a content request from a publisher, wherein the content request originates from a mobile communication facility, and wherein the content request is associated with a publisher'"'"'s exception management rule;

sending the content request, exception management rule, and at least one datum from the mobile communication facility device characteristics database that relates to the mobile communication facility to a content inventory in response to the content request;

receiving a content from the content inventory, wherein the content relates to the content request, and conforms to the exception management rule and to a requirement that is associated with the datum sent from the mobile communication facility device characteristics database; and

sending the received content to the publisher.

36. The method of claim 35 wherein the exception management rule relates to an acceptable content resolution.

37. The method of claim 35 wherein the exception management rule relates to an acceptable file size.

38. The method of claim 35 wherein the exception management rule relates to an acceptable handset capability stated by the publisher.

39. The method of claim 35 wherein the exception management rule relates to a content type.

40. The method of claim 35 wherein the exception management rule relates to a browser capability.