Content Engine for Mobile Communications Systems

1. A method comprising: receiving, at a content engine and from a mobile device, a request for content; determining if access to the content has exceeded a threshold value; retrieving, if access to the content has not exceeded the threshold value, the content in response to the request; modifying, at a content format modifier of the content engine and by utilizing instructions from a memory that are executed by a processor, the content based on specifications of the mobile device to create modified content formatted for the mobile device, wherein the specifications are associated with one of a hardware component, a software component, and a firmware component of the mobile device, and wherein the specifications are identified by a make of the mobile device, a firmware version of the mobile device, and a revision number of the mobile device; and sending the modified content to the mobile device, wherein the modified content is sent to the mobile device based in part on an index of available content.

2. The method of claim 1 , wherein the content is associated with one of cached web content stored in a cache server of the content engine, non-cacheable web content provided by a non-cacheable web content provider that is in communication with the content engine, and digital media content stored in a digital media content server of the content engine.

3. The method of claim 2 , further comprising: analyzing the request to determine to which of the digital media content server, the cache server, and the non-cacheable web content provider the request should be routed; and routing the request to one of the digital media content server, the cache server, and the non-cacheable web content provider based upon the analysis.

4. The method of claim 3 , further comprising analyzing the request to determine where the request should be routed by comparing the content to a lookup table, which is stored within the content engine and is indicative of the cached web content stored in the cache server, to determine if the content is cached in the cache server.

5. The method of claim 4 , further comprising updating, by utilizing the cache server, the lookup table to reflect changes to cache server content stored by the cache server.

6. The method of claim 3 , further comprising analyzing the request, based on a rule, to determine where the request should be routed.

7. The method of claim 6 , wherein the rule is a caching rule that defines which type of content of a plurality of content types the content engine should cache in the cache server.

8. A content engine, comprising: a memory that stores instructions; a processor that executes the instructions to perform operations, the operations comprising: receiving, by utilizing a content gateway of the content engine, a request for content from a mobile device; determining if access to the content has exceeded a threshold value; retrieving, if access to the content has not exceeded the threshold value, content in response to the request, wherein the content is retrieved by utilizing the content gateway; modifying, by utilizing a content format modifier of the content engine, the content based on specifications of the mobile device 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, and wherein the specifications are identified by a make of the mobile device, a firmware version of the mobile device, and a revision number of the mobile device; and sending the modified content to the content gateway for delivery to the mobile device, wherein the modified content is sent to the mobile device based in part on an index of available content.

9. The content engine of claim 8 , wherein the content is associated with one of cached web content stored in a cache server, non-cacheable web content provided by a non-cacheable web content provider that is in communication with the content engine, and digital media content stored in a digital media content server.

10. The content engine of claim 9 , wherein the cache server and the digital media content server are components of the content engine.

11. The content engine of claim 9 , wherein the operations further comprise: analyzing, by utilizing the content gateway, the request to determine to which of the digital media content server, the cache server, and the non-cacheable web content provider the request should be routed; and routing, by utilizing the content gateway, the request to one of the digital media content server, the cache server, and the non-cacheable web content provider based upon the analysis.

12. The content engine of claim 11 , wherein the operations further comprise analyzing the request to determine where the request should be routed by comparing the content to a lookup table, which is stored within the content engine and is indicative of the cached web content stored in the cache server, to determine if the content is cached in the cache server.

13. The content engine of claim 12 , wherein the operations further comprise updating, by utilizing the cache server, the lookup table to reflect changes to cache server content stored by the cache server.

14. The content engine of claim 11 , wherein the operations further comprise analyzing, based on a rule, the request to determine where the content request should be routed.

15. The content engine of claim 14 , wherein the rule is a caching rule that defines which type of content of a plurality of content types the content engine should cache in the cache server.

16. 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 a request for content from a mobile device; determining if access to the content has exceeded a threshold value; retrieving, if access to the content has not exceeded the threshold value, the content in response to the request; modifying the content based on specifications of the mobile device 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, and wherein the specifications are identified by a make of the mobile device, a firmware version of the mobile device, and a revision number of the mobile device; and sending the modified content to the mobile device, wherein the modified content is sent to the mobile device based in part on an index of available content.

17. The non-transitory computer-readable medium of claim 16 , wherein the content is associated with one of cached web content stored in a cache server of the content engine, non-cacheable web content provided by a non-cacheable web content provider that is in communication with the content engine, and digital media content stored in a digital media content server of the content engine.

18. The non-transitory computer-readable medium of claim 17 , wherein the operations further comprise: analyzing the request to determine to which of the digital media content server, the cache server, and the non-cacheable web content provider the request should be routed; and routing the request to one of the digital media content server, the cache server, and the non-cacheable web content provider based upon the analysis.

19. The non-transitory computer-readable medium of claim 17 , wherein the operations further comprise: analyzing the request to determine where the content request should be routed; comparing the content to a lookup table, which is stored within the content engine and is indicative of the cached web content stored in the cache server, to determine if the content is cached in the cache server.

20. The non-transitory computer-readable medium of claim 16 , wherein the operations further comprise determining if the content is cached, wherein the operations further comprise determining if the content is cacheable if the content is determined to not be cached, and wherein the operations further comprise determining that the content is cacheable based on historical data provided by a lookup table.