IP Library Granted Patent US 7,099,929
Granted Patent B1
US 7,099,929 · App. 09/357,250 · Granted Aug 29, 2006

System and method for transferring information in a hypertext transfer protocol based system

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 7,099,929
App. No.
09/357,250
Granted
Aug 29, 2006
Kind
B1
Abstract

A system and method for transferring information between an HTTP client and an HTTP server where a state object is stored on the HTTP client before making a request to the HTTP server. The state object may be sent to any HTTP server in any domain. In one embodiment, a particular state object is sent to the HTTP server based on the information requested from the HTTP client. In another embodiment a state object is automatically created by the HTTP client based on previously requested information. Additionally, the state object and their attributes can be defined and/or created by the user.

Claims (81)

1. A method of presenting custom information to an HTTP client

from an HTTP server, the method comprising the steps of:

creating a plurality of state objects at the HTTP client;

storing the plurality of state objects on the HTTP client prior to an initial interaction with the HTTP server;

initiating an interaction between the HTTP client and the HTTP server;

requesting information from the HTTP server;

sending at least one of the state objects to the HTTP server so that the information can be formatted responsive to the sent state object;

receiving the formatted information from the HTTP client;

based on previously requested information, automatically creating a state object by the HTTP client;

storing the automatically created state object on the HTTP client;

if information on the HTTP server is requested, additionally sending the automatically created state object to the HTTP server; and

based on the automatically created state object, transmitting the information relating to the previously requested information to the HTTP client.

2. The method of claim 1 further comprising the step of:

selecting the at least one of the state objects based on the information requested and prior to any interaction between the HTTP client and the HTTP server.

3. The method of claim 1 , wherein the plurality of state objects include at least one attribute.

4. The method of claim 3 further comprising the step of defining the attributes by a user.

5. The method of claim 3 further comprising the steps of:

creating new attributes by a user; and

defining the new attributes by the user.

6. A method of transferring state objects between an HTTP client and a plurality of HTTP servers, the method comprising the steps of:

creating a plurality of state objects at the HTTP client;

storing the plurality of state objects on the HTTP client prior to any interaction with a first HTTP server;

if information on the first HTTP server is requested sending the plurality of state objects to the first HTTP server;

if information on a second HTTP server is requested, sending the plurality of state objects to the second HTTP server;

based on the plurality of state objects, transmitting the information to the HTTP client;

based on previously requested information, automatically creating a state object by the HTTP client;

storing the automatically created state object on the HTTP client;

if information on the plurality of HTTP servers is requested, additionally sending the automatically created state object to the plurality of HTTP servers; and

based on the automatically created state object, transmitting the information relating to the previously requested information to the HTTP client.

7. The method of claim 6 , wherein the plurality of HTTP servers may be located in a single domain.

8. The method of claim 6 , wherein the plurality of HTTP servers may be located in a plurality of domains.

9. The method of claim 6 further comprising the steps of:

based on the information requested, sending certain state objects to the plurality of HTTP servers; and

based on the certain state objects, transmitting the information to the HTTP client.

10. The method of claim 6 , wherein the plurality of state objects include at least one attribute.

11. The method of claim 10 further comprising the step of defining the attributes by a user.

12. The method of claim 10 further comprising the steps of:

creating new attributes by a user; and

defining the new attributes by the user.

13. A communication network comprises:

a client system having a client processor and a client computer readable medium coupled to the client processor, the client computer readable medium containing program instructions for:

creating a plurality of state objects including at least one automatically created state object based on previously requested information;

storing the plurality of state objects and the at least one automatically created state object independent of an HTTP server;

requesting information from the HTTP server;

sending the plurality of state objects to the HTTP server including the at least one automatically created state object when the requested information includes previously requested information; and

receiving the information from the HTTP server based on the plurality of state objects or the at least one automatically created state object; and

a server system having a server processor and a server computer readable medium coupled to the server processor, the server system coupled to the client system, the server computer readable medium containing program instructions for:

receiving the request for information from the client system, the request being a first interaction between the HTTP server and the HTTP client;

receiving the plurality of state objects and the at least one automatically created state object; and

transmitting the information to the client system based on the plurality of state objects, wherein the information relating to the previously requested information is transmitted to the client system based on the at least one automatically created state object.

14. A computer readable medium on an HTTP client, wherein the computer readable medium contains executable program instructions for:

creating a plurality of state objects at the HTTP client including at least one automatically created state object based on previously requested information;

storing the plurality of state objects and the at least one automatically created state object on the HTTP client independent of an HTTP server;

requesting information from the HTTP server;

sending the plurality of state objects to the HTTP server including the at least one automatically created state object when the requested information includes previously requested information; and

receiving the information from the HTTP server based on the plurality of state objects and the at least one automatically created state object.

15. A computer readable medium on an HTTP server, wherein the computer readable medium contains executable program instructions for:

receiving a request for information from an HTTP client, the request being a first interaction between any HTTP server and the HTTP client wherein the request for information includes previously requested information;

receiving, from the HTTP client, a plurality of state objects that were not forwarded by any HTTP server to the HTTP client, the plurality of state objects including at least one automatically created state object that was created based on the previously requested information and stored on the HTTP client; and

transmitting the information to the HTTP client based on the plurality of state objects including the at least one automatically created state object.

16. A computer system comprises:

a processor;

memory coupled to the processor; and

a computer readable medium coupled to the processor, wherein the computer readable medium includes executable program instructions for:

creating a plurality of state objects at a client;

storing the plurality of state objects on the client, independent of a particular server;

if information on a server is requested, sending the plurality of state objects to the server;

based on the plurality of state objects transmitting the information to the client;

based on previously requested information, automatically creating a state object by the client;

if information on the server is requested, additionally sending the automatically created state object to the server;

based on the automatically created state object, transmitting the information relating to the previously requested information to the client; and

storing the automatically created state object on the client.

17. The computer system of claim 16 wherein the plurality of state objects may be sent to any server in any domain.

18. The computer readable medium of claim 16 , wherein the executable program instructions further:

based on the information requested, send certain state objects to the server; and

based on the certain state objects, transmit the information to the client.

19. The computer readable medium of claim 16 , wherein the plurality of state objects include at least one attribute.

20. The computer readable medium of claim 19 , wherein the executable program instructions further allow a user to define the attributes.

21. The computer readable medium of claim 19 , wherein the executable program instructions further:

allow a user to create new attributes; and

allow the user to define the new attributes.

Assignments (8)
RELEASE OF SECURITY INTEREST Recorded Oct 26, 2020
From: JEFFERIES FINANCE LLC
To: RPX CLEARINGHOUSE LLC
Reel/Frame 054305/0505 →
SECURITY INTEREST Recorded Jun 29, 2018
From: RPX CLEARINGHOUSE LLC
To: JEFFERIES FINANCE LLC
Reel/Frame 046485/0644 →
RELEASE (REEL 038041 / FRAME 0001) Recorded Jan 2, 2018
From: JPMORGAN CHASE BANK, N.A.
To: RPX CORPORATION; RPX CLEARINGHOUSE LLC
Reel/Frame 044970/0030 →
SECURITY AGREEMENT Recorded Mar 9, 2016
From: RPX CORPORATION; RPX CLEARINGHOUSE LLC
To: JPMORGAN CHASE BANK, N.A., AS COLLATERAL AGENT
Reel/Frame 038041/0001 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Feb 9, 2015
From: ROCKSTAR CONSORTIUM US LP; ROCKSTAR CONSORTIUM LLC; BOCKSTAR TECHNOLOGIES LLC; CONSTELLATION TECHNOLOGIES LLC; MOBILESTAR TECHNOLOGIES LLC; NETSTAR TECHNOLOGIES LLC
To: RPX CLEARINGHOUSE LLC
Reel/Frame 034924/0779 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Mar 6, 2014
From: ROCKSTAR BIDCO, LP
To: ROCKSTAR CONSORTIUM US LP
Reel/Frame 032399/0442 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Oct 28, 2011
From: NORTEL NETWORKS LIMITED
To: ROCKSTAR BIDCO, LP
Reel/Frame 027164/0356 →
CORRECTIVE ASSIGNMENT TO CORRECT THE NAME OF THE RECEIVING PARTY TO REMOVE PART OF ADDRESS PREVIOUSLY RECORDED ON REEL 010125 FRAME 0398. ASSIGNOR(S) HEREBY CONFIRMS THE RECEIVING PARTY'S NAME IS NORTEL NETWORKS CORPORATION. Recorded May 9, 2011
From: ADAMS, RODNEY G.
To: NORTEL NETWORKS CORPORATION
Reel/Frame 026242/0520 →