Demand-based edge caching video content system and method

• US 8,505,057 B2
• Filed: 10/05/2010
• Issued: 08/06/2013
• Est. Priority Date: 10/05/2010
• Status: Active Grant

• Current Assignee: Vecima Networks Incorporated
• Original Assignee: Concurrent Computer Corporation
• Inventors: Rogers, Thomas J.
• Primary Examiner(s): LANGHNOJA, KUNAL N
• Application Number:
  US12/897,985
• Publication Number:
  US 20120084821A1
• Time in Patent Office: 1,036 Days
• Field of Search: 725/87, 725 91- 93, 709/217
• US Class Current: 725/87
• CPC Class Codes: H04N 21/2225 Local VOD servers
• CPC Class Codes: H04N 21/47202 for requesting content on demand, e.g. video on demand
• CPC Class Codes: H04N 21/6581 Reference data, e.g. a movie identifier for ordering a movie or a product identifier in a home shopping application

Abstract

A method (300) and system (200) for of conserving resources in a video-on-demand environment are provided. The method (300) includes storing a stub file (223) on an edge storage device while storing content (110) at a central storage device (222). When a video-on-demand request (440) is received, a resource management system (206) reads (305) the stub file (223) to determine a storage location at the central storage device (222). The resource management system (206) then retrieves the content (110) from the storage location determined from the stub file (223) and either stores it at an edge storage device (111) or delivers it the a subscriber device (109) to fulfill the video-on-demand request (440).

Claims

1. A method of conserving resources of an edge server disposed across a network and in communication with a central server, comprising:

storing a stub file at the edge server, the stub file comprising metadata for content and a storage location for the content;

informing a back office manager that the stub file is stored at the edge server, thereby causing the back office manager to perceive the content is stored at the edge server, when only the stub file is stored on the edge server and the content is stored on a server other than the edge server;

marking, with the back office manager, that the content is ready for usage in response to the informing;

receiving a demand for the content at a resource manager disposed across a network from the back office manger;

in response to the receiving, reading, with the resource manager, the stub file to determine the storage location;

retrieving, with the resource manager, the content from the storage location read from the stub file; and

storing the content at the edge server.

2. The method of claim 1, wherein the storage location comprises a memory location at the central server, wherein the retrieving comprises retrieving the content from the central server.

3. The method of claim 1, further comprising:

delivering retrieved content from the edge server to a streaming server to fulfill a video-on-demand session request.

4. The method of claim 1, further comprising:

determining whether demand for the content exceeds a demand threshold;

wherein the retrieving, and the storing occurs only where the demand for the content exceeds the demand threshold.

5. In a video-on-demand system comprising an edge server disposed distally across a network from, and in communication with, a central storage server, a method of delaying delivery of content from the central storage server to the edge server comprising:

receiving the content from an external source;

storing the content on the central storage server;

creating a stub file;

transmitting the stub file across the network and storing the stub file on the edge server;

informing a back office system that the content is stored on the edge server after the storing the stub file on the edge server but prior to the storing the content at the edge server;

receiving a video-on-demand session request for the content;

in response to the receiving, reading, at the edge server, the stub file to determine storage location information for the content;

retrieving the content in accordance with the storage location information determined from the stub file; and

delivering the content to fulfill the video-on-demand session request.

6. The method of claim 5, further comprising storing the content at the edge server upon retrieving the content.

7. The method of claim 6, wherein the delivering comprises delivering the content from the edge server to a streaming server.

8. The method of claim 5, further comprising notifying the back office system of a video-on-demand session when the video-on-demand session request is received.

9. The method of claim 5, further comprising adding at least a portion of metadata corresponding to the content to a menu before the storing the content on the edge server.

10. The method of claim 6, wherein the stub file comprises metadata for the content and a storage location of the content.

11. The method of claim 10, wherein the storage location comprises a memory location of the central storage server.

12. The method of claim 5, further comprising determining whether restrictions established in the video-on-demand system prevent the creating of the stub file.

13. A video-on-demand system, comprising:

a content receiver in communication with a central storage server, a back office system, and at least one edge server disposed distally across a network from the central storage server, wherein the content receiver is configured to;

receive content from an external source; and

upon receiving the content from the external source;

store the content on the central storage server;

deliver metadata corresponding to the content to the back office system;

generate a stub file comprising at least a portion of the metadata and a storage location on the central storage server for the content;

store the stub file on the at least one edge server; and

send a notification to the back office system that the content is stored on the at least one edge server while the content is not stored on the at least one edge server.

14. The video-on-demand system of claim 13, further comprising an edge resource manager in communication with the central storage server and the at least one edge server, wherein the edge resource manager is configured to receive a video-on-demand session request, read the stub file to determine the storage location, retrieve the content from the storage location, and store the content on the at least one edge server.

15. The video-on-demand system of claim 14, wherein the edge resource manager is in communication with the back office system, wherein the edge resource manager is configured to notify the back office system that the video-on- demand session request is received.

16. The video-on-demand system of claim 14, further comprising a menu generator in communication with the back office system, wherein the menu generator is configured to add the metadata corresponding to the content to a menu after the stub file is stored on the at least one edge server but before the content is stored on the at least one edge server.

17. The video-on-demand system of claim 13, wherein the stub file comprises a location on the central storage server corresponding to the content.

18. The video-on-demand system of claim 17, wherein the stub file further comprises caching policy information, wherein the caching policy information comprises one or more of a time limit for caching, a file number limit for caching, or content restrictions on caching.