Content engine for mobile communications systems

• US 9,986,059 B2
• Filed: 02/17/2016
• Issued: 05/29/2018
• Est. Priority Date: 05/22/2007
• Status: Expired due to Fees

• Current Assignee: AT&T Mobility II LLC (AT&T, Inc.)
• Original Assignee: AT&T Mobility II LLC (AT&T, Inc.)
• Inventors: Lee, Bo, Hu, Qingmin
• Primary Examiner(s): CHO, HONG SOL
• Application Number:
  US15/045,885
• Publication Number:
  US 20160164995A1
• Time in Patent Office: 832 Days
• Field of Search: None
• CPC Class Codes: H04L 67/289 Intermediate processing functionally located close to the data consumer application, e.g. in same machine, in same home or in same sub-network
• CPC Class Codes: H04L 67/34 involving the movement of software or configuration parameters network booting or remote initial program loading [RIPL] G06F9/4416
• CPC Class Codes: H04L 67/563 Data redirection of data network streams
• CPC Class Codes: H04L 67/565 Conversion or adaptation of application format or content adding application control or application functional data H04L67/561
• CPC Class Codes: H04L 67/568 Storing data temporarily at an intermediate stage, e.g. caching
• CPC Class Codes: H04W 88/18 Service support devices; Network management devices

Abstract

An exemplary content engine includes a content gateway configured to analyze and route content requests to a content server. The content server can be a cache server or a mobile content server. The cache server can be configured to receive and store cacheable web content from a controller that is configured to receive the cacheable web content from at least one cacheable web content provider, such as a web server, and route the content to the cache server. The mobile content server can be configured to receive, from the controller, and store the digital media content. The controller can be further configured to receive the digital media content from at least one external content server and route the content to the mobile content server. The content gateway can be further configured to receive non-cacheable web content from at least one non-cacheable web content provider.

Claims

1. A system, comprising:

a memory that stores instructions;

a processor that executes the instructions to perform operations, the operations comprising;

receiving, from a mobile device, a request for content;

retrieving the content in response to the request;

modifying, based on a device configuration of the mobile device, a device type of the mobile device, and specifications of the mobile device, the content to create modified content formatted for the mobile device, wherein the specifications are associated with a hardware component, a software component, and a firmware component of the mobile device;

transmitting, to the mobile device and by utilizing a controller, the modified content formatted for the mobile device, wherein the modified content is transmitted to the mobile device based on an index of content that indicates a time when the modified content is scheduled to be available from a cache server, wherein the controller is invisible to the mobile device and the modified content is transmitted to the mobile device by the controller to appear as if the modified content is delivered directly from an original content provider instead of the controller;

determining a most often used format type for the content; and

storing a configuration of the content corresponding to the most often used format type for the content.

2. The system of claim 1, wherein the operations further comprise identifying the specifications of the mobile device based on a make of the mobile device, a firmware version of the mobile device, a revision number of the mobile device, or a combination thereof.

3. The system of claim 1, wherein the operations further comprise determining, in response to the request for the content, a content type associated with the content.

4. The system of claim 1, wherein the operations further comprise determining if the content is cached.

5. The system of claim 4, wherein the operations further comprise determining, if the content is determined to not be cached, if the content is cacheable.

6. The system of claim 5, wherein the operations further comprise forwarding, if the content is determined to be cacheable, the request for the content to a content gateway.

7. The system of claim 1, wherein the operations further comprise determining if access to the content has exceeded a threshold value.

8. The system of claim 7, wherein the operations further comprise retrieving, if access to the content has not exceeded the threshold value, the content in response to the request.

9. The system of claim 1, wherein the operations further comprise analyzing the request to determine where the request is to be routed by comparing the content to a lookup table.

10. The system of claim 9, wherein the operations further comprise updating the lookup table based on a change to cache server content of the cache server.

11. The system of claim 1, wherein the operations further comprise retrieving the content from an external content provider.

12. The system of claim 1, wherein the operations further comprise identifying the device type of the mobile device.

13. A method, comprising:

receiving, from a mobile device, a request for content;

obtaining the content in response to the request;

altering, based on a device configuration of the mobile device, a device type of the mobile device, and specifications of the mobile device, the content to create modified content formatted for the mobile device, wherein the specifications are associated with a hardware component, a software component, and a firmware component of the mobile device, wherein the altering is performed by utilizing instructions from a memory that are executed by a processor;

forwarding, to the mobile device and by utilizing a controller, the modified content formatted for the mobile device, wherein the modified content is transmitted to the mobile device based on an index of content that indicates a time when the modified content is scheduled to be available from a cache server, wherein the controller is invisible to the mobile device and the modified content is transmitted to the mobile device by the controller to appear as if the modified content is delivered directly from an original content provider instead of the controller;

determining a most often used format type for the content; and

storing a configuration of the content corresponding to the most often used format type for the content.

14. The method of claim 13, further comprising identifying the specifications of the mobile device based on a make of the mobile device, a firmware version of the mobile device, a revision number of the mobile device, or a combination thereof.

15. The method of claim 13, further comprising determining, in response to the request for the content, a content type associated with the content.

16. The method of claim 13, further comprising determining if the content is cached.

17. The method of claim 16, further comprising obtaining the content from the cache server if the content is cached.

18. The method of claim 13, further comprising identifying the device type of the mobile device.

19. The method of claim 13, further comprising maintaining the index of available content.

20. A non-transitory computer-readable medium of a content engine comprising computer-executable instructions, which, when loaded and executed by a processor, cause the processor to perform operations, the operations comprising:

receiving, from a mobile device, a request for content;

obtaining the content in response to the request;

modifying, based on a device configuration of the mobile device, a device type of the mobile device, and specifications of the mobile device, the content to create modified content formatted for the mobile device, wherein the specifications are associated with a hardware component, a software component, and a firmware component of the mobile device;

forwarding, to the mobile device and by utilizing a controller, the modified content formatted for the mobile device, wherein the modified content is transmitted to the mobile device based on an index of content that indicates a time when the modified content is scheduled to be available from a cache server, wherein the controller is invisible to the mobile device and the modified content is transmitted to the mobile device by the controller to appear as if the modified content is delivered directly from an original content provider instead of the controller;

determining a most often used format type for the content; and

storing a configuration of the content corresponding to the most often used format type for the content.