throbber
Case 3:20-cv-08297-RS Document 49 Filed 04/05/21 Page 1 of 2
`
`UNITED STATES DISTRICT COURT
`
`NORTHERN DISTRICT OF CALIFORNIA
`
`In re EXPRESS MOBILE CASES
`
`Case Nos. 3:19-cv-06559-RS
`3:20-cv-06152-RS
`3:20-cv-08297-RS
`3:20-cv-08321-RS
`3:20-cv-08335-RS
`3:20-cv-08339-RS
`3:20-cv-08461-RS
`3:20-cv-08491-RS
`3:20-cv-08492-RS
`3:21-cv-01145-RS
`
`ORDER GRANTING IN PART AND
`DENYING IN PART STAY MOTIONS
`
`In the interests of efficiency and to avoid delaying the parties’ efforts to comply with the
`
`prior order directing them to coordinate claim construction in these matters, the motions to stay
`
`will be decided without reply briefing or oral argument. It is apparent there is a basis to treat the
`
`five patents at issue across these cases in two separate groups. The ’397 patent and the ’168 patent
`
`will hereinafter be referred to as the Rempel patents, after the sole named inventor. The ’755
`
`patent, the ’287 patent, and the ’044 patent will be referred to as the RCB patents, after the initials
`
`of the three named inventors.
`
`The Rempel patents are presently subject to reexamination proceedings, and the one case
`
`in this court involving only those patents, X.Commerce, Inc. (Magento) v. Express Mobile, Inc.,
`
`1
`
`2
`
`3
`
`4
`
`5
`
`6
`
`7
`
`8
`
`9
`
`10
`
`11
`
`12
`
`13
`
`14
`
`15
`
`16
`
`17
`
`18
`
`19
`
`20
`
`21
`
`22
`
`23
`
`24
`
`25
`
`26
`
`27
`
`28
`
`Northern District of California
`
`United States District Court
`
`Adobe v. Express Mobile - IPR2021-01227
`PO_EM287_2007-0001
`
`

`

`Case 3:20-cv-08297-RS Document 49 Filed 04/05/21 Page 2 of 2
`
`Case No. 17-cv-2605- RS, is temporarily stayed for that and other reasons. Claim construction
`
`proceedings as to the Rempel patents were completed in the X.Commerce matter.
`
`Good cause appearing, further claim construction of the Rempel patents will not go
`
`forward in any of these cases at the present time, and the stay motions are granted to that extent.
`
`The parties are relieved from any remaining deadlines relating to claim construction as to the
`
`Rempel patents only. The status of this stay will be reviewed on or before November 30, 2021 in
`
`conjunction with further consideration of the status in the X.Commerce matter. The parties need
`
`not separately file any status updates in these cases, however. Additionally, the parties should not
`
`assume the stays in these cases necessarily will remain tied to the status of the stay in
`
`X.Commerce, as some of the relevant considerations differ.
`
`The stay motions are denied as to the RCB patents. The parties should proceed with the
`
`efforts to comply with the order requiring coordination of claim proceedings as to those patents.
`
`The parties may now presume that one joint claim construction hearing will be held as to the RCB
`
`patents, and that another joint claim construction hearing will be held as to the Rempel patents at a
`
`later time, after the stay has been lifted.
`
`In both the RCB patents claim construction hearing and the subsequent Rempel patents
`
`claim construction hearing the parties will be expected to make every effort to comply with the ten
`
`terms limit—i.e., ten terms for the RCB patents and ten terms for the Rempel patents. Again, some
`
`flexibility may be available in the event differences among defendants’ accused instrumentalities
`
`make different claim terms important to some defendants.
`
`IT IS SO ORDERED.
`
`Dated: April 2, 2021
`
`______________________________________
`
`RICHARD SEEBORG
`Chief United States District Judge
`
`2
`
`CASE NO. 17-cv-02605-RS
`
`1
`
`2
`
`3
`
`4
`
`5
`
`6
`
`7
`
`8
`
`9
`
`10
`
`11
`
`12
`
`13
`
`14
`
`15
`
`16
`
`17
`
`18
`
`19
`
`20
`
`21
`
`22
`
`23
`
`24
`
`25
`
`26
`
`27
`
`28
`
`Northern District of California
`
`United States District Court
`
`Adobe v. Express Mobile - IPR2021-01227
`PO_EM287_2007-0002
`
`

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