throbber
Paper No. 18
`
`
`UNITED STATES PATENT AND TRADEMARK OFFICE
`
`––––––––––––––––––
`
`BEFORE THE PATENT TRIAL AND APPEAL BOARD
`
`––––––––––––––––––
`
`GREAT WEST CASUALTY COMPANY; BITCO GENERAL INSURANCE
`CORPORATION; and BITCO NATIONAL INSURANCE COMPANY,
`Petitioners,
`
`v.
`
`INTELLECTUAL VENTURES II LLC,
`Patent Owner.
`
`––––––––––––––––––
`
`Case No. IPR2015-01706
`U.S. Patent No. 7,516,177
`
`––––––––––––––––––
`
`PETITIONERS’ REPLY
`
`
`
`

`
`IPR2015-01706
`
`
`
`Petitioners’ Reply
`
`Table of Contents
`
`I.
`
`II.
`
`INTRODUCTION ........................................................................................ 1
`
`PATENT OWNER MISCONSTRUES THE CLAIMS ............................... 11
`
`A. A Link Is A Type of “Content” ......................................................... 11
`
`B.
`
`“Content” Is Added by Linking to It ................................................. 11
`
`III. CLAIM 11 IS UNPATENTABLE .............................................................. 12
`
`A. Wherein Clause ................................................................................. 12
`
`B.
`
`Administrative Interface ................................................................... 17
`
`IV. CLAIM 16 IS UNPATENTABLE .............................................................. 19
`
`A.
`
`B.
`
`Selecting Content .............................................................................. 19
`
`Accessing the Centralized Access Point ............................................ 21
`
`V.
`
`CONCLUSION .......................................................................................... 22
`
`
`
`
`
`
`
`i
`
`

`
`IPR2015-01706
`
`
`
`Petitioners’ Reply
`
`TABLE OF AUTHORITIES
`
` Page(s)
`
`Cases
`
`Applied Medical Resources Corp. v. US Surgical Corp.,
`448 F. 3d 1324 (Fed.Cir. 2006) .......................................................................... 7
`
`Becton, Dickinson & Co. v. Tyco Healthcare Group,
`616 F.3d 1249 (Fed. Cir. 2010) ...................................................................... 5, 6
`
`Blue Calypso, Inc. v. Groupon, Inc.,
`93 F. Supp. 3d 575 (E.D. Tx. 2015) ................................................................... 7
`
`Cuozzo Speed Techs., LLC v. Lee,
`136 S. Ct. 2131 (2016) ....................................................................................... 2
`
`Dealertrack, Inc. v. Huber,
`674 F.3d 1315 (Fed. Cir. 2012) .......................................................................... 7
`
`EMC Corp. et al. v. Pure Storage, Inc.,
`Civ. No. 13-1985-RGA, Dkt. No. 362 (D. Del. Feb. 2, 2016) ............................ 6
`
`Facebook Inc. v. Pragmatus LLC,
`582 Fed.Appx. 864, slip. Op. (Fed. Cir. 2014) ................................................... 8
`
`Kraft Foods, Inc. v. International Trading Co.,
`203 F.3d 1362 (Fed. Cir. 2000) .......................................................................... 7
`
`Ex parte Markush,
`1925 Dec. Comm’r Pat. 126 (1924) ................................................................... 3
`
`Phillips v. AWH Corp.,
`415 F.3d 1303 (Fed. Cir. 2005) ................................................................ 5, 8, 11
`
`Powell V. Home Depot U.S.A., Inc.,
`663 F.3d 1221 (Fed. Cir. 2011) .......................................................................... 6
`
`Silergy Corp., v. Monolithic Power Sys., Inc.,
`IPR2015-00803, Paper 9 (Sept. 11, 2015) ........................................................ 22
`
`Vitronics Corp. v. Conceptronic, Inc.,
`90 F.3d 1576 (Fed. Cir. 1996) .................................................................... 11, 20
`ii
`
`

`
`IPR2015-01706
`
`Other Authorities
`
`
`
`Petitioners’ Reply
`
`37 C.F.R. § 42.100(b) ............................................................................................. 2
`
`MPEP 2173.05(H) .................................................................................................. 3
`
`
`
`
`
`iii
`
`

`
`IPR2015-01706
`
`
`
`Petitioners’ Reply
`
`Exhibit List
`
`1006
`1007
`1008
`1009
`1010
`
`1011
`1012
`
`1013
`
`Exhibit # Reference Name
`1001
`U.S. Patent No. 7,516,177 to Knapp
`1002
`File History of U.S. Patent No. 7,516,177
`1003
`Declaration of Philip Greenspun, Ph.D.
`1004
`Curriculum Vitae of Philip Greenspun, Ph.D.
`Eric Lease Morgan, MyLibrary: A Model for Implementing a User-
`1005
`centered, Customizable Interface to a Library’s Collection of
`Information Resources (1999)
`U.S. Patent No. 5,715,314 to Payne
`[RESERVED]
`U.S. Patent No. 5,987,440 to O’Neil
`U.S. Patent No. 8,601,373 to Ackley
`Declaration of Eric Lease Morgan regarding Public Accessibility of
`the MyLibrary Article (August 3, 2015)
`Declaration of Simeon Warner (July 6, 2015)
`Ginsparg, P., It was twenty years ago today . . . arXiv.org history (Sep.
`13, 2011)
`Berners-Lee, T. and Connolly, D., RFC 1866, Hypertext Markup
`Language – 2.0 (November 1995)
`Berners-Lee, T., Fielding, R., and Frystyk, H., RFC 1945, Hypertext
`Transfer Protocol – HTTP/1.0 (May 1996)
`U.S. Patent No. 5,761,662 to Dasan
`[RESERVED]
`U.S. Patent No. 6,632,248 to Isaac
`U.S. Patent No. 6,119,167 to Boyle
`U.S. Patent No. 4,925,240 to Peters
`U.S. Patent No. 5,288,980 to Patel
`U.S. Patent No. 6,347,333 to Eisendrath
`
`1014
`
`1015
`1016
`1017
`1018
`1019
`1020
`1021
`
`iv
`
`

`
`IPR2015-01706
`
`
`
`Petitioners’ Reply
`
`1025
`1026
`
`1027
`
`1028
`1029
`1030
`
`1031
`1032
`
`Exhibit # Reference Name
`1022
`U.S. Patent No. 6,032,162 to Burke
`1023
`U.S. Patent No. 6,135,646 to Kahn
`White, S., ABYSS: A Trusted Architecture for Software Protection,
`1024
`IEEE (1987)
`U.S. Patent No. 5,260,999 to Wyman
`Bartlett, J., Experience with a Wireless World Wide Web Client, IEEE
`(1995)
`Joseph, A., Mobile Computing with the Rover Toolkit, IEEE
`Transaction on Computers, Vol. 46, No. 3 (March 1997)
`U.S. Patent No. 5,857,191 to Blackwell
`U.S. Patent No. 6,625,447 to Rossmann
`Lidsky, D., Home on the Web, PC Magazine (Vol. 17, No. 15)(Sept. 1,
`1998)
`Chesnais, P., et al., The Fishwrap Personalized News System, IEEE
`Rich, L., et al., How Libraries Are Providing Access to Electronic
`Serials: A Survey of Academic Library Web Sites, Serials Review 25:2,
`35-46 (1999)
`Poynder, R., Lexis-Nexis: Past and Future, Online & CD-ROM
`Review, Vol. 22, No. 2 (1998)
`MyLibrary, Archive.org - my.lib.ncsu.edu (8/16/99)
`U.S. Patent No. 6,922,781 to Shuster
`Berners-Lee, T., et al., The World-Wide Web, Communications of the
`ACM, Vol. 37, No. 8, p. 76 (August 1994)
`Persistent Client State HTTP Cookies, Wayback Machine –
`https://web.archive.org/web/19981205102303/http://www.netscape.co
`m/newsref/std/cookie_spec.html
`U.S. Patent No. 6,393,462 to Mullen-Schultz
`U.S. Patent Application Publication No. 20010032152 to Khosla
`[RESERVED]
`[RESERVED]
`
`1033
`
`1034
`1035
`1036
`
`1037
`
`1038
`1039
`1040
`1041
`
`v
`
`

`
`IPR2015-01706
`
`
`
`Petitioners’ Reply
`
`Exhibit # Reference Name
`1042
`Exhibit A - Infringement Contentions to Reply Brief Supporting
`BITCO’s Amended Venue Transfer Motion (Dkt 44, Ex. 3) Civ. No.
`6-15-cv-59 (May 29, 2015)
`[RESERVED]
`[RESERVED]
`[RESERVED]
`Declaration of Vernon M. Winters
`Deposition Transcript of Dr. Yannis Papakonstantinou (June 9, 2016)
`
`1043
`1044
`1045
`1046
`1047
`[NEW]
`1048
`[NEW]
`
`Infringement Contentions as to the BITCO Defendants, Civ. No. 6-15-
`cv-59 (May 15, 2015)
`
`vi
`
`

`
`IPR2015-01706
`
`
`
`Petitioners’ Reply
`
`I.
`
`INTRODUCTION
`
`Patent Owner asks the Board to finally construe the word “content” to
`
`exclude “links to content.” That would be error, for three reasons. First, that
`
`construction is not the broadest reasonable construction. Second, the 177 Patent’s
`
`specification expressly describes “content” to include links to content—links are a
`
`type, or species, of content. Third, precedent holds merely that different claim
`
`terms are presumed to have different scope. That presumption can be, and often is,
`
`overcome—it is readily overcome based on the intrinsic record in this case.
`
`Patent Owner also implicitly asks the Board to construe claim language
`
`requiring the selection of “content” for addition to a “centralized access point” as
`
`excluding the selection of content that results in the addition of links to the access
`
`point. That too would be error, as the only disclosed example of the selection of
`
`“content” for addition to a “centralized access point” results in the addition of links
`
`to the access point. When one adds milk to a shopping list, one does not open the
`
`jug and pour the liquid onto the list.
`
`Patent Owner’s remaining arguments similarly ignore the claim language,
`
`the clear disclosures of the specification, or both. They must all be rejected and the
`
`claims at issue here found unpatentable.
`
`1
`
`

`
`IPR2015-01706
`
`
`
`Petitioners’ Reply
`
`II.
`
`PATENT OWNER MISCONSTRUES THE CLAIMS
`
`A. A Link Is A Type of “Content”
`
`Patent Owner contends that the claim word “content” must be construed to
`
`exclude links to content, relying on the language of claim 11 requiring a “server
`
`operative to store one or more of: a) content, b) links to content, c) information
`
`about content, and d) information about users including information about which
`
`content a user has chosen.” (emphasis added). Patent Owner argues from the list
`
`set forth in this server element that “content” must be construed to exclude “links
`
`to content.” Resp. 10. This position is contrary to the intrinsic record, Patent
`
`Owner’s litigation positions, and settled case-law.
`
`Patent Owner fundamentally misapplies the claim construction methodology
`
`that governs IPRs. The Supreme Court has recently confirmed that claims in an
`
`IPR must be given their broadest reasonable construction, Cuozzo Speed Techs.,
`
`LLC v. Lee, 136 S. Ct. 2131, 2134-35 (2016); 37 C.F.R. § 42.100(b), yet Patent
`
`owner’s claim construction argument instead tries to impose an unreasonably
`
`narrow construction. Here, the intrinsic record demonstrates that the claim terms
`
`“content” and “links to content” have different, but overlapping, scope because in
`
`the context of the 177 Patent links are a type (i.e., a species) of content.
`
`For example, the claim language at issue merely lists the type of information
`
`the claimed server must be “operative to store.” That the listed items may have
`
`2
`
`

`
`IPR2015-01706
`
`
`
`Petitioners’ Reply
`
`some overlap does not make one or more of them superfluous. Indeed, the
`
`“server” limitation of claim 11 is in the nature of a Markush Group, a well-known
`
`and long-used claiming technique. See Ex parte Markush, 1925 Dec. Comm’r Pat.
`
`126, 127 (1924). The fact that one member of such a group is a genus (“content”)
`
`and another is a species of that genus (“links to content”) is of no moment, as the
`
`Office has explained:
`
`Similarly, the double inclusion of an element by members of a
`Markush group is not, in itself, sufficient basis for objection to or
`rejection of claims. … The mere fact that a compound may be
`embraced by more than one member of a Markush group recited in the
`claim does not necessarily render the scope of the claim unclear. For
`example, the Markush group, “selected from the group consisting of
`amino, halogen, nitro, chloro and alkyl” should be acceptable even
`though “halogen” is generic to “chloro.”
`
`MPEP 2173.05(H) (emphasis added). An interpretation of claim 11 that held
`
`“content” to be generic to “links to content” is thus perfectly acceptable under the
`
`Office’s own procedures.
`
`Moreover, while nothing in the claim language indicates that “content” must
`
`exclude “links,” the specification requires the opposite by defining “links” to be a
`
`type of “content.” For example, in the context of the 177 Patent “content” is stored
`
`in a data structure called a “content object.” Ex. 1001 at 17:31-35. Indeed, Patent
`
`3
`
`

`
`IPR2015-01706
`
`
`
`Petitioners’ Reply
`
`Owner’s proposed interpretation for “content object” is “an object containing
`
`content.” Paper 7 at 23-24 (emphasis added).
`
`The specification of the 177 patent, moreover, discloses a “link type content
`
`object” that contains only a link to content. See Ex. 1001 at 47:15-18 (“FIG. 43 is
`
`a diagram of a screen display showing a link content builder page 504 provided for
`
`a content object type comprising a link.” (emphasis added)), 48:47-48, 48:64.
`
`Thus, under the specification, the content contained in a “link type content object”
`
`is a link, so a link must be a type of content.1
`
`Other passages of the 177 Patent confirm this conclusion by explaining how
`
`a “link type content object” can be built. For example, Figure 43 discloses that the
`
`“type” of content included in such a content object is a “link”:
`
`
`
`1 The 177 Patent also refers to a “tutorial content object,” which contains a tutorial.
`
`Ex. 1001 at 47:5-7. This tutorial “can consist exclusively of external links.” Ex.
`
`1001 at 53:54-56 (emphasis added). Thus, the patent discloses at least two types
`
`(species) of “content”—links and tutorials—that can comprise links.
`
`4
`
`

`
`IPR2015-01706
`
`
`
`Petitioners’ Reply
`
`
`
`Ex. 1001 at Fig. 43 (emphasis added). As the Federal Circuit explained in Phillips
`
`v. AWH Corp., 415 F.3d 1303, 1315 (Fed. Cir. 2005), the specification is the single
`
`best guide to the proper construction of a claim term—indeed, it is often
`
`dispositive. Here, that single best guide points, and firmly so, away from the result
`
`that the Patent Owner seeks.
`
`Patent Owner’s reliance on an isolated statement in Becton, Dickinson & Co.
`
`v. Tyco Healthcare Group, 616 F.3d 1249, 1254 (Fed. Cir. 2010), concerning
`
`infringement, does not suggest a different result. See Resp. 10. In Becton, the
`
`issue was whether two separately recited claim elements could be satisfied for
`
`purposes of infringement by a single accused structure. 616 F.3d at 1254-55.
`
`Because claim construction is a patent-specific exercise, the Court in that case
`5
`
`

`
`IPR2015-01706
`
`
`
`Petitioners’ Reply
`
`found they could not, based on its analysis of both the specification and claim
`
`language. Id. at 1255-57. In the context of other specifications and claim
`
`language, other courts have come to the opposite conclusion, see Powell V. Home
`
`Depot U.S.A., Inc., 663 F.3d 1221, 1231-32 (Fed. Cir. 2011), so Becton cannot be
`
`read as setting forth a hard and fast rule. As with most claim construction issues,
`
`the analysis turns on the intrinsic record, which in this case defines links as a type
`
`of content.
`
`Patent Owner’s mis-description of Becton, however, goes deeper than that.
`
`Just because two claim elements must read on two separate structures for purposes
`
`of infringement does not mean that the interpretation of those elements must be
`
`different, or mutually exclusive, as Patent Owner would have it. Consider a claim
`
`to a bicycle reciting “a first brake” and “a second brake.” To be satisfied, that
`
`claim may very well require two separate brakes, but that does not mean those two
`
`claim terms would not be construed in exactly the same way. See EMC Corp. et
`
`al. v. Pure Storage, Inc., Civ. No. 13-1985-RGA, Dkt. No. 362, at *7 (D. Del. Feb.
`
`2, 2016). Nothing in Becton suggests otherwise.
`
`Moreover, even different claim language can still read on the same structure.
`
`Consider, for example, claim 12 of the 177 Patent, which requires that “the
`
`distributed information access point comprises one or more of: a) a web page; b) a
`
`plurality of web pages; c) a portion of a web page ….” Ex. 1001 at 55:28-31. A
`
`6
`
`

`
`IPR2015-01706
`
`
`
`Petitioners’ Reply
`
`prior art “distributed information access point” comprising a plurality of web
`
`pages would also comprise “a web page” and “a portion of a web page.” While
`
`different claim terms may have different claim scope, and even different meanings,
`
`they can still read on the same structure. Applied Medical Resources Corp. v. US
`
`Surgical Corp., 448 F. 3d 1324, 1333 n.3 (Fed.Cir. 2006).
`
`The basis for Patent Owner’s error, which it asks the Board to adopt, is the
`
`assertion that different claim elements must to be construed as mutually exclusive.
`
`That is not the law. Different claim terms merely presumptively have different
`
`scope, but that presumption can be, and often is, rebutted by the intrinsic record,
`
`see, e.g., Kraft Foods, Inc. v. International Trading Co., 203 F.3d 1362, 1368 (Fed.
`
`Cir. 2000), and it does not preclude two different claim elements being given
`
`overlapping interpretations (as with the listed terms of claim 12, discussed above),
`
`see Blue Calypso, Inc. v. Groupon, Inc., 93 F. Supp. 3d 575, 600-01 (E.D. Tx.
`
`2015) (construing “set” to mean “a collection of one or more” even though the
`
`same claim included the phrase “at least one”).
`
`Under the broadest reasonable interpretation consistent with the
`
`specification, the Board must construe “content” to embrace all examples of
`
`content disclosed in the specification, so the claim term “content” must include a
`
`link to content. See Dealertrack, Inc. v. Huber, 674 F.3d 1315, 1322 (Fed. Cir.
`
`7
`
`

`
`IPR2015-01706
`
`
`
`Petitioners’ Reply
`
`2012) (including enumerated and non-enumerated examples within a term’s
`
`scope).
`
`Finally, Patent Owner is in no position to argue otherwise. In parallel
`
`litigation, for example, Patent Owner’s infringement contentions specifically
`
`identified links (called “Bookmarks”) on a portal website as satisfying the
`
`“content” requirements of the claims. See Ex. 1048 at 43-49. Patent Owner should
`
`not be heard to argue that the broadest reasonable interpretation of its claims does
`
`not cover the very structure it has accused of infringement under the Phillips
`
`standard. Facebook Inc. v. Pragmatus LLC, 582 Fed.Appx. 864, slip. Op. at *869
`
`(Fed. Cir. 2014) (non-precedential) (interpretation under BRI “cannot be narrower”
`
`than under Phillips). Given the intrinsic record here and the positions Patent
`
`Owner has taken, the broadest reasonable interpretation of the claim term
`
`“content” must include links to content.
`
`B.
`
`“Content” Is Added by Linking to It
`
`Patent Owner also contends that certain claim language (as in claim 16)
`
`requiring “selecting content … for addition to a centralized access point” does not
`
`cover the selection of content that results in the addition of a link to a user’s
`
`“centralized access point.” Resp. 37-39. That is incorrect. Regardless of the
`
`construction of “content,” such claim language must be construed broadly enough
`
`8
`
`

`
`IPR2015-01706
`
`
`
`Petitioners’ Reply
`
`to cover the addition of links to a centralized access point because that is the only
`
`disclosed example of the claimed functionality.
`
`For example, the only detailed example of selecting information for addition
`
`to a centralized access point in the 177 Patent is described with respect to Figures
`
`8, 9 and 10. Figure 8 is “a diagram of a screen display for a personal HowZone”
`
`(i.e., a centralized access point) before anything has been selected for addition. Ex.
`
`1001 at 3:58-60; 22:20-22. As is evident from the Figure, there is no content on
`
`the web page:
`
`
`
`Ex. 1001 at Fig. 8.
`
`The patent then describes the process of selecting content (in the example an
`
`article entitled “What is a Wireless LAN?”) for addition to the user’s personal web
`
`page by manipulating a different webpage called a “content detail page.” Ex. 1001
`
`at 23:11-24:4; Fig. 9. Figure 10 depicts the result of that process. Id. at 24:5-35.
`
`9
`
`

`
`IPR2015-01706
`
`
`
`Petitioners’ Reply
`
`As is again evident from the Figure, the only things that have been added to the
`
`user’s personal web page are a link (232) to the selected article and certain
`
`information about the article:
`
`
`
`Ex. 1001 at Fig. 10 (emphasis added). There is no other example of “selecting
`
`content … for addition to a centralized access point” in the patent specification, so
`
`the claims must be construed to cover such functionality.
`
`It is true that the patent also states that a “content object” may be added to a
`
`user’s personal web page. Ex. 1001 at 25:20-23. But a content object is not
`
`content; it is the container for content, as even Patent Owner recognizes (Paper 7 at
`
`23-24), and the patent explains that “[i]t is understood that, when a user adds a
`
`content object to their personal HowZone, they are actually adding a ‘link’ to that
`
`specific content object, wherein the link is actually provided on the user’s personal
`
`10
`
`

`
`IPR2015-01706
`
`
`
`Petitioners’ Reply
`
`web page, within box 212 of FIG. 8.” Ex. 1001 at 23:46-49 (emphasis added).2
`
`Thus, in the context of the 177 Patent, the addition of a “content object” to a
`
`personal web page is accomplished by adding a link.
`
`The Board cannot ignore these disclosures and must construe the claims in
`
`the context of the entire patent. Phillips v. AWH Corporation, 415 F.3d 1303,
`
`1313 (Fed. Cir. 2005). The only disclosed example of selecting content for
`
`addition to a personalized web page results only in the addition of a link to that
`
`content. The claims must be construed to embrace that functionality. Vitronics
`
`Corp. v. Conceptronic, Inc., 90 F.3d 1576, 1583 (Fed. Cir. 1996).
`
` .
`
`
`
`
`
`2 Indeed, Figure 10’s “Brief Description” states that it shows “the addition of a
`
`content object,” Ex. 1001 at 3:65-67, but its “Detailed Description” explains that
`
`“FIG. 10 is a diagram of the personal web page, corresponding with the personal
`
`web page of FIG. 8, but showing the addition of a link to a content object that has
`
`been added to the user's personal web page, or personal HowZone.” Id. at 24:5-11
`
`(emphasis added).
`
`11
`
`

`
`IPR2015-01706
`
`
`
`Petitioners’ Reply
`
`III. CLAIM 11 IS UNPATENTABLE
`
`A. Wherein Clause
`
`The “wherein clause” of claim 11 recites two separate capabilities, (1) a “log
`
`on” capability and (2) an “access content” capability:
`
`wherein a user is enabled with the capability to log on to their
`centralized access point from one or more distributed information
`access point(s) and access content chosen from one or more
`distributed information access point(s).
`
`Ex. 1001 at 55:23-27 (emphasis added).
`
`The Petition demonstrated that the “capability to … access content” claim
`
`language was satisfied in MyLibrary by the ability of a user to select, via
`
`Customization web pages, links for addition to her personal web page and to use
`
`those links to access content. See Pet. 35; Ex. 1005 at 9-10; Ex. 1003 at ¶¶134-38,
`
`235–236. As Petitioner’s expert Dr. Greenspun explained:
`
`MyLibrary explains that the user can customize information and links
`shown in the “Library and University Link,” “Bibliographic
`Databases, Electronic Journals, and Reference Shelf”; “Personal
`Links” and “Quick Searches” categories by selecting a “Customize
`hotlink” button associated with the category the user desires to
`customize. Ex. 1005 at 4–6. (Though somewhat obscured in the figure
`above, the “Customize” links is depicted in the dark-colored title bar
`above these sections.) Once the “Customize hotlink” button is
`selected, the user is presented with a list of links to additional
`
`12
`
`

`
`IPR2015-01706
`
`
`
`Petitioners’ Reply
`
`information that can be selected or de-selected and thereby added or
`removed from the user’s personalized web page. Id. at 6.
`
`Ex. 1003 at ¶134 (citations omitted).
`
`In its Institution Decision, the Board agreed, noting that the patent’s
`
`description of accessing content on the World Wide Web via links “unequivocally
`
`supports a construction that ‘access to content’ is broad enough to be met by the
`
`presence of links to content,” Paper 11 (“Dec.”) at 9, and concluded with respect to
`
`the “wherein” clause of claim 11 that “we construe ‘access to content’ as being met
`
`by the presence of links to content. MyLibrary discloses that a user’s personalized
`
`web page includes links to content, such as Reference Shelf, Bibliographic
`
`Databases, and Electronic Journals. Ex. 1005, 4.” Dec. 15. Patent Owner no
`
`longer disputes that “access to content” should be construed as including the
`
`presence of links to content. See Resp. 15-32 (never arguing the Board’s
`
`construction in this regard is incorrect).
`
`As to the “log on” capability, the Board concluded that “the precise
`
`relationship between the different elements of the ‘wherein’ clause [of claim 11]
`
`are not disclosed explicitly in MyLibrary,” but was persuaded “that the
`
`modifications to MyLibrary articulated by Petitioner to meet the ‘wherein’ clause
`
`would have been within the abilities of one of ordinary skill.” Dec. 15-16 (citing
`
`Pet. 47-48). The portions of the Petition cited by the Board in this passage (pages
`
`13
`
`

`
`IPR2015-01706
`
`
`
`Petitioners’ Reply
`
`47-48) demonstrated that “it would have been obvious to include a home page for
`
`the MyLibrary system that included a log on facility and other library information
`
`generally available to library users.” Pet. 47 (emphasis added). Thus, the Board
`
`agreed it would have been obvious to include a log on facility on the MyLibrary
`
`home page, and thereby satisfy the “capability to log on” requirement of claim 11.
`
`Patent Owner does not contest that conclusion either. See Resp. 15-32.
`
`Instead, Patent Owner argues that the Customization pages of MyLibrary
`
`“do not permit the accessed content to be chosen for addition to a user’s
`
`MyLibrary personalized web page” and therefore do not satisfy the “wherein”
`
`clause. Resp. 18 (emphasis in original).
`
`The “wherein” clause, however, does not require “the accessed content to be
`
`chosen for addition to a user’s” personalized web page, but instead requires that a
`
`user be “enabled with the capability to … access content chosen from one or more
`
`distributed information access point(s).” Nowhere does this claim language
`
`require that the content that is chosen be “for addition,” or actually added to, the
`
`user’s personal web page, and Patent Owner points to no language reciting such a
`
`requirement.5
`
`
`
`5 Even if such language existed in claim 11, as explained below in § IV.A with
`
`respect to claim 16, it would be insufficient to distinguish MyLibrary’s disclosure.
`
`14
`
`

`
`IPR2015-01706
`
`
`
`Petitioners’ Reply
`
`Moreover, as the Board found, a MyLibrary user is enabled with the ability
`
`to access content she has chosen from one or more distributed information access
`
`points (i.e., customization pages) by the presence of links to that content appearing
`
`on her personal web page. Dec. 15. In other words, the links are the mechanism
`
`by which the user is enabled with the capability to access chosen content.
`
`Indeed, an interpretation of this claim language excluding such links
`
`functionality would be inconsistent with the specification. As the Board noted, the
`
`patent’s description of using links on the World Wide Web to access content,
`
`“unequivocally supports a construction that ‘access to content’ is broad enough to
`
`be met by the presence of links to content.” Dec. 9. And, as demonstrated above,
`
`see § II, in the only disclosed example of adding content to a personal web page—
`
`described with respect to Figures 8, 9 and 10—the patent discloses adding only a
`
`link to the user’s web page, which the user can then use to access the chosen
`
`content.
`
`Patent Owner also argues that “MyLibrary’s customization pages … do not
`
`provide access to content that is chosen, as required by the wherein clause.” Resp.
`
`19-21. However, once again, the “wherein” clause of claim 11 does not require
`
`that “MyLibrary’s customization pages [i.e., the distributed information access
`
`points] … provide access to content that is chosen,” Resp. 19-21, but instead
`
`requires only that “a user is enabled with the capability to … access content
`
`15
`
`

`
`IPR2015-01706
`
`
`
`Petitioners’ Reply
`
`chosen from one or more distributed information access point(s)” (emphasis
`
`added). The distributed information access point of the claim enables the
`
`choosing, not the access. As the Board correctly concluded in its Institution
`
`Decision, MyLibrary satisfies this claim language because it discloses that a user
`
`can choose content from the customization pages (i.e., “distributed information
`
`access points”), and then access that content via the links that are thereby added to
`
`her personal web page. See Dec. 15-16 (citing Pet. 47-48).
`
`In sum, the “wherein” clause of claim 11 requires that the “user is enabled
`
`with the capability to … access content chosen from one or more distributed
`
`information access points,” which the Board has correctly construed to cover the
`
`use of links. Dec. 8-9, 15. The link capability of MyLibrary clearly satisfies that
`
`claim language. And since Patent Owner does not contest that “it would have been
`
`obvious to include a home page for the MyLibrary system that included a log on
`
`facility and other library information generally available to library users,” Pet. 47-
`
`48, MyLibrary also satisfies the remainder of the wherein clause of claim 11.6
`
`
`
`6 Patent Owner also contends that Petitioner’s expert, Dr. Greenspun, “signaled
`
`Petitioner’s intent to propound a new theory,” Resp. 18, and spends a fair amount
`
`of ink addressing this alleged new theory, id. at 18-19, 21-25. There is no new
`
`theory. The analysis discussed in this brief is the same one advanced in the
`
`16
`
`

`
`IPR2015-01706
`
`
`
`Petitioners’ Reply
`
`B. Administrative Interface
`
`Patent Owner next argues that MyLibrary does not disclose the
`
`“administrative interface” of claim 11 because the administrative functionality of
`
`MyLibrary is supposedly not “operative to create groupings of content,” an
`
`argument based on Patent Owner’s assertion that the claim phrase “groupings of
`
`content” is limited to the creation of entirely new “categories” mentioned in the
`
`patent. Resp. 32-37.
`
`Patent Owner’s implicit claim interpretation is erroneous. The claim does
`
`not require the ability to create “categories of content,” just the ability to create
`
`“groupings of content,” and the ordinary meaning of “category” (e.g. teenagers) is
`
`not the same as the meaning of “grouping” (e.g., John, Paul, George, and Ringo).
`
`Moreover, the Summary of the Invention discloses that the categorization and
`
`grouping of content are two different functionalities:
`
`Additionally, information in the form of content objects available on
`the networked system is enhanced … by categorizing content.
`Furthermore, content is distributed to users in several manners: by
`way of a primary Web site, and by way of predetermined but dynamic
`
`
`
`Petition and analyzed in the Institution Decision. Pet. 29-34; Dec. 13-16. Dr.
`
`Greenspun was merely responding to ambiguous, open-ended cross-examination
`
`questions. See, e.g., Ex. 2008 at 16:19-22, 17:10-12.
`
`17
`
`

`
`IPR2015-01706
`
`
`
`Petitioners’ Reply
`
`groups of aggregated content objects which are made available via
`banners and/or tokens.
`
`Ex. 1001 at 2:37-43 (emphasis added). This conclusion is further confirmed by the
`
`disclosure of the 177 Patent that categories may be initially created without any
`
`content in them at all. Ex. 1001 at 30:36-38 (“Accordingly, it is possible that a
`
`new category may not have a content object assigned to it at the time the new
`
`category is added.”). A category with no content in it at all cannot fairly be called
`
`a “grouping of content,” so the mere creation of a category cannot be an example
`
`of creating a “grouping of content.”
`
`Indeed, as demonstrated by the distinction between “groupings” and
`
`“categories” drawn in the Summary of Invention, the actual disclosed example of
`
`the claimed “grouping of content” is what the patent refers to as the “aggregation”
`
`(a synonym for “grouping”) of content objects. See, e.g., Ex. 1001 at 14:15-18
`
`(“FIG. 2 forms a process flow diagram showing the logic processing for
`
`aggregating content objects using system 100 (of FIG. 1). More particularly, FIG.
`
`2 illustrates logic processing used to aggregate content objects.” (emphasis
`
`added.)). As Figure 2 and its related description confirm, the aggregation of
`
`content objects involves the “associate[ion of] one or more content objects with a
`
`distribution mechanism,” such as on the “display of a client computer.” See id. at
`
`14:29-42.
`
`18
`
`

`
`IPR2015-01706
`
`
`
`Petitioners’ Reply
`
`As the Petition demonstrated,

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