US 5995898

I'll run several searches to ground this in current sources.

US 5,995,898 — "RFID system in communication with vehicle on-board computer"

Basis: Google Patents full-text record (https://patents.google.com/patent/US5995898/en), corroborated by uspto.report (https://uspto.report/patent/grant/[5995898](/patent/5995898)) and the EPO family record for EP0941532 / WO9825248 (data.epo.org). Identifiers below are transcribed literally, not normalized.

Bibliographic data

Abstract (verbatim)

"A system comprising a vehicle on-board computer; and a wireless transponder device coupled to the vehicle on-board computer. The system performs a variety of functions because of its ability to transmit and receive data from other transponders which may be remote from the vehicle or located in the vehicle at a location spaced apart from the system. Remote transponders are spaced apart from the vehicle. The remote transponders can be positioned, for example, at a gas station, toll booth, service center, dealership, parking lot, or along a roadside."

Plain-language overview of the independent claims

• Claim 1 — telemetry system with co-housed engine-compartment module. Combination of (a) a vehicle on-board computer system with a first microprocessor; (b) a radio frequency transponder in communication with it, the transponder built as an integrated circuit with a transmitter, a receiver, and a second microprocessor; and (c) a common housing enclosing both, the housing being sized for insertion in a vehicle engine compartment. The housing/engine-compartment sizing limitation is the distinctive structural hook of this claim.

• Claim 10 — roadside-interrogator ID transmission. A vehicle system with an on-board computer plus an RFID device (IC with memory, transmitter, receiver, microprocessor) that is configured to provide an identification code, where the RFID device transmits the ID code to interrogators that the system passes along a road/highway.

• Claim 11 — multi-sensor telemetry, internal-combustion embodiment. For an internal-combustion-engine vehicle: an oil pressure sensor sensing engine oil pressure, a vehicle on-board computer, an RF transponder (IC with Tx, Rx, and a microprocessor coupled to both), an engine temperature sensor, and a battery voltage sensor. The transponder transmits data from a selected one of the sensors, by RF, in response to an interrogation and depending on which information the interrogator requests.

• Claim 12 — multi-sensor telemetry, data routed through the on-board computer. Structurally similar to claim 11 (on-board computer, RFID device with Tx/Rx/microprocessor, oil pressure sensor, engine temperature sensor, battery voltage sensor), but the emphasis is that the oil-pressure and engine-temperature sensors communicate their readings to the on-board computer, and the RFID device transmits the data that was communicated to the on-board computer in response to an interrogation — with selection of which sensor's data is sent made by the interrogator's request.

• Claim 13 — vehicle plus a plurality of roadside interrogators. A vehicle on-board computer; an RFID device (memory, Tx, Rx, microprocessor, provides an ID code); and a plurality of RF interrogators provided along a road or highway, each with its own communications range. The RFID device is configured to transmit the ID code to whichever interrogators it comes within range of. This is the claim most directly tied to electronic tolling / roadside reading infrastructure.

• Claim 14 — method of logging vehicle history (general). Steps: provide a memory in a vehicle; connect a wireless communication device (IC with Tx, Rx, microprocessor) to the vehicle's on-board computer; periodically store information from the on-board computer in the memory; and wirelessly read that memory from a location spaced apart from the vehicle.

• Claim 15 — method of logging vehicle history (transmission-specific). Same general scheme, but for a vehicle having a transmission: the memory stores information representative of transmission performance, which is then read wirelessly from off-vehicle. Dependent claims 16–22 add engine-performance data, maintenance records, owner identity, purchase price, purchase date, installed options, and repair records.

• Claim 23 — rental-vehicle return logging. A system with an RF transponder device plus on-board computer in a rental vehicle; the transponder IC has memory storing data identifying the vehicle and a microprocessor coupled to it; a mileage sensor in communication with the transponder device generates mileage information; a remote transponder at a controlled access point of a rental vehicle facility communicates with the transponder device to wirelessly receive the identifying data and mileage information when the vehicle passes the access point, thereby determining that the vehicle has passed. Dependent claims 24–31 add a further sensor (fuel level, oil pressure, knock, engine temperature, exhaust gas, battery voltage, alternator current).

Note: many of the described embodiments (debit/credit-card circuitry 60/62, brake control 54, electronic ignition 56, steering control 58, navigation display 64, cruise control 66, speed-limit and recommended-speed transponders, triangulation-based positioning) appear only in the specification and are not claimed.

Family and prosecution notes

• The same disclosure was pursued broadly abroad: EP0941532B1, EP1445749B1, EP1713046A1, EP1903507A3, DE69730344T2, DE69736409T2, ATE274221T1, ATE334460T1, AU5375398A, JP3665875B2 — all claiming the 1996-12-06 US priority date.
• Conception date context: the specification incorporates by reference commonly assigned application 08/705,043, filed Aug. 29, 1996 (the RFID IC disclosure).
• US 5,995,898 itself surfaces in later European search reports as X-category prior art against unrelated applications (e.g., EP1118965A1, where it was cited against claims 1–3, 5, 10, 11, 13).

Enforcement / litigation status

• The Google Patents litigation panel (Unified Patents Litigation Data) lists one US case for this patent: California Northern District Court, case 5:21-cv-09775. The panel does not name the parties in the text I retrieved, so I cannot state who sued whom.
• Ownership chain visible in the record: Micron Communications, Inc. → Micron Technology, Inc. (1999-11-08 merger) → Keystone Technology Solutions, LLC (2007-09-13) → Round Rock Research, LLC (2010-01-04); a 2010-01-26 reassignment back to Micron Technology, Inc. from Keystone also appears, so the recorded chain is not strictly linear on its face.

Explicit uncertainties / caveats

1. No CAFC 2026 activity found. I searched for a Federal Circuit or 2026 docket referencing 5995898 / 5,995,898 and found no results. That is a negative search result, not proof of absence — I do not have direct access to the CAFC docket system (PACER/CM/ECF) or to the USPTO Patent Trial and Appeal Board/PTAB APIs in this session, so I cannot rule out a 2026 appeal in which this patent is one of many asserted patents without being named in the captioned text.
2. Priority-date discrepancy. Google Patents (the authoritative full text supplied) says priority/prior-art date 1996-12-06; the Unified Patents record for "US-5995898-A" states priority date 1996-12-05. I flag rather than reconcile this; 1996-12-06 is the actual application filing date.
3. Assignee inconsistency. uspto.report lists the assignee as "Micron Communication, Inc. (Boise, ID)" (original), while Google Patents lists current assignee as Round Rock Research LLC. Both can be simultaneously correct at different points in time.
4. Apparent class-code anomaly. uspto.report renders the "Current U.S. Class" as "701/102; 427/255.31." Class 427/255.31 is a coating/etching class that has no evident relationship to this disclosure and looks like a database artifact; treat the 701/102 entry as the meaningful one.
5. Internal inconsistencies in the printed patent (flagging, not correcting): the Background cites "U.S. Pat. No. 4,875,391 to Leising et al." while the Detailed Description cites "U.S. Pat. No. 4,875,391 to Berra"; the sensor list refers to sensors numbered 26–50 but the enumerated list jumps to "transmission sensor 60," and reference numeral 60 is also used for "debit card circuitry 60." These are common typographical artifacts in this document family and should be verified against the printed patent images before being relied on.
6. Claim-text OCR. The claim text above is taken from the Google Patents HTML rendering and matches uspto.report's rendering. Where the OCR reads "th e" and "include s" (specification), those are transcription artifacts, not part of the patent text.

If you need a party-named docket entry for the N.D. Cal. case 5:21-cv-09775, or confirmation of whether any live 2026 appeal exists, that requires a direct PACER/CM-ECF or CAFC docket lookup, which I could not complete here.

I'll run targeted searches for litigation involving this specific patent number.

The general searches returned mostly noise. Let me drill into the specific case number and the likely 2021 campaign.

Bottom line

Based on the searches I was able to complete, I could not verify any US patent infringement litigation in which US 5,995,898 ("5995898") is actually asserted as a patent-in-suit. The only litigation linkage in the record is a single docket number that Google Patents' litigation panel attributes to this patent — and when I chased that docket number down, it resolved to a different parties and a different posture than a "Round Rock v. somebody" automotive case. Details below, with the conflict flagged rather than papered over.

Note on dates: my system date is 2026-09-30, while the task states "Current Date: April 26, 2026." I searched as of my session date; nothing in the results turns on that gap.

1. The one litigation entry tied to '898 in the patent record

The Google Patents panel for US 5,995,898 carries exactly one US case entry: "US case filed in California Northern District Court … https://portal.unifiedpatents.com/litigation/California%20Northern%20District%20Court/case/5%3A21-cv-09775" (District Court jurisdiction; labeled Critical).

What that docket number actually is (per an independent litigation database): RPX Insight's coverage of 5:21-cv-09775 describes it as Keep Truckin, Inc. v. Fleet Connect Solutions LLC, N.D. Cal., Judge P. Casey Pitts (+1), filed 2021-12-17, closed 2023-11-17, cause of action: Declaratory Judgment — patent invalidity / patent non-infringement, market sector "Logistics" (https://insight.rpxcorp.com/litigation/candce-[389623](/patent/389623)-keep-truckin-v-fleet-connect-solutions).

This is a material conflict with the prior section of this analysis, which (correctly, at the time) recorded only that Google Patents listed the N.D. Cal. case number without naming parties. The parties, per RPX, are not Round Rock Research — they are Keep Truckin (now Motive) as declaratory-judgment plaintiff and Fleet Connect Solutions LLC as defendant. There is no indication in the RPX summary that '898 is among the patents-in-suit in that DJ action, and the subject-matter profile (fleet/telematics declaratory judgment) does not match '898's claim set (on-board computer + RF transponder telemetry, roadside interrogators).

Consequence: I cannot state that 5:21-cv-09775 is a case "involving" 5995898. The most likely explanations — both unverified — are (a) a mapping artifact in the litigation dataset, (b) '898 being cited as prior art or in an invalidity/claim-construction filing in a case where some other patent was asserted, or (c) '898 being one of many patents swept into an omnibus complaint whose caption doesn't name it. To confirm which, you need the case's actual patent-in-suit list (see §4).

2. Searches that returned no '898 litigation

Targeted searches for the patent number against the obvious candidate asserters returned nothing tying '898 to a case:

• "5995898" patent litigation — no litigation hits. Results were Google Patents/Justia bibliographic pages (where '898 appears as a cited reference in later patents such as US 6,850,153; US 9,396,450; US 12,205,483), a WIPO/PCT search-report family table (listing US 6112152 A and US 5995898 A as family members), a Lithuanian companies-register PDF that merely contains the numeral string, and a Google Patents bibliographic-data collision — note US 6,297,426's INPADOC "Application number" field renders as "US09/059,958 US5995898A," i.e. an internal application-number vs. publication-number artifact, not a citation to '898's disclosure. Do not read those as litigation.

• "5,995,898" Round Rock Research — hits are Round Rock's well-documented 2010–2016 NPE campaigns, none of which name '898 among asserted patents:

  • Round Rock Research LLC v. HTC Corp., D. Del. 1:10-cv-00840 (filed 2010-10-01)
  • Round Rock v. Dell Inc., D. Del. 1:11-cv-00976 (filed 2011-10-14) — and v. Acer 1:11-cv-00977, v. ASUSTek 1:11-cv-00978 (same day)
  • Round Rock v. Oracle Corp. et al., E.D. Tex. 4:11-cv-00332 (asserted '816, '098, '067, '173, '838, '721, '006, '416, '342 — later settled)
  • SanDisk Corp. v. Round Rock Research LLC, N.D. Cal. 3:11-cv-05243 (DJ) and Round Rock v. SanDisk Corp., D. Del. 1:12-cv-00569 ('159, '798, '041, '531, '719) and 1:14-cv-01456
  • Round Rock v. Nintendo Co. Ltd., D. Del. 1:14-cv-01491 ('347, '405, '801, '935, '336, '683)
  • Round Rock v. Canon Inc. et al., D. Del. 1:14-cv-01457; Round Rock v. Ricoh Americas Corp. et al., D. Del. 1:15-cv-00157
  • The Dell/Acer dispute was characterized in expert testimony as "a patent dispute involving USB and BIOS, specifically US 5,991,843 and US 5,938,764."

  Every asserted-patent list I could retrieve consists of memory, flash-controller, USB/BIOS, and image-processing patents from the Micron-origin portfolio. No '898.

• "US5995898" OR "US 5995898" infringement suit — no litigation results; only the Google Patents page and unrelated PCT family tables.

• Unified Patents portal — I could not retrieve the portal's per-patent litigation page directly in this session (the portal caselist URL you supplied is behind dynamic content that my searches did not surface as indexed text). The Google Patents panel is itself sourced from Unified Patents Litigation Data, so its single entry is the best available proxy.

Also relevant: '898's own "Cited By" list (226 entries) and "Families Citing this family" (243 entries) are prosecution/prior-art citations, not litigation. The huge downstream citation count (Zonar, Honda, Oshkosh, Donnelly, Amazon, Platform Science, etc.) reflects the disclosure's breadth, not enforcement activity.

3. Why the absence of litigation is plausible (context, not proof)

• The patent is expired. Google Patents records anticipated expiration 2016-12-06 and legal status "Expired – Lifetime." Any suit filed after that date could only reach past damages within the 35 U.S.C. § 286 six-year lookback; the practical assertion window closed around the mid-2010s.
• Ownership timing. Micron Communications → Micron Technology (1999 merger) → Keystone Technology Solutions (2007-09-13) → Round Rock Research (2010-01-04), with an anomalous 2010-01-26 reassignment back to Micron Technology from Keystone. Round Rock's campaigns ran 2010–2016 against computer/memory/consumer-electronics defendants — the opposite of the automotive/tolling/telematics verticals '898 targets.
• Same-family sibling. The continuation US 09/378,435 → US 6,112,152 A (filed 1999-08-20, issued 2000-08-29) shares the '898 specification. I did not specifically docket-search '112152; if you need reassurance that no suit named the family, that is an additional check (see §4).

4. What I could not verify, and how to close it

Stated plainly: I do not have high-confidence access to a complete litigation record for '898 in this session. My searches did not return (and I cannot claim absence of) the following, which are the places a 1999–2016 assertion would show up:

1. Default/consent judgments and sealed-settlement cases in D. Del., E.D. Tex., C.D. Cal., or N.D. Cal. that never generated indexed opinions.
2. The actual patent-in-suit list for 5:21-cv-09775 — needed to confirm or refute the Google Patents mapping. Get it from the PACER docket for N.D. Cal. 5:21-cv-09775 (the complaint and any "Report on the Filing of an Action Regarding a Patent" form will list the asserted patent numbers), or from RPX Insight's "Patent Information" tab for that case (https://insight.rpxcorp.com/litigation/candce-389623-keep-truckin-v-fleet-connect-solutions), which the search snippet showed but did not expand.
3. Any PTAB proceeding. No IPR/PGR/CBM involving '898 appeared. (The one PTACTS document surfaced — petition 1527002 — is an expert's CV referencing other Round Rock cases and is not a proceeding on '898.) Confirm via the USPTO PTAB Patent Trial and Appeal Board Endpoint / PTAB APIs.
4. Any Federal Circuit appeal naming or implicating '898 — impossible to rule out from the captioned text of an appeal alone; the earlier section of this analysis likewise found no 2026 CAFC activity. Confirm via the CAFC docket (https://cafc.uscourts.gov) and CM/ECF.
5. State-court or ITC actions — not searched (ITC § 337 complaints would be the only plausible non-district-court forum, and are unlikely given expiry).

Recommended verification path (in order): (a) PACER docket pull for N.D. Cal. 5:21-cv-09775 → confirm whether 5,995,898 is in the asserted-patent list; (b) Docket Navigator or RPX patent-level search on "5,995,898" (patent-level, not party-level, which is what defeated my keyword searches); (c) Unified Patents portal patent page; (d) CourtListener RECAP full-text search for "5,995,898"; (e) CAFC/PTAB dockets.

Direct answer to the question

• Plaintiff(s), defendant(s), jurisdiction, case number, filing date, outcome/status for confirmed '898 litigation: I cannot furnish these, because no source I retrieved confirms a case in which 5,995,898 was asserted. The single case number linked to '898 in the patent's own litigation panel — N.D. Cal. 5:21-cv-09775 — is identified by RPX as Keep Truckin, Inc. v. Fleet Connect Solutions LLC (filed 2021-12-17; closed 2023-11-17; declaratory judgment of invalidity/non-infringement; Judge P. Casey Pitts), with no confirmation that '898 is a patent-in-suit. Treating that docket as "'898 litigation" would be an unverified inference, and I flag it as such rather than report it as fact.
• If no litigation is known: On the evidence available to me, that is the correct answer — no litigation is confirmed — with the explicit caveats in §4 about the limits of my docket coverage. This is a negative search result, not proof of non-existence.

Corroboration note: This finding is consistent with — and now sharpens — the prior section's caveat #1 ("No CAFC 2026 activity found … negative search result, not proof of absence") and the litigation-status paragraph describing the panel's unattributed N.D. Cal. entry. The new information here is the party identification that contradicts a Round Rock attribution for that docket, which should be carried forward as a correction to any internal summary that treated 5:21-cv-09775 as a Round Rock automotive case.

Sources cited: https://patents.google.com/patent/US5995898/en (litigation panel; expiration; cited-by lists); https://insight.rpxcorp.com/litigation/candce-389623-keep-truckin-v-fleet-connect-solutions (case 5:21-cv-09775 parties/status); https://dockets.justia.com/docket/delaware/dedce/1:2011cv00976/47259 (Round Rock v. Dell); https://docs.justia.com/cases/federal/district-courts/texas/txedce/4:2011cv00332/[130566](/patent/130566)/1/1.html (Round Rock v. Oracle, patent list); https://www.ded.uscourts.gov/opinion/round-rock-research-llc-v-dell-inc; https://unicourt.com (Round Rock v. SanDisk 1:12-cv-00569; v. Nintendo 1:14-cv-01491; v. Canon 1:14-cv-01457; v. Ricoh 1:15-cv-00157); https://patentlaw.jeffer.com/files/2016/12/Sandiskx.pdf (SanDisk v. Round Rock, N.D. Cal. 3:11-cv-05243, personal jurisdiction); https://www.law.com/article/almID/1202537867176/ (Oracle settlement); https://ptacts.uspto.gov/ptacts/public-informations/petitions/1527002/... (expert CV describing Dell/Acer USB-BIOS patents).

I'll verify the structured "no proceedings" default against live sources before writing anything.

No hits tying 5,995,898 to an IPR yet. Drilling into the Round Rock enforcement campaign and the N.D. Cal. case, plus a docket-level check.

The N.D. Cal. case is Keep Truckin, Inc. v. Fleet Connect Solutions LLC — worth confirming whether 5,995,898 is actually in that suit, and whether any IPR followed.

Proceedings overview

Total: zero AIA trial proceedings on file for US 5,995,898. The structured "PTAB proceedings on file" block (USPTO Open Data Portal ingest) returns no IPRs, PGRs, or CBM reviews, and my independent searches for 5,995,898 / 5,995,898 in combination with "IPR," "PTAB," "petition," and "Round Rock" surfaced no petition, institution decision, or Final Written Decision of any kind (breakdown therefore: active 0 / claims invalidated 0 / claims sustained 0 / settled 0 / institution denied 0). The defensive bottom line is not "the patent has survived two IPRs and is hardened" and not "claims 1–5 have been canceled" — it is an absence of record entirely, which is a different (and, for a defendant in 2026, a much weaker-looking) posture for the patent owner: all 31 claims stand exactly as they issued on 1999-11-30, never tested, never narrowed, never construed by the Board — and the patent expired 2016-12-06, which is the single most important fact in this analysis.

Two structural consequences follow immediately and are the real takeaway:

1. An IPR/PGR is no longer a realistic tool (and arguably pointless). PGR is unavailable (the application was filed 1996-12-06; PGR reaches only patents with an effective filing date on or after 2016-03-16). CBM review is unavailable — the CBM program sunset, and new CBM petitions could not be filed after 2020-09-16. IPR remains technically available against an expired patent (the Board applies a Phillips-style construction rather than B.

RI to claims that have expired — Board practice traceable to Sony Corp. v. Yissum, IPR2013-00219), but with issuance in 1999 and expiration on 2016-12-06, there is no prospective infringement and no ongoing-royalty exposure to enjoin, so the cost/benefit of a post-grant challenge is poor for everyone.

1. No estoppel has attached. Because no IPR was ever instituted, 35 U.S.C. § 315(e)(2) estoppel is a null set — no petitioner or privy is barred from anything (see the estoppel discussion below). Conversely, no FWD exists to cite, and there is no Board claim construction to leverage.

No proceeding to enumerate — what I checked, and what the record actually links to

There is no proceeding number to report, and I will not manufacture one. For completeness, here is the adjacent activity that a practitioner would expect to appear in a "what happened at the PTAB" search, and why each is not an AIA trial:

Search limitation, stated plainly: I searched public web sources and the litigation aggregators; I do not have a direct, live query into the PTAB E2E / PTAB API in this session. A negative result in these sources is strong but not conclusive evidence of absence — the authoritative check is the PTAB API/E2E at https://developer.uspto.gov/ptab-api (search by patent number) or PTAB Decisions at https://www.uspto.gov/patents/ptab/decisions. If you are budgeting litigation spend, run that query yourself before relying on this section.

Strategic summary

Claim status: nothing CANCELED, nothing SUSTAINED by the Board, everything UNTESTED. Because no AIA trial ever reached a Final Written Decision, the claim-level matrix is trivially simple but the practical point is not: all 31 claims — independent claims 1, 10, 11, 12, 13, 14, 15, and 23 plus dependents 2–9, 16–22, and 24–31 — retain their original, as-issued scope. There is no cancellation certificate, no certificate of correction affecting claim scope that I found, and no substitute claim from a motion to amend. For a defendant, that cuts both ways: you cannot win by pointing to a canceled claim, but you are litigating against pristine, never-construed claim language from 1996 — including claim 1's distinctive "common housing … sized for insertion in a vehicle engine compartment" structural limitation and claim 11/12's interrogator-selectable multi-sensor telemetry limitation, both of which are narrower than the specification's rhetoric (the debit/credit card circuitry 60/62, brake control 54, ignition 56, steering 58, navigation 64, and cruise 66 embodiments described in the specification are not claimed — do not let a demand letter blur specification disclosure into claim scope).

Estoppel landscape: § 315(e)(2) is a blank slate. Since no IPR was instituted, no petitioner and no privy is barred from raising any § 102/§ 103 ground, and there is no Board record that a defendant could be estopped from contradicting. In principle a defendant still has the entire prior-art universe — including patents and printed publications cited during the 1996–1999 prosecution, the art cited in the parallel foreign prosecutions (e.g., EP0941532, JP3665875, and the European search report in EP1118965A1 that rated 5,995,898 as X-category prior art against unrelated claims 1–3, 5, 10, 11, 13 and 1–6, 8, 13, a useful window into how examiners elsewhere treated this family's claims), and any art a third party could have found. The only statutory bar to watch is § 315(b) — one year from service of an infringement complaint — but that is academic here. Practical caveat: the same clean slate means there is no FWD to quote at a defendant, and equally no FWD to hand a plaintiff a res judicata or estoppel win. Nobody has ever litigated these claims to judgment at the Board.

Pattern signals: no petitioner repetition, no aggregated defense, and the patent is out of runway. No petitioner filed even once against 5,995,898, so there is no serial-petitioner pattern and no evidence of a defensive aggregator (e.g., Unified Patents) spending against this specific patent — although the 2011 anonymous reexamination wave against sibling Round Rock RFID patents (90/011,897, 90/011,898, 90/011,900, 90/011,901) shows someone was systematically clearing the Round Rock RFID portfolio, just not via AIA trials and not apparently against this patent. That combination — an expired patent (2016-12-06), a $0 forward-looking exposure, and no post-grant history — is precisely the fact pattern that generates zero IPRs. The absence here is not anomalous; it is the expected equilibrium, and it means the "well-asserted patents eventually attract IPRs" heuristic does not apply to this patent today.

Recommended next steps

• If you are a defendant being accused in 2026: do not build your defense around a PTAB outcome, because there isn't one. Attack the damages window first. The patent expired 2016-12-06; any recovery is limited by 35 U.S.C. § 286 (six-year lookback) to infringement occurring within six years before the filing of the claim, capped at expiration. That is a narrow, historical slice — build your § 101, § 102, § 103, and § 112 positions against the as-issued claims, and consider whether the asserted products/services even implement the claim-1 "engine compartment"-sized common housing or the claim 11/12 interrogator-selectable sensor-telemetry architecture.
• Distinguish the two dispositive documents a plaintiff might wave at you, and demand the FWD that does not exist. There is no PTAB Final Written Decision to quote at you. If a demand letter implies the patent was "upheld by the PTAB," that characterization would be unsupportable — the correct response is that no AIA proceeding has ever been filed. You can verify that yourself at PTAB E2E / https://developer.uspto.gov/ptab-api and cross-check PTAB Decisions at https://www.uspto.gov/patents/ptab/decisions.
• Pressure-test the (non-linear) chain of title. The prior section flagged: Micron Communications → Micron Technology (1999-11-08 merger) → Keystone Technology Solutions (2007-09-13) → Round Rock Research (2010-01-04), plus a 2010-01-26 reassignment from Keystone back to Micron Technology. Google Patents lists current assignee as Round Rock Research LLC, but the recorded chain does not read as strictly linear on its face. Whoever asserts 5,995,898 must prove ownership of all substantial rights at the relevant times — get certified USPTO assignment abstracts (https://assignment.uspto.gov/).
• Reconcile the Fleet Connect link before you assume it matters. If you are facing Fleet Connect Solutions LLC (an NPE identified in a 2025 S.D. Cal. DJ complaint as "owned and controlled by Empire IP LLC," with 50+ suits), note that its demonstrated portfolio in Motive v. Fleet Connect (N.D. Cal. 5:21-cv-09775, closed 2023-11-17) did not visibly include 5,995,898. Confirm from the ECF No. 1 docket whether 5,995,898 was ever pleaded; if it was, get the infringement contentions to see which claims were mapped. The Motive and Platform Science (Platform Science, Inc. v. Fleet Connect Solutions, LLC, S.D. Cal. 3:25-cv-00457) pleadings are useful templates if you intend to file a declaratory judgment action rather than an IPR — the DJ route avoids the § 315(b) one-year bar because an unserved DJ plaintiff has no service-triggering complaint.
• If you nonetheless want a Board proceeding: an IPR on an expired patent is legally possible but strategically near-worthless (no prospective relief, Phillips-style construction, and you would be spending six figures to invalidate claims whose only value is a time-barred damages claim). Spend that budget on § 286, laches-type equitable defenses in your district, and invalidity contentions instead.

I'll ground this in live sources before reconstructing the chain.

Key lead: the N.D. Cal. case is Keep Truckin v. Fleet Connect Solutions LLC (DJ action). Let me dig into the assignee chain and that litigation.

Fleet Connect Solutions appears to be the actual litigation-side owner. Let me verify the link to '589 and find the assignment records.

I hit the tool-step ceiling mid-research. Below is what I could actually ground, with an explicit map of the gaps.

Scoping note up front: I could not reach USPTO Assignment Center / Assignment Search in this session (no direct API or portal access, and my search budget ran out before I could pull the reel/frame records). Google Patents' legal-events panel — which is derived from the same assignment data — is the only chain record I can cite. Reel/frame numbers and correspondent-of-record names are therefore NOT verified for this patent. I flag each place where that matters rather than filling in plausible-looking numbers.

Inventors

• Single inventor. No co-inventor departures, no "all inventors left within 12 months" pattern — that tell is not available here because there is only one inventor, and he remained a Micron inventor-of-record (his assignment of interest to Micron Communications, Inc. was recorded 1997-03-11, roughly three months after the 1996-12-06 filing).
• Conception context: the specification incorporates by reference commonly assigned application 08/705,043, filed 1996-08-29 (the RFID IC disclosure) — i.e., Tuttle was filing an RFID transponder/IC application and this vehicle-telemetry application in the same ~3-month window. That is consistent with a deliberate internal portfolio build-out, not a distressed inventor exit.
• Unverified: Tuttle's later employment history. I have no evidence he left Micron, and I have no evidence he stayed; I will not assert either.

Original assignee

Micron Communications, Inc. (Boise, Idaho) — named as Original Assignee on the issued patent, and the assignee on the recorded 1997-03-11 ASSIGNMENT OF ASSIGNORS INTEREST from Tuttle.

• Primary line of business: integrated circuits / radio frequency identification devices. Micron Communications was the Micron family's communications-and-RFID arm; it is the entity that appears throughout the specification as the owner of the incorporated-by-reference RFID IC work.
• Did it ship a product embodying the claims? No evidence of one. Claim 1 requires a common housing enclosing both a vehicle on-board computer system and an RFID transponder, sized for a vehicle engine compartment. Micron Communications made transponders and ICs, not vehicle on-board computers or engine-compartment modules. The commercial RFID work sits on the transponder side of the claim, not the vehicle-side combination. Treat "original assignee practiced the claims" as not established.
• Current status: Micron Communications, Inc. did not survive independently — per the Google Patents legal events it was merged into Micron Technology, Inc. by a Merger conveyance recorded 1999-11-08. Micron Technology remains an operating, publicly traded semiconductor manufacturer. (I did not verify the Micron Communications legal status in Idaho's corporate registry or Micron's 10-K, and I have no reliable sourcing on the later disposition of Micron's RFID product line — flagging as unverified.)

Assignment timeline

Caveat on formatting: the records below are reconstructed from the publication's legal-events entries. They supply no reel/frame and no correspondent. I have not invented either. Where the task asks for reel/frame, the honest answer is not retrievable in this session.

• execution date not stated / recorded 1997-03-11 — Reel not retrieved

  • Conveyance: Assignment of interest (ASSIGNMENT OF INTEREST (SEE DOCUMENT FOR DETAILS))
  • Assignor: Tuttle, John R.
  • Assignee: Micron Communications, Inc.
  • Correspondent: not retrieved. Cannot assess recurrence.
  • Context: routine inventor-to-employer assignment; the patent issued on this chain.

• execution date not stated / recorded 1999-11-08 — Reel not retrieved

  • Conveyance: Merger (not an assignment of interest)
  • Assignor: Micron Communications, Inc.
  • Assignee: Micron Technology, Inc.
  • Correspondent: not retrieved
  • Context: internal corporate reorganization — Micron Communications absorbed into its parent. Title passed by operation of the merger, not by purchase.

• execution date not stated / recorded 2007-09-13 — Reel not retrieved

  • Conveyance: Assignment of interest
  • Assignor: Micron Technology, Inc.
  • Assignee: Keystone Technology Solutions, LLC
  • Correspondent: not retrieved. This is the single most valuable missing data point on the whole chain — see Signal 3.
  • Context: transfer of Micron patent assets into an IP-holding vehicle. Whether this was a bona fide portfolio sale or an intra-Micron holding step is not determinable from the record I have; note that a later recorded assignment runs Keystone → Micron Technology, which suggests Keystone functioned at least partly as an internal holding entity.

• execution date not stated / recorded 2010-01-04 — Reel not retrieved

  • Conveyance: Assignment of interest
  • Assignor: Micron Technology, Inc.
  • Assignee: Round Rock Research, LLC
  • Correspondent: not retrieved
  • Context: transfer to an asserter. Round Rock Research LLC is a licensing/enforcement entity with no products; this is the link that converts the chain from operating-company-owned to assertion-owned.

• execution date not stated / recorded 2010-01-26 — Reel not retrieved

  • Conveyance: Assignment of interest
  • Assignor: Keystone Technology Solutions, LLC
  • Assignee: Micron Technology, Inc.
  • Correspondent: not retrieved
  • Context: change of custody / internal cleanup. A recorded January-2010 assignment running back to Micron three weeks after the Micron→Round Rock recording makes the four-year segment 2007→2010 non-linear on its face. Two readings are possible: (a) Keystone acted as a holding conduit and its interest was folded back before the Round Rock transfer, or (b) two overlapping conveyances of the same asset were recorded and one was corrective. I cannot distinguish these without the reel/frame images.

What is missing and what it would settle: the recording order (execution date vs. recording date), the reel/frame for each link, and the correspondent. Those three fields would tell us whether the 2007 Keystone link and the 2010 Micron→Round Rock link are the same transaction chain or two parallel ones — the difference between "clean cascade" and "recorded twice." Pull them at https://assignmentcenter.uspto.gov/ (or https://assignment.uspto.gov/patent/index.html) by patent number 5995898.

Timeline diagram

timeline
    title Ownership of US 5995898
    1996 : Filed by Micron Communications Inc
    1997 : Tuttle assigns interest to Micron Communications
    1999 : Micron Communications merged into Micron Technology
    2007 : Assigned to Keystone Technology Solutions LLC
    2010 : Assigned to Round Rock Research LLC
         : Reassignment recorded back to Micron Technology
    2021 : Keep Truckin files DJ against Fleet Connect

NPE / troll-pattern signals

1. Shell-entity transfer — PRESENT (in part) / UNCLEAR (in part).
The 2010-01-04 record transfers the patent from operating company Micron Technology to Round Rock Research, LLC — an entity whose entire recorded business is licensing and enforcement. That is the core of the signal. What I cannot supply is the corroborating detail the rubric asks for: I have no registered-agent address, no entity-formation record, and no confirmation of members for Round Rock, and I have no product evidence either way for Keystone Technology Solutions, LLC (2007-09-13). Do not treat Keystone as a shell on the strength of the name alone — the fact that a Keystone→Micron Technology conveyance was recorded on 2010-01-26 actively cuts against a pure third-party sale reading for that link.

2. Known asserter in the chain — PRESENT.
Round Rock Research LLC appears as an assignee on 2010-01-04 and as Google Patents' current assignee, and it is independently a serial patent plaintiff, not merely a name on a list. Grounded examples: Round Rock Research LLC v. SanDisk Corp., D. Del. 1:12-cv-00569 (complaint filed 2012-05-03); Round Rock Research LLC v. Dell, Inc., D. Del. 1:11-cv-00976 (filed 2011-10-14); ASUS Computer International v. Round Rock Research LLC, N.D. Cal. 3:12-cv-02099 (filed 2012-04-26); and SanDisk Corp. v. Round Rock Research LLC, N.D. Cal. 3:11-cv-05243-RS, which ran to summary judgment and a July 2014 stipulated final judgment. A secondary, less certain link: Fleet Connect Solutions LLC is alleged in a filed federal complaint to be "a non-practicing entity owned and controlled by Empire IP LLC" and to have "filed over 50 patent infringement lawsuits in at least ten different district courts" — Platform Science, Inc. v. Fleet Connect Solutions, LLC, S.D. Cal. 3:25-cv-00457 (¶¶ 9–12). See Signal 5 for why I cannot yet place Fleet Connect on this patent's chain.

3. Repeat correspondent across the chain — UNCLEAR / NOT VERIFIED.
This is the signal I most wanted and could not get. No correspondent names were retrievable in this session. Because the rubric is explicit that a single appearance is not a finding and the signal is recurrence, I am recording this as unverified rather than present or absent. Concretely: the 2007-09-13 Keystone recording and the 2010-01-04 Round Rock recording are the two entries where a shared correspondent would be most probative, and I have neither. Anyone continuing this analysis should pull the correspondent field for all five recorded entries at Assignment Center before drawing a conclusion.

4. Cascading transfers — WEAK / UNCLEAR.
Four recorded conveyances touch this patent between 1997 and 2010. But the 1997 link is a routine inventor assignment and the 1999 link is a merger, not a purchase, so only two links are genuine asset transfers (2007 and 2010), and they are ~28 months apart — outside the "<24 months" cascade threshold. The two January-2010 recordations, 22 days apart, are the closest thing to a cascade, and they point in opposite ownership directions. Not a clean cascade finding.

5. Pre-litigation transfer — UNCLEAR, and this is the live question.
Google Patents' litigation panel for US5995898 lists N.D. Cal. 5:21-cv-09775, which I confirmed is Keep Truckin, Inc. v. Fleet Connect Solutions LLC (filed 2021-12-17, closed 2023-11-17; Judge P. Casey Pitts; RPX Insight docket page). If that case was brought over the '589 patent, then ownership passed to Fleet Connect at some point after the last recorded 2010 event, and the transfer would be a textbook pre-litigation arrangement. But the consolidated complaint in that action undercuts the assumption. Motive Technologies, Inc.'s consolidated DJ complaint (N.D. Cal. 5:21-cv-09775-EJD, incorporating 5:22-cv-06083 and 5:23-cv-00757) enumerates twenty patents-in-suit, and US 5,995,898 is not among them — the list runs 6,429,810; 6,647,270; 7,450,955; 7,463,896; 7,536,189; 7,596,391; 7,599,715; 7,742,388; 7,783,304; 8,005,053; 6,549,583; 6,633,616; 7,092,723; 7,206,837; 7,260,153; 7,058,040; 7,656,845; 7,747,291; 8,494,581; 6,961,586. So either '589 was pleaded in the original 2021 complaint and later dropped/consolidated out, or Google Patents has miscarried this case to this patent page. I cannot resolve that without the original 2021 complaint, which I did not pull. Flag this as the single most important open item.

6. Bankruptcy fire-sale — NOT PRESENT.
No bankruptcy of Micron Communications or Micron Technology appears in the record, and the 1999 event is expressly a merger, not a Chapter 7/11 sale. Not a Kodak/Nortel-style proceeding.

7. Privateering — UNCLEAR / WEAK.
The shape (operating chipmaker → enforcement-only LLC holding a broad patent portfolio) resembles privateering, but the classic privateering tell is the operating company continuing to benefit from assertions against its competitors while staying out of the caption. Round Rock's 2011–2014 campaigns (SanDisk, Dell, ASUS, SK hynix-related) read as a standalone monetization program rather than a Micron-directed campaign. No SEC filing evidence of a Micron–Round Rock arrangement is in front of me. Would not call it.

8. Defensive aggregator — NOT PRESENT.
The chain does not terminate at RPX, AST, LOT, Unified Patents, or OIN. No neutralizing terminal transfer observed. Note the inverse: Unified Patents maintains an active litigation-data page for this patent (portal.unifiedpatents.com), which is a defensive-monitoring interest signal, not a defensive-aggregation ownership signal.

Cross-check with the earlier generated section — one material update

The prior summary correctly recorded that Google Patents lists N.D. Cal. 5:21-cv-09775 but "does not name the parties." That gap is now closed: the parties are Keep Truckin, Inc. (now Motive Technologies, Inc.) as declaratory-judgment plaintiff and Fleet Connect Solutions LLC as defendant. This is an addition, not a contradiction. The prior summary's caveat #1 (no CAFC 2026 activity, negative search result only) stands unchanged.

Verdict

NPE — high confidence.

Two independent strong signals. First, Signal 2 (known asserter): the 2010-01-04 recorded assignment conveys the patent from Micron Technology, Inc. to Round Rock Research, LLC, a licensing-only entity with a documented multi-defendant assertion campaign (Round Rock v. Dell, D. Del. 1:11-cv-00976, filed 2011-10-14; Round Rock v. SanDisk, D. Del. 1:12-cv-00569, filed 2012-05-03; ASUS v. Round Rock, N.D. Cal. 3:12-cv-02099, filed 2012-04-26) and no products. Second, Signal 1 (shell-entity transfer): that same 2010-01-04 entry is the terminal transfer from an operating manufacturer to a non-practicing licensing vehicle — and the enforcement-side interest now plausibly sits with Fleet Connect Solutions LLC, alleged in a filed complaint to be "a non-practicing entity owned and controlled by Empire IP LLC" with 50+ infringement suits (Platform Science v. Fleet Connect Solutions, S.D. Cal. 3:25-cv-00457 ¶¶ 9–12). Signal 5 is unclear rather than a third hit, because I could not confirm that '589 was actually asserted in the Fleet Connect/Motive DJ.

The two findings I could not make, and what they would change. (a) Reel/frame and correspondent fields are unretrieved for all five recorded entries — the chain above is reconstructed from Google Patents legal events, and it contains no reel/frame numbers and no attorney names, so Signal 3 is honestly reported as unverified rather than as a negative. (b) The 2007 Keystone → 2010 Micron → Round Rock ordering is non-linear on the face of the record and I could not resolve whether Keystone was an internal holding conduit or a genuine intermediate purchaser; the reel/frame images and execution dates would settle it. Neither gap changes the verdict, because the Round Rock link alone satisfies Signal 2, but both should be closed before this chain is relied on.

Verify at: https://assignmentcenter.uspto.gov/ (search patent number 5995898) or https://assignment.uspto.gov/patent/index.html — pull all five entries and record reel/frame plus correspondent for each.

I'll ground this in live sources. Let me search for the specific patent and its cited prior art.

Let me pull the front-page "References Cited" list and the patent's own PDF.

Scope note before the analysis

I attempted to query the USPTO record for exactly US 5,995,898. What I could actually reach in this session:

• Google Patents https://patents.google.com/patent/US5995898/en (supplied as authoritative full text) — this rendering contains the forward citation block ("Cited By (226)") and the prior-art keyword tags (vehicle, sensor, radio frequency, board computer, memory), but the front-page "Patent Citations" (backward citation) block is absent from the supplied text.
• uspto.report/patent/grant/5995898 — returned only partial body-text fragments, no citation table.
• EPO/EPO-derived records for the equivalent family member — EP0941532A1, EP1713046A1, WO9825248A1 (per data.epo.org).
• USPTO Patent Public Search / PatentCenter / the file wrapper (Office Actions) were not reachable — I cannot state what the examiner actually applied in a § 102 rejection.

So I could not lift the front-page "U.S. Patent Documents" list verbatim. Instead I reconstructed the citation set from two verifiable sources, and I label which is which below:

• Group A — references cited inside the US 5,995,898 specification (applicant's "incorporated by reference" citations; these are the ones that would appear on the front page as applicant-cited art).
• Group B — references cited in the search report of the corresponding family case (EP 1 713 046 A1 / EP 0 941 532 / WO 98/25248). Confirmed as the same disclosure: the EPO record I retrieved is titled "RFID system for communicating with vehicle on-board computer" and its citation list ends with "US 5995898 A 19991130."

Legal framework used: This application was filed 1996-12-06, so pre-AIA 35 U.S.C. § 102 governs. § 102(b) requires publication before 1995-12-06; § 102(a) requires publication before the applicant's invention date; § 102(e) requires a U.S. patent/application filed before the invention date. All references below are non-U.S. publications unless noted, so § 102(e) is generally unavailable for Group B (its U.S. family members, where they exist, are the § 102(e) candidates).

Group A — References cited in the US 5,995,898 specification

Group B — References on the search report for the same disclosure (EP 1 713 046 A1 / EP 0 941 532 / WO 98/25248)

These are the examiner-side citations, and they carry the EPO's X/Y categorisation — the closest thing to a § 102 attack on this disclosure that I could recover. (X = novelty-destroying alone; Y = obviousness in combination; A = background.)

Ranking of the most relevant prior art

1. WO 95/01607 A1 (Tsakanikas et al., pub. 1995-01-12) — the only reference the record shows being applied alone (X) against the family's broadest claims. This is where a validity challenge to claims 10 and 13 would start. (Note: its U.S. family member US 5,420,794, issued 1995-05-30, is also § 102(b) art and a cleaner citation for U.S. purposes.)
2. EP 0 725 377 A2 (IBM, pub. 1996-08-07) — § 102(a)-only X reference; the most probable anticipation candidate against the claim 14/15 logging methods.
3. GB 2 277 844 A (1994-11-09) and WO 90/12365 A1 (1990-10-18) — § 102(b) art bearing on the data-logging and RFID-ID-code elements respectively.
4. FR 2 647 930 A1 / GB 2 169 173 A / EP 0 456 425 A1 / WO 91/18452 A1 — the § 102(b) cluster aimed at the roadside-interrogator/ID-code claims.
5. DE 35 40 599 A1 and U.S. Pat. No. 5,459,660 — the best § 103 combination anchors for the "on-board computer" + "housing" elements, but neither anticipates.

Claims that appear unassailable on this citation record: claim 1 (RF transponder IC with two microprocessors co-housed with the on-board computer in a common housing sized for a vehicle engine compartment), claims 11 and 12 (the specific oil-pressure + engine-temperature + battery-voltage trio read out by RF on interrogator demand), and claim 23 (rental-vehicle mileage sensor + remote transponder at a rental-facility controlled access point). No citation in either group appears directed at these combinations — Group A supplies only the computer/sensors, Group B only the transponder/ID layer.

Flags, anomalies and contradictions

1. A record artifact that a literal-ID reading must confront. The Google Patents record for US 6,297,426 B1 ("Methods of mediating female fertility in plants," application 09/059,958) renders its identifier field as: US6297426B1 US6297426B1 US09/059,958 US5995898A US6297426B1…. Taking IDs literally, US5995898A appears there — but its subject matter (floral homeotic genes, Zea mays) is wholly unrelated to vehicle RFID. I treat this as a Google Patents field-encoding artifact (it accompanies the equally unrelated application number 09/059,958), not as evidence that US 5,995,898 is a plant-biology patent. Flagging per the literal-identifier rule; verify against the printed patent before relying on it.
2. Contradiction with the previously generated section — date. That section was produced with "Today's date: 2026-09-30" and a fetch stamp of 2026-09-24; this task specifies April 26, 2026. Nothing substantive turns on it, but the two sections cannot both be the operative date. Also, the prior section's caveat about the "Current U.S. Class 427/255.31" anomaly was not resolved by any search in this session — it remains unexplained.
3. Self-inconsistency in the printed citation (already flagged, repeated because it affects any § 102 reading of A1): U.S. Pat. No. 4,875,391 is attributed to Leising et al. in the Background and to Berra in the Detailed Description. Under the strict-literal rule I have not chosen between them; whichever it is, it is cited only as an on-board-computer example and cannot anticipate any independent claim.
4. I could not verify the disclosure (not just the bibliographic data) of any Group A or Group B reference. The Group B claim mappings above are hypotheses built from the EPO's X/Y/A categorisation and the cited pinpoints — they are not confirmed anticipation conclusions. Each mapping needs to be confirmed by reading the reference against the claim language under the pre-AIA § 102 rubric.
5. Leads that are NOT on this patent's citation record (offered only so they are not mistaken for cited art): DE 19532067C1 (Daimler-Benz, pub. 1996-10-24) surfaced alongside US5995898A in a third-party citation table (DE10021971B4) and is titled as a vehicle return/retrieval control system — a possible § 102(a) concern for claim 23 (rental-return logging), which no cited reference in Group A or B appears to address. Treat as an investigative lead, not as cited art.
6. Forward citations are not prior art. The "Cited By (226)" block and the prior-art keyword tags (vehicle, sensor, radio frequency, board computer, memory) post-date the 1996-12-06 filing and have no § 102 effect on US 5,995,898 — though the patent's own use as an X reference against EP 1 118 965 A1 (claims 1–3, 5, 10, 11, 13) shows the claimed subject matter was, in turn, treated as anticipatory of later filings.
7. File wrapper not retrieved. If you need to know which of these references the USPTO examiner actually applied, and whether any § 102 rejection was made and overcome, that requires the application 08/759,737 file wrapper in USPTO PatentCenter, which I could not reach in this session.

I'll ground this analysis in the actual prior-art record for this patent before reasoning about combinations.

Now let me pull the specific prior-art references and technical context I'd need to build § 103 combinations.

0. What the "Prior Art" material on this page actually is — read this first

The Google Patents record supplied for US 5,995,898 (https://patents.google.com/patent/US5995898/en) does not contain a front-page "References Cited" (examiner-cited) list. My attempts to retrieve one (searches on US5995898 "References Cited") did not surface it, and the fetched page text ends at the "Families Citing this family" table. So the prior-art content actually available on this page is four things, and it matters which is which:

I also searched for PTAB/IPR/PGR activity naming 5,995,898 and found none — the PTAB petition documents my searches returned (petitions/1557215, petitions/1557879, re "Murphy"/"Arshad"/"Petrik") belong to unrelated proceedings and must not be attributed to this patent.

Below I build the §103 case from categories A + C, plus references I could confirm by search (each flagged with how far I verified it).

1. Person of ordinary skill (POSITA), as of December 1996

A POSITA here would be a BS-level electrical/computer engineer or equivalent with ~2–4 years in automotive electronics and RF identification: comfortable with engine control modules (ECMs) and their sensor sets, serial vehicle data buses, and RF transponder/reader link design. The patent's own specification sets this baseline by admitting that on-board computers, engine/transmission/brake control, sensor suites, multiplexed data buses, handheld diagnostic display tools, and the OBDII/CARB interface with SAE J1850 and ISO 9141 variants were all known (US 5,995,898, Background).

Key structural point: the specification's own "Prior art keywords" (vehicle / sensor / radio frequency / on-board computer / memory) track the elements of independent claims 1, 10, 11, 12, 13 with striking fidelity. Where a claimed combination is coextensive with the examiner's keyword set, the §103 question collapses into "is the arrangement of those known elements inventive?"

2. The prior-art universe I will use

2.1 References cited in the patent's own specification (category C) — strongest, because they are self-admissions

2.2 Search-confirmed external prior art

I attempted but did not verify (so I am deliberately not relying on them): US 5,442,553 (vehicle data collection/transmission), US 4,926,331 (Windle), US 5,208,756, US 5,086,389. Treat any use of those as unconfirmed.

3. Ground-by-ground §103 analysis

Ground A — Claim 1 (co-housed ECM + RF transponder, engine-compartment-sized)

Combination: US 4,875,391 (or US 5,150,690 / DE 35 40 599 A1) + US 5,459,660 (Berra) + US 5,196,846 (Brockelsby) + US 4,853,850 (Krass) or US 5,479,479 (Braitberg).

Claim 1 is the broadest and the most vulnerable claim in the patent, because it requires only the physical combination: (i) an on-board computer with a first microprocessor; (ii) an RF transponder IC with a transmitter, a receiver and a second microprocessor; (iii) a common housing enclosing both, sized for the engine compartment. It does not require that any data ever be transmitted (claim 2 adds that).

• Elements (i) from '391/'690; element (ii) from Brockelsby '846 (transponder with storage and transmit/receive control) or Braitberg '479 (vehicle air-link transceiver); the integration into an IC is a routine 1990s fabrication trend.
• Element (iii) is the only candidate "hook," and it is weak: the ECM itself is an in-engine-compartment module (the very thing '391/'690 are), so the claim amounts to putting the transponder in the box that already exists.
• Motivation is supplied by the patent's own Background, which frames the problem as harness complexity: data-bus art exists so that "simple wire harnesses can be employed for data transmission." A POSITA seeking fewer harness runs, connectors and pass-throughs would co-locate the transponder with the computer/sensors it serves rather than remote-mount it. KSR, 550 U.S. at 416–17: "[a] combination of familiar elements according to known methods is likely to be obvious when it does no more than yield predictable results," and the "predictable use of prior art elements according to their established functions."
• Second-microprocessor limitation: a POSITA would offload the RF protocol/anti-collision task to a dedicated processor — a known technique for improving a similar device in the same way (KSR's "used to improve one device … would improve similar devices in the same way" rationale). Krass '850's dual-ported-RAM architecture shows that multi-processor vehicle/external-device coupling was routine.
• Objective indicia: none in the record. No unexpected-result data, no nexus evidence. The specification's own framing ("It is now possible, therefore, for a garage … to diagnose a problem … without needing to physically connect diagnostic equipment") describes an appreciated benefit, not an unexpected one.

Ground B — Claims 2–9 (transmit sensor data on interrogation; oil pressure / knock / engine temp / exhaust gas / battery voltage / alternator current / engine RPM)

Combination: Ground A + US 4,168,679, 4,237,830, 4,335,695, 4,524,745, 4,552,116 (admitted sensor art) + Brockelsby '846.

• Every claimed sensor is either named in the specification's own sensor list (oil pressure 30, engine temperature 32, battery voltage 34, alternator current 36, engine RPM 38, exhaust gas 26, knock 28) or covered by the incorporated sensor patents. These are admission-based grounds: the patent itself says these sensors are "typically employed with vehicle on-board computers."
• The "in response to a radio frequency interrogation" limitation is met by Brockelsby '846, whose transponder transmits "in response to a received first trigger pulse."
• Motivation: on-demand, selective read-out instead of continuous broadcasting — conserves RF bandwidth and vehicle power in a shared interrogation zone, which '846 addresses directly (multi-transponder capture zones).

Ground C — Claims 11 and 12 (oil pressure + engine temperature + battery voltage; interrogator-selective read-out; claim 12 routes data through the on-board computer)

Combination: US 4,875,391 + US 5,459,660 (Berra) + US 4,853,850 (Krass) + Brockelsby '846.

• Claim 11's three sensors are admitted conventional. Its novelty lies in selection by the interrogator — a POSITA would implement this as a routine addressable/memory-mapped data set (and '846's write-back protocol already contemplates interrogator-directed data exchange).
• Claim 12's distinguishing feature is that the sensors talk to the on-board computer and the RFID device transmits the data that was communicated to the on-board computer. That is precisely the architecture of Krass '850 (vehicle computer I/O port → adapter → off-board device), with the ribbon cable replaced by the RF air link of Braitberg '479 or the RFID IC of '846. The substitution of a wireless link for the '850 hard-wired adapter is the archetypal KSR "simple substitution of one known element for another."
• Motivation: the specification's own stated purpose (diagnosis without physically connecting equipment; diagnosis beginning as the vehicle drives in) is the design incentive, and it is the same incentive Braitberg '479 articulates for vehicle air links.

Ground D — Claims 10 and 13 (ID code transmitted to roadside interrogators; plurality of interrogators along a road/highway with respective ranges)

Combination: US 5,196,846 (Brockelsby) alone, or Brockelsby '846 + US 5,192,954 + US 4,870,411 / 4,937,581 (Baldwin).

• This is the strongest ground in the whole analysis — arguably close to anticipation rather than obviousness.
  • '846 discloses a transponder moving past a fixed-location interrogator, holding transponder data, transmitting it on interrogation, and receiving/writing data back, with express applications in roadway-use tolls and a credit-balance transponder (i.e., stored value).
  • Claim 10's "identification code" is the core function of the Brockelsby/Baldwin AVI family; claim 13's "plurality of radio frequency interrogators provided along a road or highway, respectively having a communications range" is the ordinary deployment topology of that art ('954 is literally a family of roadway antennas sized to create capture zones so vehicles "occupying reduced portions of a standard highway lane" are reliably read).
• Because the architecture and the roadside topology both pre-date the critical date, claim 13 reduces to the routine aggregation of known transponders with known readers. Motivation: automated tolling/traffic management, stated as the objective in '846's own Background.
• Where the patent can fight: the claim language "configured to provide an identification code" and the vehicle-side framing (the claim packages the vehicle with the readers). The patentee would argue the claim is to the vehicle-side subsystem. But the claim recites the roadside interrogators as elements, so the roadside art is squarely on point.

Ground E — Claims 14–22 (method of logging vehicle history; periodically storing; wireless reading off-vehicle)

Combination: US 4,602,127 (Neely, "Diagnostic Data Recorder") + US 4,853,850 (Krass) + US 5,479,479 (Braitberg) or Brockelsby '846.

• Claim 14's steps — memory in a vehicle; wireless device connected to the on-board computer; periodic storing of on-board-computer information; reading from off-vehicle — are each disclosed: storing = Neely '127; connection to the on-board computer and off-vehicle read-out = Krass '850; replacing the physical link with a wireless one = Braitberg '479 / '846.
• Claim 15's "transmission performance" is a subset of the same logging, and '391 (cited by the patent as a computerised vehicle system; the Leising/Berra attribution conflict is noted but immaterial here) is transmission-control art.
• Claims 16–22 (engine performance, maintenance records, owner ID, purchase price, purchase date, installed options, repair records) are content-of-information limitations on an otherwise-unchanged memory. A POSITA storing vehicle history would obviously choose to store the fields a service writer, dealer or buyer would want. This is the In re Gulack / In re Ngai line: where the recorded information is not functionally related to the structure that stores it, changing the content does not render the claim patentable. I'd pair Gulack (703 F.2d 1381) with the "intended use / data content" §103 principle; I flag that I did not re-verify the exact MPEP subsection number in this session.

Ground F — Claims 23–31 (rental-vehicle return logging)

Combination: Brockelsby '846 + US 5,459,660 (Berra) + admitted odometer/fuel-level sensor art (US 5,995,898 spec, sensors 44 and 46) + US 4,168,679 et al.

• Claim 23 = a known vehicle-borne transponder storing a vehicle ID (Brockelsby '846), a known odometer/mileage sensor (admitted), and a known fixed interrogator at a controlled access point (Brockelsby '846 / '954) — arranged so the interrogator reads ID + mileage as the vehicle passes.
• The only new "environment" element is "a controlled access point of a rental vehicle facility." Under In re Schreiber, 128 F.3d 1473 (Fed. Cir. 1997), a recitation of intended use/environment does not impart patentable weight where the structure and function are unchanged. Nothing in claim 23 requires the rental-facility controller to do anything structurally different from a toll gantry controller.
• Claims 24–31 add one further sensor (fuel level / oil pressure / knock / engine temperature / exhaust gas / battery voltage / alternator current) — each already in the admitted sensor list. Pure simple substitution of one known sensor for another.
• Motivation: automated return processing and immediate billing do reduce labour (the specification's stated goal), and Brockelsby '846 already frames the same use case for tolls ("debits an account associated with that particular identification code").

4. The motivation-to-combine story, consolidated

Using the KSR/MPEP 2143 rationales, and preferring grounds that rest on the patent's own admissions:

5. Where the patent can actually resist — and the limits of those arguments

1. The engine-compartment RF environment (the best defence, for claim 1 only). An under-hood RFID transponder must radiate from inside/near a shielded metal bay with thermal and EMI load. Prior-art AVI deployments conventionally put the tag on the windshield or bumper. A patentee could argue that this constituted teaching away and an unexpected problem. This is undercut by the patent's own text: the specification states that the antenna 18 "can either be supported by the system 16, or can be located at another location of the vehicle 10, and connected to the RFID circuitry 14 via a cable." If the antenna may be remote from the housing, the "can't radiate from the engine bay" argument loses most of its force as to the claimed structure (the claim recites a housing, not a sealed RF-transparent housing). Also, claim 1 contains no heat/EMI/sealing limitation to point to.
2. The "second microprocessor" as a structural requirement. A patentee could argue that the prior art used discrete transponder logic. This is a weak position: integration into an IC is a routine engineering trend, and the claim's own words ("integrated circuit having … a second microprocessor") map onto the spec's admitted RFID IC disclosure.
3. Claim 13's system framing (vehicle plus the readers) gives the patentee an argument that the prior art taught the reader side or the transponder side, but not the claimed aggregation. This argument is weak because claim 13 recites the interrogators as elements and the aggregation produces no new co-operative function beyond reading the passing tag.
4. Secondary considerations. I found none in the record — no unexpected results, no nexus evidence, no evidence of copying, long-felt need, or industry praise tied to the claimed features. The 226 forward citations show the art built on the patent, which is not itself a nexus-qualified indicium. Any patentee case would have to be built from scratch.
5. Common ownership of the RFID IC reference. See below — it cuts a hole in the cleanest grounds.

5.4 The §103(c) problem with USSN 08/705,043

The specification's example RFID IC is commonly assigned application 08/705,043 (Tuttle), filed 1996-08-29 — under four months before this filing, and Tuttle is also this patent's inventor. If a challenger wants to use '043 as the RFID-IC element in a §103 combination, several obstacles arise:

• Pre-AIA §102(e)/(a)/(g) art must be "by another." Where the inventive entity overlaps, the reference may not qualify.
• Pre-AIA §103(c) (added by the AIPA, effective 1999-11-29) removes commonly-owned §102(e)/(f)/(g) art from §103 consideration. I flag explicitly that I did not resolve whether §103(c) reaches a 1996-filed application in a present-day or 2021-filed challenge — that is a legal question beyond what I verified in this session.

Practical consequence: a well-built obviousness ground should establish the RFID-transponder element from third-party art (Brockelsby '846 / Baldwin '411/'581; Braitberg '479; the general transponder-with-memory art), not from '043. Every ground I set out above is drafted that way.

6. Evidentiary gaps — what I could not verify

1. No front-page "References Cited" list was retrievable, so I cannot tell you what the examiner actually cited or relied on for allowance. That is the single biggest gap; the grounds above are constructed, not reconstructed from the file wrapper.
2. I could not confirm the publication dates of US 4,875,391, US 5,459,660, US 5,278,759, US 5,150,690, US 4,168,679, US 4,237,830, US 4,335,695, US 4,524,745, US 4,552,116, or US 5,189,612 from a primary source in this session. All are cited within the patent as existing art, and all are numbered below the 5,995,898 series, so each pre-dates the filing on its face — but page/column pinpoint citations for a real §103 chart must be read off the printed documents. Do not treat my characterisations as pinpoint citations.
3. I did not verify US 5,442,553, US 4,926,331, US 5,086,389 or US 5,208,756 and therefore do not rely on them.
4. No PTAB/IPR/PGR proceeding naming 5,995,898 surfaced in my searches. That is a negative result, not proof of absence — I have no direct PTAB API access here.
5. The N.D. Cal. case 5:21-cv-09775 (from the Google Patents litigation panel) still cannot be attributed to named parties on the evidence I retrieved. If the patentee's infringement theory in that case tracks claims 10/13 (roadside ID reading), note that those are precisely the claims with the strongest prior-art attack. However, the patent expired 2016-12-06, so any present-day challenge is retrospective (past damages within the limitations period; reexamination rather than IPR-style amendment). I did not verify current docket status.
6. Litigation/appeal status as of 2026 — as flagged in the earlier section, no 2026 CAFC activity was found; that remains a negative search result requiring PACER/CM-ECF or CAFC docket confirmation.

7. Bottom line

Overall: the record supports strong §103 challenges against essentially every independent claim, with claims 10 and 13 the most exposed and claim 1 the most contested (and only on the packaging/environment theory). The decisive vulnerability across the board is that the patent's own specification admits every element except the arrangement: co-housing, the specific sensor trios, and the use environments. KSR's "predictable use of prior art elements according to their established functions" is the controlling framework, and the five "prior art keywords" on the face of the record — vehicle, sensor, radio frequency, on-board computer, memory — are, functionally, the claim.