WO2005099223A1 - Cache server network and method of scheduling the distribution of content files - Google Patents

Cache server network and method of scheduling the distribution of content files Download PDF

Info

Publication number
WO2005099223A1
WO2005099223A1 PCT/US2004/007652 US2004007652W WO2005099223A1 WO 2005099223 A1 WO2005099223 A1 WO 2005099223A1 US 2004007652 W US2004007652 W US 2004007652W WO 2005099223 A1 WO2005099223 A1 WO 2005099223A1
Authority
WO
WIPO (PCT)
Prior art keywords
cache server
request
content
server
cache
Prior art date
Application number
PCT/US2004/007652
Other languages
French (fr)
Inventor
Jun Li
Junbiao Zhang
Snigdha Verma
Original Assignee
Thomson Licensing
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Thomson Licensing filed Critical Thomson Licensing
Priority to CN200480042399.4A priority Critical patent/CN1981501A/en
Priority to BRPI0418629-0A priority patent/BRPI0418629A/en
Priority to US10/592,345 priority patent/US20070208737A1/en
Priority to EP04720439A priority patent/EP1723763A1/en
Priority to PCT/US2004/007652 priority patent/WO2005099223A1/en
Priority to JP2007502777A priority patent/JP2007529073A/en
Publication of WO2005099223A1 publication Critical patent/WO2005099223A1/en

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00—Network arrangements or protocols for supporting network services or applications
    • H04L67/2866—Architectures; Arrangements
    • H04L67/2885—Hierarchically arranged intermediate devices, e.g. for hierarchical caching
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00—Network arrangements or protocols for supporting network services or applications
    • H04L67/50—Network services
    • H04L67/52—Network services specially adapted for the location of the user terminal
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00—Network arrangements or protocols for supporting network services or applications
    • H04L67/50—Network services
    • H04L67/55—Push-based network services
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00—Network arrangements or protocols for supporting network services or applications
    • H04L67/50—Network services
    • H04L67/60—Scheduling or organising the servicing of application requests, e.g. requests for application data transmissions using the analysis and optimisation of the required network resources
    • H04L67/62—Establishing a time schedule for servicing the requests
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L69/00—Network arrangements, protocols or services independent of the application payload and not provided for in the other groups of this subclass
    • H04L69/30—Definitions, standards or architectural aspects of layered protocol stacks
    • H04L69/32—Architecture of open systems interconnection [OSI] 7-layer type protocol stacks, e.g. the interfaces between the data link level and the physical level
    • H04L69/322—Intralayer communication protocols among peer entities or protocol data unit [PDU] definitions
    • H04L69/329—Intralayer communication protocols among peer entities or protocol data unit [PDU] definitions in the application layer [OSI layer 7]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L12/00—Data switching networks
    • H04L12/02—Details
    • H04L12/16—Arrangements for providing special services to substations
    • H04L12/18—Arrangements for providing special services to substations for broadcast or conference, e.g. multicast

Definitions

  • the present invention relates generally to the field of data communication and cache server networks, and specifically to systems and methods for scheduling multicasting distribution of content files within content delivery networks.
  • a client may rather watch a high quality downloaded video at a future scheduled time than view a low quality streaming video instantaneously.
  • a mobile user can order a video in advance while he/she is in a cellular mobile network and download it at a later time while he/she is in a hotspot wireless LAN. This is known as a remote site downloading. As such, the mobile user can enjoy a high quality content at low cost.
  • a content delivery network (CDN) consists of cache servers at different geographic locations, i.e., network nodes with storage and transport capabilities.
  • CDN content delivery network
  • the basic premise of CDN technology is that the link between the cache server and the client has low cost and high bandwidth. If at the time a client requests a content file, the content file is stored in the cache of a nearby cache server, the downloading will be fast. Otherwise, the client may experience a longer delay. Thus, it is preferable for a client to download the content file from the most nearby cache server.
  • the technology of finding the nearby cache server for a client is called request-routing.
  • an extension of conventional request-routing with content timing is provided to redirect a request to a closer cache server based on the future availability of the requested content on the cache server.
  • a client can tolerate a delay for a large size content file up to the expected service time which the client designates as the time he/she wishes to retrieve the content file.
  • the client will not experience a delay. It is a goal of the industry to reduce these delays by properly scheduling the downloading of requested content files to the appropriate cache server for client retrieval.
  • Multicasting content delivery can be requested at different cache servers.
  • a downloading service requires a CDN to provide distribution of a content file to the cache server closest to where the client request for that content file is coming from.
  • the content file must be stored on that cache server and ready for downloading to the client at a time no later than the expected service time designated by the client.
  • the invention concerns a method for scheduling the distribution of a content file within a cached network environment.
  • the method comprises the steps of: receiving a request for content to be delivered at a service time, associating the content file with a particular cache server, dynamically establishing a multicasting tree of cache servers, and delivering the requested content at the service time from the multicasting tree of cache servers.
  • Figure 1 is a schematic of a content delivery network according to one embodiment of the present invention.
  • Figure 2 is a schematic of the content delivery network of FIG. 1 showing the downloading and association structure resulting from a number of user requests for a content file according to one embodiment of the present invention considering closeness of cache servers.
  • Figure 3 is a flowchart diagram of a method of scheduling distribution and downloading of content files in a content delivery network according to one embodiment of the present invention considering closeness of cache servers.
  • Multicasting distribution can be implemented at either the transport layer or the application layer. Because there are a number of deficiencies associated with transport layer multicasting, only application layer multicasting is considered for the present invention.
  • Transport layer multicasting requires a multicasting enabled transport network. The Internet does not typically have such a transport network. Additionally, even if there is a multicasting enabled transport network available, the transmission on all the branches of a multicasting tree must be simultaneous. This may not be possible if any of the network nodes (i.e., the cache servers) on the multicasting tree do not have transport or cache capacity at any period of the multicasting session.
  • application layer multicasting can be more flexible on the transmission schedule from node to node on a multicasting tree.
  • application layer multicasting For a downloading service that has many downloading requests at different expected service times, the application layer multicasting could be more suitable.
  • application layer multicasting is defined as a store/forward action at each network node on the multicasting tree. Store implies caching on intermediate nodes and forward means transmission to multiple ports at same or different time.
  • System 100 comprises content server S, and a CDN comprising cache server A, cache server B, and cache server C. While a specific structure is illustrated for CDN with only three cache servers, the present invention is not limited to any particular network structure or configuration. Regardless of the structure of a CDN network (flat or hierarchical), a multicasting tree can be established for content file distribution according to the present invention. So long as requests for the same content file do not have the same expected service time, the downloading and association structure (i.e., the multicasting tree structure) will depend not only on the distances between source and destinations but also on the gaps between different expected service times.
  • Fig. 2. which illustrates content delivery system 100 with data flow arrows connecting the illustrated components
  • Fig. 3 an embodiment of the method of the invention
  • clients/users Al, Bl, and CI each generate a request for the same content file.
  • Each request for the content file has an estimated service time.
  • the service time of a request is that time at which the client requests that the content file be available for downloading to the client's electronic device, be it a computer, a cell phone, or a persona] data assistant.
  • the service time is designated by clients Al, Bl, and CI when the request is made.
  • the service times for the requests generated by clients Al, Bl, and CI are 7 PM, 5 PM, and 8 PM respectively.
  • the service times having a chronological order of B1-A1-C1 there is no limitation on the order in which the requests may have " been generated by the clients and/or received by the system 100.
  • requests Al, Bl, and CI are associated to cache server, A, B, C, respectively, completing step 310.
  • the associations of the requests Al, Bl, and CI with cache server A, B, and C are designated by lines 1, 2, and 3 respectively in FIG. 2.
  • the association decision is made by the CDN through either static hierarchical structure or dynamic request-routing process.
  • the choice of which cache server each request is associated with is determined " by the closeness of the cache server to the client.
  • a request is associated with the cache server that is closest to the client making the request for the content file.
  • closeness can be determined using physical locality and/or network locality taking into consideration bandwidth cost and/or congestion.
  • Technology used to perform such associations is known as request-routing technology.
  • the determination of which cache server to associate a request with can be learned statically, i.e., there is a pre- established hierarchical structure as in multi-proxy servers, or dynamically.
  • the client can designate a specific cache server to which his/her request should be associated with, such as with remote site downloading function at hotspots.
  • extended request-routing technology should be used. E. In this case, even when the requested content file is currently not available on a cache server, the request-routing can still associate the request to that cache server because the association is meant to deliver the content file to that cache server at a future time.
  • Requests Al, Bl and CI are sent to the content server S in the order of Bl, CI and Al.
  • the multicasting tree will initially have only one node, content server S, Because request Bl is the first request sent to content server S, step 320 will be performed for cache server B first.
  • the determination is made whether the cache server B is on the multicasting tree. If the answer is NO (which it is in this case), the system adds node B to the multicasting tree and continues to step 330.
  • the system checks for the existence of a closest upstream cache server and, in this case, finds upstream cache server C. This is done through either static hierarchy or request-routing. Request routing is illustrated.
  • Request Bl is then associated to the cache server C, completing step 340. The association of request Bl to cache server C is shown in FIG 2 as line 4.
  • Step 320 is then performed for cache server C. According to step 320, it is then determined whether cache server C is on the multicasting tree. If the answer is NO, which it is in this case, the system adds node C to the multicasting tree. The cache server C then finds its closest upstream node, which is the content server S completing step 330. The request CI is then associated to the content server S in step 340, which is shown in FIG 2 as line 5.
  • Step 320 is then performed for content server S.
  • the answer is YES and it goes to step 350. Since the current server is the content server, the answer at 350 is NO and it goes to process the next request.
  • request CI is generated in step 300 (subsequent to request Bl), and associated with the cache server C in step 310. Since the node C was already added to the multicasting tree in performing the process for request Bl, the answer at step 320 is YES and process continues to step 350. Since the service time of CI (8 PM) is later than the service time of Bl (5 PM), the answer to step 350 is NO. The process then starts over and processes the next request.
  • request Al which was received subsequent to request CI, request Al is generated in step 300 and associated with the cache server A in step 310.
  • step 320 the determination is made whether the cache server A is on the multicasting tree. In this case, the answer is NO and the process continues to step 330.
  • node A is first added to the multicasting tree and then cache server A finds its upstream cache server B, completing step 330.
  • Request Al is then associated to the cache server ?B in step 340. This association is shown in FIG. 2 as line 6. Since node B is already on the multicasting tree and the service time of Al is later than service time on node B, the - answer to step 350 is NO. The process then begins over and processes the next request.
  • the algorithm used in determining the distance between cache servers is not only based on the geographical distance but also other factors, such as cache capacity, load balance of network links, etc. For example, node A may find node C is its upstream node because the cost of caching the content from 5 PM to 7 PM at node B may be larger than the cost difference between link 7 and link 6.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Computer Security & Cryptography (AREA)
  • Information Transfer Between Computers (AREA)

Abstract

A technique for scheduling distribution of a content file within a content delivery network and a content delivery network adapted to perform the same are disclosed. The technique comprise scheduling distribution of the content file based on delivery location, service time of content requests, and cache server hierarchy. Preferably, a multicasting tree for delivering each content file is dynamically established in the content delivery network based on location and service time considerations.

Description

CACHE SERVER NETWORK AND METHOD OF SCHEDULING THE DISTRIBUTION OF CONTENT FILES
Field of the Invention
[0001] The present invention relates generally to the field of data communication and cache server networks, and specifically to systems and methods for scheduling multicasting distribution of content files within content delivery networks.
Background of the Invention
[0002] For large size content, such as movies, content clients usually can tolerate some delay in exchange for better quality. A client may rather watch a high quality downloaded video at a future scheduled time than view a low quality streaming video instantaneously. For example, a mobile user can order a video in advance while he/she is in a cellular mobile network and download it at a later time while he/she is in a hotspot wireless LAN. This is known as a remote site downloading. As such, the mobile user can enjoy a high quality content at low cost.
[0003] In recent years, the use of content delivery network (CDN) technology has spread to the Internet to improve the downloading of web pages. A content delivery network (CDN) consists of cache servers at different geographic locations, i.e., network nodes with storage and transport capabilities. The basic premise of CDN technology is that the link between the cache server and the client has low cost and high bandwidth. If at the time a client requests a content file, the content file is stored in the cache of a nearby cache server, the downloading will be fast. Otherwise, the client may experience a longer delay. Thus, it is preferable for a client to download the content file from the most nearby cache server. The technology of finding the nearby cache server for a client is called request-routing. It is a procedure of redirecting a content request to a closer cache server. For example, modifying a URL from the original URL to a URL prefixed by the cache server. In another application of us, an extension of conventional request-routing with content timing is provided to redirect a request to a closer cache server based on the future availability of the requested content on the cache server.
[0004] Typically, a client can tolerate a delay for a large size content file up to the expected service time which the client designates as the time he/she wishes to retrieve the content file. Thus, even if the requested content file is not currently stored in a cache server close to the client, so long as the downloading system transfers the content file to the cache server prior to the expected service time, the client will not experience a delay. It is a goal of the industry to reduce these delays by properly scheduling the downloading of requested content files to the appropriate cache server for client retrieval.
[0005] Multicasting content delivery can be requested at different cache servers.
Due to the availability of advanced content request information before content downloading, it is possible to optimize content distribution in a CDN through multicasting technologies. Typically, a downloading service requires a CDN to provide distribution of a content file to the cache server closest to where the client request for that content file is coming from. The content file must be stored on that cache server and ready for downloading to the client at a time no later than the expected service time designated by the client. As such, a need exists for improved systems and methods for scheduling the distribution of a content file to cache servers associated with requests for that content file.
Disclosure of the Invention
[0007] Briefly, the invention concerns a method for scheduling the distribution of a content file within a cached network environment. The method comprises the steps of: receiving a request for content to be delivered at a service time, associating the content file with a particular cache server, dynamically establishing a multicasting tree of cache servers, and delivering the requested content at the service time from the multicasting tree of cache servers.
Brief Description of the Drawings
[0008] Figure 1 is a schematic of a content delivery network according to one embodiment of the present invention. [0009] Figure 2 is a schematic of the content delivery network of FIG. 1 showing the downloading and association structure resulting from a number of user requests for a content file according to one embodiment of the present invention considering closeness of cache servers.
[00010] Figure 3 is a flowchart diagram of a method of scheduling distribution and downloading of content files in a content delivery network according to one embodiment of the present invention considering closeness of cache servers.
Modes for Carrying Out the Invention
[00011] Multicasting distribution can be implemented at either the transport layer or the application layer. Because there are a number of deficiencies associated with transport layer multicasting, only application layer multicasting is considered for the present invention. Transport layer multicasting requires a multicasting enabled transport network. The Internet does not typically have such a transport network. Additionally, even if there is a multicasting enabled transport network available, the transmission on all the branches of a multicasting tree must be simultaneous. This may not be possible if any of the network nodes (i.e., the cache servers) on the multicasting tree do not have transport or cache capacity at any period of the multicasting session. However, application layer multicasting can be more flexible on the transmission schedule from node to node on a multicasting tree. For a downloading service that has many downloading requests at different expected service times, the application layer multicasting could be more suitable. As used herein, application layer multicasting is defined as a store/forward action at each network node on the multicasting tree. Store implies caching on intermediate nodes and forward means transmission to multiple ports at same or different time.
[00012] Referring now to FIG. 1, an embodiment of a content delivery system of the invention 100 is illustrated. System 100 comprises content server S, and a CDN comprising cache server A, cache server B, and cache server C. While a specific structure is illustrated for CDN with only three cache servers, the present invention is not limited to any particular network structure or configuration. Regardless of the structure of a CDN network (flat or hierarchical), a multicasting tree can be established for content file distribution according to the present invention. So long as requests for the same content file do not have the same expected service time, the downloading and association structure (i.e., the multicasting tree structure) will depend not only on the distances between source and destinations but also on the gaps between different expected service times.
[00013] Referring now to Fig. 2. which illustrates content delivery system 100 with data flow arrows connecting the illustrated components, and Fig. 3, an embodiment of the method of the invention, at step 300, clients/users Al, Bl, and CI each generate a request for the same content file. Each request for the content file has an estimated service time. As used herein, the service time of a request is that time at which the client requests that the content file be available for downloading to the client's electronic device, be it a computer, a cell phone, or a persona] data assistant. The service time is designated by clients Al, Bl, and CI when the request is made. In the example, the service times for the requests generated by clients Al, Bl, and CI are 7 PM, 5 PM, and 8 PM respectively. Despite the service times having a chronological order of B1-A1-C1, there is no limitation on the order in which the requests may have "been generated by the clients and/or received by the system 100.
[00014] The requests generated by clients Al, Bl, and CI (which for simplification of understanding will "be called requests Al, Bl, and CI) are associated to cache server, A, B, C, respectively, completing step 310. The associations of the requests Al, Bl, and CI with cache server A, B, and C are designated by lines 1, 2, and 3 respectively in FIG. 2. The association decision is made by the CDN through either static hierarchical structure or dynamic request-routing process. The choice of which cache server each request is associated with is determined "by the closeness of the cache server to the client. Preferably, a request is associated with the cache server that is closest to the client making the request for the content file. As used herein, closeness can be determined using physical locality and/or network locality taking into consideration bandwidth cost and/or congestion. Technology used to perform such associations is known as request-routing technology. The determination of which cache server to associate a request with can be learned statically, i.e., there is a pre- established hierarchical structure as in multi-proxy servers, or dynamically. Alternatively, the client can designate a specific cache server to which his/her request should be associated with, such as with remote site downloading function at hotspots. [00015] When the association of a request to a cache server is dynamically determined by request-routing technology, extended request-routing technology should be used. E. In this case, even when the requested content file is currently not available on a cache server, the request-routing can still associate the request to that cache server because the association is meant to deliver the content file to that cache server at a future time.
[00016] Requests Al, Bl and CI are sent to the content server S in the order of Bl, CI and Al. The multicasting tree will initially have only one node, content server S, Because request Bl is the first request sent to content server S, step 320 will be performed for cache server B first. At step 320, the determination is made whether the cache server B is on the multicasting tree. If the answer is NO (which it is in this case), the system adds node B to the multicasting tree and continues to step 330. At step 330, the system checks for the existence of a closest upstream cache server and, in this case, finds upstream cache server C. This is done through either static hierarchy or request-routing. Request routing is illustrated. Request Bl is then associated to the cache server C, completing step 340. The association of request Bl to cache server C is shown in FIG 2 as line 4.
[00017] Step 320 is then performed for cache server C. According to step 320, it is then determined whether cache server C is on the multicasting tree. If the answer is NO, which it is in this case, the system adds node C to the multicasting tree. The cache server C then finds its closest upstream node, which is the content server S completing step 330. The request CI is then associated to the content server S in step 340, which is shown in FIG 2 as line 5.
[00018] Step 320 is then performed for content server S. According to step 320, since the content server S is on the multicasting tree, the answer is YES and it goes to step 350. Since the current server is the content server, the answer at 350 is NO and it goes to process the next request.
[00019] Turning now to request CI, request CI is generated in step 300 (subsequent to request Bl), and associated with the cache server C in step 310. Since the node C was already added to the multicasting tree in performing the process for request Bl, the answer at step 320 is YES and process continues to step 350. Since the service time of CI (8 PM) is later than the service time of Bl (5 PM), the answer to step 350 is NO. The process then starts over and processes the next request.
[0002O] Turning now to request Al, which was received subsequent to request CI, request Al is generated in step 300 and associated with the cache server A in step 310. According to step 320 the determination is made whether the cache server A is on the multicasting tree. In this case, the answer is NO and the process continues to step 330. At this point, node A is first added to the multicasting tree and then cache server A finds its upstream cache server B, completing step 330. Request Al is then associated to the cache server ?B in step 340. This association is shown in FIG. 2 as line 6. Since node B is already on the multicasting tree and the service time of Al is later than service time on node B, the - answer to step 350 is NO. The process then begins over and processes the next request.
[00021] The algorithm used in determining the distance between cache servers is not only based on the geographical distance but also other factors, such as cache capacity, load balance of network links, etc. For example, node A may find node C is its upstream node because the cost of caching the content from 5 PM to 7 PM at node B may be larger than the cost difference between link 7 and link 6.
[00022] While the invention has been described and illustrated in sufficient detail that those skilled in this art can readily make and use it, various alternatives, modifications, and improvements should become readily apparent without departing from the spirit and scope of the invention.

Claims

1. A method for processing requests for content files from a content delivery network system comprising: receiving a request for content to be delivered at a service time, associating the content file with a particular cache server, dynamically establishing a multicasting tree of cache servers, and delivering the requested content at the service time from the multicasting tree of cache servers.
2. The method according to claim 1 wherein the associating step further comprises the step of associating the request with a closest cache server.
3. The method according to claim 1 wherein the dynamically establishing step further comprises the step of adding a cache server associated with a request if the cache server is not already associated with the multicasting tree.
4. The method according to claim 1 wherein the associating step further comprises the step of associating the request with a closest cache server if the request has an earlier service time than previous requests.
5. A method for processing requests for content files from a content delivery network system comprising the steps of:
(a) receiving a first request for a content file having a first service time; (b) associating the first request with a cache server for retrieval;
(c) determining whether the associated cache server is on a multicasting tree rooted at a content server that is an origin of the content file;
(d) upon determining that the associated cache server is not on the multicasting tree, adding the associated cache server to the multicasting tree, finding an upstream cache server towards the content server, associating the first request with the upstream cache server found so that the upstream cache server becomes the associated cache server, and repeating step (c) until the content server is reached and the first request is associated with the content server, wherein upon the first request being associated with content server, processing a next request for the content file beginning with step (a);
(e) upon determining that the associated cache server is on the multicasting tree, determining whether the first service time is earlier than all service times of requests for the content file that already exist on the associated cache server;
(f) upon determining that the first service time is not earlier than all other service times of requests that already exist on the associated cache server, associating the first request with the cache server and processing the next request for the content file beginning with step (a); and
(g) upon determining that the first service time is earlier than all other service times of requests that already exist on the associated cache server , associating the first request with the cache server that was determined to be the upstream cache server toward the content server the multicasting tree so that this cache server becomes the associated cache server and returning to step (c) until the first request is associated with the content server, wherein upon the first request being associated with the content server, processing the next request for the content file beginning with step (a).
6. The method of claim 5 wherein the step of finding an upstream cache server comprises finding a closest upstream cache server using request routing procedures.
7. The method of claim 6 wherein closeness is determined using at least one factor selected from the group consisting of geographical distance, cache occupancy , and load balance of network links.
8. The method of claim 5 wherein the step of finding an upstream cache server comprises finding the upstream cache server using a hierarchical relationship.
9. A content delivery network system for processing requests for content files comprising a content server and a CDN network with at least one cache server adapted to (a) receive a first request for a content file from a client, (b) associate the first request with a cache server for retrieval, (c) determine if the associated cache server is on a multicasting tree and if not, associate the cache server to the multicasting tree.
10. The system of claim 9 having means to determine whether the first service time is earlier than all other service times of requests that already exist on the associated cache server on the multicasting tree, and if it is not, associate the first request with the cache server which is on the tree, and if it is, find an upstream cache server and associate the first request to the upstream cache server until either the first service time is not earlier than all other service times of requests that already exist on the associated cache server on the multicasting tree or the first request is associated to the content server.
11. The system of claim 9 having means for associating the first request with the cache server that was determined to be on the multicasting tree if the first service time is not earlier than all other service times of requests that already exist on the associated cache server on the tree.
12. The system of claim 9 having means for finding a closest upstream cache server by means of request routing.
13. The system of claim 12 having means for finding a closest upstream cache server using at least one factor selected from the group consisting of geographical distance, cache occupancy , and load balance of network links.
14. The system of claim 9 having means for finding an upstream cache server using a hierarchical relationship.
15. The system of claim 9 further including a content delivery network broker which is adapted to provide information for a request routing procedure whose result is to be used by the content server, and the information is regarding the availability of the requested content file on one or more cache servers in a content delivery network.
16. The system of claim 9 further including a content delivery network broker which is adapted to provide information for a request routing procedure whose result is to be used by the content server, and the information is regarding the availability of the requested content file on one or more cache servers in a content delivery network or to schedule the future availability of the content file at one or more cache servers 13.
17. The system of claim 9 further including one or more cache servers and a content delivery network broker and means for the broker, cache servers, and/or content server to determine the future time period and the server from which the client can request the file.
PCT/US2004/007652 2004-03-12 2004-03-12 Cache server network and method of scheduling the distribution of content files WO2005099223A1 (en)

Priority Applications (6)

Application Number Priority Date Filing Date Title
CN200480042399.4A CN1981501A (en) 2004-03-12 2004-03-12 Method of scheduling the distribution of content files and cache server
BRPI0418629-0A BRPI0418629A (en) 2004-03-12 2004-03-12 caching server network and content file distribution programming method
US10/592,345 US20070208737A1 (en) 2004-03-12 2004-03-12 Cache Server Network And Method Of Scheduling The Distribution Of Content Files Within The Same
EP04720439A EP1723763A1 (en) 2004-03-12 2004-03-12 Cache server network and method of scheduling the distribution of content files
PCT/US2004/007652 WO2005099223A1 (en) 2004-03-12 2004-03-12 Cache server network and method of scheduling the distribution of content files
JP2007502777A JP2007529073A (en) 2004-03-12 2004-03-12 Cache server network and content file delivery scheduling method

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/US2004/007652 WO2005099223A1 (en) 2004-03-12 2004-03-12 Cache server network and method of scheduling the distribution of content files

Publications (1)

Publication Number Publication Date
WO2005099223A1 true WO2005099223A1 (en) 2005-10-20

Family

ID=34957434

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/US2004/007652 WO2005099223A1 (en) 2004-03-12 2004-03-12 Cache server network and method of scheduling the distribution of content files

Country Status (6)

Country Link
US (1) US20070208737A1 (en)
EP (1) EP1723763A1 (en)
JP (1) JP2007529073A (en)
CN (1) CN1981501A (en)
BR (1) BRPI0418629A (en)
WO (1) WO2005099223A1 (en)

Cited By (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2008138376A1 (en) * 2007-05-14 2008-11-20 Nec Europe, Ltd. Method and system for delivering media data to a user's mobile device
KR100923954B1 (en) 2007-11-22 2009-10-29 삼성네트웍스 주식회사 Apparatus and Method for Supporting Content Delivery Network Service based on Peer-to-Peer
WO2010140935A1 (en) * 2009-06-03 2010-12-09 Telefonaktiebolaget L M Ericsson (Publ) Method and node for finding content in a content distribution network, and method for creating a virtual representation of a content distribution network
WO2012075954A1 (en) * 2010-12-10 2012-06-14 华为技术有限公司 Content acquisition method and redirection node

Families Citing this family (109)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20060206586A1 (en) * 2005-03-09 2006-09-14 Yibei Ling Method, apparatus and system for a location-based uniform resource locator
US7376792B2 (en) * 2005-08-17 2008-05-20 International Business Machines Corporation Variable cache data retention system
US10387919B1 (en) * 2006-06-30 2019-08-20 Google Llc Accelerated content delivery in bandwidth-constrained networks
CN101512935B (en) * 2006-07-27 2013-10-30 艾利森电话股份有限公司 Layered broadcast transmission through multiple transmitters
US9112873B2 (en) * 2007-04-10 2015-08-18 Apertio Limited Alias hiding in network data repositories
US8782085B2 (en) * 2007-04-10 2014-07-15 Apertio Limited Variant entries in network data repositories
US7991910B2 (en) 2008-11-17 2011-08-02 Amazon Technologies, Inc. Updating routing information based on client location
US8028090B2 (en) 2008-11-17 2011-09-27 Amazon Technologies, Inc. Request routing utilizing client location information
US7697557B2 (en) * 2007-12-26 2010-04-13 Alcatel Lucent Predictive caching content distribution network
US8447831B1 (en) 2008-03-31 2013-05-21 Amazon Technologies, Inc. Incentive driven content delivery
US8156243B2 (en) 2008-03-31 2012-04-10 Amazon Technologies, Inc. Request routing
US8321568B2 (en) 2008-03-31 2012-11-27 Amazon Technologies, Inc. Content management
US8601090B1 (en) 2008-03-31 2013-12-03 Amazon Technologies, Inc. Network resource identification
US7970820B1 (en) * 2008-03-31 2011-06-28 Amazon Technologies, Inc. Locality based content distribution
US8533293B1 (en) 2008-03-31 2013-09-10 Amazon Technologies, Inc. Client side cache management
US8606996B2 (en) 2008-03-31 2013-12-10 Amazon Technologies, Inc. Cache optimization
US7962597B2 (en) * 2008-03-31 2011-06-14 Amazon Technologies, Inc. Request routing based on class
US7925782B2 (en) * 2008-06-30 2011-04-12 Amazon Technologies, Inc. Request routing using network computing components
US9407681B1 (en) 2010-09-28 2016-08-02 Amazon Technologies, Inc. Latency measurement in resource requests
US9912740B2 (en) 2008-06-30 2018-03-06 Amazon Technologies, Inc. Latency measurement in resource requests
US8464303B2 (en) * 2008-09-18 2013-06-11 Alcatel Lucent System and method for determining a cache arrangement
US8521880B1 (en) 2008-11-17 2013-08-27 Amazon Technologies, Inc. Managing content delivery network service providers
US8060616B1 (en) 2008-11-17 2011-11-15 Amazon Technologies, Inc. Managing CDN registration by a storage provider
US8065417B1 (en) 2008-11-17 2011-11-22 Amazon Technologies, Inc. Service provider registration by a content broker
US8122098B1 (en) 2008-11-17 2012-02-21 Amazon Technologies, Inc. Managing content delivery network service providers by a content broker
US8732309B1 (en) 2008-11-17 2014-05-20 Amazon Technologies, Inc. Request routing utilizing cost information
US8073940B1 (en) 2008-11-17 2011-12-06 Amazon Technologies, Inc. Managing content delivery network service providers
US8688837B1 (en) 2009-03-27 2014-04-01 Amazon Technologies, Inc. Dynamically translating resource identifiers for request routing using popularity information
US8756341B1 (en) 2009-03-27 2014-06-17 Amazon Technologies, Inc. Request routing utilizing popularity information
US8412823B1 (en) 2009-03-27 2013-04-02 Amazon Technologies, Inc. Managing tracking information entries in resource cache components
US8521851B1 (en) 2009-03-27 2013-08-27 Amazon Technologies, Inc. DNS query processing using resource identifiers specifying an application broker
US8782236B1 (en) 2009-06-16 2014-07-15 Amazon Technologies, Inc. Managing resources using resource expiration data
US8397073B1 (en) 2009-09-04 2013-03-12 Amazon Technologies, Inc. Managing secure content in a content delivery network
US8433771B1 (en) 2009-10-02 2013-04-30 Amazon Technologies, Inc. Distribution network with forward resource propagation
CN102045656A (en) * 2009-10-23 2011-05-04 清华大学 Method for adding time tags in communication service
US9495338B1 (en) 2010-01-28 2016-11-15 Amazon Technologies, Inc. Content distribution network
US8756272B1 (en) 2010-08-26 2014-06-17 Amazon Technologies, Inc. Processing encoded content
US8930513B1 (en) 2010-09-28 2015-01-06 Amazon Technologies, Inc. Latency measurement in resource requests
US9712484B1 (en) 2010-09-28 2017-07-18 Amazon Technologies, Inc. Managing request routing information utilizing client identifiers
US8938526B1 (en) 2010-09-28 2015-01-20 Amazon Technologies, Inc. Request routing management based on network components
US9003035B1 (en) 2010-09-28 2015-04-07 Amazon Technologies, Inc. Point of presence management in request routing
US10097398B1 (en) 2010-09-28 2018-10-09 Amazon Technologies, Inc. Point of presence management in request routing
US8468247B1 (en) 2010-09-28 2013-06-18 Amazon Technologies, Inc. Point of presence management in request routing
US8577992B1 (en) 2010-09-28 2013-11-05 Amazon Technologies, Inc. Request routing management based on network components
US8924528B1 (en) 2010-09-28 2014-12-30 Amazon Technologies, Inc. Latency measurement in resource requests
US10958501B1 (en) 2010-09-28 2021-03-23 Amazon Technologies, Inc. Request routing information based on client IP groupings
US8819283B2 (en) 2010-09-28 2014-08-26 Amazon Technologies, Inc. Request routing in a networked environment
US8452874B2 (en) 2010-11-22 2013-05-28 Amazon Technologies, Inc. Request routing processing
US8626950B1 (en) 2010-12-03 2014-01-07 Amazon Technologies, Inc. Request routing processing
US9391949B1 (en) 2010-12-03 2016-07-12 Amazon Technologies, Inc. Request routing processing
US10467042B1 (en) 2011-04-27 2019-11-05 Amazon Technologies, Inc. Optimized deployment based upon customer locality
CN102891869B (en) * 2011-07-20 2015-07-15 郑州威科姆科技股份有限公司 CDN (Content Delivery Network) and content distribution and scheduling method
CN102413069B (en) * 2011-11-23 2014-07-16 中兴通讯股份有限公司 Method and system for downloading in multicast way in ubiquitous network
US8904009B1 (en) 2012-02-10 2014-12-02 Amazon Technologies, Inc. Dynamic content delivery
US10021179B1 (en) 2012-02-21 2018-07-10 Amazon Technologies, Inc. Local resource delivery network
US9083743B1 (en) 2012-03-21 2015-07-14 Amazon Technologies, Inc. Managing request routing information utilizing performance information
US10623408B1 (en) 2012-04-02 2020-04-14 Amazon Technologies, Inc. Context sensitive object management
CN102857547B (en) * 2012-04-12 2016-03-30 华为技术有限公司 The method and apparatus of distributed caching
US9154551B1 (en) 2012-06-11 2015-10-06 Amazon Technologies, Inc. Processing DNS queries to identify pre-processing information
US9525659B1 (en) 2012-09-04 2016-12-20 Amazon Technologies, Inc. Request routing utilizing point of presence load information
US9712854B2 (en) * 2012-09-06 2017-07-18 Alcatel Lucent Cost-aware cloud-based content delivery
US9323577B2 (en) 2012-09-20 2016-04-26 Amazon Technologies, Inc. Automated profiling of resource usage
US9135048B2 (en) 2012-09-20 2015-09-15 Amazon Technologies, Inc. Automated profiling of resource usage
US10205698B1 (en) 2012-12-19 2019-02-12 Amazon Technologies, Inc. Source-dependent address resolution
US10027586B2 (en) * 2013-03-15 2018-07-17 Star2Star Communications, LLC Network address family translation method and system
US9294391B1 (en) 2013-06-04 2016-03-22 Amazon Technologies, Inc. Managing network computing components utilizing request routing
US10075741B2 (en) * 2013-07-03 2018-09-11 Avago Technologies General Ip (Singapore) Pte. Ltd. System and control protocol of layered local caching for adaptive bit rate services
US10110541B2 (en) * 2013-10-17 2018-10-23 International Business Machines Corporation Optimization of posting in social networks using content delivery preferences comprising hashtags that correspond to geography and a content type associated with a desired time window
US10033627B1 (en) 2014-12-18 2018-07-24 Amazon Technologies, Inc. Routing mode and point-of-presence selection service
US10091096B1 (en) 2014-12-18 2018-10-02 Amazon Technologies, Inc. Routing mode and point-of-presence selection service
US10097448B1 (en) 2014-12-18 2018-10-09 Amazon Technologies, Inc. Routing mode and point-of-presence selection service
US10425494B2 (en) 2014-12-19 2019-09-24 Smugmug, Inc. File size generation application with file storage integration
US10225326B1 (en) 2015-03-23 2019-03-05 Amazon Technologies, Inc. Point of presence based data uploading
US9887932B1 (en) 2015-03-30 2018-02-06 Amazon Technologies, Inc. Traffic surge management for points of presence
US9819567B1 (en) 2015-03-30 2017-11-14 Amazon Technologies, Inc. Traffic surge management for points of presence
US9887931B1 (en) 2015-03-30 2018-02-06 Amazon Technologies, Inc. Traffic surge management for points of presence
CN106155575A (en) * 2015-04-17 2016-11-23 伊姆西公司 Method and apparatus for the cache of extension storage system
US9832141B1 (en) 2015-05-13 2017-11-28 Amazon Technologies, Inc. Routing based request correlation
US10616179B1 (en) 2015-06-25 2020-04-07 Amazon Technologies, Inc. Selective routing of domain name system (DNS) requests
US10097566B1 (en) 2015-07-31 2018-10-09 Amazon Technologies, Inc. Identifying targets of network attacks
US9794281B1 (en) 2015-09-24 2017-10-17 Amazon Technologies, Inc. Identifying sources of network attacks
US9774619B1 (en) 2015-09-24 2017-09-26 Amazon Technologies, Inc. Mitigating network attacks
US9742795B1 (en) 2015-09-24 2017-08-22 Amazon Technologies, Inc. Mitigating network attacks
US10270878B1 (en) 2015-11-10 2019-04-23 Amazon Technologies, Inc. Routing for origin-facing points of presence
US10257307B1 (en) 2015-12-11 2019-04-09 Amazon Technologies, Inc. Reserved cache space in content delivery networks
US10049051B1 (en) 2015-12-11 2018-08-14 Amazon Technologies, Inc. Reserved cache space in content delivery networks
US20170171627A1 (en) * 2015-12-15 2017-06-15 Le Holdings(Beijing)Co., Ltd. Method and electronic device for pushing a video over a cdn
US10348639B2 (en) 2015-12-18 2019-07-09 Amazon Technologies, Inc. Use of virtual endpoints to improve data transmission rates
US10871878B1 (en) * 2015-12-29 2020-12-22 Palantir Technologies Inc. System log analysis and object user interaction correlation system
US10412168B2 (en) * 2016-02-17 2019-09-10 Latticework, Inc. Implementing a storage system using a personal user device and a data distribution device
US10462539B2 (en) * 2016-05-23 2019-10-29 Verizon Patent And Licensing Inc. Managing transitions between a local area network and a wide area network during media content playback
US10075551B1 (en) 2016-06-06 2018-09-11 Amazon Technologies, Inc. Request management for hierarchical cache
US10110694B1 (en) 2016-06-29 2018-10-23 Amazon Technologies, Inc. Adaptive transfer rate for retrieving content from a server
US9992086B1 (en) 2016-08-23 2018-06-05 Amazon Technologies, Inc. External health checking of virtual private cloud network environments
US10033691B1 (en) 2016-08-24 2018-07-24 Amazon Technologies, Inc. Adaptive resolution of domain name requests in virtual private cloud network environments
US10469513B2 (en) 2016-10-05 2019-11-05 Amazon Technologies, Inc. Encrypted network addresses
US10831549B1 (en) 2016-12-27 2020-11-10 Amazon Technologies, Inc. Multi-region request-driven code execution system
US10372499B1 (en) 2016-12-27 2019-08-06 Amazon Technologies, Inc. Efficient region selection system for executing request-driven code
US10263951B2 (en) * 2017-01-09 2019-04-16 Star2Star Communications, LLC Network address family translation method and system
US10938884B1 (en) 2017-01-30 2021-03-02 Amazon Technologies, Inc. Origin server cloaking using virtual private cloud network environments
US10503613B1 (en) 2017-04-21 2019-12-10 Amazon Technologies, Inc. Efficient serving of resources during server unavailability
US11075987B1 (en) 2017-06-12 2021-07-27 Amazon Technologies, Inc. Load estimating content delivery network
US10447648B2 (en) 2017-06-19 2019-10-15 Amazon Technologies, Inc. Assignment of a POP to a DNS resolver based on volume of communications over a link between client devices and the POP
US10742593B1 (en) 2017-09-25 2020-08-11 Amazon Technologies, Inc. Hybrid content request routing system
FR3075541A1 (en) * 2017-12-20 2019-06-21 Orange METHOD FOR DISTRIBUTING CONTENT IN A CONTENT DISTRIBUTION NETWORK, ENTITY OF ORIGIN AND CORRESPONDING DISTRIBUTION ENTITY
US10592578B1 (en) 2018-03-07 2020-03-17 Amazon Technologies, Inc. Predictive content push-enabled content delivery network
US10862852B1 (en) 2018-11-16 2020-12-08 Amazon Technologies, Inc. Resolution of domain name requests in heterogeneous network environments
US11025747B1 (en) 2018-12-12 2021-06-01 Amazon Technologies, Inc. Content request pattern-based routing system
US11064249B2 (en) 2019-02-26 2021-07-13 At&T Intellectual Property I, L.P. System and method for pushing scheduled content to optimize network bandwidth

Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20030105809A1 (en) * 2001-11-30 2003-06-05 Fujitsu Limited Method and system for distributing digital content, and server and terminal stations therefor
GB2385683A (en) * 2002-02-22 2003-08-27 Thirdspace Living Ltd Distribution system with content replication

Family Cites Families (15)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JPH10222411A (en) * 1997-02-05 1998-08-21 Nippon Telegr & Teleph Corp <Ntt> Proxy cache server control method and proxy cache server
US6594682B2 (en) * 1997-10-28 2003-07-15 Microsoft Corporation Client-side system for scheduling delivery of web content and locally managing the web content
US6108703A (en) * 1998-07-14 2000-08-22 Massachusetts Institute Of Technology Global hosting system
JP2001229081A (en) * 2000-02-17 2001-08-24 Hitachi Ltd Data transfer system
US6970939B2 (en) * 2000-10-26 2005-11-29 Intel Corporation Method and apparatus for large payload distribution in a network
US6751673B2 (en) * 2001-01-03 2004-06-15 Akamai Technologies, Inc. Streaming media subscription mechanism for a content delivery network
US7240105B2 (en) * 2001-01-26 2007-07-03 International Business Machines Corporation Distributed multicast caching technique
WO2003015377A1 (en) * 2001-08-04 2003-02-20 Kontiki, Inc. Method and apparatus for facilitating distributed delivery of content across a computer network
JP2003085070A (en) * 2001-09-11 2003-03-20 Oki Electric Ind Co Ltd Content delivery system, content copying method and multicast method
EP1446909A4 (en) * 2001-10-31 2005-05-04 Akimbo Systems Inc Data transmission process and system
EP1466259A4 (en) * 2001-12-13 2010-08-18 Thomson Licensing Apparatus and methods for information transfer using a cached server
US6954456B2 (en) * 2001-12-14 2005-10-11 At & T Corp. Method for content-aware redirection and content renaming
JP2003234776A (en) * 2002-02-13 2003-08-22 Nippon Telegr & Teleph Corp <Ntt> Multicast communication system, method, method program and apparatus communication node therefor, and recording medium
US7395355B2 (en) * 2002-07-11 2008-07-01 Akamai Technologies, Inc. Method for caching and delivery of compressed content in a content delivery network
WO2005020541A1 (en) * 2003-08-13 2005-03-03 Thomson Licensing Method and device for securing content delivery over a communication network via content keys

Patent Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20030105809A1 (en) * 2001-11-30 2003-06-05 Fujitsu Limited Method and system for distributing digital content, and server and terminal stations therefor
GB2385683A (en) * 2002-02-22 2003-08-27 Thirdspace Living Ltd Distribution system with content replication

Non-Patent Citations (2)

* Cited by examiner, † Cited by third party
Title
ATHENA VAKALI, GEORGE PALLIS: "Content Delivery Networks: Status and Trends", IEEE INTERNET COMPUTING, vol. 7, no. 6, December 2003 (2003-12-01), pages 68 - 74, XP002308155, Retrieved from the Internet <URL:http://ieeexplore.ieee.org/iel5/4236/27995/01250586.pdf> *
DAN LI, ARUN DESAI, ZHENG YANG, KENNETH MUELLER, STEPHEN MORRIS, DMITRY STAVISKY: "Multicast Cloud with Integrated Multicast and Univcast Content Distribution Routing", EIGHTH INTERNATIONAL WORKSHOP ON WEB CONTENT CACHING AND DISTRIBUTION, 29 September 2003 (2003-09-29), HAWTHORNE, NY USA, pages 1 - 6, XP002308154, Retrieved from the Internet <URL:http://2003.iwcw.org/papers/li.pdf> *

Cited By (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2008138376A1 (en) * 2007-05-14 2008-11-20 Nec Europe, Ltd. Method and system for delivering media data to a user's mobile device
KR101088326B1 (en) 2007-05-14 2011-11-30 엔이씨 유럽 리미티드 Method and system for delivering media data to a user's mobile device
KR100923954B1 (en) 2007-11-22 2009-10-29 삼성네트웍스 주식회사 Apparatus and Method for Supporting Content Delivery Network Service based on Peer-to-Peer
WO2010140935A1 (en) * 2009-06-03 2010-12-09 Telefonaktiebolaget L M Ericsson (Publ) Method and node for finding content in a content distribution network, and method for creating a virtual representation of a content distribution network
US8665757B2 (en) 2009-06-03 2014-03-04 Telefonaktiebolaget Lm Ericsson (Publ) Method and node for finding content in a content distribution network, and method for creating a virtual representation of a content distribution network
WO2012075954A1 (en) * 2010-12-10 2012-06-14 华为技术有限公司 Content acquisition method and redirection node

Also Published As

Publication number Publication date
JP2007529073A (en) 2007-10-18
EP1723763A1 (en) 2006-11-22
BRPI0418629A (en) 2007-05-29
CN1981501A (en) 2007-06-13
US20070208737A1 (en) 2007-09-06

Similar Documents

Publication Publication Date Title
US20070208737A1 (en) Cache Server Network And Method Of Scheduling The Distribution Of Content Files Within The Same
US11425088B2 (en) Content delivery network optimization system
EP2704402B1 (en) Method and node for distributing electronic content in a content distribution network
US6377972B1 (en) High quality streaming multimedia
EP1474751B1 (en) Managed object replication and delivery
US6892218B2 (en) Extending network services using mobile agents
EP2719133B1 (en) A generalized dual-mode data forwarding plane for information-centric network
US20130132544A1 (en) Precise geolocation for content caching in evolved packet core networks
Majeed et al. Multimedia streaming in information-centric networking: A survey and future perspectives
JP2007529072A (en) Download scheduling system and method in cache network environment
Rodriguez et al. Improving the WWW: caching or multicast?
US7373394B1 (en) Method and apparatus for multicast cloud with integrated multicast and unicast channel routing in a content distribution network
KR20040032106A (en) A system and method for reducing the time to deliver information from a communications network to a user
JP2014522518A (en) Content processing method, content processing device, and content processing system
CN103931158A (en) System and method for content and application acceleration in a wireless communications system
JP2008544690A (en) Multicast download using route information
US20120191778A1 (en) Content distribution network for supporting peer-to-peer live streaming
WO2011017976A1 (en) Method and system for media service
EP1735992A1 (en) Satellite anticipatory bandwidth acceleration
US20060005224A1 (en) Technique for cooperative distribution of video content
WO2012034414A1 (en) Method and system for processing peer to peer (p2p) services
Nguyen et al. Adaptive caching for beneficial content distribution in information-centric networking
Woo et al. Proactive neighbor pushing for enhancing provider mobility support in content-centric networking
Mishra et al. A review on content centric networking and caching strategies
Ball et al. Distributed content delivery using load-aware network coordinates

Legal Events

Date Code Title Description
AK Designated states

Kind code of ref document: A1

Designated state(s): AE AG AL AM AT AU AZ BA BB BG BR BW BY BZ CA CH CN CO CR CU CZ DE DK DM DZ EC EE EG ES FI GB GD GE GH GM HR HU ID IL IN IS JP KE KG KP KR KZ LC LK LR LS LT LU LV MA MD MG MK MN MW MX MZ NA NI NO NZ OM PG PH PL PT RO RU SC SD SE SG SK SL SY TJ TM TN TR TT TZ UA UG US UZ VC VN YU ZA ZM ZW

AL Designated countries for regional patents

Kind code of ref document: A1

Designated state(s): BW GH GM KE LS MW MZ SD SL SZ TZ UG ZM ZW AM AZ BY KG KZ MD RU TJ TM AT BE BG CH CY CZ DE DK EE ES FI FR GB GR HU IE IT LU MC NL PL PT RO SE SI SK TR BF BJ CF CG CI CM GA GN GQ GW ML MR NE SN TD TG

DPEN Request for preliminary examination filed prior to expiration of 19th month from priority date (pct application filed from 20040101)
121 Ep: the epo has been informed by wipo that ep was designated in this application
WWE Wipo information: entry into national phase

Ref document number: 2007502777

Country of ref document: JP

Ref document number: 2004720439

Country of ref document: EP

WWE Wipo information: entry into national phase

Ref document number: 10592345

Country of ref document: US

Ref document number: 2007208737

Country of ref document: US

Ref document number: 1020067018529

Country of ref document: KR

WWE Wipo information: entry into national phase

Ref document number: 200480042399.4

Country of ref document: CN

NENP Non-entry into the national phase

Ref country code: DE

WWW Wipo information: withdrawn in national office

Ref document number: DE

WWE Wipo information: entry into national phase

Ref document number: 5716/DELNP/2006

Country of ref document: IN

WWP Wipo information: published in national office

Ref document number: 2004720439

Country of ref document: EP

WWP Wipo information: published in national office

Ref document number: 1020067018529

Country of ref document: KR

ENP Entry into the national phase

Ref document number: PI0418629

Country of ref document: BR

WWP Wipo information: published in national office

Ref document number: 10592345

Country of ref document: US