throbber
Case 1:22-cv-01331-MSN-JFA Document 67 Filed 05/19/23 Page 1 of 4 PageID# 754
`
`IN THE UNITED STATES DISTRICT COURT
`FOR THE EASTERN DISTRICT OF VIRGINIA
`ALEXANDRIA DIVISION
`
`GEOSCOPE TECHNOLOGIES PTE. LTD.,
`
`
`
`
`
`GOOGLE LLC,
`
`
`
`
`Plaintiff,
`
`
`
`Defendant.
`
`v.
`
`
`
`
`
`Civil Action No. 1:22-cv-01331-MSN-JFA
`
`JURY TRIAL DEMANDED
`
`
`
`
`
`
`
`
`MEMORANDUM IN SUPPORT OF PLAINTIFF GEOSCOPE TECHNOLOGIES PTE.
`LTD.’S UNOPPOSED MOTION FOR LEAVE TO AMEND ITS CLAIM ELECTION
`
`Pursuant to the Joint Discovery Plan (Dkt. No. 50), Plaintiff Geoscope Technologies Pte.
`
`Ltd. (“Geoscope”) respectfully requests leave to amend its election of asserted claims to include
`
`claim 13 and related dependent claims 15-17 and 20 from U.S. Patent No. 8,320,264 (“the ’264
`
`Patent”). Google has indicated that it does not oppose this motion.
`
`On May 5, 2023, Geoscope served its Pre-Markman claim election, identifying 40 asserted
`
`claims on which it intends to proceed. Dkt. No. 50 at 14. As explained in further detail below,
`
`shortly thereafter on May 10, 2023, Geoscope provided Google with notice that it intended to
`
`amend its election to identify five additional claims from the ’264 Patent while dropping five
`
`claims across the asserted patents from its prior election to remain at the presumptive 40-claim
`
`limit. The Joint Discovery Plan states that, in connection with the Pre-Markman Claim Election,
`
`“Plaintiff’s election of asserted claims is without prejudice to Plaintiff requesting, by an
`
`appropriate motion, to assert additional claims upon a showing of good cause.” Id. Geoscope
`
`submits this motion to assert these additional claims, while remaining at the presumptive 40-claim
`
`limit, to provide clarity to the parties and the Court on the scope of the upcoming claim
`
`construction proceedings in this case.
`
`
`
`
`
`
`
`
`

`

`Case 1:22-cv-01331-MSN-JFA Document 67 Filed 05/19/23 Page 2 of 4 PageID# 755
`
`Good cause exists for Geoscope’s amendment, which arises directly out of recently learned
`
`facts regarding the functionality of the Accused Instrumentality (i.e., Google Location Services
`
`and the components and software comprising it). Geoscope’s review of Google’s source code has
`
`provided Geoscope with newly-learned facts regarding the details of how the Accused
`
`Instrumentality makes and uses path loss determinations in a manner that Geoscope alleges
`
`infringes claims 13, 15-17, and 20 of the ’264 Patent. In particular, these newly-learned facts relate
`
`to how the Accused Instrumentality makes and uses path loss determinations not just to locate
`
`devices at unknown locations, but also as part of generating and updating information maintained
`
`by Google that is used for subsequent location determinations of devices.
`
`In evaluating good cause in similar circumstances, courts look to several factors, including
`
`the reason for the delay, the diligence of the moving party, and the potential prejudice if the Court
`
`allows the amendment. See, e.g., O2 Micro v. Monolithic Power Sys., 467 F.3d 1355, 1363 (Fed.
`
`Cir. 2006); Tactile Feedback Tech. LLC v. Samsung Elecs. Am., Inc., No. 2:14-cv-940, 2015 WL
`
`13469637, at *1 (E.D. Tex. July 31, 2015); Volterra Semiconductor LLC v. Monolithic Power Sys.,
`
`Inc., No. 19-2240-CFC-SRF (D. Del. Nov. 30, 2021), Dkt. 297 at 6 (finding good cause where
`
`amendment to infringement contentions arose out of defendant’s recent production of nonpublic
`
`information). All factors weigh in favor of Geoscope here.
`
`Geoscope’s diligence in seeking this amendment is clear. Although Geoscope’s
`
`preliminary identification of asserted claims served on March 27th pursuant to the Joint Discovery
`
`Plan (see Dkt. No. 50 at 2) did not include these newly-asserted claims, that preliminary
`
`identification was made without the benefit of any non-public information regarding the Accused
`
`Instrumentality. Since then, Google has produced source code and other nonpublic technical
`
`documents, which Geoscope has endeavored to review as expeditiously as possible. Geoscope’s
`
`
`
`2
`
`
`
`

`

`Case 1:22-cv-01331-MSN-JFA Document 67 Filed 05/19/23 Page 3 of 4 PageID# 756
`
`source code reviewers inspected the source code produced by Google for the entirety of the weeks
`
`of April 24th and May 1st. However, in view of the large volume of source code produced and
`
`iterative nature of source code review, it has taken time for Geoscope and its reviewers to
`
`understand the code and confirm that understanding. Just days after completing its initial review
`
`of Google’s source code on May 5th—during which Geoscope first uncovered facts warranting this
`
`amendment—Geoscope notified Google that it was amending its election of claims to include
`
`claim 13 and related dependent claims 15-17 and 20 of the ’264 Patent and remove other
`
`previously-elected claims to remain at the presumptive 40-claim limit. Ex. 1, May 10, 2023 Email
`
`from S. Desai to Google’s Counsel. Because such information was discovered during Geoscope’s
`
`initial review of Google’s source code that was completed on May 5th, the timing of this
`
`amendment—which Geoscope gave notice of on May 10th—is not for Geoscope’s lack of
`
`diligence. Likewise, there was no unreasonable delay in Geoscope’s analysis of Google’s source
`
`code, its notification to Google of its new claim assertions, or its subsequent filing of this motion
`
`to amend.
`
`Moreover, the assertion of these claims will not prejudice Google, who has already been
`
`provided with Geoscope’s first supplemental infringement contentions that include detailed
`
`information regarding the newly-asserted claims. Google will have the opportunity to analyze
`
`these supplemental contentions before it provides its non-infringement contentions, and if
`
`necessary, will have the opportunity to supplement its invalidity contentions to address the newly-
`
`asserted claims per the parties’ agreement. Ex. 2, May 18, 2023 Email from S. Desai to M. Liu.
`
`Additionally, no materially different claim terms exist in newly-asserted claim 13 of the ’264
`
`Patent as compared to previously-asserted claims, such as claims 1 and 11, so this amendment is
`
`unlikely to have any impact on the upcoming claim construction proceedings. In any event, if
`
`
`
`3
`
`
`
`

`

`Case 1:22-cv-01331-MSN-JFA Document 67 Filed 05/19/23 Page 4 of 4 PageID# 757
`
`necessary, Google will have the opportunity to supplement its claim construction positions to
`
`address the newly-asserted claims. Id. There will also be no prejudice to Google with respect to
`
`claim narrowing as Geoscope will be substituting five of its previously-asserted claims for the five
`
`’264 Patent claims, keeping with the pre-Markman claim narrowing contemplated in the Joint
`
`Discovery Plan. Dkt. No. 50 at 14.
`
`Accordingly, Geoscope respectfully requests that the Court grant its motion for leave to
`
`amend its claim election to include claim 13 and related dependent claims 15-17 and 20 of the
`
`’264 Patent.
`
`Dated: May 19, 2023
`
`
`
`
`
`
`
`
`Respectfully submitted,
`
`
`/s/ Saunak K. Desai
`John M. Erbach (VSB No. 76695)
`Chris Bascom (VSB No. 87302)
`SPOTTS FAIN, P.C.
`Renaissance Centre
`411 East Franklin Street, Suite 600
`Richmond, Virginia 23219
`Tel: (804) 697-2044
`Fax: (804) 697-2144
`jerbach@spottsfain.com
`cbascom@spottsfain.com
`
`Timothy K. Gilman (pro hac vice)
`Saunak K. Desai (pro hac vice)
`Gregory R. Springsted (pro hac vice)
`Alexandra J. Cho (pro hac vice)
`SCHULTE ROTH & ZABEL LLP
`919 Third Avenue
`New York, NY 10022
`Tel: (212) 756-2000
`Fax: (212) 593-5955
`tim.gilman@srz.com
`saunak.desai@srz.com
`gregory.springsted@srz.com
`alexandra.cho@srz.com
`
`Attorneys for Plaintiff Geoscope Technologies
`Pte. Ltd.
`
`
`
`
`
`4
`
`

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