Electrical computers and digital processing systems: multicomput – Computer network managing
Reexamination Certificate
1999-01-13
2001-05-22
Coulter, Kenneth R. (Department: 2154)
Electrical computers and digital processing systems: multicomput
Computer network managing
C707S793000
Reexamination Certificate
active
06237033
ABSTRACT:
FIELD OF THE PRESENT INVENTION
The present invention pertains to user-characterizing network protocol headers, such as so-called Internet “cookies,” which are used by Internet content providers for various reasons, but in particular for providing information about a user to a website operated by the Internet content provider. More particularly, the present invention pertains to a system for managing such protocol headers, enabling a user to interpret and, preferably, adjust the content of the protocol headers.
BACKGROUND OF THE INVENTION
An Internet cookie is a protocol header consisting of a string of characters (cookie content) that is inserted by a web server, operated by an Internet Content Provider (ICP), into the random access memory (RAM) on a user's computer (client) while the user is operating a browser (application program) to access web pages on the Internet, typically through an Internet Service Provider (ISP) using the World Wide Web (type of network operating system). An ICP may also be an ISP, as in the case of, for example, American On Line.
A web server may “set” a cookie at various points during a user's access of the web server. The string of characters or content comprising a cookie specifies a domain, path, lifetime and value of a variable. The variable may be, for example, the number of times the user has visited the web server or particular web pages provided by the web server, and the domain and path indicate a website (a group of similar web pages operated by a single entity). If the lifetime of the cookie is greater than the time the user spends at the website, then the cookie may be saved in a cookie file (file of cookies) for future reference by either the user, the web server setting the cookie or other web servers.
Cookies are set for many different reasons, including enabling a web server or an ICP to customize the information it provides to a user, to facilitate on-line sales or services (e.g., implementing a so-called “shopping basket”), for tracking web pages the user has visited, or for providing the web server or ICP's website with some demographic information (presumably only geographical information or at what time a user tends to visit the ICT's website).
The idea behind the use of protocol headers such as cookies is to enable a web server or ICP to gather information about a user. By setting one or more long-lived cookies in a user's cookie file, the next time the user accesses the website, the ICP can know certain information about the user that will, in theory, facilitate the user's productive use of the information accessible at the ICP's website. This works because when an ISP directs a user to a website, the browser on the user's computer examines its cookie file for cookies that have been set by the website and provides those cookies to the website by way of introducing itself (representing the user) to the website. The website may then, or sometime later, set new cookies on the users computer, or alter the value of cookies previously set there.
Cookies are also used to securely store personal data a user has shared with a website. As mentioned above, cookies et by an ICP in the RAM of a user's computer end up stored in a file on the user's hard drive if the lifetime of cookie is longer than the time the user spends at the ICP's website. All such cookies are stored in a single file on the user's hard drive (a file usually called “cookies.txt”).
More browsers today, including Netscape and Microsoft Internet Explorer, can be configured to display to a user a warning that a cookie is about to be set, and to give the user the option of blocking the cookie. The user is often even able to view the content of the cookies. However, the user often has no knowledge of the meaning of the content of the cookie nor the intended use for the cookie contents by the ICP. In some cases, when a user blocks an ICP from setting a cookie, the ICP's website refuses to allow access to the website by the user. Since there are many innocuous and quite useful reasons for a website to set a cookie, it is probably not, as a general rule, in the user's best interest to simply block all cookies.
In addition to configurable software for disabling a website from setting a cookie in the first place, the prior art includes a number of applications intended to assist a user in removing the file of long-lived cookies (the cookie file). Both the cookie-blocking browsers and cookie file managers indicate to a user the identity of the website responsible for each cookie intended to be set or stored in the cookie file. Identifying the website that set a cookie is easy because, as indicated above, each cookie includes, as text, the path and domain for the website that set the cookie. The prior art also includes software that will enable a user to remove sensitive information from the user's browser cache and cookie files.
What the prior art does not provide is a means by which a user can, using the same mechanism for exchanging information about who the user is, convey to a website preferences the user may wish to convey, instead of only preferences the website has deemed useful to know. For example, a user may wish to communicate to a website that the user would prefer to receive any advertising, demonstration material or other kinds of literature as postal mail or through a courier service.
What stands in the way of communicating such preferences is that the ICP website that set a cookie sometimes does not have variables (type of cookie) that are appropriate for what the user wants to express. What is needed is a means by which a user can not only identify and delete a cookie file or delete particular cookies within a cookie file or still in RAM, only guessing what the cookies content conveys, but a means of actually interpreting the content of the cookies within a cookie file or still in RAM, and also a means by which a user can create new types of cookies (cookies with new variables) that may be offered to a website of an ICP.
SUMMARY OF THE INVENTION
Accordingly, the present invention has as an object interpreting for a computer user the content of a user-characterizing protocol header, such as an Internet cookie, and, optionally, adjusting its content.
It is another object of the present invention to enable such a user to fabricate a user-characterizing protocol header having content of the user's own creation, and thereby convey to a website information the user wants to convey.
Correspondingly, it is a still further, optional object of the present invention to provide a means by which a website receiving from a user a protocol header fabricated by the user can interpret the protocol header if its interpretation is not apparent from inspection.
To achieve these objects, the present invention interfaces with a string of characters defining a protocol header on a user's computer to provide a user with an interpretation of at least a portion of the string of characters, the invention comprising: a dictionary containing at least one entry, the entry comprising a first string of characters representing at least a portion of the protocol header and a second string of characters representing a meaning associated with the first string of characters; an interpreter for retrieving the second string of characters based upon the first string of characters; and an editor, for displaying the second string of characters retrieved by the interpreter.
REFERENCES:
patent: 5684954 (1997-11-01), Kaiserswerth et al.
patent: 6085224 (2000-07-01), Wagner
patent: 6085230 (2000-07-01), Ryuutou et al.
patent: 6134592 (2000-10-01), Montulli et al.
Doeberl Terrence M.
Macdonald Marcy F.
Martin Judith A.
Porter Paul W
Prakash Suti
Coulter Kenneth R.
Melton Michael E.
Pitney Bowes Inc.
Reichman Ronald
LandOfFree
System for managing user-characterizing network protocol... does not yet have a rating. At this time, there are no reviews or comments for this patent.
If you have personal experience with System for managing user-characterizing network protocol..., we encourage you to share that experience with our LandOfFree.com community. Your opinion is very important and System for managing user-characterizing network protocol... will most certainly appreciate the feedback.
Profile ID: LFUS-PAI-O-2458885