throbber
Case 2:12-cv-02830-JPM-tmp Document 47 Filed 06/19/13 Page 1 of 10 PageID 572
`
`UNITED STATES DISTRICT COURT
`WESTERN DISTRICT OF TENNESSEE
`WESTERN DIVISION
`
`)))))))))))
`
`
`B.E. TECHNOLOGY, L.L.C.,
`
`
`
`
`
`Plaintiff,
`
` v.
`
`
`GOOGLE INC.,
`
`
`Civil Action No. 2:12-cv-02830-JPM-tmp
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`Defendant.
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`JOINT MOTION (INCLUDING MEMORANDUM) OF
`PLAINTIFF B.E. TECHNOLOGY, LLC and DEFENDANT GOOGLE INC.
`TO MODIFY CERTAIN LOCAL PATENT RULES DEADLINES
`AND RESTORE UNIFORMITY TO RELATED CASE SCHEDULES
`(WITH CERTIFICATE OF CONSULTATION)
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`Plaintiff B.E. Technology, LLC (“plaintiff”) and defendant Google Inc. (“Google” or
`
`“defendant”) jointly move the Court to enter the accompanying proposed Order, modifying the
`
`deadlines for four events under the Local Patent Rules (LPR’s) in this action. This joint motion
`
`results from extensive consultation between counsel for these parties as well as the majority of
`
`the defendants in eighteen other, related actions filed by plaintiff in this Court. It is anticipated
`
`that at least the vast majority of those other defendants, including but not limited to all twelve
`
`represented by the same undersigned defense counsel, will join with plaintiff in equivalent
`
`motions in those other cases as well.
`
`The effect of this motion and the ones to follow, if granted, would be to restore the
`
`uniformity of schedules in all affected actions that existed prior to the entry of stays of all
`
`

`
`Case 2:12-cv-02830-JPM-tmp Document 47 Filed 06/19/13 Page 2 of 10 PageID 573
`
`proceedings during the Court’s consideration of motions to transfer their venue, for all cases
`
`whose venue is not transferred.
`
`
`
`The four event deadlines encompassed by this motion (and the anticipated ones in the
`
`other cases) are for Google’s service of non-infringement and invalidity contentions and
`
`production of related documents (LPR 3.3-3.6) and plaintiff’s validity and enforceability
`
`contentions (LPR 3.7); and both parties’ exchange of preliminary and final patent claim terms to
`
`be construed under LPR 4.1(a) and (c). Except for one minor change requested by plaintiff and
`
`agreed to by defendant(s), no amendment of other LPR deadlines would be necessary to the
`
`objective of this motion (and the ones to follow) because all other deadlines either follow
`
`intervals from the foregoing ones automatically under the LPR’s, or will be tied to the Patent
`
`Scheduling Conference date not yet determined by the Court, or will not begin to run until the
`
`Court makes a Claim Construction Ruling. The total effect of the relief sought would be to
`
`establish the following amended deadlines for all the affected actions, measured from the date of
`
`entry of the last Order granting or denying a pending motion to transfer venue (the “Last
`
`Order”):
`
`1. Initial Non-Infringement Contentions: Modified to 30 days from the Last
`
`2. Invalidity and Unforceability Contentions: Modified to 60 days from the Last
`
`
`Order;
`
`Order;
`3. Preliminary Identification of Claim Terms to be Construed: Modified to 65
`
`days from the Last Order;
`
`4. Validity and Enforceability Contentions: 42 days after Event 2, a modification
`of 21 days from the automatic LPR deadline;
`
`5. Final Identification of Claim Terms to be Construed: Modified to 75 days
`from the Last Order;
`
`6. Preliminary Claim Constructions and Supporting Material: Automatically 14
`days from the preceding event;
`
`7. Initial Expert Claim Construction Reports: Automatically 14 days from the
`preceding event;
`
`8. Rebuttal Expert Claim Construction Reports: Automatically 14 days from the
`preceding event;
`
`
`
`2
`
`

`
`Case 2:12-cv-02830-JPM-tmp Document 47 Filed 06/19/13 Page 3 of 10 PageID 574
`
`9. Completion of Expert Discovery: Automatically 14 days from the preceding
`
`
`event;
`10. Final Claim Construction: Automatically 7 days from the preceding event;
`
`11. Opening Claim Construction Briefs: Automatically 14 days from the
`
`preceding event;
`
`12. Responsive Claim Construction Briefs: Automatically 30 days from the
`preceding event;
`
`13. Joint Claim Construction and Prehearing Statement: Automatically 7 days
`from the preceding event;
`
`14. Claim Construction Hearing: As set by the Court pursuant to LPR 4.6;
`
`15. Remaining LPR events: Automatically timed from the Court’s Claim
`Construction Ruling.
`
`As further support and explanation for this joint motion, the parties respectfully show the
`
`
`
`following, all established from the Docket in this action and the eighteen other related cases:
`
`
`
`1. Between September 7 and October 10, 2012, plaintiff filed nineteen actions in this
`
`Court against nineteen defendants, including this action against Google (filed September 21),
`
`alleging infringement of one or more of three U.S. Patents involving certain computer interface
`
`technology. A table identifying the docket numbers, defendants, filing dates, patent(s) asserted,
`
`and other logistical information referenced below, for each of the nineteen cases, is attached to
`
`this motion.
`
`2. By previous unopposed motions in each case, the deadline for the “Responsive
`
`Pleading,” as defined by the LPR’s, was set at December 31, 2012 in every case except the one
`
`against Amazon Digital Services, Inc. (“Amazon”), which was set just a week later. Because all
`
`of the early disclosures and related actions of the parties under the LPR’s are tied either directly
`
`or indirectly to the Responsive Pleading date, except events tied directly to the Patent Scheduling
`
`Conference date when set by the Court, the uniform Responsive Pleading dates had the effect of
`
`putting all of the actions on parallel schedules.
`
`3. Parallel attributes of the schedules in these cases have substantial present and future
`
`value. Although the plaintiff and each of the defendants do not agree fully on formal
`
`
`
`3
`
`

`
`Case 2:12-cv-02830-JPM-tmp Document 47 Filed 06/19/13 Page 4 of 10 PageID 575
`
`consolidation of the cases, a review of the Patent Scheduling Conference Notices filed by the
`
`parties in each case (see ECF numbers in the attached table) reveal that all parties agree that at
`
`least some concurrence of the schedules makes sense. And obviously, if the Court decides at a
`
`future time to schedule certain events in the cases together, concurrence of their schedules would
`
`assure the simultaneous readiness of all affected cases for those events.
`
`4. Between December 18, 2012, and February 12, 2013, each of the nineteen defendants
`
`filed motions to transfer venue to another District under 28 U.S.C. 1404. Subsequently, each
`
`defendant moved to stay proceedings in its action pending the Court’s decision on venue. After
`
`the Court began granting these individual stay motions, plaintiff did not oppose the remaining
`
`motions (although it did not consent to them). Within a short period, the Court entered stay
`
`Orders in all nineteen actions. The date of the stay Order in each action is included in the
`
`attached table. Each stay Order was entered at a varying point during the periods prescribed for
`
`each defendant to serve its initial non-infringement and invalidity contentions (with many
`
`subsequent deadlines flowing from those events as previously summarized). Understandably and
`
`consistent with the purpose of the stay Orders, the defendants suspended work on these matters,
`
`some of which would not be required at all in the proposed transferee forums.
`
`5. On May 24, 2013, the Court denied defendant Google’s motion to transfer and lifted
`
`the stay previously imposed in the instant case (ECF No. 45). As of the filing of this instant
`
`motion, the Court has not yet ruled on any of the other eighteen motions for transfer of the other
`
`cases, and the stays in all of those cases remain in effect.
`
`6. For each action retained in this venue, the pending stay will of course be lifted. When
`
`that occurs, the time periods remaining for the above-mentioned contentions will vary
`
`considerably, and time periods for subsequent events will vary in like measure. Further and even
`
`
`
`4
`
`

`
`Case 2:12-cv-02830-JPM-tmp Document 47 Filed 06/19/13 Page 5 of 10 PageID 576
`
`greater variations may occur due to varying dates when stays are lifted. Naturally, the parties do
`
`not presume to tell the Court, either directly or by some “forecast,” when the Court will or
`
`should rule on the remaining transfer motions in relation to the many other matters on the
`
`Court’s docket. Rather, the best method to restore uniformity to the schedules of all actions
`
`ultimately retained in this District is to re-initiate the schedule prescribed by the LPR’s, currently
`
`stayed in 18 of the 19 total actions, on an identical date – the date when all of the stays have been
`
`lifted.
`
`7. The LPR’s give the Court broad discretion to “modify the obligations or deadlines set
`
`forth in the[m] … based on the circumstances of any particular case, including, without
`
`limitation, the simplicity or complexity of the case as shown by the … parties involved.” LPR
`
`1.5. The Court has equivalent express power to manage schedules under Fed.R.Civ.P. 16 and 26,
`
`and equivalent inherent powers. The fact that this case, and each of the 18 others, involve a total
`
`of twenty parties and correspondingly extensive sets of activities for their preparation and
`
`disposition surely presents a situation of aggregate complexity contemplated in the LPRs’
`
`provisions for scheduling flexibility. The relief sought here would restore uniformity to all
`
`nineteen case schedules (and even eliminate the original seven-day difference in the Amazon
`
`case schedule) or such smaller number as may remain in this district after the Court rules on all
`
`pending transfer motions.
`
`8. In this instant action against Google and in the eighteen others, the stays also
`
`suspended the time for response to motions under Fed.R.Civ.P. 12 to strike defenses and/or
`
`dismiss counterclaims set forth in the defendants’ answers, and suspended the Court’s
`
`consideration of motions to enlarge that response time in certain actions. The Order denying
`
`transfer and lifting the stay in this action included a new deadline for Google to respond to such a
`
`
`
`5
`
`

`
`Case 2:12-cv-02830-JPM-tmp Document 47 Filed 06/19/13 Page 6 of 10 PageID 577
`
`motion to strike (see ECF No. 45), and Google already filed a timely response (ECF No. 46). It
`
`is assumed that Orders lifting stays in the other related actions that have Rule 12 motions
`
`pending will include similar determinations of the new deadlines for responding to those Rule 12
`
`motions. Accordingly, the schedule modifications sought in this motion, expected to be joined in
`
`by defendants in the other actions, would not affect the periods otherwise fixed by the Court for
`
`responding to Rule 12 motions.
`
`CERTIFICATE OF CONSULTATION
`
`
`
`The foregoing motion is presented by plaintiff and defendant jointly, based on successful
`
`consultation compliant with the Court’s Local Rule 7.2.
`
`Respectfully submitted,
`
`
`
`
`
`
`
`
`
`
`s/Glen G. Reid, Jr.
`Glen G. Reid, Jr. (#8184)
`WYATT, TARRANT & COMBS, LLP
`1715 Aaron Brenner Drive, Suite 800
`Memphis, TN 38120-4367
`Telephone: 901.537.1000
`Facsimile: 901.537.1010
`greid@wyattfirm.com
`
`
`s/Mark Vorder-Bruegge, Jr.
`Mark Vorder-Bruegge, Jr. (#06389)
`WYATT, TARRANT & COMBS, LLP
`1715 Aaron Brenner Drive, Suite 800
`Memphis, TN 38120-4367
`Telephone: 901.537.1000
`Facsimile: 901.537.1010
`mvorder-bruegge@wyattfirm.com
`
`A. John P. Mancini
`MAYER BROWN LLP
`1675 Broadway
`New York, NY 10019-5820
`Telephone: (212) 506-2500
`jmancini@mayerbrown.com
`
`
`
`
`
`6
`
`

`
`Case 2:12-cv-02830-JPM-tmp Document 47 Filed 06/19/13 Page 7 of 10 PageID 578
`
`Brian A. Rosenthal
`Ann Marie Duffy
`MAYER BROWN LLP
`1999 K Street, NW
`Washington, DC 20006
`Telephone: (202) 263-3000
`brosenthal@mayerbrown.com
`aduffy@mayerbrown.com
`
`Attorneys for Defendant Google Inc.
`
`
`
`
`
`s/Richard M. Carter (per consent MVB)
`Richard M. Carter (TN B.P.R. #7285)
`Adam C. Simpson (TN B.P.R. #24705)
`MARTIN, TATE, MORROW & MARSTON, P.C.
`6401 Poplar Avenue, Suite 1000
`Memphis, TN 38119-4839
`Telephone: (901) 522-9000
`Facsimile: (901) 527-3746
`rcarter@martintate.com
`asimpson@martintate.com
`
`Robert E. Freitas (CA Bar No. 80948)
`Craig R. Kaufman (CA Bar No. 159458)
`Daniel J. Weinberg (CA Bar No. 227159)
`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
`dweinberg@ftklaw.com
`jlin@ftklaw.com
`qolaniran@ftklaw.com
`
`Attorneys for Plaintiff B.E. Technology, L.L.C.
`
`
`
`7
`
`

`
`Case 2:12-cv-02830-JPM-tmp Document 47 Filed 06/19/13 Page 8 of 10 PageID 579
`
`
`
`CERTIFICATE OF SERVICE
`
`
`
`The foregoing document has been filed using the Court’s CM/ECF system, thereby
`
`automatically effecting electronic mail service upon all parties through their counsel of record.
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`s/Mark Vorder-Bruegge, Jr.
`Mark Vorder-Bruegge, Jr.
`
`
`
`
`
`
`8
`
`
`
`
`
`
`
`
`

`
`Case 2:12-cv-02830-JPM-tmp Document 47 Filed 06/19/13 Page 9 of 10 PageID 580
`
`ATTACHMENT TO JOINT MOTION (INCLUDING MEMORANDUM) OF
`PLAINTIFF B.E. TECHNOLOGY, LLC and DEFENDANT GOOGLE INC.
`TO AMEND CERTAIN LOCAL PATENT RULE DEADLINES
`AND RESTORE UNIFORMITY TO RELATED CASE SCHEDULES
`
`
`U.S. Patent Names:
`
`U.S. Patent No. 6,141,010, “Computer Interface Method and Apparatus with Targeted
`Advertising”
`
`U.S. Patent No. 6,628,314, “Computer Interface Method and Apparatus with Targeted
`Advertising”
`
`U.S. Patent No. 6,771,290, “Computer Interface Method and Apparatus with Portable Network
`Organization System and Targeted Advertising”
`
`Docket No.
`
`Defendant Name
`
`Filing Date
`
`Patent(s)
`Asserted
`
`
`2:12-cv-02767
`
`
`Amazon
`
`2:12-cv-02769
`2:12-cv-02772
`
`2:12-cv-02781
`2:12-cv-02782
`2:12-cv-02783
`2:12-cv-02823
`
`2:12-cv-02824
`
`2:12-cv-02825
`
`2:12-cv-02826
`
`2:12-cv-02827
`
`2:12-cv-02828
`
`Facebook, Inc.
`LinkedIn
`Corporation
`Groupon, Inc.
`Pandora Media, Inc.
`Twitter, Inc.
`Barnes & Noble,
`Inc.
`Samsung
`Telecommunications
`America, LLC
`Samsung
`Electronics
`America, Inc.
`Sony Computer
`Entertainment
`America LLC
`Sony Mobile
`Communications
`(USA) Inc.
`Sony Electronics
`Inc.
`2:12-cv-02829 Microsoft
`Corporation
`Google Inc.
`
`2:12-cv-02830
`
`2:12-cv-02831
`
`Apple Inc.
`
`
`09/07/12
`
`09/07/12
`09/07/12
`
`09/10/12
`09/10/12
`09/10/12
`09/21/12
`
`09/21/12
`
`
`6,771,290
`6,141,010
`6,628,314
`6,628,314
`
`6,628,314
`6,628,314
`6,628,314
`6,771,290
`
`6,771,290
`
`09/21/12
`
`6,771,290
`
`09/21/12
`
`6,771,290
`
`09/21/12
`
`6,771,290
`
`09/21/12
`
`09/21/12
`
`09/21/12
`
`09/22/12
`
`6,771,290
`
`6,628,314
`6,771,290
`6,628,314
`6,771,290
`6,628,314
`6,771,290
`6,628,314
`
`2:12-cv-02832
`
`Spark Networks,
`
`09/22/12
`
`
`
`9
`
`Patent
`Scheduling
`Conference
`Notice ECF No.
`
`39
`
`31
`28
`
`22
`24 and 25
`27
`29
`
`24
`
`28
`
`22
`
`26
`
`21
`
`29
`
`30
`
`31
`
`27
`
`Stay Entered
`
`
`02/12/13
`
`02/08/13
`02/12/13
`
`02/11/13
`02/08/13
`02/11/13
`02/14/13
`
`02/08/13
`
`02/08/13
`
`02/11/13
`
`02/11/13
`
`02/11/13
`
`02/11/13
`
`02/11/13
`
`02/11/13
`
`02/14/13
`
`

`
`Case 2:12-cv-02830-JPM-tmp Document 47 Filed 06/19/13 Page 10 of 10 PageID 581
`
`09/22/12
`09/22/12
`10/02/12
`
`6,628,314
`6,628,314
`6,771,290
`
`25
`22
`27
`
`02/12/13
`02/12/13
`02/11/13
`
`Inc.
`People Media, Inc.
`2:12-cv-02833
`2:12-cv-02834 Match.com L.L.C.
`2:12-cv-02866 Motorola Mobility
`Holdings LLC
`
`
`
`
`
`10

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