throbber
Case 2:22-cv-00828-CDS-BNW Document 63 Filed 12/05/22 Page 1 of 4
`
`
`
`
`
`
`Joseph R. Ganley (5643)
`Brenoch R. Wirthlin (10282)
`HUTCHISON & STEFFEN, PLLC
`Peccole Professional Park
`10080 West Alta Drive, Suite 200
`Las Vegas, Nevada 89145
`Telephone: (702) 385-2500
`Facsimile: (702) 385-2086
`jganley@hutchlegal.com
`bwirthlin@hutchlegal.com
`
`Edward R. Nelson III
`Christopher G. Granaghan
`John P. Murphy
`Carder W. Brooks
`NELSON BUMGARDNER CONROY PC
`3131 West 7th Street, Suite 300
`Fort Worth, TX 76107
`Telephone: (817) 377-9111
`ed@nelbum.com
`chris@nelbum.com
`murphy@nelbum.com
`carder@nelbum.com
`
`Attorneys for Defendant R2 Solutions LLC
`
`
`
`UNITED STATES DISTRICT COURT
`DISTRICT OF NEVADA
`
`
`Case No. 2:22-cv-00828-CDS-BNW
`
`REPLY IN SUPPORT OF DEFENDANT
`R2 SOLUTIONS LLC’S MOTION TO
`MODIFY LOCAL PATENT RULES TO
`CANCEL CLAIM CONSTRUCTION
`PROCEEDINGS AND TO AMEND
`SCHEDULING ORDER ACCORDINGLY
`
`ALLEGIANT TRAVEL COMPANY,
`
`Plaintiff,
`
`v.
`
`R2 SOLUTIONS LLC,
`
`Defendant.
`
`
`
`
`
`
`
`
`
`REPLY IN SUPPORT OF MOTION TO MODIFY
`LOCAL PATENT RULES
`
`
`
`CASE NO: 2:22-CV-00828-CDS-BNW
`
`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
`
`
`
`

`

`Case 2:22-cv-00828-CDS-BNW Document 63 Filed 12/05/22 Page 2 of 4
`
`
`
`
`The only issues in this case are jurisdictional. There are no technical infringement issues for the
`Court to resolve. There are no validity issues for the Court to resolve. If there are no technical
`infringement or validity issues, there is no need for claim construction. Allegiant disputes none of this.
`Indeed, Allegiant represented that it will file a motion for summary judgment on the basis that its non-
`infringement contentions are uncontroverted and that claim construction is not necessary to decide it.1
`Allegiant insists nevertheless that the parties and the Court expend significant resources on claim
`construction because R2 will not stipulate to judgment of non-infringement. Resp. ECF 62 at 2-3. This is
`nonsense. R2 has told Allegiant that it is not raising infringement issues in this case. If the Court
`determines that it has, and will exercise, jurisdiction, the case is essentially over pending appeal. But R2
`cannot simply stipulate to judgment against it. R2 filed a motion to dismiss on jurisdictional grounds, and
`that motion remains pending. ECF 28. Agreeing to the relief Allegiant seeks would risk waiving some or
`all of R2’s jurisdictional arguments. See, e.g., Aeration Solutions, Inc. v. Dickman, 85 F. App’x 772, 775
`(Fed. Cir. 2004) (holding that defendants waived personal jurisdiction defense by stipulating to
`injunction). Thus, as R2 told Allegiant during the meet-and-confer process, R2 will oppose Allegiant’s
`forthcoming motion for summary judgment on the same grounds R2 asserted in its motion to dismiss and
`its response to Allegiant’s non-infringement contentions. ECF 60-4 at 2. Because R2 has declined to
`assert infringement or otherwise contravene Allegiant’s non-infringement contentions, that will be R2’s
`only response.
`Allegiant implies that R2 is engaged in a nefarious plot to “cancel discovery only temporarily”
`and later “reverse its position about infringement” if the Court denies R2’s motion to dismiss. ECF 62 at
`3. To be clear, R2 is not raising, and will not raise, infringement issues in this case. R2 believes that the
`Court lacks subject-matter and personal jurisdiction, or, at the very least, should not exercise subject-
`matter jurisdiction under the Declaratory Judgment Act. If the Court disagrees, then R2 will appeal. But
`R2 will not assert infringement here. If infringement is not at issue in this case, neither is validity. And if
`neither infringement nor validity are at issue, claim construction is irrelevant. See Vivid Techs., Inc. v.
`
`1 Despite stating that it planned on filing its motion for summary judgment the same week that it filed its
`response to R2’s Motion to Modify Local Patent Rules to Cancel Claim Construction and to Amend
`Scheduling Order Accordingly (ECF 62 at 2), Allegiant has yet to file its motion for summary judgment.
`
`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
`
`
`
`REPLY IN SUPPORT OF MOTION TO MODIFY
`LOCAL PATENT RULES
`
`
`
`1
`
`CASE NO: 2:22-CV-00828-CDS-BNW
`
`

`

`Case 2:22-cv-00828-CDS-BNW Document 63 Filed 12/05/22 Page 3 of 4
`
`
`
`
`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
`
`Am. Science & Eng’g, Inc., 200 F.3d 795, 803 (Fed. Cir. 1999) (“[O]nly those terms need be construed
`that are in controversy, and only to the extent necessary to resolve the controversy.”).
`Finally, Allegiant accuses R2 throughout its response of ignoring its discovery obligations and the
`Court’s rules. Allegiant is wrong. In response to R2’s motion to stay discovery, the Court ordered R2 to
`“take a position.” ECF 59 at 3-4. That is what R2 did—it explicitly informed Allegiant that it was not
`asserting infringement and that it declined to contravene Allegiant’s non-infringement contentions on any
`basis other than the bases raised in R2’s motion to dismiss. ECF 60-3. Once R2 took this position, it
`made all issues other than the jurisdictional ones irrelevant. R2 thus objected to Allegiant’s first set of
`requests for production because the issues to which they are directed (mostly validity) are irrelevant.
`And, on the deadline to exchange claim terms and phrases for construction, R2 complied with the
`deadline by informing Allegiant that it did not believe any terms require construction. ECF 62-2. That is
`just the natural result of R2’s decision not to assert infringement. The Court should recognize as much
`and cancel all claim construction proceedings as unnecessary and a waste of resources.
`Dated: December 5, 2022
`
`
`
`Respectfully submitted,
`
`
`/s/ Edward R. Nelson III
`Joseph R. Ganley (5643)
`Brenoch R. Wirthlin (10282)
`HUTCHISON & STEFFEN, PLLC
`Peccole Professional Park
`10080 West Alta Drive, Suite 200
`Las Vegas, Nevada 89145
`jganley@hutchlegal.com
`bwirthlin@hutchlegal.com
`
`Edward R. Nelson III
`Christopher G. Granaghan
`John P. Murphy
`Carder W. Brooks
`NELSON BUMGARDNER CONROY PC
`3131 West 7th Street, Suite 300
`Fort Worth, TX 76107
`Telephone: (817) 377-9111
`ed@nelbum.com
`chris@nelbum.com
`murphy@nelbum.com
`carder@nelbum.com
`
`
`
`REPLY IN SUPPORT OF MOTION TO MODIFY
`LOCAL PATENT RULES
`
`
`
`2
`
`CASE NO: 2:22-CV-00828-CDS-BNW
`
`

`

`Case 2:22-cv-00828-CDS-BNW Document 63 Filed 12/05/22 Page 4 of 4
`
`
`
`
`
`ATTORNEYS FOR DEFENDANT
`R2 SOLUTIONS LLC
`
`
`CERTIFICATE OF SERVICE
`
`I hereby certify that on December 5, 2022, I caused a true and correct copy of the foregoing
`
`DEFENDANT R2 SOLUTIONS LLC’S REPLY IN SUPPORT OF MOTION TO MODIFY LOCAL
`
`PATENT RULES TO CANCEL CLAIM CONSTRUCTION PROCEEDINGS AND TO AMEND
`
`SCHEDULING ORDER ACCORDINGLY to be submitted electronically for filing and service with the
`
`United States District Court for the District of Nevada via the Electronic Filing System to the following:
`
`
`Patrick H. Hicks (4632)
`Kelsey E. Stegall (14279)
`LITTLER MENDELSON, P.C.
`3960 Howard Hughes Parkway, #300
`Las Vegas, Nevada 89169
`phicks@littler.com
`kstegall@littler.com
`
`Michael A. Oblon
`JONES DAY
`51 Louisiana Avenue, N.W.
`Washington, D.C. 20001
`moblon@jonesday.com
`
`
`
`
`
`Keith Davis
`JONES DAY
`2727 North Harwood
`Dallas, Texas 75201
`kbdavis@jonesday.com
`
`H. Albert Liou
`JONES DAY
`717 Texas Avenue, Suite 3300
`Houston, Texas 77002
`aliou@jonesday.com
`
`Attorneys for Plaintiff
`Allegiant Travel Company
`
`
`
`/s/ Edward R. Nelson III
`
`
`
`
`
`
`
`
`
`
`
`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
`
`
`
`REPLY IN SUPPORT OF MOTION TO MODIFY
`LOCAL PATENT RULES
`
`
`
`3
`
`CASE NO: 2:22-CV-00828-CDS-BNW
`
`

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