Multicase Downloading Using Path Information

• US 20090113024A1
• Filed: 06/22/2005
• Published: 04/30/2009
• Est. Priority Date: 06/22/2005
• Status: Abandoned Application

• Current Assignee: Thomson Licensing (Vantiva SA)
• Original Assignee: Thomson Licensing SA (Vantiva SA)
• Inventors: Li, Jun, Zhang, Junbiao, Verma, Snigdha
• Application Number:
  US11/922,762
• Publication Number:
  US 20090113024A1
• Time in Patent Office: Days
• US Class Current: 709/219
• CPC Class Codes: H04L 65/1101 Session protocols
• CPC Class Codes: H04L 65/612 for unicast
• CPC Class Codes: H04L 67/06 specially adapted for file transfer, e.g. file transfer protocol [FTP]
• CPC Class Codes: H04L 67/1001 for accessing one among a plurality of replicated servers
• CPC Class Codes: H04L 67/289 Intermediate processing functionally located close to the data consumer application, e.g. in same machine, in same home or in same sub-network
• CPC Class Codes: H04L 67/568 Storing data temporarily at an intermediate stage, e.g. caching
• CPC Class Codes: H04L 67/62 Establishing a time schedule for servicing the requests
• CPC Class Codes: H04L 67/63 Routing a service request depending on the request content or context
• CPC Class Codes: H04L 69/329 in the application layer [OSI layer 7]

Abstract

The downloading of content to a requesting client (A1, A2 and A3) through content distribution network consisting of edge servers occurs upon receiving a content request, a content server responses with a request-routing message that includes source data identifying the content and path data identifying a path through the network to a source of such content. Having the path information in request-routing message enables a requesting client to make the request to a particular edge server, which in turn can register the downloading request and access the content from an appropriate location, thereby obviating the frequent communication between the content server and edge servers on the path.

Claims

1. A method for delivering content to a requesting client from a content server through a content delivery network containing edge servers, comprising the steps of:

receiving a content request by said content server, from said requesting client;

creating a path of edge servers, by said content server, the path is from said requesting client to a source of the requested content;

returning a request-routing message containing said path, by said content server, to said requesting client to identify at least one edge server via which the client can request the content for delivery.

2. The method according to claim 1 further comprising the steps of

receiving said content delivery request from the client, by an edge server;

parsing the path data within said content request, by said edge server, to identify the at least one server via which the requested piece of content will be delivered; and

forwarding a content request to the identified server by said edge server;

delivering the requested piece of content from the identified server.

3. The method according to claim 1 wherein the step of returning the routing message includes the step of returning a path-containing uniform resource locator (URL).

4. The method according to claim 1 wherein the step of creating a path of edge servers further includes the step of adding the path to a multicasting tree if the path is not a first path for requested content in the content delivery network.

5. The method according to claim 4 further comprising the step of updating the existing multicasting tree to optimize content delivery.

6. The method according to claim 5 further comprising the step of updating the existing multicasting tree dynamically in response to changing conditions.

7. The method according to claim 6 further comprising the step of updating the existing multicasting tree in response to failure of a server within the tree.

8. The method according to claim 6 further comprising the step of updating the existing multicasting tree dynamically in response a change in content availability.

9. The method according to claim 3 wherein the parsing step includes the step of adding at least one server to the multicasting tree in accordance with the path information in the content information.

10. Apparatus for delivering content to a requesting client, comprising:

content server means for (1) receiving a content request from said requesting client, (2) for creating a path of edge servers from said requesting client to a source of the requested content;

(3) for returning to a request-routing message containing said path, by said content server, to said requesting client; and

(4) for sending a content request, by said requesting client, to at least a first edge server on said path; and

wherein

the at least one of the edge server means receiving said content request and parsing the path data within said content request, to identify at least one server via which the requested piece of content will be delivered; and

forwarding a content request to the identified server by said edge server;

so said identified server can deliver the requested piece of content.

11. The apparatus according to claim 10 wherein the request-routing message comprises a path-containing uniform resource locator.

12. A method for delivering content to a requesting client, comprising the steps of:

responsive to a request from the client for a piece of content, returning to the requesting client content information including source data identifying a source of the content and path data identifying a path to such content source;

receiving from the requesting client the content source information to initiate content delivery;

parsing the path data within the received client source information to identify at least one server via which the requested piece of content will be delivered; and

downloading the requested piece of content via the identified server.