CONTENT DELIVERY ARCHITECTURE AND METHOD
A content delivery architecture comprises an intermediate domain via which content is transferable from content providers in at least one content provider domain to consumers in at least one consumer domain. A delivery layer is included having a content store in the intermediate domain for storing content from content providers in the at least one content provider domain for delivery to a consumer. A discovery layer has a content metadata store in the intermediate domain for storing metadata associated with content available from the content store and from content providers in the at least one content provider domain. A support and service layer administers the delivery of content from the content store, and from content providers in the at least one content provider domain, to a consumer using metadata stored in the content metadata store.
1 . A content delivery architecture comprising:
an intermediate domain via which content is transferable from content providers in at least one content provider domain to consumers in at least one consumer domain;
a delivery layer having a content store in the intermediate domain for storing content from content providers in the at least one content provider domain for delivery to a consumer;
a discovery layer having a content metadata store in the intermediate domain for storing metadata associated with content available from the content store and from content providers in the at least one content provider domain; and
a support and service layer for administering the delivery of content from the content store, and from content providers in the at least one content provider domain, to a consumer using metadata stored in the content metadata store.
2 . The architecture as claimed in claim 1 wherein the support and service layer includes a user profile store and the discovery layer includes a recommendation engine for recommending content to a consumer, the recommendation engine using information from the user profile store and from the content metadata store in making the recommendation.
3 . The architecture as claimed in claim 2 wherein the user profile store is updated with consumer information obtained from consumer requests for content.
4 . The architecture as claimed in claim 2 wherein the recommendation engine and the content store exchange information concerning delivery and the exchanged information including at least one of: availability of content stored in the content store; hit ratio; and request rate.
5 . The architecture as claimed in claim 2 wherein the support and service layer includes a content popularity processor for monitoring the popularity of content and the recommendation engine uses information regarding content popularity from the content popularity processor in making a recommendation.
6 . The architecture as claimed in claim 5 wherein the content popularity processor receives information from consumer requests for content.
7 . The architecture as claimed in claim 1 wherein the content store is arranged to retain more popular content and discard less popular content.
8 . The architecture as claimed in claim 7 wherein more popular content is determined by the recommendation engine.
9 . The architecture as claimed in claim 1 wherein the content metadata store stores metadata associated only with content for which support and service is available.
10 . The architecture as claimed in claim 1 and including a delivery mechanism for streaming content from the content store to a consumer.
11 . The architecture as claimed in claim 1 wherein, when a consumer requests content available from a content provider or content providers in the at least one content provider domain and not stored in the content store, the delivery layer transfers the requested content to the consumer from said content provider or content providers without storing the content in the content store.
12 . The architecture as claimed in claim 1 wherein the hit ratio is used in determining the amount of recommended content stored in the content store.
13 . The architecture as claimed in claim 12 wherein the request rate is used in determining the amount of recommended content stored in the content store.
14 . The architecture as claimed in claim 1 wherein the intermediate domain comprises a plurality of sub-domains, each sub-domain including:
an intermediate domain via which content is transferable from content providers in at least one content provider domain to consumers in at least one consumer domain;
a delivery layer having a content store in the intermediate domain for storing content from content providers in the at least one content provider domain for delivery to a consumer;
a discovery layer having a content metadata store in the intermediate domain for storing metadata associated with content available from the content store and from content providers in the at least one content provider domain; and
a support and service layer for administering the delivery of content from the content store, and from content providers in the at least one content provider domain, to a consumer using metadata stored in the content metadata store.
15 . The architecture as claimed in claim 1 and including at least one source domain and/or sink domain.
16 . A method for content delivery comprising:
transferring content via an intermediate domain from content providers in at least one content provider domain to consumers in at least one consumers domain;
in a delivery layer, storing content in the intermediate domain from content providers in the at least one content provider domain for delivery of content to a consumer;
in a discovery layer, storing metadata in the intermediate domain, the metadata being associated with stored content from the stored content store and content available from content providers in the at least one content provider domain; and
in a support and service layer, administering the delivery of stored content, and content available from content providers in the at least one content provider domain, to a consumer using stored metadata.
17 . The method as claimed in claim 16 and recommending content to a consumer using information from a user profile store included in the support and service layer and information from the stored content metadata and information from the delivery layer including at least one of: availability of content stored in the content store;
hit ratio; and request rate.
18 . The method as claimed in claim 16 and including monitoring the popularity of content and using information regarding content popularity in making a content recommendation to a consumer.
19 . The method as claimed in claim 18 wherein more popular content is determined by the recommendation engine.
20 . The method as claimed in claim 16 wherein the stored content metadata is metadata associated only with content for which support and service is available.