throbber
Paper No. 14
`
`
`UNITED STATES PATENT AND TRADEMARK OFFICE
`
`
`
`
`
`
`
`BEFORE THE PATENT TRIAL AND APPEAL BOARD
`
`
`
`
`
`
`
`OLD REPUBLIC GENERAL INSURANCE GROUP, INC.;
`OLD REPUBLIC INSURANCE COMPANY;
`OLD REPUBLIC TITLE INSURANCE GROUP, INC.; and
`OLD REPUBLIC NATIONAL TITLE INSURANCE COMPANY
`Petitioners,
`
`v.
`
`INTELLECTUAL VENTURES I LLC,
`Patent Owner
`
`____________________
`
`Inter Partes Review No. IPR2015-01992
`Patent No. 6,546,002
`
`
`
`
`
`
`
`
`
`
`PETITIONER’S REPLY
`________________________
`
`
`
`

`
`IPR2015-01992
`
`
`
`Contents
`
`Petitioners’ Reply
`
`I.
`
`II.
`
`INTRODUCTION ........................................................................................... 1
`
`PATENT OWNER MISCONSTRUES THE CLAIMS .................................. 1
`
`A.
`
`B.
`
`“Mobile Interface” ................................................................................. 1
`
`“Pointer” ................................................................................................ 4
`
`C. Means-Plus-Function ............................................................................ 7
`
`III. CLAIMS 1-49 ARE UNPATENTABLE ........................................................ 8
`
`A. Huang Anticipates Claims 1, 2, 7-12, 17-23, 25, 26, 30-38, 40-45, and
`47-49 ...................................................................................................... 8
`
`1.
`
`2.
`
`3.
`
`4.
`
`Huang Discloses a “Mobile Interface Including a Plurality of
`Pointers” (Claims 1, 11, 34, and 40) ........................................... 8
`
`Huang Discloses “Means for Accessing …” (Claim 25) ......... 11
`
`Huang Discloses “Means for Retrieving …” (Claim 49) ......... 14
`
`Huang Discloses “Retrieving the Mobile Interface Via a
`Cellular Network” (Claims 9, 19, 32, 37, and 44) .................... 15
`
`B.
`
`C.
`
`Huang Renders Obvious Claims 4, 14, 21-23 and 28 ......................... 18
`
`Huang and Boyer Render Claims 3, 13, and 27 Obvious ................... 18
`
`D. Huang and Boyer Render Claims 5, 15, and 29 Obvious ................... 21
`
`E.
`
`F.
`
`Huang and Hayes Render Claims 6, 16, 39, and 46 Obvious ............. 22
`
`Huang and Raman Render Claim 24 Obvious .................................... 25
`
`IV. CONCLUSION .............................................................................................. 25
`
`
`
`i
`
`
`
`

`
`IPR2015-01992
`
`
`
`Petitioners’ Reply
`
`TABLE OF AUTHORITIES
`
` Page(s)
`
`Cases
`In re Antor Media Corp.,
`689 F.3d 1282 (Fed. Cir. 2012) .......................................................................... 18
`
`Blackboard, Inc. v. Desire2Learn, Inc.,
`574 F.3d 1371 (Fed.Cir. 2009) ............................................................................. 8
`
`Cadiocom, LLC v. Robert Bosch Healthcare Sys., Inc.,
`IPR2013-00451, Paper 65 (Jan. 15, 2015) .......................................................... 18
`
`Chiuminatta Concrete Concepts v. Cardinal Industries,
`145 F. 3d 1303 (Fed.Cir. 1998) ............................................................................ 8
`
`In re Donohue,
`766 F.2d 531 (Fed. Cir. 1985) ............................................................................ 19
`
`Google Inc. v. Jongerius Panoramic Technologies, LLC,
`IPR2013-00191, Paper 70 (Aug. 12, 2014) ........................................................ 18
`
`Howmedica Osteonics Corp. v. Wright Med. Tech.,
`540 F.3d 1337 (Fed. Cir. 2008) ............................................................................ 3
`
`In re Paulsen,
`30 F.3d 1475 (Fed. Cir. 1994) .............................................................................. 6
`
`Phillips v. AWH Corporation,
`415 F.3d 1303 (Fed. Cir. 2005) ............................................................................ 5
`
`Vivid Techs., Inc. v. Am. Sci. & Eng’g, Inc.,
`200 F.3d 795 (Fed. Cir. 1999) .............................................................................. 2
`
`WMS Gaming, Inc. v. Int’l Game Tech.,
`184 F.3d 1339 (Fed. Cir. 1999) ............................................................................ 8
`
`Statutes
`
`35 U.S.C. § 112(6) ............................................................................................... 8, 16
`
`37 C.F.R. § 42.6(e) ................................................................................................... 28
`ii
`
`

`
`IPR2015-01992
`IPR2015—O1992
`
`
`
`Petitioners’ Reply
`Petitioners’ Reply
`
`37 C.F.R. § 42.24 ..................................................................................................... 27
`37 C.F.R. § 42.24 ................................................................................................... ..27
`
`MPEP § 2181(I)(A) .................................................................................................... 8
`MPEP § 2181(I)(A) .................................................................................................. ..8
`
`
`
`
`
`iii
`
`iii
`
`

`
`IPR2015-01992
`
`
`
`Petitioners’ Reply
`
`Exhibit List
`
`Exhibit # Reference Name
`1001
`U.S. Patent No. 6,546,002 to Kim
`1002
`U.S. Patent No. 6,546,002 File History
`1003
`Declaration of Dr. Philip Greenspun
`1004
`Curriculum Vitae of Dr. Philip Greenspun
`1005
`U.S. Patent No. 6,571,245 to Huang
`1006
`U.S. Patent No. 6,268,849 to Boyer
`1007
`U.S. Patent No. 6,339,826 to Hayes
`Berners-Lee, RFC1866, Hypertext Markup Language – 2.0
`1008
`(November 1995)
`U.S. Patent No. 5,491,783 to Douglas
`Raman, T.V., Emacspeak – A Speech Interface (April 13-18, 1996)
`Microsoft Press Computer Dictionary (1997)
`U.S. Patent No. 5,519,760 to Borkowski
`U.S. Patent No. 6,571,245 – Exhibit A
`Common Ground, Chi 96 Conference Proceedings
`Bartlett, Experience with a Wireless World Wide Web Client, IEEE
`(1995)
`Email, dated October 8, 2014, from Derek Gilliland regarding IV v.
`Old Republic
`[RESERVED]
`WO 1998012833 Patent to Arnold
`
`1009
`1010
`1011
`1012
`1013
`1014
`1015
`
`1016
`
`1017-23
`1024
`[NEW]
`1025-29
`1030
`
`1031
`1032
`[NEW]
`
`[RESERVED]
`Intellectual Ventures I LLC, et. al., v. Old Republic General Ins. Grp.,
`Inc., Case No. 2-14-cv-01130, Doc. No. 1 (W.D. Pa. Aug 22, 2014)
`Declaration of Vernon M. Winters
`Deposition Transcript of Tim Williams, Ph.D. (September 23, 2016)
`
`iv
`
`

`
`IPR2015-01992
`
`
`
`Petitioners’ Reply
`
`I.
`
`INTRODUCTION
`
`Patent Owner asks the Board to undo the claim interpretations provisionally
`
`adopted in the Institution Decision, each of which was finally adopted in unrelated
`
`proceedings involving the 002 Patent. See IPR2015-00089, 00092. Patent Owner
`
`presents no new argument not already advanced in its preliminary response in this
`
`proceeding and during the course of the full trial in those other proceedings.
`
`Merely maintaining those interpretations here therefore requires rejection of almost
`
`all of Patent Owner’s arguments in this proceeding.
`
`For the few remaining issues, Patent Owner advances an unreasonably
`
`narrow understanding of the claims and, in at least one case, ignores the language
`
`of the claims entirely. The 002 Patent, however, is unexpired, so its claims must
`
`be given their broadest reasonable interpretation consistent with the specification.
`
`As demonstrated below, by that standard all claims of the patent are unpatentable
`
`over the prior art Huang patent. The Board should so find.
`
`II.
`
`PATENT OWNER MISCONSTRUES THE CLAIMS
`
`A.
`
`“Mobile Interface”
`
`The Board has construed “mobile interface” to mean “a user interface
`
`accessible on different computing devices.” Paper 7 (“Dec.”) at 8. Patent Owner
`
`asserts the term should be construed to additionally require that the mobile
`
`interface be “capable of dynamically accessing user-specific data on a network
`
`1
`
`

`
`IPR2015-01992
`
`
`
`Petitioners’ Reply
`
`server and local device.” Paper 11 (“Resp.”) at 8-11. Patent Owner and its expert,
`
`however, do not advance any argument as to why Huang would not disclose a
`
`“mobile interface” as they seek to have it construed. See Resp. 21-25; Ex. 2002,
`
`¶¶53, 55-58. Nor could they—as explained in the Petition, Huang discloses a user
`
`interface accessible on different computing devices capable of dynamically
`
`accessing user-specific data on a network server and local device. Pet. 17 (citing,
`
`inter alia, Ex. 1005, 2:25-34; 3:2-4; 5:31-54, 6:58-60, 7:22-24). The Board
`
`therefore need not address Patent Owner’s claim construction argument on this
`
`claim term in this proceeding, as it is irrelevant to the parties’ dispute. See Vivid
`
`Techs., Inc. v. Am. Sci. & Eng’g, Inc., 200 F.3d 795, 803 (Fed. Cir. 1999).
`
`To the extent the Board addresses this issue, however, Patent Owner’s
`
`arguments have already been finally rejected by the Board in its Final Written
`
`Decision in IPR2015-00092, Paper 44 at 9-12, and should be here for the same
`
`reasons. Moreover, in its Institution Decision in this proceeding the Board rejected
`
`this same argument, noting that “[a]lthough the term ‘dynamically access’ is used
`
`repeatedly in the ’002 patent, the difference between accessing and dynamically
`
`accessing resources is not explained in the ’002 patent or addressed by Patent
`
`Owner.” Paper 7, 8. Patent Owner provides no further explanation of the
`
`differences between “accessing” and “dynamically accessing” in its formal
`
`response, see Resp. 8-11, and its expert has conceded that the phrase would
`
`2
`
`

`
`IPR2015-01992
`
`
`
`Petitioners’ Reply
`
`effectively cover any type of accessing, Ex. 1032, 38:6-9, so its argument should
`
`be rejected again on the same basis. Indeed, the independent claims already
`
`require that the mobile interface be capable of accessing, in a dynamic sense,
`
`information stored both locally and remotely, see, e.g., Ex. 1001 at 17:18-20, so its
`
`proposed additional language adds nothing to the claim or is inconsistent
`
`therewith.1
`
`Nor does Patent Owner provide any other sufficient basis for adding this
`
`potentially narrowing language to the construction. For example, it cites a
`
`sentence from the specification (Ex. 1001 at 1:11–16) discussing “the present
`
`invention,” Resp. 8-9, but that passage merely states what the mobile interface can
`
`be used for or relates to. It is certainly not definitional. See Howmedica Osteonics
`
`Corp. v. Wright Med. Tech., 540 F.3d 1337, 1345 (Fed. Cir. 2008) (noting that a
`
`specification feature described as part of the present invention will only be read
`
`into the claims where “the specification makes clear that the invention requires”
`
`that feature) (emphasis added).
`
`
`
`1 Patent Owner contends that “dynamic access using the mobile interface is
`
`achieved by ‘periodically updat[ing] or query[ing] user profile data,’” citing Ex.
`
`1001, 5:61-62, but the cited sentence does not use the phrase “dynamic access.”
`
`3
`
`

`
`IPR2015-01992
`
`
`
`Petitioners’ Reply
`
`B.
`
`“Pointer”
`
`Patent Owner next argues that “pointer” should be construed, based on only
`
`one of several specification statements concerning pointers, to be limited to “a
`
`reference to a type of menu item that can be accessible on the computer, PDA or a
`
`server.” Resp. 11-13. But Patent Owner again makes no argument for
`
`patentability based on this construction, since its analysis ignores that its proposed
`
`interpretation requires “a reference to a type of menu item …” and does not apply
`
`that language. See, e.g., Resp. at 22 (asserting that the claim requires “a reference
`
`to a type of item” but arguing only that Huang does not include “reference to
`
`another data item.”); see also Ex. 2002 at ¶ 56 (same).2
`
`In any event, Patent Owner’s arguments in this regard have already been
`
`finally rejected by the Board in its Final Written Decision in IPR2015-00092,
`
`
`
`2 This understanding of Patent Owner’s interpretation was explained by Patent
`
`Owner’s expert, who testified that the word “reference” meant a “location,” Ex.
`
`1032, 62:14-25, and that the “reference” must be to a “category” of menu items,
`
`Ex. 1032, 60:11-13 (“Q. Okay. And so your interpretation requires a reference to
`
`a category of menu item? A. Yes.”). Patent Owner’s proposed interpretation, as
`
`understood by the expert, requires a location of a category of menu items. Patent
`
`Owner does not apply that understanding in its analysis.
`
`4
`
`

`
`IPR2015-01992
`
`
`
`Petitioners’ Reply
`
`Paper 44 at 13-15, and should be here for the same reasons. As the Board noted
`
`when it rejected this same argument in the Institution Decision in this proceeding,
`
`the 002 Patent characterizes the claimed pointer in several passages, Paper 7 at 8-9,
`
`and the specification discloses that the claimed inventions may be used in various
`
`technological contexts beyond just computers and PDAs, so there is no basis for
`
`adopting an interpretation limited to computers and PDA, as Patent Owner
`
`requests, id. at 9-10. Nor can the Board ignore the additional specification
`
`statements describing the claimed “pointer,” as Patent Owner demands, since
`
`claims must be construed in the context of the entire patent. Phillips v. AWH
`
`Corporation, 415 F.3d 1303, 1313 (Fed. Cir. 2005).3
`
`Finally, Petitioner observes that the passage relied on by Patent Owner (Ex.
`
`1001, 1:35-38) is located in a description of the background of the invention and in
`
`the context of a description of prior art operating systems and their user interfaces,
`
`see, e.g., Ex. 1001 at 1:20-65, not in any summary or detailed description of the
`
`
`
`3 Patent Owner also quotes Petitioner’s expert statement that he may have
`
`construed pointer “with a slightly different wording.” Resp. 13. Dr. Greenspun
`
`did not testify, however, that the Board’s opinion is wrong, and Patent Owner does
`
`not even suggest that whatever “slightly different” verbal formulation Dr.
`
`Greenspun would have used would have avoided a finding of unpatentability.
`
`5
`
`

`
`IPR2015-01992
`
`
`
`Petitioners’ Reply
`
`putative invention of the 002 Patent. Thus, the “context” referred to in that column
`
`1 passage is prior art computer user interfaces, which unsurprisingly refers to
`
`computers, PDAs and “menu items.”
`
`The passage relied on by the Board (Ex. 1001, 10:8-10), on the other hand,
`
`is located in the detailed description of the invention, see, e.g., id. at 9:61 et seq.
`
`(“FIG. 4 illustrates a detailed block diagram of an MIA in accordance with the
`
`present invention. …”), and is broader, just as the putative invention described in
`
`the 002 Patent is expressly intended to be used in various devices beyond a
`
`computer or PDA. See e.g., Ex. 1001, 1:16-19 (“… any computer device.”), 6:24-
`
`27. Thus, to the extent the inventor of the 002 Patent can be said to have acted as
`
`his own lexicographer for the claim term “pointer,” he did so in column 10, not in
`
`column 1.4 Patent Owner’s proposed interpretation must therefore be rejected
`
`again.
`
`
`
`4 Patent Owner cites In re Paulsen, 30 F.3d 1475, 1480 (Fed. Cir. 1994) for the
`
`proposition that there is a “presumption” that the broadest reasonable interpretation
`
`claim construction standard “is rebutted when the inventor provides a definition for
`
`a term in the specification with reasonable clarity, deliberateness, and precision.”
`
`Resp. 11. Paulson describes no such presumption, and if there was a lexicographic
`
`act, it is found in column 10, not column 1.
`
`6
`
`

`
`IPR2015-01992
`
`
`
`Petitioners’ Reply
`
`C. Means-Plus-Function
`
`Patent Owner next argues that the corresponding structure for the claimed
`
`“means for accessing …” element of claim 25 should be construed to be “a
`
`component that processes the associated location information for an item and
`
`causes the local device to access the item using the associated location
`
`information.” Resp. 14-17. Patent Owner’s arguments have already been rejected
`
`by the Board in its Final Written Decision in IPR2015-00092, Paper 44 at 17-19,
`
`and should be rejected here for the same reasons.
`
`Moreover, Patent Owner’s proposed corresponding structure is legally
`
`erroneous for several additional reasons. For example, none of the specification
`
`passages Patent Owner cites actually discloses “a component that processes the
`
`associated location information for an item and causes the local device to access
`
`the item using the associated location information.” See Resp. 14-17 (citing Ex.
`
`1001, 10:5-7, 10-15). While those passages refer to certain functionality of
`
`“controller 200” and “pointer resolver 206,” Patent Owner does not ask that
`
`controller 200 or pointer resolver 206 be included in the corresponding structure
`
`for this means element. See id. It is legally improper, however, to generalize the
`
`specific structures disclosed in the specification in a means-plus-function analysis.
`
`See WMS Gaming, Inc. v. Int’l Game Tech., 184 F.3d 1339, 1348-49 (Fed. Cir.
`
`7
`
`

`
`IPR2015-01992
`
`
`
`Petitioners’ Reply
`
`1999); Chiuminatta Concrete Concepts v. Cardinal Industries, 145 F. 3d 1303,
`
`1308 (Fed. Cir. 1998).
`
`Further, Patent Owner’s proposal is not structural at all, but instead purely
`
`functional. The word “component,” for example, is a nonce word that does not
`
`connote any definite structure. See, e.g., MPEP § 2181(I)(A). And the words that
`
`follow “component” in Patent Owner’s proposal are also purely functional. The
`
`statute, however, requires identification of the disclosed corresponding structure,
`
`see 35 U.S.C. § 112(6), and the identification of disclosed functionality is not
`
`sufficient, WMS Gaming, 184 F.3d at 1348-49; Blackboard, Inc. v. Desire2Learn,
`
`Inc., 574 F.3d 1371, 1383 (Fed.Cir. 2009).
`
`III. CLAIMS 1-49 ARE UNPATENTABLE
`
`A. Huang Anticipates Claims 1, 2, 7-12, 17-23, 25, 26, 30-38, 40-45,
`and 47-49
`
`1.
`
`Huang Discloses a “Mobile Interface Including a Plurality of
`Pointers” (Claims 1, 11, 34, and 40)
`
`The Petition demonstrated that Huang’s virtual desktop includes icons linked
`
`to various local and remote resources, Pet. 19; Ex. 1005, 6:60-7:1, Fig. 3; Ex.
`
`1003, ¶134, and that those icons are “pointers” under the interpretation adopted by
`
`the Board, Pet. 19-20. Patent Owner does not dispute that conclusion, see Resp. at
`
`21-25, so the Board can reject Patent Owner’s arguments on this issue if it
`
`maintains the interpretation of “pointer” it adopted in its Institution Decision and
`
`8
`
`

`
`IPR2015-01992
`
`
`
`Petitioners’ Reply
`
`in IPR2015-00092, Paper 44 at 13-15.
`
`However, even if Patent Owner’s construction were applied, Huang still
`
`satisfies the claims. Huang’s virtual desktop is preferably implemented using a
`
`web browser and presented in part as a web page containing icons representing a
`
`user’s applications and files, Ex. 1005, 6:40-7:10, though Huang also discloses that
`
`the icons can alternatively be presented in other forms such as a “list” (i.e., a
`
`menu), id. at 7:1-3. These icons each link to other web pages using conventional
`
`Uniform Resource Locaters (URLs), which Huang explains are “used as an
`
`identifier to point to a specific site or location of a computer and its contents on the
`
`web.” Ex. 1005, 5:60-66; see id. at 5:55-6:15, 19:54-56.
`
`Huang’s disclosure thus fits within Patent Owner’s proposed construction
`
`because each of Huang’s icons includes a “reference” (URL, id., 6:40-7:10) “to a
`
`type of menu item” (text file, image, etc., id.), at least in the manner Patent Owner
`
`is reading that phrase in its analysis.5 Such files “can be accessible on the
`
`computer, PDA or a server” (e.g., when retrieved and displayed via a browser, Ex.
`
`
`
`5 Patent Owner’s expert Dr. Williams confirmed, for example, that for a “URL
`
`point[ing] to a file, the file would be the item,” and “[t]he URL would be the
`
`pointer.” Ex. 1032, 78:22-79:1, 80:13-15.
`
`9
`
`

`
`IPR2015-01992
`
`
`
`Petitioners’ Reply
`
`1005, 6:40-7:10). Thus, Huang discloses the claimed “pointers” even under Patent
`
`Owner’s proposed interpretation.6
`
`Patent Owner makes only two arguments for why it believes Huang does not
`
`disclose “pointers” under its interpretation.7 First, Patent Owner asserts that
`
`Huang is “devoid of information regarding what information is contained with the
`
`icons.” Resp. 23. Not so. Each icon is a link containing a URL that identifies the
`
`location of an HTML page or other file on a server. Ex. 1005, 2:30-32 (“The web
`
`page represents the virtual desktop of the user and includes links for applications
`
`
`
`6 Dr. William’s earlier assertion (from which he backed away during cross
`
`examination, see n.7 supra) that a URL does not include “reference (e.g., location)
`
`information” was never credible. Ex. 1032, 63:11-65:22. The 002 Patent equates a
`
`URL with an “address,” Ex. 1001, 2:30, which is clearly a type of location
`
`information, and Huang expressly states that the Uniform Resource Locator points
`
`to a specific location, see Ex. 1005, 5:57-62.
`
`7 In passing Patent Owner asserts that Petitioner “relies on broad conclusory
`
`statements” to show “pointers,” but quotes from claim 49’s means-plus-function
`
`equivalence analysis. Resp. 23 (citing Pet. 37-38). This is irrelevant to whether
`
`Huang’s icons fit within the broadest reasonable interpretation of a claimed
`
`“pointer.”
`
`10
`
`

`
`IPR2015-01992
`
`
`
`Petitioners’ Reply
`
`available to the user and files accessible by the user.”), 6:5-7 (“[I]f the user selects
`
`a link in an HTML page, the browser will access the new URL location pointed to
`
`by the link.”). Thus, Huang discloses icons that contain specific location
`
`information.
`
`Second, Patent Owner argues that in Huang “commands that are received
`
`and processed by one or more backend servers” do not include “references to
`
`underlying items represented by the icons.” Resp. 24. But the Petition never
`
`identifies the cited “commands” of Huang as satisfying the claimed “pointers,” so
`
`that argument is irrelevant.
`
`Huang therefore discloses the use of “pointers” under either parties’
`
`construction of that term.
`
`2.
`
`Huang Discloses “Means for Accessing …” (Claim 25)
`
`The Petition also demonstrated that Huang satisfies the “means for
`
`accessing” of claim 25 under the Board’s interpretation by the disclosure of the
`
`networked computers of Figures 1 & 2 (i.e., the corresponding structure of this
`
`means element: “a computer connected to a network”) that can, via a web browser,
`
`load a user’s virtual desktop and its associated icons to access her files,
`
`applications, etc. (i.e., the function of this means element: “accessing the user
`
`specific resources and information using the plurality of pointers”). Pet. 28-29;
`
`Ex. 1005, 7:28-30, Figs. 1-2; Ex. 1003, ¶¶120-122, 179-180, 260-61. Patent
`
`11
`
`

`
`IPR2015-01992
`
`
`
`Petitioners’ Reply
`
`Owner does not dispute this conclusion. See Resp. at 25-26.
`
`Instead, Patent Owner argues that Huang “does not disclose the structure
`
`equivalent to the local pointer resolver of the ’002 patent.” Resp. 26. However,
`
`Patent Owner has not requested an interpretation that identifies “the local pointer
`
`resolver of the ’002 patent” as part of the disclosed corresponding structure of this
`
`claim element. See id. at 14-17. Instead, its proposed corresponding structure is “a
`
`component that processes the associated location information for an item and
`
`causes the local device to access the item using the associated location
`
`information.” See id. Its argument about the pointer resolver is thus irrelevant.
`
`Moreover, Huang does disclose a “pointer resolver” because it discloses that
`
`the networked computers of Huang’s Figures 1 and 2 (i.e., the structure identified
`
`in the Petition as satisfying this claim element, see Pet. at 29; Ex. 1003 at ¶¶ 179-
`
`180) provide the functionality required by this claim element via a web browser
`
`running on those computers, Ex. 1005 at 6:8-10, and that the browser resolves the
`
`URLs of Huang’s icons, Ex. 1005 at 5:66-6:25. This is the same
`
`structure/algorithm disclosed for the pointer resolver of the 002 Patent, at least for
`
`URL pointers. See Ex. 1001 at col. 10:13-18. Accordingly, to the extent a browser
`
`or pointer resolver were included in the corresponding structure of this claim
`
`element, Huang discloses the same structure for performing the function of this
`
`claim element as does the 002 Patent.
`
`12
`
`

`
`IPR2015-01992
`
`
`
`Petitioners’ Reply
`
`Indeed, even if one were to conclude that Huang does not disclose exactly
`
`the same structure, the browser of Huang is at least the equivalent to the 002 Patent
`
`pointer resolver/web browser. For example, URLs are a standardized mechanism
`
`for accessing resources on the web. Ex. 1005, 5:55-6:7. Thus, the web browser of
`
`Huang performs the same function (access resources) in at least substantially the
`
`same way (resolve URLs) to achieve the same results (obtain information for the
`
`user) as the pointer resolver or web browser of the 002 Patent.8
`
`Similarly, if one were to accept Patent Owner’s proposed corresponding
`
`structure – “a component that processes associated location information for an item
`
`and causes a local device to access the item using the associated location
`
`information,” Resp. 14-17 – Huang would still disclose the same or equivalent
`
`structure. The web browser as disclosed in Huang is “a component” (e.g., a
`
`portion of Huang’s client) “that processes associated location information” (e.g.,
`
`
`
`8 Moreover, while the 002 Patent suggests the pointer resolver may process pointer
`
`data that is similar to a URL but which has additional information, Ex. 1001 at
`
`8:34-35, it never states that such additional information has anything to do with the
`
`function of this claim element, so processing a URL is sufficient to perform that
`
`function. Thus, any differences between the pointer resolver and a web browser
`
`are insubstantial for purposes of this claim element.
`
`13
`
`

`
`IPR2015-01992
`
`
`
`Petitioners’ Reply
`
`processes a URL) “for an item” (e.g. a linked file) “and causes a local device to
`
`access the item using the associated location information” (e.g., resolving the URL
`
`and obtaining the file). Ex. 1005, 5:55-6:39. The Huang web browser is therefore
`
`the same or equivalent structure as Patent Owner has proposed be adopted as the
`
`corresponding structure for this means element.
`
`3.
`
`Huang Discloses “Means for Retrieving …” (Claim 49)
`
`The Petition explained how Huang discloses an embodiment in which the
`
`icons are replaced by a list of items, and how this list performs the same function
`
`and has the same corresponding structure (i.e., a pointer ) of the claimed “means
`
`for retrieving.” Pet. 36-37; Ex. 1005, 7:1-3. The Petition also explained that, “[t]o
`
`the extent one might argue Huang does not disclose identical structure for this
`
`claim element, the disclosed structures of Huang (icons, toolbars, lists, objects, or
`
`other indicators) are equivalent to the pointers of 002 Patent,” Pet. 37-38, relying
`
`on detailed testimony from Petitioners’ expert, Dr. Greenspun, see id. (citing Ex.
`
`1003, ¶¶357-60).
`
`In response, Patent Owner argues that, Huang cannot disclose the claimed
`
`“means for retrieving” because Huang purportedly does not disclose “pointers”
`
`under its construction. Resp. 26. This argument is misplaced because Patent
`
`Owner’s construction of “pointers” is wrong, see §II.B above, and because Huang
`
`discloses “pointers” even under that construction, see §III.A.1 above.
`
`14
`
`

`
`IPR2015-01992
`
`
`
`Petitioners’ Reply
`
`Further, Patent Owner ignores Petitioners equivalence analysis, offering no
`
`rebuttal whatsoever, and therefore concedes that Huang discloses at least the
`
`equivalent structure for this means element. Indeed, while Petitioner advanced
`
`extensive evidence on this point, see Pet. 37-38 (citing Ex. 1003, ¶357-60), Patent
`
`Owner’s expert never analyzed the question of equivalence, see Ex. 2002, ¶61; Ex.
`
`1032, 32:25-9 (“… I don’t think I have expressed an opinion on that.”), and
`
`apparently did not understand that a means-plus-function claim element can be
`
`literally met by an equivalent corresponding structure performing the claimed
`
`function, Ex. 1032, 32:18-24. Patent Owner and its expert therefore ignore the
`
`explicit language of Section 112 requiring a means-plus-function element “be
`
`construed to cover the corresponding structure … described in the specification
`
`and equivalents thereof.” 35 U.S.C. § 112 ¶6 (pre-AIA) (emphasis added).
`
`4.
`
`Huang Discloses “Retrieving the Mobile Interface Via a
`Cellular Network” (Claims 9, 19, 32, 37, and 44)
`
`The Petition also demonstrated that Huang discloses accessing the virtual
`
`desktop (which Huang explains is a web page, e.g., Ex. 1005 at 2:25-27; 6:16-25)
`
`through “a browser application installed on computer system 210,” which in one
`
`embodiment can be “mobile cellular phone 132” accessing the network over “a
`
`cellular link.” Pet. 44-45; Ex. 1005, 6:8-10, 4:23-24, 3:66-67; Ex. 1003, ¶179-81.
`
`For example, Petitioners’ expert Dr. Greenspun testified that it was “well-known
`
`by the filing date of Huang’s application that cellular phones and other mobile
`15
`
`

`
`IPR2015-01992
`
`
`
`Petitioners’ Reply
`
`devices could include web browsers capable of accessing the Internet and the
`
`World Wide Web.” Ex. 1003, ¶181.9 In support of his opinion, Dr. Greenspun
`
`also cited a 1995 IEEE publication that explained the “interactive response” of
`
`browsing the web over a cellular link “is satisfactory” even at “4800 baud.” Ex.
`
`1015, 155.10 The Petition therefore demonstrated that Huang discloses accessing
`
`his web page/virtual desktop (“mobile interface”) on a cellular phone over a
`
`cellular network and that, years before the July 1999 priority date of the 002
`
`Patent, those of ordinary skill in the art could access web pages in that manner.
`
`Patent Owner nevertheless argues that Huang “would not have enabled a
`
`person of ordinary skill to implement Huang’s virtual desktop over a cellular
`
`network without undue experimentation.” Resp. 27-30. This argument is not
`
`credible. The evidence cited by Dr. Greenspun, Ex. 1015, explains how a cellular
`
`phone was actually used to access a web page over a cellular network “[u]sing
`
`equipment available in the winter of 1994,” Ex. 1015 at Abstract, four years before
`
`
`
`9 Dr. Greenspun’s testimony is also informed by his experience in the late 1990s
`
`developing mobile phone Internet applications. See Ex. 1004, 1 (ArsDigita Corp.).
`
`10 See also Ex. 1015, 154 (“Sections 2 through 5 provide a roughly chronological
`
`record of the design and implementation of W4, a ‘proof of concept’ for a Wireless
`
`World Wide Web client.”)
`
`16
`
`

`
`IPR2015-01992
`
`
`
`Petitioners’ Reply
`
`the priority date of the 002 Patent. Moreover, Ex. 1015 and all of its details as to
`
`how to accomplish such an access was published in 1995, so a person of ordinary
`
`skill would have been aware of how to make such an access long before the 1999
`
`priority date of the 002 Patent. This is confirmed by various other publications of
`
`the time. See, e.g., Ex. 1003, ¶149; Ex. 1006, 2:49-65; see also, Int’l App. Publ.
`
`No. WO 98/12833 to Arnold et al. (1998) (Ex. 1024), 3:14-27; id. at 1:4-8, 8:1-29,
`
`10:27-30, Fig. 1.
`
`Moreover, the only evidence Patent Owner cites in response is the
`
`unsupported testimony of its expert, Dr. Williams. Such ipse dixit testimony by an
`
`expert should be ignored, Cadiocom, LLC v. Robert Bosch Healthcare Sys., Inc.,
`
`IPR2013-00451, Paper 65 at 28-29 (Jan. 15, 2015), and is wholly insufficient to
`
`meet Patent Owner’s burden of proving the non-enablement of a prior art U.S.
`
`patent, see In re Antor Media Corp., 689 F.3d 1282, 1287–88 (Fed. Cir. 2012);
`
`Google Inc. v. Jongerius Panoramic Technologies, LLC, IPR2013-00191, Paper 70
`
`at 37 (Aug. 12, 2014),
`
`Even when considered, however, Dr. Williams’ testimony does not support
`
`Patent Owner’s argument because Dr. Williams never testified that a skilled artisan
`
`could not have accessed a web page over a cellular network in 1999. Rather, his
`
`testimony was consistently hedged. See, e.g., Ex. 2002, ¶63-65 (Huang’s cellular
`
`network would not provide “reliable transport” and might be “unusable in most
`
`17
`
`

`
`IPR2015-01992
`
`
`
`Petitioners’ Reply
`
`scenarios”) (emphasis added).
`
`Thus, the unrebutted evidence of record demonstrates that the re

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