throbber
Case 1:22-cv-22706-RNS Document 161-3 Entered on FLSD Docket 03/31/2023 Page 1 of 7
`
`
`
`EXHIBIT C
`
`

`

`Case 1:22-cv-22706-RNS Document 161-3 Entered on FLSD Docket 03/31/2023 Page 2 of 7
`
`From: Chajon, Michael (WDC)
`Mail received time: Mon, 27 Mar 2023 22:07:29
`Sent: Tue, 28 Mar 2023 02:07:13
`To: Christopher Clayton
`Cc: Paul Richter Adam Woodward Alexander F. Rojas Jose I. Rojas Moffa, Matthew (NYC) Patariu, Kevin (SDO) Joseph
`W. Bain Jodi-Ann Tillman Jason Xu andrew.fuller@nelsonmullins.com Gass, Christopher J. Airan, David Kopinski, Nicole
`Subject: RE: BNR v. HMD et al., No. 1:22-cv-22706 - Discovery hearing and upcoming negotiations
`Importance: Normal
`Sensitivity: None
`
`EXTERNAL: This email originated from outside of the SHUTTS email system. Do not respond, click any links or open any
`attachments unless you trust the sender and know the content is safe.
`
`Chris,
`
`\~
`
`Thank you for sending this proposal. To have a meaningful meet and confer tomorrow, we are sending our initial reactions to
`your proposal.
`
`\~
`
`P.R. 3-1(c) (claim charts). For the proposed supplementation under P.R. 3-1(c) (claim charts), we agree that a representative
`basis will obviate the need for additional charts if it establishes that each limitation of each asserted patent claim is present in each
`Accused Instrumentality. As you know, to prove infringement, “the patentee must show that [an] accused device contains each
`and every limitation of the asserted claims.” Ericsson, Inc. v. D-Link Systems, Inc., 773 F.3d 1201, 1215 (Fed. Cir. 2014).
`The representative basis you provide needs to meet this standard.
`
`\~
`
`The proposed language you us sent merely asserts that “each Accused Instrumentality is compliant with the 802.11n” and “the
`same infringing features exist within the 802.11n standard in the same way.” But you gave no basis for this assertion. We are
`therefore unable to test the truth of your sweeping statement. At minimum, you must provide for each Accused Instrumentality
`the basis for BNR’s assertion that the device is 802.11n compliant and why compliance is enough to establish that each limitation
`of each asserted patent claim is supposedly satisfied in the same way—i.e., that each accused device implements the cited
`portions of the standard in the same way you allege for the representative device (e.g., the Nokia G50). BNR knows that these
`devices are manufactured by different ODMs with chipsets from different suppliers, and the ODMs and chipset suppliers, not
`HMD, know how a given device implements a standard. See Silicon Labs., Inc. v. Cresta Tech. Corp., No. 14-CV-03227,
`2015 WL 846679, at *3 (N.D. Cal. Feb. 25, 2015) (A patentee must “look to the information available to it to explain how the
`non-charted products work in the same material fashion as those charted.”).
`
`\~
`
`BNR cannot merely allege that a product is representative without providing the basis for its assertion. See Silicon Labs., 2015
`
`

`

`Case 1:22-cv-22706-RNS Document 161-3 Entered on FLSD Docket 03/31/2023 Page 3 of 7
`WL 846679, at *2 (“[I]n order to rely on a claim that one accused product represents another for purposes of Rule 3-1(c), a
`patentee must do more than state as much. A patentee must state how.”); Geovector Corp. v. Samsung Elecs. Co., No. 16-
`CV-02463, 2017 WL 76950, at *5 (N.D. Cal. Jan. 9, 2017) (“GeoVector does not offer any analysis why these products,
`many of which are not even the same general type of product, can be charted representatively except to conclusorily state that
`‘the infringing devices contain’ the various claim limitations.”).
`
`\~
`
`Also, you gave us the representative basis only for the ’629 patent. To have a meaningful discussion, we need to see the
`proposed language for each asserted patent. Without the proposed supplementation for each patent, we cannot tell if you will
`provide the information required by the Patent Rules and case law. For some patents, BNR relies on compliance with other
`standards (e.g., the ’914 patent/ 802.11ac, the ’072 patent/ETSI TS 144 018 V.10.4.0). For other patents, you do not rely on
`standards at all but instead rely on software or hardware features (e.g., device components, chip packages, sensors,
`microprocessors, Find My Device software, etc.).
`
`\~
`
`P.R. 3-1(d) (indirect infringement). For the proposed supplementation under P.R. 3-1(d) (indirect infringement), you propose
`identifying “Defendant’s customers and end-users that would be the direct infringers,” and “the ‘acts’ of indirect infringement”
`“based on public information, such as website links showing how customers and end-users should use the accused products.” To
`have a meaningful discussion, we need to see your proposed supplementation to understand what specific acts of direct
`infringement you allege are the predicates for indirect infringement, who you allege does them, and what acts you allege each
`Defendant does to induce that infringement. The Defendants operate at different levels of the supply chain and their involvement
`varies.
`
`\~
`
`P.R. 3-1(e) (doctrine of equivalents): We agree to your proposed supplementation, namely, that BNR will revise its claim
`charts to identify each “function, way, and result that is equivalent [and] why any differences are not substantial” for each
`pertinent claim limitation. If BNR does this, we believe this dispute will be resolved.
`
`\~
`
`P.R. 3-1(b) (method claims): We understand that you will identify the specific defendant for each asserted method claim, and
`will add an allegation that the claimed method is supposedly performed by the identified defendant when it uses an accused
`product that you will also specifically identify. If BNR does this, we believe this dispute will be resolved.
`
`\~
`
`P.R. 3-1(c) (means-plus-function limitations): We agree to your proposed supplementation, namely, that BNR will revise the
`pertinent claim chart to reflect structure disclosed in the asserted patent. If BNR does this, we believe this dispute will be
`resolved.
`
`\~
`
`Please let us know if you will provide the information we request either before our meet-and-confer or during the conference.
`We are amenable to rescheduling the conference if you need more time.
`
`\~
`
`Thanks,
`
`

`

`Case 1:22-cv-22706-RNS Document 161-3 Entered on FLSD Docket 03/31/2023 Page 4 of 7
`
`Mike
`
`\~
`
`Mike Chajon | Perkins Coie LLP
`
`COUNSEL
`
`D. +1.202.654.3316
`
`E. MChajon@perkinscoie.com
`
`\~
`
`From: Christopher Clayton <cclayton@devlinlawfirm.com>
`Sent: Wednesday, March 22, 2023 9:23 PM
`To: Chajon, Michael (WDC) <MChajon@perkinscoie.com>
`Cc: Paul Richter <prichter@devlinlawfirm.com>; Adam Woodward <awoodward@devlinlawfirm.com>; Alexander F. Rojas
`<arojas@rojaslawfirm.com>; Jose I. Rojas <jrojas@rojaslawfirm.com>; Moffa, Matthew (NYC)
`<MMoffa@perkinscoie.com>; Patariu, Kevin (SDO) <KPatariu@perkinscoie.com>; Joseph W. Bain <JBain@shutts.com>;
`jtillman@shutts.com; Jason Xu <jason.xu@rimonlaw.com>; andrew.fuller@nelsonmullins.com; Gass, Christopher J.
`<cgass@leydig.com>; Airan, David <dairan@leydig.com>; Kopinski, Nicole <nkopinski@leydig.com>
`Subject: RE: BNR v. HMD et al., No. 1:22-cv-22706 - Discovery hearing and upcoming negotiations
`
`\~
`
`Counsel,
`
`\~
`
`Please see the attached letter proposal in PDF and Word.\~ We are available to videoconference during the times below:
`
`\~
`
`\~
`
`Friday (3/24), from 10 AM to 2 PM ET;
`Monday (3/27), from 11 AM to 2 PM ET;
`Tuesday (3/29), from 10 AM to 2 PM ET.
`
`If none of these times work, please propose alternate times.
`
`\~
`
`Best,
`
`\~
`
`Chris
`
`\~
`
`

`

`Case 1:22-cv-22706-RNS Document 161-3 Entered on FLSD Docket 03/31/2023 Page 5 of 7
`
`From: Chajon, Michael (WDC) <MChajon@perkinscoie.com>
`Sent: Friday, March 17, 2023 12:26 PM
`To: Christopher Clayton <cclayton@devlinlawfirm.com>
`Cc: Paul Richter <prichter@devlinlawfirm.com>; Adam Woodward <awoodward@devlinlawfirm.com>; Alexander F. Rojas
`<arojas@rojaslawfirm.com>; Jose I. Rojas <jrojas@rojaslawfirm.com>; Moffa, Matthew (NYC)
`<MMoffa@perkinscoie.com>; Patariu, Kevin (SDO) <KPatariu@perkinscoie.com>; Joseph W. Bain <JBain@shutts.com>;
`jtillman@shutts.com; Jason Xu <jason.xu@rimonlaw.com>; andrew.fuller@nelsonmullins.com; Gass, Christopher J.
`<cgass@leydig.com>; Airan, David <dairan@leydig.com>; Kopinski, Nicole <nkopinski@leydig.com>
`Subject: RE: BNR v. HMD et al., No. 1:22-cv-22706 - Discovery hearing and upcoming negotiations
`
`\~
`
`Hi Chris,
`
`\~
`
`Thank you for agreeing to the extension. To avoid any doubt, we explicitly preserve our objections including for attorney-client
`privilege, work product doctrine, or any other privilege or immunity.
`
`\~
`
`Best,
`
`Mike
`
`\~
`
`Mike Chajon | Perkins Coie LLP
`
`COUNSEL
`
`D. +1.202.654.3316
`
`E. MChajon@perkinscoie.com
`
`\~
`
`From: Christopher Clayton <cclayton@devlinlawfirm.com>
`Sent: Thursday, March 16, 2023 12:23 PM
`To: Chajon, Michael (WDC) <MChajon@perkinscoie.com>
`Cc: Paul Richter <prichter@devlinlawfirm.com>; Adam Woodward <awoodward@devlinlawfirm.com>; Alexander F. Rojas
`<arojas@rojaslawfirm.com>; Jose I. Rojas <jrojas@rojaslawfirm.com>; Moffa, Matthew (NYC)
`<MMoffa@perkinscoie.com>; Patariu, Kevin (SDO) <KPatariu@perkinscoie.com>; Joseph W. Bain <JBain@shutts.com>;
`jtillman@shutts.com; Jason Xu <jason.xu@rimonlaw.com>; andrew.fuller@nelsonmullins.com; Gass, Christopher J.
`<cgass@leydig.com>; Airan, David <dairan@leydig.com>; Kopinski, Nicole <nkopinski@leydig.com>
`Subject: RE: BNR v. HMD et al., No. 1:22-cv-22706 - Discovery hearing and upcoming negotiations
`
`\~
`
`Mike,
`
`

`

`Case 1:22-cv-22706-RNS Document 161-3 Entered on FLSD Docket 03/31/2023 Page 6 of 7
`
`\~
`
`BNR does not oppose an extension of Defendants’ written discovery deadline to April 10.
`
`\~
`
`Best,
`
`\~
`
`Chris
`
`\~
`
`From: Chajon, Michael (WDC) <MChajon@perkinscoie.com>
`Sent: Wednesday, March 15, 2023 4:55 PM
`To: Christopher Clayton <cclayton@devlinlawfirm.com>
`Cc: Paul Richter <prichter@devlinlawfirm.com>; Adam Woodward <awoodward@devlinlawfirm.com>; Alexander F. Rojas
`<arojas@rojaslawfirm.com>; Jose I. Rojas <jrojas@rojaslawfirm.com>; Moffa, Matthew (NYC)
`<MMoffa@perkinscoie.com>; Patariu, Kevin (SDO) <KPatariu@perkinscoie.com>; Joseph W. Bain <JBain@shutts.com>;
`jtillman@shutts.com; Jason Xu <jason.xu@rimonlaw.com>; andrew.fuller@nelsonmullins.com; Gass, Christopher J.
`<cgass@leydig.com>; Airan, David <dairan@leydig.com>; Kopinski, Nicole <nkopinski@leydig.com>
`Subject: BNR v. HMD et al., No. 1:22-cv-22706 - Discovery hearing and upcoming negotiations
`
`\~
`
`Hi Chris,
`
`\~
`
`In light of the hearing today and the 2-week period to negotiate BNR’s supplementation and our motion to strike, please let us
`know if BNR would oppose an extension of Defendants’ March 20 written discovery deadline for 3 weeks, to April 10? The
`scope of our responses and objections will be affected by the scope of accused instrumentalities in the case. If any agreement we
`reach impacts the scope of your accusations, it may avoid some issues surrounding the written discovery and response.
`
`\~
`
`We look forward to hearing from you.
`
`\~
`
`Best,
`
`Mike
`
`\~
`
`Mike Chajon | Perkins Coie LLP
`
`COUNSEL
`
`D. +1.202.654.3316
`
`

`

`Case 1:22-cv-22706-RNS Document 161-3 Entered on FLSD Docket 03/31/2023 Page 7 of 7
`E. MChajon@perkinscoie.com
`
`\~
`
`\~
`
`NOTICE: This communication may contain privileged or other confidential information. If you have received it in error, please advise the sender by reply email and immediately delete the
`message and any attachments without copying or disclosing the contents. Thank you.
`
`\~
`
`NOTICE: This communication may contain privileged or other confidential information. If you have received it in error, please advise the sender by reply email and immediately delete the
`message and any attachments without copying or disclosing the contents. Thank you.
`
`NOTICE: This communication may contain privileged or other confidential information. If you have received it in error, please advise the sender by reply email and
`immediately delete the message and any attachments without copying or disclosing the contents. Thank you.
`
`

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