throbber
Case 2:12-cv-02831-JPM-tmp Document 31 Filed 01/10/13 Page 1 of 11 PageID 226
`
`UNITED STATES DISTRICT COURT
`WESTERN DISTRICT OF TENNESSEE
`WESTERN DIVISION
`
`B.E. TECHNOLOGY, L.L.C.,
`
`Plaintiff,
`
`v.
`
`APPLE INC.,
`
`Defendant.
`
`)
`)
`)
`)
`)
`)
`)
`)
`)
`)
`
`
`
`Case No. No. 2:12-cv-02831-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 Apple Inc. (“Apple”) 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.
`
`Apple’s Position: This matter is not ripe for a Patent Scheduling Conference, for
`
`two reasons. First, on December 20, 2012, Apple filed a Motion to Transfer Venue
`
`Pursuant to 28 U.S.C. §1404(a), requesting that this action be transferred to the Northern
`
`District of California., for the convenience of the parties and witnesses and in the
`
`interests of justice. (Dkt. 20.) A substantial number of the defendants in the eighteen
`
`other actions filed by Plaintiff in this District, all of which assert one or more of the
`
`

`
`Case 2:12-cv-02831-JPM-tmp Document 31 Filed 01/10/13 Page 2 of 11 PageID 227
`
`patents-in-suit in this action, have filed similar motions seeking transfer, a majority of
`
`them to the Northern District of California. Apple believes that in short order, virtually
`
`all of the other defendants will have filed similar motions. Apple respectfully submits
`
`that efficient judicial administration and the interests of all parties would best be served
`
`by first determining the judicial district(s) in which these actions should be venued, as it
`
`is a threshold issue that is common to all the 19 related actions. Further, the Federal
`
`Circuit recently stated its expectation that a timely transfer motion be ruled upon before a
`
`district court proceeds to the merits. See, In re Fusion I-O, Inc., 2012 WL 6634939, at *1
`
`(Fed. Cir. 2012).
`
`Second, the Patent Scheduling Conference called for in the Patent Local Rules is
`
`geared to a single-defendant case, contemplating detailed case treatment of the individual
`
`case, including presentations regarding the technology at issue and attendance by party
`
`representatives with settlement authority. In this case, however, B.E. has filed 19
`
`separate cases, and a threshold issue is the degree of coordination, if any, the Court will
`
`order with respect to issues common to the cases and whether there will be any form of
`
`common schedule. Therefore, Apple suggests that rather than setting this matter for the
`
`Patent Scheduling Conference called for in the Local Rules (and as requested by B.E.),
`
`this Court set an initial joint case management conference. Apple submits that such
`
`conferences are authorized under Fed. R. Civ. P. 16(a)(1)-(3), at the Court’s discretion for
`
`purposes of case management and efficiency.
`
`While Apple does not believe this case is ripe for further scheduling, Apple does
`
`recognize certain efficiencies to holding an initial case management conference jointly
`
`among the 19 cases. First, it provides the opportunity to discuss whether a Joint Patent
`
`- 2 -
`
`

`
`Case 2:12-cv-02831-JPM-tmp Document 31 Filed 01/10/13 Page 3 of 11 PageID 228
`
`Scheduling Conference would be beneficial or efficient if and when such time for a
`
`Patent Scheduling Conference should arise. Second, it provides the opportunity to
`
`discuss how the issue of consolidation (which plaintiff has not yet moved for) should be
`
`addressed.
`
` One example of where coordination might promote efficient case
`
`management is with respect to the filing of a Joint Planning Report and Joint Scheduling
`
`Order as required by LPR 2.1(c).
`
`Irrespective of any party’s present views on issues such as these, Apple’s
`
`fundamental point in suggesting an initial management conference rather than a full
`
`Patent Scheduling Conference (or potentially 19 such Patent Scheduling Conferences) at
`
`this point, is that an initial multi-case management conference is the best setting in which
`
`to discuss precisely what portions of all these processes should proceed concurrently, and
`
`what portions should proceed independently.
`
`(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
`
`
`1 For ’314 Patent: B.E. Technology, L.L.C. v. Facebook, Inc., 2:12-cv-02769 JPM-tmp; B.E.
`Technology, L.L.C. v. Groupon, Inc., 2:12-cv-02781 JPM-tmp; B.E. Technology, L.L.C. v.
`Match.com L.L.C., 2:12-cv-02834 JPM-tmp; B.E. Technology, L.L.C. v. People Media, Inc.,
`2:12-cv-02833 JPM-tmp; B.E. Technology, L.L.C. v. Pandora Media, Inc., 2:12-cv-02782 JPM-
`tmp; B.E. Technology, L.L.C. v. LinkedIn Corporation, 2:12-cv-02772 JPM-tmp; B.E.
`Technology, L.L.C. v. Spark Networks, Inc., 2:12-cv-02832 JPM-tmp; B.E. Technology, L.L.C. v.
`Twitter, Inc., 2:12-cv-02783 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.
`For ’290 Patent: 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. Motorola Mobility Holdings LLC, 2:12-cv-02866 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;
`
`- 3 -
`
`

`
`Case 2:12-cv-02831-JPM-tmp Document 31 Filed 01/10/13 Page 4 of 11 PageID 229
`
`deadlines set by the Patent Local Rules are necessary, beyond any minor modifications
`
`necessary to synchronize the actions.
`
`Apple’s Position:
`
`With respect to B.E.’s request for consolidation, including consolidated trials on
`
`certain issues, Apple does not consent to joinder and respectfully submits that involuntary
`
`joinder is prohibited by 35 U.S.C. § 299(c). Further, B.E.’s position regarding
`
`consolidation should be raised by motion with an opportunity for full briefing. As set
`
`forth elsewhere in this notice, however, Apple does agree that some level of coordination
`
`among the 19 cases would serve the interests of judicial efficiency.
`
`If the Court nonetheless decides to proceed with a full Patent Scheduling
`
`Conference in this case at this time, Apple respectfully submits that the Court should
`
`consider modifying the requirements of the Local Patent Rules as follows:
`
`First, as set forth above, Apple 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 stay all actions on the merits, including staying
`
`all other procedures and filings called for in the Local Patent Rules, until such motion is
`
`determined. Although the Northern District of California has adopted local patent rules,
`
`they differ in material respects from the rules adopted by this District, particularly with
`
`respect to the timing and nature of the various sets of infringement and validity related
`
`contentions and other discovery and disclosure requirements. Therefore, Apple
`
`
`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.
`
`- 4 -
`
`

`
`Case 2:12-cv-02831-JPM-tmp Document 31 Filed 01/10/13 Page 5 of 11 PageID 230
`
`respectfully suggests that this Court should first determine whether this matter will be
`
`transferred to the Northern District of California, before the parties commit substantial
`
`resources to activities required by the Local Patent Rules of this District.
`
`Second, as noted previously, Apple suggests that the Court set an initial, joint case
`
`management conference encompassing this and the other 18 pending B.E. Technology
`
`actions, to address the scheduling and case administration issues that are, and are not,
`
`common to all the cases and to consider setting a coordinated set of disclosure, discovery
`
`and other deadlines. Based upon the LPR 2.1(a) Notice filed in each action, the Court
`
`would normally conduct a Patent Scheduling Conference for that action under LPR
`
`2.1(d), the agenda for which is governed concurrently by that LPR and Local Rule 16
`
`(see LPR 2.1(d)(1)). The Planning Meeting between BE Tech and each of the defendants
`
`to address the matters required in LPR 2.1(b), and the preparation of the Joint Planning
`
`Report and Proposed Scheduling Order for each action required by LPR 2.1(c) –
`
`mandated at least fourteen and seven days, respectively, before the Patent Scheduling
`
`Conference in each action – will merit and entail extensive work, and obviously have a
`
`great impact on all of the remaining pretrial and trial proceedings in each action. The
`
`purpose inherent in LPR 2.1 will best be served by determination, at this early juncture,
`
`of the portions of the LPR 2.1 process that can best be conducted in a coordinated
`
`fashion, and the best schedule for both the concurrent and separate portions.
`
`Third, Apple respectfully suggests that Apple’s non-infringement contentions
`
`under LPR 3.3 and B.E. Technology’s validity contentions under LPR 3.7 be rescheduled
`
`to some time after this Court addresses construction of the asserted claims, as this would
`
`allow the parties to better target their contentions and arguments and more efficiently
`
`- 5 -
`
`

`
`Case 2:12-cv-02831-JPM-tmp Document 31 Filed 01/10/13 Page 6 of 11 PageID 231
`
`work with their respective experts. To the extent the Court determines not to grant this
`
`request, Apple plans to seek an extension with respect to its non-infringement contentions
`
`under LPR 3.3. On January 7, 2012, B.E. served its LPR 3.1 infringement contentions,
`
`and identified the following Apple products as allegedly infringing:
`
`
`iAd Network
` MacBook (all models from 2006 to present)
` MacBook Air (all models from 2008 to present)
` MacBook Pro (all models from 2006 to present)
` Apple TV (1st Generation)
` Apple TV (2nd Generation)
` Apple TV (3rd Generation)
`
`iMac (all models from 2006 to present)
`
`iPad
` iPad 2nd Generation
`
`
` iPad 3rd Generation
`
` iPad 4th Generation
`
` iPad mini
`
` iPhone
`
` iPhone 3G
`
` iPhone 3GS
`
` iPhone 4,
`
` iPhone 4S
`
` iPhone 5
`
` iPod Touch
`
` iPod Touch (2nd Generation)
` iPod Touch (3rd Generation)
`
`
`iPod Touch (4th Generation)
`
`iPod Touch (5th Generation)
` Mac Mini (all models from 2006 to present)
`
`“all of Defendant’s products and/or services with the following programs, features,
`software, firmware, or applications . . . App Store, iTunes, YouTube, Netflix, and Hulu
`Plus.”
`
`
`
`B.E.’s claim charts comprise over 350 pages, plus over 2,800 pages of associated document
`
`production. This is a very large and unwieldy group of products and associated contentions..
`
`Based on the filing date of its complaint, B.E. had almost three and a half months to put together
`
`its infringement contentions, not counting the time to perform whatever pre-filing investigation it
`
`may have conducted. As a matter of fairness and given the voluminous nature of its contentions,
`
`- 6 -
`
`

`
`Case 2:12-cv-02831-JPM-tmp Document 31 Filed 01/10/13 Page 7 of 11 PageID 232
`
`Apple respectfully requests that, at a minimum, its LPR 3.3 contentions be extended to occur
`
`simultaneously with its LPR 3.5 Invalidity and Unenforceability Contentions.
`
`Fourth, Apple 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 Apple’s transfer motion (D.I. 20, pp.
`
`6, 13-14), Apple 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. Apple 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 Apple 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, Apple 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 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 LPR and Apple believes the 30
`
`day window should remain if LPR 4.7 is amended as requested.
`
`Sixth, Apple believes that the provisions of LPR 3.4 (requiring producing or
`
`making available for inspection and copying documents relating to Apple’s non-
`
`infringement contentions0, be made contingent upon the entry of a suitable protective
`
`- 7 -
`
`

`
`Case 2:12-cv-02831-JPM-tmp Document 31 Filed 01/10/13 Page 8 of 11 PageID 233
`
`order governing the production of highly confidential technical information, including
`
`source code. The patents-in-suit relate to a computerized method for presenting
`
`advertisements to users and to graphical user interfaces and user profiles, all implemented
`
`through computer software. Therefore, Apple expects that the documents and
`
`information contemplated by LPR 3.4 may require inspection of Apple’s proprietary
`
`source code and possibly the source code of third-party application developers. Such
`
`source code comprises trade secrets and other highly confidential technical information.
`
`Even the “temporary,” “attorneys eyes only” protection prescribed in the LPR’s may not
`
`have sufficient measures to govern the disclosure of matters such as source code. In the
`
`event the parties are unable to agree on a form of protective order and require the Court's
`
`involvement to resolve an impasse, LPR 3.4 should be made contingent upon entry of a
`
`protective order.
`
`(3)
`
`Case Management Issues
`
`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.
`
`Apple’s position on this issue is that some level of coordination among the cases
`
`may be appropriate, but Apple objects to consolidation, including consolidation for trial,
`
`and submits that involuntary consolidation is barred by 35 U.S.C. § 299(c).
`
`B.E.’s position is there are no other case management issues that would impact
`
`any party’s ability to conform to the Local Patent Rules.
`
`- 8 -
`
`

`
`Case 2:12-cv-02831-JPM-tmp Document 31 Filed 01/10/13 Page 9 of 11 PageID 234
`
`It is Apple’s position that the schedule of disclosures and discovery called for in
`
`the Local Patent Rules will likely need to be varied to reflect the complexity of the case
`
`as determined by the voluminous number of products accused by B.E.
`
`
`
`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
`Telephone: (901) 522-9000
`Facsimile: (901) 527-3746
`rcarter@martintate.com
`asimpson@martintate.com
`
`Attorneys for Plaintiff
`B.E. Technology, L.L.C.
`
`_s/Clayton C. James (per email consent dated 1/10/13)
`Clayton C. James
`Srecko Vidmar
`HOGAN LOVELLS LLP
`One Tabor Center, Suite 1500
`1200 Seventeenth Street
`
`- 9 -
`
`
`
`
`
`
`
`

`
`Case 2:12-cv-02831-JPM-tmp Document 31 Filed 01/10/13 Page 10 of 11 PageID 235
`
`Denver, CO 80202
`(303) 899-7300 (phone)
`(303) 899-7333 (fax)
`clay.james@hoganlovells.com
`lucky.vidmar@hoganlovells.com
`
`s/Glen G. Reid, Jr. (per email consent dated 1/10/13)
`Glen G. Reid, Jr. (#8184)
`WYATT, TARRANT & COMBS, LLP
`1715 Aaron Brenner Drive, Suite 800
`Memphis, TN 38120-4367
`(901) 537-1000 (phone)
`(901) 537-1010 (fax)
`greid@wyattfirm.com
`
`s/Mark Vorder-Bruegge, Jr. (per email consent dated 1/10/13)
`Mark Vorder-Bruegge, Jr. (#06389)
`WYATT, TARRANT & COMBS, LLP
`1715 Aaron Brenner Drive, Suite 800
`Memphis, TN 38120-4367
`(901) 537-1000 (phone)
`(901) 537-1010 (fax)
`mvorder-bruegge@wyattfirm.com
`
`Attorneys for Defendant Apple Inc.
`
`- 10 -
`
`
`
`
`
`
`
`

`
`Case 2:12-cv-02831-JPM-tmp Document 31 Filed 01/10/13 Page 11 of 11 PageID 236
`
`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
`Phone: 901.537.1000
`Facsimile: 901.537.1010
`greid@wyattfirm.com
`mvorder-bruegge@wyattfirm.com
`
`Clay C. James
`Srecko (Lucky) Vidmar
`C. Matthew Rozier
`HOGAN LOVELLS US LLP
`One Tabor Center, Suite 1500
`1200 Seventeenth Street
`Denver, CO 80202
`Telephone: (303) 899-7300
`Facsimile: (303) 899-7333
`clay.james@hoganlovells.com
`lucky.vidmar@hoganlovells.com
`matt.rozier@hoganlovells.com
`
`
`- 11 -
`
`s/Craig R. Kaufman
`Craig R. Kaufman
`Attorney for Plaintiff

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