throbber
Case 2:12-cv-02866-JPM-tmp Document 27 Filed 01/10/13 Page 1 of 8 PageID 191
`
`UNITED STATES DISTRICT COURT
`WESTERN DISTRICT OF TENNESSEE
`WESTERN DIVISION
`
`B.E. TECHNOLOGY, L.L.C.,
`
`Plaintiff,
`
`v.
`
`MOTOROLA MOBILITY
`HOLDINGS LLC,
`
`Defendant.
`
`)
`)
`)
`)
`)
`)
`)
`)
`)
`)
`)
`
`
`
`Case No. 2:12-cv-02866 JPM tmp
`
`JURY TRIAL DEMANDED
`
`
`PATENT SCHEDULING CONFERENCE NOTICE
`
`Pursuant to Local Patent Rule 2.1(a), Plaintiff B.E. Technology, L.L.C. (“B.E.”) and
`
`Defendant Motorola Mobility Holdings LLC (“Motorola”) jointly submit this Patent Scheduling
`
`Conference Notice informing the Court:
`
`(1)
`
`Scheduling for a Patent Scheduling Conference
`
`B.E.’s position is this action is ripe to be scheduled for a Patent Scheduling Conference.
`
`B.E. believes that the Court should hold a consolidated conference to address consolidation of
`
`the related cases and other issues related to judicial economy and efficiency.
`
`Motorola believes this action is not yet ripe for a Patent Scheduling Conference of the
`
`scope prescribed in Local Patent Rule (“LPR”) 2.1(d). On December 18, 2012, pursuant to 28
`
`U.S.C. § 1404(a), Motorola filed a motion to transfer this action to the Northern District of
`
`California. (D.I. 18). Most of the defendants in the eighteen other actions filed by Plaintiff in
`
`this District, all of which assert one or more of the patents-in-suit in this action, already have
`
`filed similar motions seeking transfer, a majority of them to the Northern District of California,
`
`and Motorola understands that additional transfer motions will be filed shortly. In view of these
`
`

`
`Case 2:12-cv-02866-JPM-tmp Document 27 Filed 01/10/13 Page 2 of 8 PageID 192
`
`transfer motions Motorola respectfully submits that efficient judicial administration and the
`
`interests of all parties to the 19 cases filed by B.E. would be best served by first determining the
`
`judicial district(s) in which these actions should be venued before proceeding with discovery or
`
`further scheduling of this action.
`
`Alternatively, should the Court be inclined not to defer all activity in the case(s) until
`
`venue is determined, Motorola respectfully submits that an initial multi-case management
`
`conference comprising only counsel for the parties should be held before this case or the other 18
`
`cases are deemed ripe for a full Patent Scheduling Conference within the meaning of LPR 2.1(d)
`
`and the preparation process for it that would be required by LPR 2.1(b) and (c). Motorola
`
`submits that such an initial management conference encompassing all 19 cases is authorized
`
`under Fed. R. Civ. P. 16(a)(1)-(3) at the Court’s discretion for purposes of case management and
`
`efficiency. While Motorola does not believe the cases should be consolidated or even be
`
`conducted concurrently in all respects, there are certain elements of the proceedings in each case
`
`wherein the actions required of the parties, or to be addressed by the Court, would be more
`
`efficient, and not vulnerable to additional confusion, if conducted concurrently. For example, an
`
`initial case management conference jointly encompassing the 19 cases would provide the
`
`opportunity to discuss whether a Joint Patent Scheduling Conference (and the actions of the
`
`parties required in advance thereof) would be beneficial or efficient if and when such time for a
`
`Patent Scheduling Conference should arise. Second, it would provide the opportunity to discuss
`
`whether other portions of the procedures in the 19 cases should be coordinated, such as a joint
`
`claim construction hearing, depositions, and other discovery. Motorola notes that as a result of
`
`unopposed motions filed by the defendants in each of the 19 cases, December 31, 2012 was fixed
`
`as a uniform date for the “Responsive Pleading” as defined in LPR 1.3 (answer or Rule 12
`
`- 2 -
`
`

`
`Case 2:12-cv-02866-JPM-tmp Document 27 Filed 01/10/13 Page 3 of 8 PageID 193
`
`motion) across the 19 cases (except for one case where that deadline was fixed a week later, at
`
`January 7, 2013). Because many of the requirements in the Local Patent Rules are based on this
`
`date, these 19 cases now share virtually identical deadlines under the Local Patent Rules. An
`
`initial multi-case management conference would provide an opportunity to fully discuss what
`
`similarities and differences in the cases may permit, or interfere with, the setting of parallel
`
`schedules.
`
`(2) Modifications to the Local Patent Rules
`
`B.E.’s position is this action should be consolidated with the other B.E. actions pending
`
`before this Court for consolidated claim construction proceedings and a trial on invalidity and
`
`unenforceability of the patents-in-suit1 and that no modifications to the deadlines set by the
`
`Patent Local Rules are necessary, beyond any minor modifications necessary to synchronize the
`
`actions.
`
`Motorola does not believe this case should be consolidated with any other patent
`
`infringement action filed by B.E. in this Court involving the same patents at issue. Should the
`
`Court consider consolidation, Motorola requests that the parties be allowed the opportunity to
`
`fully brief this issue and requests a hearing.
`
`Motorola respectfully requests that this Court consider the following modifications to the
`
`requirements of the Local Patent Rules:
`
`
`1 B.E. Technology, L.L.C. v. Amazon Digital Services, Inc., 2:12-cv-02767 JPM-tmp; B.E.
`Technology, L.L.C. v. Barnes & Noble, Inc., 2:12-cv-02823 JPM-tmp; B.E. Technology, L.L.C. v.
`Samsung Electronics America, Inc., 2:12-cv-02825 JPM-tmp; B.E. Technology, L.L.C. v.
`Samsung Telecommunications America, LLC, 2:12-cv-02824 JPM-tmp; B.E. Technology, L.L.C.
`v. Sony Computer Entertainment America LLC, 2:12-cv-02826 JPM-tmp; B.E. Technology,
`L.L.C. v. Sony Electronic Inc., 2:12-cv-02828 JPM-tmp; B.E. Technology, L.L.C. v. Sony Mobile
`Communications (USA) Inc., 2:12-cv-02827 JPM-tmp; B.E. Technology, L.L.C. v. Google Inc.,
`2:12-cv-02830 JPM-tmp; B.E. Technology, L.L.C. v. Microsoft Corporation, 2:12-cv-02829
`JPM-tmp; B.E. Technology, L.L.C. v. Apple Inc., 2:12-cv-02831 JPM-tmp.
`
`- 3 -
`
`

`
`Case 2:12-cv-02866-JPM-tmp Document 27 Filed 01/10/13 Page 4 of 8 PageID 194
`
`First, as discussed above, Motorola respectfully requests that the Court address its
`
`pending motion seeking transfer of this action, before proceeding with the Patent Scheduling
`
`Conference and that the Court suspend all other procedures and filings called for in the Local
`
`Patent Rules until such motion is determined. If Motorola’s motion is granted, the parties will be
`
`subject to a different case management order and schedule. Motorola submits that this approach
`
`would minimize any negative impact on judicial economy by helping to avoid duplication of
`
`effort between this Court and a transferee venue.
`
`Second, should the Court not suspend all procedures and filings called for the in the
`
`Local Patent Rules pending resolution of the venue issue, Motorola requests that its Initial Non-
`
`Infringement Contentions pursuant to LPR 3.3 be rescheduled from 28 days after service of the
`
`Initial Infringement Contentions to 90 days after the Responsive Pleading is filed. Motorola
`
`believes such an extension may provide the Court sufficient time to rule on the pending motion
`
`to transfer venue before the parties have to engage in substantial discovery efforts without the
`
`Court having to enter a formal stay of discovery.
`
`Third, Motorola believes that the provisions of LPR 3.4, requiring producing or making
`
`available for inspection and copying copies of documents relating to Motorola’s non-
`
`infringement contentions, be made contingent upon the entry of a suitable protective order
`
`governing the production of highly confidential technical information, including source code.
`
`With respect to some anticipated disclosures, such an order arguably needs to be even stricter
`
`than the “default” attorney-eyes-only provisions of the Local Patent Rule’s. The patent-in-suit
`
`relates to graphical user interfaces and user profiles implemented through computer software. As
`
`such, Motorola expects that the documents and information contemplated by LPR 3.4 may
`
`require inspection of Motorola’s proprietary source code. Such source code comprises trade
`
`- 4 -
`
`

`
`Case 2:12-cv-02866-JPM-tmp Document 27 Filed 01/10/13 Page 5 of 8 PageID 195
`
`secrets and other highly confidential technical information. In the event the parties are unable to
`
`agree on a form of protective order and require this Court’s involvement to resolve an impasse,
`
`LPR 3.4 should be made contingent upon entry of a protective order.
`
`Fourth, Motorola believes that the procedures of LPR 4.7 should be amended to provide
`
`for the close of fact discovery 60 (rather than 30) days following issuance of the Court’s claim
`
`construction ruling. As explained in Motorola’s transfer motion (D.I. 18-1, pp. 5-6, 10-11),
`
`Motorola believes that this case is likely to involve discovery from a number of third-party
`
`witnesses knowledgeable about prior art. Depending on the Court’s claim construction rulings,
`
`some prior art may become more relevant or additional prior art may be located. Motorola
`
`believes that a 60 day window to close fact discovery following the Court’s claim construction
`
`ruling is in the interest of justice to ensure an adequate time for Motorola to seek discovery of
`
`facts relevant to invalidity of the patent-in-suit.
`
`Fifth, should LPR 4.7 be amended to provide for the close of fact discovery 60 days
`
`following issuance of the Court’s claim construction ruling, Motorola believes that the
`
`procedures of LPR 5.1(b) should be amended to provide for the initial expert witness disclosures
`
`required by Rule 26 of the Federal Rules of Civil Procedure on issues for which it bears the
`
`burden of proof to be served 90 (rather than 60) days following the Court’s claim construction
`
`ruling. Should LPR 4.7 be amended, extending the deadline for expert disclosures from 60 to 90
`
`days following issuance of the Court’s claim construction ruling will provide 30 days between
`
`the close of fact discovery and expert discovery. This 30 day window is currently provided for
`
`under the Local Patent Rule and Motorola believes the 30 day window should remain if LPR 4.7
`
`is amended as requested.
`
`(3)
`
`Case Management Issues
`
`- 5 -
`
`

`
`Case 2:12-cv-02866-JPM-tmp Document 27 Filed 01/10/13 Page 6 of 8 PageID 196
`
`B.E.’s position is this action should be consolidated, for claim construction, discovery,
`
`and trial on issues of invalidity and unenforceability, with all of the other patent infringement
`
`actions filed by B.E. in this Court involving the same patents at issue.
`
`Motorola does not believe this case should be consolidated with any other patent
`
`infringement actions filed by B.E. in this Court involving the same patents at issue. Should the
`
`Court consider consolidation, Motorola respectfully requests that the parties be allowed the
`
`opportunity to fully brief this issue and requests a hearing.
`
`B.E. believes that there are no other case management issues that would impact any
`
`party’s ability to conform to the Local Patent Rules.
`
`Motorola believes there may be other case management issues that could arise during the
`
`course of this litigation and reserves its right to address those issues at the appropriate time(s).
`
`
`
`Dated: January 10, 2013
`
`
`
`
`Respectfully submitted,
`
`
`
`By: s/Craig R. Kaufman
`Robert E. Freitas (CA Bar No. 80948)
`Craig R. Kaufman (CA Bar No. 159458)
`James Lin (CA Bar No. 241472)
`Qudus B. Olaniran (CA Bar No. 267838)
`FREITAS TSENG & KAUFMAN LLP
`100 Marine Parkway, Suite 200
`Redwood Shores, CA 94065
`Telephone: (650) 593-6300
`Facsimile: (650) 593-6301
`rfreitas@ftklaw.com
`ckaufman@ftklaw.com
`jlin@ftklaw.com
`qolaniran@ftklaw.com
`
`
`Richard M. Carter (TN B.P.R. #7285)
`Adam C. Simpson (TN B.P.R. #24705)
`MARTIN, TATE, MORROW & MARSTON, P.C.
`6410 Poplar Avenue, Suite 1000
`Memphis, TN 38119-4839
`
`- 6 -
`
`

`
`Case 2:12-cv-02866-JPM-tmp Document 27 Filed 01/10/13 Page 7 of 8 PageID 197
`
`Telephone: (901) 522-9000
`Facsimile: (901) 527-3746
`rcarter@martintate.com
`asimpson@martintate.com
`
`
`Attorneys for Plaintiff
`B.E. Technology, L.L.C.
`
`
`
`Respectfully submitted,
`
`
`By: s/Glen G. Reid (per email consent dated 1/10/13)
`Glen G. Reid, Jr.
`WYATT, TARRANT & COMBS, LLP
`1715 Aaron Brenner Drive, Suite 800
`Memphis, TN 38120-4367
`Phone: 901.537.1000
`Facsimile: 901.537.1010
`greid@wyattfirm.com
`
`Mark Vorder-Bruegge, Jr.
`WYATT, TARRANT & COMBS, LLP
`1715 Aaron Brenner Drive, Suite 800
`Memphis, TN 38120-4367
`Phone: 901.537.1000
`Facsimile: 901.537.1010
`mvorder-bruegge@wyattfirm.com
`
`Attorneys for Defendant
`
`
`
`Dated: January 10, 2013
`
`
`
`Of counsel:
`
`A. John P. Mancini
`MAYER BROWN LLP
`1675 Broadway
`New York, NY 10019-5820
`(212) 506-2500
`jmancini@mayerbrown.com
`
`Brian A. Rosenthal, pro hac pending
`Ann Marie Duffy, pro hac pending
`MAYER BROWN, LLP
`1999 K Street, NW
`Washington, DC 20006
`(202) 263-3000
`brosenthal@mayerbrown.com
`aduffy@mayerbrown.com
`
`Attorneys for Defendant
`
`- 7 -
`
`
`
`
`
`
`
`

`
`Case 2:12-cv-02866-JPM-tmp Document 27 Filed 01/10/13 Page 8 of 8 PageID 198
`
`CERTIFICATE OF SERVICE
`I hereby certify that on this 10th day of January, 2013, a copy of the foregoing was
`filed through the Court’s CM/ECF system.
`
`Glen G. Reid, Jr.
`Mark Vorder-Bruegge, Jr.
`WYATT, TARRANT & COMBS, LLP
`1715 Aaron Brenner Drive, Suite 800
`Memphis, TN 38120-4367
`Tel: 901.537.1000
`greid@wyattfirm.com
`mvorder-bruegge@wyattfirm.com
`
`A. John P. Mancini
`MAYER BROWN LLP
`1675 Broadway
`New York, NY 10019
`Tel: 212.506.2295
`jmancini@mayerbrown.com
`
`Brian A. Rosenthal
`Ann Marie Duffy
`Mayer Brown LLP
`1999 K Street, NW
`Washington, D.C. 20006
`Tel: (202) 263-3000
`brosenthal@mayerbrown.com
`aduffy@mayerbrown.com
`
`
`
`
`
`
`
`s/Craig R. Kaufman
`Craig R. Kaufman
`Attorney for Plaintiff
`
`
`
`- 8 -

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