throbber
From: Tony Nguyen nguyen@fr.com
`Subject: FW: CPC v. Apple; CPC v. HMD - Markman Follow Up Schedule
`Date: February 11, 2022 at 9:53 AM
`To: Jennifer Bailey jennifer.bailey@eriseip.com, Adam Sandwell adam.sandwell@eriseip.com
`
`Also, FYI, from last night a3er our Markman.
`
`From: Peter Tong <Peter_Tong@txwd.uscourts.gov>
`Sent: Thursday, February 10, 2022 7:44 PM
`To: Tony Nguyen <nguyen@fr.com>; Ben.Roxborough@klgates.com; Benjamin C. Elacqua
`<Elacqua@fr.com>; bstevens@wscllp.com; BeUy Chen <bchen@fr.com>; DK.Kim@klgates.com;
`Eda Stark <stark@fr.com>; Beth.Gilman@klgates.com; george.summerfield@klgates.com;
`hcannom@wscllp.com; steve.ravel@kellyhart.com; Jim.Shimota@klgates.com;
`jonah.heemstra@klgates.com; Joy Kete <kete@fr.com>; Kate Quisenberry
`<quisenberry@fr.com>; kelly.ransom@kellyhart.com; Seth Sproul <sproul@fr.com>;
`stewart.mesher@klgates.com; Ben.Roxborough@klgates.com; dpekarekkrohn@perkinscoie.com;
`DK.Kim@klgates.com; Beth.Gilman@klgates.com; george.summerfield@klgates.com;
`Jim.Shimota@klgates.com; jonah.heemstra@klgates.com; jvillarreal@perkinscoie.com;
`mmoffa@perkinscoie.com; stewart.mesher@klgates.com; wmccabe@perkinscoie.com
`Subject: CPC v. Apple; CPC v. HMD - Markman Follow Up Schedule
`
`
`[This email originated outside of F&R.]
`
`
`Counsel for CPC, Apple, and HMD:
`
`The Court will construe all disputed means plus funcaon terms in their cases if the paraes cannot
`agree on their construcaon.
`
`The paraes in each case are ordered to meet and confer regarding expediang the schedule for
`narrowing the claims and prior art and scheduling a second Markman hearing if needed. The
`paraes are further ordered to file a joint moaon for a modified scheduling order within one
`week. Of course, if the paraes do not dispute any other means plus funcaon claims, then these
`orders do not apply.
`
`The Court typically gives 10 hours per side at trial. The Court strongly encourages the paraes to
`drop redundant claims and prior art. To discourage the paraes from needlessly preserving
`cumulaave claims or prior art, the Court will require each party’s expert to walk through every
`remaining asserted claim or prior art at trial.
`
`The Court suggests the following default schedule:
`
`
`Event
`Date
`February 28, 2022 Deadline for the first of three meet and confers to discuss
`significantly narrowing the number of claims and asserted prior art
`references at issue.
`
`IPR2022-00602
`Apple EX1078 Page 1
`
`

`

`Two weeks after
`the Final
`Contention
`Deadline
`July 13, 2022
`
`July 20, 2022
`
`July 20, 2022
`
`August 1, 2022
`
`references at issue.
`Deadline for the second of three meet and confers to discuss
`significantly narrowing the number of claims and asserted prior art
`references at issue.
`
`Final deadline to narrow the number of claims and asserted prior art
`references at issue. Any preserved claim or prior art must be
`asserted at trial.
`Parties to file updated status report and email the clerks if remaining
`means plus function claims require construction.
`Markman briefs due on any remaining disputed means plus function
`terms. Page limit of 1 page per disputed term. Parties to email the
`clerks to confirm Markman date. One round of briefing only.
`Markman hearing at 9 am.
`
`Peter Tong
`Law Clerk to the
`Honorable Alan D Albright
`U.S. District Court
`Western District of Texas
`Office: 254-750-1518
`
`**********************************************************************************
`******************************************
`This email message is for the sole use of the intended recipient(s) and may
`contain confidential and privileged information. Any unauthorized use or
`disclosure is prohibited. If you are not the intended recipient, please contact
`the sender by reply email and destroy all copies of the original message.
`**********************************************************************************
`******************************************
`
`IPR2022-00602
`Apple EX1078 Page 2
`
`

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