throbber
Case 2:21-cv-00072-JRG Document 25-8 Filed 04/23/21 Page 1 of 3 PageID #: 428
`Case 2:21-cv-00072-JRG Document 25-8 Filed 04/23/21 Page 1 of 3 PageID #: 428
`
`
`
`
`
`
`
`EXHIBIT 7
`
`EXHIBIT 7
`
`
`

`

`Case 2:21-cv-00072-JRG Document 25-8 Filed 04/23/21 Page 2 of 3 PageID #: 429
`
`
`
`
`
`
`
`
`April 21, 2021
`
`VIA EMAIL (mreiter@gibsondunn.com)
`
`Mark Reiter, Esq.
`Gibson, Dunn & Crutcher LLP
`2001 Ross Avenue
`Dallas, Texas 75201-2911
`
`
`
`
`Dear Mark:
`
`Re:
`
`
`AGIS Software Development LLC v. Uber Technologies, d/b/a Uber
`Case No. 2:21-cv-00026-JRG (E.D. Tex.)
`
` I
`
` write on behalf of AGIS Software Development LLC (“AGIS”) in response to your letter dated
`April 2, 2021 relative to the above-referenced matter. Your April 2 letter makes frivolous
`arguments based on either incongruous assumptions or no evidentiary support, and AGIS will
`seek the appropriate relief for responding to these contentions.
`
`AGIS disagrees with Uber’s contention that the claims of the ’724, ’100, and ’838 patents must
`be dismissed. While Uber states that an investigation “has revealed facts,” Uber identifies no
`facts to support its allegation that Microsoft is a co-owner of the Asserted Patents. Uber’s
`assertions are not based on any facts relevant to AGIS or Mr. Rice. Rather, Uber relies on
`excerpts of what it alleges is a 2005 Microsoft Employment Agreement, a copy of such
`agreement not being provided. Uber does not show that any of the cited provisions were
`excerpted from Mr. Rice’s agreement with Microsoft. The April 2 letter excerpts a number of
`provisions, but Uber intentionally withheld identification of the parties, if any, to the purported
`2005 Microsoft Employment Agreement. Instead, the portions of the purported 2005 Microsoft
`Employment Agreement in Uber’s letter appear to be excerpted from a different unrelated case
`concerning unrelated parties or a generic template of an agreement. Uber does not, and cannot,
`establish that this 2005 Microsoft Employment Agreement is the employment agreement
`executed between Mr. Rice and Microsoft. Uber does not cite to any authority regarding the
`applicability of an unrelated agreement that was not signed by the inventor as proof of prior
`assignment or lack of inventorship. It is clear from the language of the letter that Uber has no
`information about any of Mr. Rice’s employment agreements. Uber’s frivolous contentions are
`thus factually unsupportable and legally unwarranted.
`
`In your April 2 letter, the only facts relevant to Mr. Rice’s inventorship are the duly executed
`inventor declarations and assignment agreements by Mr. Rice. The rest of your letter relies on
`pure conjecture based tenuously on irrelevant information concerning unrelated parties. Uber
`cannot rely on the provisions of a completely unrelated agreement or generic template to support
`
`

`

`Case 2:21-cv-00072-JRG Document 25-8 Filed 04/23/21 Page 3 of 3 PageID #: 430
`
`
`
`Mark Reiter, Esq.
`April 21, 2021
`Page 2
`
`a contention to dismiss AGIS’s claims. In the course of fact discovery, Uber may subpoena
`Mr. Rice and take discovery related to its defenses. Indeed, any such investigation into the terms
`of Mr. Rice’s agreement with Microsoft would require a fact-intensive inquiry that Uber has not
`executed here.
`
`Accordingly, AGIS disagrees with Uber’s frivolous arguments, and AGIS reserves the right to
`seek from the Court the appropriate relief for any efforts and expenses related to responding to
`the frivolous contentions stated its April 2nd Letter.
`
`Sincerely,
`
`FABRICANT LLP
`
`/s/ Vincent J. Rubino, III
`
`Vincent J. Rubino, III
`
`
`
`
`
`
`
`

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