Scalable cluster-based architecture for streaming media

• US 20050262245A1
• Filed: 04/19/2005
• Published: 11/24/2005
• Est. Priority Date: 04/19/2004
• Status: Abandoned Application

• Current Assignee: Kasenna, Inc. (Enghouse Systems Limited)
• Original Assignee: Kasenna, Inc. (Enghouse Systems Limited)
• Inventors: Joshi, Vinay, Menon, Satish, Muthukumarasamy, Jayakumar, Azinyue, Innocent
• Application Number:
  US11/110,101
• Publication Number:
  US 20050262245A1
• Time in Patent Office: Days
• US Class Current: 709/226
• CPC Class Codes: H04L 67/1001 for accessing one among a plurality of replicated servers
• CPC Class Codes: H04L 67/1008 based on parameters of servers, e.g. available memory or workload monitoring of computer activity G06F11/30
• CPC Class Codes: H04L 67/101 based on network conditions
• CPC Class Codes: H04L 67/1017 based on a round robin mechanism
• CPC Class Codes: H04L 67/1023 based on a hash applied to IP addresses or costs
• CPC Class Codes: H04L 67/1034 Reaction to server failures by a load balancer
• CPC Class Codes: H04N 21/23103 using load balancing strategies, e.g. by placing or distributing content on different disks, different memories or different servers storage management G06F3/0604; allocation of resources considering the load in multiprogramming arrangements G06F9/505; techniques for rebalancing the load in a distributed system G06F9/5083; access to distributed or replicated servers, e.g. load balancing, in data networks H04L67/1001
• CPC Class Codes: H04N 21/23106 involving caching operations prefetching while addressing of a memory level in which the access to the desired data or data block requires associative addressing means within memory systems or architectures G06F12/0862; caching at an intermediate stage in a data network H04L67/568
• CPC Class Codes: H04N 21/23113 involving housekeeping operations for stored content, e.g. prioritizing content for deletion because of storage space restrictions storage management, e.g. defragmentation G06F3/0604; snloading stored programs G06F9/445; housekeeping operations in file systems, e.g. deletion policies G06F16/10; buffering arrangements in a network node or in an end terminal in packet networks H04L49/90
• CPC Class Codes: H04N 21/23116 involving data replication, e.g. over plural servers synchronization of replicated data G06F11/1658; error detection or correction by means of data replication G06F11/2053; replication in distributed file systems G06F16/10; replication in distributed file systems G06F16/27; replication or mirroring of data in data networks H04L67/1095
• CPC Class Codes: H04N 21/2405 Monitoring of the internal components or processes of the server, e.g. server load allocation of resources in multiprogramming arrangements G06F9/50; performance measurement of computer activity G06F11/34
• CPC Class Codes: H04N 21/2408 Monitoring of the upstream path of the transmission network, e.g. client requests monitoring data switching networks utilization H04L43/0876; scheduling or organising the servicing of application requests H04L67/60
• CPC Class Codes: H04N 21/47202 for requesting content on demand, e.g. video on demand

Abstract

A scalable, cluster-based VoD system implemented with a multi-server, multi-storage architecture to serve large scale real-time ingest and streaming requests for content assets is provided. The scalable, cluster-based VoD system implements sophisticated load balancing algorithms for distributing the load among the servers in the cluster to achieve a cost-effective and high streaming and storage capacity solution capable of serving multiple usage patterns and large scale real-time service demands. The VoD system is designed with a highly-scalable and failure-resistant architecture for streaming content assets in real-time in various network configurations.

Claims

1. A system architecture for streaming content assets, the system architecture comprising:

a cluster of servers comprising a plurality of servers connected through a network for streaming content assets to a plurality of clients;

a plurality of storage devices connected to the plurality of servers, each storage device associated with one of the plurality of servers and comprising;

a first storage component for storing original content assets; and

a second storage component for storing replicas of the original content assets; and

a plurality of load balancing software modules running on the plurality of servers for load balancing storage and streaming requests among the plurality of servers in the cluster of servers.

2. The system architecture of claim 1, further comprising a load balancing component for connecting the cluster of servers to the plurality of clients.

3. The system architecture of claim 2, wherein the load balancing component comprises a plurality of load balancing software modules for load balancing storage and streaming requests among the plurality of servers in the cluster of servers.

4. The system architecture of claim 1, wherein the content assets comprise at least one of:

audio assets, video assets, or time-based multimedia assets.

5. The system architecture of claim 1, wherein the content assets comprise fractions or prefixes of content assets.

6. The system architecture of claim 1, wherein the plurality of servers comprise ingest and streaming servers.

7. The system architecture of claim 1, further comprising a plurality of software agents running on the plurality of servers for sharing content asset metadata information among the plurality of servers and handling content asset requests made by one of the plurality of clients.

8. The system architecture of claim 7, wherein the content asset metadata information comprises information about the content asset comprising at least one of:

content asset availability;

content asset type;

or content asset biographical information.

9. The system architecture of claim 7, wherein the plurality of software agents comprise software agents for selecting one server from the plurality of servers to store an incoming content asset based on resource availability and load balancing requirements.

10. The system architecture of claim 7, wherein the plurality of software agents comprise software agents for storing the incoming content asset in the second storage component of the selected server.

11. The system architecture of claim 7, wherein the plurality of software agents comprise software agents for selecting one server from the plurality of servers to service a streaming content request based on resource availability and load balancing requirements.

12. The system architecture of claim 11, wherein the plurality of software agents comprise software agents for determining whether the streaming content request exceeds the current streaming capacity of the cluster of servers.

13. The system architecture of claim 1, wherein the plurality of load balancing software modules comprise at least one of:

a hot-asset replication software module;

an aggressive caching software module;

a load-based replication software module;

or a time-based averaging software module.

14. The system architecture of claim 1, further comprising a replication software module for replicating content assets to the second storage component of one or more servers selected from the plurality of servers.

15. The system architecture of claim 1, further comprising a cache reclamation software module for reclaiming space in the second storage component of one or more servers selected from the plurality of servers to store replicas of the original content assets in the second storage component of the one or more servers.

16. A method for streaming content assets to a plurality of clients from a cluster of servers comprising a plurality of servers connected through a network, the method comprising:

storing a content asset in a first storage device associated with a first server from the plurality of servers based on the capacity of each one of the plurality of servers;

selecting a server from the plurality of servers to service a request for the content asset made by one of the plurality of clients;

making a replica of the content asset in a second storage device associated with a second server from the plurality of servers if future requests for the content asset will exceed the current capacity of the plurality of servers; and

load balancing subsequent requests for content assets among the plurality of servers.

17. The method of claim 16, wherein storing a content asset comprises storing at least one of:

audio assets, video assets, or time-based multimedia assets.

18. The method of claim 16, wherein storing a content asset comprises storing fractions or prefixes of content assets.

19. The method of claim 16, wherein storing a content asset in a first storage device associated with a first server from the plurality of servers comprises storing the content asset in a title storage device.

20. The method of claim 16, wherein making a replica of the content asset in a second storage device associated with a second server from the plurality of servers comprises storing the content asset in a cache storage device associated with the second server.

21. The method of claim 16, wherein load balancing subsequent requests for content assets among the plurality of servers comprises replicating content assets based on resource availability and load balancing requirements using at least one of:

a hot-asset replication software module;

an aggressive caching software module;

a load-based replication software module;

or a time-based averaging software module.

22. The method of claim 16, further comprising reclaiming space in the second storage device of the second server to store the replica of the content asset.

23. A system architecture for streaming content assets to a plurality of clients, the system architecture comprising:

a cluster of servers comprising a plurality of library servers and a plurality of cache servers for streaming content assets to a plurality of clients;

a library storage device connected to the plurality of library servers for storing content assets;

a plurality of cache storage devices connected to the plurality of cache servers for storing content assets, each cache storage device associated with one of the plurality of cache servers; and

a plurality of load balancing software modules running on the plurality of library servers and on the plurality of cache servers for load balancing storage and streaming requests to the cluster of servers from the plurality of clients.

24. The system architecture of claim 23, wherein the library storage device comprises at least one of:

a shared storage device;

a plurality of library storage devices, each library storage device associated with one of the plurality of library servers;

or a combination of a shared storage device and a plurality of library storage devices, each library storage device associated with one of the plurality of library servers.

25. The system architecture of claim 23, further comprising a load balancing component for connecting the cluster of servers to the plurality of clients.

26. The system architecture of claim 25, wherein the load balancing component comprises a plurality of load balancing software modules for load balancing storage and streaming requests among the plurality of library servers and the plurality of cache servers in the cluster of servers.

27. The system architecture of claim 23, wherein the content assets comprise at least one of:

audio assets, video assets, or time-based multimedia assets.

28. The system architecture of claim 23, wherein the content assets comprise fractions or prefixes of content assets.

29. The system architecture of claim 23, wherein the plurality of library servers comprise ingest and streaming servers.

30. The system architecture of claim 23, wherein the content asset metadata information comprises information about the content asset comprising at least one of:

content asset availability;

content asset type;

or content asset biographical information.

31. The system architecture of claim 23, further comprising a plurality of library software agents running on the plurality of library servers for sharing content asset metadata information among the plurality of library servers and the plurality of cache servers and handling content asset requests made by one of the plurality of clients.

32. The system architecture of claim 23, further comprising a plurality of cache software agents running on the plurality of cache servers for sharing content asset metadata information among the plurality of cache servers and handling content asset requests made by one of the plurality of clients.

33. The system architecture of claim 31, wherein the plurality of library software agents comprise software agents for selecting one library server from the plurality of library servers to store an incoming content asset based on resource availability and load balancing requirements in the library storage device associated with the selected library server.

34. The system architecture of claim 31, wherein the plurality of library software agents comprise software agents for streaming content assets stored in the library storage devices associated with the plurality of library servers directly to the plurality of clients.

35. The system architecture of claim 31, wherein the plurality of library software agents comprise software agents for replicating content assets stored in the library storage devices associated with the plurality of library servers to one or more of cache storage devices from the plurality of cache storage devices associated with the plurality of cache servers based on resource availability and load balancing requirements.

36. The system architecture of claim 32, wherein the plurality of cache software agents comprise software agents for streaming content assets stored in the cache storage devices associated with the plurality of cache servers directly to the plurality of clients.

37. The system architecture of claim 23, wherein the plurality of load balancing software modules comprise at least one of:

a hot-asset replication software module;

an aggressive caching software module;

a load-based replication software module;

or a time-based averaging software module.

38. The system architecture of claim 23, further comprising a replication software module for replicating content assets stored in the plurality of library storage devices to one or more cache storage devices from the plurality of cache storage devices.

39. The system architecture of claim 23, further comprising a cache reclamation software module for reclaiming space in one or more cache storage devices from the plurality of cache storage devices to store one or more replicas of a content asset stored in a library storage device.