US 6697730

I'll search for the specific patent number and check for any recent CAFC 2026 activity.

Let me verify the litigation/docket status and get the actual claim text.

Let me try to retrieve the actual claim language and check for any 2026 CAFC activity specifically on this patent.

Scope note first (important)

I ran targeted searches on the exact number 6697730 and on the CAFC/PTAB dockets. Two findings up front:

1. No CAFC 2026 docket exists for patent 6,697,730. The only Federal Circuit appeal involving this patent is RideApp, Inc. v. Lyft, Inc., No. 20-1284 (opinion issued March 25, 2021, nonprecedential), which affirmed invalidity. The patent also expired April 4, 2021 (anticipated expiration), and the district court case was closed in 2019–2020.
2. A 2026 PTAB proceeding surfaces in search, but it is not against '730. IPR2026-00308 (Uber Technologies v. Carma Technology, filed March 12, 2026) challenges US 11,017,668, and cites the '730's pre-grant publication as prior art: Exhibit 1030 = US 2001/0037174 A1 to Dickerson. Do not conflate that with a proceeding on the '730 patent itself. Similarly, the 2026 Supreme Court petition in Rideshare Displays, Inc. v. Lyft, Inc. (No. 25-1132) concerns US 9,892,637 / 10,559,199 / 10,169,987 / 10,395,525 / 10,748,417 — different patents.

US 6,697,730 B2 — bibliographic data

Prior art cited on the face of the patent (as printed): U.S. 4,220,946 (Henrici); 5,187,810 (Yoneyama et al.); 5,493,295 (Lewiner et al.); 5,623,260, 5,657,010, 5,668,543 (all Jones); 5,739,774 (Olandesi); 5,799,263 (Culbertson); 5,818,356 (Schuessler); 5,867,780 (Malackowski et al.); 5,987,377 (Westerlage et al.); 6,006,159 (Schmier et al.); 6,085,976 (Schurzum); 6,313,760 (Jones); 6,363,488 (Ginter et al.); 6,397,057 and 6,411,803 (Malackowski et al.).

Abstract (verbatim)

"A communications and computing based urban transit system based on digital cellular communication, GPS locating technology, and digital computers to provide real-time command and control of passengers and vehicles with the objective of minimizing the social costs of urban transportation."

Plain-language overview of the independent claims

Caveat on completeness: the authoritative full text I was given truncates inside the description (Table 1), so I do not have verbatim claim text in front of me, and I exhausted my search budget before retrieving the full claim set. I therefore will not invent claim language. What follows is drawn from the Federal Circuit's own recitation of the claims in RideApp v. Lyft, 20-1284 (Fed. Cir. Mar. 25, 2021), which explicitly identifies claims 2, 3 and 6 as independent claims, and from the district court's construction order (N.D. Cal. No. 18-cv-07152-JST, Oct. 16, 2019) as summarized in that opinion.

Shared architecture of the independent claims. All three independent claims recite a system built around (a) a first limitation I could not verify verbatim, followed by (b) "a central data system for tracking passenger transportation vehicle usage and distributing periodic invoices for the usage" — i.e., a central computer that tracks how vehicles are used and issues periodic (e.g., monthly) bills, plus wireless links to vehicles and passengers.

• Claim 2 (independent). Adds (c) "a wireless means of on-demand allocation of a passenger to a specific vehicle through the central data system." In plain terms: when a rider makes a request, a wireless/central mechanism assigns that rider to a particular vehicle, on demand.
• Claim 3 (independent). Contains the same opening limitations and the on-demand allocation element, and then adds (d) "a wireless means of informing the passenger of . . ." (the full text of this informing limitation was not captured in my search results — I am flagging this rather than guessing).
• Claim 6 (independent). Contains the same first two limitations as claims 2 and 3, and recites (c) "a wireless means of detecting the proximity of the passenger and alerting the passenger of the proximity of the vehicle." In plain terms: the system senses when rider and vehicle are close to each other and notifies the rider.

Claim 1 — unverified. I could not confirm the text or independent/dependent status of claim 1. The patent almost certainly has a claim 1, but I have no authoritative basis for characterizing it, so I decline to do so rather than fabricate. (The figures — FIG. 5/6 trip-request flow, FIG. 7 rental-car flow, FIG. 8 automated billing, FIG. 9 composite interaction — correspond to the claimed functionality.)

Why these claims matter legally: the "wireless means of . . ." language triggered 35 U.S.C. § 112 ¶ 6 (means-plus-function). Under Williamson v. Citrix Online, LLC, 792 F.3d 1339 (Fed. Cir. 2015), the specification must disclose a corresponding algorithm. The district court found none for the on-demand allocation and proximity limitations; the Federal Circuit affirmed, holding claims 2, 3 and 6 invalid as indefinite and expressly declining to reach the "tracking and distributing" or "expected arrival time" limitations. Citations: https://cases.justia.com/federal/appellate-courts/cafc/20-1284/20-1284-2021-03-25.pdf and https://www.courtlistener.com/opinion/[4867540](/patent/4867540)/rideapp-inc-v-lyft-inc/

2026 status snapshot (this is the part most relevant to a current docket check)

• CAFC: no 2026 appeal pending on '730. The 20-1284 mandate is long final. The docket page: https://dockets.justia.com/docket/circuit-courts/cafc/20-1284
• PTAB history on '730: IPR2019-00414 and IPR2019-00671 (Lyft, Inc. v. RideApp, Inc.), both recorded by Google Patents as "Not Instituted – Merits." https://portal.unifiedpatents.com/ptab/case/IPR2019-00414 and .../IPR2019-00671
• District court matters touching '730: RideApp v. Lyft, N.D. Cal. 4:18-cv-07152-JST (invalidity judgment, Oct. 2019; fee motion denied Feb. 2020); RideApp v. Juno USA, S.D.N.Y. 1:18-cv-11579; a further S.D.N.Y. case 1:18-cv-06625; Ga. N.D. 1:19-cv-02507. Stanford NPE database: https://npe.law.stanford.edu/patent/6697730
• 2026 activity using '730's disclosure as prior art (not against '730): IPR2026-00308, Uber Technologies, Inc. and Uber Freight US LLC v. Carma Technology, Ltd. (filed Mar. 12, 2026; US 11,017,668; Petitioner Exhibit 1030 = US 2001/0037174 A1 to Dickerson, i.e., the '730 pre-grant publication). https://ai-lab.exparte.com/case/ptab/IPR2026-00308/uber-technologies-inc-v-carma-technology-ltd
• Term: expired Apr. 4, 2021 — no enforceable term remains, which is also why no 2026 enforcement litigation against the '730 patent itself appears.

Explicit uncertainties / discrepancies I will not paper over

1. Full claim text — not verified by me; claims 2, 3, 6 are characterized above only as recited by the Federal Circuit. Claim 1 is unverified, and I do not know the total claim count.
2. Priority date discrepancy between sources. Google Patents lists priority date 2000-04-04; one third-party aggregator (Unified Patents listing) shows 2000-04-03. The patent's own text says provisional 60/194,416 was "filed on Apr. 4, 2000." I treat 2000-04-04 as correct and flag the other as likely aggregator error.
3. Assignee field differs by source: the printed grant says Georgia Tech Research Corp.; Google Patents' "current assignee" says Rideapp Inc; one aggregator lists "Dickerson Stephen L" with priority 2000-04-03. The assignment chain above reconciles these, but the "current assignee" field should be treated as a database annotation, not a legal conclusion (Google itself disclaims this).
4. Prior-art name spelling differs across the record ("Schmier" in the patent text vs. "Schnier" in one OCR'd reproduction). I have not independently verified which is correct.
5. I found no CAFC 2026 docket naming 6697730. If you have a specific 2026 case number in mind, it does not appear in any indexed source I retrieved, and I would not infer one.

I'll research the litigation history for US patent 6697730. Let me search multiple sources.

Let me dig deeper into specific cases and outcomes.

Litigation Involving U.S. Patent No. 6,697,730

Patent: U.S. Patent No. 6,697,730 B2 ("Communications and computing based urban transit system") — the "'730 Patent"
Inventor: Stephen L. Dickerson | Owner/Plaintiff: RideApp, Inc. (assignee; ownership transferred from Georgia Tech Research Corp. to Dickerson in Feb./Apr. 2018, then to RideApp on May 7, 2018)

The '730 Patent was asserted in a coordinated campaign by RideApp against several ride-hailing/bike-share companies beginning in 2018. Below are the known cases.

1. District Court Litigation (Patent Infringement)

Key holding (Lyft litigation): The district court and Federal Circuit held the asserted means-plus-function limitations — including "a wireless means of on-demand allocation of a passenger to a specific vehicle" and "a wireless means of detecting the proximity of the passenger" — lacked the corresponding algorithmic structure required under Williamson, rendering claims 2, 3, and 6 invalid as indefinite. The Federal Circuit affirmed Nov. 26 → see RideApp, Inc. v. Lyft, Inc., No. 20-1284 (Fed. Cir. Mar. 25, 2021).

2. PTAB Post-Grant Proceedings (IPRs) — arising from the litigation

Both IPR petitions challenged claims 2, 3, and 6 of the '730 Patent on prior-art grounds (e.g., Behnke, Jaffe, Jones, Penzias). The Board denied institution. RideApp also argued in IPR2019-00414 that Uber Technologies, Inc. was an unnamed real party-in-interest (UPI/Uber relationship), citing the Applications in Internet Time standard. The PTAB never reached the merits of the prior-art challenge; instead the indefiniteness issues were resolved by the district court and Federal Circuit.

3. Sources

• NPE Litigation Database (Stanford): https://npe.law.stanford.edu/patent/6697730
• Federal Circuit opinion (20-1284): https://cases.justia.com/federal/appellate-courts/cafc/20-1284/20-1284-2021-03-25.pdf
• CourtListener opinion: https://www.courtlistener.com/opinion/[4867540](/patent/4867540)/rideapp-inc-v-lyft-inc/
• Law360 case page (RideApp v. Lyft): https://www.law360.com/cases/5d6861cbf842d407de173444/articles
• Unified Patents news: https://www.unifiedpatents.com/insights
• UniCourt docket (RideApp v. Uber, N.D. Ga.): https://unicourt.com/case/pc-db5-rideapp-inc-v-uber-technologies-inc-et-al-[129512](/patent/129512)
• PTAB IPR2019-00414 documents (RideApp Sur-Reply on RPI): docketalarm/U.S. PTO
• Patent-term record: https://patents.google.com/patent/[US6697730](/patent/US6697730)/en

4. Caveats / Gaps

• Not confirmed: The final disposition of the Juno (1:18-cv-11579) and Uber/Social Bicycles (1:19-cv-02507) cases. They were filed after the Lyft suit; given the Federal Circuit's March 2021 invalidation of the asserted claims, they may have been dismissed, stayed, or resolved by settlement, but I could not verify this. I do not know their outcome with confidence.
• Case-number discrepancy: The Google Patents record lists the N.D. Cal. Lyft case as 4:18-cv-07152, while multiple litigation databases/news sources cite it as 3:18-cv-07152. I have noted both. Per the strict rule, I have not silently harmonized them.
• IPR vs. litigation: IPR2019-00414 and IPR2019-00671 are USPTO Patent Trial and Appeal Board proceedings, not Article III litigation; they are included because they directly arise from and are part of the '730 Patent dispute history.

Summary: The known affirmative litigation over the '730 Patent is the RideApp campaign against Lyft (S.D.N.Y. → N.D. Cal. → Fed. Cir.), Juno (S.D.N.Y.), and Uber/Social Bicycles (N.D. Ga.). The only fully resolved track — the Lyft case — ended in invalidation of claims 2, 3, and 6 for indefiniteness, affirmed by the Federal Circuit on March 25, 2021. Two parallel IPRs (Lyft and Unified Patents) were both denied institution. The Juno and Uber matters' final outcomes are not confirmed here.

I'll research this before writing anything. Key tension up front: the structured ODP block says "no AIA trials on file," but the Google Patents family page embedded in the patent text lists two PTAB cases. Let me resolve that.

Two IPRs confirmed — and the structured data's petitioner attribution for one of them appears wrong. Let me dig into the decisions, the claim set, and the related litigation/appeal.

Strong material. Now let me confirm the reasoning in each institution denial, the full claim set, and the parallel district-court cases (esp. the Georgia action).

AIA Trial Proceedings — US 6,697,730 ("Communications and computing based urban transit system")

Reconciling the structured block first. The "PTAB proceedings on file" block says the ODP API returns no AIA trials for this patent. That block is incomplete, not exculpatory: two IPR petitions were filed against the '730 patent and both are documented on the PTAB docket and on the patent's own family page. I am not inferring these from the Google Patents "litigation" widget alone — each has docket-level corroboration (petition papers, institution decisions, a refund notice). I flag the ODP gap explicitly rather than treat it as an absence of art.

A second correction the reader needs up front. The Google Patents family page labels both PTAB entries with "Petitioner: Unified Patents PTAB Data." That string is Unified Patents' data-licensing attribution (the CC-BY "Unified Patents PTAB Data" feed), not a petitioner name. The actual petitioner in IPR2019-00414 was Unified Patents Inc.; the actual petitioner in IPR2019-00671 was Lyft, Inc. Two different petitioners, not one aggregator filing twice. Do not propagate the family-page label into a brief.

Proceedings overview

There are two AIA trial proceedings on the '730 patent — IPR2019-00414 (Unified Patents) and IPR2019-00671 (Lyft) — and both were denied institution, so there are zero claims canceled, zero claims sustained, zero settlements, and zero Final Written Decisions. The bottom line for a defendant today is not the IPR posture at all: the PTAB never narrowed this patent, but that is irrelevant, because asserted claims 2, 3, and 6 were held invalid as indefinite by the district court and the Federal Circuit affirmed on 2021-03-25, and the patent expired on 2021-04-04. If a demand letter cites claims 2, 3, or 6, it is citing dead claims from a dead patent.

IPR2019-00671 — Lyft, Inc. v. RideApp, Inc.

• Type: Inter Partes Review
• Filed: 2019-02-12
• Status: Institution Denied (PTAB/Google Patents status listed as "Not Instituted – Merits"). Institution decision 2019-08-12.
• Judge panel: Not confirmed. I was unable to retrieve the -00671 decision text and will not invent a panel. (Do not confuse it with the -00414 panel below.)
• Petition grounds: Seven separate grounds of unpatentability were asserted, per contemporaneous trade reporting (Mealey's, 2019-02-13). The petition challenged only three of the six claims — claims 2, 3, and 6. I could not verify the specific reference combinations or the precise statutory split (§ 102 vs. § 103) from a primary source; Lyft's petition is reported to have carried § 112 contentions as well, but § 112 is not an IPR ground, so that material would have been background only.
• Institution decision: Denied. Per the secondary source I could verify (Finnegan, "Ridesharing Dispute Exposes Differences Between Strong and Weak Patents," 2019-09-01), the Board never reached the prior-art merits: it found the "wireless means of on-demand allocation" and "wireless means of detecting proximity" limitations lacked sufficient corresponding structure to be construed, leaving the claims too vague to adjudicate, and the Board lacked authority to cancel claims on vagueness grounds. Treat that reasoning as reported-not-verified — I could not pull the decision PDF in this session, and this is the one factual link in my chain that rests on a law-firm client alert rather than the paper itself.
• Final Written Decision: None. Institution was denied, so no FWD issued and no claim-level validity determination was ever made by the Board.
• Settlement / termination: Not settled. After denial, the Board mailed a Notice of Refund on 2019-11-07, returning $15,000.00 in post-institution fees to Petitioner's deposit account (Paper 14). Petitioner's counsel: Baker Botts (Eliot Williams, Jeremy Taylor, Hyun Kyu Han). Patent Owner's counsel: Kasowitz (Ralph Gaskins).
• Appeal: None from this proceeding. There is no FWD to appeal, and no Federal Circuit appeal of IPR2019-00671 exists. (The only CAFC case in this saga, 20-1284, is an appeal from the district court — see below. Do not describe it as an appeal of either IPR.)
• Defensive value: The denial gives a defendant no § 315(e) estoppel benefit against Lyft and no adjudicated invalidity finding — but it also cost the patent owner nothing on the merits, because the merits were never reached. The real takeaway is procedural: the Board's inability to construe the means-plus-function limitations foreshadowed the district court's indefiniteness holding six weeks later.

IPR2019-00414 — Unified Patents Inc. v. RideApp, Inc.

• Type: Inter Partes Review
• Filed: 2018-12-12
• Status: Institution Denied (listed as "Not Instituted – Merits"). Institution decision 2019-07-17.
• Judge panel: Mitchell G. Weatherly, Jason W. Melvin, and Aaron W. Moore, Administrative Patent Judges. Melvin authored.
• Petition grounds: Two obviousness (§ 103) challenges directed at claims 2, 3, and 6 — each of which is independent. The Board's decision recites that "Petitioner, Unified Patents, Inc., filed a Petition … requesting inter partes review of claims 2, 3, and 6 ('the challenged claims')." Unified's own internal announcement (Exhibit 1011) described the '730 patent as "directed to a transit system based on cellular communication, GPS locating technology, and digital computers" and characterized RideApp as an NPE. The primary reference appears to be Penzias, with the petition's theory contested on whether Penzias disclosed "tracking passenger transportation vehicle usage" and "three-way wireless communication."
• Institution decision: Denied. The Board's reasoning, quoted verbatim: "For the reasons set forth below, we conclude that Petitioner has not shown a reasonable likelihood it will prevail in establishing the unpatentability of at least one challenged claim. We, therefore, do not institute inter partes review of the challenged claims." Patent Owner's Preliminary Response had also pressed a threshold defect: that the petition failed to name Uber Technologies, Inc. as a real party-in-interest, arguing Uber was "a clear beneficiary of the Petition" and that the IPR was filed only after RideApp approached Uber about a license. The Board denied on the merits (no reasonable likelihood) and did not rest its denial on the RPI theory — so the RPI argument is preserved as an argument, not a holding.
• Final Written Decision: None issued. No claim was canceled; no claim was sustained.
• Settlement / termination: Not settled; the proceeding simply ended at the § 314 threshold.
• Appeal: None. No FWD, no appeal.
• Defensive value: Because there was no FWD, § 315(e)(1)–(2) estoppel never attached to Unified (or to Lyft in -00671) — a defendant cannot borrow estoppel from either proceeding. Correspondingly, the prior art these petitioners assembled was never publicly tested on the merits, so it is unvetted: usable, but not "IPR-proven."

⚠️ Docket-filename trap. The -00414 institution decision is hosted at a file literally named Institution_Decision-15-Trial_Instituted_Document.pdf. The document itself is captioned "Decision Denying Inter Partes Review — 35 U.S.C. § 314." The filename is wrong/auto-generated. Do not cite it as an institution.

Related district court and Federal Circuit activity (context — not PTAB)

• RideApp, Inc. v. Lyft, Inc., No. 18-cv-07152-JST (N.D. Cal.) (also docketed as 3:18-cv-7152 and 4:18-cv-07152). RideApp asserted claims 2, 3, and 6. In its 2019-10-16 claim construction order, 2019 WL 7834175, the court held four computer-implemented means-plus-function limitations indefinite under Williamson v. Citrix Online and entered final judgment for Lyft.
• RideApp, Inc. v. Lyft, Inc., No. 20-1284 (Fed. Cir.), appeal filed 2019-12-23, opinion issued 2021-03-25, nonprecedential, AFFIRMED: "Because we agree with the district court that the on-demand allocation and proximity limitations are indefinite, we affirm without addressing the tracking and distributing or expected arrival time limitations." — https://www.courtlistener.com/opinion/[4867540](/patent/4867540)/rideapp-inc-v-lyft-inc/ and https://cases.justia.com/federal/appellate-courts/cafc/20-1284/20-1284-2021-03-25.pdf
• Other docketed actions on the family page — S.D.N.Y. 1:18-cv-06625 (filed 2018-07-23) and 1:18-cv-11579, and N.D. Ga. 1:19-cv-02507 — I could not verify the parties for the Georgia action in this session and will not guess. Unified's press release states the '730 patent was "asserted in district court litigation against Lyft and Juno," and RideApp's POPR references Uber, so treat Uber/Juno involvement as likely but unconfirmed here.

Strategic summary

Claim status: none of the six claims is "canceled" by the PTAB, but the three that were ever asserted are invalid. The '730 patent issued with six claims. Claims 2, 3, and 6 — all independent, all sharing the "central data system for tracking passenger transportation vehicle usage and distributing periodic invoices" and "plurality of communication devices" limitations — were the only claims RideApp asserted or anyone challenged, and they were invalidated for indefiniteness by the N.D. Cal. court and affirmed by the Federal Circuit. Claims 1, 4, and 5 were never asserted and never challenged in any IPR; I could not verify their text in this session, so treat them as genuinely UNTESTED rather than implicitly dead. Do not tell a court that "the patent was canceled" — it wasn't, and the mechanism matters: this was a court invalidity judgment plus expiration, not a PTAB cancellation.

Estoppel: there is none, and that cuts in an unusual direction. IPR estoppel under 35 U.S.C. § 315(e)(1)–(2) is triggered by a final written decision, not by a denial of institution. Neither proceeding produced one. Lyft and Unified are therefore not estopped from re-raising the grounds they briefed, which means the Unified/Lyft prior-art combinations remain theoretically available to a third-party defendant — but also that no one has a merits ruling blessing them. If you are defending today, your strongest invalidity evidence is not prior art at all: it is the 2019 WL 7834175 judgment plus the 20-1284 affirmance on indefiniteness. That is preclusive against the patent owner on claims 2, 3, and 6.

Pattern signals. Unified Patents — a defensive aggregator — was first to file (2018-12-12), four days before Lyft's own later petition in February 2019, in two different forums (S.D.N.Y., then N.D. Cal.), with the Board denying Unified's RPI objection unmade. RideApp's POPR framed Uber as the unseen beneficiary of the Unified petition, but the Board never adopted that framing. The patent owner litigated aggressively (through the Federal Circuit) and lost everything that was actually adjudicated. There is no indication of any third IPR, any rehearing request, or any Director review — and no reason for one now.

The expiration point that ends the analysis. The patent's term ran out on 2021-04-04 (20 years from the 2001-04-04 filing; status "Expired – Lifetime"). As of today (2026-09-30) there is no ongoing infringement to enjoin, and the § 286 damages window reaches back only to 2020-09-30 — a period that begins after the invalidity judgment in N.D. Cal. and is entirely covered by the affirmed final judgment. Past-damages exposure to a defendant who was never a party is, at best, theoretical and barred by Blonder-Tongue.

Recommended next steps

1. If the demand letter cites claims 2, 3, or 6 (the only claims ever asserted): reject and cite the disposition. The Federal Circuit held: "Because we agree with the district court that the on-demand allocation and proximity limitations are indefinite, we affirm without addressing the tracking and distributing or expected arrival time limitations." *RideApp, Inc. v. Lyft, Inc., No. 20-1284 (Fed. Cir. Mar. 25, 2021) (nonprecedential) — https://cases.justia.com/federal/appellate-courts/cafc/20-1284/20-1284-2021-03-25.pdf and https://www.courtlistener.com/opinion/4867540/rideapp-inc-v-lyft-inc/. Add Blonder-Tongue collateral estoppel and the 2021-04-04 expiration.
2. If it cites claims 1, 4, or 5: these were never asserted and never challenged, so there is no judgment covering them. But note that the same § 112(b) Williamson attack that killed claims 2, 3, and 6 targets recited means terms, and any claim sharing the "central data system for tracking … and distributing periodic invoices" and "plurality of communication devices" limitations is exposed to the identical argument that the specification discloses no algorithm. Verify the claim text before asserting this — do not assume claim 1 mirrors claim 2.
3. If you are contemplating an IPR: don't. The patent expired 2021-04-04; there is nothing to invalidate prospectively, the asserted claims are already judicially dead, and two prior petitions were denied at the § 314 threshold. The correct vehicle is a court-based invalidity or Blonder-Tongue defense, not a PTAB filing.
4. Flag the data-quality issue internally. The ODP "no AIA trials" block missed two docketed proceedings, and the family page mislabels the IPR2019-00671 petitioner as Unified. If your conflicts, diligence, or monitoring workflow relies on those two feeds, they will under-report PTAB activity on non-instituted proceedings and attribute Unified's data license as a petitioner name.

Verification gaps I want to name explicitly: (a) I could not retrieve the IPR2019-00671 institution decision text, so its reasoning and judge panel rest on a secondary source and are unconfirmed; (b) I could not confirm the specific prior-art references in Lyft's seven grounds or in Unified's Penzias-based challenges beyond what is quoted above; (c) I could not verify the text of claims 1, 4, and 5 or the parties to N.D. Ga. 1:19-cv-02507. Everything else above is anchored to a docket entry, a decision, or the patent itself.

I'll research the assignment record for US 6697730 across the sources you specified.

Good — I have two reel/frames. Let me find the RideApp recording and the correspondent details.

Let me pin down the RideApp recording and check for any further post-2018 transfers.

Assignment & Ownership Analysis — US 6,697,730 B2

Source note (important for provenance): I could not open the USPTO Assignment Center directly in this session, and my search budget closed before I could pull the fourth (RideApp) record. The reel/frame data below is taken from a USPTO "Assignment Abstract of Title" reproduced verbatim inside the '730 PTAB exhibit LYFT, INC. v. RIDEAPP, INC., IPR2019-00671, Ex. 1002 (a Derwent/INPADOC export dated 2018-08-13 capturing the USPTO reassignment table), cross-checked against Google Patents legal events and RideApp's own pleadings. Where a reel/frame or correspondent is not confirmed I say so rather than fill it in. Verify at https://assignmentcenter.uspto.gov/ (search by patent number 6697730) or the legacy https://assignment.uspto.gov/patent/index.html.

Inventors

Unusual patterns — two worth flagging:

1. A single inventor asserting a 17-year-dormant university patent. The classic red flag ("all inventors depart the assignee within 12 months") is absent — there is only one inventor. The analogous anomaly here is temporal: GTRC held the patent from 2001 to 2018 and, on RideApp's own admission, "licensed the '730 Patent but made no effort to enforce it against any infringing parties during the time that it held the patent by assignment" (S.D.N.Y. Compl. ¶14). The patent then reverted to the inventor and was asserted against three ride-hailing defendants within ~11 weeks.
2. Emeritus status + obligation-to-assign. Dickerson assigned to GTRC as a "faculty member" obligation even though he had retired in 1996 and the invention post-dates his retirement. The reversion in 2018 was negotiated directly between Dickerson and GTRC — a bilateral unwinding of the original obligation, not a market sale.

Original assignee

Georgia Tech Research Corporation (GTRC), Atlanta, GA — named in the (73) field of the printed grant.

• Primary line of business: GTRC is the technology-transfer / sponsored-research contracting arm of the Georgia Institute of Technology — a nonprofit whose business is IP administration and licensing. It is, by design, a non-practicing licensing entity (though a university-affiliated one, not an NPE in the troll sense).
• Product embodying the claims: None. No commercial product was ever shipped. The Register's coverage states the patent "was never developed into an idea" commercially; RideApp's complaint describes GTRC as a passive licensor that never enforced.
• Current status: Operating (GTRC remains an active Georgia Tech affiliate as of my training data — flagging that I did not independently re-verify this via a 2026 filing because my search budget closed). It was not in bankruptcy, and there is no recorded security interest, lien, merger, or change-of-name in the chain.

Assignment timeline

The chain consists of four recorded assignments (three confirmed reel/frames + one confirmed event whose reel/frame I could not retrieve).

1. 2001-04-04 (executed) / recorded 2001-04-04 — Reel 011685/0781

• Conveyance: Assignment of Assignors' Interest
• Assignor: Dickerson, Stephen L. (Atlanta, GA)
• Assignee: Georgia Tech Research Corporation (Atlanta, GA)
• Correspondent: Charles Vondran, Troutman Sanders LLP, Bank of America Plaza, Suite 5200, 600 Peachtree Street NE, Atlanta, GA 30308-2216
• Context: Internal obligation-to-assign (faculty invention) — the original university assignment, executed on the filing date of the '730 application.

2. 2018-02-09 (executed) / recorded 2018-02-20 — Reel 044979/0797

• Conveyance: Assignment of Assignors' Interest
• Assignor: Georgia Tech Research Corporation
• Assignee: Dickerson, Stephen L. (Atlanta, GA)
• Correspondent: Ryan Schneider, Troutman Sanders LLP, 600 Peachtree St NE, Ste 3000, Atlanta, GA 30308
• Context: Reversion / transfer back to inventor — negotiated unwinding of the 2001 obligation; this is the instrument that created standing for the 2018 campaign.

3. 2018-04-20 (executed) / recorded 2018-04-26 — Reel 045646/0769

• Conveyance: Assignment of Assignors' Interest (see document for details)
• Assignor: Georgia Tech Research Corporation
• Assignee: Dickerson, Stephen L. (Sandy Springs, GA)
• Correspondent: Benjamin Balser, 303 Perimeter Center North, Suite 300, Atlanta, GA 30346 — different correspondent and different address from both prior Troutman Sanders recordings.
• Context: Corrected assignment — RideApp's complaint (¶15) states the February reversion was superseded by "a corrected assignment subsequently recorded on April 26, 2018." A same-conveyance re-recording 65 days later indicates a defect was cured (likely the inventor's address and/or document formalities) shortly before the patent was moved to the asserting entity.

4. ~2018-05 (executed) / recorded 2018-05-07 — Reel NNNNNN/NNNN (NOT CONFIRMED)

• Conveyance: Assignment of Assignors' Interest (see document for details) — per Google Patents legal events
• Assignor: Dickerson, Stephen L.
• Assignee: RideApp, Inc.
• Correspondent: Not retrieved — I flag this as a gap. It is the single most probative data point in the whole chain (the correspondent who filed the transfer-to-asserter recording), and I will not guess it.
• Context: Transfer to the asserting entity — the inventor's own newly formed, non-practicing transportation company, recorded ~11 weeks before the first infringement suits.

Corroboration / discrepancy note: RideApp's S.D.N.Y. complaint (¶15) independently states the RideApp recording date was May 7, 2018, matching Google Patents. The Derwent/INPADOC legal-status table reproduced in the 2018 PTAB exhibit lists only three AS events (2001-04-04, 2018-02-20, 2018-04-26) and omits the May 7 entry — most plausibly INPADOC lag, since the export predates the pleading that confirms the date. It is not evidence that the RideApp recording does not exist.

No records found for: security agreements, licenses, releases, mergers, change-of-name (other than the above), or any transfer to a defensive aggregator (RPX / AST / LOT / Unified / OIN).

Timeline diagram

timeline
    title Ownership of US 6697730
    2001 : Filed by Stephen L Dickerson
         : Assigned to Georgia Tech Research Corp
    2004 : Patent issued
    2018 : Returned to Dickerson reel 044979 0797
         : Corrected assignment reel 045646 0769
         : Assigned to RideApp Inc
         : Suits filed against Lyft and Juno
    2019 : PTAB IPRs denied institution
    2021 : Patent expires Apr 4
         : CAFC affirms invalidity

NPE / troll-pattern signals

Verdict

NPE — moderate confidence.

Justification: The patent's current owner, RideApp, Inc. (rec. 2018-05-07), is a non-practicing entity — no product embodies the claims and the company was formed only months before litigation — and the assertion was enabled by a strong pre-litigation transfer (transfer recorded 2018-05-07, first suit filed 2018-07-23, ~11 weeks) sitting atop a cascading reversion chain (Reels 044979/0797 of 2018-02-20 and 045646/0769 of 2018-04-26, both GTRC→Dickerson, executed within 12 weeks of the transfer to RideApp) plus a repeat correspondent at Troutman Sanders across Reels 011685/0781 and 044979/0797. I stop at moderate rather than high confidence because the classic aggregator markers are absent: there is no shell LLC, no known-asserter link, no correspondent recurrence into the RideApp recording (that correspondent is unretrieved), and the owner is the sole named inventor with a genuine 1999–2000 R&D provenance — this reads as a solo-inventor monetization vehicle, not a portfolio troll.

Verify at: https://assignmentcenter.uspto.gov/ (search "6697730") or https://assignment.uspto.gov/patent/index.html (same records). The two open items to pull there are (a) the reel/frame and correspondent of record for the 2018-05-07 RideApp assignment, and (b) confirmation that no fifth assignment (e.g., a security interest or a transfer to a successor entity) exists post-2018.

I'll search the USPTO and related sources for each patent cited on the face of US 6,697,730. Let me batch these.

Let me search the remaining cited references.

Prior-art analysis for US 6,697,730 B2

0. Method and confidence conventions (read this first)

I confirmed the patent's identity against the authoritative full text supplied with this task and against the Google Patents record for US 6,697,730 B2 (app. 09/826,272, filed Apr. 4, 2001, issued Feb. 24, 2004). I then attempted to retrieve each reference printed on the face of the patent. Because my search budget was exhausted partway through that second pass, I flag each entry below as:

• [V] Verified — the reference's title/date was returned in my searches this session.
• [R] Record-based — characterized from the '730 prosecution/PTAB record I retrieved, not from the reference itself.
• [K] Training-knowledge, unverified — I have a recollection but could not confirm it this session; treat as provisional.
• [X] Not retrieved — I have no reliable basis and will not guess.

Important caveat carried over from the earlier sections: the printed grant's independent claims (per the Federal Circuit's recitation) are claims 2, 3 and 6, and the '730 was ultimately invalidated for § 112 indefiniteness, not on any § 102 ground. The '730's effective filing is 2001, so pre-AIA 35 U.S.C. § 102 governs (the AIA first-inventor-to-file provisions apply only to applications filed on/after Mar. 16, 2013). Any § 102 mapping below is therefore provisional and framework-level, not a verbatim element-by-element chart.

A note on the file history I retrieved: the '730 prosecution record (RideApp/Lyft Exhibit 1002) refers to then-pending claims 1, 38, 43, 66 and 69. Those numbers do not all survive into the grant (independent claims 2, 3, 6 per the CAFC). So where I cite the examiner's rejection, the claim numbers are the pre-grant numbers — I say so explicitly rather than silently translating.

1. References cited on the face of US 6,697,730

1.1 US 4,220,946 — Henrici [X]

• Citation: U.S. Pat. No. 4,220,946, inventor Henrici (as printed on the '730 face).
• Date: Not retrieved.
• Note: A search on "4,220,946 Henrici" returned U.S. Pat. No. 4,236,946 (Aboaf et al., "Amorphous magnetic thin films with highly stable easy axis," NC State repository, 1980). That is a different patent number and is unrelated to transit — I am not conflating it with 4,220,946.
• Description / § 102 relevance: Cannot assess. I will not fabricate a subject matter for this reference.

1.2 US 5,187,810 — Yoneyama et al. [K]

• Citation: U.S. Pat. No. 5,187,810, Yoneyama et al. This one is expressly discussed in the '730 specification: "U.S. Pat. No. 5,187,810 to Yoneyama et al. ('810)."
• Date: unverified (early 1990s).
• Description [K]: navigation/positioning apparatus.
• § 102 relevance: At most tangential — route guidance/positioning. Would not, on its face, reach the "central data system … distributing periodic invoices" or "wireless means of on-demand allocation" limitations. Flagged as low-confidence.

1.3 US 5,493,295 — Lewiner et al. [K]

• Citation: U.S. Pat. No. 5,493,295, Lewiner et al. Also discussed in the '730 specification as "('295)."
• Date: unverified (mid-1990s).
• Description [K]: vehicle/fleet monitoring and locating.
• § 102 relevance: Bears only on the vehicle tracking/locating aspect (the "vehicle usage" monitoring component). Nothing on passenger-side on-demand allocation or invoicing.

1.4 US 5,623,260; 5,657,010; 5,668,543 — all to Jones [R]

• Citation: the three Jones patents listed on the '730 face.
• Description [R]: This is the vehicle-arrival-notification family. The PTAB petition record I retrieved characterizes "Jones" as "a vehicle notification system that notifies users of the impending arrival of a vehicle … at a particular vehicle stop," comprising "an on-board vehicle control unit VCU (12) … and a base station control unit BSCU (14)," with an "update message" … "when a particular vehicle is delayed" (petition quoting Ex. 1006 at Abstract and col. 31).
• Dates [K]: likely mid-1997 (I could not confirm the individual issue dates this session).
• § 102 relevance — this is the most important face-cited family for the passenger-notification limitations:
  • The petition asserted Jones renders the "wireless means of informing the passenger of the assignment and updated expected arrival time" limitation obvious (relevant to claim 3) and the "wireless means of detecting the proximity of the passenger and alerting the passenger of the proximity of the vehicle" limitation obvious (relevant to claim 6), when combined with Behnke.
  • So: Jones is not a standalone anticipation reference for any independent claim, but it is the reference that supplies the notification/proximity elements the other art lacks. Source: https://ptacts.uspto.gov/ptacts/public-informations/petitions/[1523675](/patent/1523675)/download-documents?artifactId=pJjPFl80JXDps4XUPTpmw14e4ARZAms-0C9pczkWeYUNBAs2Q3923FU

1.5 US 5,739,774 — Olandesi, "Mass transit monitoring and control system" [V]

• Citation: U.S. Pat. No. 5,739,774; issued April 14, 1998 (confirmed from the printed header).
• Description [V]: a distributed mass-transit monitoring/control system: a plurality of stop units, a plurality of vehicle units, and computing means. Vehicles exchange information with stop units over short-range communication links; the stop units disseminate expected arrival times to waiting passengers; the system monitors schedule adherence and issues updates to all downstream stops (and can combat "bunching").
• § 102 relevance: Directly bears on:
  • the "wireless means of informing the passenger" limitation (relevant to claim 3); and
  • the vehicle tracking/schedule-monitoring component of the claimed "central data system."
• Not disclosed: on-demand matching of a passenger request to a specific vehicle, and periodic invoicing. So it does not anticipate a full independent claim; it is a § 103 building block.
• Sources: https://patentimages.storage.googleapis.com/40/51/1c/15c60d932bde77/US5739774.pdf ; http://www.everypatent.com/comp/pat5739774.html

1.6 US 5,799,263 — Culbertson, "Public transit system and public transit dispatching apparatus and method" [V]

• Citation: U.S. Pat. No. 5,799,263; issued August 25, 1998.
• Description [V]: a "transit cell" architecture. A dispatching computer receives user requests (preferably by telephone; caller-ID captured), associates request/destination telephone numbers with locations, and assigns each transit request to a matching intracell vehicle route; explicitly aimed at eliminating vehicle backtracking. The reference itself distinguishes U.S. Pat. No. 5,168,451 (Bolger), a "user responsive transit system" with automatically dispatched small vehicles and request terminals in cells.
• § 102 relevance: This is the closest face citation on the "matching a passenger's trip request with … transit parameters to determine vehicle assignment and routes" step (the heart of claims 2/3). But Culbertson uses landline telephones and fixed request terminals — no wireless passenger device, no GPS, no periodic invoicing — so it cannot anticipate the wireless/invoicing limitations.
• Source: https://patentimages.storage.googleapis.com/af/be/a0/48026b17b544ec/US5799263.pdf
• (Useful side note: the same search surfaced a Justia citation table listing "5799263 | August 25, 1998 | Culbertson.")

1.7 US 5,818,356 — Schuessler, "Method and device for guiding vehicles as a function of the traffic situation" [V]

• Citation: U.S. Pat. No. 5,818,356; issued October 6, 1998.
• Description [V]: a control center receives vehicle data anonymously, computes an optimum route as a function of current traffic, and transmits intermediate-destination/route data to a vehicle-end navigation device (via GSM mobile radio or RDS-TMC). The vehicle end then issues optical/audible guidance — no on-board road-network map required.
• § 102 relevance: Bears on the "central assigning/routing + wireless downlink to the vehicle" aspect and on dynamic re-routing. Nothing passenger-facing; no ride-matching on a rider request; no invoicing.
• Sources: https://patentimages.storage.googleapis.com/3f/6c/fb/061167f57bfe9a/US5818356.pdf ; https://uspto.report/patent/grant/5818356

1.8 US 5,867,780 — Malackowski et al. [K]

• Citation: U.S. Pat. No. 5,867,780, Malackowski et al.
• Date/description [K]: vehicle tracking/locating (GPS-based); unverified.
• § 102 relevance: tracking/locating component of the "central data system."

1.9 US 5,987,377 — Westerlage et al., "Method and apparatus for determining expected time of arrival" [V]

• Citation: U.S. Pat. No. 5,987,377; issued November 16, 1999; 52 claims.
• Description [V]: a dispatch remotely located from the vehicle generates destination information; a mobile unit on the vehicle (with a satellite positioning system) determines vehicle position and computes the expected time of arrival; a cellular communications link couples dispatch and mobile unit; ETAs update continuously and the vehicle can transmit "late" information back. (The '377 patent was itself heavily litigated — Vehicle IP v. AT&T Mobility — which confirms the ETA/mobile-unit architecture.)
• § 102 relevance: This is arguably the most technically on-point face citation for the claimed tracking + expected-arrival-time updating functionality. However:
  • it is vehicle-centric, with no passenger terminal making an on-demand trip request;
  • it has no periodic invoicing; and
  • no passenger/vehicle proximity alert.
    So § 103 combination material, not standing anticipation.
• Sources: https://uspto.report/patent/grant/5987377 ; https://www.ptablitigationblog.com/wp-content/uploads/2018/07/Paper-9.pdf

1.10 US 6,006,159 — Schmier et al. [R] — the legally operative face citation

• Citation: U.S. Pat. No. 6,006,159, Schmier et al. (also discussed in the '730 specification as "('159)").

• Date [K]: issued c. Dec. 21, 1999 (unverified).

• Description / § 102 relevance — from the '730's own file history [R]: The examiner-rejection text I retrieved states verbatim:

  "As per claims 1, 43, 66 and 69, Schmier teaches a central assignment system for matching a passenger's trip request with transit parameters to determine vehicle assignment and routes wherein the transit parameters and passenger location are obtained via wireless communication devices (figure 1 and abstract). Schmier teaches the use of a public transit vehicle (column 1, lines 1–14)…" (and, for claim 38, Schmier teaches receiving data from the passenger's communication device re: a trip request, processing it centrally, transmitting route alternatives to the passenger's device, and receiving additional data.)

  This shows Schmier was applied against the pre-grant claim set (1, 38, 43, 66, 69) as the primary reference, with the public/private-vehicle integration being supplied by an obviousness rationale.

• Note on the spelling discrepancy flagged earlier: the earlier sections noted "Schmier" (patent text) vs. "Schnier" (one OCR'd reproduction). My searches this session returned "Schmier" in the prosecution record and petition text — consistent with the authoritative full text. I therefore treat "Schmier" as correct.

• Source: https://www.docketalarm.com/cases/PTAB/IPR2019-00671/Lyft_Inc._v._RideApp_Inc/docs/02-12-2019-Petitioner/Exhibit-1002-Ex_1002___File_History.pdf

1.11 US 6,085,976 — Schurzum [X]

• Citation: U.S. Pat. No. 6,085,976, Schurzum (per the '730 face).
• Date/description/§ 102 relevance: Not retrieved. No verified basis. (Its number range suggests issuance in 2000, which would place it in the § 102(a) window — but I am not asserting this.)

1.12 US 6,313,760 — Jones [K]/[R]

• Citation: U.S. Pat. No. 6,313,760, Jones.
• Description [R]: same advance-notification family as § 1.4 (same VCU/BSCU notification architecture).
• Date [K]: issued c. Nov. 6, 2001 — i.e., after the Apr. 4, 2001 filing. If cited, it would be § 102(e) art (a U.S. patent by another, effective as of its earlier filing), not § 102(a)/(b).
• § 102 relevance: same as § 1.4 (claims 3 / 6 notification-proximity elements).

1.13 US 6,363,488 — Ginter et al. [K]

• Citation: U.S. Pat. No. 6,363,488, Ginter et al. (Intertrust-style trusted-computing family).
• Date [K]: issued c. Mar. 26, 2002 — after the '730 filing; likely § 102(e) art only.
• § 102 relevance [K, low confidence]: presumably cited for secure identification / usage-metering / electronic-billing concepts (relevant to the "distributing periodic invoices" and low-power-ID enabling features). I could not verify this and flag it as speculative.

1.14 US 6,397,057 and US 6,411,803 — Malackowski et al. [K]

• Citation: the two later Malackowski patents on the '730 face.
• Date [K]: issued 2002 (post-filing → § 102(e) only).
• Description [K]: vehicle-tracking family (same lineage as § 1.8).
• § 102 relevance: tracking/locating.

2. Critical-date framework (why the face citations split the way they do)

Using the '730's Apr. 4, 2001 filing date and Apr. 4, 2000 earliest priority as anchors (pre-AIA § 102):

The practical takeaway: the four post-filing-era citations on the face ('760, '488, '057, '803) could only have come in as § 102(e) secret prior art; the examiner's real § 102/§ 103 thrust was the pre-2000 group, dominated by Schmier '159 and the Jones notification family.

3. The most relevant prior art — and it is largely OFF the face of the patent

This is the analytically important finding. The genuinely closest art to the '730's independent claims was not cited on the face of the patent; it surfaced in the 2019 IPR petitions (Lyft v. RideApp, IPR2019-00414 / -00671, both not instituted).

3.1 US 4,360,875 — Behnke, "Flexible-route transportation system," issued Nov. 23, 1982 [V]

• Description [V] (per the IPR record quoting Behnke): a flexible-route ridesharing system "primarily utilizing privately-owned vehicles," with interactive terminals for drivers (ride offers) and riders (ride requests) linked by a telecommunications network to a **"central operations coordinating station, equipped with a general-purpose programmable computer."* The central station matches ride requests with ride offers trip-by-trip, then "transmits to the driver the rider's identity and location and transmits to the rider the description and identity of the vehicle." Critically, it "includes security features … accounting features for properly billing riders and reimbursing vehicle owners … and special terminals for entering trip information."
• § 102 relevance: This single reference appears to disclose, in substance:
  • a central computer that matches a passenger's trip request to a specific vehicle (→ claim 2's on-demand allocation, though Behnke's terminals are not cellular);
  • informing the rider of the vehicle description/identity (→ claim 3); and
  • automated billing of riders / reimbursement of owners (→ the "distributing periodic invoices" limitation).
    This is why the IPR petitioner paired Behnke + Jones to attack claims 2, 3 and 6. It is the closest single reference in the whole record and was not before the examiner.
• Sources: https://patents.justia.com/patent/[11288960](/patent/11288960) (citation table showing "4360875 | November 23, 1982 | Behnke"); https://ptacts.uspto.gov/ptacts/public-informations/petitions/[1540825](/patent/1540825)/download-documents?artifactId=YY2CNiy0mopyBylMt4B8cx7MpnXcydiqcKCEzLXxUf7LMnRk-nJ6z2w

3.2 "Jaffe" — dispatch system (patent number not verified) [R]

• Description [R] (per the IPR petition): "a request dispatch system for assigning an 'operator driven mobile unit' with a requesting user," with portable user terminals and operator terminals wirelessly communicating with a control center that assigns an operator to a user on request; after assignment, "the control center sends vehicle identifiers and estimated time of arrival to the passenger," and "the control center further includes an accounting module for handling periodic payments from the users." Operator-driven mobile units include taxis.
• § 102 relevance: The petition's Ground 4 asserted that claims 2, 3, and 6 are anticipated by Jaffe — i.e., a straight § 102 anticipation theory on the very claims later invalidated. This is the most direct § 102 assertion anywhere in the '730 record. I could not verify Jaffe's patent number and decline to guess it.
• Source: https://ptacts.uspto.gov/ptacts/public-informations/petitions/1523675/download-documents?artifactId=pJjPFl80JXDps4XUPTpmw14e4ARZAms-0C9pczkWeYUNBAs2Q3923FU

4. Bottom line

1. Single-reference § 102 (anticipation) candidates: On this record, the only references plausibly anticipating an independent claim outright are the off-face references Behnke '875 (claims 2/3, and the billing limitation) and Jaffe (petition-asserted as anticipating claims 2, 3 and 6). I do not see a face-cited reference that anticipates any independent claim on its own.
2. Best face-of-patent art: Schmier '159 is the examiner's primary reference (pre-grant claims 1, 38, 43, 66, 69); Westerlage '377 covers ETA/tracking; Culbertson '263 covers request-to-route matching; Olandesi '774 and the Jones family cover passenger arrival/proximity notification; Schuessler '356 covers central traffic-based routing.
3. Material caveat: The '730 was invalidated on § 112 indefiniteness (claims 2, 3, 6) and both IPRs were not instituted, so no § 102 ground ever carried the day. The prior art above is therefore of historical/prosecution-interest value, not the basis of the patent's demise.

Open items I could not resolve (stated rather than filled in)

• US 4,220,946 (Henrici), US 6,085,976 (Schurzum): not retrieved; no basis to characterize. (Searching 4,220,946 returned the unrelated 4,236,946 — a different number.)
• Jaffe patent number: unverified.
• Issue dates for 5,187,810; 5,493,295; 5,623,260; 5,657,010; 5,668,543; 5,867,780; 6,006,159; 6,085,976; 6,313,760; 6,363,488; 6,397,057; 6,411,803: not confirmed this session (flagged [K] where I gave a recollection).
• Claim-number mapping: the file history's claim numbers ≠ granted claim numbers, so § 102 → claim mappings above are framework-level only.

If you have search budget to spare, the highest-value next step is retrieving the full text of US 6,006,159 (Schmier) and US 4,360,875 (Behnke) for a verbatim element-by-element chart against granted claims 2, 3 and 6.

I'll ground the prior-art characterizations before building the §103 analysis. Let me run targeted searches on the key references.

Good — the IPR petitions give me the actual §103 grounds asserted. Let me verify a few more of the cited references' subject matter before I build the combinations.

Preliminary framing (must read before the analysis)

Three threshold points govern everything below, and two of them are contradictions I want flagged rather than smoothed over:

1. The claims I am asked to analyze have already been held invalid — not for obviousness, but for indefiniteness. Claims 2, 3 and 6 were held invalid under 35 U.S.C. § 112 ¶ 2 (means-plus-function, Williamson v. Citrix), and the Federal Circuit affirmed in RideApp, Inc. v. Lyft, Inc., No. 20-1284 (Fed. Cir. Mar. 25, 2021). A § 103 analysis presupposes a definite claim scope to compare against the art. Here there is none, which is precisely why the Board never reached the merits of any § 103 ground — the Jellicoe declaration in IPR2019-00671 addresses "Behnke Fails To Teach all Elements," and the Board denied institution in both IPR2019-00414 and IPR2019-00671. So the grounds below are advocacy-grade reconstructions, not adjudicated invalidity.
2. I do not have verbatim claim text. The independent-claim recitations I use below are those quoted in the Federal Circuit opinion and in the IPR petition/exhibit record (e.g., Jellicoe Ex. 2003, https://www.docketalarm.com/cases/[PTAB](/ptab)/IPR2019-00671/Lyft_Inc._v._RideApp_Inc/docs/05-22-2019-Patent_Owner/Exhibit-2003-Jellicoe_Declaration.pdf). The opening limitation of claims 2/3/6 was not captured verbatim in any source I retrieved; I mark it as unverified and do not rely on it.
3. Legal effect of item 1 on § 103: because the claims are means-plus-function, the prior art must be mapped not merely to the recited function but to the corresponding structure/algorithm disclosed in the '730 specification. The district court found no such algorithm for the on-demand-allocation and proximity limitations. This means the strongest § 103 grounds (which map to those very functions) are also the grounds that are analytically unstable. I note this at each step rather than hiding it.

Representative person of ordinary skill in the art (POSITA)

I could not verify a stipulated POSITA from the record. On the art itself I would use: a person with a bachelor's degree in electrical engineering, computer science, or transportation engineering, plus 2–3 years' experience with demand-responsive transit dispatch, wireless data communication and vehicle-location systems, or equivalent. ⚠️ Flagged as my construction, not the parties'.

The prior-art landscape actually relied on

Element-by-element mapping (claims 2, 3, 6)

The § 103 combinations and the motivation to combine

Graham/KSR framework: scope and content of the art; differences; PHOSITA level; secondary considerations. Motivation rationales are drawn from KSR (predictable use of prior-art elements; known technique improving a similar device; obvious to try; design/market incentives).

Ground 1 — Behnke in view of Jones (strongest on the paper record)

Behnke supplies nearly the whole architecture: a central assigning computer, wireless rider and in-vehicle terminals, rider-to-specific-vehicle matching, transmission of the vehicle's identity and ETA to the rider, and periodic account-based billing of riders and periodic payment to drivers. Jones supplies the GPS-based on-board unit and the threshold-triggered arrival/proximity notification. Motivation: Behnke itself states the rider "should be informed as to the vehicle's identity and estimated time of arrival"; Jones teaches a better (GPS-derived, distance-triggered) way of performing exactly that function — KSR's "known technique to improve a similar device" and "predictable result" rationales; both are in the same field of demand-responsive/advance-notification transit. This was the asserted ground, and PO's rebuttal was that Behnke "teaches away" from tracking (it uses telephone numbers rather than vehicle tracking) and lacks three-way communication. That is the best available rebuttal and should be taken seriously.

Ground 2 — Jaffe alone, or Jaffe in view of Jones and/or the knowledge of a POSITA

Jaffe is the closest single reference to the on-demand allocation limitation: a cellular-phone-like terminal with differential GPS, a control center that computes distance to available taxis and assigns the closest one within ~30 seconds, ETA, and an acknowledgement/timeout protocol. Motivation: no field change; the "on-demand/ASAP" real-time allocation that Behnke arguably lacks is Jaffe's core competency. Jones or POSITA knowledge adds the proximity/updated-arrival alert; Malackowski or conventional utility-style billing (admitted in the '730 spec) adds the periodic-invoice element.

Ground 3 — Penzias in view of Jones

Penzias presents multiple paths and prices to a passenger who selects one — i.e., the alternatives/notification and fare-communication features that the '730 specification describes ("communicates the alternatives to the passenger… picks one of the alternatives based on timing and locations… and perhaps cost"). Jones adds the GPS-based arrival/proximity alert. Motivation: Penzias' passenger-selection model is improved by more reliable arrival timing, a predictable improvement in the same field.

Ground 4 — Culbertson in view of Westerlage in view of Jones

Culbertson gives demand-responsive automatic dispatch with telephone-number-based location identification; Westerlage gives ETA computation and delivery over a cellular link with traffic/weather inputs; Jones gives the proximity trigger. Motivation: Culbertson's soft-route system's central weakness is uncertainty in pickup timing; Westerlage supplies precisely that missing element over the same cellular infrastructure.

Ground 5 — billing element

The "periodic invoices" element is the weakest element to attack by combination because it is conceded: Behnke performs it explicitly, and the '730 specification itself describes utility-style monthly billing as the preferred, conventional mechanism. Under KSR, an admitted-conventional element cannot supply patentability.

Differences that keep the claims arguably non-obvious (the counter-case)

1. "On-demand" real-time allocation vs. Behnke's advance offer/request matching. PO's argument, made in IPR2019-00671, has real force against Ground 1.
2. Three-way communication (passenger↔central, vehicle↔central, and passenger↔vehicle at short range), which Behnke arguably lacks; Jaffe helps but the short-range passenger-to-vehicle leg is thin in both.
3. Integration of ride-sharing + mass transit + car rental into one central system with a single utility-style account — the '730 patent's own "defining elements" — is arguably more than the mere aggregation of Behnke + Malackowski.
4. Note the analytical trap: the features in (1)–(3) map onto the very limitations the courts held indefinite. The claim features that arguably distinguish the art are the features with no disclosed structure. A § 103 invalidity case and a § 112 indefiniteness case therefore pull in opposite directions here, and the Board avoided the conflict by denying institution rather than resolving it.

Bottom line

On the face of the paper record, claims 2, 3 and 6 would be obvious under § 103 in at least three alternative combinations — Behnke + Jones; Jaffe (alone or + Jones); Penzias + Jones — with Malackowski/conventional utility billing covering the periodic-invoice element, and Culbertson + Westerlage + Jones as a further route. The motivations are straightforward under KSR: same field, predictable results, improvement of the prior-art's own stated aim (reliable pickup times).

But this conclusion must be qualified heavily: (i) the claims were held invalid as indefinite and the Federal Circuit affirmed, so there is no definite scope against which to apply § 103; (ii) both IPRs on the '730 were denied institution, so no § 103 ground against the '730 has ever been adjudicated to a final decision; (iii) PO's teaching-away and three-way-communication rebuttals are non-trivial; and (iv) the patent expired April 4, 2021, so this is now a history/prior-art-status question. Its continuing relevance is as prior art itself — e.g., IPR2026-00308 (Uber v. Carma, filed Mar. 12, 2026) relies on the '730's pre-grant publication, US 2001/0037174 A1 to Dickerson, as Exhibit 1030 against US 11,017,668.

Uncertainties I am not papering over: verbatim claim text (especially claim 1 and the opening limitation of claims 2/3/6); the stipulated POSITA; the disclosures of Schmier '159, Sehr '976 and Ginter '488; the exact filing dates of the Jones family; and the final dispositions of RideApp v. Juno and RideApp v. Uber/Social Bicycles.