APPENDIX A - PAYNE AND RELATED REFERENCES
`
`The payment URL authenticator is a hash of other information
`in the payment URL, the hash being defined by a key shared by
`the merchant and the operator of the payment computer.”
`
`(Payne, Col. 5, lines 27-46) ~
`
`Payne further teaches associating a payment object identity (i.e., the .
`signature or hash, which is the MD5 hash of the attributes and
`information entries in -the payment URL) with information entries
`(e.g., a text description of the item to‘be put into the buyer’s
`Smartstatement) and attributes (e.g., desc is an attribute).
`
`A payment URL looks likn this:
`
`zitcp: / /payment: xapenrnarkec . com/pay . cgi ?hash: EieJcl1=va1n;e1& Eieldzavaiuez
`
`In any of the field values, the fottowing characters arccscapeu: ’+'.
`anything less than 03:21).
`
`'
`
`‘=’. ' ', and
`
`‘The URL fields cucudr: Lin: dcusils uf (Inc payinctn urdcr:
`
`I
`Description (desc)
`This is a text description or the item to he put imu lhc buyer's Smm1S£memea1t
`
`Sigiamun: lhsaash)
`The signature (hash) is computed as the MD5 hash of (lacy, ficldsuing}. where
`fie1dst.r‘mg1's everything after the coion. The key is a secret key shared between
`Open Market and the march.-mL The -signature prcvcms user zmnpcring oflhe
`
`(Id., Appendix E, Pg. 5, Exh. Pg. 128)5
`
`Additionally, Payne teaches associating other object identities (e.g.,
`object identities associated with a merchant computer) with
`'
`information entries and attributes. Payne teaches creating a
`signature hash associated with the information entries and attributes,
`which are included in the access URL that is sent to a merchant
`
`computer:
`
`5 For the Examiner’s convenience, Exhibit 3 has been paginated by requester, as certain
`appendices to the Payne patent do not have page numbers. Thus, citations to “Exh. p. __” are to
`the page numbers created by requester for the Exhibit.
`
`APPENDIX A — Page 8
`821
`A
`
`SAP 1002 (Part 3 of 4)
`
`CBM ofU.S. Patent No. 8,037,158
`
`821
`
`

`
`APPENDIX A - PAYNE AND RELATED REFERENCES
`
`
` 5.-‘I9
`Annotate
`gprians
`_A_Iaw‘gala
` Docnrnant 11:99: LC’: dubut on the lnmcxnut; Library or congr-
`Document LRL:
`— h?t*p:(//urn-v. opannnrtut. earn] Qofloisadnsdlobdz 66
`
`
`
`
`
`
` l.C'a debut on the Internet Library at congress
`
`
`
`-Text of Article
`
`
`(Id., Fig. 10)
`An access URL looks like this:
`' s
`
`
`
`
`http: '//merchant . £oo.<:.nai1/enash: fie1d1=va 1ue1& fie_1d2:—.ra 1u22/rea 1-ur}.
`
`
`
`anything less than 0x20.
`
`in any of thc field value-ti lht: following charactcrs arc escaped: '+’. ‘dz’. '=‘, ‘ ', and
`
`‘me URL fields encode the details nf thcawcs:
`
`
`
`
`
`
`
`
`Expirt (exp i re)
`This fields specifies the expiration time for the access. in seconds since January
`1. I970 UTC.
` {P Addnzss tip)
`‘ specifics the ip addnm from which the rcqucst must cumc
`
` Signature (hash)
`.
`Thcsignnture (hash) is computed as thr: MD5 hash of (key. ficldsu-lug I, -:vhcn:
`
`fieldstrinq is c\erylh:'ng after the colon. Thekey is a secret hy shared between
`
`Open Market and the merchant. The ipaddr is the [P addncss or the Client
`attempting natr-ss and domain is the nrrnssrinmnin. ‘fir. signature prcvrnts
`user tampering of the access URL.
`
`
`
`
`
`
`
`The effnct is to gr-mt mass to :: specified domain, frmn a specified clizcm IP addrass.
`
`for an (nptirenal) period of tirnc.
`
`
` If desired. my additional infctrmntion can be encoded in an access URL.
` User ID (id)
`The unique ID til‘ the buycr. {mm the field ptim:ipal__id of the principal lalalc in the
`
`paymcnt database. This field will be included in an access UR.L.if the name value
`
`
`pair itl=‘? was in the payment URL.
` User Name iname) '
`
`
`’
`_
`Thcprint name of the buyer. from the field [rincipnl_na:ne from the principal table
`in the payment tlat.-1basc.‘l‘his field will be included in an access URL if mt: name
`value pair id=? was in the payment URL.
`
`
`
`
`
` (Id., Appendix E, Pg. 9, Exh. Pg. 136)
` Above, the merchant access “signature(hash)” is associated with
`
`APPENDIX A — Page 9
`822
`
`822
`
`

`
`APPENDIX A - PAYNE AND RELATED REFERENCES
`
` information entries and attributes contained in the access URL (e.g.,
`User ID, User Name, IP Address).
`
`
`
`
`Payne also discloses “names”, which are unique per object, and can
`be used to access information entries and attributes:
`
`
`R=_-solvable
`
`A name will cantain encnrgh information to
`alicm the dczc'u:ren.t or
`index ta which it
`
`
`
`
`
`Unique
`
`refers to be accessed, perhaps via resolution
`into an intermediate. more. physical. name".
`Each ab‘j‘ec:. can only have one such name,
`-‘P21-e
`fact that we such names are di.E,£ezenc
`ilwlies than the objects :0 which this}! refer
`are different: {in some way) .
`
`
`
`puts SE '<2h"rU': n%\"une__.ur£1":*.ype=:cbnc:n'.bax ‘-
`lltstn 1I;'s>¢,.,'u.1.'1J>'-§>5‘!.'.¥Li. Name :5 ‘h'.£Iarvr¢sLi4'.\n-=:"8>~'-'3?‘-.2"
`‘pints $6 ‘By choosing this option van
`inclsltfifi L115. n-tum D! 3.6%?!
`
`fl.)=$—-E¥>"
`
`pm: St
`
`‘<H:i?Csn'.—'nn In1'>2ma.:1-an. :9: Scan Ihn:r:rfliz“
`
`
`
`
` (Id.,'Appendix D, Pgs. 2-3, Exh. Pgs.‘ 103-104)
`
`
`
`
`
`
`
`
`
`'
` Payne/’519 Application/Gifford
`
`Payne/’519 Application/Gifford discloses that nonces (i.e., object
`identities) representing a payment order are stored in a settlement
`
`database (i.e. a VIS), and are checked (i.e., used to identify a payment
`
`
`order object) during a payment transaction versus entries in a
`
`settlement database (VIS).
`
`“Replay is checked for by making sure that the sender did not
`previously present a payment order with the same nonce by checking
`
`an index of committed payment orders by nonce in settlement
`database 74. If nonces are based on time, then a payment order that is
`older than an administratively determined value can be rejected out
`of hand. Time based nonces or sequential nonces permit old nonces to
`be removed from the settlement database 74.”
`
`
`
`
`
`
`
`
`
`
` (’519 Application, Pg. 21, line 24 — Pg. 25, line 6) (similarly, see
`Gifford, Col. 8, lines 55-62)
` One of ordinary skill in the art would understand the nonce described in
`
`APPENDIX A — Page 10
`823
`
`(Id., Appendix F, page entitled “CustItemEntryPage.cgi,” Exh. Pg.
`164)
`
`
`
`‘Y-nu an. aim spocizy ALt1'i_§u.:ayz :.£_ys:u,~.: 15525:.”-;*u==,I be:
`am.» 3;:
`putt.» SE ‘fiat. any :0: n‘u'p:pI3.I:v:l
`Example-n: Coleen. Unighgz,
`you SE‘ "Dln:ms1mu, um-bar of Baum, Running '§'izr.o.¢,P>'
`
`o~;’|L‘,.e95r_Qfl_.‘
`.'.izn:,.'“ _
`
`823
`
`

`
`APPENDIX A - PAYNE AND RELATED REFERENCES
`
`
` Payne/’519 Application/Gifford to be a number used once, a unique
`identifier usedfor authentication purposes.
`
`Payne/’519 Application/Gifford also discloses that “digests” (i.e.,
`object identities) are sent along with an object (i.e., a payment order)
`in order to identify the object in the client or payment computers
`databases.
`
`
`
`
`
`
`
`“In a first method for authenticators, at steps 80 or 89, a digest of the
`payment order is signed by the sending computer using a public-key
`cryptographic system such as RSA. This signature is used as the
`
`authenticator. As is well known in the art, the signing can be
`
`accomplished using a private key created from a public-key pair,
`
`where the signing key is only known by the signer, and the other
`
`public key is known to the receiving computer. At the payment
`
`computer the public key corresponding to each sender is kept in
`
`credential database 76. The private key for the payment service is
`
`C also kept in database 76. At steps 82 or 91, the signature of the
`
`received message is checked using the public key known to the
`receiving computer.”
`
`
`
`
`
`
`
`
`
`
`
`(Id., Pg. 26, lines 10-22) (similarly, see Gifford, Col. 10, lines 30-42)
`
`
`“A digest of a payment order can be created with an algorithm such
`as MD5 (R. Rivest, The MD5 Message-Digest Algorithm, MIT
`
`for Comments 1321).”
`Laboratory for Computer Science, Network Working Group Request
`
`
`
`
`
`(Id., Pg. 30, lines 10-13) (similarly, see Gifford, Col. 11, lines 60-63)
`
`
`
`
`Payne/’519 Application/Gifford also discloses that an authenticator,
`generated by a Smart-Card, can be used to identify a payment order
`
`object:
`
`
`
`
`
`
`
`“In a third method for authenticators, at step 80 the authenticator is
`computed by a protected device external to the system such as a
`Smart-Card. A protected device is specifically designed to be
`extremely difficult both to replicate and to compromise.In this
`method, the payment order is communicated at 80 to a Smart-Card.
`The Smart-Card computes and signs a digest of the payment order,
`and then communicates the signature back at 80 to be used as an
`authenticator. A Smart-Card produced authenticator uniquely
`associates a payment order with its creating Smart-Card.”
`
`
`
`
`
`
`
`
`
`
`
`
`
`APPENDIX A — Page 11
`824
`
`824
`
`

`
`APPENDIX A - PAYNE AND RELATED REFERENCES
`
`
`
`
` Payne/’519 Application/Gifford discloses objects representing digital
`attributes (e.g., price, product abstract).
` “The invention relates to a network sales system for enabling users
`
`
`to purchase products using a plurality of buyer computers that
`communicate over a network with a plurality of merchant
`computers. Each merchant computer has a database of digital
`advertisements. Each digital advertisement includes a price and
`a product abstract. Buyer computers request, display, and
`respond to digital advertisements from merchant computers.”
`
`
`
`
`
`
`
`‘
`
` “A digital advertisement includes a product description and a
`
` (Id., Pg. 10, line 23 — Col. 11, line 2) (similarly, see Gifford, Col. 4,
`‘
`‘
`‘
`lines 53-56)
`
`
`Payne/’5l9 Application/Gifford also teaches a system for associating
`payment object identities (e.g., a sender-unique nonce) with payment
`
`order information entries and attributes (e.g., sender identity,
`
`
`payment amount, beneficiary):
`
`
`
`
`price. In digital advertisement database 65 prices and descriptions
`may be stored separately, and one price may apply to many
`product descriptions.”
`
`(Id., Pg. 6, line 21 — Pg.. 7, line 3) (similarly, see Gifford, Col. 3, lines
`15-21)
`_
`'
`
`
`
`
`
`
`
`
`(Id., Pg. 27, lines 10-19) (similarly, see Gifford, Col. 10, lines 54-64)
`
`advertisements, which are associated with information entries and
`
`
`
`
`“A payment order describes the identity of a sender, a payment
`‘ amount, a beneficiary, and a sender unique nonce. A sender is a
`
`principal making a payment.”
`
`
`
`(Id., Pg. 5, lines 19-22) (similarly, see Gifford, Col. 2, lines 53-55)
`
`PAYNE:
`
`Payne teaches that an object name (object identity) will represent a
`networked object. The object identity “signature” is shared over the
`network between computers via the payment URL mechanism:
`
` “The buyer, merchant, payment, and creation computers are all
`
`object;
`inter—connected by a computer network 10 such as the Internet."
`
`
`
`
`
`
`APPENDIX A — Page 12
`825
`
`
`
`wherein the
`
`object
`identity
`represents a
`networked
`
`
`
`
`
`825
`
`

`
`APPENDIX A - PAYNE AND RELATED REFERENCES
`
`(Payne, Col. 4, lines 43-45)
`
`A paymmt. URI. lrols lib: this:
`
`,-'
`
`http: //payment. cpenmarket .cam/pay . cgi '.’ha5h:.fie1d1=value1& fie1d2=valueZ
`
`In xtayot the new values. the tottowing crtaracters are escaped: '4'. ‘6c‘. ‘=1 ' ‘. and
`anything less than 01:20.
`
`The URL fluids ettculc tin: details uf tétcpayincnt Urtbr:
`
`-
`'
`Signature (hash)
`The sig nature (hash) is computed as the MEDS hash of (key. ficidstring} , where
`f ieldstzrfmg is everything after the colon. The key is :1 secret key smrcd helwecn
`Open Market and the merchant. The signature prevents user tampering of the-
`
`(Id., Appendix E, Pg. 5, Exh. Pg. 128)
`
`Additionally, Payne also teaches an object identity sent to the
`merchant computer via an access URL representing a networked
`object:
`
`H
`, Y‘
`__._.,
`.
`An nccessURLlookslik=this,:
`h'tt:.p://merchant . .£oo.<£aai{/enasttaz fie1<i1=value1& fie1d2=va'%_ue2/real-—ux'1
`
`The URL fields encode the details ofthe access
`
`Signature (hash)
`The signature (hash) is computed as the MD5 hash of (key, ftcldstring], where
`fieldstr ing is everything after the colon. The key is :1 secret key shared between
`Open Market and the merch:1nL The ipaddr is the IP address of the client
`attempting access and domain is the access domain. The signature prevents
`uscr tampering of the access URL.
`
`(Id., Appendix E, Pg. 9, Exh. Pg. l36)
`
`This paper discueaas the -tequiremcnen on a universal B3113:-32¢
`can he used to refer to objects available using existing
`protocolsv, and may be extended with teclulology-.
`It: makes a,
`recommendation for a generic mcrataac, and, for specific some
`for ‘flnifortn Reswxce Lacacozvs-'
`(UR;-mo: clajcct accessible
`using extnscirrg Internet protocols-
`
`(Id., Appendix D, Pg. 1, Exh. Pg. 102)
`
`Payne discloses that object identities (i.e., “names”) are resolvable,
`that is, they allow an object to be accessed over the network:
`
`Rasolvable
`
`enough inforntatiort to
`A name P1111
`allow the document or index. to which it
`
`APPENDIX A — Page 13
`826
`
`826
`
`

`
`APPENDIX A — PAYNE AND RELATED REFERENCES
`
`_
`
`unique
`
`imzermediace, more physical, name,
`into
`Each object can only have one such name,
`fact that we rzuch names are diffietant
`
`Th.-e
`
`implies time the objects to which they refer
`aw; diffarpnt
`(in arm: way)
`
` ruir.-rs to be econ-seed, perhaps via racoluci.-:~:n
`
`
`
`
`
` (Id., Appendix D, Pgs. 2-3, Exh. Pgs. 103-104)
`Payne/’519 Application/Gifford
`
`
`Payne/’519 Application/Gifford further teaches that an object
`identity “signature” is shared over the network between computers
`via the payment URL mechanism:
`'
`
`
`
`
`
`
`
`
`
`
`
`“The invention relates to a network sales system for enabling users
`to purchase products using a plurality of buyer computers that
`communicate over a network with a plurality of merchant
`computers. Each merchant computer has a database of digital .
`advertisements. Each digital advertisement includes a price and a
`product abstract. Buyer computers request, display, and respond to
`digital adveitisements from merchant computers.”
`‘
`
`
`
`
`
`
`
`(‘519 Application, Pg. 6, line 21 — Col. 7, line 3) (similarly, see Gifford,
`Col. 3, lines 15-21)
`-
`
`“Purchase button 48 will send the optional user reference
`string in dialog box 50 to the merchant computer described by
`the URL behind button 48 and purchase the product corresponding
`to digital advertisement 39. Cancel link 49 will return the user to
`the document shown in FIG. 2.
`
`When purchase button 48 is activated, a document 51 is sent by
`the merchant computer and displayed by the buyer computer as
`shown in FIG. 11.”
`
`(Id., Pg. 18, lines 4-12) (similarly, see Gifford, Col. 7, lines 30-38)
`
`
`
`construed, such as multimedia documents that include text, audio,
`
`“A document is defined to be any type of digital data broadly
`
`Payne/’519.Application/Gifford discloses that “documents,” such as
`‘those that are represented by the object identities in the advertising
`databases, may be broadly construed to be any kind of digital data,
`and thus can be considered “objects.”
`
`APPENDIX A — Page 14
`827
`
`827
`
`

`
`APPENDIX A - PAYNE AND RELATED REFERENCES
`
`and video, and documents that contain programs.”
`
`(Id., Pg. 11, lines 16-19) (similarly, see Gifford, Col. 5, lines 3-6)
`
`storing said
`information
`
`entries and
`said
`
`attributes in a
`virtual
`
`information
`
`PAYNE:
`
`Payne further teaches storing product information (entries and
`attributes) in a virtual information “store”. Payne discloses the use of
`an associative array (i.e., a TCL associative array, which stores the
`signature hash) to store information entries and attributes in a virtual
`information store associated with a payment computer:
`
`store;
`
`The va1ue_array contains the necessary name—va1ue pairs to handle paymen
`
`(a domain is a security 6
`...doain...
`set va1ue_array(domain)
`of the thing purchased, it is also used to detect duplic
`purchases, so it should be unique to separately buyable
`set va1ue_an-aytdesc)
`. . .item description...
`set value_array(amt)
`..monetary amount...
`set va1ue_array(cc)
`..currency code...
`(OPTIONAL. but us i
`set value_array(expire)
`..seconds of access...
`(OPTIONAL, defa
`is 30 days at the moment)
`...URL of the thing bought...
`set va1ue_array(ur1)
`(In the shopping ca t case,
`this should be the URL of
`the relevant catalog page)
`
`(Payne, Appendix E, Pg. 6, Exh. Pg. 130)
`
`In particular, in the example TCL code immediately above,‘the set
`
`value__array(desc) instruction stores the “item description” in the
`associative array “value_'array” using the attribute “desc.” A TCL
`
`associative array is an information store (i.e., the array stores data,
`such as the item description, in a table, which is indexed by the
`
`attribute “desc.”) The “set” instruction adds the information entries
`and attributes to the associative array. Therefore, Payne discloses
`storing information entries and attributes in a virtual information
`
`store associated with a payment computer.
`
`Additionally, Payne also teaches storing networked objects in a
`virtual information store associated with a merchant computer:
`
`“Creation computer 20 is programmed to build a "store" of
`products for the merchant. A printout of a computer program for
`use in creating such a "store" in accordance with the present
`invention is provided as Appendix F.”
`
`APPENDIX A - Page 15
`828
`
`828
`
`

`
`APPENDIX A - PAYNE AND RELATED REFERENCES
`
`(Id., Col. 4, lines 46-49)
`
`“[T]he payment computer creates an access URL (step 80) that
`includes a merchant computer identifier, a domain identifier, a
`product identifier, an indication of the end of the duration time for
`which access to the product is to be granted, the buyer network
`address, and an access URL authenticator that is a digital signature
`based on a cryptographic key. The access URL authenticator is a
`hash of other information in the access URL, the hash being defined
`by a key shared by the merchant and the operator of the payment
`computer. The payment computer then records the product‘
`identifier, the domain, the user account, the merchant account, the
`end of duration time, and the actual payment amount in the
`settlement database (step 88).
`
`(Id., Col. 7, lines 18-30)
`
`Figure 10 discloses an access URL, which consists of information
`entries and attributes (e.g., expiration date, user name) associated
`with an object identity (the “hash” signature” in the access URL),
`which would be stored in a virtual information store associated with a
`merchant computer, in a similar manner to that described for the
`payment URLs associated with a payment computer, above.
`
`APPENDIX A — Page 16
`829
`'
`
`829
`
`

`
`APPENDIX A — PAYNE AND RELATED REFERENCES
`
`f/79 Qplians
`
`_lg‘avr'gale Annotate
`
`LC‘s dnbut ontha Internet IJhx-ary of Congress
`earlnlng
`
`(Id., Fig. 10)
`
`APPENDIX A — Page 17
`830
`
`830
`
`

`
`APPENDIX A - PAYNE AND RELATED REFERENCES
`
` Encoding access in URLs
`
`
`
`
`
`An access URL. looks like this:
`-,....-
`
`
`hl.l;p:i/1leu‘:liau1i. . [O0 .C0m/@':1:‘::l'A: fia1Ll1=va.1u€_<l& E.'u:.1c_l2=va1u-.52 (real-u1'1
` In any cf 1}]: field values. the follcawing chmactcrs arc csmpcd; ’+’. ‘E, '=‘, ' ‘. and
`'
`anything Iegs than 0x20.
` The URL fzclds encode the details of the access‘
` Expire (exp i te)
`This felds spncitics. the expiration time for me nc:cs.:. in secor.ds since January
`1. 197-) UTC.
` IP Addtz.$s(ip)
`spccifcs the ip addxcss frc-rn which the rcqucsa. must come
` Sigmlu-Y? (hash)
`Th: sigtmur: (hash) is computai as the MD!» nash 0:‘ (key. ficldslringl. wicm
`f ieldstring is everything after the colon. The key is asccret kc-y shared belwecn
`Open Manic: and the merchant. 'I'hc»ipadar is the 1P adclrcss or the ciiem
`attempting access and domain is the access domain. The sigtmuxc pcvcnia
`
`
`
`
`user tampering of the access URL.
`
`
`
`The affect is to grim acccssm 1 specified domain, from a spccifiw ciicm [P -address.
`for an (oplizinal) [.tI‘i0d nftimc.
` |r'drsircd_ any miditinnw infnrmnrinn can he cntndrd in an mrmes URL.
` User" 1D{id)
`_
`'
`The uriquc [D n!’ the buytr. {mm um: field _3rir.ci[1al_i.d of mo principal mm: in me
`pnymau database. This field will bcindudcd in an access URL ifthc name vuluc
`pair id='! was in Lhepaymenx URL.
`
`
`
`
`
`
`
`
`'
`
`_
`User Name~(name) V
`ms prim name om: wycr. from me neIaprinclpaI_nn:ne from the principal table
`in the payment database. This field will be includcd in an amass URL iflhe name
`
`
`value pair i(1=‘.7 waxin the payment URL.
`
` (Id., Appendix E, Pg. 9, Exh. Pg. 136)
`
`
`
`{mica $£ '<.m1=u'r nam¢=‘\."uaQ_url\‘ typecdhackbvx \
`KI‘:-up !¥fiQ.,,;\lét‘.1.}1“<!3‘3'3~.3¢ 9.h|$#m 95 .1n£u:ua=d/mu}!-><l~R>'
`
`puts: if ‘Bar chmsiw this ozxtian
`an ilI=:1t.1.$& Qua
`at year !.11.e.<?>'-‘—
` puma. if '<i{3?Cuu:am Intaxmtian Eur Stem I’cans~:_’;’1-last"
`
`
`put): 3’!
`‘Yuu an aim. agmaeity attribggqg ta: 39,3: pgoaneen. ta
`q;p;g:¢d-
`put: SE ‘that are not 511;’;-1/ibfi above. 5 __ Was: Colags. Eniqtag, 53:93.“
`
`‘
`put: if “E1innnz.“.ur~..n, Huubcr of Fauna. Riga: pg P_i,ma.<Ba'
`
`
`
`
` (Id., Appendix F, page entitled “CustItemEntryPage.cgi,” Exh. Pg.
`164)
`
`
`
`
`
`
`I1; is suggested. that eaah object have a
`name. This riame oouztd be stored in the object in some
`repreaentatibns. or Btored .1.n'a database accessible to the
`server, for example. Any references within that object
`In the
`should be parsed in the context of the official name.
`presence of B directcxy sayviaa,
`the ofifiicial name will
`annually be the registered name of the object. Hm-raver, a name
`in any scheme will do, so long as it is cactinfilecely sp¢ciE.ied-
`
`
`
`
`
`APPENDIX A — Page 18
`ssi
`
`831
`
`

`
`APPENDIX A - PAYNE AND RELATED REFERENCES
`
` (Id., Appendix D, Pg. 5, Exh. Pg. 106)
`
` Payne/’519 Application/Gifford
`
`
`
`
`
`
`_
`
`
`
`
`
`
`“The invention relates to a network sales system for enabling
`users to purchase products using a plurality of buyer computers
`that communicate over a network with a plurality of merchant
`computers. Each merchant computer has a database of digital
`advertisements. Each digital advertisement includes a price
`and a product abstract. Buyer computers request, display, and
`respond to digital advertisements from merchant computers.”
`
`
`
`
`
`
`~
`
`Col. 3, lines 15-21)
`
`
` (9519 Application, Pg. 6, line 21 — Col. 7, line 3) (similarly, see Gifford,
`
`
`“A digital advertisement includes a product description and a
`price. In digital advertisement database 65 prices and
`
`
`descriptions may be stored separately, and one price may apply
`to many product descriptions.” '
`‘
`
`
`
`
`
`(Id., Pg. 10, line 23 — Col. 11, line 2) (similarly, see Gifford, Col. 4,
`lines 53-56)
`
`
`Further, Payne/’519 Application/Gifford discloses a similar virtual
`information store(s) on the payment computer, for storing
`"information about accounts and purchases:
`C
`
`
`
`
`
`
`
`. each payment computer [has] an account database 73, a
`.
`‘.
`settlement database 74, an authorized address database 75, a
`sender credential database 76, a financial system interface 77,
`and a real-time authorization interface 78. The interfaces 77 and 78
`may be implemented by a single communications line.”
`
`
`
`
`
`
`
`
`
`
` (Id., page 19, lines 19-24) (similarly, see Gifford, Col. 8, lines 2-7)
`
`
`
`
`“Account database 73 maintains temporal spending amounts,
`
`such as the amount spent in the current day, and also
`
`maintains temporal spending limits. The account database may
`
`
`
`The account database, for example, has information entries and
`attributes regarding a user’s account, such as spending limits and
`amount spent, as well as identifiers for the account and its location,
`even if outside the network:
`'
`
`
`
`APPENDIXA - Page 19
`832
`
`832
`
`

`
`APPENDIX A - PAYNE AND RELATED REFERENCES
`
`also maintain a translation between principal identifiers and
`external account identifiers. Settlementdatabase 74 records
`
`committed payment orders along with any authorization
`information for the orders that was obtained from interface 78.”
`
`(Id., Pg. 20, lines 5-12) (similarly, see Gifford, Col. 8, lines 13-20)
`
`assigning a
`unique
`network
`address to
`
`said object
`identity;
`
`PAYNE:
`Payne teaches using unique network addresses (e.g., “payment
`URLs”) to identify objects associated with a payment computer:
`i
`
`“The payment URL authenticator is a hash of other information
`in the payment URL, the hash being defined by a key shared by
`, the merchant and the operator of the payment computer.”
`
`(Payne, Col. 5, lines 43-47)
`
`APPENDIX A — Page 20
`833
`
`833
`
`

`
`APPENDIX A - PAYNE AND RELATED REFERENCES
`
`file
`
`gptions
`
`flavlgare Annotate
`
`DOCWMI 71%: sun Busttnent noun
`
`Docunmt UFIL:
`
`hctxul/pay-nut.opcnanarket.canlOcs32:15(ac8on
`
`"
`
`smart Slatumofi Dot-all
`am In tho mama tuanuttm about 1 particular trauactlm tzou ycnr Bart su-anon:
`
`Tran5ac!5nn Information
`urn nctzpzlluwmupvzunrlsrc.coI1uInua/nuu'.irI|luInlu- rlnqirprluc/lknxslcl-|.I:§o
`\=ruaune.uu1a_uq'_fl: $025». .0
`currmcyt as
`£'r|nta|:t1u.n__dIu:I ‘.l'l1)7‘It)J
`initiator; x..n
`wtyktllslwu IIIRGOO
`dancrxptzuu stead can Cllltrll Article
`Alfitflti 2.95
`Uavultzctlryt nu
`imam»: 1l9.i7o.n:‘1.:
`ntnnsncttou t’
`.9
`cknninx Inna. ntxnct-3
`
`Mondmnt .5-xtomzatbn
`canvases»: 517-3::-mo:
`a.1:'c,n_;_: G;-In llncant, Inc.
`ad(tru:::_,!: 215 Pixut strut
`tax: 011421-I10:
`¢4x.I.rou_:: can-xaqo.
`ISA
`(nil: tax:-nrubaztfizpornnnahmn
`prinnlpntg-an-x Than-. now-zzlunm
`
`(Id., Fig. 12)
`
`Payne further teaches assigning a unique network address, the
`payment URL, which is a network accessible address created by
`concatenating a base URL with the object identity:
`
`Encoding payment orders in URLs
`
`:|,
`
`ApaymcntuRL1oomimms:
`
`http://payment.openr.arket.com/pay.cgi?hash:field1=va1ue1& Eieldzuvaluez
`
`(Id., Appendix E, Pg. 5, Exh. Pg. 128)
`
`APPENDIX A — Page 21 .
`834
`
`834
`
`

`
`APPENDIX A - PAYNE AND RELATED REFERENCES
`
`nph-payment script on the payment server, and the ticket which is the signed
`
`
` Two compunents are necessary for the payment URL. The URL itself, which refers to the
`nnme—value list.
` The URL is usually a constant, it is stored in ..Jliblpztyment.tcl as
`set: payl inkbase " $payment_server_root:/ bin/nph-payment: . cgi ? "
` where $payment__server_root is inherited from .../liblmaltconf
`
`The ticket is created using ..Jlib/ticltet.tcl by code like the folloiving:
` set nvtnamell valuel
`
`set uvtnamezl valuez
`
`set: ticket [create-ticket ssecretkey nv]
`
`
`
`
`
`arbitrary suing, but will usually be a 16-hex-digit DES key.
`
`
`where namel—-vatueland namcz-vatuc2 are the name value pairs to be encoded. "the
`procedure create-ticket properly formats and quotes the name value pairs, and signs
`the result using an MD5 hash of the string with the secretkey. The secretkey is an
`
`(Id., Appendix E, Pg. 10, Exh. Pg. 138).
`
`
`
`Additionally, Payne teaches assigningia unique network address (e.g.,-
`an access URL) for object identities associated with a merchant
`
`
`
`computer:
`
`
`
`
`
`“Otherwise, the payment computer creates an access URL (step 80)
`that includes a merchant computer identifier, a domain identifier, a
`product identifier, an indication of the end of the duration time for
`which access to the product is to be granted, the buyer network
`address, and an access URL authenticator that is a digital signature
`based on a cryptographic key. The access URL authenticator is a
`hash of other information in the access URL, the hash being
`defined by a key shared by the merchant and the operator of the
`payment computer.”
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`(Id., Col. 7, lines 18-27)
`
`Appendix E discloses that the access URL is created by concatenating
`an address at the merchant computer with the object identity
`(“@hash”) associated with information entries and attributes:
`
`
`
`http: I /merchant: . foo.c'Aoti1/ehashz fie1d1=va1ue1& fie,1d2:va1ue2/real-—url.
`
`
`
`
`An acccssU'RLIoolt.slikcthis:
`
`:--‘r
`
`_._.,
`
`_
`
`.5.
`
`»
`
`fie
`
`-
`
`APPENDIX A — Page 22
`835
`
`835
`
`

`
`APPENDIX A - PAYNE AND RELATED REFERENCES
`
`
`
`term "uddre:su" is xeucz-ved for an string
`‘fin:
`universal nun} .
`which specifies a more or lesa physical location- The term
`'1oca:ar" refeam to n 0121. as here defimsd.
`'
`
`(Id., Appendix D, Pg. 2, Exh. Pg. 103)
`
`
`
`
`
`
`Resolvable
`A name will ccntain enough infonnaticzn to
`allow the document
`0.1;‘ incla-.x to which it
`
`
`
`Unique
`'
`
`refers to be accessed. perhaps via xesoluticm
`intg an intemediate. more phygical, name,
`Each objeci can only have cme such name. The
`-fact: that two tzuch names are dififar.-en:
`-ituplies that the chjecns :0 which they refer"
`are different {in some way! .
`
`
`
`
`
`
`
`
`
`(Id., Appendix D, Pgs. .2-3, Exh. Pgs. 103-104)
`
`
`
`eiajegt have a n.:1_11..i:1ue
`it 1:: Suggested that
`name. This name could be. gtored. in the ohajcc: £n same
`repreeentaczions, or stored in a database
`accessible to the-
`server, E-at exaniple. Any" references within that object
`In the
`shmalid be parsed in the context of the official name.
`presence of a directory service.
`the ofifiicial
`will
`normally be the registered name oi the object. Hpwavat, a name
`in any achane will do, so lung as in is cwupletely specified.
`
`
`
`
`
`
`(1.1., Pg. 5, Exh. Pg. 106)
`
`
`
`
`
`
`
`
`an adflrassing syntax is remixed which win be able ta
`encompass ex:i.sx'.-.1'.ng physical address spaces, and be extendibke
`
`requires: that it ccncain an
`to any Euxzmtc prcuoools. This
`at
`..ide:a.'u;i15_iez--in: the pratoccnl
`in use, The .format of we rent.
`the address I.:r_1'1 necessarily depend to a certain extent on the
`
`trcuocol. .
`(Id-)
` Re ccazmenéa ciune
`
`
`This acctiun describes the syntax for."Un;‘Lfor1'm Resource
`weavers‘ (93398):
`that is.
`ba.e=L<;41'A1y p¥1Y,r.si¢a1 er..I.¢_ms§¢:3 9:
`
`
`
`objects which an t-u-.1-:ie-vable using protocols already deployed
`
`
`on the net. The generic syntax prcrvidea at framework for new
`schemes for names to be resolved using as yet xmdefined
`
`
`
`
`protocols.
`The syntax in {Inscribed in two parts; Eiratly. we give the
`syntax rules of A comglctezy specified name;
`secondly,
`the
`give the rules under which parts of thc name may be ocnxitted in
`a meal 1-detinad Eontext,
`
`
`
`
`
`(111,, Pg. 8, Exh. Pg. 109)
`
`
`APPENDIX A — Page 23
`‘
`836
`
`836
`
`

`
`APPENDIX A ~ PAYNE AND RELATED REFERENCES
`
`
` Payne/’5 19 Application/Gifford
`
`
`
`
`
`“Payment orders are signed with authenticators that can be based on
`any combination of a secret function of the payment order parameters,
`a single-use transaction identifier, or a specified network address.”
`
`
`
`
`
`
`
`
` '(‘519 Application, Abstract) (similarly, see. Gifford, Abstract)
`
`
`
`“Appendix D describes how documents are named with Uniform
`Resource Locators (URLs) in the network of computers. A
`document is defined to be any type of digital data broadly construed,
`such as multimedia documents that include text, audio, and video, and
`documents that contain programs.”
`
`
`
`(Id.,.Pg. 11, lines 14-19) (similarly, see Gifford, Col. 5, lines 1-6)
`
`“An initial user inquiry 19 from activating link 1 results in the HTTP
`request 20 for a specific document with a specified URL. The ‘URL
`specifies the name of the merchant computer. The merchant
`computer retrieves the document given the URL at 21, and returns
`it to the buyer computer at 22.”
`
`(Id., Pg. 13, lines 15-20) (similarly, see Gifford, Col. 5, lines 51-56)
`
`
`
`
`
`
`Each advertisement in the advertisement database (VIS) contains a
`link that represents a given product from a given merchant. When a
`user clicks on the link, a URL is generated which allows the user to
`enter purchase information and direct a request for a specific object
`to the merchant offering the object represented by the link, allowing
`the object to be located and sent back to the user upon payment.
`Thus, the object identified in the advertisement has a unique network
`address for the object assigned to it:
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`“Figure 9 shows digital advertisements 39, 40, 41, 42, 43, and 44
`that were found in response to the query initiated by button 40. A
`scroll bar 45 shows that there are additional digital advertisements
`that are not ‘shown. When link 46 is activated, the missing account
`information document shown in Figure 10 is returned by the
`merchant computer.
`
`
`
`
`
`
`
`
`
`Figure 10 shows that the merchant computer has partial
`information on the buyer's account. Message 47 shows that the
`merchant computer already knows the buyer's account number.
`Purchase button 48 will send the optional user reference string
`
`APPENDIX A — Page 24
`837
`
`
`
`
`
`
`
`837
`
`

`
`APPENDIX A - PAYNE AND RELATED REFERENCES
`
`in dialog box 50 to the merchant computer described by the
`URL behind button 48 and purchase the product
`corresponding to digital advertisement 39. Cancel link 49 will
`return the user to the document shown in Figure 2.
`
`When purchase button 48 is activated, a document 51 is sent
`by the merchant computer and displayed by the buyer
`computer as shown in Figure 11.”
`
`(Id., Pg. 17, line 18 — Pg. 18, line 12) (similarly, see Gifford, Col. 87,
`lines 20-38)
`
`NCSA MOSEIOI DOCUITIBM VIBW
`
`fie
`
`gprlms
`
`[(5 rlyato
`
`41!?/101819
`
`Documanf Tina;
`
`quay