throbber

`
`UNITED STATES PATENT AND TRADEMARK OFFICE
`
`__________________
`
`
`BEFORE THE PATENT TRIAL AND APPEAL BOARD
`
`__________________
`
`
`SAMSUNG ELECTRONICS CO., LTD. et al,
`Petitioner,
`
`v.
`
`MEMORYWEB, LLC,
`Patent Owner.
`
`
`
`
`
`
`
`
`
`
`Case IPR2022-00222
`Patent 10,621,228
`
`
`
`
`
`
`
`
`
`
`
`
`
`PETITIONER’S BRIEF ON FORFEITURE AND/OR WAIVER
`
`
`
`
`
`

`

` INTRODUCTION
`The law is clear. When a party is required to put in evidence to place a
`
`Proceeding No.: IPR2022-00222
`Attorney Docket: 39843-0117IP1
`
`particular issue into dispute—as was MemoryWeb’s obligation to raise its real
`
`party in interest (“RPI”) argument—said party must do so in a timely fashion, or
`
`otherwise it has “waived its arguments on this issue.” In re NuVasive, Inc., 842
`
`F.3d 1376, 1380-81 (Fed. Cir. 2016); see also 37 CFR § 42.25(b) (“A party should
`
`seek relief promptly after the need for relief is identified.”).1
`
`Yet through a series of deliberate actions, MemoryWeb repeatedly chose not
`
`to challenge Samsung’s identification of RPI and Samsung’s position that it was
`
`not an RPI to the prior Unified IPR. See Petition, 92. As apparent from its activity
`
`in IPR2021-01413, from the outset, MemoryWeb’s strategy involved arguing that
`
`Samsung was an RPI to the prior Unified IPR and that Samsung’s IPR should be
`
`estopped upon entry of a Final Written Decision in the Unified IPR, which was
`
`required by statute to occur before the oral hearing in Samsung’s IPR. But rather
`
`than seeking to develop a record to support its position in this proceeding,
`
`MemoryWeb sat on its hands. To this point, MemoryWeb did not bother to seek
`
`proper entry into this record of timely evidence that Samsung was an RPI to the
`
`Unified IPR. By choosing not to renew its pre-institution argument regarding RPI
`
`
`1 All emphasis added unless otherwise noted.
`1
`
`
`
`

`

`Proceeding No.: IPR2022-00222
`Attorney Docket: 39843-0117IP1
`in this proceeding, MemoryWeb made the decision not to challenge Samsung’s
`
`and the Board’s RPI identification.
`
`Rather than properly raising its arguments and evidence in this proceeding as
`
`the law requires, MemoryWeb chose to raise the issue in a different proceeding
`
`that did not include Samsung. Worse, MemoryWeb’s arguments and evidence in
`
`the Unified IPR were cloaked by seal and could not even be reviewed by
`
`Samsung—the party that would be aggrieved if MemoryWeb’s arguments were
`
`successful. With its conduct, MemoryWeb clearly sought to prevent Samsung due
`
`process and spring a trap that would ensnare Samsung into an estoppel that
`
`Samsung had no ability to fairly defend against. This type of gamesmanship
`
`should not be permitted, much less rewarded.
`
`If desiring its consideration in this proceeding, MemoryWeb should have
`
`confronted Samsung with its RPI arguments and evidence at a time when briefing
`
`and discovery were open within this proceeding. By seeking an advisory opinion
`
`in a proceeding that did not involve Samsung and then waiting until the eve of oral
`
`argument to spring its trap (after briefing and discovery had been closed for
`
`months), MemoryWeb has prejudiced Samsung by, inter alia, frustrating the
`
`efficiency and speed of IPR. Indeed, by unilaterally taking away, through its
`
`gamesmanship, Samsung’s opportunity to consider and rebut any RPI related
`
`arguments during the normal course this proceeding, MemoryWeb has frustrated
`
`
`
`2
`
`

`

`Proceeding No.: IPR2022-00222
`Attorney Docket: 39843-0117IP1
`Samsung’s objective in pursuing IPR by burdening Samsung with the prospect of
`
`unanticipated costs and delay.
`
`MemoryWeb should not be rewarded with an extended proceeding that
`
`allows it to re-do discovery and briefing that could have, and should have, been
`
`completed on the normal schedule in this proceeding. The only basis for
`
`MemoryWeb’s untimely request—its own deliberate delay—stands in stark
`
`contrast to the good cause required to justify such extended proceedings.
`
`Notably, MemoryWeb has offered no reasonable justification for delaying
`
`introduction of RPI arguments and corresponding evidence into this proceeding.
`
`In fact, all of the briefing and discovery MemoryWeb now seeks could have been
`
`raised earlier—no new facts or evidence concerning RPI have developed since the
`
`filing of the present IPR. Even the fact that a final written decision later came out
`
`in the Unified IPR was entirely foreseeable and does not excuse MemoryWeb from
`
`intentionally forcing Samsung to sit on the sidelines with respect to the RPI issue
`
`until it was too late for Samsung to respond in kind during the normal course of
`
`this proceeding. Because MemoryWeb failed to timely raise these issues when it
`
`clearly had an opportunity to do so in this proceeding, MemoryWeb has forfeited
`
`and waived the issue of RPI and should not be relieved of the forfeiture/waiver that
`
`MemoryWeb brought upon itself. Moreover, the issue of 35 U.S.C. § 315(e)
`
`estoppel, which arises directly out of and is inescapably linked to the RPI issue, is
`
`
`
`3
`
`

`

`Proceeding No.: IPR2022-00222
`Attorney Docket: 39843-0117IP1
`necessarily forfeited/waived by extension, as it cannot survive apart from a hitherto
`
`non-existent RPI determination.
`
`MemoryWeb should not be rewarded for its failure to timely raise its RPI
`
`arguments and evidence by forcing Samsung into compressed post-hearing
`
`discovery and briefing, in contravention of Congress’s intent for IPR proceedings
`
`to be compact and cost-effective. Nor should MemoryWeb be allowed to re-
`
`litigate, at this extremely late stage in the proceeding, issues that it clearly
`
`forfeited/waived.
`
` MEMORYWEB FAILED TO OFFER TIMELY ARGUMENTS AND
`EVIDENCE TO PUT THE RPI ISSUE INTO DISPUTE
`A. MemoryWeb Knowingly Forfeited/Waived the RPI Issue
`
`It is well established that “forfeiture is the failure to make the timely
`
`assertion of a right” and “waiver is the ‘intentional relinquishment or abandonment
`
`of a known right.’” United States v. Olano, 507 U.S. 725, 733 (1993) (quoting
`
`Johnson v. Zerbst, 304 U.S. 458, 464 (1938)). However, as the Federal Circuit
`
`recognized, the court and parties often use the terms “waiver” and “forfeiture”
`
`interchangeably. In re Google Tech. Holdings LLC 980 F.3d 858, 862-863 & n.8
`
`(Fed. Cir. 2020). PTAB’s Trial Practice Guide and this proceeding’s Scheduling
`
`Order, for instance, only mention waiver—and not forfeiture—with respect to
`
`arguments that are not timely raised. On the other hand, the Federal Circuit noted,
`
`
`
`4
`
`

`

`Proceeding No.: IPR2022-00222
`Attorney Docket: 39843-0117IP1
`for example in In re Google, that arguments not timely raised during the
`
`proceedings before the Board are forfeited. In re Google Tech. Holdings LLC at
`
`864.
`
`Regardless of whether MemoryWeb’s shortcomings constitute forfeiture or
`
`waiver (or both), the circumstances of the present case overwhelmingly point to a
`
`clear case of MemoryWeb failing to raise the issue of RPI in a timely manner
`
`during the course of these proceedings and doing so in a deliberate manner.
`
`Indeed, MemoryWeb had multiple opportunities during the IPR proceeding to
`
`address RPI issues. In each instance, it chose not to.
`
`At the outset, in the Petition as filed, Samsung made clear that only
`
`“Samsung Electronics Co., Ltd. and Samsung Electronics America, Inc.”
`
`(collectively “Samsung”) were the real parties in interest. Petition, 92. Further,
`
`Samsung explicitly stated that Samsung was not an RPI to petitions “filed by
`
`Unified Patents LLC (IPR2021-01413)” and “filed by Apple Inc. (IPR2022-
`
`00031).” Id.
`
`The Board, at the time of institution, recognized Samsung’s RPI
`
`identification, noting that they “agree with Petitioner that it is not related to
`
`Unified Patents or Apple because there is no evidence that it controls Unified
`
`Patents or Apple and its interests differ from Unified Patents and Apple.”
`
`Institution Decision, 11.
`
`
`
`5
`
`

`

`Proceeding No.: IPR2022-00222
`Attorney Docket: 39843-0117IP1
`Following institution, MemoryWeb had the opportunity to rebut the Board’s
`
`initial RPI determination by properly and timely addressing the RPI issue in its
`
`Patent Owner Response (“POR”) of September 6, 2022. Instead, MemoryWeb
`
`chose to not say anything at all, providing zero evidence/argument to rebut the RPI
`
`identification as provided in this proceeding by Samsung and as endorsed by the
`
`Board in the institution decision. There can be no clearer case of
`
`forfeiture/waiver. See Unified Patents, LLC, v. Gesture Technology Partners,
`
`LLC, IPR2021-00917, Paper 32, 5 (PTAB Dec. 16, 2022) (“By failing to raise the
`
`issue of real party in interest or privity in Patent Owner’s Response (Paper 13), we
`
`determine that Patent Owner waived those issues at trial. Patent Owner knew of
`
`the issues and chose not to include it in its briefings post-institution.”); see also
`
`Google LLC v. Uniloc 2017 LLC, IPR2020-00447, Paper 24, 9-10 n. 6 (PTAB May
`
`11, 2021) (finding waiver because POR did not renew pre-institution argument);
`
`NuVasive, 842 F.3d at 1380-81 (issues not renewed in POR are waived); IPR2022-
`
`00222, Scheduling Order (Paper 13), 9 (Board explaining that “any arguments not
`
`raised in the response may be deemed waived”); Trial Practice Guide, 94 (similarly
`
`explaining Patent Owner’s waiver of unaddressed issues). And to the extent
`
`MemoryWeb’s preliminary response (“POPR”) had presented any relevant
`
`arguments/evidence related to the RPI issue, which Samsung does not see,
`
`
`
`6
`
`

`

`Proceeding No.: IPR2022-00222
`Attorney Docket: 39843-0117IP1
`MemoryWeb incontrovertibly waived the same by choosing not to raise the issue
`
`in the POR. See id.
`
`Subsequently, in its Sur-Reply, MemoryWeb even more clearly manifested
`
`its unmistakable intent to forfeit/waive the RPI issue. Specifically, in the
`
`Petitioner’s Reply following MemoryWeb’s POR, Samsung had noted that
`
`MemoryWeb has only ever raised the RPI issue in the Unified IPR and further that
`
`MemoryWeb “has neither alleged nor submitted any evidence of direction, control,
`
`joint funding, or any relevant communication or coordination between Samsung
`
`and the other entity.” IPR2022-00222, Paper 24, 24. In response, in the Sur-
`
`Reply, MemoryWeb simply chose to proclaim that “estoppel would apply if the
`
`Board determines Petitioner is an unnamed RPI in the Unified IPR,” without
`
`addressing much less acknowledging Samsung’s argument that RPI had not been
`
`brought into dispute in this proceeding. IPR2022-00222, Paper 30, 33.
`
`Speaking of the Unified IPR, it is worth noting that, in the corresponding
`
`institution decision that came out nearly six months prior to MemoryWeb’s filing
`
`of the POR in this proceeding, the Board had declined to address the RPI issue
`
`because an RPI analysis was deemed to be not warranted in that proceeding as per
`
`“the Board’s precedential decision in SharkNinja Operating LLC v. iRobot Corp.,
`
`IPR2020-00734, Paper 11 at 18 (PTAB Oct. 6, 2020) (precedential).” Unified
`
`Patents, LLC, v. MemoryWeb, LLC, IPR2021-01413, Paper 15, 13 (PTAB Mar. 14,
`
`
`
`7
`
`

`

`Proceeding No.: IPR2022-00222
`Attorney Docket: 39843-0117IP1
`2022). Director Vidal, in the Decision Granting Director Review, later confirmed
`
`the applicability of SharkNinja’s reasoning in this instance. See IPR2021-01413,
`
`Paper 76, 5 (PTAB May 22, 2023) (confirming that “[t]he Board should not have
`
`determined whether Apple and Samsung are RPIs in [the Unified] proceeding
`
`given that determination was not necessary to resolve the proceeding.”).
`
`But despite precedent laid out in SharkNinja and the Board’s reliance on the
`
`same in declining to address the RPI issue in the Unified IPR institution decision,
`
`MemoryWeb chose to raise the RPI issue in its POR in the Unified proceeding
`
`while choosing not to raise the issue in the POR in this proceeding. That bears
`
`repeating: MemoryWeb decided to (1) pursue the RPI issue in the Unified IPR
`
`despite the Board having clearly explained, in the institution decision, why the RPI
`
`issue need not be decided in that proceeding and (2) abandon the RPI issue in this
`
`proceeding despite the Board having agreed with Samsung, in the institution
`
`decision, that Samsung and Unified were not real parties in interest.
`
`Incidentally, prior to institution in its POPR, MemoryWeb had argued that
`
`“Samsung should have been named as a real party in interest in the Unified IPR.”
`
`POPR, 30-31. MemoryWeb even provided some evidence that allegedly supported
`
`its claim that Samsung and Unified were somehow RPIs. See id., 30-32 (citing to
`
`Exs. 2005-2011). But as noted above, MemoryWeb very clearly and knowingly
`
`forfeited/waived these arguments by failing to raise the RPI issue in the POR. And
`
`
`
`8
`
`

`

`Proceeding No.: IPR2022-00222
`Attorney Docket: 39843-0117IP1
`instead of choosing to pursue the RPI issue in this proceeding where the Board had
`
`provisionally denied MemoryWeb’s RPI argument at institution, MemoryWeb
`
`chose to abandon those arguments here and instead pursue them in the Unified
`
`IPR, where the Board did not decide the RPI issue at institution based on clear
`
`precedent laid out in SharkNinja.
`
`Ultimately, for gamesmanship or otherwise, MemoryWeb knowingly and
`
`repeatedly refused to address the RPI issue in this proceeding. Samsung’s
`
`contention that it was not an RPI in the Unified IPR therefore stands unchallenged.
`
`Yet now, over three months after the Oral Hearing and over a year since the
`
`institution decision, MemoryWeb for the first time seeks additional discovery and
`
`briefing in this proceeding regarding RPI. As demonstrated above, this issue could
`
`and should have been raised long ago. There is no reason why it couldn’t have
`
`been raised earlier. MemoryWeb’s attempt to surface this issue for the first time
`
`now, after oral argument, flouts the intent of Congress and the well-established
`
`Board practice of providing a compact and speedy proceeding.
`
`Interestingly, during the Oral Hearing for this proceeding, Judge Trock
`
`questioned MemoryWeb’s counsel regarding Samsung’s lack of opportunity “to
`
`contest the issue of whether or not it ever was a real party-in-interest in the prior
`
`proceeding.” IPR2022-00222, Paper 34, 31:17-32:2. Judge Trock’s question
`
`highlights the procedural dilemma created by MemoryWeb where, because
`
`
`
`9
`
`

`

`Proceeding No.: IPR2022-00222
`Attorney Docket: 39843-0117IP1
`MemoryWeb never raised the RPI issue in this proceeding until now, Samsung’s
`
`only recourse appears to have been taking some sort of third party action in the
`
`Unified IPR—this assuming knowledge of papers and evidence under seal in that
`
`proceeding. Indeed, in responding to Judge Trock, MemoryWeb’s counsel
`
`suggested that “in terms of due process, the appropriate actions that should have
`
`been taken was that Samsung should have requested leave to intervene and [in] the
`
`Unified proceeding to present [its] evidence that it was not a real party-in-interest
`
`in that proceeding, where the real party in issue was in dispute.” Id., 32:3-7. Here,
`
`MemoryWeb’s counsel acknowledges that the RPI issue was never in dispute in
`
`the Samsung proceeding and further suggests the extraordinary and unheard of step
`
`of having Samsung intervene in the Unified proceeding.
`
`MemoryWeb is wrong. The party seeking to avail itself of relief (i.e.,
`
`MemoryWeb) must create a record and establish a baseline of evidence and create
`
`a reasonable opportunity for the party targeted by such relief (i.e., Samsung) to
`
`understand the allegation, and respond. Samsung should not be somehow required
`
`to intervene in a proceeding between third parties to preserve its rights. Not
`
`surprisingly, the extreme action of a third party intervention is not something that
`
`is remotely contemplated—in the Trial Practice Guide or elsewhere. And why
`
`would it? MemoryWeb had every opportunity to properly raise the RPI issue in
`
`this proceeding through well-established and widely recognized procedural
`
`
`
`10
`
`

`

`Proceeding No.: IPR2022-00222
`Attorney Docket: 39843-0117IP1
`mechanisms that were no less available to it during the regular course of this
`
`proceeding than during the course of the Unified proceeding.
`
`
`
`Also, during the Oral Hearing and in response to Samsung’s counsel’s
`
`explanation that MemoryWeb had waived the RPI issue by failing to put any
`
`evidence into the record in this proceeding to substantiate its position that Samsung
`
`and Unified were RPIs, Judge Trock noted that he was sympathetic to Samsung’s
`
`position on the issue of RPI waiver but queried, hypothetically, how the Board
`
`should deal with the estoppel issue “[i]f there is an order by the Board that
`
`Samsung was found to be a real party-in-interest” in the Unified IPR. IPR2022-
`
`00222, Paper 34, 14:21-15:10. Notably, Director Vidal vacated the Board’s RPI
`
`determination in the Unified IPR, rendering moot the concern expressed through
`
`the question: the Board need not deal with the estoppel issue because the RPI issue
`
`has been forfeited/waived by MemoryWeb and, as a consequence, no other RPI
`
`determinations will come into existence. See IPR2021-01413, Paper 76, 5 (PTAB
`
`May 22, 2023) (vacating the Board’s RPI determination and the RPI Order).
`
`B. MemoryWeb Ignored PTAB Precedent in Forfeiting/Waiving the RPI
`Issue
`
`For the reasons provided above, MemoryWeb should have known—by no
`
`later than the March 14, 2022 institution date of the Unified IPR—that the Unified
`
`IPR was the wrong proceeding to challenge any alleged RPI issue involving
`
`
`
`11
`
`

`

`Proceeding No.: IPR2022-00222
`Attorney Docket: 39843-0117IP1
`Unified since the Board “need not address whether Apple and Samsung are
`
`unnamed RPIs because, even if either were, it would not create a time bar or
`
`estoppel under 35 U.S.C. § 315.” IPR2021-01413, Paper 15, 13. Specifically, as
`
`per SharkNinja, the Board “need not address whether [a party] is an unnamed RPI
`
`because, even if it were, it would not create a time bar or estoppel under 35 U.S.C.
`
`§ 315.” SharkNinja Operating LLC v. iRobot Corp., IPR2020-00734, Paper 11, 18
`
`(PTAB Oct. 6, 2020) (precedential). In fact, Director Vidal later confirmed in the
`
`Unified IPR that the “precedential SharkNinja decision held that it best serves the
`
`Office’s interests in cost and efficiency to not resolve an RPI issue when ‘it would
`
`not create a time bar or estoppel under 35 U.S.C. § 315’ in that proceeding.”
`
`IPR2021-01413, Paper 76, 5 (citing SharkNinja, Paper 11, 18).
`
`Thus, based at least on well-established precedent in SharkNinja,
`
`MemoryWeb should have known that the Unified IPR—where a time bar or
`
`estoppel under 35 U.S.C. § 315 was completely out of play—was the wrong
`
`proceeding to be challenging the RPI issue if it genuinely desired to preserve a
`
`future estoppel argument against Samsung. In fact, MemoryWeb did know this, as
`
`the Board conveyed the precedential decision in SharkNinja and its implications to
`
`MemoryWeb in the Unified institution decision. See IPR2021-01413, Paper 15, 13
`
`(the Board explaining that it “need not address whether Apple and Samsung are
`
`
`
`12
`
`

`

`Proceeding No.: IPR2022-00222
`Attorney Docket: 39843-0117IP1
`unnamed RPIs [in the Unified IPR] because, even if either were, it would not
`
`create a time bar or estoppel under 35 U.S.C. § 315.”).
`
`At the time of this realization—i.e., no later than the March 14, 2022
`
`institution date of the Unified IPR—MemoryWeb had a choice. MemoryWeb
`
`could have continued to press forward the RPI issue in the Unified IPR in
`
`contravention of clear guidance provided in SharkNinja and in the Unified
`
`institution decision; or MemoryWeb could have spent the next six months
`
`preparing to properly raise the RPI issue in the Samsung IPR by the September 6,
`
`2022 POR deadline. MemoryWeb deliberately and knowingly chose the former
`
`despite the clear precedent set out in SharkNinja, and, as a consequence, it should
`
`now have to live with that decision.
`
`Samsung, who had no say in MemoryWeb’s decision to ignore clear PTAB
`
`precedent, should not be the one paying the price by getting embroiled in
`
`additional post-hearing discovery/briefing and being subject to potential estoppel
`
`based on an RPI issue that was long ago forfeited/waived by MemoryWeb. See
`
`IPR2021-00917, Paper 32, 5 (PTAB Dec. 16, 2022); IPR2020-00447, Paper 24, 9-
`
`10 n. 6 (PTAB May 11, 2021); NuVasive, 842 F.3d at 1380-81; IPR2022-00222,
`
`Paper 13, 9; Trial Practice Guide, 94.
`
`C. MemoryWeb Should Not Be Rescued from a Predicament of Its Own
`Making
`
`
`
`13
`
`

`

`Proceeding No.: IPR2022-00222
`Attorney Docket: 39843-0117IP1
`While Samsung strongly believes, for at least the reasons provided above,
`
`that the RPI and any resulting estoppel issues have been unequivocally waived—or
`
`otherwise forfeited—by MemoryWeb based at least on its repeated failure to
`
`address the same in this proceeding, Samsung nevertheless recognizes that there
`
`are instances where the Board may make a determination sua sponte even if a party
`
`had failed to timely advance a particular argument, and that such an argument may
`
`not always be deemed to be forfeited. See, e.g., Apple Inc. v. MPH Techs. Oy,
`
`Nos. 2021-1355, 2021-1356, 2022 WL 4103286, at *4 (Fed. Cir. Sept. 8, 2022)
`
`(the court “declin[ing] to find forfeiture where neither party disputed the
`
`construction of a [claim] term and the Board nevertheless issued a sua sponte
`
`construction in its final written decision that diverged from the parties’
`
`understanding of the claim”).
`
`But especially in a case like ours where a party (i.e., MemoryWeb) has
`
`repeatedly ignored the Board’s guidance and PTAB precedent to implicate
`
`themselves in the procedural predicament that they now find themselves in, said
`
`party should not later be excused from the plain notice and diligence requirements
`
`in PTAB proceedings and be given the extraordinary relief of post-oral hearing
`
`discovery and briefing on an issue that it chose to ignore in the first place during
`
`the regular course of this proceeding. And while we agree with Director Vidal that
`
`the Board “can and should make” an RPI determination in certain scenarios,
`
`
`
`14
`
`

`

`Proceeding No.: IPR2022-00222
`Attorney Docket: 39843-0117IP1
`MemoryWeb in this instance should not be allowed to contort PTAB guidelines
`
`and precedent to help relieve itself of an unnecessary procedural quagmire that it
`
`created of its own strategic volition.
`
`Declining post-oral hearing discovery and briefing for an issue raised out of
`
`time by MemoryWeb is keeping with the Board’s handling of past cases where a
`
`party had multiple chances to raise the issue but failed to do so. See NuVasive, 842
`
`F.3d at 1380-81 (issues not renewed in POR are waived); Unified Patents, LLC, v.
`
`Gesture Technology Partners, LLC, IPR2021-00917, Paper 32, 5 (PTAB Dec. 16,
`
`2022) (“By failing to raise the issue of real party in interest or privity in Patent
`
`Owner’s Response (Paper 13), we determine that Patent Owner waived those
`
`issues at trial. Patent Owner knew of the issues and chose not to include it in its
`
`briefings post-institution.”); Google LLC v. Uniloc 2017 LLC, IPR2020-00447,
`
`Paper 24, 9-10 n. 6 (PTAB May 11, 2021) (finding waiver because POR did not
`
`renew pre-institution argument); see also IPR2022-00222, Scheduling Order
`
`(Paper 13), 9 (Board explaining that “any arguments not raised in the response may
`
`be deemed waived”); Trial Practice Guide, 94 (similarly explaining Patent Owner’s
`
`waiver of unaddressed issues).
`
` Conclusion
`It was MemoryWeb who, in this proceeding, chose to knowingly abandon its
`
`pre-institution RPI argument following the Board’s rejection of the same in the
`
`
`
`15
`
`

`

`Proceeding No.: IPR2022-00222
`Attorney Docket: 39843-0117IP1
`institution decision and decided, instead, to solely pursue it in a different
`
`proceeding (i.e., Unified IPR) where its determination would have had no bearing
`
`on the outcome in that case, given the lack of time bar or estoppel issues there.
`
`And it was MemoryWeb who, with RPI arguments and evidence cloaked by seal in
`
`the Unified proceeding, sought to ensnare Samsung with late allegations of
`
`unnamed RPIs in this proceeding, rather than properly confronting Samsung at the
`
`appropriate time and allowing Samsung to defend itself during the normal course
`
`of this proceeding.
`
`In short, MemoryWeb put itself into this position and should not, in the
`
`interest of justice, be rewarded by being given the chance to re-litigate the RPI
`
`issue (and by extension other issues arising therefrom), particularly after having
`
`deliberately chosen to not raise such issue in the appropriate proceeding at the
`
`appropriate time.
`
`
`Dated: June 30, 2023
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
` /W. Karl Renner/
`W. Karl Renner, Reg. No. 41,265
`Jeremy J. Monaldo, Reg. No. 58,680
`Hyun Jin In, Reg. No. 70,014
`Fish & Richardson P.C.
`3200 RBC Plaza, 60 South Sixth Street
`Minneapolis, MN 55402
`T: 202-783-5070
`F: 877-769-7945
`
`
`Attorneys for Petitioner
`
`16
`
`

`

`Proceeding No.: IPR2022-00222
`Attorney Docket: 39843-0117IP1
`
`
`
`CERTIFICATE OF SERVICE
`
`Pursuant to 37 CFR §§ 42.6(e)(1) and 42.6(e)(4)(iii), the undersigned
`
`certifies that on June 30, 2023, a complete and entire copy of this Petitioner’s Brief
`
`on Forfeiture and/or Waiver was provided via email to the Patent Owner by
`
`serving the email correspondence addresses of record as follows:
`
`Jennifer Hayes
`George Dandalides
`Matthew A. Werber
`Nixon Peabody LLP
`300 South Grand Avenue, Suite 4100
`Los Angeles, CA 90071-3151
`
`Email: jenhayes@nixonpeabody.com
`gdandalides@nixonpeabody.com
`mwerber@nixonpeabody.com
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`/Kristyn Waldhauser/
`Kristyn Waldhauser
`Fish & Richardson P.C.
`60 South Sixth Street, Suite 3200
`Minneapolis, MN 55402
`
`
`
`17
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`

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