Content engine for mobile communications systems

• US 7,756,130 B1
• Filed: 05/22/2007
• Issued: 07/13/2010
• 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: Hu, Q. James, Lee, Bo
• Primary Examiner(s): Vu, Thong H
• Application Number:
  US11/752,199
• Time in Patent Office: 1,148 Days
• Field of Search: 370/237, 370/392, 711/118, 711/129, 709/203, 709/213, 709/227, 709/219, 709/237, 709/231, 709/236, 709/233, 709/217, 709/247
• US Class Current: 370/389
• 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 method for content provisioning via an intra-network content engine, the method comprising:

receiving a content request from a mobile device at the content engine, the content request being used to request specific content that is one of cached web content stored in a cache server, non-cacheable web content provided by non-cacheable web content provider, and digital media content stored in a digital media content server;

the content engine analyzing the content request to determine to which of the digital media content server, the cache server, and the non-cacheable web content provider, the content request should be routed;

the content engine routing the content request to the cache server, if the requested specific content is cached web content;

the content engine routing the content request to the digital media content server, if the requested specific content is digital media content;

the content engine routing the content request to the non-cacheable web content provider, if the requested specific content is non-cacheable web content;

the content engine retrieving the requested specific content from either the cache server, the digital media content server, or the non-cacheable web content provider based upon the determination made by the content gateway;

the content engine sending the requested specific content to a content format modifier;

the content format modifier modifying the requested specific content in accordance with specifications of the mobile device, the specifications being identified by one of an International Mobile Equipment Identity (IMEI), a make of the mobile device, a model of the mobile device, and a revision number of the mobile device; and

the content engine sending the requested content to the mobile device.

2. The method of claim 1, wherein the content engine analyzing the content request to determine to which of the mobile content server, the cache server, and the non-cacheable web content provider, the content request should be routed comprises the content engine comparing the content to a lookup table, which is stored within the content engine and periodically updated by the cache server, based upon the cached web content stored in the cache server at any given time to determine if the requested content is cached in the cache server.

3. The method of claim 1, wherein the content engine analyzing the content request to determine to which of the digital media content server, the cache server, and the non-cacheable web content provider, the content request should be routed comprises the content engine utilizing one or more rules to determine to which of the digital media content server, the cache server, and the non-cacheable web content provider, the content request should be routed, the rules being based upon needs of a wireless operator.

4. An intra-network content engine configured to process content requests received from a plurality of mobile devices, the content engine comprising:

a content gateway configured to;

receive a specific content request from a mobile device of the plurality of mobile device, the content request being used to request specific content that is one of cached web content stored in a cache server, non-cacheable web content provided by non-cacheable web content provider, and digital media content stored in a digital media content server;

analyze the specific content request to determine to which of the cache server, the non-cacheable web content provider, and the digital media content server, the specific content request should be routed;

route the specific content request to the cache server, if the requested specific content is cached web content;

route the specific content request to the digital media content server, if the requested specific content is digital media content;

route the specific content request to the non-cacheable web content provider, if the requested specific content is non-cacheable web content;

retrieve the requested specific content from either the cache server, the digital media content server, or the non-cacheable web content provider based upon the determination;

send the requested specific content to a content format modifier;

the content format modifier being configured to;

modify the requested specific content in accordance with specifications of the mobile device, the specifications being identified by one of an International Mobile Equipment Identity (IMEI), a make of the mobile device, a model of the mobile device, and a revision number of the mobile device;

the content engine being further configured to;

send the requested specific content to the mobile device.

5. The content engine of claim 4, wherein the non-cacheable web content provider is a web server.

6. The content engine of claim 4, wherein the cacheable web content provider is a web server.

7. The content engine of claim 4, wherein the content gateway is further configured to store a lookup table and compare the specific content request to the lookup table to determine if the specific requested content is cached and stored in the cache server, the lookup table being periodically updated by the cache server based upon the cached web content stored in the cache server at any given time.

8. The content engine of claim 4, wherein the content gateway comprises one or more rules used to determine to which of the cache server, the non-cacheable web content provider, and the digital media content server, the specific content request should be routed.

9. The content engine of claim 4, wherein the content gateway comprises one or more rules used to determine if the requested specific content is cacheable.

10. A non-transitory computer-readable medium of a content engine comprising computer-executable instructions which, when executed, perform the steps of:

receiving a content request from a mobile device, the content request being used to request specific content that is one of cached web content stored in a cache server, non-cacheable web content provided by non-cacheable web content provider, and digital media content stored in a digital media content server;

analyzing the content request to determine to which of the digital media content server, the cache server, and the non-cacheable web content provider, the content request should be routed;

routing the content request to the cache server, if the requested specific content is cached web content;

routing the content request to the digital media content server, if the requested specific content is digital media content;

routing the content request to the non-cacheable web content provider, if the requested specific content is non-cacheable web content;

retrieving the requested specific content from either the cache server, the digital media content server, or the non-cacheable web content provider based upon the determination;

sending the requested content to a content format modifier to modify the content in accordance with specifications of the mobile device, the specifications are provided by one of an International Mobile Equipment Identity (IMEI) of the mobile device, a make of the mobile device, a model of the mobile device, and a revision number of the mobile device; and

sending the requested content to the mobile device.

11. The non-transitory computer-readable medium of claim 10, further comprising instructions which, when executed, perform a step of comparing the content request to a lookup table to determine if the requested content is cached in the cache server.

12. The non-transitory computer-readable medium of claim 10, further comprising instructions which, when executed, perform a step of analyzing the content request to determine to which of the digital media content server, the cache server, and the non-cacheable web content provider, the content request should be routed based upon one or more rules, the rules being based upon needs of a wireless operator.