Legal Opinion

In re Bear Creek Technologies, Inc., ('722) Patent Litigation

United States Judicial Panel on Multidistrict Litigation

Decided May 2, 2012No. MDL No. 2344PublishedCited by 8 opinions

1Opinion of the Court

TRANSFER ORDER

KATHRYN H. VRATIL, Acting Chairman.

Before the Panel:* Pursuant to 28 U.S.C. § 1407, patentholder Bear Creek Technologies, Inc. (Bear Creek) moves for centralization in the District of Delaware or, alternatively, the Eastern District of Virginia. This litigation currently consists of fourteen actions, pending in three districts, as listed on Schedule A. At issue in each action is the infringement of a Bear Creek patent by various telecommunications companies and related questions surrounding the validity or enforceability of the patent.

Certain multi-system operator defendants 1…

2Cases cited7 opinions

  1. Connecticut National Bank v. GermainSupreme Court of the United States · 1992
  2. Lexecon Inc. v. Milberg Weiss Bershad Hynes & LerachSupreme Court of the United States · 1998
  3. In Re Enron Corp. Securities, Derivative & "Erisa" LitigationUnited States Judicial Panel on Multidistrict Litigation · 2002
  4. In Re CVS Caremark Corp. Wage & Hour Employment Practices LitigationUnited States Judicial Panel on Multidistrict Litigation · 2010
  5. In Re Rembrandt Technologies, Lp, Patent Lit.United States Judicial Panel on Multidistrict Litigation · 2007

2 more not listed; retrieve them via the Exa API.

3Cited by8 opinions

  1. In re Maxim Integrated Products, Inc.United States Judicial Panel on Multidistrict Litigation · 2012
  2. Global Touch Solutions, LLC v. Toshiba Corp.District Court, E.D. Virginia · 2015
  3. In re TLI Communications LLC Patent LitigationUnited States Judicial Panel on Multidistrict Litigation · 2014
  4. In re Automated Transactions LLC Patent LitigationUnited States Judicial Panel on Multidistrict Litigation · 2013
  5. In re BRCA1- & BRCA2-based Hereditary Cancer Test Patent LitigationUnited States Judicial Panel on Multidistrict Litigation · 2014

3 more not listed; retrieve them via the Exa API.

Showing a preview — retrieve the full document via the Exa API.

Powered by the Exa API