US20130218958A1 - Content request routing method - Google Patents
Content request routing method Download PDFInfo
- Publication number
- US20130218958A1 US20130218958A1 US13/860,092 US201313860092A US2013218958A1 US 20130218958 A1 US20130218958 A1 US 20130218958A1 US 201313860092 A US201313860092 A US 201313860092A US 2013218958 A1 US2013218958 A1 US 2013218958A1
- Authority
- US
- United States
- Prior art keywords
- distribution network
- content
- network node
- content distribution
- refusing
- 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/1001—Protocols in which an application is distributed across nodes in the network for accessing one among a plurality of replicated servers
- H04L67/1004—Server selection for load balancing
- H04L67/1014—Server selection for load balancing based on the content of a request
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L61/00—Network arrangements, protocols or services for addressing or naming
- H04L61/35—Network arrangements, protocols or services for addressing or naming involving non-standard use of addresses for implementing network functionalities, e.g. coding subscription information within the address or functional addressing, i.e. assigning an address to a function
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L61/00—Network arrangements, protocols or services for addressing or naming
-
- 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/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
- H04L67/1004—Server selection for load balancing
- H04L67/1008—Server selection for load balancing based on parameters of servers, e.g. available memory or workload
-
- 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
- H04L67/1036—Load balancing of requests to servers for services different from user content provisioning, e.g. load balancing across domain name 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/01—Protocols
- H04L67/10—Protocols in which an application is distributed across nodes in the network
- H04L67/104—Peer-to-peer [P2P] networks
-
- 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/104—Peer-to-peer [P2P] networks
- H04L67/1087—Peer-to-peer [P2P] networks using cross-functional networking aspects
- H04L67/1089—Hierarchical topologies
-
- 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/104—Peer-to-peer [P2P] networks
- H04L67/1087—Peer-to-peer [P2P] networks using cross-functional networking aspects
- H04L67/1091—Interfacing with client-server systems or between P2P systems
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/50—Network services
- H04L67/60—Scheduling or organising the servicing of application requests, e.g. requests for application data transmissions using the analysis and optimisation of the required network resources
- H04L67/63—Routing a service request depending on the request content or context
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L9/00—Cryptographic mechanisms or cryptographic arrangements for secret or secure communications; Network security protocols
- H04L9/40—Network security protocols
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L69/00—Network arrangements, protocols or services independent of the application payload and not provided for in the other groups of this subclass
- H04L69/30—Definitions, standards or architectural aspects of layered protocol stacks
- H04L69/32—Architecture of open systems interconnection [OSI] 7-layer type protocol stacks, e.g. the interfaces between the data link level and the physical level
- H04L69/322—Intralayer communication protocols among peer entities or protocol data unit [PDU] definitions
- H04L69/329—Intralayer communication protocols among peer entities or protocol data unit [PDU] definitions in the application layer [OSI layer 7]
Abstract
A method of redirecting content requests among content distribution network peers. In operation, a client sends a request for content to a content distribution network (CDN). When this CDN does not currently have the capacity to deliver the content, the CDN refers to one or more content distribution tables to see if the neighbour peers are able to provide this content. The content distribution table is populated at the time of distribution of the content. When the neighbour peer has this content, the request is redirected to the neighbour peer. In redirecting request, an address of the neighbour peer is appending to the previous address such that each peer receiving the request knows where the request came from and where it has been previously.
Description
- This application is a continuation of co-pending U.S. patent application Ser. No. 10/013,677, entitled “Content Request Routing Method,” which was filed on Dec. 13, 2001, and which is hereby incorporated herein by reference in its entirety.
- The present invention relates to content request routing and is particularly concerned with routing between content network peers.
- A current Internet draft “Known Mechanisms for Content Internetworking” by F. Douglas et al. provides a useful overview of content internetworking. (Nov. 8, 2001) The use of “Intelligent DNS (IDNS) is discussed as a way to handle request redirection.
- Content networks play an important role in the overall architecture of the web. In the Internet today several approaches have been proposed for providing infrastructure, at
layers 4 through 7, to get content to end users or user agents in a scalable, reliable, and cost-effective fashion. In this regard, various protocols and appliances have been developed for the location, download, and usage tracking of content. Examples of such technologies include: web caching proxies, content management tools, and intelligent web switches. - In general, a content network can be viewed as a virtual content overlay network in the OSI stack. This content overlay layer enables the delivery of richer services that rely on underlying elements from all 7 layers of the stack to subscribers or end users. Content overlay services rely on layer 7 protocols such as HTTP or RTSP for transport.
- However, regardless of the size of a content network, its ability to serve clients and subscribers is limited by economic realities and other factors. Hence, in order to increase the scale, reach and performance of content networks, it is possible to interconnect them. Hence, content internetworking is the interconnection of multiple content networks. In the networking field, content internetworking is also known as content distribution internetworking or content peering.
- Content internetworking allows different content networks to cooperate to serve content to end users or user agents. This leads to the ability of content networks to share resources so as to provide larger scale and/or reach to each participant than they could otherwise achieve. In order to be able to interconnect content networks, various architectural components must be introduced. In particular, the interconnection of content networks is achieved through the establishment of common internetworking gateway. The gateway must be able to provide mechanisms to distribute content or inject content into the networks and must also be able to direct user requests between them. The task of directing users requests to various surrogates among the inter-networked content networks is also called request routing and it is done in a content router. It is also possible to define various accounting and authorization schemes for financial settlements. In the literature, a content router is also called a request routing system (RRS).
- There are various request routing techniques that could be used within a content router to direct users request for content among internet-worked content networks. At a high-level, these may be classified under: DNS request-routing, transport-layer request-routing, and application-layer request-routing. However, regardless of the technique that is used for request routing, there should exist mechanisms within the content router that insures that the task of directing users requests is performed in a loop free manner.
- Among the various request routing techniques, the use of DNS based mechanisms has gained popularity due to the ubiquity of DNS as a directory service. In DNS based request-routing techniques, the content router acts as a specialized DNS server that is inserted in the DNS resolution process. The content router is capable of returning a different set of A, NS or CNAME records based on defined policies, network conditions and cost. Such DNS servers have also been called Intelligent DNS servers (IDNS). In general, within IDNS, the use of CNAME redirection techniques is the preferred method of request routing.
- Referring to
FIG. 1 there is illustrated in a block diagram an internetworking of a plurality of content distribution networks (CDN). In general, an intelligent DNS (IDNS) system uses aDNS server 18, to redirect, typically via the DNS CNAME response, to anIDNS brokering server 20 within a selected CDN, for example CDNB16. Thebrokering DNS server 20 monitors the load of other CDNs,CDNC 26, and CDNA 30 within abet of predefined “regions” (e.g., individual countries). Using the IP address of theDNS server 14 making a request, the IDNSbrokering server 20 maps theDNS server 14 to a region and selects the CDN that serves that region “best” based on various metrics, forexample CDNC 26. - The IDNS
brokering server 20 uses CNAME or NS redirection to other CDNs, or it can forward the DNS request directly to a CDN that will respond to the request directly (not shown inFIG. 1 ). For example, aclient 12 initially contacts (1) itslocal DNS server 14, which (2) contacts the IDNSbrokering server 20, via aDNS server 18. The IDNS brokering server 20 (3) returns either (A) a CNAME or NS record redirecting to another CDN, e.g. GDNC 26, or (B) an A record for anedge server 22 within CDNB 16. (The latter is called a “triangular resolution”.) Eventually, (4) an IP address is returned to theclient 12, which then requests (5) the control fromserver 28 and receives (6) the actual content. - Request-routing systems (RRS) present a “black-box” view of their associated distribution systems. Since in such an environment no CDN possesses a global view of all other CDNs, the request-routing system has to rely on a peer-to-peer model in which each request-routing system is only aware of its direct neighbor.
- There are two known methods for redirecting a request between two interconnected request-routing systems. The first method is an interactive method where a RRS directs the request to the next-hest (neighbor) RRS. This continues until a surrogate is finally selected. The second method is recursive where a RRS directs a request to the next-best RRS but expects an answer to return to the client. These two methods are analogous to recursive vs. iterative DNS lookups.
- The interactive approach will either find a CDN that will accept the request or it will return a request failed message. With either result, considerable resources are involved with the messaging that is exchanged in this process.
- Referring to
FIG. 2 there is illustrated a typical exchange for four content delivery networks. Aclient 40 makes a request via its local access provider that is routed to RRS 42. The RRS 42 then relays the request to a CDNA 44, who refuses the request. The RRS 42 next relays the request to a CDNB 46, who refuses the request. The RRS 42 next relays the request to aCDNC 48, who accepts the request. RRS 42 then provides the client with the DNS of CDNC 48 via its local access provider. - A second method of request redirection is recursive. Here the RRS redirects a request to the next best RRS, but expects the new RRS to return a reply to the client. Either of these methods will work if there is one level of peering. However, if there are multiple levels of peering, these simple redirection schemes may lead to looping, where the request continues to be past among the CDN peers without converging on a CDN that will accept the request.
- An object of the present invention is to provide an improved content request routing method.
- Accordingly, the present invention defines peering levels at distribution of content from a content source then tags each redirection of requests with an identifier of the CDN forwarding the request to a peer. Advantageously, the peers only require knowledge of nearest neighbours.
- Conveniently, a content by CDN matrix is populated at the time of distribution.
-
FIG. 1 illustrates in a block diagram a known internetworking of a plurality of content distribution networks; -
FIG. 2 illustrates a message exchange for request redirection in the internetworking ofFIG. 1 ; -
FIG. 3 illustrates an ordered peering of CDN using a method of request redirection in accordance with an embodiment of the present invention; -
FIGS. 4 a, 4 b, and 4 c illustrate content distribution tables for nearest peers in accordance with an embodiment of the present invention; and -
FIG. 5 illustrates in a flow chart the method of request redirection in accordance with an embodiment of the present invention. - Referring to
FIG. 3 there is illustrated an ordered peering of content distribution networks (CDN) using a method of redistribution in accordance with an embodiment of the present invention. The ordered peering 50 includes content distribution network (CDN),CDNA 60,CDNB 70,CDNC 80,CDND 90,CDNE 100 ordered inpeer levels L1 110 andL2 120. Each CDN is coupled to its nearest peer henceCDNA 60 is coupled via 62 itslevel 1peer CDNB 70 and via 64 to itslevel 2peer CDND 90. Similarly,CDNB 70 is coupled via 72 to itslevel 1peer CDNC 80 and to itslevel 2 peers CDND 90 and CDNE 100, via 74 and 76, respectively. AndCDNC 90 is coupled to alevel 2peer CDNE 100 via 92. - In operation, a
client 130 sends arequest 132 addressed {www.a.com/α} for content α toCDNA 60. However,CDNA 60 does not currently have the capacity to deliver this content. So it refers to its content distribution table 134 to see if the neighboring peers are able to provide this content. TheCDNA 60 sees that it has a level I peer,CDNB 70 that has the α content and forwards the request to CDNB 70 addressed (www.a.b.com/α). - The
CDNB 70 is also too busy to handle the request and determines from its distribution table 138 that itslevel 1peer CDNC 80 does not have the content α, however itslevel 2peer CDND 90 does. In this case, theCDNB 70 forwards therequest 140 addressed, www.a.b.d.com/α, to theCDND 90. TheCDND 90, is also too busy to handle the request so consults its distribution table 142 and determines that the only two peers having content α areCDNA 60 andCDNB 70, but the address ww.a.b.d.com/α shows that these two peers have already refused the request. At thispoint CDND 90 returns a network busy request refusedmessage 144 to theclient 130. - Referring to
FIGS. 4 a, 4 b, and 4 c, there is illustrated the content distribution tables of CDN A, B, and D, respectively ofFIG. 3 . Each distribution table is populated at the time of distribution of the content. Also at the time of content distribution, peering levels are established. In the present example only two levels,level 1 andlevel 2, are shown. Also for convenience the content distribution tables show a single table for a plurality of different content. Various implementations of content tables are possible. For example content tables could include all content from a particular content source. Alternatively, a table could exist for each content. - In the example above, the initial CDN peer was CDNA. If the CDN peer had been CDN B, the addressing of the re-routed request would be www.b.nextpeer.com. Hence, the re-routed request has the general form:
-
- www.<1stpeer>.<next peer>.<peer of next peer>.com.
- Referring to
FIG. 5 , there is illustrated in a flow chart the request redirection method in accordance with an embodiment of the present invention. The method begins with adecision block 200 asking whether the address CDN has capacity to fill the content request. If YES, aprocess block 202 sends an affirmation reply to the client and content transfer begins. If NO, aprocess block 204 reviews a distribution table to determine what peer has the requested content. Adecision block 206 determines if a neighbour peer has content α. If no neighbor peer has the content, a refuse request message is sent to the client, as represented by aprocess block 208. lf a neighbor peer is found to have the content, the request is forwarded, as represented by a process block 210, appending the peers address to the previous address. In this way, each peer receiving the request knows where the request came from, and where it has been previously. This becomes increasingly important as the number of redirections required increases and as the number of peer levels increase.
Claims (24)
1. A method of redirecting content requests among peer content distribution network nodes, the method comprising:
providing, at a first content distribution network node, information identifying content contained on each peer content distribution network node of the first content distribution network node;
receiving, at the first content distribution network node, a content request comprising an identification of requested content;
responsive to a determination that the first content distribution network node will refuse the content request, determining, from the information identifying the content contained on each peer content distribution network node of the first content distribution network node, whether a second content distribution network node is a candidate for providing the requested content; and
when the second content distribution network node is the candidate for providing the requested content, redirecting the content request from the first content distribution network node to the second content distribution network node.
2. The method of claim 1 , wherein:
when the content request received by the first content distribution network node has been refused by at least one refusing content distribution network node, the content request received by the first content distribution network node comprises information identifying the at least one refusing content distribution network node; and
determining whether the second content distribution network node is the candidate for providing the requested content comprises determining, from the information identifying the content contained on each peer content distribution network node of the first content distribution network node and from the information identifying the at least one refusing content distribution network node, whether the second content distribution network node contains the requested content and is not a refusing content distribution network node.
3. The method of claim 2 , wherein determining whether the second content distribution network node is the candidate for providing the requested content comprises:
determining, from the information identifying the content contained on each peer content distribution network node of the first content distribution network node and from the information identifying the at least one refusing content distribution network node, a plurality of peer content distribution network nodes that contain the requested content and that are not refusing content distribution network nodes; and
selecting one of the plurality of peer content distribution network nodes as the second content distribution network node.
4. The method of claim 3 , wherein redirecting the content request from the first content distribution network node to the second content distribution network node comprises adding, to the information identifying the at least one refusing content distribution network node of the redirected content request, information identifying the first content distribution network node as a refusing content distribution network node.
5. The method of claim 4 , wherein:
the content request received by the first content distribution network node comprises an address associated with the first content distribution network node;
the information identifying the at least one refusing content distribution network node is encoded in the address; and
adding, to the information identifying the at least one refusing content distribution network node of the redirected content request, the information identifying the first content distribution network node as a refusing content distribution network node comprises adding information identifying the first content distribution network node to the address of the content request redirected to the second content distribution network node.
6. The method of claim 5 , wherein the address comprises a set of refusing content distribution network node identifiers.
7. The method of claim 6 , wherein the set is ordered according to an order in which the refusing content distribution network nodes refused the content request.
8. The method of claim 6 , wherein the address is a uniform resource locator.
9. The method of claim 2 , wherein:
the content request received by the first content distribution network node comprises an address associated with the first content distribution network node; and
the information identifying the at least one refusing content distribution network node is encoded in the address.
10. The method of claim 9 , wherein the address comprises a set of refusing content to distribution network node identifiers.
11. The method of claim 10 , wherein the set is ordered according to an order in which the refusing content distribution network nodes refused the content request.
12. The method of claim 10 , wherein the address is a uniform resource locator.
13. The method of claim 1 , wherein determining whether the second content distribution network node is the candidate for providing the requested content comprises determining that no peer content distribution network node is a candidate for providing the requested content.
14. The method of claim 13 , comprising sending a content request refusal message indicating that the requested content will not be provided.
15. The method of claim 13 , wherein:
when the content request received by first content distribution network node has been refused by at least one refusing content distribution network node, the content request received by the first content distribution network node comprises information identifying the at least one refusing content distribution network node; and
determining that no peer content distribution node is a candidate for providing the requested content comprises determining, from the information identifying the content contained on each peer content distribution node of the first content distribution node and from the information identifying the at least one refusing content distribution network node, that no peer content distribution network node both contains the requested content and is not a refusing content distribution network node.
16. The method of claim 15 , wherein:
the content request received by the first content distribution network node comprises an address associated with the first content distribution network node; and
the information identifying the at least one refusing content distribution network node is encoded in the address.
17. The method of claim 16 , wherein the address comprises a set of refusing content distribution network node identifiers.
18. The method of claim 17 , wherein the set is ordered according to an order in which the refusing content distribution network nodes refused the content request.
19. The method of claim 17 , wherein the address is a uniform resource locator.
20. The method of claim 1 , wherein redirecting the content request from the first content distribution network node to the second content distribution network node comprises adding to the content request an indication that the content request was refused by the first content distribution network node.
21. The method of claim 1 , wherein the content request received by the first content distribution network node comprises an address associated with the first content distribution network node.
22. The method of claim 1 , wherein providing the information identifying the content contained on each peer content distribution network node of the first content distribution network node comprises providing at least one distribution table at the first content distribution network node, the at least one distribution table associating content items with peer content distribution network nodes containing the content items.
23. The method of claim 22 , wherein providing the at least one distribution table at the first content distribution network node comprises providing a separate distribution table for each of a plurality of content items on the first content distribution network node.
24. The method of claim 22 , wherein:
the at least one content distribution table at the first content distribution network node lists the peer content distribution network nodes according to a peering hierarchy; and
when a plurality of peer content distribution network nodes contains the requested content and does not comprise refusing content distribution network nodes, the first content distribution network node preferentially selects the second content distribution network node based on the peering hierarchy.
Priority Applications (1)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US13/860,092 US20130218958A1 (en) | 2001-12-13 | 2013-04-10 | Content request routing method |
Applications Claiming Priority (2)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US10/013,677 US8429221B2 (en) | 2001-12-13 | 2001-12-13 | Content request routing method |
US13/860,092 US20130218958A1 (en) | 2001-12-13 | 2013-04-10 | Content request routing method |
Related Parent Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US10/013,677 Continuation US8429221B2 (en) | 2001-12-13 | 2001-12-13 | Content request routing method |
Publications (1)
Publication Number | Publication Date |
---|---|
US20130218958A1 true US20130218958A1 (en) | 2013-08-22 |
Family
ID=21761143
Family Applications (2)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US10/013,677 Expired - Fee Related US8429221B2 (en) | 2001-12-13 | 2001-12-13 | Content request routing method |
US13/860,092 Abandoned US20130218958A1 (en) | 2001-12-13 | 2013-04-10 | Content request routing method |
Family Applications Before (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US10/013,677 Expired - Fee Related US8429221B2 (en) | 2001-12-13 | 2001-12-13 | Content request routing method |
Country Status (1)
Country | Link |
---|---|
US (2) | US8429221B2 (en) |
Cited By (2)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
WO2016094603A1 (en) * | 2014-12-10 | 2016-06-16 | Akamai Technologies, Inc. | Server-side prediction of media client steady state |
CN108696594A (en) * | 2018-05-27 | 2018-10-23 | 佛山市虚拟现实大数据产业研究院有限公司 | A kind of the big data traffic load equalization methods and device of market surpervision block chain |
Families Citing this family (64)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US9130954B2 (en) | 2000-09-26 | 2015-09-08 | Brocade Communications Systems, Inc. | Distributed health check for global server load balancing |
US7657629B1 (en) | 2000-09-26 | 2010-02-02 | Foundry Networks, Inc. | Global server load balancing |
US7454500B1 (en) | 2000-09-26 | 2008-11-18 | Foundry Networks, Inc. | Global server load balancing |
US7149797B1 (en) * | 2001-04-02 | 2006-12-12 | Akamai Technologies, Inc. | Content delivery network service provider (CDNSP)-managed content delivery network (CDN) for network service provider (NSP) |
US20020198930A1 (en) * | 2001-06-25 | 2002-12-26 | International Business Machines Corporation | Method and apparatus for wide-spread distribution of electronic content in a peer to peer fashion |
US20050066219A1 (en) | 2001-12-28 | 2005-03-24 | James Hoffman | Personal digital server pds |
US7289519B1 (en) * | 2002-05-01 | 2007-10-30 | Cisco Technology, Inc. | Methods and apparatus for processing content requests using domain name service |
US7086061B1 (en) | 2002-08-01 | 2006-08-01 | Foundry Networks, Inc. | Statistical tracking of global server load balancing for selecting the best network address from ordered list of network addresses based on a set of performance metrics |
US7676576B1 (en) | 2002-08-01 | 2010-03-09 | Foundry Networks, Inc. | Method and system to clear counters used for statistical tracking for global server load balancing |
US7574508B1 (en) * | 2002-08-07 | 2009-08-11 | Foundry Networks, Inc. | Canonical name (CNAME) handling for global server load balancing |
US20030149581A1 (en) * | 2002-08-28 | 2003-08-07 | Imran Chaudhri | Method and system for providing intelligent network content delivery |
US7369567B2 (en) * | 2002-12-31 | 2008-05-06 | Motorola, Inc. | Methods for affiliating endpoints with a group and determining common communication capabilities for the affiliated endpoints |
US7366780B2 (en) * | 2002-12-31 | 2008-04-29 | Motorola, Inc. | System and method for controlling and managing sessions between endpoints in a communications system |
US7574528B2 (en) * | 2003-08-27 | 2009-08-11 | Cisco Technology, Inc. | Methods and apparatus for accessing presence information |
US9584360B2 (en) | 2003-09-29 | 2017-02-28 | Foundry Networks, Llc | Global server load balancing support for private VIP addresses |
US7657622B1 (en) * | 2003-12-23 | 2010-02-02 | At&T Intellectual Property Ii, L.P. | Unified web hosting and content distribution system and method for assuring predetermined performance levels |
US7496651B1 (en) | 2004-05-06 | 2009-02-24 | Foundry Networks, Inc. | Configurable geographic prefixes for global server load balancing |
US7584301B1 (en) | 2004-05-06 | 2009-09-01 | Foundry Networks, Inc. | Host-level policies for global server load balancing |
US7423977B1 (en) * | 2004-08-23 | 2008-09-09 | Foundry Networks Inc. | Smoothing algorithm for round trip time (RTT) measurements |
US20090113024A1 (en) * | 2005-06-22 | 2009-04-30 | Snigdha Verma | Multicase Downloading Using Path Information |
US8588210B2 (en) * | 2005-07-22 | 2013-11-19 | Motorola Solutions, Inc. | Method and apparatus for floor control in a communication system |
US8792358B2 (en) * | 2006-04-27 | 2014-07-29 | Futurewei Technologies, Inc. | Content aware transport layer multicast |
US20080219151A1 (en) * | 2007-03-07 | 2008-09-11 | Nokia Corporation | System and method for using a peer to peer mechanism to repair broadcast data in wireless digital broadcast networks |
CN101282281B (en) * | 2007-04-03 | 2011-03-30 | 华为技术有限公司 | Medium distributing system and apparatus as well as flow medium play method |
US8996723B2 (en) * | 2007-06-04 | 2015-03-31 | Microsoft Technology Licensing, Llc | ISP-aware peer-to-peer content exchange |
US8615008B2 (en) | 2007-07-11 | 2013-12-24 | Foundry Networks Llc | Duplicating network traffic through transparent VLAN flooding |
US8248928B1 (en) | 2007-10-09 | 2012-08-21 | Foundry Networks, Llc | Monitoring server load balancing |
US20090150564A1 (en) * | 2007-12-10 | 2009-06-11 | Dorai Ashok Anbalagan | Per-user bandwidth availability |
US8489731B2 (en) | 2007-12-13 | 2013-07-16 | Highwinds Holdings, Inc. | Content delivery network with customized tracking of delivery data |
JP5029700B2 (en) * | 2007-12-13 | 2012-09-19 | 富士通株式会社 | Packet communication system, packet communication method, node and user terminal |
US8200810B2 (en) | 2007-12-13 | 2012-06-12 | Highwinds Holdings, Inc. | Content delivery network |
EP2240865B1 (en) * | 2007-12-20 | 2020-11-04 | Fast Health Corporation | Method for redirecting a website upon the occurrence of a disaster or emergency event |
GB2456026A (en) * | 2007-12-26 | 2009-07-01 | Contendo Inc | CDN balancing and sharing platform |
US8180896B2 (en) * | 2008-08-06 | 2012-05-15 | Edgecast Networks, Inc. | Global load balancing on a content delivery network |
US8549148B2 (en) | 2010-10-15 | 2013-10-01 | Brocade Communications Systems, Inc. | Domain name system security extensions (DNSSEC) for global server load balancing |
CN101984578B (en) * | 2010-10-28 | 2012-08-22 | 中国联合网络通信集团有限公司 | Control method and code stream sending method of point-to-point (P2P) broadcast service, as well as device and system |
EP2678992B1 (en) * | 2011-02-21 | 2020-11-11 | BlackBerry Limited | On the managed peer-to-peer sharing in cellular networks |
FR2973978A1 (en) * | 2011-04-08 | 2012-10-12 | France Telecom | METHOD OF COMMUNICATION BETWEEN DIGITAL CONTENT DISTRIBUTION NETWORKS |
CN102868664B (en) * | 2011-07-04 | 2017-07-14 | 南京中兴新软件有限责任公司 | Service system and service distribution method based on service delivery network |
US8510807B1 (en) | 2011-08-16 | 2013-08-13 | Edgecast Networks, Inc. | Real-time granular statistical reporting for distributed platforms |
US8689280B2 (en) | 2011-09-09 | 2014-04-01 | Microsoft Corporation | DNS-based content routing |
CN104012049B (en) * | 2011-10-13 | 2016-12-07 | 交互数字专利控股公司 | For the method and apparatus providing interface between content delivery network |
US9451045B2 (en) | 2011-12-14 | 2016-09-20 | Level 3 Communications, Llc | Content delivery network |
FR2988544A1 (en) * | 2012-03-23 | 2013-09-27 | France Telecom | SELECTING A NETWORK ENTITY FOR PROVIDING DIGITAL CONTENT |
US9628344B2 (en) | 2012-12-13 | 2017-04-18 | Level 3 Communications, Llc | Framework supporting content delivery with reducer services network |
US10701149B2 (en) | 2012-12-13 | 2020-06-30 | Level 3 Communications, Llc | Content delivery framework having origin services |
US9634918B2 (en) | 2012-12-13 | 2017-04-25 | Level 3 Communications, Llc | Invalidation sequencing in a content delivery framework |
US10652087B2 (en) | 2012-12-13 | 2020-05-12 | Level 3 Communications, Llc | Content delivery framework having fill services |
US10701148B2 (en) | 2012-12-13 | 2020-06-30 | Level 3 Communications, Llc | Content delivery framework having storage services |
US20140337472A1 (en) | 2012-12-13 | 2014-11-13 | Level 3 Communications, Llc | Beacon Services in a Content Delivery Framework |
US10791050B2 (en) | 2012-12-13 | 2020-09-29 | Level 3 Communications, Llc | Geographic location determination in a content delivery framework |
US9882767B1 (en) | 2013-07-23 | 2018-01-30 | Zscaler, Inc. | Distributed cloud-based dynamic name server surrogation systems and methods |
US9565138B2 (en) | 2013-12-20 | 2017-02-07 | Brocade Communications Systems, Inc. | Rule-based network traffic interception and distribution scheme |
US9648542B2 (en) | 2014-01-28 | 2017-05-09 | Brocade Communications Systems, Inc. | Session-based packet routing for facilitating analytics |
US10911353B2 (en) | 2015-06-17 | 2021-02-02 | Extreme Networks, Inc. | Architecture for a network visibility system |
US10129088B2 (en) | 2015-06-17 | 2018-11-13 | Extreme Networks, Inc. | Configuration of rules in a network visibility system |
US9866478B2 (en) | 2015-03-23 | 2018-01-09 | Extreme Networks, Inc. | Techniques for user-defined tagging of traffic in a network visibility system |
US10771475B2 (en) | 2015-03-23 | 2020-09-08 | Extreme Networks, Inc. | Techniques for exchanging control and configuration information in a network visibility system |
US10057126B2 (en) | 2015-06-17 | 2018-08-21 | Extreme Networks, Inc. | Configuration of a network visibility system |
US10530688B2 (en) | 2015-06-17 | 2020-01-07 | Extreme Networks, Inc. | Configuration of load-sharing components of a network visibility router in a network visibility system |
US10243813B2 (en) | 2016-02-12 | 2019-03-26 | Extreme Networks, Inc. | Software-based packet broker |
US10999200B2 (en) | 2016-03-24 | 2021-05-04 | Extreme Networks, Inc. | Offline, intelligent load balancing of SCTP traffic |
CN105847154A (en) * | 2016-04-25 | 2016-08-10 | 乐视控股(北京)有限公司 | Route selection method and device |
US10567259B2 (en) | 2016-10-19 | 2020-02-18 | Extreme Networks, Inc. | Smart filter generator |
Citations (10)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US5224205A (en) * | 1990-05-21 | 1993-06-29 | International Business Machines Corp. | Method of combining architecturally dissimilar computing networks into a single logical network |
US6055561A (en) * | 1996-10-02 | 2000-04-25 | International Business Machines Corporation | Mapping of routing traffic to switching networks |
US6415323B1 (en) * | 1999-09-03 | 2002-07-02 | Fastforward Networks | Proximity-based redirection system for robust and scalable service-node location in an internetwork |
US6529958B1 (en) * | 1998-07-17 | 2003-03-04 | Kabushiki Kaisha Toshiba | Label switched path set up scheme with reduced need for label set up retry operation |
US20030088696A1 (en) * | 1999-01-11 | 2003-05-08 | Fastforward Networks, Inc. | Performing multicast communication in computer networks by using overlay routing |
US6597663B1 (en) * | 1997-03-03 | 2003-07-22 | Cisco Technology, Inc. | Technique for handling forwarding transients with link state routing protocol |
US6654807B2 (en) * | 1998-02-10 | 2003-11-25 | Cable & Wireless Internet Services, Inc. | Internet content delivery network |
US6704795B1 (en) * | 1999-10-12 | 2004-03-09 | Cisco Technology, Inc. | Technique for reducing consumption of router resources after BGP restart |
US6785704B1 (en) * | 1999-12-20 | 2004-08-31 | Fastforward Networks | Content distribution system for operation over an internetwork including content peering arrangements |
US6850980B1 (en) * | 2000-06-16 | 2005-02-01 | Cisco Technology, Inc. | Content routing service protocol |
Family Cites Families (1)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US5978379A (en) | 1997-01-23 | 1999-11-02 | Gadzoox Networks, Inc. | Fiber channel learning bridge, learning half bridge, and protocol |
-
2001
- 2001-12-13 US US10/013,677 patent/US8429221B2/en not_active Expired - Fee Related
-
2013
- 2013-04-10 US US13/860,092 patent/US20130218958A1/en not_active Abandoned
Patent Citations (13)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US5224205A (en) * | 1990-05-21 | 1993-06-29 | International Business Machines Corp. | Method of combining architecturally dissimilar computing networks into a single logical network |
US6055561A (en) * | 1996-10-02 | 2000-04-25 | International Business Machines Corporation | Mapping of routing traffic to switching networks |
US6597663B1 (en) * | 1997-03-03 | 2003-07-22 | Cisco Technology, Inc. | Technique for handling forwarding transients with link state routing protocol |
US6654807B2 (en) * | 1998-02-10 | 2003-11-25 | Cable & Wireless Internet Services, Inc. | Internet content delivery network |
US6529958B1 (en) * | 1998-07-17 | 2003-03-04 | Kabushiki Kaisha Toshiba | Label switched path set up scheme with reduced need for label set up retry operation |
US6611872B1 (en) * | 1999-01-11 | 2003-08-26 | Fastforward Networks, Inc. | Performing multicast communication in computer networks by using overlay routing |
US20030088696A1 (en) * | 1999-01-11 | 2003-05-08 | Fastforward Networks, Inc. | Performing multicast communication in computer networks by using overlay routing |
US20040010616A1 (en) * | 1999-01-11 | 2004-01-15 | Fastforward Networks, Inc. | Performing multicast communication in computer networks by using overlay routing |
US6415323B1 (en) * | 1999-09-03 | 2002-07-02 | Fastforward Networks | Proximity-based redirection system for robust and scalable service-node location in an internetwork |
US20050010653A1 (en) * | 1999-09-03 | 2005-01-13 | Fastforward Networks, Inc. | Content distribution system for operation over an internetwork including content peering arrangements |
US6704795B1 (en) * | 1999-10-12 | 2004-03-09 | Cisco Technology, Inc. | Technique for reducing consumption of router resources after BGP restart |
US6785704B1 (en) * | 1999-12-20 | 2004-08-31 | Fastforward Networks | Content distribution system for operation over an internetwork including content peering arrangements |
US6850980B1 (en) * | 2000-06-16 | 2005-02-01 | Cisco Technology, Inc. | Content routing service protocol |
Cited By (3)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
WO2016094603A1 (en) * | 2014-12-10 | 2016-06-16 | Akamai Technologies, Inc. | Server-side prediction of media client steady state |
US10904312B2 (en) | 2014-12-10 | 2021-01-26 | Akamai Technologies, Inc. | Server-side prediction of media client steady state |
CN108696594A (en) * | 2018-05-27 | 2018-10-23 | 佛山市虚拟现实大数据产业研究院有限公司 | A kind of the big data traffic load equalization methods and device of market surpervision block chain |
Also Published As
Publication number | Publication date |
---|---|
US8429221B2 (en) | 2013-04-23 |
US20030115283A1 (en) | 2003-06-19 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
US8429221B2 (en) | Content request routing method | |
EP1250785B1 (en) | A content distribution system for operating over an internetwork including content peering arrangements | |
US7830896B2 (en) | Server load balancing using IP option field approach to identify route to selected server | |
US6687731B1 (en) | Arrangement for load sharing in computer networks | |
US6856991B1 (en) | Method and apparatus for routing data to a load balanced server using MPLS packet labels | |
US7418509B2 (en) | Method and apparatus for a distributed server tree | |
US6901445B2 (en) | Proximity-based redirection system for robust and scalable service-node location in an internetwork | |
US7490164B2 (en) | Method providing server affinity and client stickiness in a server load balancing device without TCP termination and without keeping flow states | |
US20030174648A1 (en) | Content delivery network by-pass system | |
US20110282945A1 (en) | Network aware peer to peer | |
US6850484B1 (en) | Packet redirection and message stream management | |
US9154571B2 (en) | Publish/subscribe networks | |
US7508753B2 (en) | Packet redirection and message stream management | |
Le et al. | A novel P2P approach to S-CSCF assignment in IMS | |
Knauf | Ausarbeitung Anwendungen 2-SoSe 2010 |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
AS | Assignment |
Owner name: RPX CLEARINGHOUSE LLC, CALIFORNIA Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNORS:ROCKSTAR CONSORTIUM US LP;ROCKSTAR CONSORTIUM LLC;BOCKSTAR TECHNOLOGIES LLC;AND OTHERS;REEL/FRAME:034924/0779 Effective date: 20150128 |
|
STCB | Information on status: application discontinuation |
Free format text: ABANDONED -- FAILURE TO RESPOND TO AN OFFICE ACTION |