US20080071859A1 - Popularity-based selective replication in content delivery network - Google Patents
Popularity-based selective replication in content delivery network Download PDFInfo
- Publication number
- US20080071859A1 US20080071859A1 US11/980,672 US98067207A US2008071859A1 US 20080071859 A1 US20080071859 A1 US 20080071859A1 US 98067207 A US98067207 A US 98067207A US 2008071859 A1 US2008071859 A1 US 2008071859A1
- Authority
- US
- United States
- Prior art keywords
- server
- requested
- edge
- popularity
- parent
- Prior art date
- Legal status (The legal status 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 status listed.)
- Abandoned
Links
Images
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/01—Protocols
- H04L67/10—Protocols in which an application is distributed across nodes in the network
- H04L67/1095—Replication or mirroring of data, e.g. scheduling or transport for data synchronisation between network nodes
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F15/00—Digital computers in general; Data processing equipment in general
- G06F15/16—Combinations of two or more digital computers each having at least an arithmetic unit, a program unit and a register, e.g. for a simultaneous processing of several programs
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F17/00—Digital computing or data processing equipment or methods, specially adapted for specific functions
-
- 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/56—Provisioning of proxy services
- H04L67/563—Data redirection of data network streams
-
- 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/56—Provisioning of proxy services
- H04L67/568—Storing data temporarily at an intermediate stage, e.g. 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/01—Protocols
- H04L67/10—Protocols in which an application is distributed across nodes in the network
- H04L67/1001—Protocols in which an application is distributed across nodes in the network for accessing one among a plurality of replicated servers
-
- 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/56—Provisioning of proxy services
- H04L67/568—Storing data temporarily at an intermediate stage, e.g. caching
- H04L67/5682—Policies or rules for updating, deleting or replacing the stored data
Definitions
- This invention relates in general to the field of computer networks. Particularly, aspects of this invention pertain to managed object replication and delivery over a network.
- FIG. 1 is a high-level block diagram of a topology of the managed object replication and delivery method and system according to embodiments of the invention
- FIG. 2 is a high-level block diagram illustrating the data flows of managed object replication and delivery method according to embodiments of the invention
- FIGS. 3 ( a ), 3 ( b ) and 3 ( c ) are a flow chart of the managed object replication and delivery method and the object purging method according to embodiments of the invention.
- FIG. 4 is a flow chart of a popularity computation according to embodiments of the invention.
- FIG. 5 is a flow chart of a replication scheme according to embodiments of the invention.
- FIG. 6 is a flow chart of a purge scheme according to embodiments of the invention.
- FIG. 7 is a block diagram of the managed object replication and delivery system according to embodiments of the invention.
- a typical content delivery network (CDN) operator deploys one or more parent servers, hosting a plurality of objects, in a network and one or more edge servers at the edge of the network to facilitate more cost-effective and efficient delivery of such objects to an end-user (client).
- End-users or client proxies that access customers' objects are called clients.
- Content provider companies, organizations, etc. that subscribe to the CDN service are referred to as customers.
- an object includes, without limitation, an audio file (such as, e.g., an MP3 (Motion Picture Experts Group-1 Layer 3) file and a RealNetworks, Inc.
- Real format file a video file (such as an MPEG file), an image file (such as, e.g., a BMP (bitmap) file or JPEG (Joint Photographic Experts) file) and any other software or data file or object.
- a video file such as an MPEG file
- an image file such as, e.g., a BMP (bitmap) file or JPEG (Joint Photographic Experts) file
- BMP bitmap
- JPEG Joint Photographic Experts
- the edge servers It is typically not feasible to store all objects on the edge servers.
- the main difficulty is due to the fact that many such objects are very large (typically on the order of 10 MB (10,000,000 bytes)—in the neighborhood of 500 MB for movies).
- the storage and rack space required to accommodate often large and sometimes rarely requested objects at every edge server can be cost prohibitive as the number of customers grows and the number of their objects increases. It may not even be possible to store a good working set of objects, for example a set of objects thought to be requested often and/or better suited to be served from an edge server, because of the size and changing demand for objects in the working set.
- One obvious solution is to pre-populate edge servers with objects for which there will likely be a significant or high demand.
- a related solution is to associate objects with two or more domains depending on popularity of the object, e.g., one domain for popular objects (served from edge servers) and another domain for less popular objects (served from parent servers).
- this requires some way to pre-determine what objects are popular and what objects are less popular statically, and build that popularity into the domain name of the object.
- pre-populating it is difficult to predict popularity and to manage assignment of domains based on such popularity determinations.
- Fetching a large object to the handling edge server through a parent path can be slow. For example, there may be limited available bandwidth from the parent server to the handling edge server, i.e., sometimes the parent path has less bandwidth than even the network path from the edge server to the client (e.g., the “last mile” in a broadband network). If a parent server uses too much bandwidth copying an object to an edge server, this can create congestion at that parent server. If storage fill bandwidth is matched to client bandwidth, it is difficult to handle a second, faster client and if fetch is done using a streaming protocol (for instance, the Real-Time Streaming Protocol (RTSP) and Real-Time Transport Protocol (RTP) standards), the quality of the copy made can be hurt due to lost packets (“thinning”).
- RTSP Real-Time Streaming Protocol
- RTP Real-Time Transport Protocol
- a parent server may fail, for example, to stream the object in time or to maintain the stream of an object at a requested bit rate thereby causing a thinned object, i.e., an object with lower quality due to lost packets in its transmission, to be populated at the edge server and delivered to subsequent clients requesting the same object.
- edge servers with the most popular objects yet somehow serve the rest from parent servers with a goal to maximize the amount of object bits served from edge servers of the network. It would also be advantageous to populate edge servers by, for example, storage fill on demand when an object is popular enough, without having to make the end-user wait for such population. Therefore, it would be advantageous to provide a method and system for managed object replication and delivery over a network.
- a method and system for managed object replication and delivery over a network redirects, directly or indirectly, a client's request for an object that is not available at a best or optimal handling edge server of the network to a parent server of the network that has the requested object. So, where the requested object is not available at the handling edge server, the client's request is redirected directly to the parent server that can provide the requested object to the client or indirectly via one or more parent servers to a parent server that can provide the requested object to the client.
- the method and system further intelligently replicates the object to the edge server if the object is popular enough. Likewise, an object is removed from an edge server when the object is no longer popular. All redirection and replication operations are preferably transparent to the end-user and do not degrade the quality of service. Other embodiments of the invention are possible and some are described hereafter.
- a request for a streaming object will be served by a handling edge server if that handling edge server has a copy of that object. Otherwise, the request is redirected, directly or indirectly, to a parent server for service of the requested streaming object to the client. If the requested streaming object is popular, the object is replicated from a parent server that has the requested streaming object to the handling edge server so that the handling edge server will serve the object from the edge of the network when the object is requested in the future. If a streaming object is no longer popular, the object is removed from an edge server.
- replication generally refers to the permanent and/or volatile storage of an object in a server, particularly an edge server and if applicable, a parent server. Accordingly, the term replication will be considered synonymous to storing, caching and copying. In typical embodiments, replication of an object will usually refer to temporary storage of the object in an edge server and/or a parent server for an undefined duration.
- the network 100 comprises one or more parent server sites 120 and one or more edge server sites 130 .
- the network also optionally has access to one or more origin server sites 110 .
- the origin server sites are typically owned and/or maintained by the network provider's customers for storing and serving one or more objects. Each customer (content provider) may have its own origin server site.
- one or more clients 140 access the network to request one or more objects.
- a parent server site (or simply parent site or parent server) may comprise one parent server or a cluster of parent servers.
- an edge server site may comprise one edge server or a cluster of edge servers and an origin server site (or simply origin site or origin server) may comprise one origin server or a cluster of origin servers.
- the network 100 is configured such that servers in a cluster share a common storage. In any event, configuration details of the parent server site, edge server site, and the origin server site are not important to the present invention.
- the parent servers and edge servers are maintained by a network provider, wherein the parent servers are primarily used for storing and managing one or more objects and edge servers are primarily used for serving objects to clients.
- all the objects are retrieved from origin servers and stored over one or more parent servers before any end-users can access each such object as the object is stored on the parent servers.
- the origin servers play no significant role in the managed object replication and delivery method except to supply new and/or updated objects for storage on the parent servers.
- only the parent servers communicate with the origin servers.
- each requested object is replicated from one or more origin servers to one or more parent servers (and/or one or more edge servers) when the requested object becomes popular (as described in more detail below).
- the origin servers play a more significant role in the managed object replication and delivery method to supply objects to parent and/or edge servers when requested. So, in these embodiments, the origin servers and parent servers communicate between each other and the origin servers and clients may also communicate between each other. In all of these embodiments, the communications relationships between origin servers and parent servers may be one-to-one, one-to-many or many-to-many.
- the parent servers and edge servers communicate between each other, edge servers and clients communicate between each other and parent servers and clients communicate between each other. While in embodiments, as shown in FIG. 1 , the edge servers have a one-to-one or one-to-many communications relationship with parent servers, edge servers may also have many-to-many communications relationships with parent servers. As discussed in more detail below, the edge servers act as the primary source of serving objects but if a requested object is not available at the edge server a parent server that has the requested object will serve the requested object to the clients. Also, FIG. 1 shows a single layer or level of parent servers and origin servers. As will be apparent to those skilled in the art, more than one layer or level of parent servers and/or origin servers may be used.
- FIGS. 2 , 3 ( a ), 3 ( b ) and 3 ( c ) depict embodiments of the method in relation to a portion of the network 100 , an origin server 110 and a client 140 as shown in FIG. 1 .
- the method of managed object replication and delivery directs (at 200 , 300 ) a client, requesting one or more objects, to an edge server in the network, whether or not the edge server has the requested object(s).
- the client is directed to an optimal edge server, e.g., based on network traffic conditions and server load.
- an optimal edge server e.g., based on network traffic conditions and server load.
- any number of currently known or future developed mechanisms may be used to select a best or optimal edge server. Determination of a best or optimal edge server preferably includes selection of an edge server most suitable for delivery of one or more objects to the client according to any number of currently known or future developed algorithms.
- determination of a best or optimal edge server may be performed based on the likelihood of a copy of the requested object(s) being available at the candidate edge server, on the bandwidth between a candidate edge server and the client, on a best repeater selector (for example, as described in U.S. Pat. No. 6,185,598) and/or on any number of other criteria.
- the selected best or optimal edge server 130 determines (at 305 ) whether the edge server already has the requested object and, if so, serves (at 205 , 310 ) the object to the requesting client 140 . For example, the selected edge server 130 will check its storage to determine whether the requested object is available and if so, may serve the object to the requesting client 140 .
- a check is initiated (at 315 ) for the edge server to determine whether the requested object is popular and if so, to replicate the popular requested object to the edge server.
- the method depicted in FIG. 3 ( b ) and discussed in more detail below is employed to determine whether the requested object is popular and if so, to replicate the popular requested object to the edge server.
- the checking of whether the requested object is popular and replicating the popular requested object to the edge server may be performed independently of one or more functions of the method of managed object replication and delivery, such as the checking if a server has the requested object and serving the requested object to the client if the server has the requested object or redirecting the client to a server that has the requested object (and serving the requested object to the client).
- the checking of whether the requested object is popular and replicating the popular object to the edge server may be performed in parallel with or before the performance of certain functions of the method of managed object replication and delivery such as the checking if a server has the requested object and serving the requested object to the client if the server has the requested object or redirecting the client to a server that has the requested object (and serving the requested object to the client).
- the checking of whether the requested object is popular and replicating the popular object to the edge server can manage the continued delivery of objects to clients from edge servers.
- the checking, redirecting and serving of the requested object can manage the continued delivery of objects from servers in the network.
- the selected edge server directs (at 210 , 320 ) the requesting client 140 to a parent server 120 .
- the client 140 is redirected to a parent server that has the requested object and is able to serve (at 215 , 345 ) the requested object to the client.
- a parent server does not have (at 325 ) the requested object, a check is initiated (at 330 ) for the parent server to determine whether the requested object is popular and if so, to replicate the popular requested object to the parent server. In embodiments, the method depicted in FIG.
- the checking of whether the requested object is popular and replicating the popular requested object to the parent server is performed independently of one or more functions of the method of managed object replication and delivery such as the checking if a server has the requested object and serving the requested object to the client if the server has the requested object or redirecting the client to a server that has the requested object (and serving the requested object to the client).
- the checking of whether the requested object is popular and replicating the popular requested object to the parent server may be performed in parallel with or before one or more functions of the method of managed object replication and delivery such as the checking if a server has the requested object and serving the requested object to the client if the server has the requested object or redirecting the client to a server that has the requested object (and serving the requested object to the client).
- a parent server could itself use a redirection technique recursively (at 325 , 335 , 320 ) until a final parent server is reached that has the requested object.
- the parent server that has the requested object serves (at 215 , 345 ) the object to the client. If the object is determined to be unavailable (at 335 ) (from all parent servers), an error message is returned (at 340 ) regarding the unavailability of the requested object.
- a handling edge server may request information from a database about to which parent server the client should be redirected.
- the edge server might have a local database, populated by pushes of redirection data from one or more servers in the network.
- the edge server may also simply query one or more servers in the network to identify one or more parent servers to which the client can be directed.
- the edge server may redirect the client to the parent server that responds to the query first, the edge server may redirect the client to the parent server that is topologically closest to the edge server in the network or the edge server may redirect the client to the parent server that represents the best or optimal candidate based on criteria such as network efficiency, bandwidth requirement and/or cost.
- an edge server may always go to default parent servers.
- a best or optimal parent server may be determined using any of the techniques outlined above. Redirection may be performed by simply sending the request onto a parent server or returning redirection information to the client for accessing the parent server. As will be apparent to those skilled in the art, any number of implementations may be used to provide the redirection information to the handling edge server.
- the client may be redirected (at 225 , 320 ) to the origin server if the requested object is not available on the parent servers. If the origin server has the requested object (at 325 ), the origin server would serve (at 230 , 345 ) the object directly to the client (not shown in FIG. 1 ). Otherwise if the object is unavailable (at 335 ), an error message would be returned (at 340 ) regarding the unavailability of the requested object.
- an edge and/or parent server determines (at 350 ) that a requested object is popular (by some measure of popularity) but the edge and/or parent server does not have a copy of the object
- the edge and/or parent server initiates a pull of the object to the edge and/or parent server. So, for example, when the edge server determines (at 350 ) that a requested object is popular but the edge server does not have a copy of the requested object, the edge server initiates the replicating (at 220 , 360 ) of the popular requested object to the edge server from a parent server that has the requested object.
- a parent server 120 determines (at 350 ) that a requested object is popular but the parent server does not have a copy of the requested object
- the parent server initiates the replicating (at 240 , 360 ) of the popular requested object to the parent server from an origin server that has the requested object.
- a parent and/or origin server may receive information regarding object popularity, such as popularity determinations for objects or data about object popularity, from one or more edge and/or parent servers and may push popular objects to the edge and/or parent servers.
- the parent server may initiate the replicating (at 220 , 360 ) of the popular requested object to the edge server from the parent server.
- the origin server determines (at 350 ) that a requested object is popular at a parent server but the parent server does not have a copy of the requested object
- the origin server initiates the replicating (at 240 , 360 ) of the popular requested object to the parent server from the origin server.
- the edge server if none of the parent servers has the requested object, the edge server initiates the replication (at 235 , 360 ) of the popular requested object to the edge server from the origin server having the requested object (if the network has access to the origin server).
- the replicated object is not served or further replicated until the object has been completely copied to the respective server.
- such replicating may be utilized by and between the parent servers themselves to facilitate the reduction of the traffic to and from the origin server.
- one or more objects may be purged (at 355 ) from the edge and/or parent server to make space for the popular object.
- servers other than the edge and/or parent server for which an object is determined popular may perform the actual determination of whether an object is popular by using for example, popularity information provided by the handling edge and/or parent server. The popularity determinations can then be used to initiate replication (for example, pushing or pulling) of the object to the edge and/or parent server for the which the object is determined popular.
- the server may delete the object (at 370 ) from the storage.
- an edge server may delete (at 245 , 370 ) any objects from the edge server's storage that are no longer popular.
- a parent server may delete (at 250 , 370 ) any objects from the parent server's storage that are no longer popular.
- the determining of whether any object(s) in the server's storage is no longer popular and if so, deleting the no longer popular object(s) from the server's storage may be performed independently of, for example in parallel with or before, one or more functions of the method of managed object replication and delivery.
- the no longer popular objects are removed from edge servers and, if the no longer popular objects are hosted on an origin server, from parent servers.
- Determining the popularity can be based on the number of requests.
- Popularity can also be based on the request rate.
- Popular objects typically have higher request rates or higher number of requests than unpopular objects.
- Popularity can also be determined by tracking the last X number of request times for an object and then use the difference between the current time and these request times to calculate a running average for how often the object is requested. Determining the popularity can also be gauged on the request rate for an object that is perhaps weighted for more recent requests for the object (which is a predictor that the object will be requested again).
- An exponential decay method and an artificial neural network could also be used to determine popularity of an object.
- the popularity of an object is based on the request rate of the object and computed over a sliding time window in a discrete manner.
- the variable I denotes the time interval over which the popularity of an object is measured.
- the time interval is divided into N equal sub-intervals of duration I/N.
- the time interval is not required to be equally divided and may instead be divided in other manners.
- a linked list P of size N is created for each object.
- the value of N determines the quality of approximation. The smaller the value of N, the coarser the approximation. In some embodiments, the value of N is set to 5.
- the first element P[1] of the list records the number of requests that arrived when the current time was within the first sub-interval
- the second element P[2] records the number of requests that arrived when the current time was within the 2nd interval, and so on.
- the list is rotated such that P[I] becomes P[I+1] except for P[N] which becomes P[1], so, e.g., P[1] becomes P[2], P[2] becomes P[ 3 ], and P[N] becomes P[1].
- the new P[1] is reset to zero. Accordingly, only the end time of the first sub-interval needs to be recorded and compared against the current time to check if the list should be rotated. For each new request within the sub-interval, P[1] is simply incremented by 1. In this way, the arrival time of each request need not be recorded.
- the popularity of an object is simply the sum of all numbers in the list.
- the sum of P[2]+P[3]+ . . . +P[N] is stored in a register M.
- the popularity can be then computed by adding P[1] to M.
- the popularity of an object may be queried constantly. So, to avoid the extra addition involved for each such inquiry, the value of P[1] can be set to M after the rotation. Then, the value of P[1] is the popularity of the object.
- the popularity computation algorithm may be summarized as follows.
- the linked list P of size N for an object, wherein each of P[1] . . . P[N] represents a time sub-interval, is initialized (at 400 ).
- any number of techniques may be used to initiate replication of an object.
- An edge server and/or a parent server might replicate an object on the first request by a client for the object.
- the edge server and/or parent server may be tuned to wait until the edge server and/or parent server receives a specific number or range of requests for the object.
- the object may be pulled if the object is more popular (e.g., a higher request rate) than the least popular object currently in the storage.
- the replicating decision can be a function of the popularity of the object, the cost of storing the object, the cost of pulling the object from the network and any other relevant cost factors.
- the popularity of objects may change significantly with time. Initiating a pull decision of an object purely based on a fixed threshold does not capture this dynamic nature of popularity.
- a replication policy that compares against the least popularity of replicated objects has its limitations, although the policy does not use a fixed threshold. Consider where the storage is only half full but all the replicated objects are extremely popular. Since only objects exceeding the least popularity of the replicated objects will be replicated under this replication policy, objects with moderate popularity will be rejected despite that there is plenty of storage space available and that the objects are reasonably popular.
- a replication scheme should be able to automatically adjust the replication threshold by taking into consideration the dynamic nature of popularity and the fullness of the storage. If there are more popular objects than the storage capacity allows, the replication scheme should raise the threshold. If there is more available storage capacity, the replication scheme should decrease the threshold so that more objects can be stored.
- an object is replicated (at 520 ) into storage when the popularity P of the object is greater (at 500 ) than the initial threshold P I and when there is enough space (at 510 ) in the storage to replicate the object. If there is not enough storage to replicate the requested object, a replacement algorithm is performed in which the popularity P of the object is compared (at 530 ) against the popularity P L of the least popular object in the storage.
- the current least popular object is removed (at 540 ) from the storage to free up more storage space, the next least popular object is identified (at 540 ), the value of the least popularity is updated (at 550 ), and a new iteration begins by checking if there is enough storage space to store the requested object (at 510 ). The storage space freeing iteration is terminated when either 1) enough storage space has been freed up to accommodate the requested object or 2) the requested object is not as popular as the least popular object in the storage.
- the least popular objects are removed from edge servers and, if there are origin servers with a copy of the least popular objects, from parent servers. Where no origin servers exist with a copy of the least popular objects, least popular objects are not removed from parent servers in order to keep a copy of the least popular objects in the network.
- the managed object replication and delivery method and system records the time on which an object was last requested.
- a purge scheme is invoked to clean up the storage of servers, for example, on a regular time interval basis or when a popular object is replicated to an edge and/or parent server but there is inadequate space at the edge and/or parent server.
- all stale objects are removed from the storage (at 600 ), the remaining objects are sorted based on popularity (at 610 ), and the new values of P L and P I are determined (at 620 , 630 ).
- An object is stale if its age (that is the time since the object was last requested) is over a pre-defined value, typically set to the duration of the sliding window used to measure the popularity multiplied by an adjustable factor. As will be apparent to those skilled in the art, the value may vary and indeed other staleness algorithms may be used.
- the popularity of the least popular object in the storage after purging is assigned as the new P L .
- the new P I is determined by using the sorted popularity and is set to the popularity of the last object that can fit into the storage if more popular objects are replicated first. Typically, P L should be greater than or equal to P I . If not, the value of P L is assigned to be the new P I .
- the purge process is implemented as a separate thread in a multi-thread system.
- the stale objects are removed from edge servers and, if there are origin servers with a copy of the stale objects, from parent servers. Where no origin servers exist with a copy of the stale objects, stale objects are not removed from parent servers in order to keep a copy of the stale objects in the network.
- the initial values of both P L and P I can be set to zero. This forces the replication scheme to store the objects on their first request, but the purge scheme that is run on a regular basis will adjust the values of P L and P I automatically.
- the initial values of P L and P I can also be set to other values. Indeed, the initial values of P L and P I can be determined by taking into consideration the cost of storage, the cost of fetching, and the cost difference in deliveries from different servers. In any case, the system allows the specification of minimum P L and P I . If a computed P L or P I is smaller than the minimum specification, P L or P I is set to the minimum specification.
- storage fill is separated from data delivery. In this way, the data transfer between multiple sets of storages can tolerate a slower connection, and a server never streams an object unless the object is entirely in the storage. As will be apparent to those skilled in the art, it is possible to start streaming an object when there is enough data in the storage and that replication need not be completed before serving the object. Further, storage fill may be staged by copying to a separate location, then moving the copied data to a servable location when the data is complete.
- an object is changed at an origin server, there may be a need to broadcast a message to remove the object at one or more parent servers and/or one or more edge servers.
- an object is changed at the parent server(s)
- future requests for the removed object would be handled as in the normal case where a requested object is not available at an edge server and/or a parent server.
- the system of managed object replication and delivery comprises one or more servers in a network designated as parent servers and one or more servers in the network designated as edge servers.
- parent servers 120 have large storage capacity (on the order of 5 terabytes (TB)) while edge servers 130 have smaller storage space (ranging from 1 TB to 500 GB).
- One or more redirectors for implementing the method of managed object replication and delivery are installed on each edge server cluster.
- one or more objects are replicated to one or more of the parent servers from the origin servers and then pulled from the parent servers to the edge servers as needed.
- one or more objects are replicated to one or more of the edge servers and/or to one or more of the parent servers, from the origin servers as needed.
- a data transfer method 700 , 710 is implemented to transfer data between parent servers and edge servers.
- the data transfer method supports the Transport Layer Security (TLS) protocol (described in the Internet Engineering Task Force (IETF) RFC 2246, located at “http://www.ietf.org/rfc/rfc2246.txt”, incorporated by reference herein) to ensure communication privacy.
- TLS Transport Layer Security
- the implementation of the method for managed object replication and delivery supports three popular object formats, namely Apple Computer, Inc.'s QuickTimeTM, RealNetworks, Inc.'s RealTM, and Microsoft Corporation's WindowsMediaTM formats for streaming of requested object(s).
- any number of other protocols and object formats may be used.
- a number of software components are used to facilitate the method of managed object replication and delivery.
- a first component is a WindowsMedia redirector 720 , 760 which is a service running on the Microsoft Windows NT operating system that processes requests from a Windows Media player and performs the redirection of the request for Windows Media objects.
- the WindowsMedia redirector is provided on edge servers and parent servers.
- MMS Microsoft Media Server
- MMS Microsoft Media Server
- URI uniform resource identifier
- URIs as used herein generally have the following form (defined in detail in T.
- schedule can be a symbol such as “http” (see Hypertext Transfer Protocol—HTTP/1.1, IETF RFC 2616, located at “http://www.ietf.org/rfc/rfc2616.txt”, incorporated by reference herein) for an object on a Web server or “rtsp” (see Real Time Streaming Protocol (RTSP), IETF RFC 2326, located at “http://www.ietf.org/rfc/rfc2326.txt”, incorporated by reference herein) for an object on a streaming server.
- RTSP Real Time Streaming Protocol
- Other schemes can also be used and new schemes may be added in the future.
- the port number “port” is optional, the system substituting a default port number (depending on the scheme) if none is provided.
- the “host” field maps to a particular network address for a particular computer.
- the “uri-path” is relative to the computer specified in the “host” field.
- An uri-path is typically, but not necessarily, the path-name of a file in a media server directory.
- the HTTP protocol is used to effect the redirection of WindowsMedia objects. Therefore, the “scheme” field of the URIs of the WindowsMedia objects is changed from “mms” to “http”.
- the URI for a sample object “sample.asf” in the Windows Media Advanced Streaming Format will have a new URI of the form “http://host/path/sample.asf”.
- a sample URI for the “meta.asx” object will be in the form “http://host/?www.customer.com/path/meta.asx”, where “customer” is the name of the content provider of “meta.asx”. All URIs contained within the “meta.asx” object remain unchanged.
- IP Internet Protocol
- a final round of redirection is reached when none of the parent servers (and the origin server, if applicable) has the requested object. In this case, the redirection process is terminated, and a “not found” error message is sent to the requesting client.
- Requests for ASX objects are processed in a similar way.
- the WindowsMedia redirector Upon receiving the request for the sample object “meta.asx”, the WindowsMedia redirector checks the availability of the object pointed to by each URI inside “meta.asx” and rewrites the URI of each object accordingly. Then the WindowsMedia redirector sends a response to the request with the rewritten “meta.asx” in the message body of the response.
- the URI rewriting is done as follows.
- a requested object for example, “file.asf”
- the corresponding URI would be rewritten to “mms://servername/path/file.asf”, where “servername” is or resolves to the IP address of the media server that will serve the requested object to the requesting client. If “file.asf” cannot be found, the corresponding URI is rewritten to “http://redirectorname/path/file.asf”, where “redirname” is or resolves to the IP address of a parent server redirector.
- a Real/QuickTime redirector 730 , 770 which is an application that processes Real-Time Streaming Protocol (RTSP) requests from a Real or QuickTime player for one or more objects and performs the redirection of the method for Real and QuickTime objects.
- RTSP Real-Time Streaming Protocol
- the Real/QuickTime redirector is provided on edge servers and parent servers.
- the RTSP described in detail in the IETF RFC 2326, is used for streaming Real and QuickTime objects, and the “REDIRECT” method supported in that protocol is used to effect redirection.
- a redirect request informs the client that it must reconnect to another server location and provides for the client the URI of that new server in the redirect request.
- a best or optimal server selection mechanism is also provided (not shown in FIG. 7 ).
- the best or optimal server selection mechanism includes selection of an edge server most suitable for delivery of one or more objects to the client according to any number of currently known or future developed algorithms.
- the best or optimal server mechanism may also be applied to trigger one or more further redirections to one or more parent server(s) when a requested object is not available at the handling edge server.
- the hostname part of the URI for a requested object is modified.
- the parent-edge server topology is defined and the best or optimal server selection mechanism is provided a parent server table defining the relationships of such a topology.
- the best or optimal server selection mechanism is similar to the best repeater selector described in U.S. Pat. No. 6,185,598.
- a file replication manager application 740 , 750 is also provided that manages object replication to and object removal from storage, retrieves objects from parent servers for replication to edge server storage, and performs storage cleanup as needed.
- the file replication manager is provided on edge servers and parent servers.
- the file replication manager application uses the data transfer method and is in communication with the WindowsMedia and Real/QuickTime redirectors to provide, if available in the storage, objects requested by those redirectors.
- the message communicated between a WindowsMedia or a Real/QuickTime redirector and a file replication manager and between file replication managers is encapsulated using the User Datagram Protocol (UDP).
- UDP User Datagram Protocol
- MD5 See, e.g., Rivest, R., “The MD5 Message Digest Algorithm”, IETF RFC 1321, April 1992) is supported to provide a basic level of security.
- the MD5 hash is generated by running a MD5 hash algorithm on the message number, message, and a secret pass phrase only shared by components of the system of managed object replication and delivery.
- the MD5 hash of the message number, message, and secret pass phrase is computed and compared against the MD5 hash provided in the message. If these two MD5 hashes do not match, the message is invalid, and will be discarded.
- FIG. 7 represents only some embodiments of the system according to the present invention. Many variations for implementing the system according to the teachings of the present invention are possible and are all within the scope of the invention.
- An extension of the above method and system is to provide chunking.
- Studies of log data show that, even for popular objects, a good percentage of requests for such objects exit before the object is completely served.
- objects can be segmented into chunks and initial chunks of an object can be given preferential treatment in the replication scheme. For example, only the initial chunks of a object are replicated when a replication admission decision is made and the remaining chunks of the object are pulled to the storage only if the client does not exit before a certain amount or number (e.g., 90%) of the initial chunks of the object are served.
- the initial chunks of an object can be left in the storage even when the object becomes unpopular.
- some or all of the objects may be permanently retained in edge server storage or be retained depending on a quota.
- a configurable or automatically adjusting threshold for storage filling and deletion may be provided.
- an edge server may be configured to determine whether a requested object in a server's storage is fresh and serve the requested object only when the object is not stale.
- a file is maintained which lists the maximum storage age and storage quota in order to facilitate determining whether a requested object is fresh. If a request is received for a stale object a redirect is initiated to the relevant parent server or origin server to provide the requested object and a storage refresh will be performed if the requested object is popular.
- edge server storage fills of objects may be served by other peer edge servers instead of a relevant parent server or origin server. If a popular object has already been replicated to an edge server filling a new edge server request for that object from one of the peer edge servers may be more efficient than the parent server or origin server. Since there are typically more edge servers than parent servers and origin servers, there is an increased likelihood that a peer edge server may be closer in terms of network distance than a relevant parent server or origin server. Moreover, such peer edge server storage fills could also lessen the burden on the parent servers or origin servers.
- a procedure is here, and generally, conceived to be a self-consistent sequence of operations leading to a desired result. These operations comprise physical manipulations of physical quantities. Usually, though not necessarily, these quantities take the form of electrical or magnetic signals capable of being stored, transferred, combined, compared, and otherwise manipulated. It proves convenient at times, principally for reasons of common usage, to refer to these signals as bits, values, elements, symbols, characters, terms, numbers, objects, attributes or the like. It should be noted, however, that all of these and similar terms are to be associated with the appropriate physical quantities and are merely convenient labels applied to these quantities.
- the manipulations performed are often referred to in terms, such as adding or comparing, which are commonly associated with mental operations performed by a human operator. No such capability of a human operator is necessary, or desirable in most cases, in any of the operations of the invention described herein; the operations are machine operations.
- Useful machines for performing the operations of the invention include general purpose digital computers, special purpose computers or similar devices.
- Each operation of the method may be executed on any general computer, such as a mainframe computer, personal computer or the like and pursuant to one or more, or a part of one or more, program modules or objects generated from any programming language, such as C++, Perl, JavaTM, Fortran, etc.
- each operation, or a file, module, object or the like implementing each operation may be executed by special purpose hardware or a circuit module designed for that purpose.
- the invention may be implemented as a firmware program loaded into non-volatile storage or a software program loaded from or into a data storage medium as machine-readable code, such code being instructions executable by an array of logic elements such as a processor or other digital signal processing unit.
- Any data handled in such processing or created as a result of such processing can be stored in any memory as is conventional in the art.
- data may be stored in a temporary memory, such as in the RAM of a given computer system or subsystem.
- data may be stored in longer-term storage devices, for example, magnetic disks, rewritable optical disks, and so on.
- Embodiments of the invention may be implemented as an article of manufacture comprising a computer usable medium having computer readable program code means therein for executing the method operations of the invention, a program storage device readable by a machine, tangibly embodying a program of instructions executable by a machine to perform the method operations of the invention, or a computer program product.
- Such an article of manufacture, program storage device or computer program product may include, but is not limited to, CD-ROM, CD-R, CD-RW, diskettes, tapes, hard drives, computer system memory (e.g., RAM or ROM), and/or the electronic, magnetic, optical, biological or other similar embodiments of the program (including, but not limited to, a carrier wave modulated, or otherwise manipulated, to convey instructions that can be read, demodulated/decoded and executed by a computer).
- computer system memory e.g., RAM or ROM
- the electronic, magnetic, optical, biological or other similar embodiments of the program including, but not limited to, a carrier wave modulated, or otherwise manipulated, to convey instructions that can be read, demodulated/decoded and executed by a computer.
- the article of manufacture, program storage device or computer program product may include any solid or fluid transmission medium, whether magnetic, biological, optical, or the like, for storing or transmitting signals readable by a machine for controlling the operation of a general or special purpose computer according to any or all methods of the invention and/or to structure its components in accordance with a system of the invention.
- Embodiments of the invention may also be implemented in a system.
- a system may comprise a computer that includes a processor and a memory device and optionally, a storage device, an output device such as a video display and/or an input device such as a keyboard or computer mouse.
- a system may comprise an interconnected network of computers. Computers may equally be in stand-alone form (such as the traditional desktop personal computer) or integrated into another apparatus (such as a cellular telephone).
- the system may be specially constructed for the required purposes to perform, for example, the method of the invention or the system may comprise one or more general purpose computers as selectively activated or reconfigured by a computer program in accordance with the teachings herein stored in the computer(s).
- the system could also be implemented in whole or in part as a hard-wired circuit or as a circuit configuration fabricated into an application-specific integrated circuit.
- the invention presented herein is not inherently related to a particular computer system or other apparatus. The required structure for a variety of these systems will appear from the description given.
Abstract
Description
- This application is a continuation of co-pending U.S. patent application Ser. No. 11/715,316, titled “Managed Object Replication And Delivery” filed Mar. 8, 2007, which is a continuation of co-pending U.S. patent application Ser. No. 10/073,938 titled “Managed Object Replication And Delivery” filed Feb. 14, 2002, the disclosures of each of which are incorporated herein by reference in their entirety. This application is also related to U.S. patent application Ser. No. ______, (attorney docket no. 2711-0101), titled “Peer Server Handoff in Content Delivery Network,” and filed on even date herewith, the entire disclosure of which is incorporated herein by reference.
- This invention relates in general to the field of computer networks. Particularly, aspects of this invention pertain to managed object replication and delivery over a network.
- Exemplary embodiments of the invention are illustrated in the accompanying drawings in which like references indicate similar or corresponding elements and in which:
-
FIG. 1 is a high-level block diagram of a topology of the managed object replication and delivery method and system according to embodiments of the invention; -
FIG. 2 is a high-level block diagram illustrating the data flows of managed object replication and delivery method according to embodiments of the invention; - FIGS. 3(a), 3(b) and 3(c) are a flow chart of the managed object replication and delivery method and the object purging method according to embodiments of the invention;
-
FIG. 4 is a flow chart of a popularity computation according to embodiments of the invention; -
FIG. 5 is a flow chart of a replication scheme according to embodiments of the invention; -
FIG. 6 is a flow chart of a purge scheme according to embodiments of the invention; and -
FIG. 7 is a block diagram of the managed object replication and delivery system according to embodiments of the invention. - A typical content delivery network (CDN) operator deploys one or more parent servers, hosting a plurality of objects, in a network and one or more edge servers at the edge of the network to facilitate more cost-effective and efficient delivery of such objects to an end-user (client). End-users or client proxies that access customers' objects are called clients. Content provider companies, organizations, etc. that subscribe to the CDN service are referred to as customers. As used herein, an object includes, without limitation, an audio file (such as, e.g., an MP3 (Motion Picture Experts Group-1 Layer 3) file and a RealNetworks, Inc. Real format file), a video file (such as an MPEG file), an image file (such as, e.g., a BMP (bitmap) file or JPEG (Joint Photographic Experts) file) and any other software or data file or object. It is typically desirable to serve objects from edge servers because the edge servers are typically closer (by various measures of distance) to end-users. For example, streaming content data from edge servers saves parent-to-edge bandwidth. Furthermore, the less the distance objects must travel can also mean reduced network congestion and packet losses, which can lead to a better experience for the end-user through faster response times and better quality of service.
- It is typically not feasible to store all objects on the edge servers. The main difficulty is due to the fact that many such objects are very large (typically on the order of 10 MB (10,000,000 bytes)—in the neighborhood of 500 MB for movies). The storage and rack space required to accommodate often large and sometimes rarely requested objects at every edge server can be cost prohibitive as the number of customers grows and the number of their objects increases. It may not even be possible to store a good working set of objects, for example a set of objects thought to be requested often and/or better suited to be served from an edge server, because of the size and changing demand for objects in the working set.
- One obvious solution is to pre-populate edge servers with objects for which there will likely be a significant or high demand. However, it is difficult to predict popularity and difficult to manage pre-populating. A related solution is to associate objects with two or more domains depending on popularity of the object, e.g., one domain for popular objects (served from edge servers) and another domain for less popular objects (served from parent servers). However, this requires some way to pre-determine what objects are popular and what objects are less popular statically, and build that popularity into the domain name of the object. As with pre-populating, it is difficult to predict popularity and to manage assignment of domains based on such popularity determinations.
- Other solutions fetch objects on demand. In such schemes, when a requested object is not available on a handling edge server, a connection is made between a parent server having the requested object and the handling edge server to fetch the requested object from the parent server. Such fetching suffers however from having to go through the parent path (the network path between the handling edge server and the parent server with the object) whenever a client requests an object that is not already at the particular edge server.
- Fetching a large object to the handling edge server through a parent path can be slow. For example, there may be limited available bandwidth from the parent server to the handling edge server, i.e., sometimes the parent path has less bandwidth than even the network path from the edge server to the client (e.g., the “last mile” in a broadband network). If a parent server uses too much bandwidth copying an object to an edge server, this can create congestion at that parent server. If storage fill bandwidth is matched to client bandwidth, it is difficult to handle a second, faster client and if fetch is done using a streaming protocol (for instance, the Real-Time Streaming Protocol (RTSP) and Real-Time Transport Protocol (RTP) standards), the quality of the copy made can be hurt due to lost packets (“thinning”).
- Moreover, there may be an unreliable end-to-end parent path due to network congestion. And, if a parent server has to preprocess an object (e.g., to generate an image at a specific bit rate) or is otherwise busy with other tasks, this may further slow its ability to serve the request for the object fast enough. For example, if a client requests a bit rate higher than the parent-to-edge bit rate, delays will likely occur. Under such conditions, the parent server may fail, for example, to stream the object in time or to maintain the stream of an object at a requested bit rate thereby causing a thinned object, i.e., an object with lower quality due to lost packets in its transmission, to be populated at the edge server and delivered to subsequent clients requesting the same object.
- Thus, it would be advantageous to populate edge servers with the most popular objects yet somehow serve the rest from parent servers with a goal to maximize the amount of object bits served from edge servers of the network. It would also be advantageous to populate edge servers by, for example, storage fill on demand when an object is popular enough, without having to make the end-user wait for such population. Therefore, it would be advantageous to provide a method and system for managed object replication and delivery over a network.
- According to embodiments of the invention, a method and system for managed object replication and delivery over a network redirects, directly or indirectly, a client's request for an object that is not available at a best or optimal handling edge server of the network to a parent server of the network that has the requested object. So, where the requested object is not available at the handling edge server, the client's request is redirected directly to the parent server that can provide the requested object to the client or indirectly via one or more parent servers to a parent server that can provide the requested object to the client. The method and system further intelligently replicates the object to the edge server if the object is popular enough. Likewise, an object is removed from an edge server when the object is no longer popular. All redirection and replication operations are preferably transparent to the end-user and do not degrade the quality of service. Other embodiments of the invention are possible and some are described hereafter.
- So, for example, under the framework described herein, a request for a streaming object will be served by a handling edge server if that handling edge server has a copy of that object. Otherwise, the request is redirected, directly or indirectly, to a parent server for service of the requested streaming object to the client. If the requested streaming object is popular, the object is replicated from a parent server that has the requested streaming object to the handling edge server so that the handling edge server will serve the object from the edge of the network when the object is requested in the future. If a streaming object is no longer popular, the object is removed from an edge server.
- As used herein, replication generally refers to the permanent and/or volatile storage of an object in a server, particularly an edge server and if applicable, a parent server. Accordingly, the term replication will be considered synonymous to storing, caching and copying. In typical embodiments, replication of an object will usually refer to temporary storage of the object in an edge server and/or a parent server for an undefined duration.
- A typical network for the managed object replication and delivery method according to embodiments of the invention is illustrated in
FIG. 1 . Thenetwork 100 comprises one or moreparent server sites 120 and one or moreedge server sites 130. The network also optionally has access to one or moreorigin server sites 110. The origin server sites are typically owned and/or maintained by the network provider's customers for storing and serving one or more objects. Each customer (content provider) may have its own origin server site. Furthermore, one ormore clients 140 access the network to request one or more objects. A parent server site (or simply parent site or parent server) may comprise one parent server or a cluster of parent servers. Likewise, an edge server site (or simply edge site or edge server) may comprise one edge server or a cluster of edge servers and an origin server site (or simply origin site or origin server) may comprise one origin server or a cluster of origin servers. Typically, thenetwork 100 is configured such that servers in a cluster share a common storage. In any event, configuration details of the parent server site, edge server site, and the origin server site are not important to the present invention. - In the typical network, the parent servers and edge servers are maintained by a network provider, wherein the parent servers are primarily used for storing and managing one or more objects and edge servers are primarily used for serving objects to clients. In some embodiments, all the objects are retrieved from origin servers and stored over one or more parent servers before any end-users can access each such object as the object is stored on the parent servers. Accordingly, in these embodiments, the origin servers play no significant role in the managed object replication and delivery method except to supply new and/or updated objects for storage on the parent servers. Moreover, only the parent servers communicate with the origin servers. In other embodiments, each requested object is replicated from one or more origin servers to one or more parent servers (and/or one or more edge servers) when the requested object becomes popular (as described in more detail below). In these embodiments, the origin servers play a more significant role in the managed object replication and delivery method to supply objects to parent and/or edge servers when requested. So, in these embodiments, the origin servers and parent servers communicate between each other and the origin servers and clients may also communicate between each other. In all of these embodiments, the communications relationships between origin servers and parent servers may be one-to-one, one-to-many or many-to-many.
- Further, as shown in
FIG. 1 , the parent servers and edge servers communicate between each other, edge servers and clients communicate between each other and parent servers and clients communicate between each other. While in embodiments, as shown inFIG. 1 , the edge servers have a one-to-one or one-to-many communications relationship with parent servers, edge servers may also have many-to-many communications relationships with parent servers. As discussed in more detail below, the edge servers act as the primary source of serving objects but if a requested object is not available at the edge server a parent server that has the requested object will serve the requested object to the clients. Also,FIG. 1 shows a single layer or level of parent servers and origin servers. As will be apparent to those skilled in the art, more than one layer or level of parent servers and/or origin servers may be used. - According to embodiments of the invention and referring to FIGS. 2, 3(a), 3(b) and 3(c), the method of managed object replication and delivery and the method of object purging is depicted.
FIG. 2 depicts embodiments of the method in relation to a portion of thenetwork 100, anorigin server 110 and aclient 140 as shown inFIG. 1 . FIGS. 3(a), 3(b) and 3(c) depict embodiments of the method in flowchart form. - Initially, the method of managed object replication and delivery directs (at 200, 300) a client, requesting one or more objects, to an edge server in the network, whether or not the edge server has the requested object(s). Preferably, the client is directed to an optimal edge server, e.g., based on network traffic conditions and server load. As will be apparent to those skilled in the art, any number of currently known or future developed mechanisms may be used to select a best or optimal edge server. Determination of a best or optimal edge server preferably includes selection of an edge server most suitable for delivery of one or more objects to the client according to any number of currently known or future developed algorithms. For example, determination of a best or optimal edge server may be performed based on the likelihood of a copy of the requested object(s) being available at the candidate edge server, on the bandwidth between a candidate edge server and the client, on a best repeater selector (for example, as described in U.S. Pat. No. 6,185,598) and/or on any number of other criteria.
- The selected best or
optimal edge server 130 determines (at 305) whether the edge server already has the requested object and, if so, serves (at 205, 310) the object to the requestingclient 140. For example, the selectededge server 130 will check its storage to determine whether the requested object is available and if so, may serve the object to the requestingclient 140. - If the selected edge server does not have the requested object, a check is initiated (at 315) for the edge server to determine whether the requested object is popular and if so, to replicate the popular requested object to the edge server. In embodiments, the method depicted in
FIG. 3 (b) and discussed in more detail below is employed to determine whether the requested object is popular and if so, to replicate the popular requested object to the edge server. - In embodiments, the checking of whether the requested object is popular and replicating the popular requested object to the edge server may be performed independently of one or more functions of the method of managed object replication and delivery, such as the checking if a server has the requested object and serving the requested object to the client if the server has the requested object or redirecting the client to a server that has the requested object (and serving the requested object to the client). Thus, in embodiments, the checking of whether the requested object is popular and replicating the popular object to the edge server may be performed in parallel with or before the performance of certain functions of the method of managed object replication and delivery such as the checking if a server has the requested object and serving the requested object to the client if the server has the requested object or redirecting the client to a server that has the requested object (and serving the requested object to the client). Advantageously, should the checking, redirecting and serving of the requested object fail, the checking of whether the requested object is popular and replicating the popular object to the edge server can manage the continued delivery of objects to clients from edge servers. Similarly, if the checking of whether the requested object is popular and replicating the popular object to the edge server should fail, the checking, redirecting and serving of the requested object can manage the continued delivery of objects from servers in the network.
- Further, if the selected edge server does not have the requested object, the selected edge server directs (at 210, 320) the requesting
client 140 to aparent server 120. Preferably theclient 140 is redirected to a parent server that has the requested object and is able to serve (at 215, 345) the requested object to the client. If a parent server does not have (at 325) the requested object, a check is initiated (at 330) for the parent server to determine whether the requested object is popular and if so, to replicate the popular requested object to the parent server. In embodiments, the method depicted inFIG. 3 (b) and discussed in more detail below is employed to determine whether the requested object is popular and if so, to replicate the popular requested object to the parent server. As with the check for the edge server, in embodiments, the checking of whether the requested object is popular and replicating the popular requested object to the parent server is performed independently of one or more functions of the method of managed object replication and delivery such as the checking if a server has the requested object and serving the requested object to the client if the server has the requested object or redirecting the client to a server that has the requested object (and serving the requested object to the client). Thus, in embodiments, the checking of whether the requested object is popular and replicating the popular requested object to the parent server may be performed in parallel with or before one or more functions of the method of managed object replication and delivery such as the checking if a server has the requested object and serving the requested object to the client if the server has the requested object or redirecting the client to a server that has the requested object (and serving the requested object to the client). - Further, if a parent server does not have the requested object, the parent server could itself use a redirection technique recursively (at 325, 335, 320) until a final parent server is reached that has the requested object. The parent server that has the requested object serves (at 215, 345) the object to the client. If the object is determined to be unavailable (at 335) (from all parent servers), an error message is returned (at 340) regarding the unavailability of the requested object.
- As will be apparent to those skilled in the art, numerous methods are available to redirect a requesting client to another parent server, depending on the protocol(s) used to request the object. A handling edge server may request information from a database about to which parent server the client should be redirected. In an implementation, the edge server might have a local database, populated by pushes of redirection data from one or more servers in the network. The edge server may also simply query one or more servers in the network to identify one or more parent servers to which the client can be directed. When more than one parent server responds, the edge server may redirect the client to the parent server that responds to the query first, the edge server may redirect the client to the parent server that is topologically closest to the edge server in the network or the edge server may redirect the client to the parent server that represents the best or optimal candidate based on criteria such as network efficiency, bandwidth requirement and/or cost. Alternatively, an edge server may always go to default parent servers. Or, as discussed in relation to edge servers, a best or optimal parent server may be determined using any of the techniques outlined above. Redirection may be performed by simply sending the request onto a parent server or returning redirection information to the client for accessing the parent server. As will be apparent to those skilled in the art, any number of implementations may be used to provide the redirection information to the handling edge server.
- In other embodiments, where the parent servers collectively are not populated with all of the objects and the network has access to the origin server of a requested object, the client may be redirected (at 225, 320) to the origin server if the requested object is not available on the parent servers. If the origin server has the requested object (at 325), the origin server would serve (at 230, 345) the object directly to the client (not shown in
FIG. 1 ). Otherwise if the object is unavailable (at 335), an error message would be returned (at 340) regarding the unavailability of the requested object. - Referring to
FIG. 3 (b), when an edge and/or parent server determines (at 350) that a requested object is popular (by some measure of popularity) but the edge and/or parent server does not have a copy of the object, the edge and/or parent server initiates a pull of the object to the edge and/or parent server. So, for example, when the edge server determines (at 350) that a requested object is popular but the edge server does not have a copy of the requested object, the edge server initiates the replicating (at 220, 360) of the popular requested object to the edge server from a parent server that has the requested object. Similarly, for example, when aparent server 120 determines (at 350) that a requested object is popular but the parent server does not have a copy of the requested object, the parent server initiates the replicating (at 240, 360) of the popular requested object to the parent server from an origin server that has the requested object. Alternatively, a parent and/or origin server may receive information regarding object popularity, such as popularity determinations for objects or data about object popularity, from one or more edge and/or parent servers and may push popular objects to the edge and/or parent servers. So, for example, when the parent server determines (at 350) that a requested object is popular at an edge server but the edge server does not have a copy of the requested object, the parent server may initiate the replicating (at 220, 360) of the popular requested object to the edge server from the parent server. Similarly, for example, when the origin server determines (at 350) that a requested object is popular at a parent server but the parent server does not have a copy of the requested object, the origin server initiates the replicating (at 240, 360) of the popular requested object to the parent server from the origin server. - In some embodiments, if none of the parent servers has the requested object, the edge server initiates the replication (at 235, 360) of the popular requested object to the edge server from the origin server having the requested object (if the network has access to the origin server). Preferably, in each case, the replicated object is not served or further replicated until the object has been completely copied to the respective server. Optionally, such replicating may be utilized by and between the parent servers themselves to facilitate the reduction of the traffic to and from the origin server. Further, if the edge and/or parent server does not have adequate space for the popular requested object, one or more objects may be purged (at 355) from the edge and/or parent server to make space for the popular object. In embodiments, the method depicted in
FIG. 3 (c) and discussed in more detail below is employed to determine whether any object(s) in the edge and/or parent server is no longer popular and if so, to delete the no longer popular object(s) from the edge and/or parent server. Also, as will apparent to those skilled in the art, servers other than the edge and/or parent server for which an object is determined popular may perform the actual determination of whether an object is popular by using for example, popularity information provided by the handling edge and/or parent server. The popularity determinations can then be used to initiate replication (for example, pushing or pulling) of the object to the edge and/or parent server for the which the object is determined popular. - Referring to
FIG. 3 (c), if an object in a server's storage is no longer popular (at 365), the server may delete the object (at 370) from the storage. For example, an edge server may delete (at 245, 370) any objects from the edge server's storage that are no longer popular. Similarly, a parent server may delete (at 250, 370) any objects from the parent server's storage that are no longer popular. As will be apparent to those skilled in the art, the determining of whether any object(s) in the server's storage is no longer popular and if so, deleting the no longer popular object(s) from the server's storage may be performed independently of, for example in parallel with or before, one or more functions of the method of managed object replication and delivery. In embodiments, the no longer popular objects are removed from edge servers and, if the no longer popular objects are hosted on an origin server, from parent servers. - Determining Popularity
- Any number of techniques may be used to determine the popularity of an object. Determining the popularity can be based on the number of requests. Popularity can also be based on the request rate. Popular objects typically have higher request rates or higher number of requests than unpopular objects. Popularity can also be determined by tracking the last X number of request times for an object and then use the difference between the current time and these request times to calculate a running average for how often the object is requested. Determining the popularity can also be gauged on the request rate for an object that is perhaps weighted for more recent requests for the object (which is a predictor that the object will be requested again). An exponential decay method and an artificial neural network could also be used to determine popularity of an object.
- According to some embodiments of a popularity computation and referring to
FIG. 4 , the popularity of an object is based on the request rate of the object and computed over a sliding time window in a discrete manner. In these embodiments, the variable I denotes the time interval over which the popularity of an object is measured. The time interval is divided into N equal sub-intervals of duration I/N. As will be apparent, the time interval is not required to be equally divided and may instead be divided in other manners. - A linked list P of size N is created for each object. The value of N determines the quality of approximation. The smaller the value of N, the coarser the approximation. In some embodiments, the value of N is set to 5.
- The first element P[1] of the list records the number of requests that arrived when the current time was within the first sub-interval, the second element P[2] records the number of requests that arrived when the current time was within the 2nd interval, and so on. When a new sub-interval arrives, the list is rotated such that P[I] becomes P[I+1] except for P[N] which becomes P[1], so, e.g., P[1] becomes P[2], P[2] becomes P[3], and P[N] becomes P[1]. After the rotation, the new P[1] is reset to zero. Accordingly, only the end time of the first sub-interval needs to be recorded and compared against the current time to check if the list should be rotated. For each new request within the sub-interval, P[1] is simply incremented by 1. In this way, the arrival time of each request need not be recorded.
- In preferred embodiments, the popularity of an object is simply the sum of all numbers in the list. To make the computation more efficient, the sum of P[2]+P[3]+ . . . +P[N] is stored in a register M. The popularity can be then computed by adding P[1] to M. When a rotation occurs, the new value of M becomes M+=P[1]−P[N]. The popularity of an object may be queried constantly. So, to avoid the extra addition involved for each such inquiry, the value of P[1] can be set to M after the rotation. Then, the value of P[1] is the popularity of the object.
- The popularity computation algorithm may be summarized as follows. The linked list P of size N for an object, wherein each of P[1] . . . P[N] represents a time sub-interval, is initialized (at 400). The popularity M is also initialized (at 410). If there is a request for the object while the current time is within the current time sub-interval (at 420), then the value of P[1] is incremented (at 430) by 1. If the current time is within a new time sub-interval (at 440), then the value of P[1] is decremented by the value of M, M+=P[1]−P[N], the list P is rotated and P[1] is set to the value of M (at 450). Then, provided the popularity computation is continued (at 460) e.g., the popularity computation is not terminated, the popularity computation algorithm repeats itself.
- Initiating Replication
- Furthermore, any number of techniques may be used to initiate replication of an object. An edge server and/or a parent server might replicate an object on the first request by a client for the object. Alternatively, the edge server and/or parent server may be tuned to wait until the edge server and/or parent server receives a specific number or range of requests for the object. In other implementations, the object may be pulled if the object is more popular (e.g., a higher request rate) than the least popular object currently in the storage. In yet another alternative, the replicating decision can be a function of the popularity of the object, the cost of storing the object, the cost of pulling the object from the network and any other relevant cost factors. However, the popularity of objects may change significantly with time. Initiating a pull decision of an object purely based on a fixed threshold does not capture this dynamic nature of popularity.
- A replication policy that compares against the least popularity of replicated objects has its limitations, although the policy does not use a fixed threshold. Consider where the storage is only half full but all the replicated objects are extremely popular. Since only objects exceeding the least popularity of the replicated objects will be replicated under this replication policy, objects with moderate popularity will be rejected despite that there is plenty of storage space available and that the objects are reasonably popular.
- Accordingly, a replication scheme should be able to automatically adjust the replication threshold by taking into consideration the dynamic nature of popularity and the fullness of the storage. If there are more popular objects than the storage capacity allows, the replication scheme should raise the threshold. If there is more available storage capacity, the replication scheme should decrease the threshold so that more objects can be stored.
- According to embodiments of a replication scheme and referring to
FIG. 5 , an object is replicated (at 520) into storage when the popularity P of the object is greater (at 500) than the initial threshold PI and when there is enough space (at 510) in the storage to replicate the object. If there is not enough storage to replicate the requested object, a replacement algorithm is performed in which the popularity P of the object is compared (at 530) against the popularity PL of the least popular object in the storage. If P is greater than PL, the current least popular object is removed (at 540) from the storage to free up more storage space, the next least popular object is identified (at 540), the value of the least popularity is updated (at 550), and a new iteration begins by checking if there is enough storage space to store the requested object (at 510). The storage space freeing iteration is terminated when either 1) enough storage space has been freed up to accommodate the requested object or 2) the requested object is not as popular as the least popular object in the storage. In embodiments, the least popular objects are removed from edge servers and, if there are origin servers with a copy of the least popular objects, from parent servers. Where no origin servers exist with a copy of the least popular objects, least popular objects are not removed from parent servers in order to keep a copy of the least popular objects in the network. - Purging
- In some embodiments, the managed object replication and delivery method and system records the time on which an object was last requested. A purge scheme is invoked to clean up the storage of servers, for example, on a regular time interval basis or when a popular object is replicated to an edge and/or parent server but there is inadequate space at the edge and/or parent server. Referring to
FIG. 6 , in the purge scheme, all stale objects are removed from the storage (at 600), the remaining objects are sorted based on popularity (at 610), and the new values of PL and PI are determined (at 620, 630). An object is stale if its age (that is the time since the object was last requested) is over a pre-defined value, typically set to the duration of the sliding window used to measure the popularity multiplied by an adjustable factor. As will be apparent to those skilled in the art, the value may vary and indeed other staleness algorithms may be used. The popularity of the least popular object in the storage after purging is assigned as the new PL. The new PI is determined by using the sorted popularity and is set to the popularity of the last object that can fit into the storage if more popular objects are replicated first. Typically, PL should be greater than or equal to PI. If not, the value of PL is assigned to be the new PI. In some embodiments, the purge process is implemented as a separate thread in a multi-thread system. In embodiments, the stale objects are removed from edge servers and, if there are origin servers with a copy of the stale objects, from parent servers. Where no origin servers exist with a copy of the stale objects, stale objects are not removed from parent servers in order to keep a copy of the stale objects in the network. - At the outset when the system starts and there is no popularity data available yet, the initial values of both PL and PI can be set to zero. This forces the replication scheme to store the objects on their first request, but the purge scheme that is run on a regular basis will adjust the values of PL and PI automatically. The initial values of PL and PI can also be set to other values. Indeed, the initial values of PL and PI can be determined by taking into consideration the cost of storage, the cost of fetching, and the cost difference in deliveries from different servers. In any case, the system allows the specification of minimum PL and PI. If a computed PL or PI is smaller than the minimum specification, PL or PI is set to the minimum specification.
- In some embodiments, to avoid or minimize stream thinning and other quality problems, storage fill is separated from data delivery. In this way, the data transfer between multiple sets of storages can tolerate a slower connection, and a server never streams an object unless the object is entirely in the storage. As will be apparent to those skilled in the art, it is possible to start streaming an object when there is enough data in the storage and that replication need not be completed before serving the object. Further, storage fill may be staged by copying to a separate location, then moving the copied data to a servable location when the data is complete.
- Further, if an object is changed at an origin server, there may be a need to broadcast a message to remove the object at one or more parent servers and/or one or more edge servers. Similarly, if an object is changed at the parent server(s), there may be a need to broadcast a message to remove the object at one or more edge servers. In each case, future requests for the removed object would be handled as in the normal case where a requested object is not available at an edge server and/or a parent server.
- Hardware and Software
- In embodiments of the invention, referring to
FIGS. 1 and 7 , the system of managed object replication and delivery comprises one or more servers in a network designated as parent servers and one or more servers in the network designated as edge servers. In some embodiments, referring toFIG. 1 ,parent servers 120 have large storage capacity (on the order of 5 terabytes (TB)) whileedge servers 130 have smaller storage space (ranging from 1 TB to 500 GB). One or more redirectors for implementing the method of managed object replication and delivery are installed on each edge server cluster. In some embodiments, one or more objects are replicated to one or more of the parent servers from the origin servers and then pulled from the parent servers to the edge servers as needed. In other embodiments, one or more objects are replicated to one or more of the edge servers and/or to one or more of the parent servers, from the origin servers as needed. - In some embodiments, a
data transfer method - Further, in some embodiments, a number of software components are used to facilitate the method of managed object replication and delivery. A first component is a
WindowsMedia redirector scheme://host[port]/uri-path - where “scheme” can be a symbol such as “http” (see Hypertext Transfer Protocol—HTTP/1.1, IETF RFC 2616, located at “http://www.ietf.org/rfc/rfc2616.txt”, incorporated by reference herein) for an object on a Web server or “rtsp” (see Real Time Streaming Protocol (RTSP), IETF RFC 2326, located at “http://www.ietf.org/rfc/rfc2326.txt”, incorporated by reference herein) for an object on a streaming server. Other schemes can also be used and new schemes may be added in the future. The port number “port” is optional, the system substituting a default port number (depending on the scheme) if none is provided. The “host” field maps to a particular network address for a particular computer. The “uri-path” is relative to the computer specified in the “host” field. An uri-path is typically, but not necessarily, the path-name of a file in a media server directory. In a preferred embodiment, the HTTP protocol is used to effect the redirection of WindowsMedia objects. Therefore, the “scheme” field of the URIs of the WindowsMedia objects is changed from “mms” to “http”. For example, the URI for a sample object “sample.asf” in the Windows Media Advanced Streaming Format (ASF) will have a new URI of the form “http://host/path/sample.asf”. For objects using Windows Media ASX scripting, a sample URI for the “meta.asx” object will be in the form “http://host/?www.customer.com/path/meta.asx”, where “customer” is the name of the content provider of “meta.asx”. All URIs contained within the “meta.asx” object remain unchanged. Upon receiving the request “http://host/path/sample.asf”, the WindowsMedia redirector would respond to the request with the following example ASX script:
<ASX version = “3.0”> <Entry><Ref href= “mms://servername/path/sample.asf” /></Entry> </ASX> - in the message body, if the requested object is found available either locally or on another server (parent or origin). In this example, “servername” is or resolves to the Internet Protocol (IP) address of a media server that will serve the requested object to the requesting client. If the requested object cannot be found, the WindowsMedia redirector would respond to the request with the following example ASX script:
<ASX version = “3.0”> <Entry><Ref href= “http://redirname/path/sample.asf” /></Entry> </ASX>
in the message body, where “redirname” is or resolves to the IP address of the redirector of a parent server, to trigger another round of redirection. A final round of redirection is reached when none of the parent servers (and the origin server, if applicable) has the requested object. In this case, the redirection process is terminated, and a “not found” error message is sent to the requesting client. Requests for ASX objects are processed in a similar way. Upon receiving the request for the sample object “meta.asx”, the WindowsMedia redirector checks the availability of the object pointed to by each URI inside “meta.asx” and rewrites the URI of each object accordingly. Then the WindowsMedia redirector sends a response to the request with the rewritten “meta.asx” in the message body of the response. The URI rewriting is done as follows. If a requested object, for example, “file.asf”, is found available locally or on another server, the corresponding URI would be rewritten to “mms://servername/path/file.asf”, where “servername” is or resolves to the IP address of the media server that will serve the requested object to the requesting client. If “file.asf” cannot be found, the corresponding URI is rewritten to “http://redirectorname/path/file.asf”, where “redirname” is or resolves to the IP address of a parent server redirector. - Another component is a Real/
QuickTime redirector - A best or optimal server selection mechanism is also provided (not shown in
FIG. 7 ). The best or optimal server selection mechanism includes selection of an edge server most suitable for delivery of one or more objects to the client according to any number of currently known or future developed algorithms. In addition to redirection to a best or optimal edge server for handling a client request for an object, the best or optimal server mechanism may also be applied to trigger one or more further redirections to one or more parent server(s) when a requested object is not available at the handling edge server. In an implementation, to effect this operation, the hostname part of the URI for a requested object is modified. For example, in the link “http://customer-wm.fpondemand.net/customer/sample.asf”, “customer-wm.fpondemand.net” would be changed to “parent-wm.fpondemand.net” forcing the request to go through a further round of best or optimal server selection against parent servers only. In such embodiments, to effect best or optimal parent server selection, the parent-edge server topology is defined and the best or optimal server selection mechanism is provided a parent server table defining the relationships of such a topology. In some embodiments, the best or optimal server selection mechanism is similar to the best repeater selector described in U.S. Pat. No. 6,185,598. - A file
replication manager application - In some embodiments, the message communicated between a WindowsMedia or a Real/QuickTime redirector and a file replication manager and between file replication managers is encapsulated using the User Datagram Protocol (UDP). This allows address handling and delivery to be handled by UDP and facilitates fast communication. Since UDP does not guarantee delivery, the message header contains a message number to be used to confirm that a response is to the current query, and not to a previous query. In addition, MD5 (See, e.g., Rivest, R., “The MD5 Message Digest Algorithm”, IETF RFC 1321, April 1992) is supported to provide a basic level of security. The MD5 hash is generated by running a MD5 hash algorithm on the message number, message, and a secret pass phrase only shared by components of the system of managed object replication and delivery. When a message is received, the MD5 hash of the message number, message, and secret pass phrase, is computed and compared against the MD5 hash provided in the message. If these two MD5 hashes do not match, the message is invalid, and will be discarded.
- As will be apparent to those skilled in the art,
FIG. 7 represents only some embodiments of the system according to the present invention. Many variations for implementing the system according to the teachings of the present invention are possible and are all within the scope of the invention. - Chunking
- An extension of the above method and system is to provide chunking. Studies of log data show that, even for popular objects, a good percentage of requests for such objects exit before the object is completely served. To exploit this kind of object usage and further enhance the performance of the network, objects can be segmented into chunks and initial chunks of an object can be given preferential treatment in the replication scheme. For example, only the initial chunks of a object are replicated when a replication admission decision is made and the remaining chunks of the object are pulled to the storage only if the client does not exit before a certain amount or number (e.g., 90%) of the initial chunks of the object are served. The initial chunks of an object can be left in the storage even when the object becomes unpopular. By partitioning streams in this manner, a first part of an object can be served from edge servers quickly, even if most of the object stream must be fetched from a parent server or origin server.
- Object Retention and Staleness
- Optionally, some or all of the objects may be permanently retained in edge server storage or be retained depending on a quota. Similarly, a configurable or automatically adjusting threshold for storage filling and deletion may be provided.
- Also, an edge server may be configured to determine whether a requested object in a server's storage is fresh and serve the requested object only when the object is not stale. In some embodiments, a file is maintained which lists the maximum storage age and storage quota in order to facilitate determining whether a requested object is fresh. If a request is received for a stale object a redirect is initiated to the relevant parent server or origin server to provide the requested object and a storage refresh will be performed if the requested object is popular.
- Peers
- Also, edge server storage fills of objects may be served by other peer edge servers instead of a relevant parent server or origin server. If a popular object has already been replicated to an edge server filling a new edge server request for that object from one of the peer edge servers may be more efficient than the parent server or origin server. Since there are typically more edge servers than parent servers and origin servers, there is an increased likelihood that a peer edge server may be closer in terms of network distance than a relevant parent server or origin server. Moreover, such peer edge server storage fills could also lessen the burden on the parent servers or origin servers.
- The detailed descriptions may have been presented in terms of program procedures executed on a computer or network of computers. These procedural descriptions and representations are the means used by those skilled in the art to most effectively convey the substance of their work to others skilled in the art. The embodiments of the invention may be implemented as apparent to those skilled in the art in hardware or software, or any combination thereof. The actual software code or hardware used to implement the invention is not limiting of the invention. Thus, the operation and behavior of the embodiments often will be described without specific reference to the actual software code or hardware components. The absence of such specific references is feasible because it is clearly understood that artisans of ordinary skill would be able to design software and hardware to implement the embodiments of the invention based on the description herein with only a reasonable effort and without undue experimentation.
- A procedure is here, and generally, conceived to be a self-consistent sequence of operations leading to a desired result. These operations comprise physical manipulations of physical quantities. Usually, though not necessarily, these quantities take the form of electrical or magnetic signals capable of being stored, transferred, combined, compared, and otherwise manipulated. It proves convenient at times, principally for reasons of common usage, to refer to these signals as bits, values, elements, symbols, characters, terms, numbers, objects, attributes or the like. It should be noted, however, that all of these and similar terms are to be associated with the appropriate physical quantities and are merely convenient labels applied to these quantities.
- Further, the manipulations performed are often referred to in terms, such as adding or comparing, which are commonly associated with mental operations performed by a human operator. No such capability of a human operator is necessary, or desirable in most cases, in any of the operations of the invention described herein; the operations are machine operations. Useful machines for performing the operations of the invention include general purpose digital computers, special purpose computers or similar devices.
- Each operation of the method may be executed on any general computer, such as a mainframe computer, personal computer or the like and pursuant to one or more, or a part of one or more, program modules or objects generated from any programming language, such as C++, Perl, Java™, Fortran, etc. And still further, each operation, or a file, module, object or the like implementing each operation, may be executed by special purpose hardware or a circuit module designed for that purpose. For example, the invention may be implemented as a firmware program loaded into non-volatile storage or a software program loaded from or into a data storage medium as machine-readable code, such code being instructions executable by an array of logic elements such as a processor or other digital signal processing unit. Any data handled in such processing or created as a result of such processing can be stored in any memory as is conventional in the art. By way of example, such data may be stored in a temporary memory, such as in the RAM of a given computer system or subsystem. In addition, or in the alternative, such data may be stored in longer-term storage devices, for example, magnetic disks, rewritable optical disks, and so on.
- In the case of diagrams depicted herein, they are provided by way of example. There may be variations to these diagrams or the operations described herein without departing from the spirit of the invention. For instance, in certain cases, the operations may be performed in differing order, or operations may be added, deleted or modified.
- Embodiments of the invention may be implemented as an article of manufacture comprising a computer usable medium having computer readable program code means therein for executing the method operations of the invention, a program storage device readable by a machine, tangibly embodying a program of instructions executable by a machine to perform the method operations of the invention, or a computer program product. Such an article of manufacture, program storage device or computer program product may include, but is not limited to, CD-ROM, CD-R, CD-RW, diskettes, tapes, hard drives, computer system memory (e.g., RAM or ROM), and/or the electronic, magnetic, optical, biological or other similar embodiments of the program (including, but not limited to, a carrier wave modulated, or otherwise manipulated, to convey instructions that can be read, demodulated/decoded and executed by a computer). Indeed, the article of manufacture, program storage device or computer program product may include any solid or fluid transmission medium, whether magnetic, biological, optical, or the like, for storing or transmitting signals readable by a machine for controlling the operation of a general or special purpose computer according to any or all methods of the invention and/or to structure its components in accordance with a system of the invention.
- Embodiments of the invention may also be implemented in a system. A system may comprise a computer that includes a processor and a memory device and optionally, a storage device, an output device such as a video display and/or an input device such as a keyboard or computer mouse. Moreover, a system may comprise an interconnected network of computers. Computers may equally be in stand-alone form (such as the traditional desktop personal computer) or integrated into another apparatus (such as a cellular telephone).
- The system may be specially constructed for the required purposes to perform, for example, the method of the invention or the system may comprise one or more general purpose computers as selectively activated or reconfigured by a computer program in accordance with the teachings herein stored in the computer(s). The system could also be implemented in whole or in part as a hard-wired circuit or as a circuit configuration fabricated into an application-specific integrated circuit. The invention presented herein is not inherently related to a particular computer system or other apparatus. The required structure for a variety of these systems will appear from the description given.
- While this invention has been described in relation to certain embodiments, it will be understood by those skilled in the art that other embodiments according to the generic principles disclosed herein, modifications to the disclosed embodiments and changes in the details of construction, arrangement of parts, compositions, processes, structures and materials selection all may be made without departing from the spirit and scope of the invention Changes, including equivalent structures, acts, materials, etc., may be made, within the purview of the appended claims, without departing from the scope and spirit of the invention in its aspects. Thus, it should be understood that the above described embodiments have been provided by way of example rather than as a limitation of the invention and that the specification and drawing(s) are, accordingly, to be regarded in an illustrative rather than a restrictive sense. As such, the invention is not intended to be limited to the embodiments shown above but rather is to be accorded the widest scope consistent with the principles and novel features disclosed in any fashion herein.
Claims (25)
Priority Applications (1)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US11/980,672 US20080071859A1 (en) | 2002-02-14 | 2007-10-31 | Popularity-based selective replication in content delivery network |
Applications Claiming Priority (3)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US10/073,938 US9167036B2 (en) | 2002-02-14 | 2002-02-14 | Managed object replication and delivery |
US11/715,316 US20070174463A1 (en) | 2002-02-14 | 2007-03-08 | Managed object replication and delivery |
US11/980,672 US20080071859A1 (en) | 2002-02-14 | 2007-10-31 | Popularity-based selective replication in content delivery network |
Related Parent Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US11/715,316 Continuation US20070174463A1 (en) | 2002-02-14 | 2007-03-08 | Managed object replication and delivery |
Publications (1)
Publication Number | Publication Date |
---|---|
US20080071859A1 true US20080071859A1 (en) | 2008-03-20 |
Family
ID=27732351
Family Applications (6)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US10/073,938 Active 2025-11-22 US9167036B2 (en) | 2002-02-14 | 2002-02-14 | Managed object replication and delivery |
US11/715,316 Abandoned US20070174463A1 (en) | 2002-02-14 | 2007-03-08 | Managed object replication and delivery |
US11/978,656 Expired - Lifetime US8924466B2 (en) | 2002-02-14 | 2007-10-30 | Server handoff in content delivery network |
US11/980,672 Abandoned US20080071859A1 (en) | 2002-02-14 | 2007-10-31 | Popularity-based selective replication in content delivery network |
US14/887,053 Expired - Lifetime US9992279B2 (en) | 2002-02-14 | 2015-10-19 | Managed object replication and delivery |
US15/997,543 Expired - Lifetime US10979499B2 (en) | 2002-02-14 | 2018-06-04 | Managed object replication and delivery |
Family Applications Before (3)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US10/073,938 Active 2025-11-22 US9167036B2 (en) | 2002-02-14 | 2002-02-14 | Managed object replication and delivery |
US11/715,316 Abandoned US20070174463A1 (en) | 2002-02-14 | 2007-03-08 | Managed object replication and delivery |
US11/978,656 Expired - Lifetime US8924466B2 (en) | 2002-02-14 | 2007-10-30 | Server handoff in content delivery network |
Family Applications After (2)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US14/887,053 Expired - Lifetime US9992279B2 (en) | 2002-02-14 | 2015-10-19 | Managed object replication and delivery |
US15/997,543 Expired - Lifetime US10979499B2 (en) | 2002-02-14 | 2018-06-04 | Managed object replication and delivery |
Country Status (7)
Country | Link |
---|---|
US (6) | US9167036B2 (en) |
EP (1) | EP1474751B1 (en) |
JP (1) | JP4284190B2 (en) |
KR (1) | KR101028639B1 (en) |
CN (1) | CN100498756C (en) |
AU (1) | AU2003210973A1 (en) |
WO (1) | WO2003069437A2 (en) |
Cited By (134)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20090024693A1 (en) * | 2007-07-17 | 2009-01-22 | Jeffrey Mark Achtermann | Method for distributing file content from a selected target depot server in response to multiple client requests |
US20090125569A1 (en) * | 2007-11-08 | 2009-05-14 | Jeffrey Mark Achtermann | Dynamic replication on demand policy based on zones |
US20090248697A1 (en) * | 2008-03-31 | 2009-10-01 | Richardson David R | Cache optimization |
US20090254661A1 (en) * | 2008-04-04 | 2009-10-08 | Level 3 Communications, Llc | Handling long-tail content in a content delivery network (cdn) |
US20090319612A1 (en) * | 2008-06-19 | 2009-12-24 | Brother Kogyo Kabushiki Kaisha | Information distribution system, terminal apparatus, distribution server and introduction server in the information distribution system, and recording medium on which program thereof is recorded |
US20100077056A1 (en) * | 2008-09-19 | 2010-03-25 | Limelight Networks, Inc. | Content delivery network stream server vignette distribution |
US20100088505A1 (en) * | 2008-10-03 | 2010-04-08 | Limelight Networks, Inc. | Content delivery network encryption |
US20100121940A1 (en) * | 2008-11-13 | 2010-05-13 | At&T Corp. | System and Method for Selectively Caching Hot Content in a Content Delivery System |
US20100122305A1 (en) * | 2008-11-12 | 2010-05-13 | Level 3 Communications, Llc | Dynamic processing of streamed content |
US20100198977A1 (en) * | 2006-09-27 | 2010-08-05 | Adobe Systems Incorporated | Automatic live stream trees |
US20100251313A1 (en) * | 2009-03-31 | 2010-09-30 | Comcast Cable Communications, Llc | Bi-directional transfer of media content assets in a content delivery network |
US7908391B1 (en) * | 2008-03-25 | 2011-03-15 | Symantec Corporation | Application streaming and network file system optimization via feature popularity |
US20110072140A1 (en) * | 2008-03-31 | 2011-03-24 | Swaminathan Sivasubramanian | Content management |
US20110082982A1 (en) * | 2009-10-02 | 2011-04-07 | Limelight Networks, Inc. | Content delivery network cache grouping |
US20110314134A1 (en) * | 2008-10-27 | 2011-12-22 | Telefonaktiebolaget L M Ericsson (Publ) | Methods and systems for resuming, transferring or copying a multimedia session |
US8090863B2 (en) | 2010-04-07 | 2012-01-03 | Limelight Networks, Inc. | Partial object distribution in content delivery network |
US20120023530A1 (en) * | 2009-04-10 | 2012-01-26 | Zte Corporation | Content location method and content delivery network node |
US8275874B2 (en) | 2008-03-31 | 2012-09-25 | Amazon Technologies, Inc. | Locality based content distribution |
US8291117B1 (en) | 2012-02-15 | 2012-10-16 | Limelight Networks, Inc. | Scaled domain name service |
US8321588B2 (en) | 2008-11-17 | 2012-11-27 | Amazon Technologies, Inc. | Request routing utilizing client location information |
US8331370B2 (en) | 2009-12-17 | 2012-12-11 | Amazon Technologies, Inc. | Distributed routing architecture |
US8331371B2 (en) | 2009-12-17 | 2012-12-11 | Amazon Technologies, Inc. | Distributed routing architecture |
US8356074B1 (en) | 2012-08-09 | 2013-01-15 | Limelight Networks, Inc. | Inter point of presence split architecture |
US8370452B2 (en) | 2010-12-27 | 2013-02-05 | Limelight Networks, Inc. | Partial object caching |
US8386596B2 (en) | 2008-03-31 | 2013-02-26 | Amazon Technologies, Inc. | Request routing based on class |
US8397073B1 (en) * | 2009-09-04 | 2013-03-12 | Amazon Technologies, Inc. | Managing secure content in a content delivery network |
US8412823B1 (en) | 2009-03-27 | 2013-04-02 | Amazon Technologies, Inc. | Managing tracking information entries in resource cache components |
US8423667B2 (en) | 2008-11-17 | 2013-04-16 | Amazon Technologies, Inc. | Updating routing information based on client location |
US20130124371A1 (en) * | 2011-11-15 | 2013-05-16 | Verizon Patent And Licensing Inc. | Determining local catalog of digital content |
US8447831B1 (en) | 2008-03-31 | 2013-05-21 | Amazon Technologies, Inc. | Incentive driven content delivery |
US8452874B2 (en) | 2010-11-22 | 2013-05-28 | Amazon Technologies, Inc. | Request routing processing |
US8458250B2 (en) | 2008-06-30 | 2013-06-04 | Amazon Technologies, Inc. | Request routing using network computing components |
US8463877B1 (en) | 2009-03-27 | 2013-06-11 | Amazon Technologies, Inc. | Dynamically translating resource identifiers for request routing using popularitiy information |
US8468247B1 (en) | 2010-09-28 | 2013-06-18 | Amazon Technologies, Inc. | Point of presence management in request routing |
US8495220B2 (en) | 2008-11-17 | 2013-07-23 | Amazon Technologies, Inc. | Managing CDN registration by a storage provider |
EP2624524A1 (en) * | 2012-02-02 | 2013-08-07 | Comcast Cable Communications, LLC | Content distribution network supporting popularity-based caching |
US8510448B2 (en) | 2008-11-17 | 2013-08-13 | Amazon Technologies, Inc. | Service provider registration by a content broker |
US8521880B1 (en) | 2008-11-17 | 2013-08-27 | Amazon Technologies, Inc. | Managing content delivery network service providers |
US8521851B1 (en) | 2009-03-27 | 2013-08-27 | Amazon Technologies, Inc. | DNS query processing using resource identifiers specifying an application broker |
US8533293B1 (en) | 2008-03-31 | 2013-09-10 | Amazon Technologies, Inc. | Client side cache management |
US8543702B1 (en) | 2009-06-16 | 2013-09-24 | Amazon Technologies, Inc. | Managing resources using resource expiration data |
US8549531B2 (en) | 2008-09-29 | 2013-10-01 | Amazon Technologies, Inc. | Optimizing resource configurations |
US8577992B1 (en) | 2010-09-28 | 2013-11-05 | Amazon Technologies, Inc. | Request routing management based on network components |
US8583776B2 (en) | 2008-11-17 | 2013-11-12 | Amazon Technologies, Inc. | Managing content delivery network service providers |
US8601090B1 (en) | 2008-03-31 | 2013-12-03 | Amazon Technologies, Inc. | Network resource identification |
US8626950B1 (en) | 2010-12-03 | 2014-01-07 | Amazon Technologies, Inc. | Request routing processing |
US20140032714A1 (en) * | 2012-07-27 | 2014-01-30 | Interdigital Patent Holdings, Inc. | Method and apparatus for publishing location information for a content object |
US8667127B2 (en) | 2009-03-24 | 2014-03-04 | Amazon Technologies, Inc. | Monitoring web site content |
US8732309B1 (en) | 2008-11-17 | 2014-05-20 | Amazon Technologies, Inc. | Request routing utilizing cost information |
EP2738979A1 (en) * | 2011-08-16 | 2014-06-04 | Huawei Technologies Co., Ltd. | Data stream reused transmission method, duplicate point device and system |
US8756341B1 (en) * | 2009-03-27 | 2014-06-17 | Amazon Technologies, Inc. | Request routing utilizing popularity information |
US20140173229A1 (en) * | 2012-12-17 | 2014-06-19 | International Business Machines Corporation | Method and Apparatus for Automated Migration of Data Among Storage Centers |
US8762526B2 (en) | 2008-09-29 | 2014-06-24 | Amazon Technologies, Inc. | Optimizing content management |
US8788671B2 (en) | 2008-11-17 | 2014-07-22 | Amazon Technologies, Inc. | Managing content delivery network service providers by a content broker |
US8819283B2 (en) | 2010-09-28 | 2014-08-26 | Amazon Technologies, Inc. | Request routing in a networked environment |
US8843625B2 (en) | 2008-09-29 | 2014-09-23 | Amazon Technologies, Inc. | Managing network data display |
US8886814B2 (en) | 2008-02-28 | 2014-11-11 | Level 3 Communications, Llc | Load-balancing cluster |
US8924528B1 (en) | 2010-09-28 | 2014-12-30 | Amazon Technologies, Inc. | Latency measurement in resource requests |
US8930513B1 (en) | 2010-09-28 | 2015-01-06 | Amazon Technologies, Inc. | Latency measurement in resource requests |
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 |
WO2014195906A3 (en) * | 2013-06-06 | 2015-04-16 | Ericsson Television Inc. | Defragmentation of adaptive streaming segment files in a content delivery network |
US9015348B2 (en) | 2013-07-19 | 2015-04-21 | Limelight Networks, Inc. | Dynamically selecting between acceleration techniques based on content request attributes |
US20150156556A1 (en) * | 2013-12-04 | 2015-06-04 | Wowza Media Systems, LLC | Routing Media Content Based on Monetary Cost |
US9083743B1 (en) | 2012-03-21 | 2015-07-14 | Amazon Technologies, Inc. | Managing request routing information utilizing performance information |
US9088460B2 (en) | 2008-09-29 | 2015-07-21 | Amazon Technologies, Inc. | Managing resource consolidation configurations |
US9106934B2 (en) * | 2013-01-29 | 2015-08-11 | Espial Group Inc. | Distribution of adaptive bit rate live streaming video via hyper-text transfer protocol |
US9135048B2 (en) | 2012-09-20 | 2015-09-15 | Amazon Technologies, Inc. | Automated profiling of resource usage |
US9154551B1 (en) | 2012-06-11 | 2015-10-06 | Amazon Technologies, Inc. | Processing DNS queries to identify pre-processing information |
US9160641B2 (en) | 2008-09-29 | 2015-10-13 | Amazon Technologies, Inc. | Monitoring domain allocation performance |
US9191369B2 (en) | 2009-07-17 | 2015-11-17 | Aryaka Networks, Inc. | Application acceleration as a service system and method |
US9246776B2 (en) | 2009-10-02 | 2016-01-26 | Amazon Technologies, Inc. | Forward-based resource delivery network management techniques |
US9288153B2 (en) | 2010-08-26 | 2016-03-15 | Amazon Technologies, Inc. | Processing encoded content |
US9294391B1 (en) | 2013-06-04 | 2016-03-22 | Amazon Technologies, Inc. | Managing network computing components utilizing request routing |
US9323577B2 (en) | 2012-09-20 | 2016-04-26 | Amazon Technologies, Inc. | Automated profiling of resource usage |
US20160119420A1 (en) * | 2013-05-02 | 2016-04-28 | International Business Machines Corporation | Replication of content to one or more servers |
US9391949B1 (en) | 2010-12-03 | 2016-07-12 | Amazon Technologies, Inc. | Request routing processing |
US9407681B1 (en) | 2010-09-28 | 2016-08-02 | Amazon Technologies, Inc. | Latency measurement in resource requests |
US9444884B2 (en) | 2011-12-31 | 2016-09-13 | Level 3 Communications, Llc | Load-aware load-balancing cluster without a central load balancer |
US9479476B2 (en) | 2008-03-31 | 2016-10-25 | Amazon Technologies, Inc. | Processing of DNS queries |
US9495338B1 (en) | 2010-01-28 | 2016-11-15 | Amazon Technologies, Inc. | Content distribution network |
US9525659B1 (en) | 2012-09-04 | 2016-12-20 | Amazon Technologies, Inc. | Request routing utilizing point of presence load information |
US9628554B2 (en) | 2012-02-10 | 2017-04-18 | Amazon Technologies, Inc. | Dynamic content delivery |
US9712484B1 (en) | 2010-09-28 | 2017-07-18 | Amazon Technologies, Inc. | Managing request routing information utilizing client identifiers |
US9742795B1 (en) | 2015-09-24 | 2017-08-22 | Amazon Technologies, Inc. | Mitigating network attacks |
US9762692B2 (en) | 2008-04-04 | 2017-09-12 | Level 3 Communications, Llc | Handling long-tail content in a content delivery network (CDN) |
US9774619B1 (en) | 2015-09-24 | 2017-09-26 | Amazon Technologies, Inc. | Mitigating network attacks |
US9787775B1 (en) | 2010-09-28 | 2017-10-10 | Amazon Technologies, Inc. | Point of presence management in request routing |
US9794281B1 (en) | 2015-09-24 | 2017-10-17 | Amazon Technologies, Inc. | Identifying sources of network attacks |
US9800690B1 (en) | 2009-06-26 | 2017-10-24 | Tata Communications (America) Inc. | Content-based redirection |
US9819567B1 (en) | 2015-03-30 | 2017-11-14 | Amazon Technologies, Inc. | Traffic surge management for points of presence |
US9832492B2 (en) | 2013-01-29 | 2017-11-28 | Espial Group Inc. | Distribution of adaptive bit rate video streaming via hyper-text transfer protocol |
US9832141B1 (en) | 2015-05-13 | 2017-11-28 | Amazon Technologies, Inc. | Routing based request correlation |
US9887931B1 (en) | 2015-03-30 | 2018-02-06 | Amazon Technologies, Inc. | Traffic surge management for points of presence |
US9887932B1 (en) | 2015-03-30 | 2018-02-06 | Amazon Technologies, Inc. | Traffic surge management for points of presence |
US9912740B2 (en) | 2008-06-30 | 2018-03-06 | Amazon Technologies, Inc. | Latency measurement in resource requests |
US9992279B2 (en) | 2002-02-14 | 2018-06-05 | Level 3 Communications, Llc | Managed object replication and delivery |
US9992086B1 (en) | 2016-08-23 | 2018-06-05 | Amazon Technologies, Inc. | External health checking of virtual private cloud network environments |
US10021179B1 (en) | 2012-02-21 | 2018-07-10 | Amazon Technologies, Inc. | Local resource delivery network |
US10033691B1 (en) | 2016-08-24 | 2018-07-24 | Amazon Technologies, Inc. | Adaptive resolution of domain name requests in virtual private cloud network environments |
US10033627B1 (en) | 2014-12-18 | 2018-07-24 | Amazon Technologies, Inc. | Routing mode and point-of-presence selection service |
US10033804B2 (en) | 2011-03-02 | 2018-07-24 | Comcast Cable Communications, Llc | Delivery of content |
US10049051B1 (en) | 2015-12-11 | 2018-08-14 | Amazon Technologies, Inc. | Reserved cache space in content delivery networks |
US10075551B1 (en) | 2016-06-06 | 2018-09-11 | Amazon Technologies, Inc. | Request management for hierarchical cache |
US10091096B1 (en) | 2014-12-18 | 2018-10-02 | Amazon Technologies, Inc. | Routing mode and point-of-presence selection service |
US10097566B1 (en) | 2015-07-31 | 2018-10-09 | Amazon Technologies, Inc. | Identifying targets of network attacks |
US10097448B1 (en) | 2014-12-18 | 2018-10-09 | Amazon Technologies, Inc. | Routing mode and point-of-presence selection service |
US10110694B1 (en) | 2016-06-29 | 2018-10-23 | Amazon Technologies, Inc. | Adaptive transfer rate for retrieving content from a server |
US10205698B1 (en) | 2012-12-19 | 2019-02-12 | Amazon Technologies, Inc. | Source-dependent address resolution |
US10225326B1 (en) | 2015-03-23 | 2019-03-05 | Amazon Technologies, Inc. | Point of presence based data uploading |
US10257307B1 (en) | 2015-12-11 | 2019-04-09 | Amazon Technologies, Inc. | Reserved cache space in content delivery networks |
US10269077B2 (en) * | 2014-06-09 | 2019-04-23 | Visa International Service Association | Systems and methods to detect changes in merchant identification information |
US10270878B1 (en) | 2015-11-10 | 2019-04-23 | Amazon Technologies, Inc. | Routing for origin-facing points of presence |
US10348639B2 (en) | 2015-12-18 | 2019-07-09 | Amazon Technologies, Inc. | Use of virtual endpoints to improve data transmission rates |
US10372499B1 (en) | 2016-12-27 | 2019-08-06 | Amazon Technologies, Inc. | Efficient region selection system for executing request-driven code |
US10433013B2 (en) * | 2011-06-06 | 2019-10-01 | Comcast Cable Communications, Llc | Dynamic management of audiovisual and data communications |
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 |
US10462025B2 (en) | 2008-09-29 | 2019-10-29 | Amazon Technologies, Inc. | Monitoring performance and operation of data exchanges |
US10469513B2 (en) | 2016-10-05 | 2019-11-05 | Amazon Technologies, Inc. | Encrypted network addresses |
US10503613B1 (en) | 2017-04-21 | 2019-12-10 | Amazon Technologies, Inc. | Efficient serving of resources during server unavailability |
US10592578B1 (en) | 2018-03-07 | 2020-03-17 | Amazon Technologies, Inc. | Predictive content push-enabled content delivery network |
US10616179B1 (en) | 2015-06-25 | 2020-04-07 | Amazon Technologies, Inc. | Selective routing of domain name system (DNS) requests |
US10623408B1 (en) | 2012-04-02 | 2020-04-14 | Amazon Technologies, Inc. | Context sensitive object management |
US10831549B1 (en) | 2016-12-27 | 2020-11-10 | Amazon Technologies, Inc. | Multi-region request-driven code execution system |
US10862852B1 (en) | 2018-11-16 | 2020-12-08 | Amazon Technologies, Inc. | Resolution of domain name requests in heterogeneous network environments |
US10924573B2 (en) | 2008-04-04 | 2021-02-16 | Level 3 Communications, Llc | Handling long-tail content in a content delivery network (CDN) |
US10938884B1 (en) | 2017-01-30 | 2021-03-02 | Amazon Technologies, Inc. | Origin server cloaking using virtual private cloud network environments |
US10958501B1 (en) | 2010-09-28 | 2021-03-23 | Amazon Technologies, Inc. | Request routing information based on client IP groupings |
US11025747B1 (en) | 2018-12-12 | 2021-06-01 | Amazon Technologies, Inc. | Content request pattern-based routing system |
US11075987B1 (en) | 2017-06-12 | 2021-07-27 | Amazon Technologies, Inc. | Load estimating content delivery network |
US20220086254A1 (en) * | 2007-07-19 | 2022-03-17 | Akamai Technologies, Inc. | Content delivery network (CDN) cold content handling |
US11290418B2 (en) | 2017-09-25 | 2022-03-29 | Amazon Technologies, Inc. | Hybrid content request routing system |
US11323510B2 (en) | 2008-02-28 | 2022-05-03 | Level 3 Communications, Llc | Load-balancing cluster |
US11604667B2 (en) | 2011-04-27 | 2023-03-14 | Amazon Technologies, Inc. | Optimized deployment based upon customer locality |
Families Citing this family (90)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20030204602A1 (en) | 2002-04-26 | 2003-10-30 | Hudson Michael D. | Mediated multi-source peer content delivery network architecture |
US7457312B2 (en) * | 2002-06-19 | 2008-11-25 | Microsoft Corporation | Bandwidth sharing in advanced streaming format |
US8117328B2 (en) * | 2002-06-25 | 2012-02-14 | Microsoft Corporation | System and method for automatically recovering from failed network connections in streaming media scenarios |
US7290057B2 (en) * | 2002-08-20 | 2007-10-30 | Microsoft Corporation | Media streaming of web content data |
KR100895146B1 (en) * | 2002-10-19 | 2009-05-04 | 엘지전자 주식회사 | Method for controling home network |
US7487224B2 (en) * | 2002-12-19 | 2009-02-03 | At&T Intelletual Property I, L.P. | Methods and systems for routing requests using edge network elements |
US7376754B2 (en) * | 2003-02-27 | 2008-05-20 | Bea Systems, Inc. | System and method for communications between servers in a cluster |
US7529723B2 (en) * | 2003-12-15 | 2009-05-05 | Xerox Corporation | Multi-tiered structure for file sharing based on social roles |
US20110213879A1 (en) * | 2010-03-01 | 2011-09-01 | Ashley Edwardo King | Multi-level Decision Support in a Content Delivery Network |
US9325805B2 (en) | 2004-08-02 | 2016-04-26 | Steve J Shattil | Content delivery in wireless wide area networks |
JP4586203B2 (en) * | 2004-12-01 | 2010-11-24 | ブラザー工業株式会社 | Data sharing system, duplicate content data storage control device, etc. |
US10042927B2 (en) * | 2006-04-24 | 2018-08-07 | Yeildbot Inc. | Interest keyword identification |
US8145778B2 (en) * | 2006-07-28 | 2012-03-27 | Cisco Technology, Inc. | Method and system for transitioning streamed digital video content between stream servers in a digital video network |
US8255457B2 (en) * | 2006-09-01 | 2012-08-28 | Microsoft Corporation | Adaptive content load balancing |
US8806045B2 (en) * | 2006-09-01 | 2014-08-12 | Microsoft Corporation | Predictive popular content replication |
CN100525378C (en) * | 2006-11-17 | 2009-08-05 | 华为技术有限公司 | Management method, system and device to update distributed set top box |
KR101409991B1 (en) | 2007-04-16 | 2014-06-20 | 삼성전자주식회사 | Method and apparatus for data transfer in peer-to-peer network |
US20090138480A1 (en) * | 2007-08-29 | 2009-05-28 | Chatley Scott P | Filing system and method for data files stored in a distributed communications network |
WO2009039123A2 (en) * | 2007-09-17 | 2009-03-26 | Metabyte, Inc. | Copying a web element with reassigned permissions |
US8248983B2 (en) * | 2008-04-25 | 2012-08-21 | Clearwire Ip Holdings Llc | Method and system for controlling the provision of media content to mobile stations |
EP2134063B1 (en) * | 2008-05-12 | 2013-10-02 | BlackBerry Limited | Methods and apparatus for use in facilitating access to a communication service via WLAN hotspot |
US8458290B2 (en) | 2011-02-01 | 2013-06-04 | Limelight Networks, Inc. | Multicast mapped look-up on content delivery networks |
US8051166B1 (en) | 2008-09-29 | 2011-11-01 | Amazon Technologies, Inc. | Service provider optimization of content management |
US8135840B2 (en) * | 2008-11-20 | 2012-03-13 | At&T Intellectual Property I, Lp | Systems and methods for directing content requests to servers |
US20110040792A1 (en) * | 2009-08-12 | 2011-02-17 | Russell Perry | Stored Object Replication |
EP2467786B1 (en) * | 2009-08-17 | 2019-07-31 | Akamai Technologies, Inc. | Method and system for http-based stream delivery |
US20140289623A1 (en) * | 2009-11-06 | 2014-09-25 | Adobe Systems Incorporated | Methods and Systems for Using Proxies to Noninvasively Alter Media Experiences |
US8325730B2 (en) * | 2009-12-17 | 2012-12-04 | Amazon Technologies, Inc. | Distributed routing architecture |
JP5381693B2 (en) * | 2009-12-25 | 2014-01-08 | 日本電気株式会社 | Content replacement system, content replacement method, and content replacement program |
US8769139B2 (en) * | 2010-01-29 | 2014-07-01 | Clarendon Foundation, Inc. | Efficient streaming server |
US10419533B2 (en) | 2010-03-01 | 2019-09-17 | Genghiscomm Holdings, LLC | Edge server selection for device-specific network topologies |
US11330046B2 (en) | 2010-03-01 | 2022-05-10 | Tybalt, Llc | Content delivery in wireless wide area networks |
US20120265853A1 (en) * | 2010-12-17 | 2012-10-18 | Akamai Technologies, Inc. | Format-agnostic streaming architecture using an http network for streaming |
US8880633B2 (en) | 2010-12-17 | 2014-11-04 | Akamai Technologies, Inc. | Proxy server with byte-based include interpreter |
CN102546711B (en) * | 2010-12-20 | 2014-12-31 | 中国移动通信集团公司 | Storage adjustment method, device and system for contents in streaming media system |
US8291083B2 (en) | 2011-02-01 | 2012-10-16 | Limelight Networks, Inc. | Distributed landing pad and brick topology for content storage in content delivery networks |
US8521813B2 (en) * | 2011-02-01 | 2013-08-27 | Limelight Networks, Inc. | Content replication workflow in content delivery networks |
US8396970B2 (en) | 2011-02-01 | 2013-03-12 | Limelight Networks, Inc. | Content processing between locations workflow in content delivery networks |
EP2671165A1 (en) * | 2011-02-01 | 2013-12-11 | Limelight Networks, Inc. | Asset management architecture for content delivery networks |
US8478858B2 (en) | 2011-02-01 | 2013-07-02 | Limelight Networks, Inc. | Policy management for content storage in content delivery networks |
US8615577B2 (en) | 2011-02-01 | 2013-12-24 | Limelight Networks, Inc. | Policy based processing of content objects in a content delivery network using mutators |
FR2973978A1 (en) | 2011-04-08 | 2012-10-12 | France Telecom | METHOD OF COMMUNICATION BETWEEN DIGITAL CONTENT DISTRIBUTION NETWORKS |
EP2523423B1 (en) * | 2011-05-10 | 2019-01-02 | Deutsche Telekom AG | Method and system for providing a distributed scalable hosting environment for web services |
US9282158B2 (en) | 2011-06-06 | 2016-03-08 | Google Inc. | Reducing redirects |
US8745122B2 (en) * | 2011-06-14 | 2014-06-03 | At&T Intellectual Property I, L.P. | System and method for providing an adjunct device in a content delivery network |
US8577963B2 (en) | 2011-06-30 | 2013-11-05 | Amazon Technologies, Inc. | Remote browsing session between client browser and network based browser |
US9621406B2 (en) | 2011-06-30 | 2017-04-11 | Amazon Technologies, Inc. | Remote browsing session management |
CN102868542B (en) * | 2011-07-04 | 2018-02-16 | 中兴通讯股份有限公司 | The control method and system of service quality in a kind of service delivery network |
US8510807B1 (en) * | 2011-08-16 | 2013-08-13 | Edgecast Networks, Inc. | Real-time granular statistical reporting for distributed platforms |
US9195768B2 (en) | 2011-08-26 | 2015-11-24 | Amazon Technologies, Inc. | Remote browsing session management |
US10089403B1 (en) | 2011-08-31 | 2018-10-02 | Amazon Technologies, Inc. | Managing network based storage |
US8914514B1 (en) * | 2011-09-27 | 2014-12-16 | Amazon Technologies, Inc. | Managing network based content |
US9178955B1 (en) * | 2011-09-27 | 2015-11-03 | Amazon Technologies, Inc. | Managing network based content |
US20130097277A1 (en) * | 2011-10-12 | 2013-04-18 | Electronics And Telecommunications Research Institute | Method and apparatus for load balancing of content-centric network |
US8782004B2 (en) * | 2012-01-23 | 2014-07-15 | Palantir Technologies, Inc. | Cross-ACL multi-master replication |
US20130219021A1 (en) * | 2012-02-16 | 2013-08-22 | International Business Machines Corporation | Predictive caching for telecommunication towers using propagation of identification of items of high demand data at a geographic level |
US8447854B1 (en) * | 2012-12-04 | 2013-05-21 | Limelight Networks, Inc. | Edge analytics query for distributed content network |
JP5896357B2 (en) * | 2012-12-05 | 2016-03-30 | 株式会社Murakumo | Information processing apparatus, method, and program |
US9595205B2 (en) * | 2012-12-18 | 2017-03-14 | Neuron Fuel, Inc. | Systems and methods for goal-based programming instruction |
US10404834B1 (en) * | 2013-03-11 | 2019-09-03 | Amazon Technologies, Inc. | Dynamic verification of application data using deterministic functions |
CN105706412B (en) * | 2013-07-03 | 2019-09-24 | 爱立信股份有限公司 | Band-width tactics management in self-correcting content delivery network |
US10841353B2 (en) | 2013-11-01 | 2020-11-17 | Ericsson Ab | System and method for optimizing defragmentation of content in a content delivery network |
US9113182B2 (en) * | 2013-12-04 | 2015-08-18 | Wowza Media Systems, LLC | Selecting a media content source based on monetary cost |
CN103747072A (en) * | 2013-12-30 | 2014-04-23 | 乐视网信息技术(北京)股份有限公司 | Data reading and writing method and application server |
US10460098B1 (en) | 2014-08-20 | 2019-10-29 | Google Llc | Linking devices using encrypted account identifiers |
CN104320487B (en) * | 2014-11-11 | 2018-03-20 | 网宿科技股份有限公司 | The HTTP scheduling system and method for content distributing network |
US9241174B1 (en) * | 2014-11-18 | 2016-01-19 | Concurrent Computer Corporation | Demand-based edge caching video content system and methods |
US9769248B1 (en) | 2014-12-16 | 2017-09-19 | Amazon Technologies, Inc. | Performance-based content delivery |
US10027739B1 (en) | 2014-12-16 | 2018-07-17 | Amazon Technologies, Inc. | Performance-based content delivery |
US10311372B1 (en) | 2014-12-19 | 2019-06-04 | Amazon Technologies, Inc. | Machine learning based content delivery |
US10311371B1 (en) | 2014-12-19 | 2019-06-04 | Amazon Technologies, Inc. | Machine learning based content delivery |
US10225365B1 (en) | 2014-12-19 | 2019-03-05 | Amazon Technologies, Inc. | Machine learning based content delivery |
US10630771B1 (en) | 2015-02-26 | 2020-04-21 | Akamai Technologies, Inc. | Content delivery network with network storage and support for on-demand content upload |
US9892005B2 (en) * | 2015-05-21 | 2018-02-13 | Zerto Ltd. | System and method for object-based continuous data protection |
US10362134B2 (en) * | 2016-08-15 | 2019-07-23 | Verizon Digital Media Services Inc. | Peer cache filling |
CN107888636B (en) * | 2016-09-30 | 2020-01-17 | 杭州海康威视数字技术股份有限公司 | Data processing method and system based on cloud storage |
US10924583B2 (en) * | 2016-11-23 | 2021-02-16 | Level 3 Communications, Llc | Overload handling in a content delivery network (CDN) |
US10313223B2 (en) * | 2016-12-14 | 2019-06-04 | Level 3 Communications, Llc | Object integrity verification in a content delivery network (CDN) |
CN108509103A (en) * | 2017-02-27 | 2018-09-07 | 华为技术有限公司 | Text clone method and touch-screen equipment |
WO2018169083A1 (en) * | 2017-03-16 | 2018-09-20 | ソフトバンク株式会社 | Relay device and program |
US10749945B2 (en) * | 2017-10-09 | 2020-08-18 | Level 3 Communications, Llc | Cross-cluster direct server return with anycast rendezvous in a content delivery network (CDN) |
US10715561B2 (en) | 2018-04-11 | 2020-07-14 | Cisco Technology, Inc. | Reanchoring devices on servers |
CN108337327A (en) * | 2018-04-26 | 2018-07-27 | 拉扎斯网络科技(上海)有限公司 | A kind of resource acquiring method and proxy server |
US10884820B1 (en) * | 2018-08-31 | 2021-01-05 | Veritas Technologies Llc | Intelligent and automatic replication load score based load balancing and resiliency of replication appliances |
JP7150584B2 (en) | 2018-12-06 | 2022-10-11 | エヌ・ティ・ティ・コミュニケーションズ株式会社 | Edge server and its program |
JP7175731B2 (en) * | 2018-12-06 | 2022-11-21 | エヌ・ティ・ティ・コミュニケーションズ株式会社 | Storage management device, method and program |
JP7150585B2 (en) * | 2018-12-06 | 2022-10-11 | エヌ・ティ・ティ・コミュニケーションズ株式会社 | Data retrieval device, its data retrieval method and program, edge server and its program |
US11113114B2 (en) | 2019-04-09 | 2021-09-07 | Cisco Technology, Inc. | Distributed object placement, replication, and retrieval for cloud-scale storage and data delivery |
AU2020274472A1 (en) * | 2019-05-14 | 2021-11-25 | Level 3 Communications, Llc | Cache management in content delivery systems |
IT202000017023A1 (en) * | 2020-07-14 | 2022-01-14 | Mainstreaming S P A | METHOD FOR DISTRIBUTING FILES THROUGH A CONTENT DELIVERY NETWORK ALSO BASED ON ARTIFICIAL INTELLIGENCE ALGORITHMS, TELEMATIC SYSTEM AND SERVERS THAT ALLOW TO IMPLEMENT IT |
Citations (74)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US5568181A (en) * | 1993-12-09 | 1996-10-22 | International Business Machines Corporation | Multimedia distribution over wide area networks |
US5614940A (en) * | 1994-10-21 | 1997-03-25 | Intel Corporation | Method and apparatus for providing broadcast information with indexing |
US5734719A (en) * | 1993-10-15 | 1998-03-31 | International Business Systems, Incorporated | Digital information accessing, delivery and production system |
US5778187A (en) * | 1996-05-09 | 1998-07-07 | Netcast Communications Corp. | Multicasting method and apparatus |
US5777988A (en) * | 1996-04-17 | 1998-07-07 | Bell Communications Research, Inc. | System and method for equalizing delay in a dynamic packet switching network |
US5781909A (en) * | 1996-02-13 | 1998-07-14 | Microtouch Systems, Inc. | Supervised satellite kiosk management system with combined local and remote data storage |
US5819092A (en) * | 1994-11-08 | 1998-10-06 | Vermeer Technologies, Inc. | Online service development tool with fee setting capabilities |
US5832069A (en) * | 1995-11-17 | 1998-11-03 | Sprint Communications Co L.P. | Object oriented system for modeling telecommunications circuits to estimate the access cost for leasing selected circuits |
US5845090A (en) * | 1994-02-14 | 1998-12-01 | Platinium Technology, Inc. | System for software distribution in a digital computer network |
US5898456A (en) * | 1995-04-25 | 1999-04-27 | Alcatel N.V. | Communication system with hierarchical server structure |
US5913028A (en) * | 1995-10-06 | 1999-06-15 | Xpoint Technologies, Inc. | Client/server data traffic delivery system and method |
US5933835A (en) * | 1995-09-29 | 1999-08-03 | Intel Corporation | Method and apparatus for managing multimedia data files in a computer network by streaming data files into separate streams based on file attributes |
US5940831A (en) * | 1996-08-28 | 1999-08-17 | Nec Corporation | Hypermedia system and method of managing directories and directory data originating from a node link structure in a directory server |
US5951694A (en) * | 1995-06-07 | 1999-09-14 | Microsoft Corporation | Method of redirecting a client service session to a second application server without interrupting the session by forwarding service-specific information to the second server |
US6016512A (en) * | 1997-11-20 | 2000-01-18 | Telcordia Technologies, Inc. | Enhanced domain name service using a most frequently used domain names table and a validity code table |
US6016509A (en) * | 1994-05-16 | 2000-01-18 | Intel Corporation | General purpose metering mechanism for distribution of electronic information |
US6023470A (en) * | 1996-05-17 | 2000-02-08 | Lee; Warren S. | Point of presence (POP) for digital facsimile network with virtual POPs used to communicate with other networks |
US6078943A (en) * | 1997-02-07 | 2000-06-20 | International Business Machines Corporation | Method and apparatus for dynamic interval-based load balancing |
US6081835A (en) * | 1996-04-04 | 2000-06-27 | British Telecommunications Public Limited Company | Internet server and method of controlling an internet server |
US6081840A (en) * | 1997-10-14 | 2000-06-27 | Zhao; Yan | Two-level content distribution system |
US6085193A (en) * | 1997-09-29 | 2000-07-04 | International Business Machines Corporation | Method and system for dynamically prefetching information via a server hierarchy |
US6094706A (en) * | 1998-03-02 | 2000-07-25 | International Business Machines Corporation | Caching in a data processing system using the pigeon hole principle |
US6098096A (en) * | 1996-12-09 | 2000-08-01 | Sun Microsystems, Inc. | Method and apparatus for dynamic cache preloading across a network |
US6115752A (en) * | 1998-05-21 | 2000-09-05 | Sun Microsystems, Inc. | System and method for server selection for mirrored sites |
US6128623A (en) * | 1998-04-15 | 2000-10-03 | Inktomi Corporation | High performance object cache |
US6130890A (en) * | 1998-09-11 | 2000-10-10 | Digital Island, Inc. | Method and system for optimizing routing of data packets |
US6131095A (en) * | 1996-12-11 | 2000-10-10 | Hewlett-Packard Company | Method of accessing a target entity over a communications network |
US6161137A (en) * | 1997-03-31 | 2000-12-12 | Mshow.Com, Inc. | Method and system for providing a presentation on a network |
US6185598B1 (en) * | 1998-02-10 | 2001-02-06 | Digital Island, Inc. | Optimized network resource location |
US6233623B1 (en) * | 1996-01-11 | 2001-05-15 | Cabletron Systems, Inc. | Replicated resource management system for managing resources in a distributed application and maintaining a relativistic view of state |
US6240462B1 (en) * | 1997-10-14 | 2001-05-29 | At&T | System for providing enhanced grade of service for connections over a large network |
US6266335B1 (en) * | 1997-12-19 | 2001-07-24 | Cyberiq Systems | Cross-platform server clustering using a network flow switch |
US6275470B1 (en) * | 1999-06-18 | 2001-08-14 | Digital Island, Inc. | On-demand overlay routing for computer-based communication networks |
US6317787B1 (en) * | 1998-08-11 | 2001-11-13 | Webtrends Corporation | System and method for analyzing web-server log files |
US6324582B1 (en) * | 1997-07-01 | 2001-11-27 | Sitara Networks, Inc. | Enhanced network communication |
US6324580B1 (en) * | 1998-09-03 | 2001-11-27 | Sun Microsystems, Inc. | Load balancing for replicated services |
US20010049732A1 (en) * | 2000-06-01 | 2001-12-06 | Raciborski Nathan F. | Content exchange apparatus |
US20010051980A1 (en) * | 2000-06-01 | 2001-12-13 | Raciborski Nathan F. | Preloading content objects on content exchanges |
US6332157B1 (en) * | 1996-06-03 | 2001-12-18 | Webtv Networks, Inc. | Method of accessing multiple services from multiple service providers |
US6343298B1 (en) * | 1997-04-03 | 2002-01-29 | Microsoft Corporation | Seamless multimedia branching |
US6345294B1 (en) * | 1999-04-19 | 2002-02-05 | Cisco Technology, Inc. | Methods and apparatus for remote configuration of an appliance on a network |
US6351775B1 (en) * | 1997-05-30 | 2002-02-26 | International Business Machines Corporation | Loading balancing across servers in a computer network |
US6351776B1 (en) * | 1999-11-04 | 2002-02-26 | Xdrive, Inc. | Shared internet storage resource, user interface system, and method |
US6389462B1 (en) * | 1998-12-16 | 2002-05-14 | Lucent Technologies Inc. | Method and apparatus for transparently directing requests for web objects to proxy caches |
US20020078233A1 (en) * | 2000-05-12 | 2002-06-20 | Alexandros Biliris | Method and apparatus for content distribution network brokering and peering |
US6415368B1 (en) * | 1999-12-22 | 2002-07-02 | Xerox Corporation | System and method for caching |
US20020087797A1 (en) * | 2000-12-29 | 2002-07-04 | Farid Adrangi | System and method for populating cache servers with popular media contents |
US20020092026A1 (en) * | 2001-01-09 | 2002-07-11 | International Business Machines Corporation | Method and apparatus for broadcast delivery of content to a client-side cache based on user preferences |
US6421714B1 (en) * | 1997-10-14 | 2002-07-16 | Lucent Technologies | Efficient mobility management scheme for a wireless internet access system |
US6427170B1 (en) * | 1998-12-08 | 2002-07-30 | Cisco Technology, Inc. | Integrated IP address management |
US6442588B1 (en) * | 1998-08-20 | 2002-08-27 | At&T Corp. | Method of administering a dynamic filtering firewall |
US6463454B1 (en) * | 1999-06-17 | 2002-10-08 | International Business Machines Corporation | System and method for integrated load distribution and resource management on internet environment |
US6466949B2 (en) * | 1998-11-23 | 2002-10-15 | Myway.Com Corporation | Performing event notification in a database having a distributed web cluster |
US20020152318A1 (en) * | 2001-03-02 | 2002-10-17 | Menon Satish N. | Metadata enabled push-pull model for efficient low-latency video-content distribution over a network |
US20020163882A1 (en) * | 2001-03-01 | 2002-11-07 | Akamai Technologies, Inc. | Optimal route selection in a content delivery network |
US6487555B1 (en) * | 1999-05-07 | 2002-11-26 | Alta Vista Company | Method and apparatus for finding mirrored hosts by analyzing connectivity and IP addresses |
US6502205B1 (en) * | 1993-04-23 | 2002-12-31 | Emc Corporation | Asynchronous remote data mirroring system |
US20030031176A1 (en) * | 2000-10-26 | 2003-02-13 | Sim Siew Yong | Method and apparatus for distributing large payload file to a plurality of storage devices in a network |
US6591288B1 (en) * | 1998-05-19 | 2003-07-08 | Nortel Networks Limited | Data network accelerated access system |
US6594260B1 (en) * | 1999-09-03 | 2003-07-15 | Cisco Technology, Inc. | Content routing |
US6598121B2 (en) * | 1998-08-28 | 2003-07-22 | International Business Machines, Corp. | System and method for coordinated hierarchical caching and cache replacement |
US20030149581A1 (en) * | 2002-08-28 | 2003-08-07 | Imran Chaudhri | Method and system for providing intelligent network content delivery |
US20030158923A1 (en) * | 2000-05-04 | 2003-08-21 | Reed Burkhart | System and method for automated negotiation for and allocation of a broadcast satellite, communication and caching system resource |
US6678659B1 (en) * | 1997-06-20 | 2004-01-13 | Swisscom Ag | System and method of voice information dissemination over a network using semantic representation |
US6732237B1 (en) * | 2000-08-29 | 2004-05-04 | Oracle International Corporation | Multi-tier caching system |
US6741990B2 (en) * | 2001-05-23 | 2004-05-25 | Intel Corporation | System and method for efficient and adaptive web accesses filtering |
US6785704B1 (en) * | 1999-12-20 | 2004-08-31 | Fastforward Networks | Content distribution system for operation over an internetwork including content peering arrangements |
US6839758B2 (en) * | 2001-09-28 | 2005-01-04 | Intel Corporation | Network processor for cache array routing |
US20050021863A1 (en) * | 2000-06-23 | 2005-01-27 | Cloudshield Technologies, Inc. | Apparatus and method for virtual edge placement of web sites |
US6859840B2 (en) * | 2001-01-29 | 2005-02-22 | Kasenna, Inc. | Prefix caching for media objects |
US6915307B1 (en) * | 1998-04-15 | 2005-07-05 | Inktomi Corporation | High performance object cache |
US6976090B2 (en) * | 2000-04-20 | 2005-12-13 | Actona Technologies Ltd. | Differentiated content and application delivery via internet |
US6999988B2 (en) * | 2000-07-13 | 2006-02-14 | Lucent Technologies Inc. | Method and system for data layout and replacement in distributed streaming caches on the Internet |
US7254645B2 (en) * | 2000-03-30 | 2007-08-07 | Nec Corporation | Quality assured network service provision system compatible with a multi-domain network and service provision method and service broker device |
Family Cites Families (336)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US563399A (en) * | 1896-07-07 | Expansion-pulley | ||
IT1025968B (en) * | 1974-11-25 | 1978-08-30 | Broggi Izar Fab Italiane | MONOBLOCK ALUMINUM CONTAINER NOZZLE FOR AEROSOL |
JPS566626A (en) | 1979-06-29 | 1981-01-23 | Tokyo Shibaura Electric Co | Power supply circuit |
US4495570A (en) | 1981-01-14 | 1985-01-22 | Hitachi, Ltd. | Processing request allocator for assignment of loads in a distributed processing system |
FR2555388B1 (en) | 1983-11-23 | 1986-02-21 | Cit Alcatel | BACKUP DEVICE OF A SUBSCRIBER TERMINAL IN A DIGITAL CONCENTRATOR |
US4803641A (en) | 1984-06-06 | 1989-02-07 | Tecknowledge, Inc. | Basic expert system tool |
US4591983A (en) | 1984-07-09 | 1986-05-27 | Teknowledge, Inc. | Hierarchical knowledge system |
JPS61114363A (en) | 1984-11-07 | 1986-06-02 | Hitachi Ltd | Job transfer system between computer systems |
US4726017A (en) | 1985-05-21 | 1988-02-16 | Fla. | Multidrop data concentrator communication network |
US5287537A (en) | 1985-11-15 | 1994-02-15 | Data General Corporation | Distributed processing system having plural computers each using identical retaining information to identify another computer for executing a received command |
US4922417A (en) | 1986-10-24 | 1990-05-01 | American Telephone And Telegraph Company | Method and apparatus for data hashing using selection from a table of random numbers in combination with folding and bit manipulation of the selected random numbers |
US4943932A (en) | 1986-11-25 | 1990-07-24 | Cimflex Teknowledge Corporation | Architecture for composing computational modules uniformly across diverse developmental frameworks |
US4847784A (en) | 1987-07-13 | 1989-07-11 | Teknowledge, Inc. | Knowledge based tutor |
DE3876617T2 (en) | 1987-09-04 | 1993-04-08 | Digital Equipment Corp | CONNECTION CONTROL IN A NETWORK FOR A DIGITAL DATA PROCESSING SYSTEM THAT SUPPLIES MULTIPLE TRANSMISSION PROTOCOLS. |
US4920432A (en) | 1988-01-12 | 1990-04-24 | Eggers Derek C | System for random access to an audio video data library with independent selection and display at each of a plurality of remote locations |
US5191573A (en) | 1988-06-13 | 1993-03-02 | Hair Arthur R | Method for transmitting a desired digital video or audio signal |
US4949248A (en) | 1988-07-15 | 1990-08-14 | Caro Marshall A | System for shared remote access of multiple application programs executing in one or more computers |
CA1341310C (en) | 1988-07-15 | 2001-10-23 | Robert Filepp | Interactive computer network and method of operation |
US4949187A (en) | 1988-12-16 | 1990-08-14 | Cohen Jason M | Video communications system having a remotely controlled central source of video and audio data |
US5029232A (en) | 1989-01-12 | 1991-07-02 | Cycle-Sat., Inc. | Satellite communications network |
US5341477A (en) | 1989-02-24 | 1994-08-23 | Digital Equipment Corporation | Broker for computer network server selection |
US5287499A (en) | 1989-03-22 | 1994-02-15 | Bell Communications Research, Inc. | Methods and apparatus for information storage and retrieval utilizing a method of hashing and different collision avoidance schemes depending upon clustering in the hash table |
US5471622A (en) | 1989-10-04 | 1995-11-28 | Paralogic, Inc. | Run-time system having nodes for identifying parallel tasks in a logic program and searching for available nodes to execute the parallel tasks |
US5130792A (en) | 1990-02-01 | 1992-07-14 | Usa Video Inc. | Store and forward video system |
US5633999A (en) | 1990-11-07 | 1997-05-27 | Nonstop Networks Limited | Workstation-implemented data storage re-routing for server fault-tolerance on computer networks |
US5172413A (en) | 1990-12-20 | 1992-12-15 | Sasktel | Secure hierarchial video delivery system and method |
US6002720A (en) | 1991-01-07 | 1999-12-14 | H. Lee Browne, D/B/A Greenwich Information Technologies Llc | Audio and video transmission and receiving system |
US5253275A (en) | 1991-01-07 | 1993-10-12 | H. Lee Browne | Audio and video transmission and receiving system |
US5132992A (en) | 1991-01-07 | 1992-07-21 | Paul Yurt | Audio and video transmission and receiving system |
US5253341A (en) | 1991-03-04 | 1993-10-12 | Rozmanith Anthony I | Remote query communication system |
US5590288A (en) | 1991-07-30 | 1996-12-31 | Restaurant Technology, Inc. | Distributed data processing system and method utilizing peripheral device polling and layered communication software |
DE69232164T2 (en) | 1991-08-22 | 2002-07-18 | Sun Microsystems Inc | Network video provider device and method |
US5528281A (en) | 1991-09-27 | 1996-06-18 | Bell Atlantic Network Services | Method and system for accessing multimedia data over public switched telephone network |
US5247347A (en) | 1991-09-27 | 1993-09-21 | Bell Atlantic Network Services, Inc. | Pstn architecture for video-on-demand services |
JP3217821B2 (en) | 1991-12-16 | 2001-10-15 | マツダ株式会社 | Vehicle air conditioner |
US5371532A (en) | 1992-05-15 | 1994-12-06 | Bell Communications Research, Inc. | Communications architecture and method for distributing information services |
US5291554A (en) | 1992-05-28 | 1994-03-01 | Tv Answer, Inc. | Shared-price custom video rentals via interactive TV |
CA2095755C (en) | 1992-08-17 | 1999-01-26 | Mark J. Baugher | Network priority management |
US5442389A (en) | 1992-12-28 | 1995-08-15 | At&T Corp. | Program server for interactive television system |
US5508732A (en) | 1993-03-22 | 1996-04-16 | International Business Machines Corporation | Data server, control server and gateway architecture system and method for broadcasting digital video on demand |
ES2112976T3 (en) | 1993-05-19 | 1998-04-16 | Alsthom Cge Alcatel | VIDEO NETWORK ON REQUEST. |
US5550982A (en) | 1993-06-24 | 1996-08-27 | Starlight Networks | Video application server |
JPH0766829A (en) | 1993-06-30 | 1995-03-10 | Kawasaki Steel Corp | Electronic mail multiplexing system and communication control method in the system |
US5414455A (en) | 1993-07-07 | 1995-05-09 | Digital Equipment Corporation | Segmented video on demand system |
US5442390A (en) | 1993-07-07 | 1995-08-15 | Digital Equipment Corporation | Video on demand with memory accessing and or like functions |
GB2281793A (en) | 1993-09-11 | 1995-03-15 | Ibm | A data processing system for providing user load levelling in a network |
US5446736A (en) | 1993-10-07 | 1995-08-29 | Ast Research, Inc. | Method and apparatus for connecting a node to a wireless network using a standard protocol |
US5542087A (en) | 1993-10-15 | 1996-07-30 | Hewlett-Packard Company | Linear hashing for distributed records |
JPH07212712A (en) | 1993-10-29 | 1995-08-11 | Eastman Kodak Co | Method and equipment for adding and deleting digital watermark in hierarchical picture memory and fetch system |
US5475615A (en) | 1993-12-23 | 1995-12-12 | U S West Advanced Technologies, Inc. | Method and system for sizing interactive video delivery systems |
US5515510A (en) | 1994-01-14 | 1996-05-07 | Consilium Overseas Limited | Communications internetwork system connecting a client node array to a resource array |
US5644714A (en) | 1994-01-14 | 1997-07-01 | Elonex Plc, Ltd. | Video collection and distribution system with interested item notification and download on demand |
US5544327A (en) | 1994-03-01 | 1996-08-06 | International Business Machines Corporation | Load balancing in video-on-demand servers by allocating buffer to streams with successively larger buffer requirements until the buffer requirements of a stream can not be satisfied |
US6185619B1 (en) | 1996-12-09 | 2001-02-06 | Genuity Inc. | Method and apparatus for balancing the process load on network servers according to network and serve based policies |
US5544313A (en) | 1994-05-11 | 1996-08-06 | International Business Machines Corporation | Baton passing optimization scheme for load balancing/configuration planning in a video-on-demand computer system |
JP2601189B2 (en) | 1994-05-20 | 1997-04-16 | 日本電気株式会社 | Video on demand system |
US5694546A (en) | 1994-05-31 | 1997-12-02 | Reisman; Richard R. | System for automatic unattended electronic information transport between a server and a client by a vendor provided transport software with a manifest list |
US5515511A (en) | 1994-06-06 | 1996-05-07 | International Business Machines Corporation | Hybrid digital/analog multimedia hub with dynamically allocated/released channels for video processing and distribution |
US5884028A (en) | 1994-07-29 | 1999-03-16 | International Business Machines Corporation | System for the management of multiple time-critical data streams |
US6038310A (en) | 1994-08-01 | 2000-03-14 | British Telecommunications Public Limited Company | Service node for a telephony network |
US5519435A (en) | 1994-09-01 | 1996-05-21 | Micropolis Corporation | Multi-user, on-demand video storage and retrieval system including video signature computation for preventing excessive instantaneous server data rate |
US5638443A (en) | 1994-11-23 | 1997-06-10 | Xerox Corporation | System for controlling the distribution and use of composite digital works |
US5619648A (en) | 1994-11-30 | 1997-04-08 | Lucent Technologies Inc. | Message filtering techniques |
US5845303A (en) | 1994-12-06 | 1998-12-01 | Netpodium, Inc. | Document processing using frame-based templates with hierarchical tagging |
US5603026A (en) | 1994-12-07 | 1997-02-11 | Xerox Corporation | Application-specific conflict resolution for weakly consistent replicated databases |
US5623656A (en) | 1994-12-15 | 1997-04-22 | Lucent Technologies Inc. | Script-based data communication system and method utilizing state memory |
US5920701A (en) | 1995-01-19 | 1999-07-06 | Starburst Communications Corporation | Scheduling data transmission |
US5592611A (en) | 1995-03-14 | 1997-01-07 | Network Integrity, Inc. | Stand-in computer server |
JP4008049B2 (en) | 1995-03-20 | 2007-11-14 | 富士通株式会社 | Address transmitting apparatus, address transmitting method and address transmitting system |
US5802291A (en) | 1995-03-30 | 1998-09-01 | Sun Microsystems, Inc. | System and method to control and administer distributed object servers using first class distributed objects |
US5699513A (en) | 1995-03-31 | 1997-12-16 | Motorola, Inc. | Method for secure network access via message intercept |
US5680619A (en) | 1995-04-03 | 1997-10-21 | Mfactory, Inc. | Hierarchical encapsulation of instantiated objects in a multimedia authoring system |
EP0826181A4 (en) | 1995-04-11 | 2005-02-09 | Kinetech Inc | Identifying data in a data processing system |
US5742762A (en) | 1995-05-19 | 1998-04-21 | Telogy Networks, Inc. | Network management gateway |
US5646676A (en) | 1995-05-30 | 1997-07-08 | International Business Machines Corporation | Scalable interactive multimedia server system for providing on demand data |
JP2853731B2 (en) | 1995-06-02 | 1999-02-03 | 日本電気株式会社 | Voice recognition device |
US6181867B1 (en) | 1995-06-07 | 2001-01-30 | Intervu, Inc. | Video storage and retrieval system |
CA2221506A1 (en) | 1995-06-07 | 1996-12-27 | Thomas Mark Levergood | Internet server access control and monitoring system |
US6003030A (en) | 1995-06-07 | 1999-12-14 | Intervu, Inc. | System and method for optimized storage and retrieval of data on a distributed computer network |
US5956489A (en) | 1995-06-07 | 1999-09-21 | Microsoft Corporation | Transaction replication system and method for supporting replicated transaction-based services |
US5710918A (en) | 1995-06-07 | 1998-01-20 | International Business Machines Corporation | Method for distributed task fulfillment of web browser requests |
US5799141A (en) | 1995-06-09 | 1998-08-25 | Qualix Group, Inc. | Real-time data protection system and method |
US5682512A (en) | 1995-06-30 | 1997-10-28 | Intel Corporation | Use of deferred bus access for address translation in a shared memory clustered computer system |
US5896533A (en) | 1995-07-06 | 1999-04-20 | Intel Corporation | Accessing internets world-wide web through object linking and embedding technology |
US5666362A (en) | 1995-07-25 | 1997-09-09 | 3Com Corporation | Method and apparatus for asynchronous PPP and synchronous PPP conversion |
US5878212A (en) | 1995-07-31 | 1999-03-02 | At&T Corp. | System for updating mapping or virtual host names to layer-3 address when multimedia server changes its usage state to busy or not busy |
US5649186A (en) | 1995-08-07 | 1997-07-15 | Silicon Graphics Incorporated | System and method for a computer-based dynamic information clipping service |
US5815662A (en) * | 1995-08-15 | 1998-09-29 | Ong; Lance | Predictive memory caching for media-on-demand systems |
US5721914A (en) | 1995-09-14 | 1998-02-24 | Mci Corporation | System and method for hierarchical data distribution |
AU7360896A (en) | 1995-09-15 | 1997-04-17 | Cable & Wireless, Inc. | System and method for quality management |
US5712979A (en) | 1995-09-20 | 1998-01-27 | Infonautics Corporation | Method and apparatus for attaching navigational history information to universal resource locator links on a world wide web page |
US5812769A (en) | 1995-09-20 | 1998-09-22 | Infonautics Corporation | Method and apparatus for redirecting a user to a new location on the world wide web using relative universal resource locators |
US5925142A (en) | 1995-10-06 | 1999-07-20 | Micron Technology, Inc. | Self-test RAM using external synchronous clock |
US5572643A (en) | 1995-10-19 | 1996-11-05 | Judson; David H. | Web browser with dynamic display of information objects during linking |
US6029175A (en) | 1995-10-26 | 2000-02-22 | Teknowledge Corporation | Automatic retrieval of changed files by a network software agent |
US5625781A (en) | 1995-10-31 | 1997-04-29 | International Business Machines Corporation | Itinerary list for interfaces |
US5764906A (en) | 1995-11-07 | 1998-06-09 | Netword Llc | Universal electronic resource denotation, request and delivery system |
US5671279A (en) | 1995-11-13 | 1997-09-23 | Netscape Communications Corporation | Electronic commerce using a secure courier system |
US5777989A (en) | 1995-12-19 | 1998-07-07 | International Business Machines Corporation | TCP/IP host name resolution for machines on several domains |
US5903723A (en) | 1995-12-21 | 1999-05-11 | Intel Corporation | Method and apparatus for transmitting electronic mail attachments with attachment references |
US5740423A (en) | 1995-12-28 | 1998-04-14 | Csg Systems, Inc. | System and method for accessing distributed data on a plurality of databases |
US6098078A (en) | 1995-12-29 | 2000-08-01 | Lucent Technologies Inc. | Maintaining consistency of database replicas |
GB2309558A (en) | 1996-01-26 | 1997-07-30 | Ibm | Load balancing across the processors of a server computer |
US5751961A (en) | 1996-01-31 | 1998-05-12 | Bell Communications Research, Inc. | Integrated internet system for translating logical addresses of internet documents to physical addresses using integrated service control point |
US6081829A (en) | 1996-01-31 | 2000-06-27 | Silicon Graphics, Inc. | General purpose web annotations without modifying browser |
US5659729A (en) | 1996-02-01 | 1997-08-19 | Sun Microsystems, Inc. | Method and system for implementing hypertext scroll attributes |
US5856974A (en) | 1996-02-13 | 1999-01-05 | Novell, Inc. | Internetwork address mapping gateway |
DE69712552T2 (en) | 1996-02-14 | 2003-01-09 | Hitachi Ltd | Method for monitoring a computer system with distribution of performance data to several monitoring processes |
US5751956A (en) | 1996-02-21 | 1998-05-12 | Infoseek Corporation | Method and apparatus for redirection of server external hyper-link references |
US6189030B1 (en) | 1996-02-21 | 2001-02-13 | Infoseek Corporation | Method and apparatus for redirection of server external hyper-link references |
US5761507A (en) | 1996-03-05 | 1998-06-02 | International Business Machines Corporation | Client/server architecture supporting concurrent servers within a server with a transaction manager providing server/connection decoupling |
US6128660A (en) | 1996-03-21 | 2000-10-03 | Hearme | Network match maker |
US5832506A (en) | 1996-03-29 | 1998-11-03 | Intel Corporation | Directory for network servers |
US5867799A (en) | 1996-04-04 | 1999-02-02 | Lang; Andrew K. | Information system and method for filtering a massive flow of information entities to meet user information classification needs |
US5835718A (en) | 1996-04-10 | 1998-11-10 | At&T Corp | URL rewriting pseudo proxy server |
US6044405A (en) | 1996-04-12 | 2000-03-28 | Wam!Net Inc. | Service network incorporating geographically-remote hubs linked by high speed transmission paths |
DE59610895D1 (en) | 1996-04-17 | 2004-02-19 | Siemens Ag | Control device in the intelligent network |
US5828847A (en) | 1996-04-19 | 1998-10-27 | Storage Technology Corporation | Dynamic server switching for maximum server availability and load balancing |
US5894554A (en) | 1996-04-23 | 1999-04-13 | Infospinner, Inc. | System for managing dynamic web page generation requests by intercepting request at web server and routing to page server thereby releasing web server to process other requests |
US5734831A (en) | 1996-04-26 | 1998-03-31 | Sun Microsystems, Inc. | System for configuring and remotely administering a unix computer over a network |
US5784058A (en) | 1996-05-28 | 1998-07-21 | Sun Microsystems, Inc. | User-controllable persistent browser display pages |
US5715453A (en) | 1996-05-31 | 1998-02-03 | International Business Machines Corporation | Web server mechanism for processing function calls for dynamic data queries in a web page |
US5935207A (en) | 1996-06-03 | 1999-08-10 | Webtv Networks, Inc. | Method and apparatus for providing remote site administrators with user hits on mirrored web sites |
JP3178342B2 (en) | 1996-06-17 | 2001-06-18 | 松下電器産業株式会社 | Information provision system using network |
US6014686A (en) | 1996-06-21 | 2000-01-11 | Telcordia Technologies, Inc. | Apparatus and methods for highly available directory services in the distributed computing environment |
US5832514A (en) | 1996-06-26 | 1998-11-03 | Microsoft Corporation | System and method for discovery based data recovery in a store and forward replication process |
US6154777A (en) | 1996-07-01 | 2000-11-28 | Sun Microsystems, Inc. | System for context-dependent name resolution |
US6360256B1 (en) | 1996-07-01 | 2002-03-19 | Sun Microsystems, Inc. | Name service for a redundant array of internet servers |
US6134583A (en) | 1996-07-01 | 2000-10-17 | Sun Microsystems, Inc. | Method, system, apparatus and article of manufacture for providing identity-based caching services to a plurality of computer systems (#16) |
US5862339A (en) | 1996-07-09 | 1999-01-19 | Webtv Networks, Inc. | Client connects to an internet access provider using algorithm downloaded from a central server based upon client's desired criteria after disconnected from the server |
JPH1027148A (en) | 1996-07-10 | 1998-01-27 | Hitachi Ltd | Server systesm for internet |
US6038610A (en) | 1996-07-17 | 2000-03-14 | Microsoft Corporation | Storage of sitemaps at server sites for holding information regarding content |
US5919247A (en) | 1996-07-24 | 1999-07-06 | Marimba, Inc. | Method for the distribution of code and data updates |
ATE536588T1 (en) | 1996-07-25 | 2011-12-15 | Xcelera Inc | WEB SERVER SYSTEM WITH PRIMARY AND SECONDARY SERVERS |
US5774660A (en) | 1996-08-05 | 1998-06-30 | Resonate, Inc. | World-wide-web server with delayed resource-binding for resource-based load balancing on a distributed resource multi-node network |
US5890171A (en) | 1996-08-06 | 1999-03-30 | Microsoft Corporation | Computer system and computer-implemented method for interpreting hypertext links in a document when including the document within another document |
JPH11514769A (en) | 1996-08-08 | 1999-12-14 | アグラナット・システムス・インコーポレーテッド | Embedded web server |
GB2316200A (en) | 1996-08-08 | 1998-02-18 | Ibm | Accessing information about executable code |
US6347085B2 (en) | 1996-08-16 | 2002-02-12 | Netspeak Corporation | Method and apparatus for establishing communications between packet-switched and circuit-switched networks |
JPH1093552A (en) | 1996-09-11 | 1998-04-10 | Nippon Telegr & Teleph Corp <Ntt> | Communication connection method with a plurality of hosts having common identifier |
JP4025379B2 (en) | 1996-09-17 | 2007-12-19 | 株式会社ニューズウオッチ | Search system |
US5893116A (en) | 1996-09-30 | 1999-04-06 | Novell, Inc. | Accessing network resources using network resource replicator and captured login script for use when the computer is disconnected from the network |
US6092204A (en) | 1996-10-01 | 2000-07-18 | At&T Corp | Filtering for public databases with naming ambiguities |
US5931904A (en) | 1996-10-11 | 1999-08-03 | At&T Corp. | Method for reducing the delay between the time a data page is requested and the time the data page is displayed |
SE9603753L (en) | 1996-10-14 | 1998-04-06 | Mirror Image Internet Ab | Procedure and apparatus for information transmission on the Internet |
US5958008A (en) | 1996-10-15 | 1999-09-28 | Mercury Interactive Corporation | Software system and associated methods for scanning and mapping dynamically-generated web documents |
US5870559A (en) | 1996-10-15 | 1999-02-09 | Mercury Interactive | Software system and associated methods for facilitating the analysis and management of web sites |
US6138141A (en) | 1996-10-18 | 2000-10-24 | At&T Corp | Server to client cache protocol for improved web performance |
US6038216A (en) | 1996-11-01 | 2000-03-14 | Packeteer, Inc. | Method for explicit data rate control in a packet communication environment without data rate supervision |
US6049831A (en) | 1996-11-08 | 2000-04-11 | Gte Laboratories Incorporated | System for transmitting network-related information where requested network information is separately transmitted as definitions and display information |
US5802106A (en) | 1996-12-06 | 1998-09-01 | Packeteer, Inc. | Method for rapid data rate detection in a packet communication environment without data rate supervision |
US6046980A (en) | 1996-12-09 | 2000-04-04 | Packeteer, Inc. | System for managing flow bandwidth utilization at network, transport and application layers in store and forward network |
US5913033A (en) | 1996-12-20 | 1999-06-15 | International Business Machines Corporation | Apparatus and method for retrieving information using standard objects |
US6052718A (en) | 1997-01-07 | 2000-04-18 | Sightpath, Inc | Replica routing |
US6052730A (en) | 1997-01-10 | 2000-04-18 | The Board Of Trustees Of The Leland Stanford Junior University | Method for monitoring and/or modifying web browsing sessions |
US6026440A (en) | 1997-01-27 | 2000-02-15 | International Business Machines Corporation | Web server account manager plug-in for monitoring resources |
US5918010A (en) | 1997-02-07 | 1999-06-29 | General Internet, Inc. | Collaborative internet data mining systems |
US6173311B1 (en) | 1997-02-13 | 2001-01-09 | Pointcast, Inc. | Apparatus, method and article of manufacture for servicing client requests on a network |
US6108673A (en) | 1997-02-25 | 2000-08-22 | International Business Machines Corporation | System for creating a form from a template that includes replication block |
US6370571B1 (en) | 1997-03-05 | 2002-04-09 | At Home Corporation | System and method for delivering high-performance online multimedia services |
US6012090A (en) | 1997-03-14 | 2000-01-04 | At&T Corp. | Client-side parallel requests for network services using group name association |
US6421726B1 (en) | 1997-03-14 | 2002-07-16 | Akamai Technologies, Inc. | System and method for selection and retrieval of diverse types of video data on a computer network |
US6470389B1 (en) | 1997-03-14 | 2002-10-22 | Lucent Technologies Inc. | Hosting a network service on a cluster of servers using a single-address image |
US5987606A (en) | 1997-03-19 | 1999-11-16 | Bascom Global Internet Services, Inc. | Method and system for content filtering information retrieved from an internet computer network |
US5796952A (en) | 1997-03-21 | 1998-08-18 | Dot Com Development, Inc. | Method and apparatus for tracking client interaction with a network resource and creating client profiles and resource database |
US5945989A (en) | 1997-03-25 | 1999-08-31 | Premiere Communications, Inc. | Method and apparatus for adding and altering content on websites |
US6189039B1 (en) | 1997-04-10 | 2001-02-13 | International Business Machines Corporation | Selective tunneling of streaming data |
CA2202572C (en) | 1997-04-14 | 2004-02-10 | Ka Lun Eddie Law | A scaleable web server and method of efficiently managing multiple servers |
US5884038A (en) | 1997-05-02 | 1999-03-16 | Whowhere? Inc. | Method for providing an Internet protocol address with a domain name server |
US5944780A (en) | 1997-05-05 | 1999-08-31 | At&T Corp | Network with shared caching |
US6256675B1 (en) | 1997-05-06 | 2001-07-03 | At&T Corp. | System and method for allocating requests for objects and managing replicas of objects on a network |
US6314565B1 (en) | 1997-05-19 | 2001-11-06 | Intervu, Inc. | System and method for automated identification, retrieval, and installation of multimedia software components |
US6014698A (en) | 1997-05-19 | 2000-01-11 | Matchlogic, Inc. | System using first banner request that can not be blocked from reaching a server for accurately counting displays of banners on network terminals |
US6286045B1 (en) | 1997-05-19 | 2001-09-04 | Matchlogic, Inc. | Information storage and delivery over a computer network using centralized intelligence to monitor and control the information being delivered |
US6119143A (en) | 1997-05-22 | 2000-09-12 | International Business Machines Corporation | Computer system and method for load balancing with selective control |
US6173322B1 (en) | 1997-06-05 | 2001-01-09 | Silicon Graphics, Inc. | Network request distribution based on static rules and dynamic performance data |
US6125394A (en) | 1997-06-06 | 2000-09-26 | At&T Corporation | Computer system having a plurality of resources and utilizing a selection mechanism to select the resources based upon historical loading |
US5983227A (en) | 1997-06-12 | 1999-11-09 | Yahoo, Inc. | Dynamic page generator |
US6112239A (en) | 1997-06-18 | 2000-08-29 | Intervu, Inc | System and method for server-side optimization of data delivery on a distributed computer network |
US6243760B1 (en) | 1997-06-24 | 2001-06-05 | Vistar Telecommunications Inc. | Information dissemination system with central and distributed caches |
US6105028A (en) | 1997-06-26 | 2000-08-15 | Digital Equipment Corporation | Method and apparatus for accessing copies of documents using a web browser request interceptor |
US6115357A (en) | 1997-07-01 | 2000-09-05 | Packeteer, Inc. | Method for pacing data flow in a packet-based network |
US6021426A (en) | 1997-07-31 | 2000-02-01 | At&T Corp | Method and apparatus for dynamic data transfer on a web page |
US5968121A (en) | 1997-08-13 | 1999-10-19 | Microsoft Corporation | Method and apparatus for representing and applying network topological data |
US5987430A (en) | 1997-08-28 | 1999-11-16 | Atcom, Inc. | Communications network connection system and method |
US6112240A (en) | 1997-09-03 | 2000-08-29 | International Business Machines Corporation | Web site client information tracker |
US6226642B1 (en) | 1997-09-11 | 2001-05-01 | International Business Machines Corporation | Content modification of internet web pages for a television class display |
US6163779A (en) | 1997-09-29 | 2000-12-19 | International Business Machines Corporation | Method of saving a web page to a local hard drive to enable client-side browsing |
US6035332A (en) | 1997-10-06 | 2000-03-07 | Ncr Corporation | Method for monitoring user interactions with web pages from web server using data and command lists for maintaining information visited and issued by participants |
US6070191A (en) | 1997-10-17 | 2000-05-30 | Lucent Technologies Inc. | Data distribution techniques for load-balanced fault-tolerant web access |
US5996025A (en) | 1997-10-31 | 1999-11-30 | International Business Machines Corp. | Network transparent access framework for multimedia serving |
US6230196B1 (en) | 1997-11-12 | 2001-05-08 | International Business Machines Corporation | Generation of smart HTML anchors in dynamic web page creation |
US6018516A (en) | 1997-11-14 | 2000-01-25 | Packeteer, Inc. | Method for minimizing unneeded retransmission of packets in a packet communication environment supporting a plurality of data link rates |
US6041324A (en) | 1997-11-17 | 2000-03-21 | International Business Machines Corporation | System and method for identifying valid portion of computer resource identifier |
US6591299B2 (en) | 1997-11-25 | 2003-07-08 | Packeteer, Inc. | Method for automatically classifying traffic with enhanced hierarchy in a packet communications network |
US6412000B1 (en) | 1997-11-25 | 2002-06-25 | Packeteer, Inc. | Method for automatically classifying traffic in a packet communications network |
US6029176A (en) | 1997-11-25 | 2000-02-22 | Cannon Holdings, L.L.C. | Manipulating and analyzing data using a computer system having a database mining engine resides in memory |
US6167427A (en) | 1997-11-28 | 2000-12-26 | Lucent Technologies Inc. | Replication service system and method for directing the replication of information servers based on selected plurality of servers load |
AU1710099A (en) | 1997-12-08 | 1999-06-28 | Packeteer, Inc. | Method for data rate control for heterogenous or peer internetworking |
US6065062A (en) | 1997-12-10 | 2000-05-16 | Cisco Systems, Inc. | Backup peer pool for a routed computer network |
US6178160B1 (en) | 1997-12-23 | 2001-01-23 | Cisco Technology, Inc. | Load balancing of client connections across a network using server based algorithms |
US6151624A (en) | 1998-02-03 | 2000-11-21 | Realnames Corporation | Navigating network resources based on metadata |
US7054935B2 (en) | 1998-02-10 | 2006-05-30 | Savvis Communications Corporation | Internet content delivery network |
US7047300B1 (en) | 1998-02-10 | 2006-05-16 | Sprint Communications Company L.P. | Survivable and scalable data system and method for computer networks |
US6205120B1 (en) | 1998-03-13 | 2001-03-20 | Packeteer, Inc. | Method for transparently determining and setting an optimal minimum required TCP window size |
US6691148B1 (en) | 1998-03-13 | 2004-02-10 | Verizon Corporate Services Group Inc. | Framework for providing quality of service requirements in a distributed object-oriented computer system |
US6553420B1 (en) | 1998-03-13 | 2003-04-22 | Massachusetts Institute Of Technology | Method and apparatus for distributing requests among a plurality of resources |
US6430618B1 (en) | 1998-03-13 | 2002-08-06 | Massachusetts Institute Of Technology | Method and apparatus for distributing requests among a plurality of resources |
JP2002507857A (en) | 1998-03-16 | 2002-03-12 | ロイターズ・アメリカ・インコーポレーテッド | Method, apparatus and medium for minimal time multicast graft join restoration |
US6065051A (en) | 1998-04-15 | 2000-05-16 | Hewlett-Packard Company | Apparatus and method for communication between multiple browsers |
US6405257B1 (en) | 1998-06-26 | 2002-06-11 | Verizon Laboratories Inc. | Method and system for burst congestion control in an internet protocol network |
US6108703A (en) | 1998-07-14 | 2000-08-22 | Massachusetts Institute Of Technology | Global hosting system |
US6195680B1 (en) | 1998-07-23 | 2001-02-27 | International Business Machines Corporation | Client-based dynamic switching of streaming servers for fault-tolerance and load balancing |
US6226618B1 (en) | 1998-08-13 | 2001-05-01 | International Business Machines Corporation | Electronic content delivery system |
CA2467974C (en) | 1998-08-13 | 2010-03-30 | International Business Machines Corporation | System for tracking end-user electronic content usage |
US6859791B1 (en) | 1998-08-13 | 2005-02-22 | International Business Machines Corporation | Method for determining internet users geographic region |
US7110984B1 (en) | 1998-08-13 | 2006-09-19 | International Business Machines Corporation | Updating usage conditions in lieu of download digital rights management protected content |
US6144375A (en) | 1998-08-14 | 2000-11-07 | Praja Inc. | Multi-perspective viewer for content-based interactivity |
US6212565B1 (en) | 1998-08-26 | 2001-04-03 | Sun Microsystems, Inc. | Apparatus and method for improving performance of proxy server arrays that use persistent connections |
US6625643B1 (en) | 1998-11-13 | 2003-09-23 | Akamai Technologies, Inc. | System and method for resource management on a data network |
US6272566B1 (en) | 1998-11-18 | 2001-08-07 | International Business Machines Corporation | System for maintaining proper buffering within video play list |
US6553376B1 (en) | 1998-11-18 | 2003-04-22 | Infolibria, Inc. | Efficient content server using request redirection |
US6564251B2 (en) | 1998-12-03 | 2003-05-13 | Microsoft Corporation | Scalable computing system for presenting customized aggregation of information |
US7007295B1 (en) * | 1998-12-24 | 2006-02-28 | B3D, Inc. | System and method for Internet streaming of 3D animated content |
JP2000207270A (en) | 1999-01-13 | 2000-07-28 | Hitachi Ltd | Www proxy device |
US6477180B1 (en) * | 1999-01-28 | 2002-11-05 | International Business Machines Corporation | Optimizing method for digital content delivery in a multicast network |
US6529477B1 (en) | 1999-02-02 | 2003-03-04 | Mentat Inc. | Internet over satellite system |
US6654344B1 (en) | 1999-02-02 | 2003-11-25 | Mentat Inc. | Method and system for controlling data flow in an internet over satellite connection |
US6460085B1 (en) | 1999-02-02 | 2002-10-01 | Mentat Inc. | Method and system for managing memory in an internet over satellite connection |
US6934255B1 (en) | 1999-02-02 | 2005-08-23 | Packeteer, Inc. | Internet over satellite apparatus |
US6584083B1 (en) | 1999-02-02 | 2003-06-24 | Mentat Inc. | Internet over satellite method |
US6981050B1 (en) | 1999-02-11 | 2005-12-27 | Loudeye Corp. | Digital remote recorder |
US6249810B1 (en) | 1999-02-19 | 2001-06-19 | Chaincast, Inc. | Method and system for implementing an internet radio device for receiving and/or transmitting media information |
US6901604B1 (en) | 1999-02-19 | 2005-05-31 | Chaincast, Inc. | Method and system for ensuring continuous data flow between re-transmitters within a chaincast communication system |
US6338044B1 (en) | 1999-03-17 | 2002-01-08 | Loudeye Technologies, Inc. | Personal digital content system |
US6505248B1 (en) | 1999-03-24 | 2003-01-07 | Gte Data Services Incorporated | Method and system for monitoring and dynamically reporting a status of a remote server |
US8191097B1 (en) | 1999-04-01 | 2012-05-29 | Comcast Ip Holdings I, Llc | Method and apparatus for hierarchical distribution of video content for an interactive information distribution system |
US6460082B1 (en) | 1999-06-17 | 2002-10-01 | International Business Machines Corporation | Management of service-oriented resources across heterogeneous media servers using homogenous service units and service signatures to configure the media servers |
US6973490B1 (en) | 1999-06-23 | 2005-12-06 | Savvis Communications Corp. | Method and system for object-level web performance and analysis |
JP2001007844A (en) | 1999-06-24 | 2001-01-12 | Canon Inc | Network status server, information distribution system, and its control method and storage medium storing its control program |
US6463508B1 (en) | 1999-07-19 | 2002-10-08 | International Business Machines Corporation | Method and apparatus for caching a media stream |
US6801576B1 (en) | 1999-08-06 | 2004-10-05 | Loudeye Corp. | System for accessing, distributing and maintaining video content over public and private internet protocol networks |
US6834306B1 (en) | 1999-08-10 | 2004-12-21 | Akamai Technologies, Inc. | Method and apparatus for notifying a user of changes to certain parts of web pages |
US6763388B1 (en) | 1999-08-10 | 2004-07-13 | Akamai Technologies, Inc. | Method and apparatus for selecting and viewing portions of web pages |
US7028096B1 (en) * | 1999-09-14 | 2006-04-11 | Streaming21, Inc. | Method and apparatus for caching for streaming data |
US6490580B1 (en) | 1999-10-29 | 2002-12-03 | Verizon Laboratories Inc. | Hypervideo information retrieval usingmultimedia |
US6493707B1 (en) | 1999-10-29 | 2002-12-10 | Verizon Laboratories Inc. | Hypervideo: information retrieval using realtime buffers |
US6577595B1 (en) | 1999-11-12 | 2003-06-10 | Genuity Inc. | Systems and methods for transporting associated data signals over a network |
US6405252B1 (en) | 1999-11-22 | 2002-06-11 | Speedera Networks, Inc. | Integrated point of presence server network |
US6484143B1 (en) | 1999-11-22 | 2002-11-19 | Speedera Networks, Inc. | User device and system for traffic management and content distribution over a world wide area network |
US6694358B1 (en) | 1999-11-22 | 2004-02-17 | Speedera Networks, Inc. | Performance computer network method |
US6754699B2 (en) | 2000-07-19 | 2004-06-22 | Speedera Networks, Inc. | Content delivery and global traffic management network system |
US20020073167A1 (en) * | 1999-12-08 | 2002-06-13 | Powell Kyle E. | Internet content delivery acceleration system employing a hybrid content selection scheme |
US6754706B1 (en) | 1999-12-16 | 2004-06-22 | Speedera Networks, Inc. | Scalable domain name system with persistence and load balancing |
US6665726B1 (en) | 2000-01-06 | 2003-12-16 | Akamai Technologies, Inc. | Method and system for fault tolerant media streaming over the internet |
WO2001055863A1 (en) * | 2000-01-28 | 2001-08-02 | Ibeam Broadcasting Corporation | A system and method for performing broadcast-enabled disk drive replication in a distributed data delivery network |
AU2001236570A1 (en) | 2000-01-28 | 2001-08-07 | Ibeam Broadcasting Corporation | Method and apparatus for encoder-based distribution of live video and other streaming content |
WO2001055862A1 (en) | 2000-01-28 | 2001-08-02 | Ibeam Broadcasting Corporation | Method and system for real-time distributed data mining and analysis for networks |
US20010029525A1 (en) | 2000-01-28 | 2001-10-11 | Lahr Nils B. | Method of utilizing a single uniform resource locator for resources with multiple formats |
WO2001055855A1 (en) | 2000-01-28 | 2001-08-02 | Williams Communications, Llc | A system and method for mirroring and caching compressed data in a content distribution system |
EP1252577A1 (en) | 2000-01-28 | 2002-10-30 | Ibeam Broadcasting Corporation | A system and method for determining optimal server in a distributed network for serving content streams |
AU2001234620A1 (en) | 2000-01-28 | 2001-08-07 | Ibeam Broadcasting Corporation | Method and apparatus for client-side authentication and stream selection in a content distribution system |
US6718328B1 (en) | 2000-02-28 | 2004-04-06 | Akamai Technologies, Inc. | System and method for providing controlled and secured access to network resources |
US20020116444A1 (en) | 2000-02-29 | 2002-08-22 | Imran Chaudhri | Method and system for providing intelligent network content delivery |
US7117259B1 (en) | 2000-03-03 | 2006-10-03 | International Business Machines Corporation | Server time window for multiple selectable servers in a graphical user interface |
US6963910B1 (en) | 2000-03-03 | 2005-11-08 | International Business Machines Corporation | Graphical user interface for creating assets |
US6763377B1 (en) | 2000-03-03 | 2004-07-13 | International Business Machines Corporation | Asset management and scheduling graphical user interface for media streamer |
US6981180B1 (en) | 2000-03-16 | 2005-12-27 | Akamai Technologies, Inc. | Method and apparatus for testing request-response service using live connection traffic |
US20010027491A1 (en) * | 2000-03-27 | 2001-10-04 | Terretta Michael S. | Network communication system including metaswitch functionality |
US6687846B1 (en) * | 2000-03-30 | 2004-02-03 | Intel Corporation | System and method for error handling and recovery |
US7058706B1 (en) | 2000-03-31 | 2006-06-06 | Akamai Technologies, Inc. | Method and apparatus for determining latency between multiple servers and a client |
US7024466B2 (en) | 2000-04-07 | 2006-04-04 | Movielink, Llc | Network configured for delivery of content for download to a recipient |
JP2001290787A (en) | 2000-04-10 | 2001-10-19 | Ntt Communications Kk | Data distribution method and storage medium with data distribution program stored therein |
US6996616B1 (en) | 2000-04-17 | 2006-02-07 | Akamai Technologies, Inc. | HTML delivery from edge-of-network servers in a content delivery network (CDN) |
JP2001312434A (en) | 2000-04-28 | 2001-11-09 | Nippon Telegr & Teleph Corp <Ntt> | Information distribution system |
US20020016835A1 (en) | 2000-05-25 | 2002-02-07 | Gary Gamerman | System and method for cascaded distribution of processing |
CA2450394C (en) | 2000-05-26 | 2011-07-19 | Akamai Technologies, Inc. | Global load balancing across mirrored data centers |
US7028083B2 (en) | 2000-05-26 | 2006-04-11 | Akomai Technologies, Inc. | Method for extending a network map |
US7096263B2 (en) | 2000-05-26 | 2006-08-22 | Akamai Technologies, Inc. | Method for predicting file download time from mirrored data centers in a global computer network |
JP2004508613A (en) | 2000-06-01 | 2004-03-18 | エアロキャストドットコム インコーポレイテッド | Preloading content objects into the content exchange |
US8204082B2 (en) * | 2000-06-23 | 2012-06-19 | Cloudshield Technologies, Inc. | Transparent provisioning of services over a network |
US7155723B2 (en) | 2000-07-19 | 2006-12-26 | Akamai Technologies, Inc. | Load balancing service |
US20020016831A1 (en) | 2000-08-07 | 2002-02-07 | Vidius Inc. | Apparatus and method for locating of an internet user |
US7103564B1 (en) | 2000-08-17 | 2006-09-05 | International Business Machines Corporation | Method and apparatus for performing personalization based on classification |
US6950623B2 (en) | 2000-09-19 | 2005-09-27 | Loudeye Corporation | Methods and systems for dynamically serving in-stream advertisements |
US7010578B1 (en) | 2000-09-21 | 2006-03-07 | Akamai Technologies, Inc. | Internet content delivery service with third party cache interface support |
US20020083124A1 (en) | 2000-10-04 | 2002-06-27 | Knox Christopher R. | Systems and methods for supporting the delivery of streamed content |
US7203758B2 (en) | 2000-10-19 | 2007-04-10 | Loudeye Technologies, Inc. | System and method for selective insertion of content into streaming media |
KR20020030610A (en) | 2000-10-19 | 2002-04-25 | 스톰 씨엔씨 인코포레이티드 | A method for preventing reduction of sales amount of phonograph records by way of digital music file unlawfully circulated through communication network |
US20020083193A1 (en) * | 2000-11-03 | 2002-06-27 | Henry Terefenko | Parallel network data transmission |
US6963980B1 (en) | 2000-11-16 | 2005-11-08 | Protegrity Corporation | Combined hardware and software based encryption of databases |
WO2002077971A1 (en) | 2000-11-22 | 2002-10-03 | Williams Communications, Llc | Real time internet transcript presentation system |
US20020066038A1 (en) | 2000-11-29 | 2002-05-30 | Ulf Mattsson | Method and a system for preventing impersonation of a database user |
US20050273514A1 (en) * | 2000-12-22 | 2005-12-08 | Ray Milkey | System and method for automated and optimized file transfers among devices in a network |
US6751673B2 (en) | 2001-01-03 | 2004-06-15 | Akamai Technologies, Inc. | Streaming media subscription mechanism for a content delivery network |
US7096266B2 (en) | 2001-01-08 | 2006-08-22 | Akamai Technologies, Inc. | Extending an Internet content delivery network into an enterprise |
US20020131645A1 (en) | 2001-01-16 | 2002-09-19 | Packeteer Incorporated | Method and apparatus for optimizing a JPEG image using regionally variable compression levels |
US6963981B1 (en) | 2001-01-29 | 2005-11-08 | Akamai Technologies, Inc. | Method and apparatus for remote installation of an operating system over a network connection |
KR100392089B1 (en) | 2001-02-02 | 2003-07-22 | 스톰 씨엔씨 인코포레이티드 | A method for preventing reduction of sales amount of phonograph records by way of digital music file unlawfully circulated through communication network |
US6699418B2 (en) | 2001-02-23 | 2004-03-02 | Kuraray Co., Ltd. | Method for producing biaxially stretched film made of ethylene-vinyl alcohol copolymer |
US7003572B1 (en) | 2001-02-28 | 2006-02-21 | Packeteer, Inc. | System and method for efficiently forwarding client requests from a proxy server in a TCP/IP computing environment |
US20020129159A1 (en) * | 2001-03-09 | 2002-09-12 | Michael Luby | Multi-output packet server with independent streams |
US20020133537A1 (en) * | 2001-03-12 | 2002-09-19 | Whizz Technology Ltd. | Server cluster and server-side cooperative caching method for use with same |
KR100413627B1 (en) | 2001-03-19 | 2003-12-31 | 스톰 씨엔씨 인코포레이티드 | System for jointing digital literary works against unlawful reproduction through communication network and method for there of |
WO2002079905A2 (en) | 2001-04-02 | 2002-10-10 | Akamai Technologies, Inc. | Scalable, high performance and highly available distributed storage system for internet content |
US7007089B2 (en) | 2001-06-06 | 2006-02-28 | Akarnai Technologies, Inc. | Content delivery network map generation using passive measurement data |
EP1407342A2 (en) | 2001-06-14 | 2004-04-14 | Cable & Wireless Internet Services, Inc. | Secured shared storage architecture |
US6970432B1 (en) | 2001-06-18 | 2005-11-29 | Packeteer, Inc. | System and method for dynamically identifying internal hosts in a heterogeneous computing environment with multiple subnetworks |
US7647418B2 (en) | 2001-06-19 | 2010-01-12 | Savvis Communications Corporation | Real-time streaming media measurement system and method |
US20020199016A1 (en) | 2001-06-22 | 2002-12-26 | Freedman Avraham T. | Automated control of outbound transist links in a multi-homed BGP routing environment |
US6986018B2 (en) | 2001-06-26 | 2006-01-10 | Microsoft Corporation | Method and apparatus for selecting cache and proxy policy |
US7734781B2 (en) | 2001-07-09 | 2010-06-08 | Savvis Communications Corporation | Methods and systems for shared storage virtualization |
US6708137B2 (en) | 2001-07-16 | 2004-03-16 | Cable & Wireless Internet Services, Inc. | System and method for providing composite variance analysis for network operation |
US7188085B2 (en) | 2001-07-20 | 2007-03-06 | International Business Machines Corporation | Method and system for delivering encrypted content with associated geographical-based advertisements |
EP1413119B1 (en) | 2001-08-04 | 2006-05-17 | Kontiki, Inc. | Method and apparatus for facilitating distributed delivery of content across a computer network |
US7012900B1 (en) | 2001-08-22 | 2006-03-14 | Packeteer, Inc. | Method for measuring network delay using gap time |
US20030055910A1 (en) * | 2001-09-19 | 2003-03-20 | International Business Machines Corporation | Method and apparatus to manage data on a satellite data server |
WO2003027875A1 (en) | 2001-09-24 | 2003-04-03 | Loudeye Corp. | Systems and methods or enhancing streaming media |
US7406522B2 (en) | 2001-09-26 | 2008-07-29 | Packeteer, Inc. | Dynamic partitioning of network resources |
WO2003027906A2 (en) | 2001-09-28 | 2003-04-03 | Savvis Communications Corporation | System and method for policy dependent name to address resolutioin. |
US7373644B2 (en) | 2001-10-02 | 2008-05-13 | Level 3 Communications, Llc | Automated server replication |
US20030095660A1 (en) | 2001-10-15 | 2003-05-22 | Overpeer, Inc. | System and method for protecting digital works on a communication network |
US20030079027A1 (en) | 2001-10-18 | 2003-04-24 | Michael Slocombe | Content request routing and load balancing for content distribution networks |
US7054902B2 (en) | 2001-10-23 | 2006-05-30 | Packeteer, Inc. | Multicast delivery systems and methods |
US7013342B2 (en) | 2001-12-10 | 2006-03-14 | Packeteer, Inc. | Dynamic tunnel probing in a communications network |
US6954456B2 (en) | 2001-12-14 | 2005-10-11 | At & T Corp. | Method for content-aware redirection and content renaming |
US7032072B1 (en) | 2001-12-31 | 2006-04-18 | Packeteer, Inc. | Method and apparatus for fast lookup of related classification entities in a tree-ordered classification hierarchy |
JP2006502465A (en) | 2002-01-11 | 2006-01-19 | アカマイ テクノロジーズ インコーポレイテッド | Java application framework for use in content distribution network (CDN) |
US7412531B1 (en) * | 2002-01-29 | 2008-08-12 | Blue Coat Systems, Inc. | Live stream archiving method and apparatus |
US9167036B2 (en) | 2002-02-14 | 2015-10-20 | Level 3 Communications, Llc | Managed object replication and delivery |
US7133905B2 (en) * | 2002-04-09 | 2006-11-07 | Akamai Technologies, Inc. | Method and system for tiered distribution in a content delivery network |
US7266541B2 (en) * | 2002-04-12 | 2007-09-04 | International Business Machines Corporation | Adaptive edge processing of application data |
JP2005031987A (en) * | 2003-07-14 | 2005-02-03 | Nec Corp | Content layout management system and content layout management program for content delivery system |
WO2009068952A2 (en) | 2007-11-30 | 2009-06-04 | Telefonaktiebolaget L M Ericsson (Publ) | Method, network, and node for distributing electronic content in a content distribution network |
US8930538B2 (en) | 2008-04-04 | 2015-01-06 | Level 3 Communications, Llc | Handling long-tail content in a content delivery network (CDN) |
US9762692B2 (en) | 2008-04-04 | 2017-09-12 | Level 3 Communications, Llc | Handling long-tail content in a content delivery network (CDN) |
-
2002
- 2002-02-14 US US10/073,938 patent/US9167036B2/en active Active
-
2003
- 2003-02-11 EP EP03739748.6A patent/EP1474751B1/en not_active Expired - Lifetime
- 2003-02-11 JP JP2003568495A patent/JP4284190B2/en not_active Expired - Lifetime
- 2003-02-11 WO PCT/US2003/004108 patent/WO2003069437A2/en active Application Filing
- 2003-02-11 AU AU2003210973A patent/AU2003210973A1/en not_active Abandoned
- 2003-02-11 KR KR1020047012607A patent/KR101028639B1/en active IP Right Grant
- 2003-02-11 CN CNB038060396A patent/CN100498756C/en not_active Expired - Fee Related
-
2007
- 2007-03-08 US US11/715,316 patent/US20070174463A1/en not_active Abandoned
- 2007-10-30 US US11/978,656 patent/US8924466B2/en not_active Expired - Lifetime
- 2007-10-31 US US11/980,672 patent/US20080071859A1/en not_active Abandoned
-
2015
- 2015-10-19 US US14/887,053 patent/US9992279B2/en not_active Expired - Lifetime
-
2018
- 2018-06-04 US US15/997,543 patent/US10979499B2/en not_active Expired - Lifetime
Patent Citations (76)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US6502205B1 (en) * | 1993-04-23 | 2002-12-31 | Emc Corporation | Asynchronous remote data mirroring system |
US5734719A (en) * | 1993-10-15 | 1998-03-31 | International Business Systems, Incorporated | Digital information accessing, delivery and production system |
US5568181A (en) * | 1993-12-09 | 1996-10-22 | International Business Machines Corporation | Multimedia distribution over wide area networks |
US5845090A (en) * | 1994-02-14 | 1998-12-01 | Platinium Technology, Inc. | System for software distribution in a digital computer network |
US6016509A (en) * | 1994-05-16 | 2000-01-18 | Intel Corporation | General purpose metering mechanism for distribution of electronic information |
US5614940A (en) * | 1994-10-21 | 1997-03-25 | Intel Corporation | Method and apparatus for providing broadcast information with indexing |
US5819092A (en) * | 1994-11-08 | 1998-10-06 | Vermeer Technologies, Inc. | Online service development tool with fee setting capabilities |
US5898456A (en) * | 1995-04-25 | 1999-04-27 | Alcatel N.V. | Communication system with hierarchical server structure |
US5951694A (en) * | 1995-06-07 | 1999-09-14 | Microsoft Corporation | Method of redirecting a client service session to a second application server without interrupting the session by forwarding service-specific information to the second server |
US5933835A (en) * | 1995-09-29 | 1999-08-03 | Intel Corporation | Method and apparatus for managing multimedia data files in a computer network by streaming data files into separate streams based on file attributes |
US5913028A (en) * | 1995-10-06 | 1999-06-15 | Xpoint Technologies, Inc. | Client/server data traffic delivery system and method |
US5832069A (en) * | 1995-11-17 | 1998-11-03 | Sprint Communications Co L.P. | Object oriented system for modeling telecommunications circuits to estimate the access cost for leasing selected circuits |
US6233623B1 (en) * | 1996-01-11 | 2001-05-15 | Cabletron Systems, Inc. | Replicated resource management system for managing resources in a distributed application and maintaining a relativistic view of state |
US5781909A (en) * | 1996-02-13 | 1998-07-14 | Microtouch Systems, Inc. | Supervised satellite kiosk management system with combined local and remote data storage |
US6081835A (en) * | 1996-04-04 | 2000-06-27 | British Telecommunications Public Limited Company | Internet server and method of controlling an internet server |
US5777988A (en) * | 1996-04-17 | 1998-07-07 | Bell Communications Research, Inc. | System and method for equalizing delay in a dynamic packet switching network |
US5778187A (en) * | 1996-05-09 | 1998-07-07 | Netcast Communications Corp. | Multicasting method and apparatus |
US6023470A (en) * | 1996-05-17 | 2000-02-08 | Lee; Warren S. | Point of presence (POP) for digital facsimile network with virtual POPs used to communicate with other networks |
US6332157B1 (en) * | 1996-06-03 | 2001-12-18 | Webtv Networks, Inc. | Method of accessing multiple services from multiple service providers |
US5940831A (en) * | 1996-08-28 | 1999-08-17 | Nec Corporation | Hypermedia system and method of managing directories and directory data originating from a node link structure in a directory server |
US6098096A (en) * | 1996-12-09 | 2000-08-01 | Sun Microsystems, Inc. | Method and apparatus for dynamic cache preloading across a network |
US6131095A (en) * | 1996-12-11 | 2000-10-10 | Hewlett-Packard Company | Method of accessing a target entity over a communications network |
US6078943A (en) * | 1997-02-07 | 2000-06-20 | International Business Machines Corporation | Method and apparatus for dynamic interval-based load balancing |
US6161137A (en) * | 1997-03-31 | 2000-12-12 | Mshow.Com, Inc. | Method and system for providing a presentation on a network |
US6343298B1 (en) * | 1997-04-03 | 2002-01-29 | Microsoft Corporation | Seamless multimedia branching |
US6351775B1 (en) * | 1997-05-30 | 2002-02-26 | International Business Machines Corporation | Loading balancing across servers in a computer network |
US6678659B1 (en) * | 1997-06-20 | 2004-01-13 | Swisscom Ag | System and method of voice information dissemination over a network using semantic representation |
US6324582B1 (en) * | 1997-07-01 | 2001-11-27 | Sitara Networks, Inc. | Enhanced network communication |
US6085193A (en) * | 1997-09-29 | 2000-07-04 | International Business Machines Corporation | Method and system for dynamically prefetching information via a server hierarchy |
US6240462B1 (en) * | 1997-10-14 | 2001-05-29 | At&T | System for providing enhanced grade of service for connections over a large network |
US6421714B1 (en) * | 1997-10-14 | 2002-07-16 | Lucent Technologies | Efficient mobility management scheme for a wireless internet access system |
US6081840A (en) * | 1997-10-14 | 2000-06-27 | Zhao; Yan | Two-level content distribution system |
US6016512A (en) * | 1997-11-20 | 2000-01-18 | Telcordia Technologies, Inc. | Enhanced domain name service using a most frequently used domain names table and a validity code table |
US6266335B1 (en) * | 1997-12-19 | 2001-07-24 | Cyberiq Systems | Cross-platform server clustering using a network flow switch |
US6185598B1 (en) * | 1998-02-10 | 2001-02-06 | Digital Island, Inc. | Optimized network resource location |
US6094706A (en) * | 1998-03-02 | 2000-07-25 | International Business Machines Corporation | Caching in a data processing system using the pigeon hole principle |
US6915307B1 (en) * | 1998-04-15 | 2005-07-05 | Inktomi Corporation | High performance object cache |
US6453319B1 (en) * | 1998-04-15 | 2002-09-17 | Inktomi Corporation | Maintaining counters for high performance object cache |
US6128623A (en) * | 1998-04-15 | 2000-10-03 | Inktomi Corporation | High performance object cache |
US6591288B1 (en) * | 1998-05-19 | 2003-07-08 | Nortel Networks Limited | Data network accelerated access system |
US6115752A (en) * | 1998-05-21 | 2000-09-05 | Sun Microsystems, Inc. | System and method for server selection for mirrored sites |
US6317787B1 (en) * | 1998-08-11 | 2001-11-13 | Webtrends Corporation | System and method for analyzing web-server log files |
US6442588B1 (en) * | 1998-08-20 | 2002-08-27 | At&T Corp. | Method of administering a dynamic filtering firewall |
US6598121B2 (en) * | 1998-08-28 | 2003-07-22 | International Business Machines, Corp. | System and method for coordinated hierarchical caching and cache replacement |
US6324580B1 (en) * | 1998-09-03 | 2001-11-27 | Sun Microsystems, Inc. | Load balancing for replicated services |
US6130890A (en) * | 1998-09-11 | 2000-10-10 | Digital Island, Inc. | Method and system for optimizing routing of data packets |
US6466949B2 (en) * | 1998-11-23 | 2002-10-15 | Myway.Com Corporation | Performing event notification in a database having a distributed web cluster |
US6427170B1 (en) * | 1998-12-08 | 2002-07-30 | Cisco Technology, Inc. | Integrated IP address management |
US6389462B1 (en) * | 1998-12-16 | 2002-05-14 | Lucent Technologies Inc. | Method and apparatus for transparently directing requests for web objects to proxy caches |
US6345294B1 (en) * | 1999-04-19 | 2002-02-05 | Cisco Technology, Inc. | Methods and apparatus for remote configuration of an appliance on a network |
US6487555B1 (en) * | 1999-05-07 | 2002-11-26 | Alta Vista Company | Method and apparatus for finding mirrored hosts by analyzing connectivity and IP addresses |
US6463454B1 (en) * | 1999-06-17 | 2002-10-08 | International Business Machines Corporation | System and method for integrated load distribution and resource management on internet environment |
US6275470B1 (en) * | 1999-06-18 | 2001-08-14 | Digital Island, Inc. | On-demand overlay routing for computer-based communication networks |
US6594260B1 (en) * | 1999-09-03 | 2003-07-15 | Cisco Technology, Inc. | Content routing |
US6351776B1 (en) * | 1999-11-04 | 2002-02-26 | Xdrive, Inc. | Shared internet storage resource, user interface system, and method |
US6785704B1 (en) * | 1999-12-20 | 2004-08-31 | Fastforward Networks | Content distribution system for operation over an internetwork including content peering arrangements |
US6415368B1 (en) * | 1999-12-22 | 2002-07-02 | Xerox Corporation | System and method for caching |
US7254645B2 (en) * | 2000-03-30 | 2007-08-07 | Nec Corporation | Quality assured network service provision system compatible with a multi-domain network and service provision method and service broker device |
US6976090B2 (en) * | 2000-04-20 | 2005-12-13 | Actona Technologies Ltd. | Differentiated content and application delivery via internet |
US20030158923A1 (en) * | 2000-05-04 | 2003-08-21 | Reed Burkhart | System and method for automated negotiation for and allocation of a broadcast satellite, communication and caching system resource |
US20020078233A1 (en) * | 2000-05-12 | 2002-06-20 | Alexandros Biliris | Method and apparatus for content distribution network brokering and peering |
US20010049732A1 (en) * | 2000-06-01 | 2001-12-06 | Raciborski Nathan F. | Content exchange apparatus |
US20010051980A1 (en) * | 2000-06-01 | 2001-12-13 | Raciborski Nathan F. | Preloading content objects on content exchanges |
US20050021863A1 (en) * | 2000-06-23 | 2005-01-27 | Cloudshield Technologies, Inc. | Apparatus and method for virtual edge placement of web sites |
US6999988B2 (en) * | 2000-07-13 | 2006-02-14 | Lucent Technologies Inc. | Method and system for data layout and replacement in distributed streaming caches on the Internet |
US6732237B1 (en) * | 2000-08-29 | 2004-05-04 | Oracle International Corporation | Multi-tier caching system |
US20030031176A1 (en) * | 2000-10-26 | 2003-02-13 | Sim Siew Yong | Method and apparatus for distributing large payload file to a plurality of storage devices in a network |
US6651141B2 (en) * | 2000-12-29 | 2003-11-18 | Intel Corporation | System and method for populating cache servers with popular media contents |
US20020087797A1 (en) * | 2000-12-29 | 2002-07-04 | Farid Adrangi | System and method for populating cache servers with popular media contents |
US20020092026A1 (en) * | 2001-01-09 | 2002-07-11 | International Business Machines Corporation | Method and apparatus for broadcast delivery of content to a client-side cache based on user preferences |
US6859840B2 (en) * | 2001-01-29 | 2005-02-22 | Kasenna, Inc. | Prefix caching for media objects |
US20020163882A1 (en) * | 2001-03-01 | 2002-11-07 | Akamai Technologies, Inc. | Optimal route selection in a content delivery network |
US20020152318A1 (en) * | 2001-03-02 | 2002-10-17 | Menon Satish N. | Metadata enabled push-pull model for efficient low-latency video-content distribution over a network |
US6741990B2 (en) * | 2001-05-23 | 2004-05-25 | Intel Corporation | System and method for efficient and adaptive web accesses filtering |
US6839758B2 (en) * | 2001-09-28 | 2005-01-04 | Intel Corporation | Network processor for cache array routing |
US20030149581A1 (en) * | 2002-08-28 | 2003-08-07 | Imran Chaudhri | Method and system for providing intelligent network content delivery |
Cited By (325)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US10979499B2 (en) | 2002-02-14 | 2021-04-13 | Level 3 Communications, Llc | Managed object replication and delivery |
US9992279B2 (en) | 2002-02-14 | 2018-06-05 | Level 3 Communications, Llc | Managed object replication and delivery |
US20100198977A1 (en) * | 2006-09-27 | 2010-08-05 | Adobe Systems Incorporated | Automatic live stream trees |
US9021129B2 (en) | 2007-06-29 | 2015-04-28 | Amazon Technologies, Inc. | Request routing utilizing client location information |
US9021127B2 (en) | 2007-06-29 | 2015-04-28 | Amazon Technologies, Inc. | Updating routing information based on client location |
US9992303B2 (en) | 2007-06-29 | 2018-06-05 | Amazon Technologies, Inc. | Request routing utilizing client location information |
US10027582B2 (en) | 2007-06-29 | 2018-07-17 | Amazon Technologies, Inc. | Updating routing information based on client location |
US7769822B2 (en) * | 2007-07-17 | 2010-08-03 | International Business Machines Corporation | Method for distributing file content from a selected target depot server in response to multiple client requests |
US20090024693A1 (en) * | 2007-07-17 | 2009-01-22 | Jeffrey Mark Achtermann | Method for distributing file content from a selected target depot server in response to multiple client requests |
US20220086254A1 (en) * | 2007-07-19 | 2022-03-17 | Akamai Technologies, Inc. | Content delivery network (CDN) cold content handling |
US20090125569A1 (en) * | 2007-11-08 | 2009-05-14 | Jeffrey Mark Achtermann | Dynamic replication on demand policy based on zones |
US9197699B2 (en) | 2008-02-28 | 2015-11-24 | Level 3 Communications, Llc | Load-balancing cluster |
US10742723B2 (en) | 2008-02-28 | 2020-08-11 | Level 3 Communications, Llc | Load-balancing cluster |
US11323510B2 (en) | 2008-02-28 | 2022-05-03 | Level 3 Communications, Llc | Load-balancing cluster |
US8886814B2 (en) | 2008-02-28 | 2014-11-11 | Level 3 Communications, Llc | Load-balancing cluster |
US7908391B1 (en) * | 2008-03-25 | 2011-03-15 | Symantec Corporation | Application streaming and network file system optimization via feature popularity |
US20110078240A1 (en) * | 2008-03-31 | 2011-03-31 | Swaminathan Sivasubramanian | Content management |
US9009286B2 (en) | 2008-03-31 | 2015-04-14 | Amazon Technologies, Inc. | Locality based content distribution |
US20110072140A1 (en) * | 2008-03-31 | 2011-03-24 | Swaminathan Sivasubramanian | Content management |
US20110072134A1 (en) * | 2008-03-31 | 2011-03-24 | Swaminathan Sivasubramanian | Content management |
US8756325B2 (en) | 2008-03-31 | 2014-06-17 | Amazon Technologies, Inc. | Content management |
US9887915B2 (en) | 2008-03-31 | 2018-02-06 | Amazon Technologies, Inc. | Request routing based on class |
US9544394B2 (en) | 2008-03-31 | 2017-01-10 | Amazon Technologies, Inc. | Network resource identification |
US11909639B2 (en) | 2008-03-31 | 2024-02-20 | Amazon Technologies, Inc. | Request routing based on class |
US9479476B2 (en) | 2008-03-31 | 2016-10-25 | Amazon Technologies, Inc. | Processing of DNS queries |
US9894168B2 (en) | 2008-03-31 | 2018-02-13 | Amazon Technologies, Inc. | Locality based content distribution |
US10771552B2 (en) | 2008-03-31 | 2020-09-08 | Amazon Technologies, Inc. | Content management |
US9407699B2 (en) | 2008-03-31 | 2016-08-02 | Amazon Technologies, Inc. | Content management |
US8713156B2 (en) | 2008-03-31 | 2014-04-29 | Amazon Technologies, Inc. | Request routing based on class |
US9954934B2 (en) | 2008-03-31 | 2018-04-24 | Amazon Technologies, Inc. | Content delivery reconciliation |
US8275874B2 (en) | 2008-03-31 | 2012-09-25 | Amazon Technologies, Inc. | Locality based content distribution |
US9332078B2 (en) | 2008-03-31 | 2016-05-03 | Amazon Technologies, Inc. | Locality based content distribution |
US9571389B2 (en) | 2008-03-31 | 2017-02-14 | Amazon Technologies, Inc. | Request routing based on class |
US20090248697A1 (en) * | 2008-03-31 | 2009-10-01 | Richardson David R | Cache optimization |
US10797995B2 (en) | 2008-03-31 | 2020-10-06 | Amazon Technologies, Inc. | Request routing based on class |
US9621660B2 (en) | 2008-03-31 | 2017-04-11 | Amazon Technologies, Inc. | Locality based content distribution |
US10158729B2 (en) | 2008-03-31 | 2018-12-18 | Amazon Technologies, Inc. | Locality based content distribution |
US8346937B2 (en) | 2008-03-31 | 2013-01-01 | Amazon Technologies, Inc. | Content management |
US8352614B2 (en) | 2008-03-31 | 2013-01-08 | Amazon Technologies, Inc. | Content management |
US8352613B2 (en) | 2008-03-31 | 2013-01-08 | Amazon Technologies, Inc. | Content management |
US8352615B2 (en) | 2008-03-31 | 2013-01-08 | Amazon Technologies, Inc. | Content management |
US11451472B2 (en) | 2008-03-31 | 2022-09-20 | Amazon Technologies, Inc. | Request routing based on class |
US10157135B2 (en) | 2008-03-31 | 2018-12-18 | Amazon Technologies, Inc. | Cache optimization |
US9210235B2 (en) | 2008-03-31 | 2015-12-08 | Amazon Technologies, Inc. | Client side cache management |
US8386596B2 (en) | 2008-03-31 | 2013-02-26 | Amazon Technologies, Inc. | Request routing based on class |
US9208097B2 (en) | 2008-03-31 | 2015-12-08 | Amazon Technologies, Inc. | Cache optimization |
US8639817B2 (en) | 2008-03-31 | 2014-01-28 | Amazon Technologies, Inc. | Content management |
US8402137B2 (en) | 2008-03-31 | 2013-03-19 | Amazon Technologies, Inc. | Content management |
US9888089B2 (en) | 2008-03-31 | 2018-02-06 | Amazon Technologies, Inc. | Client side cache management |
US8606996B2 (en) | 2008-03-31 | 2013-12-10 | Amazon Technologies, Inc. | Cache optimization |
US8438263B2 (en) | 2008-03-31 | 2013-05-07 | Amazon Technologies, Inc. | Locality based content distribution |
US8601090B1 (en) | 2008-03-31 | 2013-12-03 | Amazon Technologies, Inc. | Network resource identification |
US8447831B1 (en) | 2008-03-31 | 2013-05-21 | Amazon Technologies, Inc. | Incentive driven content delivery |
US8930544B2 (en) | 2008-03-31 | 2015-01-06 | Amazon Technologies, Inc. | Network resource identification |
US10645149B2 (en) | 2008-03-31 | 2020-05-05 | Amazon Technologies, Inc. | Content delivery reconciliation |
US10305797B2 (en) | 2008-03-31 | 2019-05-28 | Amazon Technologies, Inc. | Request routing based on class |
US10554748B2 (en) | 2008-03-31 | 2020-02-04 | Amazon Technologies, Inc. | Content management |
US10530874B2 (en) | 2008-03-31 | 2020-01-07 | Amazon Technologies, Inc. | Locality based content distribution |
US11245770B2 (en) | 2008-03-31 | 2022-02-08 | Amazon Technologies, Inc. | Locality based content distribution |
US8533293B1 (en) | 2008-03-31 | 2013-09-10 | Amazon Technologies, Inc. | Client side cache management |
US10511567B2 (en) | 2008-03-31 | 2019-12-17 | Amazon Technologies, Inc. | Network resource identification |
US11194719B2 (en) | 2008-03-31 | 2021-12-07 | Amazon Technologies, Inc. | Cache optimization |
US9026616B2 (en) | 2008-03-31 | 2015-05-05 | Amazon Technologies, Inc. | Content delivery reconciliation |
US20090254661A1 (en) * | 2008-04-04 | 2009-10-08 | Level 3 Communications, Llc | Handling long-tail content in a content delivery network (cdn) |
EP2274684A4 (en) * | 2008-04-04 | 2012-12-05 | Level 3 Communications Llc | Handling long-tail content in a content delivery network (cdn) |
US10218806B2 (en) | 2008-04-04 | 2019-02-26 | Level 3 Communications, Llc | Handling long-tail content in a content delivery network (CDN) |
US9762692B2 (en) | 2008-04-04 | 2017-09-12 | Level 3 Communications, Llc | Handling long-tail content in a content delivery network (CDN) |
EP2274684A2 (en) * | 2008-04-04 | 2011-01-19 | Level 3 Communications, LLC | Handling long-tail content in a content delivery network (cdn) |
WO2009123868A3 (en) * | 2008-04-04 | 2010-01-07 | Level 3 Communications, Llc | Handling long-tail content in a content delivery network (cdn) |
US10924573B2 (en) | 2008-04-04 | 2021-02-16 | Level 3 Communications, Llc | Handling long-tail content in a content delivery network (CDN) |
US8930538B2 (en) | 2008-04-04 | 2015-01-06 | Level 3 Communications, Llc | Handling long-tail content in a content delivery network (CDN) |
US20090319612A1 (en) * | 2008-06-19 | 2009-12-24 | Brother Kogyo Kabushiki Kaisha | Information distribution system, terminal apparatus, distribution server and introduction server in the information distribution system, and recording medium on which program thereof is recorded |
US9608957B2 (en) | 2008-06-30 | 2017-03-28 | Amazon Technologies, Inc. | Request routing using network computing components |
US8458250B2 (en) | 2008-06-30 | 2013-06-04 | Amazon Technologies, Inc. | Request routing using network computing components |
US9912740B2 (en) | 2008-06-30 | 2018-03-06 | Amazon Technologies, Inc. | Latency measurement in resource requests |
US9021128B2 (en) | 2008-06-30 | 2015-04-28 | Amazon Technologies, Inc. | Request routing using network computing components |
US20100077056A1 (en) * | 2008-09-19 | 2010-03-25 | Limelight Networks, Inc. | Content delivery network stream server vignette distribution |
US8966003B2 (en) | 2008-09-19 | 2015-02-24 | Limelight Networks, Inc. | Content delivery network stream server vignette distribution |
US8549531B2 (en) | 2008-09-29 | 2013-10-01 | Amazon Technologies, Inc. | Optimizing resource configurations |
US9210099B2 (en) | 2008-09-29 | 2015-12-08 | Amazon Technologies, Inc. | Optimizing resource configurations |
US8843625B2 (en) | 2008-09-29 | 2014-09-23 | Amazon Technologies, Inc. | Managing network data display |
US10462025B2 (en) | 2008-09-29 | 2019-10-29 | Amazon Technologies, Inc. | Monitoring performance and operation of data exchanges |
US9088460B2 (en) | 2008-09-29 | 2015-07-21 | Amazon Technologies, Inc. | Managing resource consolidation configurations |
US8762526B2 (en) | 2008-09-29 | 2014-06-24 | Amazon Technologies, Inc. | Optimizing content management |
US9160641B2 (en) | 2008-09-29 | 2015-10-13 | Amazon Technologies, Inc. | Monitoring domain allocation performance |
US8200958B2 (en) | 2008-10-03 | 2012-06-12 | Limelight Networks, Inc. | Content delivery network encryption |
US20100088505A1 (en) * | 2008-10-03 | 2010-04-08 | Limelight Networks, Inc. | Content delivery network encryption |
US8392501B2 (en) * | 2008-10-27 | 2013-03-05 | Telefonaktiebolaget L M Ericsson (Publ) | Methods and systems for resuming, transferring or copying a multimedia session |
US20110314134A1 (en) * | 2008-10-27 | 2011-12-22 | Telefonaktiebolaget L M Ericsson (Publ) | Methods and systems for resuming, transferring or copying a multimedia session |
US8719886B2 (en) | 2008-11-12 | 2014-05-06 | Level 3 Communications, Llc | Dynamic processing of streamed content |
US8595778B2 (en) | 2008-11-12 | 2013-11-26 | Level 3 Communications, Llc | User authentication in a content delivery network |
US20100122303A1 (en) * | 2008-11-12 | 2010-05-13 | Level 3 Communications, Llc | User authentication in a content delivery network |
US20100122305A1 (en) * | 2008-11-12 | 2010-05-13 | Level 3 Communications, Llc | Dynamic processing of streamed content |
US9451040B2 (en) | 2008-11-13 | 2016-09-20 | At&T Intellectual Property I, L.P. | System and method for selectively caching hot content in a content distribution network |
US20100121940A1 (en) * | 2008-11-13 | 2010-05-13 | At&T Corp. | System and Method for Selectively Caching Hot Content in a Content Delivery System |
US8239482B2 (en) | 2008-11-13 | 2012-08-07 | At&T Intellectual Property I, Lp | System and method for selectively caching hot content in a content delivery system |
US10389833B2 (en) | 2008-11-13 | 2019-08-20 | At&T Intellectual Property I, L.P. | System and method for selectively caching hot content in a content distribution network |
US9787790B2 (en) | 2008-11-13 | 2017-10-10 | At&T Intellectual Property I, L.P. | System and method for selectively caching hot content in a content distribution network |
US8959179B2 (en) | 2008-11-13 | 2015-02-17 | At&T Intellectual Property I, L.P. | System and method for selectively caching hot content in a content distribution network |
US8583762B2 (en) | 2008-11-13 | 2013-11-12 | At&T Intellectual Property I, L.P. | System and method for selectively caching hot content in a content delivery system |
US9444759B2 (en) | 2008-11-17 | 2016-09-13 | Amazon Technologies, Inc. | Service provider registration by a content broker |
US9985927B2 (en) | 2008-11-17 | 2018-05-29 | Amazon Technologies, Inc. | Managing content delivery network service providers by a content broker |
US9515949B2 (en) | 2008-11-17 | 2016-12-06 | Amazon Technologies, Inc. | Managing content delivery network service providers |
US9590946B2 (en) | 2008-11-17 | 2017-03-07 | Amazon Technologies, Inc. | Managing content delivery network service providers |
US8583776B2 (en) | 2008-11-17 | 2013-11-12 | Amazon Technologies, Inc. | Managing content delivery network service providers |
US8732309B1 (en) | 2008-11-17 | 2014-05-20 | Amazon Technologies, Inc. | Request routing utilizing cost information |
US9734472B2 (en) | 2008-11-17 | 2017-08-15 | Amazon Technologies, Inc. | Request routing utilizing cost information |
US9451046B2 (en) | 2008-11-17 | 2016-09-20 | Amazon Technologies, Inc. | Managing CDN registration by a storage provider |
US10742550B2 (en) | 2008-11-17 | 2020-08-11 | Amazon Technologies, Inc. | Updating routing information based on client location |
US11115500B2 (en) | 2008-11-17 | 2021-09-07 | Amazon Technologies, Inc. | Request routing utilizing client location information |
US8788671B2 (en) | 2008-11-17 | 2014-07-22 | Amazon Technologies, Inc. | Managing content delivery network service providers by a content broker |
US8458360B2 (en) | 2008-11-17 | 2013-06-04 | Amazon Technologies, Inc. | Request routing utilizing client location information |
US10523783B2 (en) | 2008-11-17 | 2019-12-31 | Amazon Technologies, Inc. | Request routing utilizing client location information |
US11811657B2 (en) | 2008-11-17 | 2023-11-07 | Amazon Technologies, Inc. | Updating routing information based on client location |
US8521880B1 (en) | 2008-11-17 | 2013-08-27 | Amazon Technologies, Inc. | Managing content delivery network service providers |
US8321588B2 (en) | 2008-11-17 | 2012-11-27 | Amazon Technologies, Inc. | Request routing utilizing client location information |
US8510448B2 (en) | 2008-11-17 | 2013-08-13 | Amazon Technologies, Inc. | Service provider registration by a content broker |
US10116584B2 (en) | 2008-11-17 | 2018-10-30 | Amazon Technologies, Inc. | Managing content delivery network service providers |
US9251112B2 (en) | 2008-11-17 | 2016-02-02 | Amazon Technologies, Inc. | Managing content delivery network service providers |
US9787599B2 (en) | 2008-11-17 | 2017-10-10 | Amazon Technologies, Inc. | Managing content delivery network service providers |
US8423667B2 (en) | 2008-11-17 | 2013-04-16 | Amazon Technologies, Inc. | Updating routing information based on client location |
US8495220B2 (en) | 2008-11-17 | 2013-07-23 | Amazon Technologies, Inc. | Managing CDN registration by a storage provider |
US11283715B2 (en) | 2008-11-17 | 2022-03-22 | Amazon Technologies, Inc. | Updating routing information based on client location |
US8667127B2 (en) | 2009-03-24 | 2014-03-04 | Amazon Technologies, Inc. | Monitoring web site content |
US9191458B2 (en) | 2009-03-27 | 2015-11-17 | Amazon Technologies, Inc. | Request routing using a popularity identifier at a DNS nameserver |
US9083675B2 (en) | 2009-03-27 | 2015-07-14 | Amazon Technologies, Inc. | Translation of resource identifiers using popularity information upon client request |
US8463877B1 (en) | 2009-03-27 | 2013-06-11 | Amazon Technologies, Inc. | Dynamically translating resource identifiers for request routing using popularitiy information |
US10491534B2 (en) | 2009-03-27 | 2019-11-26 | Amazon Technologies, Inc. | Managing resources and entries in tracking information in resource cache components |
US10264062B2 (en) | 2009-03-27 | 2019-04-16 | Amazon Technologies, Inc. | Request routing using a popularity identifier to identify a cache component |
US10230819B2 (en) | 2009-03-27 | 2019-03-12 | Amazon Technologies, Inc. | Translation of resource identifiers using popularity information upon client request |
US8688837B1 (en) | 2009-03-27 | 2014-04-01 | Amazon Technologies, Inc. | Dynamically translating resource identifiers for request routing using popularity information |
US10601767B2 (en) | 2009-03-27 | 2020-03-24 | Amazon Technologies, Inc. | DNS query processing based on application information |
US8996664B2 (en) | 2009-03-27 | 2015-03-31 | Amazon Technologies, Inc. | Translation of resource identifiers using popularity information upon client request |
US10574787B2 (en) | 2009-03-27 | 2020-02-25 | Amazon Technologies, Inc. | Translation of resource identifiers using popularity information upon client request |
US8756341B1 (en) * | 2009-03-27 | 2014-06-17 | Amazon Technologies, Inc. | Request routing utilizing popularity information |
US8521851B1 (en) | 2009-03-27 | 2013-08-27 | Amazon Technologies, Inc. | DNS query processing using resource identifiers specifying an application broker |
US8521885B1 (en) | 2009-03-27 | 2013-08-27 | Amazon Technologies, Inc. | Dynamically translating resource identifiers for request routing using popularity information |
US8412823B1 (en) | 2009-03-27 | 2013-04-02 | Amazon Technologies, Inc. | Managing tracking information entries in resource cache components |
US9237114B2 (en) | 2009-03-27 | 2016-01-12 | Amazon Technologies, Inc. | Managing resources in resource cache components |
US20100250773A1 (en) * | 2009-03-31 | 2010-09-30 | Comcast Cable Communications, Llc | Dynamic generation of media content assets for a content delivery network |
US9729901B2 (en) | 2009-03-31 | 2017-08-08 | Comcast Cable Communications, Llc | Dynamic generation of media content assets for a content delivery network |
US9769504B2 (en) * | 2009-03-31 | 2017-09-19 | Comcast Cable Communications, Llc | Dynamic distribution of media content assets for a content delivery network |
US10701406B2 (en) | 2009-03-31 | 2020-06-30 | Comcast Cable Communications, Llc | Dynamic distribution of media content assets for a content delivery network |
US11356711B2 (en) | 2009-03-31 | 2022-06-07 | Comcast Cable Communications, Llc | Dynamic distribution of media content assets for a content delivery network |
US20100250772A1 (en) * | 2009-03-31 | 2010-09-30 | Comcast Cable Communications, Llc | Dynamic distribution of media content assets for a content delivery network |
US9055085B2 (en) | 2009-03-31 | 2015-06-09 | Comcast Cable Communications, Llc | Dynamic generation of media content assets for a content delivery network |
US20100251313A1 (en) * | 2009-03-31 | 2010-09-30 | Comcast Cable Communications, Llc | Bi-directional transfer of media content assets in a content delivery network |
US9584870B2 (en) * | 2009-04-10 | 2017-02-28 | Zte Corporation | Content locating method and content delivery network node |
US20120023530A1 (en) * | 2009-04-10 | 2012-01-26 | Zte Corporation | Content location method and content delivery network node |
US10521348B2 (en) | 2009-06-16 | 2019-12-31 | Amazon Technologies, Inc. | Managing resources using resource expiration data |
US9176894B2 (en) | 2009-06-16 | 2015-11-03 | Amazon Technologies, Inc. | Managing resources using resource expiration data |
US8782236B1 (en) | 2009-06-16 | 2014-07-15 | Amazon Technologies, Inc. | Managing resources using resource expiration data |
US10783077B2 (en) | 2009-06-16 | 2020-09-22 | Amazon Technologies, Inc. | Managing resources using resource expiration data |
US8543702B1 (en) | 2009-06-16 | 2013-09-24 | Amazon Technologies, Inc. | Managing resources using resource expiration data |
US10200490B2 (en) | 2009-06-26 | 2019-02-05 | Tata Communications (America) Inc. | Content-based redirection |
US9800690B1 (en) | 2009-06-26 | 2017-10-24 | Tata Communications (America) Inc. | Content-based redirection |
US9191369B2 (en) | 2009-07-17 | 2015-11-17 | Aryaka Networks, Inc. | Application acceleration as a service system and method |
US9832170B2 (en) | 2009-07-17 | 2017-11-28 | Aryaka Networks, Inc. | Application acceleration as a service system and method |
US9712325B2 (en) * | 2009-09-04 | 2017-07-18 | Amazon Technologies, Inc. | Managing secure content in a content delivery network |
US9130756B2 (en) * | 2009-09-04 | 2015-09-08 | Amazon Technologies, Inc. | Managing secure content in a content delivery network |
US10785037B2 (en) * | 2009-09-04 | 2020-09-22 | Amazon Technologies, Inc. | Managing secure content in a content delivery network |
US8397073B1 (en) * | 2009-09-04 | 2013-03-12 | Amazon Technologies, Inc. | Managing secure content in a content delivery network |
US10135620B2 (en) | 2009-09-04 | 2018-11-20 | Amazon Technologis, Inc. | Managing secure content in a content delivery network |
US20130191645A1 (en) * | 2009-09-04 | 2013-07-25 | Amazon Technologies, Inc. | Managing secure content in a content delivery network |
US20150319194A1 (en) * | 2009-09-04 | 2015-11-05 | Amazon Technologies, Inc. | Managing secure content in a content delivery network |
US20110082982A1 (en) * | 2009-10-02 | 2011-04-07 | Limelight Networks, Inc. | Content delivery network cache grouping |
US20120072527A1 (en) * | 2009-10-02 | 2012-03-22 | Limelight Networks, Inc. | Content delivery network cache grouping |
US8219647B2 (en) * | 2009-10-02 | 2012-07-10 | Limelight Networks, Inc. | Content delivery network cache grouping |
US8683002B2 (en) * | 2009-10-02 | 2014-03-25 | Limelight Networks, Inc. | Content delivery network cache grouping |
US8370449B2 (en) * | 2009-10-02 | 2013-02-05 | Limelight Networks, Inc. | Content delivery network cache grouping |
US20120254343A1 (en) * | 2009-10-02 | 2012-10-04 | Limelight Networks, Inc. | Content delivery network cache grouping |
US10218584B2 (en) | 2009-10-02 | 2019-02-26 | Amazon Technologies, Inc. | Forward-based resource delivery network management techniques |
US20130246555A1 (en) * | 2009-10-02 | 2013-09-19 | Limelight Networks, Inc. | Content devliery network cache grouping |
US8219645B2 (en) * | 2009-10-02 | 2012-07-10 | Limelight Networks, Inc. | Content delivery network cache grouping |
US9893957B2 (en) | 2009-10-02 | 2018-02-13 | Amazon Technologies, Inc. | Forward-based resource delivery network management techniques |
US9246776B2 (en) | 2009-10-02 | 2016-01-26 | Amazon Technologies, Inc. | Forward-based resource delivery network management techniques |
US8331370B2 (en) | 2009-12-17 | 2012-12-11 | Amazon Technologies, Inc. | Distributed routing architecture |
US8331371B2 (en) | 2009-12-17 | 2012-12-11 | Amazon Technologies, Inc. | Distributed routing architecture |
US8971328B2 (en) | 2009-12-17 | 2015-03-03 | Amazon Technologies, Inc. | Distributed routing architecture |
US8902897B2 (en) | 2009-12-17 | 2014-12-02 | Amazon Technologies, Inc. | Distributed routing architecture |
US9495338B1 (en) | 2010-01-28 | 2016-11-15 | Amazon Technologies, Inc. | Content distribution network |
US10506029B2 (en) | 2010-01-28 | 2019-12-10 | Amazon Technologies, Inc. | Content distribution network |
US11205037B2 (en) | 2010-01-28 | 2021-12-21 | Amazon Technologies, Inc. | Content distribution network |
US8090863B2 (en) | 2010-04-07 | 2012-01-03 | Limelight Networks, Inc. | Partial object distribution in content delivery network |
US8463876B2 (en) | 2010-04-07 | 2013-06-11 | Limelight, Inc. | Partial object distribution in content delivery network |
US9288153B2 (en) | 2010-08-26 | 2016-03-15 | Amazon Technologies, Inc. | Processing encoded content |
US10097398B1 (en) | 2010-09-28 | 2018-10-09 | Amazon Technologies, Inc. | Point of presence management in request routing |
US10778554B2 (en) | 2010-09-28 | 2020-09-15 | Amazon Technologies, Inc. | Latency measurement in resource requests |
US8938526B1 (en) | 2010-09-28 | 2015-01-20 | Amazon Technologies, Inc. | Request routing management based on network components |
US9106701B2 (en) | 2010-09-28 | 2015-08-11 | Amazon Technologies, Inc. | Request routing management based on network components |
US9712484B1 (en) | 2010-09-28 | 2017-07-18 | Amazon Technologies, Inc. | Managing request routing information utilizing client identifiers |
US11632420B2 (en) | 2010-09-28 | 2023-04-18 | Amazon Technologies, Inc. | Point of presence management in request routing |
US9185012B2 (en) | 2010-09-28 | 2015-11-10 | Amazon Technologies, Inc. | Latency measurement in resource requests |
US10015237B2 (en) | 2010-09-28 | 2018-07-03 | Amazon Technologies, Inc. | Point of presence management in request routing |
US9003035B1 (en) | 2010-09-28 | 2015-04-07 | Amazon Technologies, Inc. | Point of presence management in request routing |
US9497259B1 (en) | 2010-09-28 | 2016-11-15 | Amazon Technologies, Inc. | Point of presence management in request routing |
US9787775B1 (en) | 2010-09-28 | 2017-10-10 | Amazon Technologies, Inc. | Point of presence management in request routing |
US9407681B1 (en) | 2010-09-28 | 2016-08-02 | Amazon Technologies, Inc. | Latency measurement in resource requests |
US9191338B2 (en) | 2010-09-28 | 2015-11-17 | Amazon Technologies, Inc. | Request routing in a networked environment |
US8468247B1 (en) | 2010-09-28 | 2013-06-18 | Amazon Technologies, Inc. | Point of presence management in request routing |
US9160703B2 (en) | 2010-09-28 | 2015-10-13 | Amazon Technologies, Inc. | Request routing management based on network components |
US9253065B2 (en) | 2010-09-28 | 2016-02-02 | Amazon Technologies, Inc. | Latency measurement in resource requests |
US8676918B2 (en) | 2010-09-28 | 2014-03-18 | Amazon Technologies, Inc. | Point of presence management in request routing |
US8924528B1 (en) | 2010-09-28 | 2014-12-30 | Amazon Technologies, Inc. | Latency measurement in resource requests |
US8930513B1 (en) | 2010-09-28 | 2015-01-06 | Amazon Technologies, Inc. | Latency measurement in resource requests |
US10931738B2 (en) | 2010-09-28 | 2021-02-23 | 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 |
US8819283B2 (en) | 2010-09-28 | 2014-08-26 | Amazon Technologies, Inc. | Request routing in a networked environment |
US9794216B2 (en) | 2010-09-28 | 2017-10-17 | Amazon Technologies, Inc. | Request routing in a networked environment |
US11108729B2 (en) | 2010-09-28 | 2021-08-31 | Amazon Technologies, Inc. | Managing request routing information utilizing client identifiers |
US9800539B2 (en) | 2010-09-28 | 2017-10-24 | Amazon Technologies, Inc. | Request routing management based on network components |
US10225322B2 (en) | 2010-09-28 | 2019-03-05 | Amazon Technologies, Inc. | Point of presence management in request routing |
US10958501B1 (en) | 2010-09-28 | 2021-03-23 | Amazon Technologies, Inc. | Request routing information based on client IP groupings |
US11336712B2 (en) | 2010-09-28 | 2022-05-17 | Amazon Technologies, Inc. | Point of presence management in request routing |
US10079742B1 (en) | 2010-09-28 | 2018-09-18 | Amazon Technologies, Inc. | Latency measurement in resource requests |
US10951725B2 (en) | 2010-11-22 | 2021-03-16 | Amazon Technologies, Inc. | Request routing processing |
US8452874B2 (en) | 2010-11-22 | 2013-05-28 | Amazon Technologies, Inc. | Request routing processing |
US9003040B2 (en) | 2010-11-22 | 2015-04-07 | Amazon Technologies, Inc. | Request routing processing |
US9930131B2 (en) | 2010-11-22 | 2018-03-27 | 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 |
US8370452B2 (en) | 2010-12-27 | 2013-02-05 | Limelight Networks, Inc. | Partial object caching |
US10033804B2 (en) | 2011-03-02 | 2018-07-24 | Comcast Cable Communications, Llc | Delivery of content |
US11604667B2 (en) | 2011-04-27 | 2023-03-14 | Amazon Technologies, Inc. | Optimized deployment based upon customer locality |
US10433013B2 (en) * | 2011-06-06 | 2019-10-01 | Comcast Cable Communications, Llc | Dynamic management of audiovisual and data communications |
EP2738979A1 (en) * | 2011-08-16 | 2014-06-04 | Huawei Technologies Co., Ltd. | Data stream reused transmission method, duplicate point device and system |
EP2738979A4 (en) * | 2011-08-16 | 2014-06-18 | Huawei Tech Co Ltd | Data stream reused transmission method, duplicate point device and system |
US20130124371A1 (en) * | 2011-11-15 | 2013-05-16 | Verizon Patent And Licensing Inc. | Determining local catalog of digital content |
US9444884B2 (en) | 2011-12-31 | 2016-09-13 | Level 3 Communications, Llc | Load-aware load-balancing cluster without a central load balancer |
US10848587B2 (en) | 2012-02-02 | 2020-11-24 | Comcast Cable Communications, Llc | Content distribution network supporting popularity-based caching |
US11792276B2 (en) | 2012-02-02 | 2023-10-17 | Comcast Cable Communications, Llc | Content distribution network supporting popularity-based caching |
EP2624524A1 (en) * | 2012-02-02 | 2013-08-07 | Comcast Cable Communications, LLC | Content distribution network supporting popularity-based caching |
US11343351B2 (en) | 2012-02-02 | 2022-05-24 | Comcast Cable Communications, Llc | Content distribution network supporting popularity-based caching |
US9167049B2 (en) | 2012-02-02 | 2015-10-20 | Comcast Cable Communications, Llc | Content distribution network supporting popularity-based caching |
US10356202B2 (en) | 2012-02-02 | 2019-07-16 | Comcast Cable Communications, Llc | Content distribution network supporting popularity-based caching |
US9628554B2 (en) | 2012-02-10 | 2017-04-18 | Amazon Technologies, Inc. | Dynamic content delivery |
US8291117B1 (en) | 2012-02-15 | 2012-10-16 | Limelight Networks, Inc. | Scaled domain name service |
US10021179B1 (en) | 2012-02-21 | 2018-07-10 | Amazon Technologies, Inc. | Local resource delivery network |
US9172674B1 (en) | 2012-03-21 | 2015-10-27 | Amazon Technologies, Inc. | Managing request routing information utilizing performance information |
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 |
US11303717B2 (en) | 2012-06-11 | 2022-04-12 | Amazon Technologies, Inc. | Processing DNS queries to identify pre-processing information |
US9154551B1 (en) | 2012-06-11 | 2015-10-06 | Amazon Technologies, Inc. | Processing DNS queries to identify pre-processing information |
US10225362B2 (en) | 2012-06-11 | 2019-03-05 | Amazon Technologies, Inc. | Processing DNS queries to identify pre-processing information |
US11729294B2 (en) | 2012-06-11 | 2023-08-15 | Amazon Technologies, Inc. | Processing DNS queries to identify pre-processing information |
US20140032714A1 (en) * | 2012-07-27 | 2014-01-30 | Interdigital Patent Holdings, Inc. | Method and apparatus for publishing location information for a content object |
US8984056B2 (en) | 2012-08-09 | 2015-03-17 | Limelight Networks, Inc. | Inter point of presence split architecture |
US8356074B1 (en) | 2012-08-09 | 2013-01-15 | Limelight Networks, Inc. | Inter point of presence split architecture |
US9525659B1 (en) | 2012-09-04 | 2016-12-20 | Amazon Technologies, Inc. | Request routing utilizing point of presence load information |
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 |
US10015241B2 (en) | 2012-09-20 | 2018-07-03 | Amazon Technologies, Inc. | Automated profiling of resource usage |
US10542079B2 (en) | 2012-09-20 | 2020-01-21 | Amazon Technologies, Inc. | Automated profiling of resource usage |
US9317223B2 (en) * | 2012-12-17 | 2016-04-19 | International Business Machines Corporation | Method and apparatus for automated migration of data among storage centers |
US9311020B2 (en) | 2012-12-17 | 2016-04-12 | International Business Machines Corporation | Method and apparatus for automated migration of data among storage centers |
US20140173229A1 (en) * | 2012-12-17 | 2014-06-19 | International Business Machines Corporation | Method and Apparatus for Automated Migration of Data Among Storage Centers |
US10645056B2 (en) | 2012-12-19 | 2020-05-05 | Amazon Technologies, Inc. | Source-dependent address resolution |
US10205698B1 (en) | 2012-12-19 | 2019-02-12 | Amazon Technologies, Inc. | Source-dependent address resolution |
US9106934B2 (en) * | 2013-01-29 | 2015-08-11 | Espial Group Inc. | Distribution of adaptive bit rate live streaming video via hyper-text transfer protocol |
US9832492B2 (en) | 2013-01-29 | 2017-11-28 | Espial Group Inc. | Distribution of adaptive bit rate video streaming via hyper-text transfer protocol |
US20160119420A1 (en) * | 2013-05-02 | 2016-04-28 | International Business Machines Corporation | Replication of content to one or more servers |
US10554744B2 (en) * | 2013-05-02 | 2020-02-04 | International Business Machines Corporation | Replication of content to one or more servers |
US11388232B2 (en) | 2013-05-02 | 2022-07-12 | Kyndryl, Inc. | Replication of content to one or more servers |
US10547676B2 (en) | 2013-05-02 | 2020-01-28 | International Business Machines Corporation | Replication of content to one or more servers |
US9929959B2 (en) | 2013-06-04 | 2018-03-27 | Amazon Technologies, Inc. | Managing network computing components utilizing request routing |
US10374955B2 (en) | 2013-06-04 | 2019-08-06 | Amazon Technologies, Inc. | Managing network computing components utilizing request routing |
US9294391B1 (en) | 2013-06-04 | 2016-03-22 | Amazon Technologies, Inc. | Managing network computing components utilizing request routing |
WO2014195906A3 (en) * | 2013-06-06 | 2015-04-16 | Ericsson Television Inc. | Defragmentation of adaptive streaming segment files in a content delivery network |
US9015348B2 (en) | 2013-07-19 | 2015-04-21 | Limelight Networks, Inc. | Dynamically selecting between acceleration techniques based on content request attributes |
US20150156556A1 (en) * | 2013-12-04 | 2015-06-04 | Wowza Media Systems, LLC | Routing Media Content Based on Monetary Cost |
US9253545B2 (en) * | 2013-12-04 | 2016-02-02 | Wowza Media Systems, LLC | Routing media content based on monetary cost |
US10817957B2 (en) | 2014-06-09 | 2020-10-27 | Visa International Services Association | Systems and methods to detect changes in merchant identification information |
US10269077B2 (en) * | 2014-06-09 | 2019-04-23 | Visa International Service Association | Systems and methods to detect changes in merchant identification information |
US10097448B1 (en) | 2014-12-18 | 2018-10-09 | Amazon Technologies, Inc. | Routing mode and point-of-presence selection service |
US11863417B2 (en) | 2014-12-18 | 2024-01-02 | Amazon Technologies, Inc. | Routing mode and point-of-presence selection service |
US11381487B2 (en) | 2014-12-18 | 2022-07-05 | Amazon Technologies, Inc. | Routing mode and point-of-presence selection service |
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 |
US10728133B2 (en) | 2014-12-18 | 2020-07-28 | Amazon Technologies, Inc. | Routing mode and point-of-presence selection service |
US11297140B2 (en) | 2015-03-23 | 2022-04-05 | Amazon Technologies, Inc. | Point of presence based data uploading |
US10225326B1 (en) | 2015-03-23 | 2019-03-05 | Amazon Technologies, Inc. | Point of presence based data uploading |
US10469355B2 (en) | 2015-03-30 | 2019-11-05 | 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 |
US9887932B1 (en) | 2015-03-30 | 2018-02-06 | Amazon Technologies, Inc. | Traffic surge management for points of presence |
US10180993B2 (en) | 2015-05-13 | 2019-01-15 | Amazon Technologies, Inc. | Routing based request correlation |
US10691752B2 (en) | 2015-05-13 | 2020-06-23 | Amazon Technologies, Inc. | Routing based request correlation |
US9832141B1 (en) | 2015-05-13 | 2017-11-28 | Amazon Technologies, Inc. | Routing based request correlation |
US11461402B2 (en) | 2015-05-13 | 2022-10-04 | 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 |
US10200402B2 (en) | 2015-09-24 | 2019-02-05 | Amazon Technologies, Inc. | Mitigating network attacks |
US9794281B1 (en) | 2015-09-24 | 2017-10-17 | Amazon Technologies, Inc. | Identifying sources of network attacks |
US9742795B1 (en) | 2015-09-24 | 2017-08-22 | Amazon Technologies, Inc. | Mitigating network attacks |
US9774619B1 (en) | 2015-09-24 | 2017-09-26 | Amazon Technologies, Inc. | Mitigating network attacks |
US10270878B1 (en) | 2015-11-10 | 2019-04-23 | Amazon Technologies, Inc. | Routing for origin-facing points of presence |
US11134134B2 (en) | 2015-11-10 | 2021-09-28 | 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 |
US10348639B2 (en) | 2015-12-18 | 2019-07-09 | Amazon Technologies, Inc. | Use of virtual endpoints to improve data transmission rates |
US10075551B1 (en) | 2016-06-06 | 2018-09-11 | Amazon Technologies, Inc. | Request management for hierarchical cache |
US11463550B2 (en) | 2016-06-06 | 2022-10-04 | Amazon Technologies, Inc. | Request management for hierarchical cache |
US10666756B2 (en) | 2016-06-06 | 2020-05-26 | 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 |
US11457088B2 (en) | 2016-06-29 | 2022-09-27 | 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 |
US10516590B2 (en) | 2016-08-23 | 2019-12-24 | 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 |
US10469442B2 (en) | 2016-08-24 | 2019-11-05 | Amazon Technologies, Inc. | Adaptive resolution of domain name requests in virtual private cloud network environments |
US11330008B2 (en) | 2016-10-05 | 2022-05-10 | Amazon Technologies, Inc. | Network addresses with encoded DNS-level information |
US10469513B2 (en) | 2016-10-05 | 2019-11-05 | Amazon Technologies, Inc. | Encrypted network addresses |
US10505961B2 (en) | 2016-10-05 | 2019-12-10 | Amazon Technologies, Inc. | Digitally signed network address |
US10616250B2 (en) | 2016-10-05 | 2020-04-07 | Amazon Technologies, Inc. | Network addresses with encoded DNS-level information |
US11762703B2 (en) | 2016-12-27 | 2023-09-19 | 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 |
US10831549B1 (en) | 2016-12-27 | 2020-11-10 | Amazon Technologies, Inc. | Multi-region request-driven code execution 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 |
US11290418B2 (en) | 2017-09-25 | 2022-03-29 | Amazon Technologies, Inc. | Hybrid content request routing system |
US10592578B1 (en) | 2018-03-07 | 2020-03-17 | Amazon Technologies, Inc. | Predictive content push-enabled content delivery network |
US11362986B2 (en) | 2018-11-16 | 2022-06-14 | Amazon Technologies, Inc. | Resolution of domain name requests in heterogeneous network environments |
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 |
Also Published As
Publication number | Publication date |
---|---|
US20070174463A1 (en) | 2007-07-26 |
EP1474751A2 (en) | 2004-11-10 |
CN1777880A (en) | 2006-05-24 |
AU2003210973A1 (en) | 2003-09-04 |
US10979499B2 (en) | 2021-04-13 |
EP1474751B1 (en) | 2014-03-26 |
WO2003069437A3 (en) | 2003-11-27 |
EP1474751A4 (en) | 2010-12-01 |
CN100498756C (en) | 2009-06-10 |
KR20040105718A (en) | 2004-12-16 |
US9992279B2 (en) | 2018-06-05 |
JP2005534087A (en) | 2005-11-10 |
US20080065724A1 (en) | 2008-03-13 |
AU2003210973A8 (en) | 2003-09-04 |
WO2003069437A2 (en) | 2003-08-21 |
US9167036B2 (en) | 2015-10-20 |
US20060015574A1 (en) | 2006-01-19 |
JP4284190B2 (en) | 2009-06-24 |
US20180288151A1 (en) | 2018-10-04 |
US8924466B2 (en) | 2014-12-30 |
KR101028639B1 (en) | 2011-04-11 |
US20160044105A1 (en) | 2016-02-11 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
US10979499B2 (en) | Managed object replication and delivery | |
US11194719B2 (en) | Cache optimization | |
US10567287B2 (en) | System and methods for efficient media delivery using cache | |
US9848057B2 (en) | Multi-layer multi-hit caching for long tail content | |
US11190611B2 (en) | Content delivery network (CDN) cold content handling | |
EP2088719B1 (en) | Method and device for distributing file data | |
Hefeeda et al. | A hybrid architecture for cost-effective on-demand media streaming | |
EP2263208B1 (en) | Content delivery in a network | |
US20130304864A1 (en) | Publishing-Point Management for Content Delivery Network | |
EP1723763A1 (en) | Cache server network and method of scheduling the distribution of content files | |
WO2008025297A1 (en) | A method for downloading files by adopting the p2p technique and a p2p downloading system | |
EP2304946A1 (en) | Methods and apparatus for self-organized caching in a content delivery network | |
US20030055910A1 (en) | Method and apparatus to manage data on a satellite data server | |
US7849163B1 (en) | System and method for chunked file proxy transfers | |
US7120751B1 (en) | Dynamic streaming buffer cache algorithm selection | |
Naor et al. | Content Placement for Video-on-Demand Services Over Cellular Networks |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
AS | Assignment |
Owner name: DIGITAL ISLAND, INC., CALIFORNIA Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNORS:SEED, STEVEN L;HOBBS, KEVIN;GLYNN, SHANE M;AND OTHERS;REEL/FRAME:023428/0923;SIGNING DATES FROM 20020204 TO 20020207 Owner name: DIGITAL ISLAND, INC., CALIFORNIA Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNORS:SEED, STEVEN L;HOBBS, KEVIN;GLYNN, SHANE M;AND OTHERS;SIGNING DATES FROM 20020204 TO 20020207;REEL/FRAME:023428/0923 |
|
AS | Assignment |
Owner name: CABLE & WIRELESS INTERNET SERVICES, INC.,CALIFORNI Free format text: CHANGE OF NAME;ASSIGNOR:DIGITAL ISLAND, INC.;REEL/FRAME:024044/0676 Effective date: 20020212 Owner name: SAVVIS ASSET HOLDINGS, INC.,MISSOURI Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNOR:CABLE & WIRELESS INTERNET SERVICES, INC.;REEL/FRAME:024044/0814 Effective date: 20040213 Owner name: SAVVIS, INC.,MISSOURI Free format text: CHANGE OF NAME;ASSIGNOR:SAVVIS ASSET HOLDING, INC.;REEL/FRAME:024044/0902 Effective date: 20040308 Owner name: SAVVIS COMMUNICATIONS CORPORATION,MISSOURI Free format text: MERGER;ASSIGNOR:SAVVIS, INC.;REEL/FRAME:024044/0940 Effective date: 20050330 Owner name: MOUNT SHASTA ACQUISITION LLC,MISSOURI Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNOR:SAVVIS COMMUNICATIONS CORPORATION;REEL/FRAME:024046/0218 Effective date: 20070122 Owner name: LEVEL 3 COMMUNICATIONS, LLC,COLORADO Free format text: MERGER;ASSIGNOR:MOUNT SHASTA ACQUISITION LLC;REEL/FRAME:024046/0304 Effective date: 20070122 |
|
AS | Assignment |
Owner name: LEVEL 3 COMMUNICATIONS, LLC, COLORADO Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNOR:GREER, WILLIAM PATRICK;REEL/FRAME:031628/0714 Effective date: 20130827 |
|
STCB | Information on status: application discontinuation |
Free format text: ABANDONED -- AFTER EXAMINER'S ANSWER OR BOARD OF APPEALS DECISION |