throbber
UNITED STATES PATENT AND TRADE孔1AR玉OFFICE
`
`BEFORE THE P ATENT TRIAL AND APPEAL BOARD
`
`GOOGLEINC.
`Petitioner
`
`v.
`
`AT HOME BONDHOLDERS' LIQUIDATING TRUST
`Patent Owner
`
`Case IPR No. Unassigned
`U.S. Patent 6,286,045
`
`Petition for Inter Partes Review ofU.S. Patent No. 6,286,045 UNDER 35
`U.S.c. ~~ 311・319and 37 C.F.R. ~~ 42.1・.80,42.100-.123
`
`Mail Stop "PATENT BOARD"
`Patent Trial and Appeal Board
`U.S. Patent and Trademark Office
`P.O. Box 1450
`Alexandria, VA 22313-1450
`
`

`
`Pα!ge i
`
`Inter Partes Review of
`U.S. Patent No. 6ラ286,045
`
`T ABLE OF CONTENTS
`
`INTRODUCTION… … ...・ H ・...........・ H ・..…...・H ・..……...・H ・.....・ H ・......・H ・....・ H ・H ・H ・.1
`1.
`II. GROUNDS FOR STANDING (37 C.F.R. S 42.104(a)); PROCEDURAL
`STATEMENTS...・H ・..…...・ H ・..…...・ H ・.....・ H ・.....・ H ・..…...・ H ・..…...・ H ・.....・ H ・.....・ H ・....1
`
`II1. STATEMENT OF THE PRECISE RELIEF REQTA STED AND THE
`REASONS THEREFOR (37 C.F.R. S 42.22(a))……...・ H ・.....・ H ・.....・ H ・..…...・ H ・.2
`IV. OVERVIEW………...・ H ・.....・ H ・..… ...・H ・..…...・ H ・..…...・ H ・-・… … .,.・ H ・.....・H ・..………… 2
`
`A. The '045 Patent ...・ H ・.....・ H ・.....・ H ・.....・ H ・H ・H ・..…'"・ H ・.....・ H ・.....・ H ・.....・ H ・..… .2
`
`B. Prosecution History …・ ..........................................................................3
`
`C. State ofthe A目......................................................................................4
`
`1. Serving and Counting ofBanners was Well-Known.....・H ・........4
`
`2. Serving and Counting Banners without Significantly
`Increasing Network Traffic was Well-Known....・H ・...・ H ・-… H ・H ・..7
`
`3. Advertisement Targeting based on Demographics was
`W ell-Known ...・ H ・.....・ H ・H ・H ・..…...・ H ・.....・ H ・.....・ H ・.....・ H ・.....・ H ・.....・ H ・8
`
`4. Fault Tolerance and Reliability Were Well-Known....・H ・H ・H ・-… 9
`
`5. HTTP Redirect was Well-Known … H ・H ・-…....・ H ・-… H ・H ・.....・ H ・-… 10
`
`V. CLAIM CONSTRUCTION...…・ H ・H ・.....・ H ・..…...・ H ・.....・ H ・.....・ H ・.....・ H ・.....・ H ・....11
`
`A. "Banner"…'"・ H ・.....・ H ・..…...・ H ・.....・ H ・H ・H ・.....・ H ・.....・ H ・..… ...・ H ・..…...・ H ・..… 12
`
`B. "Content General Request Signal"…...・ H ・.....・ H ・H ・H ・.....・ H ・.....・ H ・.....・ H ・.12
`
`C. "Content Specific Request Signal" '"・ H ・..…...・ H ・..………...・ H ・.....・ H ・H ・H ・.14
`V1. PERSON OF SKILL IN THE ART & STATE OF TI王EART… H ・H ・-… H ・H ・.15
`VI1. IDENTIFICATION OF PRIOR ART AND CHALLENGE (37 C.F.R. S
`42.1 04(b ))...................................................................................................... 15
`
`A. Prior art.…….い…….日…….日…….い…….日……..…….口…….リ…….日…….日…….口…….日…….日…….日…….口……..…….一……..…….υ…….υ…….υ…….. …….日…….口…….日…….日…….口…….日…….日……..…….日…….日…….口…….口…….υ……..…….日…….日…….日…….口…….日…….口…….日…….日…….日…….日…….υ…….日…….日…….口…….日……..…….υ…….日…….口…….υ…….口……"…….一…….口…….日…….口…….日…….日…….日…….日…….日…….口…….日…….日…….日…….日…….日…….日…….川……..…….日…….口…….日…….日…….日…….日…….日…….口…….日…….日…….日…….日…….日…….日…….υ…….口….日.1行5
`B. Challenge.….リ..….日..….日.,….口..…...….日..い….リ..….口..….日..….口..….日..….一..….口..….口..….日..…...….一..…...….日..…...….い..….日..….日..….υ..….日..….日..口….口..….日..口….日..….リ...16
`1. Ground 1上:Claims 49, 51ト-づ53ラ 55-づ58,64-67,and 70-71
`would have been obvious over Angles in view of
`孔M化er打rimanand further in view ofHTTP1.0.…….日….日.……..…….日…….口……..…….日…….日…….υ…….υ…….日…….日…….日…….日…….日…….日…….日…….υ……..…….υ……..…….日…….日…….日…….い…….日….日.17
`
`

`
`Pαge ii
`
`lnter Partes Review of
`U.S. Patent No. 6,286,045
`
`2.
`
`Ground 2: Claims 50 and 69 would have been obvious
`over Angles in view ofMerriman and HTTPl.O and
`further in view of Davis ........................................................... 35
`
`3. Ground 3: Claims 49-53 and 55-57 would have been
`obvious over Wexler in view ofHTTP1.0...・H ・...・ H ・...t・H ・...・ H ・..36
`
`4. Ground 4: Claims 58, 64-67, and 69-71 would have
`been obvious over -Wexler in view ofHTTP1.0 and
`further in view of Meeker ........................................................ 45
`
`VIII. CONCLUSION ...・ H ・.....・ H ・.....・ H ・.....・ H ・H ・H ・.....・ H ・H ・H ・.....・ H ・.....・ H ・H ・H ・..…...・ H ・..50
`IX. MANDATORY NOTICES (37 C.F.R. S 42.8(a)(l))….....・ H ・-…....・ H ・t...・H ・...50
`
`•
`-1
`
`
`

`
`Pαge 1
`
`1. INTRODUCTION
`
`Inter Pαrtes Review of
`U.S. Patent No. 6,286,045
`
`Google Inc. ("Petitioner") petitions for Inter Pαrtes Review, seeking
`
`cancellation of claims 49-53, 55-58, 64-67, and 69-71 ("challenged claims") of
`
`U.S. Patent No. 6,286,045 to Griffiths et al. ("the '045 patent") (GOOO 1001),
`
`which is owned by At Home Bondholders' Liquidating Trust ("Patent Owner").
`
`11. GROUNDS FOR STANDING (37 C.F.R. ~ 42.104(a)); PROCEDURAL
`STATEMENTS
`
`Petitioner certifies that the '045 patent is available for IPR. Petitioner further
`
`certifies that it is not barred or estopped from requesting IPR of claims 49-53, 55-
`
`58, 64-67, and 69-71 on the grounds identified in this petition, as Petitioner was
`
`自rstserved less than a year ago with a complaint for infringement on Feb. 20,
`
`2014, in U.S. District Court for the District ofDelaware (1 :14-cv-00216)1. (0000
`
`1015.) Concurrently filed herewith are Powers of Attomey and an Exhibit List per
`
`S 42.1 O(b) and S 42.63( e), respectively. The required fee is paid via online credit
`
`card payment. The Office is authorized to charge fee deficiencies and credit
`
`overpayments to Deposit Acct. No. 19-0036 (Customer ID No. 45324).
`
`1 Petitioner notes that it was also served with a complaint based on the '045 patent
`
`on Feb. 10,2014. However, that complaint was dismissed without prejudice, and is
`
`therefore not relevant to the IPR bar date. (IPR2012-00004, Paper No. 18.)
`
`

`
`Pαge2
`
`Inter Pαrtes Review of
`U.S. Patent No. 6,286,045
`
`111. STATEMENT OF THE PRECISE RELIEF REQUESTED AND THE
`REASONS THEREFOR (37 C.F.R. ~ 42.22(a))
`
`Petitioner requests IPR and cancellation of claims 1-12, 14-19, 34・-38,and
`
`40-42 of the '045 patent. A detailed statement of the reasons for the relief requested
`
`is set forth in SS IV and VII below.
`
`IV. OVERVIE W
`
`Inter partes review ("IPR") was created to improve patent quality and, if
`
`warranted, cancel unpatentable claims. That core purpose is furthered by this
`
`Petition, as the challenged claims of the '045 patent should never have been issued.
`
`Not only was the alleged invention known before the '045 patent filing date, but the
`
`four "fundamental principles" of the alleged invention -touted by the Patent
`
`Owner during prosecution as distinguishing the invention from the art -were also
`
`well-understood by the industry. Because Petitioner is, at a minimum, reasonably
`
`likely to prevail in showing unpatentability, the Petition should be granted and trial
`
`instituted on all of the challenged claims as set forth below.
`
`A. The '045 Patent
`
`The '045 patent was filed on May 19, 1997, and issued on September 4,
`
`2001. According to USPTO assignment recordation records, At Home
`
`Bondholders' Liquidating Trust is now the Patent Owner.
`
`The '045 patent claims nothing more than a well-known method of Intemet
`
`advertising and the ability to accurately account for the number of times an
`
`

`
`Pαge3
`
`Inter Pαrtes Review of
`U.S. Patent No. 6,286,045
`
`advertisement is displayed to a user, while reducing heavy Intemet traffic. In
`
`general, the '045 patent's claims describe distributing a banner advertisement over a
`
`network. This involves generating a request for an ad banner from a user's
`
`computer. Rather than sending the request directly to an advertiser's web site, the
`
`request is sent to another server that counts the request and redirects the request to
`
`the desired advertiser's web site. The redirected address is sent to the user's
`
`computer and a request from the user's computer is then sent to the selected
`
`advertising web site.
`
`B. Prosecution History
`
`In arguments made during prosecution, Patent Owner emphasized four
`
`"fundamental principles" ofthe alleged invention that the Examiner was to keep in
`
`mind when analyzing the prior art. (GOOG 1002, p. 149.) First, "Applicants'
`
`invention reduces the inaccurate display counting caused by caching of the banners
`
`by making or causing request signals generated or transmitted by a client device
`
`unblockable by the client device or proxy server, even though the banners may
`
`have been previously stored on the client device or proxy server." (Id., p. 150.)
`
`"Second, applicants' invention allows such serving and counting to occur without
`
`significantly increasing data traffic on the computer network or unnecessarily
`
`delaying the display of the banners or other information on the client device." (Id.,
`
`p. 151.) "Third, applicants' invention allows banners or advertisements to be
`
`

`
`Pαge4
`
`Inter Partes Review of
`U.S. Patent No. 6,286,045
`
`targeted to users to increase the banners' or advertisements' effectiveness." (!d.)
`
`"F ourth, applicants' invention increases fault tolerance and reliability for
`
`information and banner deliv町 andstorage systems." (Id.) Such arguments were
`
`apparently persuasive to the Examiner in overcoming the cited prior art. Yet each
`
`ofthese "fundamental principles," along with the mechanisms described in the '045
`
`patent as embodying those principles, were well known in the industry before the
`
`'045 patent was filed.
`
`C. State of the Art
`
`1. Serving and Counting of Banners was Well明 Known
`
`Paul Leach was an early member of the HTTP W orking Group of the W orld
`
`Wide Web Consortium and, in the mid-1990s, was heavily involved in developing
`
`the protocols by which Web traffic was govemed.2 (GOOG 1005,市 8.)In his
`
`declaration, Mr. Leach explains that "[t]he concept and concem for accurately
`
`counting the number of times a banner was displayed on a client device was a well
`
`known issue at the time of the filing of the '045 patent." (GOOG 1005,市 20.)Mr.
`
`Leach has also explained that "[i]t was also well known that the use of cache would
`
`cause an underreporting of the counting of banners. ... 'A request is a connection to
`
`2 Mr. Leach was a contributor to both the HTTP 1.0 and HTTP 1.1 specifications.
`
`(GOOG 1008, pp. 41-42; GOOG 1026, pp. 99・100.)
`
`

`
`Pαge5
`
`Inter Pαrtes Review of
`U.S. Patent No. 6,286,045
`
`an Intemet site (i.e., hit) that successfully retrieves content,' but counting such
`
`requests accurately was a known issue 'because browser software and many
`
`Internet gateways intercept some requests before reaching the server, and these
`
`cached requests are never logged.'" (0000 1005, ~ 21 (quoting 0000 1022, p.
`
`13).)
`
`Not only was the problem a known issue, but Patent Owner's solution was
`
`also known. Specifically, cache avoidance to reliably determine page views -also
`
`known as "cache-busting" -was well known by early 1997. As Mr. Leach stated in
`
`his co-authored HTTP Working Oroup paper, "[司ora variety of reasons, content
`
`providers want to be able to collect information on the frequency with which their
`
`content is accessed. This desire leads to some of the 'cache-busting' done by
`
`existing servers. ('Cache-busting' is the use by servers of techniques intended to
`
`prevent caching ofresponses...)" (0000 1024, pp. 2-3.) Further, as discussed in
`
`an earlier version ofthe same Working Oroup paper, "[s]ome cache-busting is also
`
`done to provide different advertising images to appear on the same page (i. e., each
`
`retrieval of the page sees a different ad).. ..HTTP/l.l already allows origin servers
`
`to prevent caching of responses, and we have evidence that at least some of the
`
`time, this is being done for the sole purpose of collecting counts of the number
`
`

`
`Pαge6
`
`lnter Partes Review of
`U.S. Patent No. 6,286,045
`
`ofaccesses ofspecific pages.,,3 (GOOG 1016, pp. 2-3.)
`
`Peter Kent is another expert in the field, having been involved in Intemet
`
`advertising企omthe early days of the Web. (GOOG 1003,柄 5-8.) Mr. Kent
`
`agrees that:
`
`[c]ounting accuracy for delivered content was a widely known issue剖
`
`the time the '045 patent was filed, and the proposed solution in the
`
`'045 patent was also already widely known. In fact, attempting to
`
`improve counting accuracy via cache avoidance was such a burden on
`
`the Web's bandwidth that by early 1997, other proposals were already
`
`being made to move advertisers away from the use of cache-
`
`avoidance. At any rate, such cache avoidance was already widely
`
`known before the alleged invention. (GOOG 1003,司15.)
`
`Further, the cache avoidance methods described in the '045 patent
`
`specification ("HTTP no-cache pragma, appending a random segment to the URL,
`
`and using a cgi script to generate dynamic pages") were already known before the
`
`patent's filing date. (GOOG 1003,司16.)Mr. Kent also describes additional known
`
`cache avoidance methods, including modifシingURLs and the use of third party
`
`products such as PageMeter. (GOOG 1003, ,-r17.)
`
`Thus, it was well-known by a person of ordinary skill in the art ("POSA")
`
`when the '045 patent was filed "that caching distorted the accurate counting of the
`
`3 Emphasis added throughout unless otherwise noted.
`
`

`
`Pαge 7
`
`Inter Pαrtes Review of
`U.S. Patent No. 6,286,045
`
`display of advertising banners and web pages and that there were known 'cache-
`
`busting' methods that could be used to prevent caching and thus allow for a more
`
`accurate method of counting the delivery and display of Intemet based
`
`advertisements." (GOOG 1005,市 27.)
`
`2. Serving and Counting Banners without Significantly
`Increasing Network Traffic was Well-Known
`
`While cache-busting allowed for a more accurate counting ofbanners, it was
`
`recognized in the industry at the time that cache-busting "also resulted in increased
`
`loads on servers." (GOOG 1005,市 28.)"Not only was this method expensive
`
`computational1y to the sever, but it defeated intermediary caching and did not
`
`correctly handle the exchanging of URLs between people." (GOOG 1005,需28,
`
`GOOG 1023, p. 2.) So, methodologies to allow for the serving and counting of
`
`banner advertisements without significantly increasing data traffic through the use
`
`of cache田 bustingwere also "well known at the time of the filing of the '045 patent
`
`application." (GOOG 1005, ,-r29.)
`
`Mr. Leach declares that "[o]ne of ordinary skill in the art at the time of the
`
`filing of the '045 patent would have known that cache control mechanisms such as
`
`If-Modified-Since or If-NoneMatch headers would result in not blocking the
`
`request signal企omreaching the intended server, but avoiding a refetch of the
`
`requested information ifthat information existed in cache." (GOOG 1005,市32,see
`
`

`
`Pαge8
`
`αIso GOOG 1 005, ~~33 ・34.)
`
`Inter Partes Review of
`U.S. Patent No. 6,286,045
`
`Mr. Leach's declaration also discusses a "hit-metering" approach that he and
`
`Jeffrey Mogul developed. That approach "outlines a method of counting requests,
`
`or 'hit counts' without defeating the use of cache where appropriate." (GOOG 1005,
`
`市 35.) As Mr. Leach puts it, "[o]ur hit-metering approach allowed content
`
`providers to be able to collect information on the frequency with which their
`
`content is accessed, but without resorting to 'cache七usting'techniques discussed
`
`above that defeat the use of cache." (1d.; seeαIso, GOOG 1024.)
`
`Thus, "it was well known by a POSA at the time of the filing of the '045
`
`patent that multiple methods existed that would allow for the accurate counting of
`
`banner advertisement requests without significantly increasing data traffic and that
`
`also allows for the efficient use of cache." (GOOG 1005,市36.)
`
`3. Advertisement Targeting based on Demographics was Well-
`Known
`
`Mr. Leach explains that "[t]he concept of targeting advertisements to
`
`particular users to increase advertising effectiveness was a well known issue at the
`
`time of the filing of the '045 patent." (GOOG 1005,市37.)As discussed in Mr.
`
`Leach's Hit-Metering paper, "some advertisers employed the use of 'cache-busting'
`
`to 'col1ect demographic information' so that advertising images could be tailored
`
`and targeted to those demographics, e.g., 'each retrieval of the page sees a different
`
`

`
`Pαge9
`
`lnter p,αrtes Review of
`U.S. Patent No. 6,286,045
`
`ad.'" (GOOG 1005,司 37(quoting GOOG 1024, p. 3).)
`
`And Mary Meeker, in her detailed analysis of Intemet advertising in early
`
`1997, noted, "the Intemet offers the ability to target and deliver messages to an
`
`audience with specific demographics and interests." (GOOG 1010, p. 3・13.)
`
`"Targeting gives advertisers the opportunity to filter messages to
`
`selected audiences based on certain criteria. This may be the most
`
`powerful aspect of the Intemet as an advertising medium - the
`
`ability to dictate the exact composition of an advertisement's
`
`audience.. .each individual delivery can be tailored, based on user
`
`information. The power of the second aspect is increased substantially
`
`with more detailed user data, potentially collected through regis甘ation
`
`or in the course ofusing the site." (GOOG 1010, p. 6-3.)
`
`Thus, "it was well-known by a POSA at the time of the filing of the '045
`
`patent that advertisers were developing methods using demographics to increase
`
`advertising effectiveness." (GOOG 1005,司 39.)
`
`4. Fault Tolerance and Reliability Were Well-Known
`
`Based on Mr. Leach's extensive experience in "ACM conferences and
`
`committees directed to distributed computing, replication and fault tolerance as
`
`early as 1985" and his "published papers on the theories and principles of
`
`distributed computing in 1982, 1985 and 1987," he explains that the "concept of
`
`fault tolerant computing for increased reliability was a well-known concept at the
`
`time of the filing of the '045 patent."(GOOG 1005,市40ふ Indeed,“[m]irroring
`
`

`
`Pαrge 10
`
`Inter Partes Review of
`U.S. Patent No. 6,286,045
`
`and redundancy were common fault tolerant methods at the time." (Id.) Thus, a
`
`POSA at the time of the '045 patent would have understood "that fault tolerant
`
`solutions in distributed computing existed and provided increased reliability in
`
`computer delivery and storage systems." (GOOG 1005,市 41.)
`
`5. HTTP Redirect was Well-Known
`
`Mr. Kent explains that "HTTP redirect was also widely employed in the
`
`field of information delivery (inc1uding delivery of online advertisements)," and
`
`points to prior art inc1uding "Wexler [that] describes a third party accounting and
`
`statistical service 'configured to issue a '302' redirect response when a specific
`
`URL is requested.'" (GOOG 1003,司 18(quoting GOOG 1007, 5:16-17).) Mr. Kent
`
`further notes that "Merriman describes an advertisement server for 'send[ing] the
`
`redirect message causing the user's browser to receive the URL for the advertiser's
`
`web site based upon data stored in the server.'" (GOOG 1003,明 18(quoting GOOG
`
`1013,7:22-26).)
`
`Indeed, Mr. Kent explains that "[0 ]ne well-known use of HTTP redirect
`
`messages was to refer a c1ient computer to a server located in the c10se
`
`geographical proximity of the c1ient for reducing latency... .HTTP redirect
`
`messages [were] to refer the client computer to a selected server in a group of
`
`distributed servers," because "a group of web servers can reduce latency because a
`
`distributed web server group can balance the load and dispatch the request to the
`
`

`
`Pαrge 11
`
`Inter Pαrtes Review of
`U.S. Patent No. 6,286,045
`
`least loaded web server." (GOOG 1003,明 19.)
`
`A POSA, considering the '045 patent's claims in light of the prior art, would
`
`have understood that the prior art rendered the claims unpatentable. The prior art
`
`references are discussed in detail below in Sec. V1I. Each applied reference is
`
`analogous art to the claimed invention at least because it (1) falls within the '045
`
`patent's stated field of "storage, management, and delivery of information on a
`
`computer network" (GOOG 1001, 1 :9-11), and/or (2) is reasonably pertinent to one
`
`ofthe apparent problems allegedly solved.
`
`As such, the challenged claims are well known and should not have been
`
`issued. 1nstead they should be cancelled. 1n view of the showings of obviousness
`
`provided below, Petitioner is reasonably likely to prevail in establishing that each
`
`of claims 49-53, 55-58, 64-67, and 69・71ofthe '045 patent is unpatentable.
`
`v. CLAIM CONSTRUCTION
`
`1n accordance with 37 C.F.R. S 42.100(b), the challenged claims must be
`
`given their broadest reasonable interpretations ("BRI") in light of the specification
`
`of the '045 patent. The following terms and phrases from the claims of the '045
`
`patent require construction in accordance with these principles for the pu中 oseof
`
`this 1PR. The plain and ordinary meaning should be applied to any claim terms that
`
`are not addressed below. Petitioner reserves the right to pursue different
`
`constructions under different standards applicable in other forums.
`
`

`
`Pαrge 12
`
`A. "Banner"
`
`Inter Pαrtes Review of
`U.S. Patent No. 6,286,045
`
`Claims 49, 53, 58, 64, 79, and 71 recite a "banner." Patent Owner has acted
`
`as its own lexicographer and makes it clear that this term is to be construed "very
`
`broadly." Specifically, the '045 patent specification states:
`
`For purposes of the present invention, the term守banner'is meant to
`
`be construed veηr broadly and includes any information displayed in
`
`conjunction with a web page wherein the information is not part ofthe
`
`same file as the web page. That is, a banner includes anything that is
`
`displayed or used in conjunction with a web page, but which can exist
`
`separately from the web page or which can be used in conjunction
`
`with many web pages. Banners can include graphics, textual
`
`information, video, audio, animation, and links to other computer
`
`sites, web sites, web pages, or banners. (GOOG 1001,2:28-37.)
`
`Under BRl, and given the explicit definition in the specification, a POSA
`
`would have understood the term "banner" to mean吋nformationdisplayed in
`
`conjunction with a web page wherein the infonnation is not part of the same file as
`
`the web page." This would include one or more of graphics, textual information,
`
`video, audio, animation, and links to other computer sites, web sites, web pages, or
`
`banners. (GOOG 1003,可 39.)
`
`B. "Content General Request Signal"
`
`Claim 51 recites a "content general request signal." The '045 patent
`
`specification states:
`
`

`
`Pαge 13
`
`Inter Partes Review of
`u.s. Patent No. 6,286,045
`
`In other words, the initial banner request signal generated by terminal
`
`36 during the step 112 can be a content general signal and may
`
`contain only the minimum amount of information needed to tell a
`
`designated computer site, information server, or other device which
`
`receives the initial banner request signal and on which a banner may
`
`or may not be stored or located, only that the terminal 36 desires that
`
`an unspecified banner be served to the terminal. (GOOG 1001, 15:8-
`
`16.)
`
`Further, "[i]fthe optional selection step 113 is used with the method 110, the
`
`terminal 36 will only request during step 112 that a banner be served to the
`
`termina136, but the terminal 36 will not speci命 whichbanner is to be served to the
`
`termina136." (GOOG 1001, 15:25-29.)
`
`The '045 patent specification additional1y states:
`
`A general content URL address for a banner does not provide the
`
`necessary information to determine which banner is to be displayed.
`
`Rather a general content URL address for a banner only indicates that
`
`a banner is to be displayed and the receiver of the signal generated by
`
`the terminal 36 during the step 112 can decide which banner is to be
`
`displayed during the selection step 113. A general content URL
`
`address for a banner could be of the form
`
`http://羽 川 市 .bannersite 1.com/image; spacedesc=contentsitename.
`
`(GOOG 1001,16:50-58.)
`
`Further, "[t]he space descriptor field in the general content URL address can
`
`

`
`Pαrge 14
`
`Inter Pαrtes Review of
`U.S. Patent No. 6,286,045
`
`reference different groups of banners such as, for example, a collection of car
`
`advertisements, a collection of detergent advertisements, etc., depending on the
`
`web page providing the general content URL address." (0000 1001, 17:3-8.)
`
`Accordingly, the content general request signal can still contain general
`
`information regarding a type of content or user interest, as long as a specific banner
`
`is not identified.
`
`Under BRI, a POSA would therefore have understood the term "content
`
`general request signal" to mean "a request indicating that information is to be
`
`displayed and that the receiver can decide what information is to be displayed."
`
`(0000 1003, para 46.)
`
`C. "Content Specific Request Signal"
`
`Claim 52 recites a "content specific request signal." The '045 patent
`
`specification states: "If the optional selection step 113 is not used with the method
`
`110, the terminal 36 will request during the step 112 that a specific banner to be
`
`served to the termina136." (0000 1001, 15:23-25.) Additionally:
`
`In order to speed up the process of downloading, transmitting, or
`
`serving a specific banner from an information server to the terminal
`
`56, the content specific URL address of the requested or selected
`
`banner sent to the terminal during step 114 can contain the exact
`
`Intemet Protocol (IP) address of the requested or selected banner. For
`
`example, instead of providing the specific content URL address for
`
`

`
`Pαge 15
`
`Inter Partes Review of
`U.S. Patent No. 6,286,045
`
`the banner 62 as http://www.bannersitel.com/bannerl.gif. the specific
`
`content URL address for the banner 62 could be provided as, for
`
`example, httゆp://236.4“5.78.190/沿banner叶.1.gif,thereby removing a佃ny
`
`need tωo us臼e the Domain Name System (DNS) to convert the
`
`alphanumeric address
`
`S印erve位rtωoits exact IP address. (GOOG 1001, 18:62-19:8.)
`
`Under BRI, a POSA would have understood the term "content specific
`
`request signal" to mean "a request containing a content specific URL address with
`
`the location ofthe information." (GOOG 1003,市 49.)
`
`VI. PERSON OF SKILL IN THE ART & STATE OF THE ART
`
`A POSA is presumed to be aware of all pertinent art, thinks along
`
`conventional wisdom in the art, and is a person of ordinary creativity. With respect
`
`to the '045 patent, a POSA would typically have at least (a) a Bachelor of Science
`
`degree in computer science and/or a similar field or (b) at least 3 years of
`
`experience in web-based information management and delivery systems. (GOOG
`
`1003,有明 13・14;GOOG 1005,有司 12-13.)
`
`VII. IDENTIFICATION OF PRIOR ART AND CHALLENGE (37 C.F.R. ~
`42.104(b))
`
`A. Prior art
`
`(1) U.S. Patent No. 5,933,811 to Angles et al. was filed Aug. 20, 1996, and
`
`issued Aug. 3, 1999. Titled, "System and Method for Delivering Customized
`
`Advertisements Within Interactive Communication Systems," Angles is prior art
`
`

`
`Pαge 16
`
`under 35 U.S.C. 102(e)4.
`
`lnter Partes Review of
`U.S. Patent No. 6,286,045
`
`(2) U.S. Patent No. 5,948,061 to Merriman et al. was filed Oct. 29, 1996,
`
`and issued Sept. 7, 1999. Titled "Method of Delivery, Targeting, and Measuring
`
`Advertising Over N etworks, "恥1errimanis prior art under 35 U.S.C. 102(e).
`
`(3) U.S. Patent No. 5,960,409 to Wexler was filed Oct. 11, 1996, and issued
`
`Sept. 28, 1999. Titled "Third-Party On-Line Accounting System and Method
`
`Therefor," Wexler is prior art under 35 U.S.C. 102(e).
`
`(4) Fielding et al., "HTTP W orking Group Internet Draft Hypertext Transfer
`
`Protocol -HTTP/l.O," ("HTTPl.O") was published Feb. 20, 1996. HTTPl.O is
`
`prior art under 35 U.S.C. 1 02(b).
`
`(5) Meeker, Mary, "Technology: Intemet!New Media The Intemet
`
`Advertising Report" was published by Morgan Stanley, U.S. Investment Research
`
`in January 1997. Meeker is prior art under 102(a).
`
`(6) U.S. Patent No. 5,796,952 to Davis et al. was filed Mar. 21, 1997, and
`
`issued Aug. 18, 1998. Titled, "Method and Apparatus for Tracking Client
`
`Interaction with a Network Resource and Creating Client Profiles and Resource
`
`Database," Davis is prior art under 35 U.S.C. 102(e).
`
`B. ChaIlenge
`
`4 All references to Title 35 ofthe U.S. Code are to the pre回 AIAversion.
`
`

`
`Pαge 17
`
`Inter Pαrtes Review of
`U.S. Patent No. 6,286,045
`
`IPR is requested for claims 49-53, 55・58,64-67, and 69・71on the grounds
`
`for unpatentability listed in the index below. Per 37 C.F.R. ~ 42.6(d), copies ofthe
`
`references are filed herewith. In support of the proposed grounds, this Petition is
`
`accompanied by a declaration of a technical expert, Mr. Peter Kent (GOOG 1003),
`
`which explains what the art would have conveyed to a POSA.
`
`Ground
`
`35 USC
`
`Index of Reference( s)
`
`Claims
`
`~ 103(a) Angles,孔1erriman,HTTP 1.0
`
`2
`
`3
`
`~ 103(a) Angles, Merriman, HTTP1.0, Davis
`~ 103(a) Wexler, HTTP1.0
`
`4
`
`~ 103(a) Wexler, HTTP1.0, Meeker
`
`49, 51-53, 55-
`58,64-67,
`and 70-71
`
`50 and 69
`
`49-53 and 55-
`57
`
`58,64-67,
`and 69-71
`
`1. Ground 1: Claims 49, 51-53, 55-58, 64・67,and 70-71 would
`have been obvious over Angles in view of Merriman and
`further in view of HTTPl.O
`
`αr) Independent Claim 49
`
`Claim 49 does no more than add a few limitations to a conventional method
`
`of delivering a "banner" referenced in "a document served to a device" (e.g., a web
`
`page). The added limitations include a non-cache-blockable "first banner request
`
`signal" and a redirecting "banner location signal" providing an address of the
`
`second portion of information. These added limitations themselves were also well
`
`

`
`Pαge 18
`
`Inter Partes Review of
`U.S. Patent No. 6,286,045
`
`known in the art well before the '045 patent's filing date.
`
`FIG. 4 of Angles (annotated below) illustrates the requesting and ultimate
`
`delivery of a customized advertisement to a consumer computer.
`
`First server
`
`|D… |
`
`d T A M
`E 陪 e d
`mEmvn-
`h M m ・叫
`
`,<\ -CON$V\1CR .Rf.CJ宰iRATh)N
`(SEE 引G. 5)
`8 申 CONTENTPRO'VJOER
`REC!ST民ATlON (St:E 利G. o)
`C 品 CONSlIMERAGCESSES
`j
`CON TENT PROVl.DER
`!
`i
`(SE.ξflC 7)
`1) -ELECTRONiC PAGE SSNT !
`τo CONSUMER
`j
`($EE nc. 7)
`E -C0NSUMER MEMSE'R COOE /
`SENT TO ADVERTlS[MENT,I
`PROVIOER (SEE flG. 7i .'
`f -CUSTOMIZEO AI)VERnSE.MtNT
`SENT TO C<)NSl)MER !
`{吉Et:no. 7)
`,1
`,;:-;c 4 l
`
`F
`
`Ba.nner
`location Si!rnal
`
`Angles' "Summary ofthe Invention" describes Angles' general process flow:
`
`"[T]he invention is directed to delivering custom advertisements to
`
`consumers who use their computers to view information offered by
`
`different content providers existing on the Intemet. Preferably, when a
`
`consumer accesses a content provider, the content provider transmits
`
`an electronic document to the consumer. Embedded within the
`
`

`
`Pαge 19
`
`Inter Partes Review of
`U.S. Patent No. 6,286,045
`
`electronic document is a[ n] advertisement request. When the
`
`consumer's computer displays the electronic document, the embedded
`
`advertisement request directs the consumer computer to communicate
`
`with an advertisement provider. In response, the advertisement
`
`provider provides a customized advertisement. The advertisement
`
`provider then tracks the consumer's response to the customized
`
`advertisement." (0000 1012, 2:59-3:5.) "The consumer computer
`
`the merges the content provider's electronic document with the
`
`advertisement provided by the advertisement provider to create a
`
`single displayed document to the consumer." (Id., 3:58-65.)
`
`The advertisement request in Angles is an unblockable signal. (0000 1003,
`
`司62.)In fact, Angles uses one ofthe exact same types ofrequest that is described
`
`in the '045 patent -a COI request. (Id.)百lIsmeans that the signal is dynamic and
`
`the resulting content would not be cached. (1d.) Because the request identifies
`
`dynamic content that would not have previously been cached, a POSA would also
`
`have recognized that referencing a COI script in the advertisement request prevents
`
`the advertisement request 企om being "cache-blocked" 企om reaching the
`
`advertisement provider computer 18. (Id..)
`
`Instead of the advertisement provider actually providing a copy of the
`
`advertisement, the advertisement provider wiU provide a redirect signal which
`
`directs the consumer computer to another location. For example, "the consumer
`
`computer 12 receives an advertisement command which directs the consumer
`
`

`
`Pα:ge20
`
`Inter Partes Review of
`U.S. Patent No. 6,286,045
`
`computer 12 to retrieve and display one of the advertisements stored on the
`
`advertising storage medium 44." (GOOG 1012, 11 :61-65.)
`
`While the redirect signal企omthe advertisement computer is described in
`
`Angles as pointing to a location in local storage, it would have been obvious to a
`
`POSA that the redirect signal could just as easily point to a location on an extemal
`
`storage device, such as another server. (GOOG 1003,町司 65-67.)Angles delivers
`
`advertisement information using HTTP. (See, e.g., GOOG 1

This document is available on Docket Alarm but you must sign up to view it.


Or .

Accessing this document will incur an additional charge of $.

After purchase, you can access this document again without charge.

Accept $ Charge
throbber

Still Working On It

This document is taking longer than usual to download. This can happen if we need to contact the court directly to obtain the document and their servers are running slowly.

Give it another minute or two to complete, and then try the refresh button.

throbber

A few More Minutes ... Still Working

It can take up to 5 minutes for us to download a document if the court servers are running slowly.

Thank you for your continued patience.

This document could not be displayed.

We could not find this document within its docket. Please go back to the docket page and check the link. If that does not work, go back to the docket and refresh it to pull the newest information.

Your account does not support viewing this document.

You need a Paid Account to view this document. Click here to change your account type.

Your account does not support viewing this document.

Set your membership status to view this document.

With a Docket Alarm membership, you'll get a whole lot more, including:

  • Up-to-date information for this case.
  • Email alerts whenever there is an update.
  • Full text search for other cases.
  • Get email alerts whenever a new case matches your search.

Become a Member

One Moment Please

The filing “” is large (MB) and is being downloaded.

Please refresh this page in a few minutes to see if the filing has been downloaded. The filing will also be emailed to you when the download completes.

Your document is on its way!

If you do not receive the document in five minutes, contact support at support@docketalarm.com.

Sealed Document

We are unable to display this document, it may be under a court ordered seal.

If you have proper credentials to access the file, you may proceed directly to the court's system using your government issued username and password.


Access Government Site

We are redirecting you
to a mobile optimized page.





Document Unreadable or Corrupt

Refresh this Document
Go to the Docket

We are unable to display this document.

Refresh this Document
Go to the Docket