`Shopify, Inc. v. DDR Holdings, LLC
`IPR2018-01011
`
`
`
`ro:rm PTONH49 {l\1odified)
`List of Pat~~nts ;:1.nd Puhlkat:kms For
`
`Serb! No.:
`Ross, D, Dchtno, Jt,
`First Inventor;
`08/]9/2013
`F'Hed:
`3625 {in p~1rent)
`i\rl Unit;
`Carg, \'.C (in parent)
`E;<<'.l.rniner:
`.. !~~]j~~-~!~~~--~:L?::~----------------------------------------------------------------------------------------------s~~::~~L-~s?:.: _____________________________ ?~~~~~---------------------------------------
`o·nnm /\Rl
`
`Cblm Clwrh hom Ddend;:tr!i:~" /\::n(•nrk·d In'/alldity Conk•nlinn~>.: Civll ./\d:\<)n
`.\lo .. 2-(!(i('\/,42 (DF}.. ;:om paring (:bhm; of R<)s~; •d: al. "U.S. f-'d:cnt 6,1'129 .. !33 t;·l
`,,..~~riot:~ refE·n.~n((:-s.~ FebrttD.ry 6 .. 2012.
`Ch'1Lm Ch.,n-·ts fwm fk;fend.<'ln.!:s' /\me.nded Inva!ldity Conh:.~nuons; Civil Action
`No. 2·C!6CV·42 (DF), u!mp<Hing d<~ims of .Ross ({ aL US. 1\:d:ent 6..903,5/2 to
`V<1riow~ rdcreru:.<:::s; Febnwry 6, 2012.
`Chim Ch<>rts f::\>tn D(:knd.<'lllh·' /\mended fnv-a!ldity (:onb:.·nt!ons; Cl\.-!l Adlon
`Nu. 2··06CV-42 (DFL C\}J"O~>f;dng chlrns nt Eoss ct -:ll. U.S. F<~lent ?,H1S.399 to
`Vi'lrl.OUS t-efCJ:<.~i\C<->:.: F,:bt'Hi'lt',Y 6, 2012.
`Ed;vards, d al,.: '·'\-taking \.toney Jn Cyber.~pace".: Sq>lcmh(;r !998,
`/\rchlved. 'Ncb pages <)t \·VW',v.wil:;,omveb.u)tn.:. Fcbnuwy 7 ..
`Arch1vcd >veb p<'lge <'ll >V\~··W.\-~··l.lsonwcb,G)n'l; Jmw 26, 1998.
`VV}h=;{~n ... T~~~~.1p.h; "f--~t~·vle~v nf s;~tO[)Stte "f\:j·~~ru}gcr ~L 1 N.~ VVe!:-s (~OiYtt:':.erce ··rod .. ay; J~;~ue
`2.: :·)cptf:mbe.r 1\ 199'7,
`Scret:n in:::}ge~ ft'()n"l \,v·\·\tV\:~v·,.tUsrln\vt:b<~:·orn ... · .~h_()~l/~ng NJ~_e\Jh~\,v of S.hopSi~c
`1\.tan;:~g~~t 3~ l(i'; frnrn. \V~:·b (\nru:nerct~ 'fod;:t} .. ;-1:-;sne 2; Septe:n"lbet lS .. 1997 ..
`\.Vil;;nn.- !(,~.lph; ''How Viah'cb ;'tn.d ShopSite Fro .tncnrpn:::i'de .A.f!:iktte Pmgum1
`Soft;.v~~J'e; ·vv~~b (:·orn.rocrc{· 'fn(L:t_}·'.: .L~stl.e 8 ... ?v'latLh. 1 :J ... 11..)98 (;:ts posh:~d. nn
`\V'N w. wil <.mnYeb,com)
`
`l90H.
`
`Archh···ed <.vcb pagr~at <.·V\V"i-l/.<.ru;,;l;:;.;:b.cnrn; \.-:hey 20,. :1998-
`''The (Dntnv Stnry", PW~" 172-l '?'6, rdening tn hi;,;tory in NPvernb<i.:r 1994,, ~vhtrc.h
`i 9~l?_ .. ;,:~nd :.\.:a:r 1y in -~ 998.:'···
`~~cre(~n i tx~~xge 6~f}rn. fh:trry···~; ~~·t: .. rnpJe of (~odz.l1]~:!; , ... /-...,v-~l/.gr~d:.:-:iJ1rth;.:nl.p1r';(<"}rn.,
`<ht) \-'>/l n.g (~J)·n(J~;\t .C(nn.; Sef>i(:rn b(:r 2-•:t. -~ 998 ..
`Screen im.<1~)e tn)J'i1 roL!lng:;;h)ne.o)n1, :;;ho<,vlng ilnks {\) CDmnv, Scpkmber 24 ..
`199:i>~
`.Hdpe.r, Ivt~rk_: .Archived v.;··eb pq~e at ',\.-·i·vw.buslnes~'Neck.o)n1, d.rd:cd. jurw !5,
`199?.,. sbo\·vi:ng ... 'C~ybersbJrefronts fc~r .Rookies~·'; ()ctn-ber 12 .. 200S.
`
`Archived >Vd~ pag>:~ at >·VV>'\V.iTederid;-';xom; J1Jly· 21, ! 997,
`Pag;:~s h:m:n Fubll:>h(:rs \\'eddy .. LLS. CopyTight Ofi:ice, and Phoenix Fublk
`Libnn-y .. .;,hm-ving pt1blk;'tlh:>n nf Edw·;ud~;' "-\:bklnr !\-Jnm:T in Cyfw·t'~<p<Ke····;
`AugDst H\ ! 99B.
`
`3f>7
`
`389
`
`39il
`
`394
`
`395
`
`396
`
`()90
`
`399
`
`402
`
`Archived web p<1W~ <'1!: w<,v\v.fn.>:::krkk~.com; Aprll W .. EN?.
`
`.
`I'
`:.xarotner:
`EX .. c\i',r!NER: lnilblli: n:~fcrdxe ~:nnsidett:d ~vhether or nnl: ;:!l:atkm is in nml'orn:L'tnno· wtih MP'EP 609. L!r;nv,
`1:\ne ihmt1gh {ll:ation )J nnt in confonnan.ce tllrd not cnn;;idct(:d, Tndude cnpv of l:hb form vvi.i:h rwxt
`communk<1tion to appl.kant
`ALL REFERENCES CONSIDERED EXCEPT WHERE LINED THROUGH. /Y.G./
`
`Page 2
`
`
`
`Form PT0-1449 (Modified)
`List of Patents and Publications For
`Information Disclosure Statement
`
`Serial No.:
`First Inventor:
`Filed:
`Art Unit:
`Examiner:
`Conf. No.:
`OTHER ART
`
`14/719009
`Ross, D. Delano, Jr.
`05/21/2015
`3625 (in parent)
`Garg, Y.C. (in parent)
`
`Page 19 of 25
`
`Examiner
`Initials
`
`Item
`
`393
`
`394
`
`395
`396
`
`397
`398
`
`399
`
`400
`
`401
`
`402
`403
`
`404
`
`405
`
`406
`
`407
`
`408
`
`409
`
`410
`
`Author Title Date Pertinent Pages Etc.
`Claim Charts from Defendants' Amended Invalidity Contentions; Civil Action
`No. 2-06CV-42 (DF), comparing claims of Ross et al. U.S. Patent 6,629,135 to
`various references; February 6, 2012.
`Claim Charts from Defendants' Amended Invalidity Contentions; Civil Action
`No. 2-06CV-42 (DF), comparing claims of Ross et al. U.S. Patent 6,993,572 to
`various references; February 6, 2012.
`Claim Charts from Defendants' Amended Invalidity Contentions; Civil Action
`No. 2-06CV-42 (DF), comparing claims of Ross et al. U.S. Patent 7,818,399 to
`various references; February 6, 2012.
`Edwards, et al.; "Making Money In Cyberspace"; September 1998.
`
`Archived web pages at www.wilsonweb.com; February 7, 1998.
`Archived web page at www.wilsonweb.com; June 26, 1998.
`Wilson, Ralph; "Review of ShopSite Manager 3.1"; Web Commerce Today; Issue
`2; September 15, 1997.
`Screen images from www.wilsonweb.com, showing "Review of ShopSite
`Manager 3.1"; from Web Commerce Today; Issue 2; September 15, 1997.
`Wilson, Ralph; "How Via Web and ShopSite Pro Incorporate Affiliate Program
`Software; Web Commerce Today; Issue 8, March 15, 1998 (as posted on
`www.wilsonweb.com)
`
`Archived web page at astrology.net; October 29, 1996.
`Archived web pages at www.viamall.com; March 29, 1997.
`
`Archived web page at www.austads.com; May 20, 1998.
`"The CDnow Story", pages 172-176, referring to history in November 1994, March
`1997, and "early in 1998."
`Screen image from Barry's Temple of Godzilla: www.godzillatemple.com,
`showing CDnow.com; September 24, 1998.
`Screen image from rollingstone.com, showing links to CDnow, September 24,
`1998.
`Halper, Mark; Archived web page at www.businessweek.com, dated June 15,
`1997, showing "Cyberstorefronts for Rookies"; October 12, 2008.
`
`Archived web page at www.fredericks.com; July 21, 1997.
`Pages from Publishers Weekly, U.S. Copyright Office, and Phoenix Public
`Library, showing publication of Edwards' "Making Money in Cyberspace";
`August 10, 1998.
`
`Archived web page at www.fredericks.com; April18, 1997.
`411
`ALL REFERENCES CONSiDERED EXCEPT WHERE LiNED THROUGH. /Y.G./
`/Y.C.G/
`ALL REFERENCES CONSIDERED EXCEPT WHERE LINED THROUGH.
`Date Considered: 11/09/2016
`Examiner:
`
`/YOGESH C GARG/
`
`EXAMINER: Initial if reference considered whether or not citation is in conformance with MPEP 609. Draw
`line through citation if not in conformance and not considered.
`Include copy of this form with next
`communication to applicant.
`
`Page 3
`
`
`
`Comparison of U.S. Patent No. 6,629,135 and U.S. Patent No. 6,330,575 to Moore (“Moore ’575”)1
`
`Comparison of U.S. Patent No. 6,629,135 and U.S. Patent No. 6,330,575 to Moore (“Moore ’575”)
`
`Based upon the Court’s claim construction order [DI 309], the claim interpretations Plaintiff appears to be asserting and the alleged applications of
`those interpretations to one or more products of Defendants’ products in Plaintiff’s Amended Infringement Contentions served January 23, 2012, the
`U.S. Patent No. 6,330,575 to Moore anticipates and/or renders obvious, alone or in combination with other prior art identified in Defendants’
`Amended Invalidity Contentions, the asserted claims as described in part below.
`
`Claim
`No.
`
`Claim Language of U.S. Patent No. 6,629,135
`
`Relevant Disclosure in U.S. Patent No. 6,330,575 (“Moore ’575”)
`
`Moore ’575, 10:44-53.
`
`Claim Language of U.S. Patent No. 6,629,135
`
`Relevant Disclosure in U.S. Patent No. 6,330,575 (“Moore ’575”)
`
`Claim
`No.
`
`8
`
`An e commerce outsourcing process providing a
`host website in communication with a visitor
`computer with context sensitive, transparent e
`commerce support pages, comprising the steps
`of:
`
`Briefly, according to the invention a method for designing a Web page,
`to be hosted on a Web page server, comprises: providing an object-
`oriented, template-driven interface for a customer to utilize in the design
`of the Web page. This allows the customer, through the use of the
`interface, to design the Web page. The method also comprises the step
`of publishing the Web page at a destination of the customer's choosing.
`
`Briefly, in accordance with another aspect of the invention, a method for
`designing a Web page for use in a distributed electronic commerce
`system is provided. The commerce system comprises a Web page server
`and a second server which are electrically coupled to each other, and the
`Web page server hosts the Web page. The method comprises: creating a
`link to the second server; designing the Web page such that the link can
`be embedded into the Web page; and embedding the link into the Web
`page.
`
`Moore ’575, 3:23-39.
`The Development Tool is object-oriented and template-driven, and it
`enables its customer, which is the merchant, to design a web site in only
`a few minutes and does not require any special Internet knowledge from
`the merchant. The Development Tool breaks the design process down
`into four steps. The first is to select a Web site category. The second is
`to collect optional page header and footer information. The third is to
`choose the defaults for the background color or image and for the page
`style. The fourth is to fill in the content of each page.
`
`8(a)
`
`capturing a look and feel description associated
`with a host website;
`
`The first step is to select a category. The category is selected from a list
`of ten industries such as automotive, dining, and education. Referring to
`FIG. 6, there is shown a screen 600 containing a list of possible
`industries to choose from in the Development Tool. Alternate
`embodiments could employ different industries and a different number
`of choices. The list 600 also illustrates the simplicity of the merchant
`interface. The selected category is used by the Development Tool to
`preselect the image libraries and page style libraries that will be used in
`the fourth step. The Development Tool thus simplifies for the merchant
`the processes of finding appropriate clip art and page styles.
`
`The second step is to create the default header and footer. The page
`header and footer are typically used for the company name and logo. An
`email address and a link URL are also commonly included. As with
`many of the features of the Development Tool, the field size may be
`adjusted and images may be loaded. In this case, the height of the
`header, for example, may need to be increased in order to accommodate
`a particular company logo. Referring to FIG. 7, there is shown a screen
`700 in which the merchant is prompted to enter the information for the
`header and the footer. The screen 700 further illustrates the simplicity of
`the merchant interface.
`
`The third step is to select the default background, which may be a color
`or an image, and page style. The Development Tool simplifies the
`process of choosing by offering grids of selections. The color grid, or
`pallet, contains 16 different colors. This color pallet can be used or the
`merchant can define his own. Similarly, a grid of clip art images is
`available for the merchant to choose from for background images. These
`default conditions for each page constitute a template, and begin to
`illustrate the template-driven nature of the Development Tool. The
`default background may be separately changed by the merchant for any
`
`1 Unless noted, all citations in this chart are to U.S. Patent No. 6,330,575 by Victor S. Moore and Glen R. Walters (filed March 31, 1998, issued
`December 11, 2001). [DFNDT0000181-0000207]
`
`- 1 -
`
`- 2 -
`
`Comparison of U.S. Patent No. 6,629,135 and U.S. Patent No. 6,330,575 to Moore (“Moore ’575”)
`
`Comparison of U.S. Patent No. 6,629,135 and U.S. Patent No. 6,330,575 to Moore (“Moore ’575”)
`
`Claim
`No.
`
`Claim Language of U.S. Patent No. 6,629,135
`
`Relevant Disclosure in U.S. Patent No. 6,330,575 (“Moore ’575”)
`
`Claim
`No.
`
`Claim Language of U.S. Patent No. 6,629,135
`
`Relevant Disclosure in U.S. Patent No. 6,330,575 (“Moore ’575”)
`
`particular page.
`
`Page styles allocate certain portions of each page to text, images,
`multimedia, etc. The style thus provides a template for all of the
`different content-related objects ("style components") that will appear on
`a page. Although the position and sizes of the style components are
`defined by the style, they can be changed by the merchant for any page.
`Referring to FIG. 8, there is shown a screen 800 which prompts the
`merchant to select a background and a style for the page. Page styles are
`further elaborated in FIG. 9, and FIG. 10 shows one style or template in
`isolation.
`
`The fourth step is to fill in the content for each of the style components.
`As shown, for example, in FIG. 10, each of the style components must
`be filled in. To do this, the merchant clicks on the style component and
`the Development Tool presents a "dialog" box which steps the merchant
`through the choices necessary to fill in the style component. FIGS. 11-13
`show dialog boxes for image, text, and multimedia style components,
`respectively. For images, the merchant is presented with a selection, but
`may use other images as well. It is common for a merchant to scan logos
`and images that the merchant wants to use on his Web site. Any style
`component can also have a URL attached to it, and the dialog box allows
`the merchant to select this option.
`
`Each page created by the merchant can, as mentioned earlier, be
`modified. Style components can be added, deleted, moved, resized, etc.
`Another feature of the Development Tool is that it presents the page just
`as a Web customer will see it. This feature, called WYSIWYG for "what
`you see is what you get" allows the merchant to see, without publishing
`and browsing, what the published page will look like when it is
`published. Additionally, the Development Tool also provides a
`previewing option which uploads all of the pages and allows the
`merchant to view the entire Web site with a Web browser.
`
`8(b)
`
`providing the host website with a link for
`inclusion within a page on the host website for
`serving to a visitor computer, wherein the
`provided link correlates the host website with a
`selected commerce object; and
`
`When the pages are all created, the Development Tool allows the
`merchant to upload or publish the Web pages to a site specified by the
`merchant.
`
`Moore ’575, 10:59-11:64. See also Figs. 6-13.
`Briefly, in accordance with another aspect of the invention, a method for
`designing a Web page for use in a distributed electronic commerce
`system is provided. The commerce system comprises a Web page server
`and a second server which are electrically coupled to each other, and the
`Web page server hosts the Web page. The method comprises: creating a
`link to the second server; designing the Web page such that the link can
`be embedded into the Web page; and embedding the link into the Web
`page.
`
`8(c)
`
`upon receiving an activation of the provided link
`from the visitor computer, serving to the visitor
`computer an e commerce supported page with a
`look and feel corresponding to the captured look
`and feel description of the host website
`associated with the provided link and with
`content based on the commerce object associated
`with the provided link.
`
`Moore ’575, 3:23-39.
`The Web storefront 106 acts as the virtual store for the customer 114,
`and contains whatever information the merchant has built into the Web-
`site (e.g. pictures, prices, search engines, etc.). There is provided,
`according to the present invention, a Development Tool for designing
`the Web storefront 106. This tool greatly simplifies the task of creating
`the Web storefront initially and of modifying it and updating it. The
`Tool also ensures that the operation with the Transaction Server 202 is
`seamless for the customer 114.
`
`The Tool derives much of its utility from the fact that it contains a series
`of templates, tailored to different industries, for creating pages. The
`fields on these templates can be filled with text, or with images from clip
`art (also included with the tool) or can be tailored to suit a specific
`merchant's needs. The task is greatly simplified by the inclusion of a
`prompting mode in which the tool will actually step a user through the
`process. As an additional tailoring feature, the tool can be adapted to
`whatever "look and feel" the customer may desire. The customer may
`
`- 3 -
`
`- 4 -
`
`Page 4
`
`
`
`Comparison of U.S. Patent No. 6,629,135 and U.S. Patent No. 6,330,575 to Moore (“Moore ’575”)
`
`Comparison of U.S. Patent No. 6,629,135 and U.S. Patent No. 6,490,567 to Gregory (“Gregory ’567”)1
`
`Based upon the Court’s claim construction order [DI 309], the claim interpretations Plaintiff appears to be asserting and the alleged applications of
`those interpretations to one or more products of Defendants’ products in Plaintiff’s Amended Infringement Contentions served January 23, 2012, the
`U.S. Patent No. 6,490,567 to Gregory anticipates and/or renders obvious, alone or in combination with other prior art identified in Defendants’
`Amended Invalidity Contentions, the asserted claims as described in part below.
`
`Claim Language of U.S. Patent No. 6,629,135
`
`Relevant Disclosure in U.S. Patent No. 6,490,567 (“Gregory ’567”)
`
`Claim
`No.
`
`Claim Language of U.S. Patent No. 6,629,135
`
`Relevant Disclosure in U.S. Patent No. 6,330,575 (“Moore ’575”)
`
`want to match the look and feel to that of other applications that the
`customer uses, or may simply feel more comfortable with another look
`and feel.
`
`Moore ’575, 5:27-48.
`
`The customer, using a browser, goes to the Store Server and begins
`shopping, that is, browsing the content of the Web storefront 502. When
`the customer finds a product that the customer would like to buy, he
`selects that product 504. The Store Server then jumps to the Store
`Builder Server by using a Uniform Resource Locator ("URL") 506. The
`URL, called a price URL, contains all of the relevant information on the
`product, and all the information necessary to build a "Buy Page." The
`relevant product information includes a picture of the product, the
`product's price, and a description of the product.
`
`Moore ’575, 6:12-22.
`
`See also Figs. 6-16.
`
`Claim
`No.
`
`8
`
`An e commerce outsourcing process providing a
`host website in communication with a visitor
`computer with context sensitive, transparent e
`commerce support pages, comprising the steps
`of:
`
`8(a)
`
`8(b)
`
`capturing a look and feel description associated
`with a host website;
`providing the host website with a link for
`inclusion within a page on the host website for
`serving to a visitor computer, wherein the
`provided link correlates the host website with a
`selected commerce object; and
`
`Distributed electronic commerce is conducted over a network by
`substantially separating transaction functionality from merchant content.
`Electronic commerce transaction functionality is provided by a
`commerce server having a commerce database. The commerce server
`stores merchant and purchaser profile data and merchant content
`summaries on the commerce database. The purchaser browses and
`searches for product and merchant information using the commerce
`server, and is provided with more detailed information stored at a
`separate merchant content server system. The purchaser selects products
`to purchase, and a purchase order is sent to the commerce server. The
`commerce server initiates the settlement of accounts between the
`merchant and purchaser, and initiates order fulfillment for the selected
`product. The separation of transaction functionality and merchant
`content onto separate servers under the control of a commerce service
`provider and a merchant, respectively, provides a more efficient and
`effective way of carrying out electronic commerce over a network.
`
`Gregory ’567, Abstract.
`
`A purchaser requests the commerce server to send shopping information.
`The purchaser browses or searches for products on the commerce server,
`and data regarding products and merchants is retrieved from the
`commerce database. At the purchaser's request for more information on
`a product or merchant, the commerce server refers the purchaser to an
`appropriate merchant content server, which contains much more detailed
`
`- 5 -
`
`- 1 -
`
`1 Unless noted, all citations in this chart are to U.S. Patent No. 6,490,567 by James McKanna Gregory (filed January 15, 1997, issued December 3,
`2002). [DFNDT0000145-0000163]
`
`Comparison of U.S. Patent No. 6,629,135 and U.S. Patent No. 6,490,567 to Gregory (“Gregory ’567”)
`
`Comparison of U.S. Patent No. 6,629,135 and U.S. Patent No. 6,490,567 to Gregory (“Gregory ’567”)
`
`Claim
`No.
`
`Claim Language of U.S. Patent No. 6,629,135
`
`Relevant Disclosure in U.S. Patent No. 6,490,567 (“Gregory ’567”)
`
`Claim
`No.
`
`Claim Language of U.S. Patent No. 6,629,135
`
`Relevant Disclosure in U.S. Patent No. 6,490,567 (“Gregory ’567”)
`
`information about the product and merchant than is available from the
`commerce database.
`
`While browsing or searching the merchant content server, the purchaser
`may select one or more products for purchase. When the purchaser
`indicates he is ready to effectuate such a transaction, data concerning the
`selected product or products are sent to the commerce server. The data
`include information sufficient to identify the product, purchaser and
`selling merchant. The commerce server communicates with an external
`payment system to debit the purchaser's account and credit the
`merchant's account, effectuating the sale. The commerce server also
`generates a fulfillment message that ensures product delivery to the
`purchaser.
`
`Gregory ’567, 2:48-67.
`
`See also 13-14, infra.
`“The present invention thus advantageously provides a convenient and efficient
`way for a purchaser to shop over a network through simple and easy to
`understand interfaces. An embodiment of such an interface is shown in FIG.
`11.” Gregory ’567, 7:54-57.
`
`A purchaser may choose to view product and merchant information by
`predetermined category, such as home appliances 113, outdoor gear 114,
`or electronics 115. Alternatively, the purchaser may wish to carry out a
`search of the commerce database. Such a search may be boolean, e.g.,
`HIKING AND (BOOTS OR SHOES). In another embodiment, the
`search is in a natural language format as is known in the art, e.g., I
`NEED HIKING BOOTS FOR BACKPACKING.
`
`An embodiment of a screen responsive to such a natural language
`inquiry is shown in FIG. 12. Here, the response is shown according to
`the names of merchants 121, 122, 123 and 124 who sell hiking boots. In
`
`8(c)
`
`upon receiving an activation of the provided link
`from the visitor computer, serving to the visitor
`computer an e commerce supported page with a
`look and feel corresponding to the captured look
`and feel description of the host website
`associated with the provided link and with
`content based on the commerce object associated
`with the provided link.
`
`another embodiment, the response is shown in accordance with hiking
`boots products listed in the commerce database. In the embodiment
`shown in FIG. 12, tokens are displayed for each merchant indicating the
`types of payment accepted by the merchant 125 and the number of days
`in the merchant's money-back guarantee 126. This is merely meant to be
`exemplary of the types of information that could be supplied to the
`purchaser at this stage. Other types of information such as warranty
`information and service telephone numbers could also be included.
`
`Upon selecting a merchant from the screen shown in FIG. 12, the
`purchaser is referred by the commerce server to the content server on
`which the selected merchant has placed his merchant content. In one
`embodiment in which the present invention is implemented on the
`Internet, the URL of the merchant is contained in a table in the
`commerce database that cross-references it to the merchant identifier in
`the product data structure. In another embodiment, the network address
`of the content server is included in the product data structure as an
`additional field.
`
`Upon accessing the content server, the purchaser is presented with an
`electronic version of the merchant's store. Such stores are well known in
`the art as websites on the World Wide Web (WWW). The purchaser is
`able to search and browse among products offered by the merchant;
`learn detailed information regarding the merchant's return policy; learn
`about forms of payment accepted by the merchant; and order products.
`An example of a product screen at a content server is shown in FIG. 13.
`The picture of the boot 131 may be animated, and the boot could be
`slowly turned so all sides may be viewed. Audio accompanies the
`picture, describing the advantageous features of the boot. This is
`supplemented with textual information 132, as well as information about
`the boot's available sizes 133, weight 134, suggested retail price 135,
`offer price 136, and offer expiration date 137. If the purchaser wants to
`select the boot for purchase, the purchaser selects the Buy This button
`
`- 2 -
`
`- 3 -
`
`Page 5
`
`
`
`Comparison of U.S. Patent No. 6,629,135 and (cid:56)(cid:81)(cid:76)(cid:87)(cid:72)(cid:71)(cid:3)(cid:54)(cid:87)(cid:68)(cid:87)(cid:72)(cid:86)(cid:3)(cid:51)(cid:68)(cid:87)(cid:72)(cid:81)(cid:87)(cid:3)(cid:36)(cid:83)(cid:83)(cid:79)(cid:76)(cid:70)(cid:68)(cid:87)(cid:76)(cid:82)(cid:81)(cid:3)(cid:19)(cid:28)(cid:18)(cid:28)(cid:28)(cid:24)(cid:15)(cid:21)(cid:26)(cid:27)(cid:3)(cid:69)(cid:92)(cid:3)(cid:54)(cid:68)(cid:79)(cid:76)(cid:69)(cid:68)(cid:3)(cid:11)(cid:179)(cid:54)(cid:68)(cid:79)(cid:76)(cid:69)(cid:68)(cid:3)(cid:182)(cid:21)(cid:26)(cid:27)(cid:180)) combined with the
`(cid:39)(cid:76)(cid:74)(cid:76)(cid:87)(cid:68)(cid:79)(cid:3)(cid:53)(cid:76)(cid:89)(cid:72)(cid:85)(cid:3)(cid:54)(cid:72)(cid:70)(cid:88)(cid:85)(cid:72)(cid:3)(cid:54)(cid:68)(cid:79)(cid:72)(cid:86)(cid:3)(cid:54)(cid:92)(cid:86)(cid:87)(cid:72)(cid:80)(cid:3)(cid:11)(cid:179)(cid:39)(cid:76)(cid:74)(cid:76)(cid:87)(cid:68)(cid:79)(cid:3)(cid:53)(cid:76)(cid:89)(cid:72)(cid:85)(cid:3)(cid:54)(cid:54)(cid:54)(cid:180)(cid:12)
`
`(cid:37)(cid:68)(cid:86)(cid:72)(cid:71)(cid:3)(cid:88)(cid:83)(cid:82)(cid:81)(cid:3)(cid:87)(cid:75)(cid:72)(cid:3)(cid:38)(cid:82)(cid:88)(cid:85)(cid:87)(cid:182)(cid:86)(cid:3)(cid:70)(cid:79)(cid:68)(cid:76)(cid:80)(cid:3)(cid:70)(cid:82)(cid:81)(cid:86)(cid:87)(cid:85)(cid:88)(cid:70)(cid:87)(cid:76)(cid:82)(cid:81)(cid:3)(cid:82)(cid:85)(cid:71)(cid:72)(cid:85)(cid:3)(cid:62)(cid:39)(cid:44)(cid:3)(cid:22)(cid:19)(cid:28)(cid:64)(cid:15)(cid:3)(cid:87)(cid:75)(cid:72)(cid:3)(cid:70)(cid:79)(cid:68)(cid:76)(cid:80)(cid:3)(cid:76)(cid:81)(cid:87)(cid:72)(cid:85)(cid:83)(cid:85)(cid:72)(cid:87)(cid:68)(cid:87)(cid:76)(cid:82)(cid:81)(cid:86)(cid:3)(cid:51)(cid:79)(cid:68)(cid:76)(cid:81)(cid:87)(cid:76)(cid:73)(cid:73)(cid:3)(cid:68)(cid:83)(cid:83)(cid:72)(cid:68)(cid:85)(cid:86)(cid:3)(cid:87)(cid:82)(cid:3)(cid:69)(cid:72)(cid:3)(cid:68)(cid:86)(cid:86)(cid:72)(cid:85)(cid:87)(cid:76)(cid:81)(cid:74)(cid:3)(cid:68)(cid:81)(cid:71)(cid:3)(cid:87)(cid:75)(cid:72) alleged applications of
`(cid:87)(cid:75)(cid:82)(cid:86)(cid:72)(cid:3)(cid:76)(cid:81)(cid:87)(cid:72)(cid:85)(cid:83)(cid:85)(cid:72)(cid:87)(cid:68)(cid:87)(cid:76)(cid:82)(cid:81)(cid:86)(cid:3)(cid:87)(cid:82)(cid:3)(cid:82)(cid:81)(cid:72)(cid:3)(cid:82)(cid:85)(cid:3)(cid:80)(cid:82)(cid:85)(cid:72)(cid:3)(cid:83)(cid:85)(cid:82)(cid:71)(cid:88)(cid:70)(cid:87)(cid:86)(cid:3)(cid:82)(cid:73)(cid:3)(cid:39)(cid:72)(cid:73)(cid:72)(cid:81)(cid:71)(cid:68)(cid:81)(cid:87)(cid:86)(cid:182)(cid:3)(cid:83)(cid:85)(cid:82)(cid:71)(cid:88)(cid:70)(cid:87)(cid:86)(cid:3)(cid:76)(cid:81)(cid:3)(cid:51)(cid:79)(cid:68)(cid:76)(cid:81)(cid:87)(cid:76)(cid:73)(cid:73)(cid:182)(cid:86) Amended Infringement Contentions served January 23, 2012, the
`U.S. Patent Application 09/995,278 combined with Digital River SSS renders obvious the asserted claims as described in part below.
`
`There is motivation to combine Saliba (cid:182)(cid:21)(cid:26)(cid:27) and Digital River SSS because they are both related to e-commerce outsourcing processes for selling
`products over the Internet and thus are in the same field of endeavor. (cid:54)(cid:68)(cid:79)(cid:76)(cid:69)(cid:68)(cid:3)(cid:182)(cid:21)(cid:26)(cid:27)(cid:3)(cid:71)(cid:76)(cid:86)(cid:70)(cid:79)(cid:82)(cid:86)(cid:72)(cid:86)(cid:3)(cid:68)(cid:81)(cid:3)electronic financial system for providing financial
`services over the Internet has multiple billers, a service center, multiple financial institutions. See (cid:54)(cid:68)(cid:79)(cid:76)(cid:69)(cid:68)(cid:3)(cid:182)(cid:21)(cid:26)(cid:27)(cid:3)(cid:68)(cid:87)(cid:3)(cid:36)(cid:69)(cid:86)(cid:87)(cid:85)(cid:68)(cid:70)(cid:87)(cid:17)(cid:3)(cid:3)The Digital River Secure
`Sales System brought together manufacturers and dealers enabling them to sell and deliver products via the Internet through vendor websites. See
`Exhibit 9A. Both Saliba (cid:182)(cid:21)(cid:26)(cid:27) and Digital River SSS disclose electronic commerce systems that are directed to offering commerce objects over the
`Internet.
`
`
`Claim
`No.
`
`8
`
`8(a)
`
`8(b)
`
`8(c)
`
`
`
`
`
`
`Claim Language of U.S. Patent No. 6,629,135
`
`Relevant Disclosures
`
`See Ex. 9A, at 8.
`See Ex. 31A, at 8.
`
`See Ex. 9A, at 8(a).
`See Ex. 31A, at 8(a).
`See Ex. 9A, at 8(b).
`See Ex. 31A, at 8(b).
`
`See Ex. 9A, at 8(c).
`See Ex. 31A, at 8(c).
`
`An e commerce outsourcing process providing
`a host website in communication with a visitor
`computer with context sensitive, transparent e
`commerce support pages, comprising the steps
`of:
`capturing a look and feel description associated
`with a host website;
`providing the host website with a link for
`inclusion within a page on the host website for
`serving to a visitor computer, wherein the
`provided link correlates the host website with a
`selected commerce object; and
`upon receiving an activation of the provided
`link from the visitor computer, serving to the
`visitor computer an e commerce supported page
`with a look and feel corresponding to the
`captured look and feel description of the host
`website associated with the provided link and
`with content based on the commerce object
`associated with the provided link.
`
`- 1 -
`
`Comparison of U.S. Patent No. 6,629,135 and (cid:56)(cid:81)(cid:76)(cid:87)(cid:72)(cid:71)(cid:3)(cid:54)(cid:87)(cid:68)(cid:87)(cid:72)(cid:86)(cid:3)(cid:51)(cid:68)(cid:87)(cid:72)(cid:81)(cid:87)(cid:3)(cid:36)(cid:83)(cid:83)(cid:79)(cid:76)(cid:70)(cid:68)(cid:87)(cid:76)(cid:82)(cid:81)(cid:3)(cid:19)(cid:28)(cid:18)(cid:28)(cid:28)(cid:24)(cid:15)(cid:21)(cid:26)(cid:27)(cid:3)(cid:69)(cid:92)(cid:3)(cid:54)(cid:68)(cid:79)(cid:76)(cid:69)(cid:68)(cid:3)(cid:11)(cid:179)(cid:54)(cid:68)(cid:79)(cid:76)(cid:69)(cid:68)(cid:3)(cid:182)(cid:21)(cid:26)(cid:27)(cid:180)) combined with United
`States Patent Number (cid:25)(cid:15)(cid:22)(cid:22)(cid:19)(cid:15)(cid:24)(cid:26)(cid:24)(cid:3)(cid:87)(cid:82)(cid:3)(cid:48)(cid:82)(cid:82)(cid:85)(cid:72)(cid:3)(cid:11)(cid:179)(cid:48)(cid:82)(cid:82)(cid:85)(cid:72) (cid:182)(cid:24)(cid:26)(cid:24)(cid:180)(cid:12)
`
`(cid:37)(cid:68)(cid:86)(cid:72)(cid:71)(cid:3)(cid:88)(cid:83)(cid:82)(cid:81)(cid:3)(cid:87)(cid:75)(cid:72)(cid:3)(cid:38)(cid:82)(cid:88)(cid:85)(cid:87)(cid:182)(cid:86)(cid:3)(cid:70)(cid:79)(cid:68)(cid:76)(cid:80)(cid:3)(cid:70)(cid:82)(cid:81)(cid:86)(cid:87)(cid:85)(cid:88)(cid:70)(cid:87)(cid:76)(cid:82)(cid:81)(cid:3)(cid:82)(cid:85)(cid:71)(cid:72)(cid:85)(cid:3)(cid:62)(cid:39)(cid:44)(cid:3)(cid:22)(cid:19)(cid:28)(cid:64)(cid:15)(cid:3)(cid:87)(cid:75)(cid:72)(cid:3)(cid:70)(cid:79)(cid:68)(cid:76)(cid:80)(cid:3)(cid:76)(cid:81)(cid:87)(cid:72)(cid:85)(cid:83)(cid:85)(cid:72)(cid:87)(cid:68)(cid:87)(cid:76)(cid:82)(cid:81)(cid:86)(cid:3)(cid:51)(cid:79)(cid:68)(cid:76)(cid:81)(cid:87)(cid:76)(cid:73)(cid:73)(cid:3)(cid:68)(cid:83)(cid:83)(cid:72)(cid:68)(cid:85)(cid:86)(cid:3)(cid:87)(cid:82)(cid:3)(cid:69)(cid:72)(cid:3)(cid:68)(cid:86)(cid:86)(cid:72)(cid:85)(cid:87)(cid:76)(cid:81)(cid:74)(cid:3)(cid:68)(cid:81)(cid:71)(cid:3)(cid:87)(cid:75)(cid:72) alleged applications of
`(cid:87)(cid:75)(cid:82)(cid:86)(cid:72)(cid:3)(cid:76)(cid:81)(cid:87)(cid:72)(cid:85)(cid:83)(cid:85)(cid:72)(cid:87)(cid:68)(cid:87)(cid:76)(cid:82)(cid:81)(cid:86)(cid:3)(cid:87)(cid:82)(cid:3)(cid:82)(cid:81)(cid:72)(cid:3)(cid:82)(cid:85)(cid:3)(cid:80)(cid:82)(cid:85)(cid:72)(cid:3)(cid:83)(cid:85)(cid:82)(cid:71)(cid:88)(cid:70)(cid:87)(cid:86)(cid:3)(cid:82)(cid:73)(cid:3)(cid:39)(cid:72)(cid:73)(cid:72)(cid:81)(cid:71)(cid:68)(cid:81)(cid:87)(cid:86)(cid:182)(cid:3)(cid:83)(cid:85)(cid:82)(cid:71)(cid:88)(cid:70)(cid:87)(cid:86)(cid:3)(cid:76)(cid:81)(cid:3)(cid:51)(cid:79)(cid:68)(cid:76)(cid:81)(cid:87)(