throbber
Case 2:12-cv-02831-JPM-tmp Document 64 Filed 12/05/13 Page 1 of 6 PageID 859
`
`IN THE UNITED STATES DISTRICT COURT FOR THE
`WESTERN DISTRICT OF TENNESSEE
`WESTERN DIVISION
`
`
`B.E. TECHNOLOGY, L.L.C.,
`
`v.
`
`APPLE INC.,
`
`Plaintiff,
`
`Defendant.
`
`Civil Action No. 2:12-cv-02831-JPM-tmp
`
`APPLE INC.'S NOTICE TO THE COURT REGARDING
`MOTIONS TO STAY FILED IN RELATED LITIGATIONS
`
`
`In September 2012, B.E. Technology, L.L.C. (“B.E”) sued 19 separate defendants in
`
`
`
`
`
`actions before this Court (the “Related Actions”).1 In each of those cases, B.E. asserted one or
`
`more of U.S. Patent Nos. 6,628,314 (the “’314 patent”) and 6,771, 290 (the “’290 patent”),
`
`each of which claim priority to U.S. Patent No. 6,141,010, which B.E. also asserted but only in
`
`its case against Amazon. Both the ‘314 and ‘290 patents are asserted against Apple. After the
`
`Related Actions were instituted, several defendants (the “IPR Filers”) elected to file petitions
`
`for inter partes review (“IPR”) with the United States Patent & Trademark Office (“USPTO”).
`
`To date, at least Groupon, Samsung, and Facebook have filed motions to stay their respective
`
`
`1 B.E. v. Amazon Digital Servs., Inc., No. 2:12-cv-02767-JPM-cgc; B.E. v. Facebook, Inc.,
`No. 2:12-cv-02769-JPM-tmp; B.E. v. LinkedIn Corp., No. 2:12-cv-02772-JPM-dkv; B.E. v.
`Groupon, Inc., No. 2:12-cv-02781-JPM-cgc; B.E. v. Pandora Media, Inc., No. 2:12-cv-02782-
`JPM-cgc; B.E. v. Twitter, Inc., No. 2:12-cv-02783-JPM-cgc; B.E. v. Barnes & Noble, Inc., No.
`2:12-cv-02823-JPM-tmp; B.E. v. STA, No. 2:12-cv-02824-cgc; B.E. v. SEA, No. 2:12-cv-02825-
`JPM-tmp; B.E. v. Sony Computer Entm’t Am., Inc., No. 2:12-cv-02826-JPM-tmp; B.E. v. Sony
`Mobile Commcn’s (USA) Inc., No. 2:12-cv-02827-JPM-dkv; B.E. v. Sony Elecs. Inc., No. 2:12-
`cv-02828-JPM-tmp; B.E. v. Microsoft Corp., No. 2:12-cv-02829-JPM-tmp; B.E. v. Google Inc.,
`No. 2:12-cv-02830-JPM-cgc; B.E. v. Apple Inc., No. 2:12-cv-02831-JPM-cgc; B.E. v. Spark
`Networks, Inc., No. 2:12-cv-02832-JPM-cgc (since dismissed); B.E. v. People Media, Inc., No.
`2:12-cv-02833-JPM-dkv; B.E. v. Match.com, LLC, No. 2:12-cv-02834-JPM-dkv; B.E. v.
`Motorola Mobility Holdings, LLC, No. 2:12-cv-02866-JPM-dkv.
`
`

`
`Case 2:12-cv-02831-JPM-tmp Document 64 Filed 12/05/13 Page 2 of 6 PageID 860
`
`cases pending resolution of the pending IPRs.2 In each of those motions, the proponent asks
`
`the Court to stay not only its own case, and not only the cases of the other IPR Filers, but also
`
`the cases B.E. has filed against parties who have not filed and, to Apple’s knowledge, did not
`
`participate in the IPRs. In essence, each of the parties seeking a stay is advocating that
`
`because it chose to file an IPR, that decision should determine the choice of forum for every
`
`other defendants’ invalidity case, i.e. whether invalidity should be tried before the USPTO or
`
`before this Court. Those defendants are, in substance, asking the Court to stay, sua sponte, the
`
`litigation between B.E. and Apple even though neither Apple nor B.E. have requested a stay of
`
`that case.
`
`Because Apple does not have a procedural mechanism for filing a response to the stay
`
`motions in those Related Cases, Apple submits this Notice to the Court, to clarify its position.
`
`In short, Apple does not oppose a stay of all the cases, to the extent that such a stay
`
`does not prejudice Apple’s rights to mount a full invalidity defense, including the ability to use
`
`prior art references that were used in the IPRs. Although Apple has not sought a stay in its
`
`own case, it recognizes that the IPR Filers and most or all of the other defendants will either
`
`seek, or not oppose, a stay of their own cases pending resolution of the IPRs. When it became
`
`apparent that a majority of the other defendants were interested in having their cases stayed,
`
`Apple agreed to talk to B.E.’s counsel about whether Apple would agree to join in a stay
`
`motion in order to avoid a situation in which B.E. might not agree to a stay of less than all the
`
`cases.
`
`A “meet and confer” call took place on or around November 1, 2013, between counsel
`
`for B.E., Apple and Samsung. At that time, Apple conveyed its position that it did not plan to
`
`2 Samsung and Facebook were among the IPR Filers along with Google and Microsoft. Groupon
`and the remaining defendants did not file nor participate, to Apple’s knowledge, in any the IPR
`Petitions, but Groupon did file a motion to stay its case.
`
`

`
`Case 2:12-cv-02831-JPM-tmp Document 64 Filed 12/05/13 Page 3 of 6 PageID 861
`
`seek a stay, but would not actively oppose a stay of its case if the other defendants and B.E.
`
`wanted one, as long as its own invalidity case would not be prejudiced in any way should the
`
`IPR Filers fail to have the patents invalidated before the USPTO. During that call, Apple
`
`confirmed, repeatedly, that it is not in privity with any of the IPR filers and, therefore, any
`
`prior art estoppel that might apply under 35 U.S.C. § 315(e) should not apply to Apple. Apple
`
`confirmed that it is not a participant in any of the IPRs. Apple had no role in drafting the
`
`petitions, formulating claim construction positions, choosing the submitted prior art, or
`
`providing any form of funding or other support for the IPRs. B.E.’s counsel asked whether
`
`Apple’s counsel would be willing to confirm that in writing, and Apple’s counsel agreed that
`
`he would be willing to provide a written statement or declaration to that effect. Based on those
`
`communications, it appeared that B.E. likely would be willing to agree that, if the written
`
`verification were provided, B.E. would agree that Apple would not be in privity and would not
`
`be estopped from using any prior art submitted in the IPRs.
`
`Shortly after that “meet and confer,” and presumably after counsel for B.E. conferred
`
`with their client, B.E.’s counsel stated that B.E. would not agree to “waive its rights” under 35
`
`U.S.C. § 315(e). While Apple does not fully understand the reasoning behind B.E.’s position,
`
`based on statements by their counsel it appears to hinge on a hope that the law will develop in a
`
`direction that would allow B.E. to argue at some future time that a defendant may be in privity
`
`with an IPR-filing defendant in a related case by virtue of something like participating in a joint
`
`defense group. Although B.E. does not appear to contest the fact of Apple’s non-participation in
`
`the IPRs, to date B.E.’s only concession on this issue is that it will not argue that joining in a stay
`
`motion will, in and of itself, establish privity. Notably, B.E. has not confirmed that it will not
`
`argue that joining such a motion can be one part of the estoppel analysis or that it will not argue
`
`

`
`Case 2:12-cv-02831-JPM-tmp Document 64 Filed 12/05/13 Page 4 of 6 PageID 862
`
`that the Court should require some form of estoppel as a condition of granting a stay covering all
`
`the cases.
`
`Samsung and the other IPR filers that have sought stays have argued that it may be
`
`efficient for the Court to stay all the cases until the termination of the IPRs. That may very
`
`well be the case and, for that reason, Apple is not opposed to such a stay. But, it also is
`
`evident that part of the motivation for arguing that all the cases should be stayed is that
`
`Samsung is concerned that if other parties are allowed to continue litigating issues such as
`
`claim construction in Samsung’s absence, then Samsung’s own positions might be prejudiced
`
`in the litigation if its IPR proves unsuccessful. While Samsung’s stay motion professed a lack
`
`of understanding of Apple’s position, that position is quite similar to Samsung’s own. Just as
`
`Samsung no doubt wants to ensure that its rights are not prejudiced by litigation in which it
`
`may not be participating going forward, Apple is not playing any role in the IPRs and is not
`
`willing to simply hand over its 35 U.S.C. §§102 and 103 invalidity case to some of its co-
`
`defendants to litigate before the USPTO.
`
`Therefore, although Apple does not plan to seek a stay in its own action, Apple will not
`
`oppose a stay across all cases to the extent such a stay is sought by the other defendants or B.E.,
`
`so long as Apple is not estopped from using any of the prior art that was submitted in the IPRs
`
`or included in Apple’s invalidity contentions.
`
`
`
`
`
`

`
`Case 2:12-cv-02831-JPM-tmp Document 64 Filed 12/05/13 Page 5 of 6 PageID 863
`
`Dated: December 5, 2013
`
`
`
`
`
`Respectfully submitted,
`
`
`
`/s/ Clayton James
`Clayton James
`Lucky Vidmar
`Hogan Lovells US LLP
`One Tabor Center
`1200 Seventeenth St.
`Suite 1500
`Denver, CO 80203
`Clay.james@hoganlovells.com
`Lucky.vidmar@hoganlovells.com
`303-899-7300
`
`ATTORNEYS FOR DEFENDANT
`APPLE INC.
`
`

`
`Case 2:12-cv-02831-JPM-tmp Document 64 Filed 12/05/13 Page 6 of 6 PageID 864
`
`CERTIFICATE OF SERVICE
`
`Pursuant to the Federal Rules of Civil Procedure and the Local Rules, I hereby certify
`
`that all counsel of record who have appeared in this case are being served today with a copy
`
`of the foregoing via electronic mail.
`
`
`Dated: December 5, 2013
`
`/s/ C. Matthew Rozier
`
`
`
`
`
`- 3 -

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