(12) United States Patent
`Isaac et al.
`
`(10) Patent N0.:
`(45) Date of Patent:
`
`US 6,632,248 B1
`Oct. 14, 2003
`
`US006632248B1
`
`(54)
`
`(75)
`
`CUSTOMIZATION OF NETWORK
`DOCUMENTS BY ACCESSING
`CUSTOMIZATION INFORMATION ON A
`SERVER COMPUTER USING UNIQUIE
`USER IDENTIFIERS
`
`Inventors: Steven A. Isaac, Bellevue, WA (US);
`Mark B. Grossman, Kirkland, WA
`(US); Ron E. Critch?eld, Redmond,
`WA (US); Michael H. Tuchen, Seattle,
`WA (US); James S. Gwertzman,
`Seattle, WA (US); Paul A. McDaniel,
`Bellevue, WA (US)
`
`(73)
`
`Assignee: Microsoft Corporation, Redmond, WA
`(Us)
`
`(*)
`
`Notice:
`
`Subject to any disclaimer, the term of this
`patent is extended or adjusted under 35
`U.S.C. 154(b) by 1184 days.
`
`(21)
`(22)
`(51)
`(52)
`(58)
`
`(56)
`
`Appl. No.: 08/761,566
`Filed:
`Dec. 6, 1996
`
`Int. Cl.7 .............................................. .. G06F 15/00
`
`US. Cl. . . . . . . . . . . . . . . . .
`
`. . . . . . . .. 715/501.1
`
`Field of Search ............................... .. 707/501, 513,
`707/514, 10, 104; 345/329, 333; 715/501.1,
`513, 514
`
`References Cited
`
`U.S. PATENT DOCUMENTS
`
`5,617,565 A * 4/1997 Augenbraun et al. ........ .. 707/4
`5,727,129 A * 3/1998 Barrett et al. ............... .. 706/10
`
`5,740,252 A * 4/1998 Minor et al. . . . . . .
`5,740,549 A * 4/1998
`5,774,670 A * 6/1998
`5,796,395 A * 8/1998
`5,819,284 A * 10/1998
`5,826,242 A 10/1998
`
`. . . .. 380/49
`
`OTHER PUBLICATIONS
`
`Van Name et al., “Web Security and the Cookie Contro
`versy,” PC Week (Jul. 1996) (1 page).
`Amdur, “NeW sites aim to personalize Web navigation”,
`Information & Interactive Services Report, BRP Publica
`tions, vol. 17, Issue 31, 9/96, pp. 1—5.*
`Herzoff, “Cookies are not alWays a treat for Web users”,
`NetWork World, 11/96, p. 38.*
`O’Brien, “HoW to put together an Internet Web site—
`Cookies keep’em coming back for more”, InterActivity,
`6/96, v2 n6, pp. 59—61.*
`“Persistent client state HTTP cookies”, http://oradb1.jinr.ru/
`netscape/MISC/cookieispec.htm, Aug. 24, 1996, pp1—5.*
`“Proposal for Extending Persistent Client State HTTP Cook
`ies”, http://WWW.sbm.temple.edu/~magnus/ext13 cookiei
`spec.html, Mar. 29, 1996, pp. 1—7.1—5.*
`Markoff (1999) “Microsoft Will Alter Its Software In
`Response to Privacy Concerns” The New York Times, Mar.
`6, 1999.
`(Nov. 30, 1995), Microsoft Unveils Enhanced World Wide
`Web Site>MSFT, DoW Jones NeWs Service, Copyright@
`1995), DoW Jones & Company, Inc.
`(Nov. 30, 1995), MSN, The Microsoft NetWork Offers
`Enhanced World Wide Web Site, PR neWsWire, Copyright©
`1995).
`(Nov. 30, 1995), Microsoft NetWork Adds Multimedia Chat
`Service, NeWsbytes NeWs NetWork, Nov. 30, 1995.
`
`* cited by examiner
`
`Primary Examiner—Stephen S. Hong
`(74) Attorney, Agent, or Firm—Klarquist Sparkman, LLP
`(57)
`ABSTRACT
`
`User-selected customization information for a netWork (e. g.,
`HTML) document is stored at a server With reference to user
`identifying information that uniquely identi?es the user.
`Whenever the user navigates back to the netWork address of
`the HTML document, the user is identi?ed automatically
`and receives a customized HTML document formed in
`accordance With the customization information.
`
`20 Claims, 6 Drawing Sheets
`
`Return custom HTML
`document
`
`Return default HTML
`document
`
`User navigates link and server returns
`HTML customization document to user
`client
`I
`user selects customization options in
`HTML customization document and
`returns options (0 server
`
`i
`
`Server stores customlzation options
`reierenced to customization persistent
`client state information
`
`Server returns customization persistent
`client state lniorrnation to user client
`
`96
`
`r95
`
`r100
`
`102
`
`Petitioners Great West Casualty Co., BITCO Gen. Ins. Corp., and BITCO Nat'l Ins. Co.
`Ex. 1017, p. 1
`
`

`
`U.S. Patent
`
`061. 14, 2003
`
`Sheet 1 6f 6
`
`US 6,632,248 B1
`
`mm
`
`ow
`
`on
`
`@955 @3566
`
`
`SE
`
`dm<om>w£
`
`35 .mwEEQ
`
`53%;;
`
`mm
`
`mm
`
`_ _
`
`_
`
`_ _ _ _
`
`
`u / :75 / woéohw
`
`
`u . _ SE20 5,5200%
`
`mm a‘
`
`_1 llllllllllllllllllllllllll I I |_
`
`_ w?iwwm
`
`“ E052
`3 / z_<_>_
`_ 316
`3< NM
`
`“ \ \
`
`_ vw WEPDQEOO ow
`
`
`
`_ E0 E596 Eosmz
`
`Nw _\ @E
`
`
`
`||||||| IIWIIIIIIIIIIIIIIIIIII
`
`Petitioners Great West Casualty Co., BITCO Gen. Ins. Corp., and BITCO Nat'l Ins. Co.
`Ex. 1017, p. 2
`
`

`
`U.S. Patent
`
`Oct. 14, 2003
`
`Sheet 2 0f 6
`
`US 6,632,248 B1
`
`FIG. 2
`
`HTML
`DOCUMENT
`
`DEPENDENCIES
`
`INTERNET EXPLORER
`
`__ [:1 X
`
`
`
`(:1 Q x Q,‘ 6 Address: hhp://www.microso?.com
`
`DOCUMENT DISPLAY AREA
`
`A
`
`__r- 14
`
`__,_,-—- 72
`
`V
`
`Petitioners Great West Casualty Co., BITCO Gen. Ins. Corp., and BITCO Nat'l Ins. Co.
`Ex. 1017, p. 3
`
`

`
`U.S. Patent
`
`Oct. 14, 2003
`
`Sheet 3 6f 6
`
`US 6,632,248 B1
`
`Fig. 3
`
`User navigates client to customizable
`network address
`
`82
`
`/"
`
`80
`
`84
`
`Previous
`customization
`?
`
`Yes
`/ f as
`Return custom HTML
`document
`
`No
`\ /- 88
`Return default HTML
`document
`
`\/r 96
`
`User navigates link and server returns
`HTML customization document to user
`client
`1
`User selects customization options in
`HTML customization document and
`returns options to server
`
`r98
`
`i
`Server stores customization options
`referenced to customization persistent
`client state information
`
`fioo
`
`r102
`i
`Server returns customization persistent
`client state information to user client
`
`Petitioners Great West Casualty Co., BITCO Gen. Ins. Corp., and BITCO Nat'l Ins. Co.
`Ex. 1017, p. 4
`
`

`
`U.S. Patent
`
`061. 14, 2003
`
`Sheet 4 6f 6
`
`US 6,632,248 B1
`
`Fig. 4
`Internet Explorer
`
`A
`D X
`92
`
`FAVORITE LINKS
`
`Latest Updates [:1
`
`Link of the Day E]
`
`URL
`http:/l
`
`I
`l
`l
`
`I
`I
`
`Site Name
`Address
`I MS Information I
`I www.microsoft.com I
`l
`l
`l
`l
`l
`l L
`l
`
`NEWS
`
`World News
`
`[:I
`
`National News El
`
`COMMERCE Commerce News IX]
`
`lnvestorNews I3
`
`SPORTS
`
`Sports Scores
`
`Stock Ticker - Enter stock symbols to track stocks
`
`ilLli II
`Sports News C]
`
`II
`
`II
`
`Baseball E College Football El
`NFL
`[5]
`College Basketball CI
`NHL
`I:
`NBA
`[2|
`
`ENTERTAINMENT Culture & Opinion [Z]
`Movie Reviews [XI
`TV Listings
`[:I
`
`Music News B]
`Movie Times El
`Concerts & Events IX]
`
`SCI-TECH Sci-Tech News I:
`
`Computer News [XI
`
`WEATHER
`
`National
`
`[:1
`
`World
`
`[XI
`
`Petitioners Great West Casualty Co., BITCO Gen. Ins. Corp., and BITCO Nat'l Ins. Co.
`Ex. 1017, p. 5
`
`

`
`U.S. Patent
`
`0a. 14, 2003
`
`Sheet 5 6f 6
`
`US 6,632,248 B1
`
`Fig. 5
`
`110 /
`
`116
`
`/.
`
`114
`/
`User with customization persistent client
`state information navigates client to
`customizable network address
`l
`Client passes customization persistent
`client state information to customizable
`network address
`I
`Server at customizable network
`address correlates customization
`persistent client state information with
`customization options
`i
`Server at customizable network
`address returns customized HTML
`document
`
`118
`
`120
`
`Petitioners Great West Casualty Co., BITCO Gen. Ins. Corp., and BITCO Nat'l Ins. Co.
`Ex. 1017, p. 6
`
`

`
`U.S. Patent
`
`Oct. 14, 2003
`
`Sheet 6 6f 6
`
`US 6,632,248 B1
`
`Fig. 6
`
`Internet Explorer
`
`_ D X
`
`112
`
`FAVORITE LINKS
`
`Link of the Day
`
`Ms Information Link
`
`NEWS
`
`[News display window]
`
`COMMERCE
`
`[Commerce news display window]
`
`SPORTS
`
`[Sports scores display window:
`Baseball, NFL NBA]
`
`ENTERTAINMENT
`
`L Culture and Opinion Display Window
`L Movie Reviews Display Window
`I
`Music News Display Window
`I
`Concerts & Events Display Window
`
`SCI-TECH
`
`I
`
`Computer News Display Window
`
`WEATHER
`
`.
`L World Weather Display Window
`
`I
`I
`I
`I
`
`I
`
`I
`
`Petitioners Great West Casualty Co., BITCO Gen. Ins. Corp., and BITCO Nat'l Ins. Co.
`Ex. 1017, p. 7
`
`

`
`US 6,632,248 B1
`
`1
`CUSTOMIZATION OF NETWORK
`DOCUMENTS BY ACCESSING
`CUSTOMIZATION INFORMATION ON A
`SERVER COMPUTER USING UNIQUIE
`USER IDENTIFIERS
`
`FIELD OF THE INVENTION
`
`This invention relates generally to providing information
`to a user Who accesses a document at a site on a computer
`netWork like the Internet or an intranet and, in particular, to
`automatically providing selected or customiZed information
`to the user.
`
`BACKGROUND AND SUMMARY OF THE
`INVENTION
`
`The Internet is a Well knoWn, global netWork of coopera
`tively interconnected computer netWorks. The World Wide
`Web portion of the Internet is a collection of server com
`puters (referred to as “sites”) on the Internet Which store
`HTML documents that can be publicly accessed by com
`puter users having a connection to the Internet. There are
`many such World Wide Web sites on the Internet.
`SoftWare, generally knoWn as “Internet browsers,” is noW
`in Wide-spread use for retrieving (also knoWn as
`“doWnloading”) from the World-Wide Web and vieWing
`electronic documents in hyper-text markup language
`(HTML) format. Originally, these HTML documents Were
`simply ASCII coded character ?les generally consisting of
`text and HTML “tags” that specify formatting of the
`document, links (referred to as “hyper-links”) to related
`documents on the netWork, and other ?les that contain
`information (e.g., sound, images, video, etc.) to be combined
`into the document. Typical HTML documents found on the
`World Wide Web, sometimes referred to as Web pages,
`include both text and tags specifying ?les for images that are
`to be displayed With the text. In use, broWser softWare alloWs
`a user to navigate (also knoWn as “broWse”) betWeen
`documents and sites on the World-Wide Web.
`Conventional HTML documents found on the World Wide
`Web are static in that the document is simply transferred to
`each user Who navigates to the document. Although the
`document may include images or other media formats, the
`HTML document transferred to each user is the same. The
`strength of such a document format is that it includes links
`to other documents or sites by Which the user can navigate
`to a desired document or site.
`A common type of document on the World-Wide Web is
`the top-level or trunk document for a particular site, often
`referred to as its home page. Ahome page typically provides
`a user Who accesses it With general information about the
`provider of the netWork site and organiZational information
`about, and access to, loWer levels the netWork site. Another
`common type of document provides users With a convenient
`gateWay to the World Wide Web. These types of documents
`commonly provide access to netWork search tools or
`services, neWs or other current event highlights, links to
`other sites of interest, etc. Such a netWork gateWay type
`document may be a home page or a loWer-level document
`for a particular netWork site.
`It is a shortcoming of conventional HTML documents that
`all users Who access a document receive the same informa
`tion and links. In the context of a home page or a netWork
`gateWay document, the static nature of HTML documents
`requires that only generaliZed information and links are
`included in the document so that it appeals to the Widest base
`
`10
`
`15
`
`25
`
`35
`
`45
`
`55
`
`65
`
`2
`of users. Excessive information and links in the document
`Would cause it to be too large to be practicable for most
`users. For users accessing the World-Wide Web over con
`ventional “POTS” telephone connections and modems,
`excessively large HTML documents can require more time
`for transmission than many users are Willing to accept.
`To overcome these shortcomings of conventional HTML
`documents, an HTML document customiZation method
`obtains and stores for a user customiZing information for a
`customiZable HTML document on a computer netWork like
`the Internet or an Intranet. The customiZable HTML docu
`ment may be a top-level, trunk, or home page for a netWork
`site or a World-Wide Web gateWay, or could be of any level
`at the netWork site and provide virtually any functionality of
`an HTML document.
`One aspect of the method occurs When a user navigates to
`the netWork address (e.g., Uniform Resource Locator) asso
`ciated With the customiZable HTML document and is offered
`the ability to customiZe the HTML document. The user
`might not have been to the netWork address before, or not
`elected to customiZe the HTML document during a previous
`access of it, or Will elect to revise customiZation options
`selected for the HTML document during a previous access
`of it. The server returns an HTML customiZation document
`to the user. In one embodiment, the HTML customiZation
`document is an HTML form that includes topical groupings
`of customiZation options relating to, for example, favorite
`links, neWs, sports, ?nancial matters, entertainment, science
`and technology, life, Weather, etc. that a user selects With
`graphical check boxes, buttons, etc. The customiZation
`options may relate to links to sites that provide information
`on indirect links to the selected topics. In addition, the
`HTML customiZation document can alloW the user to des
`ignate speci?c netWork addresses or URLs to be included on
`the customiZed HTML document. The user returns the
`selected customiZation options to the server as customiZa
`tion information.
`The customiZation information is stored at the server With
`reference to user identifying information that uniquely iden
`ti?es the user, and the server returns the user identifying
`information to the user (i.e., the broWser on the user com
`puter or client). In one embodiment, the user identifying
`information is customiZation persistent client state
`information, sometimes referred to as a “cookie.” The cus
`tomiZation persistent client state information is or includes,
`for example, 128-bit globally unique identi?ers (“GUID”)
`that are capable of uniquely identifying each and every user.
`Whenever the user navigates back to the netWork address
`associated With the customiZable HTML document, the
`broWser on the user client passes the customiZation persis
`tent client state information or “cookie” back to the server.
`The server correlates the customiZation persistent client state
`information With the customiZation options stored at server
`and returns to the user client a customiZed HTML document
`formed in accordance With the customiZed options stored at
`server. The customiZed HTML document may include infor
`mation on the selected topics, obtained from other sites, for
`example, or direct links to the other sites that have the
`information.
`This HTML or netWork document customiZation is
`capable or providing each user Who accesses a netWork
`address With an HTML document that is matched to that
`user’s preferences. This customiZation adds to the strength
`of linked information provided by HTML documents by
`providing each user With the information, or links to
`information, that the user actually Wants. CustomiZation of
`
`Petitioners Great West Casualty Co., BITCO Gen. Ins. Corp., and BITCO Nat'l Ins. Co.
`Ex. 1017, p. 8
`
`

`
`US 6,632,248 B1
`
`3
`HTML documents is particularly bene?cial for home pages,
`network gateway pages, or any other pages that potentially
`provide direct access to a Wide variety of links or informa
`tion.
`Additional features and advantages of the invention Will
`be made apparent from the folloWing detailed description of
`an illustrated embodiment Which proceeds With reference to
`the accompanying draWings.
`
`BRIEF DESCRIPTION OF THE DRAWINGS
`
`10
`
`15
`
`FIG. 1 is a block diagram of a computer system that may
`be used to implement a method and apparatus embodying
`the invention.
`FIG. 2 is a block diagram of the computer system of FIG.
`1 connected to a remote computer netWork (e. g., the
`Internet) for locally broWsing electronic documents residing
`at a remote computer site.
`FIG. 3 is a How diagram representing an HTML document
`customiZation method.
`FIG. 4 is an illustration of a simpli?ed HTML customi
`Zation document as it Would appear When rendered on the
`display of a user’s computer.
`FIG. 5 is a How diagram of a customiZed HTML docu
`ment delivery method.
`25
`FIG. 6 is an illustration of a simpli?ed customiZed HTML
`document.
`
`DETAILED DESCRIPTION OF EMBODIMENT
`Referring to FIG. 1, an operating environment for an
`illustrated embodiment of the present invention is a com
`puter system 20 With a computer 22 that comprises at least
`one high speed processing unit (CPU) 24, in conjunction
`With a memory system 26, an input device 28, and an output
`device 30. These elements are interconnected by at least one
`bus structure 32.
`The illustrated CPU 24 is of familiar design and includes
`an ALU 34 for performing computations, a collection of
`registers 36 for temporary storage of data and instructions,
`and a control unit 38 for controlling operation of the system
`20. The CPU 24 may be a processor having any of a variety
`of architectures including Alpha from Digital, MIPS from
`MIPS Technology, NEC, IDT, Siemens, and others, X86
`from Intel and others, including CyriX, AMD, and NeXgen,
`and the PoWerPc from IBM and Motorola.
`The memory system 26 generally includes high-speed
`main memory 40 in the form of a medium such as random
`access memory (RAM) and read only memory (ROM)
`semiconductor devices, and secondary storage 42 in the
`form of long term storage mediums such as ?oppy disks,
`hard disks, tape, CD-ROM, ?ash memory, etc. and other
`devices that store data using electrical, magnetic, optical or
`other recording media. The main memory 40 also can
`include video display memory for displaying images
`through a display device. Those skilled in the art Will
`recogniZe that the memory 26 can comprise a variety of
`alternative components having a variety of storage capaci
`ties.
`The input and output devices 28, 30 also are familiar. The
`input device 28 can comprise a keyboard, a mouse, a
`physical transducer (e.g., a microphone), etc. The output
`device 30 can comprise a display, a printer, a transducer
`(e.g., a speaker), etc. Some devices, such as a netWork
`interface or a modem, can be used as input and/or output
`devices.
`As is familiar to those skilled in the art, the computer
`system 20 further includes an operating system and at least
`
`35
`
`45
`
`55
`
`65
`
`4
`one application program. The operating system is the set of
`softWare Which controls the computer system’s operation
`and the allocation of resources. The application program is
`the set of softWare that performs a task desired by the user,
`using computer resources made available through the oper
`ating system. Both are resident in the illustrated memory
`system 26. Preferably, the operating system employs a
`graphical user interface Where the display output of an
`application program is presented in a rectangular area
`(sometimes referred to as a “WindoW”) on the screen of the
`output device 30 and is also multi-tasking (alloWing appli
`cation programs to execute computing tasks in multiple
`threads), such as Microsoft Corporation’s Windows@ 95 or
`Windows@ NT operating system, IBM’s OS/2 Warp oper
`ating system, Apple’s Macintosh System 7 operating
`system, X-WindoWs, etc.
`In accordance With the practices of persons skilled in the
`art of computer programming, the present invention is
`described beloW With reference to acts and symbolic repre
`sentations of operations that are performed by computer
`system 20, unless indicated otherWise. Such acts and opera
`tions are sometimes referred to as being computer-executed.
`It Will be appreciated that the acts and symbolically repre
`sented operations include the manipulation by the CPU 24 of
`electrical signals representing data bits Which causes a
`resulting transformation or reduction of the electrical signal
`representation, and the maintenance of data bits at memory
`locations in memory system 26 to thereby recon?gure or
`otherWise alter the computer system’s operation, as Well as
`other processing of signals. The memory locations Where
`data bits are maintained are physical locations that have
`particular electrical, magnetic, or optical properties corre
`sponding to the data bits.
`FIG. 2 shoWs a broWsing environment 50 in Which
`computer 20 (FIG. 1) as a client runs softWare, referred to
`herein as a “broWser,” for uni?ed broWsing of electronic
`documents and other data from local sources (e.g., the
`secondary storage 42 of FIG. 1) and from a remote computer
`netWork 52. The broWser can be integrated With the oper
`ating system softWare, or can be separate application soft
`Ware. The illustrated remote computer netWork 52 may be
`the Internet or an intranet. In the illustrated broWsing envi
`ronment 50, the computer 20 connects to the computer
`netWork 52 over a telephone line 54 With a modem 56. Other
`physical connections to the computer netWork alternatively
`can be used, such as an ISDN, T1 or like high speed
`telephone line and modem, a television cable and modem, a
`satellite link, an optical ?ber link, an Ethernet or other local
`area netWork technology Wire and adapter card, radio or
`optical transmission devices, etc. The invention can alter
`natively be embodied in a broWsing environment for other
`public or private computer netWorks, such as a computer
`netWork of a commercial on-line service or an internal
`corporate local area netWork (LAN), an intranet, or like
`computer netWork.
`Documents for broWsing With the illustrated broWser can
`reside as ?les of a ?le system stored in the computer’s
`secondary storage 42 (FIG. 1), or reside as resources at a
`remote computer 58 (also referred to as a “site” or server)
`connected to the computer netWork 52, such as a World-Wide
`Web site on the Internet. The illustrated document 60 resid
`ing at the site 58 conforms With HTML standards, and may
`include eXtensions and enhancements of HTML standards.
`HoWever, the illustrated broWser also can broWse documents
`having other data formats (e.g., Microsoft® Word
`documents, etc.) from the computer 20 or remote computer
`58. In conformance With HTML, the illustrated document 60
`
`Petitioners Great West Casualty Co., BITCO Gen. Ins. Corp., and BITCO Nat'l Ins. Co.
`Ex. 1017, p. 9
`
`

`
`US 6,632,248 B1
`
`10
`
`5
`can incorporate other additional information content 62,
`such as images, audio, video, executable programs, etc.
`(hereafter simply “images” 62), Which also reside at the
`remote computer 58. The document 60 and images 62
`preferably are stored as ?les in a ?le system of the remote
`computer 58. The document 60 incorporates the images 62
`using HTML tags that specify the location of ?les or other
`Internet resource containing the images on the Internet 52.
`When used for broWsing documents, the illustrated
`broWser displays the document in a WindoW 68 or rectan
`gular area of the computer’s display 30 allocated to the
`broWser by the operating system. The illustrated WindoW 68
`comprises a frame 70, a document display area 72, and user
`interface controls 74. The broWser displays the document
`Within the document display area 72 of the WindoW 68.
`FIG. 3 is a How diagram of an HTML document customi
`Zation method 80 by Which customiZing information for a
`customiZable HTML document on computer netWork 52 is
`obtained and stored for a user of client 20. The customiZable
`HTML document is described as a top-level, trunk, or home
`page for site 58 functioning as a World Wide Web gateWay.
`It Will be appreciated, hoWever, that the customiZable
`HTML document could alternatively be of any level at site
`58 and provide virtually any functionality of an HTML
`25
`document. Process block 82 indicates that a user navigates
`client 20 to the netWork address (e.g., Uniform Resource
`Locator) of customiZable HTML document at site 58. Client
`20 in this step might not been to the netWork address before,
`or might not have elected to customiZe the HTML document
`during a previous access of it, or might have elected to
`customiZe the HTML document during a previous access of
`it.
`
`15
`
`6
`uniquely identi?es the user. Process block 102 indicates that
`server 58 returns the user identifying information to the
`broWser on user client 20. In one embodiment, the user
`identifying information is customiZation persistent client
`state information, sometimes referred to as a “cookie.” The
`customiZation persistent client state information is or
`includes, for example, 128-bit globally unique identi?ers
`(“GUID”) that are capable of uniquely identifying each user
`that elects customiZation. Such identi?ers may be created for
`example With a function callnamed “CoCreateGUID” from
`the Win32TM library of functions available in the WindoWs
`95 and WindoWs NT operating systems available from
`Microsoft Corporation.
`Although described as using a persistent client state to
`carry identifying information betWeen user client 20 and
`server 58, the customiZation of HTML or other netWork
`documents is substantially independent of hoW the identi
`fying information is conveyed betWeen user client 20 and
`server 58. The information can be conveyed in any of a Wide
`variety of forms or formats, including basic authentication
`as set forth in the hypertext transfer protocol standard (e.g.,
`HTTP 1.1), any other client certi?cation standards, or even
`simple usernames or passWords. UtiliZation of usernames
`and passWords for identifying clients is incorporated, for
`example, in the Internet Information Server (IIS) feature in
`the WindoWsTM NT operating system of Microsoft Corpo
`ration. With identifying information from the user, regard
`less of the format or manner conveyed, the customiZation
`options selected by a user can be correlated With and
`returned to that user.
`Apersistent client state, or “cookie,” is generally arbitrary
`text information (e.g., of up to 255 characters) returned to
`user client 20 by server 58 When it is accessed by user client
`20. The information includes one or more netWork addresses
`(e.g., Uniform Resource Locators, URLs) for Which the
`persistent client state is applicable. For a broWser that
`accommodates client states, user client 20 stores the client
`state information. On subsequent accesses of any of the
`speci?ed netWork addresses by the broWser on user client
`20, selected information in the client state is returned to
`server 58. Abene?t of using a persistent client state to carry
`the information is that it is automatic and transparent to the
`user.
`
`Apersistent client state is speci?ed by a Set-Cookie HTTP
`response header of the form:
`Set-Cookie: name=VALUE; expires=DAT E;
`path=PATH;domain=DOMAINiNAME; secure.
`For example, When it requests an HTML document from a
`netWork address on server 58, the broWser determines
`Whether the address matches or corresponds to the addresses
`or paths speci?ed in any of the stored persistent client states.
`For each persistent client state matching or corresponding to
`the address, the broWser transmits the name and value of the
`persistent client state With the HTML document request. The
`format of the transmission is:
`
`.
`
`.
`
`Cookie: name1=VALUE1; name2=VALUE2; .
`The attributes of the Set-Cookie header are:
`name=VALUE
`This attribute speci?es the name and content of the
`persistent client state data and is the only required attribute
`on the Set-Cookie header. The name and its value can be any
`sequence of characters, except semi-colon, comma and
`White space. For example, this attribute can have the name
`‘User’ and the content or value can be a 128-bit globally
`
`Decision block 84 represents an inquiry Whether client 20
`has customiZed the HTML document during a previous
`access of it. Decision block 84 proceeds to process 86 if
`client 20 has customiZed the HTML document during a
`previous access of it, and otherWise proceeds to process
`block 88.
`Process block 86 indicates that server 58 returns a cus
`tomiZed HTML document to client 20 via the broWser. The
`customiZed HTML document includes a link by Which the
`user can navigate to an HTML customiZation document 92
`(FIG. 4).
`Process block 88 indicates that server 58 returns a default
`HTML document (not shoWn) to client 20 via the broWser.
`The default HTML document includes a link by Which the
`user can navigate to HTML customiZation document 92.
`Process block 96 indicates that the user navigates or
`activates the link to HTML customiZation document 92 so
`that server 58 returns the document to user client 20. In one
`embodiment, HTML customiZation document 92 is an
`HTML form that includes topical groupings of customiZa
`tion options relating to, for example, neWs, sports, ?nancial
`matters, entertainment, science and technology, life,
`Weather, etc. (not all of Which are shoWn), that a user selects
`With graphical check boxes, buttons, etc. The customiZation
`options may relate to links to sites that provide information
`on, or direct links to, the selected topics. In addition, HTML
`customiZation document 92 can alloW the user to designate
`speci?c URLs to be included on the customiZed document.
`The user returns the selected customiZation options to server
`58 as customiZation information.
`Process block 98 indicates that the user selects customi
`Zation options and returns them to server 58. Process block
`100 indicates that the customiZation information is stored at
`server 58 With reference to user identifying information that
`
`35
`
`45
`
`55
`
`65
`
`Petitioners Great West Casualty Co., BITCO Gen. Ins. Corp., and BITCO Nat'l Ins. Co.
`Ex. 1017, p. 10
`
`

`
`US 6,632,248 B1
`
`7
`unique identi?er (“GUID”) referenced to the time the user
`accesses the network address.
`expires=DATE
`This attribute speci?es an expiration date for the persis
`tent client state. After expiration, the persistent client state is
`no longer stored or returned to the server at the originating
`netWork address. The DATE is formatted as:
`Wdy, DD-Mon-YYYY HH:MM:SS GMT
`If this attribute is not set, then the persistent client state
`expires immediately after leaving the speci?ed netWork
`address. Accordingly, this attribute is set to alloW customi
`Zation information to be retrieved for a user during subse
`quent accesses of the speci?ed netWork addresses.
`domain=DOMAINiNAME
`This attribute speci?es a top level or “tail” domain to be
`initially examined When searching for a valid persistent state
`client in a list of persistent state clients. The top level or
`“tail” domain requires at least three periods, such as
`“.custom.home.uk,” except that only tWo periods are
`required in the top level domains “com”, “edu”, “gov”,
`“int”, “mil”, “net”, and “org”. A persistent state client With
`a matching top level domain match proceeds to path match
`ing. The default value of this attribute is the host name of the
`server generating the persistent state client.
`path=PATH
`The path attribute speci?es the netWork addresses (e.g.,
`URLs) Within a domain for Which the persistent state client
`is valid (i.e., returned by the broWser on user client 20 When
`the speci?ed netWork address is requested or accessed). The
`format for this attribute is ‘path=/foo’, and the persistent
`state client is returned only if the broWser requests a netWork
`address (e.g., URL) in the path ‘/foo’ or loWer, such as
`‘/foo/default’. The most general speci?cation is ‘path=/’. If
`this attribute is not speci?ed, the default path is the same as
`the path for the document With Which the persistent client
`state is associated.
`secure
`If this attribute is set, the persistent state client is trans
`mitted from user client 20 only if the communication
`channel With server 58 is secure (e.g., utiliZing a secure
`socket layer). If this attribute is not speci?ed, the persistent
`client state is sent regardless of the security of the channel.
`FIG. 5 is a How diagram of a customiZed HTML document
`delivery method 110 by Which a customiZed HTML docu
`ment 112 (FIG. 6) is delivered to user client 20. Customized
`HTML document 112 illustrates generally an exemplary
`lay-out of a customiZed HTML document corresponding to
`the exemplary selections in HTML customiZation document
`92 (FIG. 4).
`Process block 114 indicates that a user navigates client 20
`to the netWork address (e.g., Uniform Resource Locator) of
`customiZable HTML document at site 58. The broWser on
`user client 20 in this step has customiZation persistent client
`state information by Way of customiZation method 80.
`Process block 116 indicates that the broWser on user client
`20 passes the customiZation persistent client state informa
`tion to server 58 as a result of accessing the netWork address
`designated in the information.
`Process block 118 indicates that server 58 correlates the
`customiZation persistent client state information (i.e., the
`user identifying information) With the customiZation options
`stored at server 58. The customiZation options stored at
`server 58 may be correlated in any conventional database
`format. The customiZation options may include a Wide
`variety of information such as, for exampl