IP Library Granted Patent US 8,234,402
Granted Patent B2
US 8,234,402 · App. 11/972,548 · Granted Jul 31, 2012

Method and apparatus for request routing

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 8,234,402
App. No.
11/972,548
Granted
Jul 31, 2012
Kind
B2
Abstract

A method and apparatus for dynamically encoding transactional information into a document over a network. The transactional information may include information about client data, object properties, or network conditions. The document may contain embedded links with embedded objects that can be requested by a client. The embedded links may contain URLs with associated domain names. The transactional information may be inserted into the domain name so that when the object request is subsequently translated by a DNS server, the DNS server can utilize the transactional information to intelligently translate the domain name into an IP address of a network device that can most advantageously serve the request.

Claims (9)

1. A method, comprising routing a request for an object to a network device other than an origin server for said object according to information concerning a client requesting said object which is determined to be important to the request, transactional information regarding said object, and network conditions, said information concerning the client having been obtained from a Web address embedded in a Web document, the Web address specifying the information concerning the client and a location at which the object can be found, said network device having been determined to be guaranteed to have a copy of said object according to a mapping that identifies objects stored at network devices.

2. The method of claim 1 , wherein the information concerning the client includes a network address of the client.

3. The method of claim 1 , wherein the information concerning the client includes information authenticating the client.

4. The method of claim 1 , wherein the information concerning the client was added to the Web address following a request by the client for a document containing an embedded request call pointing to the object.

5. The method of claim 4 , wherein the information concerning the client includes a network address of the client.

6. A method, comprising receiving a request for a Web document that includes a request call specifying a Web address of an object embedded therein, dynamically encoding information regarding an entity requesting the Web document into the request call embedded within the Web document, dynamically encoding transactional information regarding the object into the request call embedded within the Web document, transmitting the Web document with the encoded request call therein, and routing a request for the object identified in the encoded request call to an intermediary network device guaranteed to store a copy of the object specified in the request call according to the transactional information in the encoded request call by determining, using said transactional information, an identity of said intermediary network device from a mapping that identifies objects stored at intermediary network devices.

7. The method of claim 6 , wherein routing the request for the object identified in the encoded request call further includes using the information regarding the entity expressed in the encoded request call.

8. The method of claim 6 , wherein routing the request for the object identified in the encoded request call further includes using network conditions that relate to the entity expressed in the encoded request call.

9. The method of claim 6 , wherein dynamically encoding information regarding the entity includes locating the request call within the document, determining information regarding the entity that is important to the request, and writing the information determined to be important to the request into a domain name included in the request call.

Assignments (12)
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Nov 21, 2019
From: SYMANTEC CORPORATION
To: CA, INC.
Reel/Frame 051144/0918 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Aug 27, 2016
From: BLUE COAT SYSTEMS, INC.
To: SYMANTEC CORPORATION
Reel/Frame 039851/0044 →
RELEASE OF SECURITY INTEREST Recorded Aug 1, 2016
From: JEFFERIES FINANCE LLC
To: BLUE COAT SYSTEMS, INC.
Reel/Frame 039516/0929 →
RELEASE OF SECURITY INTEREST IN PATENT COLLATERAL AT REEL/FRAME NO. 30740/0181 Recorded May 29, 2015
From: JEFFERIES FINANCE LLC
To: BLUE COAT SYSTEMS, INC.
Reel/Frame 035797/0280 →
RELEASE OF SECURITY INTEREST IN PATENT COLLATERAL AT REEL/FRAME NO. 27727/0144 Recorded May 29, 2015
From: JEFFERIES FINANCE LLC
To: BLUE COAT SYSTEMS, INC.
Reel/Frame 035798/0006 →
SECURITY INTEREST Recorded May 22, 2015
From: BLUE COAT SYSTEMS, INC.
To: JEFFERIES FINANCE LLC, AS THE COLLATERAL AGENT
Reel/Frame 035751/0348 →
SECOND LIEN PATENT SECURITY AGREEMENT Recorded Jul 3, 2013
From: BLUE COAT SYSTEMS, INC.
To: JEFFERIES FINANCE LLC, AS COLLATERAL AGENT
Reel/Frame 030740/0181 →
RELEASE OF SECURITY INTEREST IN PATENT COLLATERAL RECORDED AT R/F 027727/0178 Recorded Oct 16, 2012
From: JEFFERIES FINANCE LLC, AS COLLATERAL AGENT
To: BLUE COAT SYSTEMS, INC.
Reel/Frame 029140/0170 →
FIRST LIEN PATENT SECURITY AGREEMENT Recorded Feb 16, 2012
From: BLUE COAT SYSTEMS, INC.
To: JEFFERIES FINANCE LLC
Reel/Frame 027727/0144 →
SECOND LIEN PATENT SECURITY AGREEMENT Recorded Feb 16, 2012
From: BLUE COAT SYSTEMS, INC.
To: JEFFERIES FINANCE LLC
Reel/Frame 027727/0178 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Dec 6, 2011
From: KARANDIKER, SHRIKRISHNA; DUVVURI, RAVI; ALEMANY, JUAN; NATU, NEELKANTH SHASHIKANT; GOPINATH, ANIL; PAREKH, BHARAT; HERBERT, TOM
To: CACHEFLOW, INC.
Reel/Frame 027338/0757 →
MERGER Recorded Dec 6, 2011
From: CACHEFLOW, INC.
To: BLUE COAT SYSTEMS, INC.
Reel/Frame 027339/0265 →