throbber
Case IPR2022-00545
`Patent 9,689,161
`
`
`
`
`
`UNITED STATES PATENT AND TRADEMARK OFFICE
`
`
`
`
`
`
`BEFORE THE PATENT TRIAL AND APPEAL BOARD
`
`
`
`
`
`
`CHANEL, INC.,
`Petitioner,
`
`v.
`MOLO DESIGN, LTD.,
`Patent Owner.
`
`
`
`Case IPR2022-00545
`Patent 9,689,161
`
`
`
`PATENT OWNER’S PRELIMINARY RESPONSE
`UNDER 37 C.F.R. § 42.107(a)
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`

`

`Case IPR2022-00545
`Patent 9,689,161
`
`
`
`
`2. 
`3. 
`
`TABLE OF CONTENTS
`INTRODUCTION ........................................................................................... 1 
`I. 
`BACKGROUND OF RELATED LITIGATION ............................................ 2 
`II. 
`III.  THE PETITION SHOULD BE DENIED BECAUSE PETITIONER
`FAILS TO IDENTIFY THE GROUNDS FOR ITS CHALLENGE
`WITH SUFFICIENT PARTICULARITY ...................................................... 5 
`IV.  THE PETITION SHOULD BE DENIED BECAUSE PETITIONER
`HAS NOT MET ITS BURDEN TO ESTABLISH HOW THE
`CLAIMS SHOULD BE CONSTRUED ........................................................ 12 
`Petitioner’s Advancement of Claim Construction Positions That
`A. 
`It Contends are Legally Erroneous Fails to Meet its Burden .............. 12 
`Petitioner’s Inconsistent and Conflicting Positions For
`1. 
`“supports” and “self-supporting” .............................................. 13 
`Petitioner’s Inconsistent Construction for “flaccid” ................. 15 
`Petitioner’s Bases for Alleging Inconsistent Positions
`Have No Merit .......................................................................... 17 
`Petitioner’s Failure to Identify Its Inconsistent Claim
`Constructions is a Breach of the Duty of Candor ............................... 20 
`THE BOARD SHOULD DENY INSTITUTION BECAUSE THE
`PETITION HAS NOT SHOWN A REASONABLE LIKELIHOOD
`OF SUCCESS IN VIEW OF THE SOFTHOUSING REFERENCES ......... 23 
`A.  Overview of the SoftHousing and SoftWall References ...................... 23 
`1. 
`SoftHousing I (Exh. 1005) ........................................................ 23 
`2. 
`SoftHousing II (Exh. 1006) ....................................................... 25 
`3. 
`SoftHousing III (Exh. 1007) ...................................................... 27 
`
`B. 
`
`V. 
`
`
`
`i
`
`

`

`Case IPR2022-00545
`Patent 9,689,161
`
`
`
`B. 
`
`SoftWall (Exh. 1028) ................................................................. 27 
`4. 
`The Subject Matter of Each SoftHousing Reference and the
`SoftWall Reference Was Not Only Before the Examiner, but
`Does Not Disclose the Claimed Inventions ........................................ 28 
`C.  MacAllen 2008 Does Not Teach or Describe the Claimed
`Inventions ............................................................................................ 38 
`VI.  CONCLUSION .............................................................................................. 39 
`
`
`
`
`
`
`ii
`
`

`

`Case IPR2022-00545
`Patent 9,689,161
`
`
`
`TABLE OF AUTHORITIES
`
` Page(s)
`
`Cases
`Adaptics Ltd. v. Perfect Co.,
`IPR2018-01596, Paper No. 20 (PTAB Mar. 6, 2019) .................................... 6, 10
`Amgen Inc. v. Hoechst Marion Roussel, Inc.,
`314 F.3d 1313 (Fed. Cir. 2003) .................................................................... 17, 20
`Edwards LifeSciences Corp. v. Boston Scientific Scimed, Inc.,
`IPR2017-01304, Paper No. 8 (PTAB Oct. 25, 2017) ......................................... 11
`EnergySource Minerals, LLC v. TerraLithium LLC,
`IPR2019-01606, Paper No. 7 (PTAB May 4, 2020) ...................................... 6, 10
`Enzo Biochem, Inc. v. Applera Corp.,
`599 F.3d 1325 (Fed. Cir. 2010) .......................................................................... 16
`Epsilon Data Mgmt., LLC v. Umbanet, Inc.,
`IPR2017-01743, Paper No. 20 (PTAB Apr. 30, 2018) ....................................... 20
`Facebook, Inc. v. Sound View Innovations, LLC,
`IPR2017-00998 .................................................................... 15, 16, 18, 20, 21, 23
`Harmonic Inc. v. Avid Tech., Inc.,
`815 F.3d 1356 (Fed. Cir. 2016) ............................................................................ 5
`Hunting Titan, Inc. v. DynaEnergetics Europe GmbH,
`PGR2020-00080, Paper No. 7 (PTAB Feb. 12, 2021) ............................... 6, 7, 10
`Intelligent Bio-Sys., Inc. v. Illumina Cambridge Ltd.,
`821 F.3d 1359 (Fed. Cir. 2016) ............................................................................ 5
`InVue Security Prods., Inc. v. Mobile Tech., Inc.,
`IPR2019-00078, Paper No. 7 (PTAB May 1, 2019) .................................... 10, 11
`ipDataTel, LLC et al. v. ICN Acquisition,
`IPR2018-01822, Paper No. 19 (PTAB Apr. 22, 2019) ..................... 15, 16, 18, 21
`
`iii
`
`

`

`Case IPR2022-00545
`Patent 9,689,161
`
`
`Kiosoft Techs., LLC v. PayRange, Inc.,
`IPR2021-00086, Paper No. 12 (PTAB March 22, 2021) .... 15, 16, 17, 18, 20, 21
`
`L & P Property Mgmt. Co. v. Remacro Mach. & Tech. (Wujiang) Co.,
`Ltd.,
`IPR2019-00255, Paper No. 15 (PTAB June 18, 2019) ...................................... 20
`Neil Ziegmann, N.P.Z., Inc. v. Stephens,
`IPR2015-01860, Paper No. 13 (PTAB Sept. 6, 2017) .................................. 33, 34
`OrthoPediatrics Corp. v. K2M, Inc.,
`IPR2018-01546, Paper No. 10 (PTAB Feb. 14, 2019) ..................... 14, 16, 18, 21
`Samsung Elecs. Am., Inc. v. Prisua Eng’g Corp.,
`948 F.3d 1342 (Fed. Cir. 2020) .......................................................................... 16
`Statutes
`35 U.S.C. § 312(a)(3) ........................................................................................... 5, 10
`Regulations
`37 C.F.R. § 42.51 (b)(iii) ......................................................................................... 20
`37 C.F.R. § 42.104(b)(3) ........................................................... 12, 13, 16, 19, 21, 22
`77 Fed. Reg. 48,756, 48,763 (Aug. 14, 2012) ........................................................... 6
`
`
`
`
`
`
`
`
`
`
`iv
`
`

`

`Case IPR2022-00545
`Patent 9,689,161
`
`LIST OF EXHIBITS
`
`Joint Disputed Claim TermsChart, filed in Molo Design Ltd.v.
`Chanel, Inc., No 21-cv-1578 (S.D.N.Y.), dated September 24, 2021
`Dkt. No. 38
`Defendant Chanel, Inc.’s Claim Construction Brief, filed in Molo
`Design Ltd. v. Chanel, Inc., No 21-cv-1578 (S.D.N.Y.), dated
`November30, 2021 (Dkt. No. 43
`2003‘|Plaintiff Molo Design Ltd.’s Notice Regarding Chanel’s Supplement
`Claim Construction Positions, filed in Molo Design Ltd. v. Chanel,
`Inc., No 21-cv-1578 (S.D.N.Y.), dated February 18, 2022 (Dkt. No.
`51
`2004|Chanel’s Response to Molo’s Supplemental Claim Construction
`Statement, filed in Molo Design Ltd. v. Chanel, Inc., No 21-cv-1578
`S.D.N.Y.), dated February
`25, 2022 (Dkt. No. 54
`2005|Pedersen, Martin C, “The Soft House,” Metropolis Magazine(Jul.
`2004
`2006|Affidavit of Stephanie Forsythe
`2007|Affidavit of Todd MacAllen
`2008|U.S. Patent No. 7,866,366
`
`
`
`2001
`
`2002
`
`
`
`

`

`Case IPR2022-00545
`Patent 9,689,161
`
`
`I.
`
`INTRODUCTION
`The Petition for inter partes review of claims 1-10, 12, 14, 18, 19-25, and 27
`
`of U.S. Patent No. 9,689,161 (“the ’161 patent”), which is owned by Molo Design,
`
`Ltd. (“Molo” or “Patent Owner” or “Applicant”) should be denied in its entirety for
`
`multiple reasons.
`
`First, Petitioner Chanel, Inc. (“Petitioner” or “Chanel”) advances claim
`
`construction arguments that—at least according to Petitioner’s own representations
`
`to the district court—would constitute reversible legal error if adopted by the Board.
`
`In doing so, Petitioner fails to meet its statutory burden to demonstrate how the claim
`
`terms should be construed and applied to the cited art. Even more significantly,
`
`Petitioner has breached its duty of candor by concealing from the Board the fact that
`
`it has taken conflicting and irreconcilable claim constructions positions in the related
`
`district court proceeding.
`
`Second, although Petitioner purports to present five distinct grounds,
`
`including three obviousness grounds, these grounds are not delineated with the
`
`required particularity that would enable Patent Owner to effectively respond to
`
`Petitioner’s arguments. Instead, in each of its alleged obviousness grounds,
`
`Petitioner attempts to connect numerous different references using the conjunction
`
`“and/or,” resulting in at least 65 distinct obviousness combinations, in addition to
`
`other grounds allegedly based on anticipation. As this Board’s decisions confirm,
`1
`
`
`
`

`

`Case IPR2022-00545
`Patent 9,689,161
`
`
`such tactics are abusive, fail to establish the basis for Petitioner’s arguments with
`
`particularity, and are nothing short of an attempt to improperly shift Petitioner’s
`
`burden to Patent Owner.
`
`Third, to the extent that Patent Owner can discern the grounds relied on by the
`
`Petitioner, none of the references cited by Petitioner disclose, teach, or suggest the
`
`required elements of the challenged claims, either alone or in combination. Indeed,
`
`several the references are duplicative of references that were before the Office during
`
`prosecution of the ’161 patent, and Petitioner fails to identify how the examiner erred
`
`in his consideration of those references. Nor do the references teach or suggest
`
`critical elements of the challenged claims. As such, the Petition fails to demonstrate
`
`a reasonable likelihood of success on any ground.
`
`Any one of these issues—taken alone—merits denial of the Petition. When
`
`considered together, they strongly advise against instituting the IPR Petition.
`
`II. BACKGROUND OF RELATED LITIGATION
`
`On February 22, 2021, Patent Owner sued Petitioner in the Southern District
`
`of New York, alleging infringement of the ’161 patent as well as three related patents
`
`that are the subject of concurrently-filed IPR petitions. At or around the same time
`
`it filed suit in New York, Patent owner also initiated actions addressing Petitioner’s
`
`and its affiliates’ infringement of Patent Owner’s intellectual property rights in
`
`several other countries, including France, Germany, Italy, Canada, and Taiwan.
`
`2
`
`

`

`Case IPR2022-00545
`Patent 9,689,161
`
`
`
`
`In the ensuing year since Patent Owner initiated these actions, the parties have
`
`engaged in significant discovery efforts, including: searching for and producing
`
`large numbers of documents; propounding and responding to multiple sets of written
`
`discovery; conducting multiple meet-and-confers regarding discovery; and
`
`preparing and serving both infringing and invalidity contentions. The parties also
`
`completed the entire claim construction identification and briefing process pursuant
`
`to the district court’s Scheduling Order and the Southern District of New York’s
`
`Local Patent Rules.
`
`
`
`On February 4, 2022, only a few weeks before its statutory bar date, Petitioner
`
`filed this Petition, together with the following IPR petitions for three related patents
`
`that are also being asserted in the district court case:
`
` IPR2022-00543, which challenges claims in U.S. Patent No. 7,866,366;
`
` IPR2022-00544, which challenges claims in U.S. Patent No. 8,561,666;
`
`and
`
` IPR2022-00546, which challenges claims in U.S. Patent No. 9,797,134.
`
`3
`
`

`

`Case IPR2022-00545
`Patent 9,689,161
`
`
`On the same day, Petitioner also filed a motion to stay the district court proceeding
`
`in view of the IPR petitions.1
`
`Notwithstanding the fact that the Board and the district court use the same
`
`claim construction standard, Petitioner now advances vastly different claim
`
`construction positions than it advances in the district court proceeding. For instance,
`
`in the district court proceeding, Petitioner alleges that several terms in the challenged
`
`claims of the ’161 patent must be explicitly construed. Petitioner also alleges that
`
`failure to construe these terms would be both “improper” and invite “legal error,”
`
`suggesting that any decision not to construe these terms would be subject to reversal
`
`on appeal. In stark contrast to its representations to the district court, however, here
`
`Petitioner alleges that the Board need not construe any terms at all.
`
`Petitioner’s irreconcilable positions are further underscored by its position in
`
`district court that certain terms are indefinite. For example, in the district court
`
`proceeding, Petitioner contends that the term “flaccid”—which is recited in claim 10
`
`of the ’161 patent—is indefinite and cannot be readily understood by a person of
`
`
`1 On May 2, 2022, the Court stayed the district court litigation until the Board
`
`decides whether institute Petitioner’s IPR petitions.
`
`
`
`4
`
`

`

`Case IPR2022-00545
`Patent 9,689,161
`
`
`ordinary skill. But the Petition takes the opposite stance, alleging that whether a
`
`structure was made from “flaccid” material would have been so readily apparent that
`
`it need not even be construed by the Board.
`
`
`
`In the time since the Petition was filed, Petitioner has also opposed efforts to
`
`reconcile or unify its conflicting position in the different proceedings. Shortly after
`
`the Petition was filed, Patent Owner expressly raised its concerns regarding
`
`Petitioner’s inconsistent positions before the district court. But Petitioner stood fast
`
`on its conflicting positions, taking the remarkable position that its claim construction
`
`position in one proceeding “has no bearing” on its inconsistent position in the other
`
`proceeding. Even more troubling, Petitioner has made no attempt to apprise the
`
`Board of its conflicting positions and representations, despite its duty to do so.
`
`Instead, Petitioner has left Patent Owner to address the issue in this Preliminary
`
`Response.
`
`III. THE PETITION SHOULD BE DENIED BECAUSE PETITIONER
`FAILS TO IDENTIFY THE GROUNDS FOR ITS CHALLENGE WITH
`SUFFICIENT PARTICULARITY
`“In an IPR, the petitioner has the burden from the onset to show with
`
`particularity why the patent it challenges is unpatentable.” Harmonic Inc. v. Avid
`
`Tech., Inc., 815 F.3d 1356, 1363 (Fed. Cir. 2016) (citing 35 U.S.C. § 312(a)(3)). “It
`
`is of the utmost importance that petitioners in the IPR proceedings adhere to [this]
`
`requirement.” Intelligent Bio-Sys., Inc. v. Illumina Cambridge Ltd., 821 F.3d 1359,
`
`5
`
`

`

`Case IPR2022-00545
`Patent 9,689,161
`
`
`1369 (Fed. Cir. 2016). Accordingly, a petitioner should not submit “a repository of
`
`all the information that a judge could possibly consider, and instead focus on
`
`concise, well-organized, easy-to-follow arguments.” EnergySource Minerals, LLC
`
`v. TerraLithium LLC, IPR2019-01606, Paper No. 7 at 20-21 (PTAB May 4, 2020)
`
`(citing Office Patent Trial Practice Guide, 77 Fed. Reg. 48,756, 48,763 (Aug. 14,
`
`2012)).
`
`In keeping with this requirement, the Board has repeatedly explained that the
`
`use of “and/or” as a “catch all” to combine numerous different references results in
`
`grounds that are “not reasonably bounded in scope and [are] unduly burdensome for
`
`both the Board and Patent Owner to address.” Energy Source, IPR2019-01606,
`
`Paper No. 7 at 22; Hunting Titan, Inc. v. DynaEnergetics Europe GmbH, PGR2020-
`
`00080, Paper No. 7 at 10 (PTAB Feb. 12, 2021) (finding that this style “lack[s]
`
`particularity as voluminous, excessive, and burdensome”); Adaptics Ltd. v. Perfect
`
`Co., IPR2018-01596, Paper No. 20 at 18-19 (PTAB Mar. 6, 2019) (same).2 It also
`
`
`2 Indeed, because “and/or” “is a grammatical conjunction used to indicate that one
`
`or more of the cases it connects may occur,” it “has been criticized as ‘[a] device,
`
`or shortcut, that damages a sentence and often leads to confusion or ambiguity.”
`
`Adaptics, IPR2018-01596, Paper No. 20 at 18, n.13.
`
`6
`
`

`

`Case IPR2022-00545
`Patent 9,689,161
`
`
`gives rise to the “presentation of grounds that are uncertain and ill-defined.” Hunting
`
`Titan, PGR2020-00080, Paper No. 7 at 9.
`
`In this case, Petitioner has done precisely what this Board’s rules do not allow.
`
`While the Petition purports to identify five grounds on which the challenge is based,
`
`multiple grounds are based on combining a multiplicity of different references using
`
`the conjunction “and/or” as illustrated below:
`
`See Petition (“Pet.”) at 7.
`
`Thus, for example, Ground 4 alone involves at least 25 different
`
`combinations:
`
`
`
`7
`
`

`

`Case IPR2022-00545
`Patent 9,689,161
`
`
`
`
`
`SoftWall3
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`SoftWall + SoftHousing I
`
`SoftWall + SoftHousing II
`
`SoftWall + SoftHousing III
`
`SoftWall + Arens
`
`SoftWall + Okuno
`
`SoftWall + SoftHousing I + SoftHousing II
`
`SoftWall + SoftHousing I + SoftHousing III
`
`SoftWall + SoftHousing I + Arens
`
`SoftWall + SoftHousing I + Okuno
`
`SoftWall + SoftHousing II + SoftHousing III
`
`SoftWall + SoftHousing II + Arens
`
`SoftWall + SoftHousing II + Okuno
`
`SoftWall + SoftHousing III + Arens
`
`
`3 Under Petitioner’s theory, SoftWall alone would qualify as one combination as
`
`Petitioner alleges that this reference “alone in view of the knowledge of a POSITA”
`
`would render the claims obvious. Pet. at 51. Petitioner makes the same allegation
`
`for the main reference cited in Ground 2.
`
`8
`
`

`

`Case IPR2022-00545
`Patent 9,689,161
`
`
`
`
`
`SoftWall + SoftHousing III + Okuno
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`SoftWall + SoftHousing I + SoftHousing II + SoftHousing III
`
`SoftWall + SoftHousing I + SoftHousing II + Arens
`
`SoftWall + SoftHousing I + SoftHousing II + Okuno
`
`SoftWall + SoftHousing I + SoftHousing III + Arens
`
`SoftWall + SoftHousing I + SoftHousing III + Okuno
`
`SoftWall + SoftHousing II + SoftHousing III + Arens
`
`SoftWall + SoftHousing II + SoftHousing III + Okuno
`
`SoftWall + SoftHousing I + SoftHousing II + SoftHousing II + Arens
`
`SoftWall + SoftHousing I + SoftHousing II + SoftHousing II + Okuno
`
`SoftWall + SoftHousing I + SoftHousing II + SoftHousing II + Arens
`
`+ Okuno
`
`Petitioner’s strategy of using “and/or” to connect multiple different references
`
`is propagated throughout other grounds as well. For example, Petitioner’s use of
`
`“and/or” to connect multiple difference references creates at least 16 different
`
`combinations for Ground 2, and at least 24 different combinations for Ground 5. All
`
`told, the Petition thus attempts to set forth at least 65 different obviousness
`
`combinations against the claims, in addition to two separate grounds based on
`
`anticipation. This results in an unwieldly, excessive, and burdensome number of
`
`9
`
`

`

`Case IPR2022-00545
`Patent 9,689,161
`
`
`possible combinations. Energy Source, IPR2019-01606, Paper No. 7 at 20-21;
`
`Hunting Titan, PGR2020-00080, Paper No. 7 at 10; Adaptics, IPR2018-01596,
`
`Paper No. 20 at 18-19.4
`
`This prejudice to Patent Owner is compounded by the fact that Petitioner’s
`
`attempt this number of references “would require the panel or the Patent Owner to
`
`scour the Petition to discern Petitioner’s evidence as to each of [20] claims in each
`
`of three obviousness grounds.” InVue Security Prods., Inc. v. Mobile Tech., Inc.,
`
`IPR2019-00078, Paper No. 7 at 15 (PTAB May 1, 2019). Such a requirement is
`
`“tantamount
`
`to
`
`impermissibly
`
`shifting Petitioner’s
`
`burden
`
`under
`
`35 U.S.C. § 312(a)(3).” Id. (emphasis added). Nor is it the Board’s function “to
`
`comb through Petitioner’s arguments in order to decipher the strongest argument or
`
`to determine the strongest combination of references to challenge the claims.”
`
`
`4 Petitioner has taken the same approach it its co-pending IPR petitions for the
`
`related patents asserted by Patent Owner. For example, as noted in Patent Owner’s
`
`Preliminary Responses to those petitions, the petition in IPR2022-00543 asserts 36
`
`obviousness combinations, the petition IPR2022-00546 asserts 52 obviousness
`
`combinations, and the petition in IPR2022-00544 also asserts 52 obviousness
`
`combinations.
`
`10
`
`

`

`Case IPR2022-00545
`Patent 9,689,161
`
`
`Edwards LifeSciences Corp. v. Boston Scientific Scimed, Inc., IPR2017-01304,
`
`Paper No. 8 at 6, n.2 (PTAB Oct. 25, 2017) (denying institute where the petitioner
`
`asserted seven different references in various combinations connected by “and/or”).
`
`As the Board has also explained, the statutory requirement for particularity in
`
`an IPR petition takes even more “heightened importance when considered in
`
`conjunction with the all-or-nothing approach required for institution” under the
`
`Supreme Court’s decision in SAS Institute Inc. v. Iancu. See InVue, IPR2019-00078,
`
`Paper No. 7 at 13. For example, even if the Board might discern a specific
`
`combination that did not lack clarity, under SAS the Board would be “required to
`
`institute on all challenges in the Petition, not merely those that did not lack
`
`particularity or were not voluminous and excessive.” Id. at 18. This would
`
`compound the undue burden on Patent Owner, requiring it to “identify and respond
`
`to all grounds . . . despite the lack of particularity” in the references. Id. It would
`
`also require the Board to analyze whether each and every element of all 20
`
`challenged claims is taught by the multitude of different references. Id. at 15.
`
`As a result, Petitioner’s attempt to assert at least 65 different obviousness
`
`combinations, as well as two separate anticipation grounds, fails to meet the
`
`particularity requirements for an IPR petition. For this additional reason, the Petition
`
`should be denied.
`
`11
`
`

`

`Case IPR2022-00545
`Patent 9,689,161
`
`
`IV. THE PETITION SHOULD BE DENIED BECAUSE PETITIONER HAS
`NOT MET ITS BURDEN TO ESTABLISH HOW THE CLAIMS
`SHOULD BE CONSTRUED
`A.
`Petitioner’s Advancement of Claim Construction Positions That It
`Contends are Legally Erroneous Fails to Meet its Burden
`It is well established that the Petitioner has the burden to establish how a
`
`challenged claim should be construed and apply the construed limitations to the cited
`
`art. See 37 C.F.R. § 42.104(b)(3). In this proceeding, Petitioner has taken the
`
`position that the “Board need not construe any terms in order to resolve the
`
`underlying controversy.” Pet. at 22-23. But this position directly conflicts with
`
`Petitioner’s arguments in the co-pending district court litigation. In that proceeding,
`
`Petitioner not only alleges that numerous terms must be construed, but also that
`
`“fundamental” disputes regarding the scope of the claim terms are directly “relevant
`
`to the issue of invalidity.” Exh. 2002 at 6-7. Significantly, Petitioner also asserts
`
`that the very claim construction position it now advances before the Board—i.e., that
`
`none of the claim terms require construction—is both “improper” and invites
`
`reversible “legal error.” Id. at 11.
`
`In this Preliminary Response, Patent Owner addresses Petitioner’s treatment
`
`of specific claim terms in detail. As explained below, by positing claim construction
`
`positions that it simultaneously contends are improper and legally erroneous,
`
`Petitioner has failed to demonstrate how the challenged claims should be construed
`
`12
`
`

`

`Case IPR2022-00545
`Patent 9,689,161
`
`
`and applied to the identified references as required by the Board’s regulations.
`
`37 C.F.R. § 42.104(b)(3). As a result, the Petition should be denied in its entirety.
`
`1.
`
`Petitioner’s Inconsistent and Conflicting Positions For
`“supports” and “self-supporting”
`Claims 12 and 14 of the ’161 patent recite the term “supports.” In this
`
`proceeding, Petitioner takes the position that this term, together with every other
`
`term in the ’161 patent, need not be construed. Pet. at 22-23. But in the district court
`
`proceeding, Petitioner contends that “supports” must be construed as “supporting
`
`panels that are different from the laminar panels that form the core.” Exh. 2001 at
`
`6; Exh. 2002 at 5. In taking this position, Petitioner has not only represented that
`
`“there is a fundamental dispute regarding the scope of this claim term” that requires
`
`construction, but also that this dispute is directly “relevant to the issue of invalidity.”
`
`Exh. 2002 at 6-7 (emphasis added). Even more significantly, Petitioner represented
`
`to the district court that “failing to issue a construction, or issuing a ‘plain and
`
`ordinary meaning’ construction” for the term “supports”—which is precisely what
`
`Petitioner now proposes to the Board—is both “improper” and invites “legal error.”
`
`Id. at 11 (emphasis added); id. at 12, n.7 (contending that there is a “clear” dispute
`
`regarding the meaning of this term that “must be resolved” through claim
`
`construction). Thus, pursuant to Petitioner’s representations to the district court, the
`
`13
`
`

`

`Case IPR2022-00545
`Patent 9,689,161
`
`
`Board would be committing reversible legal error here by instituting this Petition
`
`based on Petitioner’s proposed construction for “supports.”
`
`But “supports” is not the only term for which Petitioner offers conflicting
`
`positions. For instance, in the district court proceeding Petitioner contends that the
`
`term “self-supporting” must be construed to mean “able to stay upright and resist
`
`collapse without being supported by something else.” Exh. 2002 at 12.5 In doing
`
`so, Petitioner has stated that the parties not only dispute the meaning of this term,
`
`but has urged that this dispute confirms the necessity of claim construction. Id. at 13.
`
`Petitioner has even introduced two different pieces of extrinsic evidence to support
`
`its contention that this term should be construed in a specific manner. Id. at 14
`
`(citing two dictionary definitions).
`
`As a result, Petitioner’s assertion that the Board need not construe these terms
`
`is in direct conflict with its representations to the district court. Moreover, by
`
`“failing to reconcile the proffered construction in the Petition with its very different
`
`construction before the district court”—and advancing positions that it alleges are
`
`legally erroneous—Petitioner “fails to satisfy [its] burden” to identify how the
`
`challenged claims are to be construed and applied to the prior art. OrthoPediatrics
`
`
`5 This term is recited in Claim 12 of the ’161 patent.
`
`14
`
`

`

`Case IPR2022-00545
`Patent 9,689,161
`
`
`Corp. v. K2M, Inc., IPR2018-01546, Paper No. 10 at 12 (PTAB Feb. 14, 2019);
`
`Kiosoft Techs., LLC v. PayRange, Inc., IPR2021-00086, Paper No. 12 at 16 (PTAB
`
`March 22, 2021) (denying institution where Petitioner had not “provided any reason
`
`behind its inconsistent claim constructions in general”); Facebook, Inc. v. Sound
`
`View Innovations, LLC, IPR2017-00998 & IPR2017-01002, Paper No. 13 at 18
`
`(PTAB Sept. 5, 2017) (denying institution where Petitioner failed to inform the
`
`board “of its seemingly inconsistent claim construction positions” before the district
`
`court); ipDataTel, LLC et al. v. ICN Acquisition, IPR2018-01822, Paper No. 19 at
`
`13-14 (PTAB Apr. 22, 2019) (denying institution where “Petitioner has not offered
`
`any explanation as to how its positions here and in the District Court can be
`
`reconciled”).
`
`2.
`Petitioner’s Inconsistent Construction for “flaccid”
`Claim 10 of the ’161 patent also recites the term “flaccid.” In this proceeding,
`
`Petitioner asserts that this term need not be construed by the Board. Pet. at 22-23.
`
`But in the district court proceeding, Petitioner alleges that this term is indefinite
`
`because it “is subjective and fails to inform those skilled in the art of the required
`
`quality of the material.” Exh. 2002 at 16 (emphasis added). Petitioner also contends
`
`that the “patent specifications fail to provide sufficient guidance regarding . . . how
`
`those skilled in the art can determine whether a particular material is ‘flaccid.’” Id.
`
`at 17 (emphasis added); see also id. at 18 (arguing that any suggestion that “those
`
`15
`
`

`

`Case IPR2022-00545
`Patent 9,689,161
`
`
`skilled in the art will know [flaccid material] when they see it” is “amorphous”); id.
`
`at 19 (asserting that the specification “fail[s] to provide a method for those skilled in
`
`the art to determine whether a material is ‘flaccid.’”).
`
`“If a claim is indefinite, the claim, by definition, cannot be construed” as
`
`required by 37 C.F.R. §42.104(b)(3). ipDataTel, IPR2018-01822, Paper No. 19 at
`
`14 (citing Enzo Biochem, Inc. v. Applera Corp., 599 F.3d 1325, 1332 (Fed. Cir.
`
`2010)); Samsung Elecs. Am., Inc. v. Prisua Eng’g Corp., 948 F.3d 1342, 1350-51
`
`(Fed. Cir. 2020) (confirming that the Board can neither “institute inter partes review
`
`of claims for indefiniteness” nor “cancel challenged claims for indefiniteness.”).
`
`Accordingly, pursuant to Petitioner’s district court position, the Board could not
`
`construe this term. Thus, Petitioner’s failure to “offer[] any explanation as to how
`
`its positions here and in the district court can be reconciled” establishes that it has
`
`not met its burden to demonstrate how the terms should be construed as required by
`
`the Board’s regulations. ipDataTel, IPR2018-01822, Paper No. 19 at 13-14
`
`(denying institution where Petitioner argued that a claim term was indefinite in the
`
`district court); see also OrthoPediatrics, IPR2018-01546, Paper No. 10 at 12;
`
`Kiosoft, IPR2021-00086, Paper No. 12 at 16; Facebook, IPR2017-00998 &
`
`IPR2017-01002, Paper No. 13 at 18.
`
`16
`
`

`

`Case IPR2022-00545
`Patent 9,689,161
`
`
`
`3.
`
`Petitioner’s Bases for Alleging Inconsistent Positions Have
`No Merit
`As noted above, Patent Owner raised the issue of Petitioner’s contradictory
`
`positions in the district court proceeding shortly after this Petition was filed.
`
`Exh. 2003. But rather reconcile its positions, Petitioner has taken the extraordinary
`
`view that its claim construction position in one proceeding “has no bearing” on its
`
`claim construction position in the other. Ex. 2004 at 3. To justify this contention,
`
`Petitioner has alleged that it is entitled to take different claim construction because
`
`the district court action “involves a broader set of issues,” including infringement.
`
`Id. at 2.
`
`Petitioner’s position is contrary to established law. Both the Board and district
`
`courts use the Phillips claim construction standard, which was specifically “adopted
`
`[by the Board] to avoid decisions that construe the same or similar claims of a
`
`patent inconsistently across different forums.” Kiosoft, IPR2021-00086, Paper
`
`No. 12 at 15 (emphasis added). Moreover, as the Federal Circuit has repeatedly
`
`explained, “[i]t is axiomatic that claims are construed the same way for both
`
`invalidity and infringement.” Amgen Inc. v. Hoechst Marion Roussel, Inc., 314 F.3d
`
`1313, 1330 (Fed. Cir. 2003) (emphasis added). Thus, Petitioner’s contention that
`
`the claims can be construed one way in this proceeding for purposes of invalidity—
`
`but must be construed differently for “a broader set of issues” such as infringement
`
`17
`
`

`

`Case IPR2022-00545
`Patent 9,689,161
`
`
`in the district court—is firmly foreclosed by controlling precedent and is nothing
`
`short of an invitation to commit clear legal error. And by taking such contradictory
`
`positions, which it makes no attempt to reconcile, Petitioner has failed to meet its
`
`burden to demonstrate how the challenged claims should be construed and applied
`
`to the identified references. ipDataTel, IPR2018-01822, Paper No. 19 at 13-14;
`
`OrthoPediatrics, IPR2018-01546, Paper No. 10 at 12; Kiosoft, IPR2021-00086,
`
`Paper No. 12 at 16; Facebook, IPR2017-00998 & IPR2017-01002, Paper No. 13
`
`at 18.
`
`Patent Owner notes that, in the corresponding district court proceeding,
`
`Petitioner also cited to a Board decision in Target Corp. v. Proxicom Wireless, LLC
`
`as alleged support for its position on differing claim construction positions.
`
`IPR2020-00904, Paper No. 11 (PTAB Nov. 10, 2020). But Petitioner’s reliance on
`
`this decision is unavailing. For example, in Target, the Petitioner had simply
`
`submitted preliminary constructions arguing that certain terms were indefinite. Id.
`
`at 11-12. But in this case, Petitioner has gone much further, taking a final position
`
`in its claim construction brief that explicitly contradicts its arguments in the Petition
`
`regarding the term “flaccid.” See, e.g., Ex. 2002 at 16 (alleging that flaccid “is
`
`subjective and fails to inform those skilled in the art of the required quality of the
`
`material”) and 17 (asserting that the “patent specifications fail to provide sufficient
`
`18
`
`

`

`Case IPR2022-00545
`Patent 9,689,161
`
`
`guidance regarding . . . how those skilled in the art can determine whether a
`
`particular material is ‘flaccid.’”). And unlike Target, Petitioner has also alleged that
`
`a failure to construe other claim terms—which is the course of action Petitioner now
`
`proposes

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