Method of data management for efficiently storing and retrieving data to respond to user access requests
View Patent ↗A method of data management for efficiently storing and retrieving data in response to user access requests. The method includes receiving a request from at least one client for a title not resident in a storage server, where the title includes a play track having a plurality of chapters. The retrieval from a secondary storage device of play track portions proximate chapter delineation points is initiated, and bandwidth capacity and quality-of-service (QoS) parameters associated with the secondary storage device is determined. In the case of a client request to begin presentation of the title at one of the chapters, streaming of retrieved portions of the play track chapter to the client is initiated, masking latency associated with the secondary storage device is provided, and retrieval of at least unretrieved portions of the play track chapter and subsequent play track portions from the secondary storage device is initiated.
1. A method comprising:
deleting a portion of content from a storage device determined to be accessed less frequently based on user access patterns, wherein the deleted portion is determined as not being bookmarked or proximate to entry points associated with the content.
2. The method of claim 1 , wherein the content comprises at least one of a play track, a trick track, a leader track, a promotional track, a still image, and metadata.
3. The method of claim 1 , further comprising:
iteratively determining a remaining capacity of the storage device; and
adapting at least a second portion of the content stored on the storage device based at least in part on the user access patterns and the determined remaining capacity of the storage device.
4. The method of claim 1 , wherein the storage device is comprised of a plurality of modules, and wherein the content is stored on at least two of the plurality of modules.
5. The method of claim 1 , wherein the deleted portion is determined as being last accessed at an earlier point in time relative to at least one other portion of the content.
6. The method of claim 1 , wherein the storage device is comprised of a plurality of modules, and wherein the portion is deleted from a first of the plurality of modules, and wherein the portion is stored on a second of the plurality of modules.
7. The method of claim 6 , wherein the deletion of the portion from the first of the plurality of modules and the storage of the portion on the second of the plurality of modules is based at least in part on a relative load between the first and second plurality of modules.
8. The method of claim 1 , wherein the storage device is included in a server, the method further comprising:
receiving second content at the server,
wherein the deletion of the portion of content is responsive to receiving the second content at the server.
9. The method of claim 8 , wherein the receipt of the second content is based at least in part on a push model, the method further comprising:
determining, at the server, that the second content is likely to be accessed by at least one user serviced by the server; and
storing the second content on the storage device responsive to determining that the second content is likely to be accessed by the at least one user.
10. The method of claim 1 , wherein the content is an audio track.
11. An apparatus comprising:
a storage device; and
a controller configured to:
delete a portion of content from the storage device determined to be accessed less frequently based on user access patterns, wherein the deleted portion is determined as not being bookmarked or proximate to entry points associated with the content.
12. The apparatus of claim 11 , wherein the content comprises at least one of a play track, a trick track, a leader track, a promotional track, a still image, and metadata.
13. The apparatus of claim 11 , wherein the controller is further configured to:
for a first publication of the content, store in the storage device meta data associated with the content, wherein the meta data comprises one or more of content description, content rights, a content price, content discount rules, still images, moving images, preview tracks, HTML links, title descriptions, MPAA ratings, and content information configured for interactive presentation within a client.
14. The apparatus of claim 11 , wherein the controller is further configured to:
iteratively determine a remaining capacity of the storage device; and
adapt at least a second portion of the content stored on the storage device based at least in part on the user access patterns and the determined remaining capacity of the storage device.
15. The apparatus of claim 11 , wherein the storage device is comprised of a plurality of modules, and wherein the content is stored on at least two of the plurality of modules.
16. The apparatus of claim 11 , wherein the deleted portion is determined by the controller to have been last accessed at an earlier point in time relative to at least one other portion of the content.
17. The apparatus of claim 11 , wherein the content is an audio track.
18. A system comprising:
a server comprising a storage device and a controller,
wherein the controller is configured to:
delete a portion of content from the storage device determined to be accessed less frequently based on user access patterns, wherein the deleted portion is determined as not being bookmarked or proximate to entry points associated with the content.
19. The system of claim 18 , further comprising:
a secondary storage device,
wherein the server is configured to receive the content from the secondary storage device via a network.
20. The system of claim 19 , further comprising:
a second server,
wherein the server is configured to receive the content from the second server via a second network.