IP Library Granted Patent US 9,602,591
Granted Patent B2
US 9,602,591 · App. 14/263,637 · Granted Mar 21, 2017

Managing TCP anycast requests

Inventor: Barrett Gibson Lyon (Pacifica, CA)
Assignees: TATA COMMUNICATIONS (AMERICA) INC.; JUNIPER NETWORKS, INC.
H04L67/1002H04L67/1004H04L67/1008H04L67/1021H04L67/1029H04L67/28H04L67/32
View Patent ↗
Loading inventors, assignments & file history…
Monitor This Case
Get email alerts when status or documents change.
Order Certified Copies
Most orders are placed with the USPTO same day — all within 24 business hours.
Order via The Patent Place →
Pre-filled with this patent's details
Quick Facts
Patent No.
US 9,602,591
App. No.
14/263,637
Granted
Mar 21, 2017
Kind
B2
Abstract

Managing TCP anycast requests at content delivery network nodes is disclosed. In some embodiments, serving a request includes receiving a request at a node of a plurality of nodes comprising a content delivery network, wherein each of the plurality of nodes share a same anycast IP address to which the request is directed and servicing the request at the node.

Claims (34)

1. A method for managing traffic in a content delivery network (CDN), comprising:

monitoring, with a network device, a number of requests being processed by a plurality of servers in a first node in said CDN;

receiving a request at the network device in the first node, wherein the request is serviceable by at least one of the first node and a second node;

first determining, with the network device, whether the first node is in a maintenance or backup mode;

redirecting, with the network device, the request to a second node if the first node is determined to be in the maintenance or backup mode as decided in the first determining step;

servicing, with the network device, any existing sessions at the first node if the first node is determined to be in the maintenance or backup mode as decided in the first determining step;

second determining, with the network device, when the servicing step is finished; and

performing a maintenance operation or backup operation at the first node when it is determined in the second determining step that the servicing step is finished;

wherein the first node and the second node share a same anycast IP.

2. The method for managing traffic as recited in claim 1 , wherein said network device is a server/router.

3. The method for managing traffic as recited in claim 1 , wherein

said request is a TCP anycast request.

4. The method for managing traffic as recited in claim 1 , wherein the redirecting of the request to the second node is via a virtual tunnel.

5. The method for managing traffic as recited in claim 1 , wherein a unicast address of the second node is used when redirecting the request to the second node.

6. The method for managing traffic as recited in claim 1 , wherein the second node is configured to generate and send a response to an end user after the request is redirected to the second node.

7. A system for managing traffic in a content delivery network (CDN), comprising:

a network device at a first node of a plurality of nodes in the CDN, said network device configured to:

monitor a number of requests being processed by a plurality of servers in a first node in said CDN;

receive a request in the first node, wherein the request is serviceable by at least one of the first node and a second node;

first determine whether the first node is in a maintenance or backup mode;

redirect the request to a second node if the first node is determined to be in the maintenance or backup mode as decided in the first determining step;

service any existing sessions at the first node if the first node is determined to be in the maintenance or backup mode;

second determine whether the service of any existing sessions at the first node is finished; and

perform a maintenance operation or backup operation at the first node when it is determined that the service of any existing sessions at the first node is finished;

wherein the first node and the second node share a same anycast IP.

8. The system for managing traffic as recited in claim 7 , wherein said network device is a server/router.

9. The system for managing traffic as recited in claim 7 , wherein

said request is a TCP anycast request.

10. The system for managing traffic as recited in claim 7 , further comprising:

a virtual tunnel,

wherein the redirecting of the request to the second node is via the virtual tunnel.

11. The system for managing traffic as recited in claim 7 , wherein a unicast address of the second node is used when redirecting the request to the second node.

12. The system for managing traffic as recited in claim 7 ,

wherein said second determination is performed by the network device.

Assignments (3)
MERGER Recorded May 24, 2016
From: BITGRAVITY, INC.
To: TATA COMMUNICATIONS (AMERICA) INC.
Reel/Frame 038700/0262 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded May 1, 2014
From: LYON, BARRETT GIBSON
To: BITGRAVITY, INC.
Reel/Frame 032801/0591 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded May 1, 2014
From: BITGRAVITY, INC.
To: JUNIPER NETWORKS, INC.
Reel/Frame 032801/0658 →
Continuity (4)
Continuation 13357485 · Jan 24, 2012
Continuation 12804902 · Jul 30, 2010
Continuation 12215715 · Jun 27, 2008
Related Publication 20140237031A1 · Aug 21, 2014