throbber

`
`
`
`
`
`
`
`
`
`
`
`Paper _____
`
` Trials@uspto.gov
`571-272-7822
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`UNITED STATES PATENT AND TRADEMARK OFFICE
`
`________________
`
`
`BEFORE THE PATENT TRIAL AND APPEAL BOARD
`
`________________
`
`UNIFIED PATENTS INC.,
`Petitioner
`
`v.
`
`SYNKLOUD TECHNOLOGIES, LLC,
`Patent Owner
`________________
`
`Case No. IPR 2019-01655
`
`Patent No. 9,098,526
`________________
`
`
`
`PATENT OWNER’S PRELIMINARY RESPONSE
`PURSUANT TO 37 C.F.R. §42.107
`
`
`
`
`
`

`

`TABLE OF CONTENTS
`
`TABLE OF CONTENTS
`
`TABLE OF AUTHORITIES
`
`LIST OF EXHIBITS
`
`
`
`
`
`
`
`
`
`
`
`
`
`PETITIONER HAS NOT MET ITS BURDEN
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`I.
`
`
`
`
`
`II.
`
`
`
`
`A. The Focus Must Be On the Claim Terms Themselves
`B. The Systems of the Prior Art Do Not Disclose the Subject
` Matter of the ‘526 Patent
`
`
`
`
`
`PROPERLY CONSTRUED, THE CLAIMS REQUIRE BOTH
`STORING AND RETRIEVAL OF A DATA OBJECT
`
`
`
`
`A. Petitioner’s Requested Construction Is Improper
`B. The Proposed Construction is Contrary to the Specification
`C. The Proposed Construction Violates a Central Tenet of
`Claim Construction
`
`
`
`
`
`
`
`III. PRUST, AS MODIFIED BY MAJOR, DOES NOT TEACH
`
`CRITICAL FEATURES OF THE CHALLENGED CLAIMS
`
`
`A. Prust in View of Major Does Not Describe and Enable the
`Claimed “Utilizing Download Information for the File
`Stored in (the) Cache
`
`
`
`B. Prust in View of Major Does Not Disclose “Predefined
`Capacity”
`
`
`
`C. Prust in View of Major Does Not Describe and Enable
`
`“Coupling” to Promote Storage and Retrieval
`
`
`D. There is No Motivation to Combine Prust with Major
`E. Dependent Claims 3 and 20 Recite Features Not Disclosed
`In Prust Combined with Major
`
`
`
`
`
`
`
`
`
`
`
`
`
`
` ii
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`ii
`
`iv
`
`v
`
`1
`
`2
`
`2
`
`7
`
`7
`9
`
`13
`
`15
`
`20
`
`27
`
`29
`31
`
`35
`
`

`

`37
`
`38
`
`40
`43
`
`46
`
`IV. CHAGANTI TAKEN IN VIEW OF MAJOR FAILS TO RENDER
`
`OBVIOUS ALL CLAIMS FOR MANY OF THE SAME REASONS
`
`PRUST IN VIEW OF MAJOR FAIL
`
`
`
`
`
`
`
`A. Chaganti in View of Major Do Not Describe and Enable
`The Claimed “Utilizing Download Information for the File
`Stored in (the) Cache”
`
`
`
`
`B. Chaganti in Light of Major Does Not Describe and Enable
`A Storage Space of Predefined Capacity Exclusively Assigned
`
`C. There is No Motivation to Combine Chaganti and Major
`
`
`
`
`V.
`
`
`
`CONCLUSION
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
` iii
`
`

`

`
`
`TABLE OF AUTHORITES
`
`
`
`
`
`
`
`
`
`
`
`PAGE NO.
`
`CASES
`
`Arctic Cat Inc. v. Bombardier Recreational Products, Inc.,
`
`876 F.3d 1350 (Fed. Cir. 2017)
`
`
`
`Aventis Pharma S.A. v. Hospira, Inc.,
`675 F.3d 1324 (Fed. Cir. 2012)
`
`
`Bicon Inc. v. Straumann Co.,
`
`441 F.3d 945 (Fed. Cir. 2006)
`
`Biofrontera Incorporated v. Dusa Pharmaceuticals, Inc.,
`
`2019 WL 965230 *10 (PTAB)
`
`
`
`Blackbird Tech LLC v. ELB Elecs., Inc.,
`895 F.3d 1374 (Fed. Cir. 2018)
`
`
`Ekchian v. Home Depot, Inc.,
`
`104 F.3d 1299 (Fed. Cir. 1997)
`
`Elekta Instrument S.A. v. O.U.R. Sci. Int’l, Inc.,
`
`214 F.3d 1302 (Fed. Cir. 2000)
`
`Ex parte Richardson,
`
`2004 WL 7730 *2 (PTAB 2009)
`
`Ex pare Wong,
`
`2014 WL 1618567 *5
`
`Gen. Am. Transp. Corp. v. Cryo-Trans, Inc.,
`
`93 F.3d 766 (Fed. Cir. 1996)
`
`In re Geerdes,
`
`491 F.2d 1260 (CCPA 1974)
`
`
`
`
`
`
`
`iv
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`43
`
`12
`
`14
`
`18
`
`12
`
`12
`
`14
`
`16
`
`23
`
`14
`
`16
`
`

`

`In re ICON Health & Fitness, Inc.,
`496 F.3d 1374 (Fed. Cir. 2007)
`
`
`In re IPR Licensing, Inc.,
`
`942 F.3d 1363 (Fed. Cir. 2019)
`
`In re Morsa,
`
`803 F.3d 1374 (NEED REST OF CITE)
`
`Merck & Co., Inc. v. Teva Pharmaceuticals USA, Inc.,
`
`395 F.3d 1364 (Fed. Cir. 2005)
`
`
`PAR Pharmaceutical, Inc. v. TWI Pharmaceuticals, Inc.,
`
`773 F.3d 1186 (Fed. Cir. 2014)
`
`
`
`Phillips v. AWH Corp.,
`415 F.3d 1303 (Fed. Cir. 2005)
`
`
`Power Integrations, Inc. v. Semiconductor Components Industries, LLC,
`
`926 F.3d 1306 (Fed. Cir. 2019)
`
`
`
`
`
`
`PPC Broadband, Inc. v. Corning Optical Communicatins RF, LLC,
`
`815 F.3d 747 (Fed. Cir. 2014)
`
`
`
`
`
`Regents of the University of Minnesota v. LSI Corporation,
`
`926 F.3d 1327 (Fed. Cir. 2019)
`
`
`
`SAS Institute v. Iancu,
`
`138 S.Ct. 1348
`
`SciMed Life Sys., Inv. V. Adv. Cardiovascular Sys., Inc.,
`
`242 F.3d 1337 (Fed. Cir. 2001)
`
`
`
`Star Scientific, Inc. v. R.J. Reynolds Tobacco Co.,
`655 F.3d 1364 (Fed. Cir. 2011)
`
`
`
`Techtronic Industries Co. Ltd. v. International Trade Commission,
`
`2019 WL 6753355 *4-6 (Fed. Cir. Dec. 12, 2019)
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
` v
`
`
`
`
`
`35
`
`32
`
`5
`
`14
`
`19
`
`11
`
`7
`
`2
`
`7
`
`1
`
`12
`
`18
`
`11,13
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`

`

`
`
`
`
`12
`
`12
`
`14
`
`12
`
`14
`
`1
`
`1
`
`1
`
`1
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`Thorner v. Sony Computer Entm’t Am. LLC,
`
`669 F.3d 1362 (Fed. Cir. 2012)
`
`Trs. Of Columbia Univ. v. Symantec Corp.,
`
`811 F.3d 1359 (Fed. Cir. 2016)
`
`Twilio Inc. v. TeleSign Corp.,
`
`2016 WL 5027521 *1 (PTAB)
`
`United States v. Adams,
`
`383 U.S. 39 (1966)
`
`Vtech Communications, Inc. v. Spherix, Inc.,
`
`2015 WL 981678 *4 (PTAB)
`
`Zodiac Pool Systems, Inc. v. Aqua Products, Inc.,
`
`2018 WL 6604633 *1 (PTAB 2018)
`
`
`
`STATUTES
`
`35 U.S.C. §314(a)
`
`37 C.F.R. §42.107
`
`37 C.F.R. §42.167(a)
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
` vi
`
`

`

`
`
`
`
`LIST OF EXHIBITS
`
`Description
`
`Exhibit
`Ex. 2001 Declaration of Jawadi
`Ex. 2002 CV of Jawadi
`Ex. 2003 Microsoft Computer Dictionary, 2002 Edition
`Ex. 2004 Hypertext Transfer Protocol – HTTP/1.1, rfc2616, June 999
`Ex. 2005 Management Systems: analyses and applications, August W. Smith,
`Dryden Press, 1982
`Ex. 2006 Definitions
`
`
`
`
`
`
`
`
` vii
`
`

`

`
`
`
`
`
`The undersigned acting on behalf of the Patent Owner, Synkloud
`
`Technologies, LLC (hereinafter “PO”) and pursuant to 37 C.F.R. §42.107,
`
`respectfully requests that the Petition of Unified Patents Inc., (hereinafter
`
`“Petitioner”) seeking Inter Partes Review (hereinafter “IPR”) of U.S. Patent No.
`
`9,098,526 (hereinafter “the ‘526 Patent”) be denied because Petitioner has failed to
`
`show that there is a reasonable likelihood that the Petitioner would prevail with
`
`respect to at least one of the claims.
`
`I. PETITIONER HAS NOT MET ITS BURDEN
`
`It is Petitioner’s burden to demonstrate, based on the parties' papers, “that there
`
`is a reasonable likelihood that the petitioner would prevail with respect to at least one
`
`of the claims challenged in the petition.” SAS Institute v. Iancu, 138 S. Ct. 1348,
`
`1353 (2018) citing 35 U.S.C. § 314(a). Importantly, the burden rests on Petitioner –
`
`there is no burden on Patent Owner to prove to the contrary. Zodiac Pool Systems,
`
`Inc. v. Aqua Products, Inc., 2018 WL 6604633 *1 (PTAB 2018). By regulation, PO’s
`
`showing is confined herein to a demonstration of the fashion in which Petitioner has
`
`failed to meet the burden imposed. 37 C.F.R. §42.167 (a). Thus, PO does not
`
`advance evidence demonstrating the patentability of the claims of the ‘526 Patent –
`
`this Preliminary Response is confined simply to a review of the reasons why there is
`
`
`
`1
`
`

`

`no reasonable likelihood of Petitioner prevailing on the charges of obviousness it has
`
`brought.
`
`
`
`
`
`
`
`A. The Focus Must Be On the Claim Terms Themselves
`
`PO notes that much of the Petition, and the Declaration relied on therein – Ex.
`
`1004 – address issues that do not arise out of a consideration of the specific
`
`limitations of the claims. In any IPR, the focus is necessarily on the recitations of
`
`those claims. Thus, the purpose of construing the claims of a patent is to better
`
`understand how the claim terms themselves are to be understood, not the other way
`
`around. PPC Broadband, Inc. v. Corning Optical Communications RF, LLC, 815 F.3d
`
`747, 755 (Fed. Cir. 2014). The ‘526 Patent addresses a problem that wireless device
`
`users were encountering in 2003 – how to quickly and efficiently access and store
`
`information secured from the internet without impacting the very limited storage
`
`capacity of that wireless device. That problem persists today. In particular – the ‘526
`
`Patent answers the very real need of how to quickly and efficiently search the internet
`
`from a wireless device, safely download data material identified without
`
`compromising the storage capacity of the wireless device, and then access that
`
`downloaded material. See the ‘526 Patent, Col. 2, ll. 29– 37.
`
`
`
`
`
`B. The Systems of the Prior Art Do Not Disclose the Subject Matter of the
`‘526 Patent
`
`
`
`
`
`
`
`
`
`The answer to the problem presented, as is discussed at length in the ‘526
`
`Patent and illustrated most simply in Figures 2 and3, is to provide an external storage
`
`
`
`
`
` 2
`
`

`

`
`
`
`for the information that can be accessed by the wireless device. Importantly, the ‘526
`
`Patent discloses and claims a system which provides for direct communication
`
`between the wireless device and a storage server through the internet (so-called in-
`
`band) downloading and “out-band” downloading, where the wireless devices directs
`
`data be downloaded to a storage server along a path from the internet to the server
`
`outside of the wireless device. Compare Figures 2 and 3.Thus, the search for data, its
`
`identification and download for storage does not require direct communication
`
`through the wireless device to download and store the data of interest (for example,
`
`multimedia data) all through one smooth operation that links the wireless device
`
`(e.g., a handheld phone) a remote storage server and the internet. Features and
`
`characteristics of the storage server and the handheld device, the method of use of
`
`that device in conjunction with the storage server and system of the ‘526 Patent, and
`
`the tools to be used in conjunction therewith are critically recited in the claims of the
`
`‘526 Patent.
`
`Before we come to the specific terms that distinguish the invention of the ‘526
`
`Patent, however, we must, because Petitioner insists we do, properly construe the
`
`terms of the claims of the ‘526 Patent. Petitioner insists that it makes no difference,
`
`whether the claims are construed to call for storing a data object on the server,
`
`retrieving a data object from the server (or storage space) or both, the challenged
`
`claims of the ‘526 Patent are obvious. Petition, pp. 7– 8: “Even if the Board were to
`
`
`
`
`
` 3
`
`

`

`
`
`
`
`disagree with the construction, the Board should still find all Challenged Claims
`
`unpatentable…”. If that were truly so, it would be unnecessary and inappropriate to
`
`construe the claims in such a fashion – there is no need to consider infringement in
`
`this proceeding. Nor is there a need to somehow measure the claims against some
`
`deployed embodiment – Petitioner relies only on three prior art references which are
`
`patent publications contemporaneous with the filing of the ‘526 Patent in 2003.
`
`PO respectfully submits that the construction is offered here, as a means to
`
`characterize the claims in co-pending litigation. No claim construction effort is
`
`appropriate here, because Petitioner tells us that no matter how the claim is
`
`construed, the claims are obvious. Such a pretext for claim construction is improper.
`
`Nonetheless, because that litigation IS co-pending, and because the ‘526 Patent has
`
`been licensed in a royalty-based environment, PO respectfully submits that a
`
`Preliminary Response in this matter properly includes a claim construction arrived at
`
`pursuant to precedent, which requires consideration of the inventor’s intent, as
`
`framed by the specification.
`
`Thereafter, PO turns in this Preliminary Response to the asserted grounds of
`
`obviousness. Petitioner argues that Claims 1–3, 5–11 and 13–20 of the ‘526 Patent
`
`would have been obvious to one of skill in the art to which it is directed prior to
`
`December 4, 2003, given U.S. Patent No. 6,735,623, (hereinafter “Prust”) read in
`
`view of WO 02/052785, (hereinafter “Major”). Petitioner further argues that wholly
`
`
`
`
`
` 4
`
`

`

`
`
`
`
`independent of that first argument, the same individual of skill in the art would have
`
`found all claims of the ‘526 Patent to be obvious, prior to December 4, 2003, given
`
`U.S. Patent No. 8,117,644, (hereinafter “Chaganti”), again read in view of Major.
`
`Accordingly, this Preliminary Response establishes the proper construction of
`
`the claims, and then turns to the combination of Prust taken in view of Major.
`
`Thereafter, the asserted unpatentability of all Claims of the ‘526 Patent as obvious
`
`over Chaganti in view of Major is discussed. The discussion demonstrates that
`
`neither Prust taken in view of Major nor Chaganti taken in view of Major describes
`
`and enables the subject matter of the ‘526 Patent. In the absence of both description
`
`and enablement of the challenged claims by the prior art, the claims cannot be
`
`unpatentable. This is as true of the asserted grounds of obviousness as it is of
`
`anticipation, In re Morsa, 803 F. 3d 1374, 1377 (Fed. Cir. 2015) (“Enablement of
`
`prior art requires that the reference teach a skilled artisan—at the time of filing—to
`
`make or carry out what it discloses in relation to the claimed invention without undue
`
`experimentation.”).
`
`Throughout this response, PO relies on the Declaration of Jawadi, Exhibit
`
`2001 hereto. While the level and understanding of those of skill in the art as
`
`described by Petitioner’s Expert Long, Ex. 1004, ¶¶ 46–64 is not specifically at issue,
`
`the conclusions drawn by the two experts are diametrically opposed – in part because
`
`Long relies on practices, such as “Copy-and-Paste” that are not reflected in, and do
`
`
`
`
`
` 5
`
`

`

`not properly characterize, the prior art relied upon. Jawadi relies on Exhibits 2002 –
`
`2006, including his own curricula vitae, as Exhibit 2002, and short prior art
`
`compendia and dictionaries, Ex. 2003–2006, relied upon to show what those of skill
`
`in the art would have understood as of December 2003.
`
`
`
`
`
`
`
`
`
`
`
`
`
` 6
`
`

`

`
`
`
`
`II.
`
`
`PROPERLY CONSTRUED, THE CLAIMS REQUIRE BOTH
`STORING AND RETRIEVAL OF A DATA OBJECT
`
`
`
`
`A. Petitioner’s Requested Construction Is Improper
`
`The Petition, as filed, in this matter begins with a request to engage in a claim
`
`construction of all claims. Petition, p. 7. Petitioner asserts that such a construction
`
`may be beneficial “as it may simplify the issues in dispute if Patent Owner argues
`
`patentability based on an alternative claim limitation.” Id. With respect, the nature
`
`of the basis for the request is not clear. Petitioner’s burden is to come forward with a
`
`basis for supporting its challenge based on ALL limitations of the claim. Petitioner
`
`does not tell us what “alternative claim limitations” it is referring to. None are
`
`apparent. Indeed, Petitioner tells us that the claim construction does not matter - all
`
`claims are obvious whether Petitioner’s construction is adopted or not.
`
`With respect, this is not the forum for unnecessary exercises in claim
`
`construction. If the outcome of the construction does not matter, then no claim
`
`construction should be engaged in. Power Integrations, Inc. v. Semiconductor
`
`Components Industries, LLC, 926 F.3d 1306, 1318 (Fed. Cir. 2019). Indeed a
`
`specific goal and intention of the IPR provisions is to “limit unnecessary and
`
`counterproductive litigation costs.” Regents of the University of Minnesota v. LSI
`
`Corporation, 926 F.3d 1327, 1335 (Fed. Cir. 2019). Respectfully, PO submits that
`
`where Petitioner seeks a claim construction exercise that it insists cannot matter in
`
`
`
`
`
` 7
`
`

`

`
`
`
`
`the determination of the patentability of the claims challenged, and can forward no
`
`concrete basis for asking the Board and the parties to engage in such a claim
`
`construction exercise – no claim construction is warranted. Respectfully, PO submits
`
`the “outcome neutral” claim construction Petitioner asks this Board to engage in has
`
`nothing to do with the positions adopted by Petitioner in this matter – it has to do
`
`with the co-pending litigation. Petitioner is taking an extra opportunity to advance a
`
`position that cannot matter in the IPR, but might well impact the parties in a co-
`
`pending litigation - an exercise not contemplated as a proper one in this IPR.
`
`Even so, it might be possible to accommodate the request and adopt the
`
`“outcome neutral” claim construction advanced by Petitioner. The construction
`
`advanced, however, is contrary to statute and regulation, and flies in the face of
`
`precedent that calls for claim construction to be based on the clear intent of the
`
`inventor where set forth in the specification. Petitioner, and Petitioner’s expert Long,
`
`neither consider nor explain that specification, nor attempt to correlate the proposed
`
`construction with the explanation of precisely what the inventor regarded as his
`
`invention – which is set forth clearly in the ‘526 Patent specification. Making matters
`
`worse, Petitioner violates a basic rule of claim construction in arriving at its proposed
`
`construction. For these reasons, PO rejects the proposed construction, below, before
`
`proceeding to the asserted grounds of invalidity.
`
`
`
`
`
`
`
`
`
` 8
`
`

`

`
`
`
`
`
`
`B. The Proposed Construction is Contrary to the Specification
`
`Petitioner’s proposed claim construction revolves around a single phrase
`
`present in both independent claims of the ‘526 Patent. No other basis for construction
`
`is offered. Both independent Claim 1 and independent Claim 11 of the ‘526 Patent
`
`recite, inter alia, a critical step of remotely accessing the storage space featured in the
`
`claims. Those claims recite this step comprises:
`
`storing a data object (in the storage space) or retrieving a data
`object therefrom
`
`
`
`
`
`Petitioner construes this claim limitation, which defines the critical interaction
`
`between the user of the wireless device such as a handheld phone, the individual who
`
`benefits from the invention, to mean that the claim is satisfied by A) storing a data
`
`object in a remote serve or B) retrieving a data object from the remote server.
`
`Petition at pp. 6–8. To characterize the invention of the ‘526 Patent as one which
`
`might allow one to store data in a remote server – but NOT retrieve it for use ignores
`
`the entire point of the invention as set forth at Col. 5, ll., 33–37 which provides that a
`
`user can:
`
` Retrieve and play multimedia file data file such as video or music
`stored in the assigned storage volume (11) located on the server.
`
`
`
`
`
`
` 9
`
`

`

`
`
`
`
`In a related embodiment also embraced by the claims of the ‘526 Patent set
`
`forth at Col. 5, ll. 40-41, the invention is intended to permit the user to:
`
`Retrieve data file from the file system of the assigned storage volume
`(11) on the server (3).
`
`
`
`If one accepts the construction urged by Petitioner, the result is an invention
`
`that does not provide for a cardinal feature of the invention –accessing and enjoying
`
`the downloaded data stored on a remote server. Petitioner’s “either this or that”
`
`approach to construction also permits a construction that characterizes the invention
`
`as not embracing the ability “to download a data from a remote web server (15) into
`
`the file system on the assigned storage volume (11) in the external storage system
`
`(10) on the server (3).” ‘526 Patent, Col. 5, ll. 3–6. Thus, Petitioner argues, one of
`
`skill in the art would have read and understood the disclosure of the ‘526 Patent to
`
`construe the claims thereof to be limited to either downloading information to a
`
`server or retrieving data from a server, but not both.
`
`It’s easy to see the inventor wrote the disclosure as embracing and calling for
`
`both downloading (storing) and accessing (retrieving) information of interest. Were it
`
`not so, the expressed aim of the invention – to provide for increased storage of data
`
`on a remote server instead of the wireless device itself, and provide for the smooth
`
`retrieval of that data – would be otherwise. This is the description of the invention set
`
`forth in the specification of the ‘526 Patent at Col. 5, ll. 1–41. Unquestionably, it was
`
`
`
`
`
` 10
`
`

`

`
`
`
`
`the “intention of the inventor …to claim a system that would do both storing AND
`
`retrieving.” Ex. 2001, ¶145.
`
`How is it possible for two experts in the art to come away with such different
`
`understanding of what the claims of the ‘526 Patent call for? The answer lies in the
`
`tiny word “or”. Petitioner, and the Expert Declaration Petitioner relies on, Exhibit
`
`1004, do not actually construe the specific language of Claim 1 or Claim 11 of the
`
`‘526 Patent. Rather, Petitioner construes or defines the word “or.” Petitioner’s
`
`argument seeks to rely solely on the word “OR” to arrive at the conclusion that the
`
`claims of the ‘526 Patent are met by providing for one of the two options – storing,
`
`accessing – but not both. See the Petition, p. 7:
`
`The plain and ordinary meaning of “comprising A or B” is that A and B
`are alternatives. Ex – 1004, ¶41.
`
`With respect, it was not truly necessary to turn to an expert to get a dictionary
`
`definition of the word OR considered in isolation. Such consideration, however, is
`
`not how claims are to be construed. The Federal Circuit had recent opportunity to
`
`address the importance of considering the specification and the clear intention of the
`
`inventor. Techtronic Industries Co. Ltd. v. International Trade Commission 2019 WL
`
`6753355 *4 - 6 (Fed. Cir. Dec. 12, 2019):
`
`
`
`
`
`
`
`
`
`We agree with the Appellants that Chamberlain disavowed coverage of wall
`consoles without a passive infrared detector. Claim terms are normally
`given their ordinary and customary meaning, as understood by persons of
`ordinary skill in the art in view of the specification and prosecution history.
`Phillips v. AWH Corp., 415 F.3d 1303, 1313 (Fed. Cir. 2005) (en banc). But
`
`
`
` 11
`
`

`

`
`
`
`
`where the inventor has clearly set forth a different definition of a claim
`
`term, or has manifested that the invention does or does not include a
`
`particular aspect, that intention “is regarded as dispositive.” Id. at 1316
`
`(citing SciMed Life Sys., Inc. v. Adv. Cardiovascular Sys., Inc., 242 F.3d
`
`1337, 1343–44 (Fed. Cir. 2001)). In the latter circumstance, the inventor has
`
`“disavowed” claim scope. A disavowal must be clear, but it need not be
`
`explicit. See Trs. Of Columbia Univ. v. Symantec Corp., 811 F.3d 1359,
`
`1363 (Fed. Cir. 2016). Disavowal “may be inferred from clear limiting
`
`descriptions of the invention in the specification or prosecution history.”
`
`Aventis Pharma S.A. v. Hospira, Inc., 675 F.3d 1324, 1330 (Fed. Cir. 2012);
`
`see also Blackbird Tech LLC v. ELB Elecs., Inc., 895 F.3d 1374, 1377–78
`
`(Fed. Cir. 2018) (collecting cases and finding no disavowal where the
`
`specification did not teach that the feature in question was “important,
`
`essential, or critical to the invention”). An inventor may also disavow claim
`
`scope “by distinguishing the claimed invention over the prior art.” Ekchian
`
`v. Home Depot, Inc., 104 F.3d 1299, 1304 (Fed. Cir. 1997). Ultimately, as
`
`this court held in Phillips, the purpose of claim construction is to
`
`“capture the scope of the actual invention,” and whether “the embodiments .
`
`. . define the outer limits of the claim term,” or are “merely . . . exemplary in
`
`nature,” is a question that must be determined “in the context of the
`
`particular patent.” 415 F.3d at 1323–24…. We disagree with the
`
`Commission. While “mere criticism” of a particular embodiment will not
`
`always rise to the level of disavowal, depending on the rest of the intrinsic
`
`record, see Thorner v. Sony Computer Entm’t Am. LLC, 669 F.3d 1362,
`
`1366–68 (Fed. Cir. 2012), we must construe claims “in the light of the
`
`specifications and . . . with a view to ascertaining the invention.” United
`
`States v. Adams, 383 U.S. 39, 49 (1966) (collecting cases). Where, as here,
`
`the specification plainly represents the scope of the invention to the
`
`exclusion of some embodiments, it is unnecessary that it also concede that
`
`those embodiments are “infeasible” or even “impossible” by reference to its
`
`teachings. See Trs. of Columbia Univ., 811 F.3d at 1363–64 (rejecting
`
`a requirement of “express[]” disavowal (citing Phillips, 415 F.3d at
`
`1320–21)). Indeed, it is difficult to imagine a situation in which the
`
`Commission’s standard for disavowal would be satisfied. Here, the entire
`
`specification focuses on enabling placement of the passive infrared
`
`detector in the wall console, which is both responsive to the prior art
`
`deficiency the ’319 patent identifies and repeatedly set forth as the
`
`objective of the invention. Thus, the ’319 patent disavows locating the
`
`detector elsewhere, even without an express concession to that effect.
`
`(emphasis supplied).
`
`
`
`
`
` 12
`
`

`

`
`
`
`
`
`
`As was the case in Techtronics, the entire specification of the ‘526 Patent
`
`focuses on single task, providing a smooth system which enhances storage
`
`capacity of a user of a wireless device by providing for streamlined ability to
`
`download, store AND retrieve data objects to and from that storage space.
`
`Nowhere does the ‘526 Patent suggest or consider the invention may be satisfied
`
`by simply storing information but not retrieving it, or only retrieving but not
`
`storing information. PO submits the specification of the ‘526 Patent makes it clear
`
`– the patent claims are directed to a system which provides for both downloading
`
`and retrieving. PO notes, in this respect, that neither the Petition nor the
`
`Declaration that is Ex. 1004 so much as considers the intent of the inventor as
`
`expressed in the specification. See the Petition, pp. 6 – 7 and Ex. 1004, ¶¶ 41–42.
`
`C. The Proposed Construction Violates a Central Tenet of Claim
`Construction
`
`
`
`
`
`
`
`
`
`Claims 1 and 11 of the ‘526 Patent both specifically recite as a claim
`
`
`
`limitation “the storing of a/the data object including to download a file from a
`
`remote server across/on a network into the assigned storage space.” Thus, all
`
`claims of the ‘526 Patent specifically require storing. Accordingly, including the
`
`storing OR retrieving feature as construed by Petitioner would be superfluous.
`
`Specifically, if storing is required as shown above, interpreting the disputed phrase
`
`to provide for OR retrieving would render it superfluous and unnecessary. Ex.
`
`
`
`
`
` 13
`
`

`

`2001, ¶146. A claim construction that renders a phrase of a claim superfluous is
`
`
`
`
`
`improper and suspect. Twilio Inc. v. TeleSign Corp., 2016 WL 5027521 *1 (PTAB)
`
`observing Federal Circuit precedent that follows this simple but clear rule:
`
` See Merck & Co., Inc. v. Teva Pharmaceuticals USA, Inc., 395 F.3d 1364,
`1372 (Fed. Cir.2005 (rejecting a proposed claim construction that would
`render claim terms superfluous); Elekta Instrument S.A. v. O.U.R. Sci. Int'l,
`Inc., 214 F.3d 1302, 1307 (Fed.Cir.2000) (construing claim to avoid
`rendering the 30 degree claim limitation superfluous); Gen. Am. Transp.
`Corp. v. Cryo–Trans, Inc., 93 F.3d 766, 770 (Fed.Cir.1996) (rejecting the
`district court's claim construction because it rendered superfluous the claim
`requirement for openings adjacent to the end walls).
`
`
`
`
`
`
`
`
`
`
`
`Petitioner nowhere considers the impact of its proposed construction that the
`
`claims of the ‘526 Patent call for only storing or retrieving as to the remaining
`
`recitations of the claim. Yet, claims are considered as a whole – either the claim is
`
`construed and, on construction, it is obvious, or the claim as construed is not
`
`obvious. Vtech Communications, Inc. v. Spherix, Inc. 2015 WL 981678 *4
`
`(PTAB) rejecting a proposed construction that rendered a phrase in an independent
`
`claim superfluous on the grounds that “it is well-settled that “claims are interpreted
`
`with an eye toward giving effect to all terms in the claim.” See, Bicon Inc. v.
`
`Straumann Co., 441 F.3d 945, 950 (Fed. Cir. 2006).
`
`Petitioner’s own argument asserts that claim construction is unnecessary –
`
`that the claims are obvious no matter what construction is adopted. Petitioner
`
`offers absolutely no possible dispute that might be short-circuited by an early and
`
`
`
`
`
` 14
`
`

`

`
`
`
`
`unnecessary claim construction. Petitioner’s claim construction nowhere refers to
`
`the specification or file history, or somehow demonstrates that its construction is
`
`consistent with the inventor’s avowed intent – an intent that is clear from the
`
`specification. The proposed construction is not only contrary to the clear intent of
`
`the inventor as set forth in the specification of the ‘526 Patent, it is contrary to a
`
`very specific rule or tenet of claim construction which precludes a claim
`
`construction which renders a phrase in a claim so construed superfluous.
`
`Petitioner's argument should be rejected – the clear intent of the inventor, as
`
`expressed in the specification, is that the claim phrase “Comprises storing a data
`
`object (in the storage space) or retrieving a data object therefrom” should be
`
`construed to require both ‘storing a data object and retrieving a data object’ in/from
`
`the storage space.
`
`III. PRUST, AS MODIFIED BY MAJOR, DOES NOT TEACH CRITICAL
`FEATURES OF THE CHALLENGED CLAIMS
`
`
`
`
`
`It is well settled that to establish that one or more claims are obvious,
`
`
`
`
`
`Petitioner must demonstrate that the claims, considered as a whole, are wholly taught
`
`by the references relied upon – each recitation of the claim must be taught by the
`
`combination of references. Petitioner relies on U.S. Patent No. 6,735,623 (hereinafter
`
`“Prust”), Ex. 1006, taken in view of WO 02/052785, (hereinafter “Major”), Ex. 1007
`
`as teaching all the features of challenged Claims 1 – 3, 5 – 11 and 13 – 20 as obvious.
`
`As is made more evident below, this combination of references does not teach all the
`
`
`
`
`
` 15
`
`

`

`
`
`
`
`recited features of the challenged claims, and so cannot establish the challenged
`
`claims are obvious – no limitation can be overlooked. One must consider all claim
`
`limitations together to determine whether a claimed invention is obvious. Ex parte
`
`Richardson, 2004 WL 7730 *2 (PTAB 2009) citing In re Geerdes,491 F2d. 1260,
`
`1262 – 1263 (CCPA 1974) for the proposition “[E]very limitation in the claim must
`
`be given effect rather than considering one in isolation from the others.” (Emphasis
`
`in original). Petitioner’s showing fails this test.
`
`Neither Prust, nor Major, nor their combination teaches the requirement of
`
`every challenged claim that downloading a data file into the assigned storage space
`
`be achieved “through utilizing download information for the file stored in (the)
`
`cache.” The use of “copy-and-paste” operations using the web-cache relied upon by
`
`Petitioner beginning at page 10 of the Petition is not in fact taught by the combination
`
`of references relied upon, and would not be recognized by a person of ordinary skill
`
`in the art (POSITA). In fact – the use of “copy-and-paste”, although relied upon
`
`exclusively by Petitioner to satisfy this element of the claim is not recited or taught
`
`by the ‘526 Patent, not shown or enabled by Prust, and not taught by Major.
`
`PO notes, in this respect, that it is Petitioner that urges that a proper
`
`understanding of the term “download information” is that such a data object is a
`
`URL. Petition, p. 4, Ex. 1004, ¶31, Ex. 2001, ¶31. PO does not necessarily agree with
`
`that definition, nor is it bound by Petitioner’s argument. Since, adopting Petitioners
`
`
`
`
`
` 16
`
`

`

`
`
`
`characterization demonstrates nonetheless the claims are not obvious over the art, PO
`
`discusses it herein.
`
`A second limitation that must be taught by the combination of Prust and Major
`
`to render all challenged claims of the ‘526 Patent obvious is the express requirement
`
`of all challenged claims that the storage space provided be “of a predefined capacity
`
`assigned exclusively to a user of the wireless device by a storage server.” Neither
`
`Prust nor Major teaches that storage capacity in a server be of a defined size set by
`
`the server before storage is allocated to the users. Again, this requirement is an
`
`essential and recited characteristic of the claims. Whether the combination of Prust
`
`and Major, given the knowle

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