US 6718239

I'll search for authoritative information on US 6,718,239 across USPTO and court sources.

Now let me check for litigation and CAFC 2026 docket activity involving this patent.

Let me do a final check for any post-grant proceedings or 2026 court activity.

US 6,718,239 B2 — Verification Summary

Search scope note: I searched for the exact identifier "6718239" / "6,718,239." I found no CAFC 2026 docket, no PTAB/IPR proceeding, and no live litigation docket naming this patent. Several search hits for the bare numeric string "6718239" were false positives (e.g., a bankruptcy creditor list showing "6718239 +HUFF, SUSAN") and are not this patent — flagged and excluded per your instruction.

Bibliographic Data

Continuity chain (continuation-in-part series, all naming Rayner):
09/020,700 (filed 1998-02-09, abandoned) → 09/405,857 (now US 6,389,340 B1) → 09/611,891 (now US 6,405,112 B1) → 09/669,449 (now US 6,449,540 B1) → 09/732,813 (the patent at issue).

Abstract (as issued)

An event recorder (10) mounted in a vehicle (20) includes sensors, including image sensor (60), sound sensor (90), location sensor (95), and vehicle performance sensors, and a capture circuit for storing sensed data signals around a triggering event. A CPU and program memory (74) are programmed to perform a validation function, such as a one-way hash function, on the captured sensor signal while transferring it to persistent memory device (100) so as to derive a validation value which is also stored in persistent memory device (100). To later verify that the data have not be tampered with, the stored data are operated on by the same validation function so as to derive an audit validation value, the audit validation value is compared with the validation value for equality and the outcome of the comparison is indicated.

Cited prior art (of record)

US 5,497,419 (Prima Facie); US 5,815,093 (Lextron); US 6,163,338 (Johnson); US 6,011,492 (Garesche); and the two Rayner family members US 6,389,340 B1 and US 6,405,112 B1.

Independent Claims — Plain-Language Overview

Claim 1 (apparatus / combination). A vehicle plus an event recorder mounted to it. The recorder must have (a) sensors producing sensor signals, including a "first image sensing means" that produces a first image sensor signal, and (b) a microprocessor with memory that (i) receives and captures the sensor signals, including the image signal, "in readily readable form" during a time period, and (ii) runs a validation function over the captured signals to derive a validation value — all while leaving the captured image signal in readily readable form (i.e., not encrypted or scrambled).

Claim 15 (method). A method, practiced in an event recorder that has captured a sensor signal including an image signal in readily readable form while attached to a vehicle, of detecting memory tampering: perform a validation function on the captured signal to derive a validation value, again leaving the image signal readily readable.

Claim 21 (method). Same as claim 15, narrowed to the case where the validation function is specifically a hash validation function, producing a "valid hash value."

Claim 31 (method, broader). A method of detecting tampering with a captured data sensor signal (including an image signal in readily readable form) of an event recorder — notably not limited to the recorder being attached to a vehicle. This is the claim whose dependent claims (32–34) add transfer to a general purpose computer, which then independently recomputes an audit validation value and compares it.

Claim 36 (apparatus / combination). Same structure as claim 1 but limited to a "first image sensing means" alone — no requirement of the broader "sensors" set of claim 1.

Recurring limitation across all five independent claims: the captured image signal must remain "in readily readable form" — the specification explains the advantage is that unaltered data "may be more easily read" (i.e., validatable without a decryption/decompression step).

Verification Cautions / Uncertainty

1. Claim-language version discrepancy. A third-party text source (searchlight.law) reproduces the claims of the 2001 pre-grant publication without the "readily readable form" language, whereas the granted text (Google Patents / USPTO PDF) includes it throughout. Treat the granted 2004 text as authoritative; the "readily readable form" limitation was apparently added during prosecution. I did not pull the full prosecution history to confirm the amendment date.
2. Assignee. Multiple security interests were recorded over the years (Leader Ventures, Wells Fargo, U.S. Bank, HPS Investment Partners, Guggenheim Credit Services as successor agent). These are lien recordings, not ownership transfers; Lytx, Inc. remains the listed assignee.
3. Litigation. DriveCam/Lytx has an enforcement history (e.g., DriveCam v. SmartDrive, filed 2011, resolved 2012), but I could not confirm from the available sources that US 6,718,239 was among the asserted patents, nor that any of that activity involved the Federal Circuit in 2026. No 2026 CAFC docket number for this patent was found.
4. Expiration. Google Patents lists "Expired – Lifetime, expires 2018-08-13" (consistent with a 1998-02-09 priority date plus term adjustment). I did not independently verify the term-adjustment calculation against the official USPTO Patent Term Adjustment record.

I'll research litigation involving US patent 6718239 using the sources you mentioned.

Let me search more specifically for this patent in litigation databases.

Let me check the Unified Patents portal directly and search for any assertion of this specific patent.

Litigation Search Results: US Patent No. 6,718,239

Bottom line: I found no evidence of any litigation asserting U.S. Patent No. 6,718,239. Based on the searches conducted (Google Patents, Unified Patents portal content, PACER-derived dockets via PacerMonitor, CourtListener, Justia, and general web searches), this patent does not appear in any district court complaint, ITC action, or PTAB proceeding as an asserted or challenged patent.

What I checked

Important caveat — do not confuse with related cases

The patent is a continuation-in-part in the family of Gary A. Rayner / I-Witness / DriveCam / Lytx patents. Searches surfaced prominent Lytx/DriveCam litigation that does not involve 6,718,239. Reporting on it here would be incorrect if labeled as litigation over the '239 patent:

• DriveCam, Inc. v. SmartDrive Systems, Inc., No. 3:11-cv-00997-H-RBB (S.D. Cal., filed 2011) — asserted U.S. Pat. Nos. 6,389,340; 7,659,827; and 7,804,426 (per DriveCam's infringement contentions cited in later patent publications). The '239 patent is not listed among the asserted patents in those contentions. Note 6,389,340 is a sibling patent from the same Rayner family, which is likely why it appears in proximity — but it is a different patent number and must not be conflated.
• Lytx BIPA class actions (e.g., Lewis v. Maverick Transportation/Lytx, S.D. Ill.; Cavanaugh v. Lytx, N.D. Ill.; Timmons v. Gemini Motor Transport, N.D. Ill. 1:21-cv-05427; and related Ryder matters) — these are biometric-privacy (740 ILCS 14/1 et seq.) class actions about the DriveCam/MV+AI product. They are not patent cases and do not involve 6,718,239.
• Interstate Patents, LLC v. Waste Connections / Amerigas (E.D. Tex., 2026) and Fleet Connect Solutions LLC v. Ryder System (E.D. Tex. 2:22-cv-00160) — these assert other patents (e.g., US 8,098,277; US RE44,797; US 8,686,844; US 7,639,943; US 7,460,737; US 7,388,848; US 7,260,153; US 7,058,040) against Lytx-branded products. None lists 6,718,239.

Litigation table

Confidence and limitations

• Confidence: moderate-to-high that no publicly indexed litigation asserts this specific patent. The patent is a data-authentication/event-recorder patent held by Lytx (current assignee), and such patents are typically used defensively; combined with the absence of any hit across the docket aggregators searched, the negative result is credible.
• Limitations: I could not directly browse the Unified Patents litigation caselist page or PACER/CAFC dockets at the URL level within this session, so this is based on indexed search results rather than a line-by-line docket confirmation. A definitive negative would require running the exact number 6718239 in Docket Navigator, Lex Machina, or PACER's "Nature of Suit" search. I did not verify PTAB ex parte or reexamination records for this patent beyond the Google Patents legal-status "Expired – Lifetime (expires 2018-08-13)" entry.

If you need a definitive answer, the authoritative next step is a Docket Navigator or Lex Machina query on "6,718,239" restricted to patent case types, plus a PACER search of the CAFC docket for appeals naming the patent.

One correction to flag: None of the numbers you might see adjacent to "6718239" in search results are the patent — e.g., 6,718,210, 6,738,681, 8,677,398 are unrelated strings/patents. I have deliberately not substituted any similar number.

I'll check the structured ODP block first (no AIA proceedings listed) and then search for any proceedings the ODP may not have indexed.

PTAB Proceedings — US 6,718,239 B2 ("Vehicle event data recorder including validation of output")

Data sources for this report: (1) the structured "PTAB proceedings on file" block supplied in this prompt (USPTO Open Data Portal, most recent ingest) — zero AIA trial proceedings; (2) the authoritative Google Patents record at https://patents.google.com/patent/US6718239/en (biblio, family, cited-by, legal status); (3) targeted web searches for IPR/PGR/CBM activity, FWDs, settlement/termination documents, and CAFC appeals. I attempted four search passes and was cut off before exhausting them; see "Verification gaps" below.

Proceedings overview

Total AIA trial proceedings on file: 0 — no IPRs, no PGRs, no CBMs; breakdown is therefore 0 active / 0 claims invalidated / 0 claims sustained / 0 settled / 0 institution denied.

Bottom line for a defendant: this patent has never been tested in an AIA trial, so there is no claim-level kill to import into your case and no § 315(e)(2) estoppel to worry about — every prior-art ground remains open to you. The more consequential fact is not the PTAB silence but the docket sheet on the patent itself: US 6,718,239 is recorded as "Expired – Lifetime," expires 2018-08-13 (Google Patents legal status; priority date 1998-02-09). An expired patent cannot be infringed going forward, and on a 2026 assertion the § 286 six-year damages lookback (reaching back only to roughly 2020) falls entirely after expiration. The defensive posture is therefore not "hardened patent" but "zombie patent" — the realistic fight is over pre-2018 back damages, not an injunction.

Proceedings

None to report. There is no {PROCEEDING_NUMBER} to list, and I will not manufacture one. Specifically, I found no IPR/PGR/CBM petition, no institution decision, no Final Written Decision, no adverse judgment or termination, and no Federal Circuit appeal arising from a PTAB proceeding against this patent.

What I can say affirmatively about the record:

• The structured ODP block in this prompt returns no AIA trial proceedings for US 6,718,239. Consistent with the operating instruction, the default is "no PTAB activity on file."
• The Google Patents record shows no PTAB trial documents, no IPR certificates, and no "PTAB Proceedings" entries in the US09/732,813 prosecution/assignment history. The event timeline on that page runs from 1998-02-09 (priority) through assignments and security interests (I Witness → DriveCam 2006-06-21 → Lytx 2014-01-14 → HPS 2017-08-31 → Guggenheim 2020-02-28), with the only "adjusted expiration" entry being 2018-08-13. Nothing in the timeline is a Board proceeding.
• The patent's examiner-cited prior art (US 5,497,419 Prima Facie; US 5,815,093 Lextron; US 6,013,492 Garesche; US 6,163,338 Johnson; and the same-family Rayner patents US 6,389,340 and US 6,405,112) reflects prosecution-art, not an IPR ground set. These references are, however, exactly the kind of art a fresh petitioner would start from — and none of them is estopped to anyone.
• I found no evidence of Unified Patents or any other defensive aggregator filing on this patent. (Unified's patent portal surfaced only other Lytx-owned patents, and only as portfolio listings — no challenge to the '239.)

A note on what "no proceedings" does not mean: the absence of an IPR is not evidence that the patent is strong. It is evidence that the patent's useful life ended before the § 315(b) one-year windows that would have prompted challenges — the 1998 priority date put expiration in 2018, and DriveCam/Lytx's known assertion activity (see below) is not something I could tie to this specific patent number.

Strategic summary

Claim status: all 42 claims UNTESTED before the PTAB; zero CANCELED; zero SUSTAINED by the Board. The patent has five independent claims — claim 1 (combination: vehicle + event recorder with first image sensing means, microprocessor capturing sensor signals "in readily readable form" and performing a validation function while "leaving the captured first image sensor signal in readily readable form"); claim 36 (image-signal-only variant of claim 1); claim 15 and claim 21 (method-of-detecting-memory-tampering claims, the latter reciting a hash validation function); and claim 31 (method performed on a captured signal of an event recorder, including transfer to a general purpose computer). Dependent claims 2–14 and 16–20, 22–30, 32–35, and 37–42 add the usual narrowing: output ports (video output port in claim 8), persistent memory file storage, validation indicators, accelerometer (claim 9), location sensor (claim 10), time sensor (claim 11), speedometer (claim 12), hash calculation (claim 13), and the tamper-security recital (claim 14). Every one of those claims is untested at the Board — no estoppel, no cancellation, no Board claim construction to borrow.

Estoppel landscape: none. § 315(e)(2) estoppel attaches only to a petitioner (and its privies/real parties in interest) after an IPR that reaches a Final Written Decision. With no FWD on this patent, no party is estopped from anything, and there is no "grounds raised or reasonably could have been raised" trap. Practically, that means: (a) you may raise any § 102/§ 103 ground in district court, including grounds that overlap with art cited during prosecution; (b) if you file a first IPR, you are not fighting anyone else's prior estoppel or a prior Board construction; and (c) conversely, you get no free ride — there is no prior petitioner's work product to copy. The prosecution-cited art listed above (§102/§103 candidates from 1994–2000: Prima Facie, Lextron, Garesche, Johnson) is where a petition would begin, but note that the "readily readable form" limitations in every independent claim are the feature the patentee will lean on to distinguish a plain hash-and-store reference.

Pattern signals: no petitioner pattern, no Board repeater, no aggregator. There is no serial-IPR petitioner on this patent, no joinder, no POP request, and no CAFC appeal to track. The relevant commercial pattern is instead assignment and encumbrance churn on the asset (I Witness → DriveCam → Lytx → secured lenders Leader Ventures, Wells Fargo, U.S. Bank, HPS, Guggenheim), i.e. the patent functions as collateral in the Lytx corporate line rather than as an asserted IPR magnet. Separately, my search did surface active litigation in which Lytx is the alleged infringer (e.g. Interstate Patents, LLC v. Amerigas Propane, L.P., No. 9:26-cv-00276 (E.D. Tex.) and Interstate Patents, LLC v. Waste Connections, Inc., No. 9:26-cv-00277 (E.D. Tex.)), both asserting unrelated third-party patents (US 8,098,277; RE44,797; US 8,686,844; US 7,639,943; US 7,460,737; US 7,388,848) against Lytx products — not asserting the '239. That is a signal about the '239's commercial relevance, not a PTAB signal, and I flag it only as context with the caveat that I have not verified the complaints beyond the docket summaries quoted in search results.

One priority/validity caveat worth a petition drafter's attention: the '239 is a continuation-in-part (App. No. 09/732,813, filed 2000-12-11) in a chain going back to App. No. 09/020,700, filed 1998-02-09 (abandoned) → 09/405,857 (US 6,389,340) → 09/611,891 (US 6,405,112) → 09/669,449 (US 6,449,540). Google Patents lists the prior-art date as 1998-02-09 "as an assumption." Because the validation/hash subject matter that distinguishes the '239's independent claims was the CIP contribution, I could not verify from the record in this prompt whether the validation claims are actually supported under § 112 in the 1998 parent. If they are not, the effective filing date for the challenged claims is 1998-02-09 only for the carryover disclosure and 2000-12-11 (or 2000-09-25) for the validation limitations — a 22-month swing that materially changes the § 102(b) art window. I am flagging this as an unverified issue, not asserting a conclusion.

Recommended next steps

1. Treat "no PTAB activity" as the answer, but verify it directly before you rely on it. The ODP block is canonical and returns zero; my independent searches found nothing either. Confirm on the authoritative sources:

   • USPTO PTAB E2E / Patent Trial Practice Guide case search for Patent Number 6,718,239 (also check the Patent Center "Proceedings" tab for ex parte reexam, which is a Reexam unit proceeding and would not appear as an AIA trial).
   • PTAB Final Written Decisions library (https://www.uspto.gov/patents/ptab/decisions) — search "6,718,239" and "6718239."
   • Docket Alarm PTAB tab and the Unified Patents portal patent page for US 6,718,239.
   • CourtListener / PACER for any district case styled Lytx / DriveCam / I Witness asserting this patent, and for any CAFC appeal (caseName or patent-number search).

2. Run the damages math before spending on invalidity. Expiration is recorded at 2018-08-13. Under 35 U.S.C. § 286, recovery is limited to infringement within six years of the complaint — for a 2026 filing, that is roughly 2020 onward, which is entirely post-expiration. Confirm the expiration date from the Patent Center "Maintenance/Expiration" data (accounting for any terminal disclaimer or PTA) before you take the position; if it holds, the strongest defense may be the shortest one.

3. If you do face pre-expiration back damages, an IPR remains technically available — the Board can institute on an expired patent (claim construction then shifts toward Phillips rather than the BRI standard), but only if you have a live reason (e.g. a pending case seeking pre-2018 damages). Watch the § 315(b) one-year clock from service of the complaint, and note that the absence of any prior institution means there is no § 315(e) estoppel and no prior Board construction to leverage — you would be the first mover, with all grounds open.

4. Do not cite claim 1 as "cancelled" — it isn't. There is no FWD, no certificate, and no Board holding of any kind on any of claims 1–42. Any statement to the contrary would be a fabrication. If you need a kill-shot argument in a demand-letter response, build it from § 286/expiration and from the prosecution-cited art, not from a nonexistent PTAB outcome.

Verification gaps (stated plainly)

• I could not open PTAB E2E or the PTAB decisions database directly in this session; the "zero proceedings" conclusion rests on (a) the structured ODP block, (b) the Google Patents record, and (c) web searches that surfaced no IPR/PGR/CBM for this patent number. I consider the negative finding well-supported but not independently double-checked against the Board's own docket.
• One search query returned no usable results because I reached the session's tool-call limit; a further sweep (specifically: "IPR2014"/"IPR2015" Lytx DriveCam petition numbers, and a Docket Alarm PTAB-tab lookup by patent number) would make the negative finding airtight.
• I did not verify any district-court or CAFC proceeding specific to the '239; the litigation items mentioned above concern Lytx products accused under unrelated patents and are contextual only.
• All proceeding-related facts would be date-stamped 2026-09-30; if a petition was filed in the last few months, the ODP ingest may lag. Re-run the E2E search before relying on this.

I'll research the assignment record before drafting. Let me pull what I can from the authoritative sources.

Let me try to locate specific reel/frame data and correspondent names.

US 6718239 B2 — Assignment / Chain-of-Title Reconstruction

Data-quality note up front (read before the timeline). The authoritative source available to me this session was the Google Patents Legal Events table for US 6718239 B2 (https://patents.google.com/patent/US6718239B2/en), which mirrors the USPTO assignment index. That feed exposes conveyance type, counterparties, and dates, but not reel/frame numbers and not the correspondent of record. I attempted to retrieve those two fields directly from the USPTO Assignment Center and via indexed mirrors (uspto.report, third-party patent portals) and could not obtain them. Rather than fabricate reel/frame numbers or attorney names, I have flagged those fields as "not retrieved" throughout. See the verification instructions at the end for pulling them yourself.

Inventors

Only one inventor is named on this patent. The four applications in this CIP chain (Ser. Nos. 09/020,700; 09/405,857; 09/611,891; 09/669,449; 09/732,813) are all Rayner-only filings, so there is no multi-inventor team, no inventor-concentration signal, and no "inventors departed within 12 months" pattern.

Adjacent name I want to handle precisely: A PTAB petition exhibit lists the DriveCam prior-art lineage as "I‑Witness Incorporated / Gary Rayner / Gary Etcheson / DriveCam Inc. / Lytx Inc." (https://ptacts.uspto.gov/ptacts/public-informations/petitions/1556487/download-documents). Gary Etcheson is a DriveCam co-founder and appears in the corporate/product history — he is NOT a named inventor on US 6718239. Do not list him as an inventor.

Pattern noted: Rayner assigned to I‑Witness on 2000‑12‑08, three days before the application was filed on 2000‑12‑11 — a clean pre-filing assignment, the standard operating-company practice. No gap, no retained reversion, no post-hoc cleanup. This is the opposite of a fire-sale tell.

Original assignee

• Entity on the issued patent (2004‑04‑06): I‑Witness, Inc., original assignee — renamed DriveCam, Inc. effective the 2006‑06‑21 change-of-name record.
• Primary line of business: Vehicle event data recorders / video telematics for commercial and government fleets. The patent's own FIG. 1–2 embodiments are the mirror-mounted and windshield-mounted DriveCam-style units.
• Did they ship a product embodying the claims? Yes. The DriveCam event recorder shipped continuously: PTAB filings date the DriveCam product to "on or before Nov. 2002," and DriveCam/Lytx user manuals, installer guides and brochures from 2002–2006 appear as prior art and evidence in later inter partes filings (US9836716, US9344683 reference lists). The claims recite exactly that product architecture.
• Current status: Operating. I‑Witness → DriveCam, Inc. → Lytx, Inc. (name changed 2014‑01‑14 per the assignment record; corporate name change announced Nov 2013). Lytx remains an operating company at 9785 Towne Centre Drive, San Diego, CA, selling DriveCam/Lytx Video Services; a 2016 municipal purchase order and current product brochures confirm active commerce. No bankruptcy, no dissolution, no patent-holding-only affiliate took title.

Assignment timeline

All entries below are from the Google Patents Legal Events feed for US 6718239 B2. Reel/frame and correspondent are NOT RETRIEVED for any entry — see the caveat at the top and the verification note at the end. Google's feed does not cleanly separate execution date from recording date, so each date is given as recorded unless the platform labels it otherwise.

• 2000‑12‑08 (recorded) — Reel not retrieved

  • Conveyance: Assignment of assignors' interest (SEE DOCUMENT FOR DETAILS)
  • Assignor: RAYNER, GARY A.
  • Assignee: I‑WITNESS, INC.
  • Correspondent: not retrieved
  • Context: Initial inventor-to-company assignment, executed three days before the 2000‑12‑11 filing. Ordinary course.

• 2006‑06‑21 (recorded) — Reel not retrieved

  • Conveyance: Change of Name
  • Assignor: I‑WITNESS, INC.
  • Assignee: DRIVECAM, INC.
  • Correspondent: not retrieved
  • Context: Internal reorg / corporate rename only. No change of beneficial owner, no consideration, no third party.

• 2009‑08‑19 (recorded) — Reel not retrieved

  • Conveyance: Security Agreement
  • Assignor: DRIVECAM, INC.
  • Assignee: LEADER VENTURES, LLC, AS AGENT
  • Correspondent: not retrieved
  • Context: Securitization — patent pledged as collateral for a venture-debt facility. Encumbrance, not a transfer of title.

• 2009‑08‑19 (recorded) — Reel not retrieved

  • Conveyance: Security Agreement
  • Assignor: DRIVECAM, INC.
  • Assignee: WELLS FARGO BANK, NATIONAL ASSOCIATION
  • Correspondent: not retrieved
  • Context: Securitization — same-date collateral pledge to the senior lender. Encumbrance, not title transfer.

• 2013‑01‑23 (recorded) — Reel not retrieved

  • Conveyance: Release by Secured Party
  • Assignor: LEADER VENTURES, LLC
  • Assignee: DRIVECAM, INC.
  • Correspondent: not retrieved
  • Context: Debt repaid / collateral released back to the company. No ownership movement.

• 2014‑01‑14 (recorded) — Reel not retrieved

  • Conveyance: Change of Name
  • Assignor: DRIVECAM, INC.
  • Assignee: LYTX, INC.
  • Correspondent: not retrieved
  • Context: Internal reorg / corporate rename only. (Note the record date lags the announced Nov 2013 rebrand.)

• 2014‑01‑29 (recorded) — Reel not retrieved

  • Conveyance: Security Agreement
  • Assignor: LYTX, INC. and MOBIUS ACQUISITION HOLDINGS, LLC
  • Assignee: WELLS FARGO BANK, NATIONAL ASSOCIATION, AS AGENT
  • Correspondent: not retrieved
  • Context: Securitization — new credit facility; patent re-pledged together with a co-grantor affiliate. The record does not explain Mobius Acquisition Holdings, LLC; I am not inferring its role.

• 2016‑03‑15 (recorded) — Reel not retrieved

  • Conveyance: Security Interest
  • Assignor: LYTX, INC.
  • Assignee: U.S. BANK NATIONAL ASSOCIATION, AS ADMINISTRATIVE AGENT
  • Correspondent: not retrieved
  • Context: Securitization — refinancing; collateral agent swapped from Wells Fargo to U.S. Bank.

• 2016‑03‑15 (recorded) — Reel not retrieved (two separate records, same date)

  • Conveyance: Release of Security Interest (one general, one expressly captioned "RELEASE OF SECURITY INTEREST IN INTELLECTUAL PROPERTY," recorded against Wells Fargo's earlier reel/frame)
  • Assignor: WELLS FARGO BANK, NATIONAL ASSOCIATION
  • Assignee: LYTX, INC. (formerly known as DriveCam, Inc.)
  • Correspondent: not retrieved
  • Context: Collateral released on payoff of the Wells Fargo facility. No ownership movement.

• 2017‑08‑31 (recorded) — Reel not retrieved

  • Conveyance: Security Interest
  • Assignor: LYTX, INC.
  • Assignee: HPS INVESTMENT PARTNERS, LLC, AS COLLATERAL AGENT
  • Correspondent: not retrieved
  • Context: Securitization — third collateral-agent restructuring (private-credit lender replacing bank lender).

• 2017‑08‑31 (recorded) — Reel not retrieved

  • Conveyance: Release by Secured Party
  • Assignor: U.S. BANK, NATIONAL ASSOCIATION
  • Assignee: LYTX, INC.
  • Correspondent: not retrieved
  • Context: U.S. Bank collateral released on payoff. No ownership movement.

• 2020‑02‑28 (recorded) — Reel not retrieved

  • Conveyance: Notice of Successor Agent and Assignment of Security Interest (reel/frame 043745/0567 referenced in the record caption)
  • Assignor: HPS INVESTMENT PARTNERS, LLC
  • Assignee: GUGGENHEIM CREDIT SERVICES, LLC
  • Correspondent: not retrieved
  • Context: Securitization — successor collateral agent on the existing secured facility. Still an encumbrance, still not title.

Bottom line on the chain count: thirteen recorded events, but only ONE of them (the 2000‑12‑08 inventor assignment) moves beneficial title. Two are pure renames. The remaining ten are collateral pledges, releases, and a successor-agent notice. There is no recorded assignment of the patent to any third-party acquirer, ever. The patent expired 2018‑08‑13.

Timeline diagram

timeline
    title Ownership of US 6718239
    1998 : Earliest priority filing
    2000 : Application filed
         : Rayner assigns to I-Witness Inc
    2004 : Patent issued
    2006 : I-Witness renamed DriveCam Inc
    2009 : Security agreement to Leader Ventures
         : Security agreement to Wells Fargo
    2011 : DriveCam sues SmartDrive Systems
    2013 : Leader Ventures releases collateral
    2014 : DriveCam renamed Lytx Inc
         : Wells Fargo security agreement
    2016 : US Bank takes security interest
         : Wells Fargo releases collateral
    2017 : HPS takes security interest
         : US Bank releases collateral
    2018 : Patent expires
    2020 : Guggenheim succeeds HPS as agent

NPE / troll-pattern signals

1. Shell-entity transfer — NOT PRESENT.
There is no recorded transfer of title from an operating assignee to a licensing-only vehicle. The three LLCs in the chain — Leader Ventures, LLC (2009), HPS Investment Partners, LLC (2017), Guggenheim Credit Services, LLC (2020) — appear only as secured lenders/agents, and each is followed by a matching release or successor-agent record. Lenders holding a security interest are not assignees of title. Title has sat with the operating company (I‑Witness → DriveCam → Lytx) since 2000‑12‑08.

2. Known asserter in the chain — NOT PRESENT.
No assignee at any point matches Acacia, Marathon, Intellectual Ventures, IPNav, Wi‑LAN, Conversant/Mosaid, Vringo, Pendrell, Innovatio, MPHJ, Lumen View, Round Rock, Document Generation, or any Spangenberg entity. Current assignee is Lytx, Inc., a product company.

3. Repeat correspondent across the chain — UNKNOWN / NOT DETERMINABLE.
This is the one signal I cannot resolve, and it is the signal you specifically asked me to capture. The Google Patents legal-events feed does not carry the correspondent of record, and I could not reach a source that exposes it this session. I will not invent attorney names or reel/frame numbers. Flagging it as an open item rather than a "not present" finding, because absence of evidence here is my access limitation, not a fact about the record.

4. Cascading transfers — NOT PRESENT (with a nuance worth stating).
There is no chain of consecutive LLC-to-LLC title assignments. What does look cascade-shaped at a glance is the collateral-agent rotation: 2014‑01‑29 (Wells Fargo) → 2016‑03‑15 (U.S. Bank) → 2017‑08‑31 (HPS) → 2020‑02‑28 (Guggenheim), four agent changes in six years, each preceded or followed by a release. This is the fingerprint of serial debt refinancing by a leveraged private company, not NPE chaining: in every instance the grantor remains Lytx, Inc., and every pledge is discharged on payoff. Do not score this as a troll signal.

5. Pre-litigation transfer — NOT PRESENT.
DriveCam sued SmartDrive Systems in DriveCam, Inc. v. SmartDrive Systems, Inc., No. 3:11-CV-00997-H-RBB (S.D. Cal.), with infringement contentions exhibited Aug 2011 and an amended complaint filed 2011‑10‑20. The nearest recorded assignment event before that suit is the 2006 change of name — five years earlier. Nothing was transferred into a new holder within six months of filing. The 2013‑01‑23 release came after the litigation.

6. Bankruptcy fire-sale — NOT PRESENT.
No Chapter 7/11 record appears in the assignment chain, and no distress-sale assignment is recorded. I found no bankruptcy of I‑Witness/DriveCam/Lytx in any source reviewed this session. (I did not run a dedicated PACER/Delaware docket search — treat this as "no evidence found," not as a positive clearance.)

7. Privateering — NOT PRESENT.
No transfer to a third-party NPE asserting on Lytx's behalf. Any assertion in the family was made by the operating company itself (DriveCam v. SmartDrive, 2011).

8. Defensive aggregator — NOT PRESENT.
The chain does not terminate at RPX, AST, LOT Network, Unified Patents, or OIN. It terminates at Lytx, Inc. The patent has not been neutralized defensively; it simply expired 2018‑08‑13 ("Adjusted expiration").

Caveat on assertion of this patent: The 2011 DriveCam infringement contentions I located name Exhibits A/B/C for US 6,389,340, US 7,659,827 and US 7,804,426 — three sibling patents in this same Rayner CIP family. I did not find 6,718,239 itself named in a DriveCam/Lytx infringement contention. It does appear as prior art cited against later filings (e.g. cited on the face of Lytx's US 9,344,683). Treat "this specific patent was asserted" as unverified; treat "the family was asserted by the operating company" as verified.

Verdict

Operating-company assertion.

The chain of title never leaves the company that made the product: Gary A. Rayner assigned to I‑Witness, Inc. on 2000‑12‑08, I‑Witness renamed itself DriveCam, Inc. on 2006‑06‑21, and DriveCam renamed itself Lytx, Inc. on 2014‑01‑14 — two change-of-name records and one inventor assignment are the entire beneficial-ownership history. Every other entry (Leader Ventures 2009‑08‑19; Wells Fargo 2009‑08‑19 and 2014‑01‑29; U.S. Bank 2016‑03‑15; HPS 2017‑08‑31; Guggenheim 2020‑02‑28) is a security interest, a release, or a successor-agent notice on a secured credit facility, with Lytx remaining the grantor throughout. The assignee ships DriveCam/Lytx event recorders embodying the claims and asserted sibling patents in this family against SmartDrive Systems in 2011. No NPE signal fires in this record.

Postscript worth flagging to whoever consumes this: the correct conclusion here is boring, and that is a finding in itself. The absence of reel/frame and correspondent data is my limitation, not the record's — a repeat-correspondent check on the ten collateral/agent recordings is the only loose thread, and it would test the (unlikely) hypothesis that Lytx's financing counterparties are affiliated.

Caveat: Nothing above is a legal conclusion on current ownership or standing. USPTO recordation is ministerial and the Office does not verify the underlying documents (37 CFR Part 3; USPTO Assignment Database webinar, 2015‑01‑20).

Verification

• USPTO Assignment Center (search "6718239"): https://assignmentcenter.uspto.gov/ — and the legacy index at https://assignment.uspto.gov/patent/index.html
• Google Patents legal events (used here): https://patents.google.com/patent/US6718239B2/en
• To fill the gap I could not fill: on the Assignment Center, open each hit for US 6718239 and record the Reel/Frame and Correspondent fields. You should expect ~13 records matching the dates above. The reel/frame cited inside the 2020‑02‑28 Guggenheim caption (043745/0567) is the HPS security-interest reel — that is the predecessor recording's number, not a 2020 reel, and it is a useful anchor for cross-checking the HPS entry.
• Litigation cross-check: DriveCam, Inc. v. SmartDrive Systems, Inc., No. 3:11-CV-00997-H-RBB (S.D. Cal.), for the 2011 assertion activity.
• Corporate history cross-check: Lytx Wikipedia entry for the Nov 2013 DriveCam→Lytx rebrand (note the ~2-month lag before the 2014‑01‑14 assignment record).

I'll search for the specific patent and its cited prior art references.

Let me gather details on the remaining cited references.

Let me get the remaining references and verify against the USPTO record.

Search result for the specific number

I ran the identifier search strictly on 6718239. The authoritative record returned is Google Patents' full-text page for US 6,718,239 B2 (which mirrors the USPTO grant PDF at patentimages.storage.googleapis.com/.../US6718239.pdf), corroborated by uspto.report/patent/grant/6718239 and the Justia pre-grant record for 2001/0005804 A1. No results for "similar" numbers were accepted, and the earlier-flagged false positive ("6718239 +HUFF, SUSAN" bankruptcy entry) remains excluded.

Bibliographic data confirmed: application 09/732,813, filed 2000-12-11, granted 2004-04-06, 42 claims, sole inventor Gary A. Rayner, original assignee I-Witness, Inc., current assignee Lytx, Inc. Consistent with the previously generated summary — no contradiction found.

The six patent citations of record

US 6,718,239 lists six references (Google Patents "Patent Citations (6)"), all examiner-cited:

¹ The Justia assignee page renders it "Prime Facie, Inc."; Google Patents renders "Prima Facie, Inc." I flag the spelling variance rather than correcting it. Note also the related continuation US 5,646,994 ("Method and apparatus for recording sensor data") surfaced in search.

Reference-by-reference analysis

1. US 5,497,419 — Prima Facie, Inc. (the most relevant reference)

• Description: Records sensor data alongside a concurrent analog video signal. Analog signals are digitized, redundant signals compressed, and "the resulting compressed and uncompressed signals are encrypted and stored on a removable hard disk." The stated object is that on playback the system assures "that the played back signals are correct reconstructions of the original signals." The specification also discloses encoding gray-scale/color so consecutive digital values do not represent consecutive grays/colors, choosing a font "very difficult to reproduce if an attempt is made to modify the video data, but very easy to verify as valid if no attempt to modify … has been made."
• Why it matters: This is the only of-record reference that squarely addresses the integrity/authentication problem the '239 patent is about. It is the closest prior art to the core validation concept.
• Claims it potentially anticipates (§102(b)): 1, 15, 21, 31 and 36 only if the "readily readable form" limitation is construed loosely. Its express encryption/compression teaching cuts the other way — the '239 specification even states the advantage of not encrypting is that data "may be more easily read." So US 5,497,419 is best characterized as a strong §103 reference, and a §102(b) anticipation candidate against dependent claims 13 (hash calculation — the "easy to verify as valid" encoding is the analogous integrity check), 14 / 20 / 26 (secure from tampering), and 19 / 25 (comparison + indication of outcome), rather than against the independent claims read as a whole.

2. US 5,815,093 — Lextron Systems, Inc.

• Description: "Computerized vehicle log" — a digital camera (CCD) with multi-sectored flash memory storing images sequentially and overwriting the oldest sector; an interrupter (impact or rollover sensor) freezes recording, "providing a visual record of a period of time immediately preceding an accident." Adds vehicle transducers (speed, fuel flow, RPM, temperature), GPS, and download via transfer terminal or radio transceiver.
• Claims it potentially anticipates (§102(e)): the apparatus elements of claims 1 and 36 (vehicle + recorder + image sensing means + microprocessor/memory capturing an image signal during a time period) and the sensor limitations of claims 9–12 (accelerometer, location/GPS, speed). It contains no validation function, no validation value, and no audit comparison, so it cannot anticipate claims 1, 15, 21, 31 or 36 as issued. Its real value is as the §103 backbone combined with a hashing reference.

3. US 6,163,338 — Johnson

• Description: Circular-buffer video/audio recorder frozen by an event-detection mechanism (accelerometer/threshold circuit), storing frames before and after the event, downloaded to a personal computer via a serial port. Notably, "the serial port 19 will have a tamper proof seal so that a third party can certify to the integrity of the data," with optional "hardware keys, software codes, or transmitted radio frequency signals to unlock the data … to ensure that the data is genuine."
• Claims it potentially anticipates (§102(e)): the capture/trigger/download structure of claims 1, 15, 31 and 36 and the transfer-to-general-purpose-computer steps of claims 32–34. Its "tamper proof seal … to certify to the integrity of the data" is relevant to claim 14 ("secure from tampering") and claims 19/25 (indicating the outcome). Again, no hash/validation-value limitation — so no literal anticipation of the independent claims, but it is the strongest §103 partner for the download-and-verify step.

4 & 5. US 6,389,340 B1 and US 6,405,112 B1 — Rayner

• Description: The two immediate family parents (continuation-in-part chain: 09/405,857 → 09/611,891 → 09/669,449 → 09/732,813). Both are named to the same sole inventor as the '239 patent and share the same 1998-02-09 priority.
• §102 caveat (important): Because these are the applicant's own earlier patents, they are not "by another" and therefore are not proper pre-AIA §102(a), (b), or (e) references against US 6,718,239. They were cited in prosecution (Google Patents marks them examiner-cited) but function as family/continuity citations — usable for obviousness-type double patenting or as evidence of what was already the inventor's own disclosure, not as §102 art. Any statement that they "anticipate" the '239 claims would be incorrect. I flag this as the one place where a naive reading of the citation table would mislead.

6. US 6,011,492 — Garesche

• Description: A vehicle safety warning system, not a recorder. A horn/siren/flashing-light activation triggers an RF transceiver that illuminates a dashboard warning light in nearby vehicles.
• Claims it potentially anticipates (§102(a)/(e)): None of claims 1–42. It discloses no event recorder, no image sensing means, no capture memory and no validation function. Its relevance is confined to the wave-pattern-detector trigger subject matter described in the '239 specification (detecting police radar, laser, flash, siren) — subject matter that was claimed in parent US 6,449,540 B1, not in the '239 claims. It is a background/§102(a) reference only.

Bottom line for the §102 question

Careful conclusion, stated with the uncertainty I actually have:

1. No one of the six cited references discloses, and therefore none literally anticipates, any of independent claims 1, 15, 21, 31 or 36 as issued. Every independent claim requires (a) a captured image signal held "in readily readable form," and (b) a validation function → validation value → audit validation value → compare sequence. Items 2, 3 and 6 lack (b); item 1 has integrity verification but through encryption, which conflicts with (a).
2. Most relevant prior art ranking: (i) US 5,497,419 — closest on the authentication concept; (ii) US 6,163,338 — closest on ring-buffer capture + download + "certify integrity"; (iii) US 5,815,093 — closest on the vehicle-mounted image-recorder apparatus; (iv) US 6,011,492 — marginal/background; (v–vi) the two Rayner parents — not §102 art.
3. Anticipation burden therefore falls on the dependent claims — principally claim 13 (hash calculation), claims 14, 20, 26 (secure from tampering) and claims 19, 25 (compare + indicate) — where US 5,497,419 and US 6,163,338 are the candidates, and the five independent claims are defendable only via the specific readily-readable + hash-validation-value combination.
4. Priority nuance that changes the §102 calculus: the "readily readable form" and validation limitations appear to be new matter introduced in the 2000-12-11 CIP (the earlier generation section flagged that the 2001 pre-grant publication's claims lack that language). If the validation claims are not entitled to the 1998-02-09 date, then US 5,815,093 (issued 1998-09-29) also becomes a §102(b) reference once the critical date is counted, strengthening the art. I have not reviewed the parent specifications to confirm where the validation disclosure first appears — this is a genuine open item, not a conclusion.

Not of record but surfaced during the identifier search (lead only): US RE41,395 E, "device for authenticating and securing control event data in a vehicle," describing time-stamp/VIN locking and reporting "unauthorized data tampering." I could not confirm its listing among the '239 citations (it appeared as a search hit, not in the citation table), so I am not treating it as of-record art. It deserves separate verification if you want a §102/§103 sweep beyond the six citations.

Not independently verified: exact claim-level correspondence to the examiner's stated reasons of allowance; I have the citations and their texts, but did not pull the '239 file wrapper to see which reference the examiner relied on for which claim.

I'll ground this analysis in the actual content of the six references of record. Let me pull their disclosures.

Now let me pull the other two cited references and the Rayner family members.

Let me verify the content of the two Rayner family references and check for any hash/validation disclosure in them.

Obviousness Analysis — U.S. Patent No. 6,718,239 B2

Method note. This analysis uses only the six references in the "Patent Citations" (Prior Art) section of the Google Patents page, plus the patent's own specification as an admission source. I treat the granted 2004 claim text as authoritative (consistent with the earlier Patent Summary). Where a reference date or disclosure matters and I could not verify it, I say so.

I. Governing framework

The application was filed 2000-12-11 and claims CIP benefit back to 1998-02-09. It is therefore governed by pre-AIA 35 U.S.C. § 103(a). The controlling question under Graham v. John Deere and KSR Int'l Co. v. Teleflex Inc., 550 U.S. 398 (2007), is whether the differences between the claims and the prior art would have been predictable to a person of ordinary skill, not merely whether each element appears somewhere.

Level of ordinary skill (proposed): a bachelor's degree in electrical engineering, computer engineering, or computer science, or equivalent, plus 2–3 years of experience with embedded video/data acquisition systems and data-security primitives (encryption/hashing). This is the level reflected in the '239 specification itself, which states that "One-way hashing is known to those skilled in the art" and that "One skilled in the art will readily be able to program memory 74 to carry out the one-way hash process."

II. Prior-art status of the references of record

Two important consequences:

1. The three core references (Hill, Kikinis, Johnson) are prior art on any theory of the effective filing date — whether the claims get the 1998-02-09 date or only the 2000-12-11 CIP date (i.e., if the validation subject matter is new matter). Hill is §102(b); Kikinis and Johnson are §102(e) as of 1996-07-26 and 1997-12-11. This makes the analysis robust to the priority question. Only Garesche is priority-sensitive.
2. The two Rayner patents should not be relied on as §103 art. They appear on the face of the patent as citations, but they share the same sole inventor and family. They are best used as evidence of what the applicant understood the art to be (see §III), not as statutory prior art.

Garesche (US 6,011,492) discloses a horn/siren-triggered transceiver that lights a dashboard warning lamp in a nearby vehicle. It is analogous only as background to the parent's wave-detector claims and is not a meaningful §103 reference for the validation claims. I do not force a combination from it.

III. The most useful admission in the record

The applicant's own sibling patent US 6,389,340 (incorporated by reference into the '239) describes the field and characterizes Hill's '419 as follows:

"U.S. Pat. No. 5,497,419 to Hill discloses a device for recording sensor data which included provisions to compress and decompress data, as well as to encrypt the stored data to enhance the integrity of the data."

and frames the field's unmet need as data that are "secure so that it could be admitted in proceedings to determine liability."

This is an applicant admission that (a) Hill is analogous art in the same field, (b) Hill was understood to address data integrity, not merely confidentiality, and (c) evidentiary admissibility was the recognized design driver. That forecloses a non-analogous-art defense and supplies much of the motivation.

IV. Element-level mapping of the independent claims

V. Obviousness combinations

Combination A (primary): Kikinis '093 + Johnson '338 + Hill '419 + the admitted knowledge of cryptographic hashing

Claim 1 / 36. Kikinis supplies the "vehicle + mounted event recorder + image sensing means + microprocessor with memory capturing sensor signals during a time period" structure, including the accelerometer, GPS, speed and engine-speed sensors recited in dependent claims 9–12. Johnson supplies the trigger-frozen circular buffer and the express evidentiary-authentication objective. Hill supplies the concept of recording vehicle sensor data with video and protecting it so that "played back signals are correct reconstructions of the original signals." The only missing element — deriving a validation value via a one-way hash — was, by the applicant's own admission, a known, off-the-shelf technique that any skilled person could implement.

Claim 13 is the clearest case. Under KSR rationale (C) — "use of a known technique to improve similar devices in the same way" — selecting MD5 or SHA as the integrity primitive for a recorder whose data must withstand evidentiary challenge is a predictable application of a known tool, and the choice among MD5/MD2/MD4/SHA/HAVAL is at most a routine design choice among equivalents the specification itself lists.

Claims 2, 16, 17, 22, 23, 32, 37 (transmit data and validation value via the output port): Kikinis claim 5 and Johnson's serial-port download already disclose transferring the captured data to an external device. Once the validation value exists, the reason to transmit it with the data is intrinsic — an auditor cannot re-compute and compare without it. This is the definition of a predictable, functionally dictated design.

Claims 3, 18, 24, 38 (store in a file on persistent memory; recompute the same function on the file): Kikinis stores images one-per-sector in non-volatile flash; Johnson stores to non-volatile memory and permits repeated download. Organizing the captured record as a discrete file/address block, and re-running the integrity function over that same block, is conventional data management.

Claims 4, 6, 7, 19, 25, 34, 39, 41, 42 (compare and indicate the outcome): Hill's playback verification is the same function; Kikinis's external display and Johnson's PC download provide the indication hardware. The '239's own "validation key 132" is a switch, not a cryptographic key element.

Claim 35 (hash performed while transferring to persistent memory and the value stored there): this recites mere sequencing of two steps a POSITA would perform as a single write-and-hash pass; Kikinis copies the buffer contents into flash at trigger time, giving the natural occasion to compute the value.

Claim 31 (preamble omits "attached to a vehicle") is broader still and is met by the same combination applied to any event recorder.

Combination B: Hill '419 as primary + Kikinis '093 + Johnson '338

Hill is the closest art on the problem: it records sensor data with a concurrent video signal, compresses, encrypts, stores on removable media, and plays back with assurance of correct reconstruction — functionally identical to "validating that output data have not been changed from the original recorded data." Its deficiencies are (i) that it provides integrity via encryption/decryption rather than a stored validation value, and (ii) that encryption destroys the "readily readable" character the claims require. Kikinis and Johnson supply the vehicle-mountable, trigger-driven, plaintext recorder. See §VI for why (ii) is not a teaching away.

Combination C: Johnson '338 as primary + Kikinis '093 + Hill '419

Johnson is the single most dangerous reference because it discloses the buffer-freeze-on-trigger architecture, download-to-PC, accelerometer triggering, and — critically — an express statement of the same unmet need: a "tamper proof seal so that a third party can certify to the integrity of the data" and mechanisms "to ensure that the data is genuine." Johnson's data path is plaintext end-to-end, so the "readily readable form" limitation is satisfied without modification. Adding a known hash to Johnson's recorder is the textbook KSR case: a known technique applied to a known device that was already identified as ready for improvement, with the improvement yielding the predictable result (third-party verification).

VI. Motivation to combine

1. Same field, same problem, same art. All three references are vehicle data/event recorders combining video with vehicle sensor data for post-hoc investigation of collisions. KSR holds this weighs heavily toward obviousness.
2. The references themselves articulate the motivation. Hill protects sensor data and verifies correct reconstruction; Johnson demands third-party certification of integrity and data that "is genuine"; Kikinis seeks to "lower[] costs in accident investigation and litigation." The '239's stated problem — "the veracity of the recorded evidence can be challenged… may have been altered" — is the identical problem. No hindsight is needed to connect them; the prior art states the objective.
3. The counterintuitive part cuts for obviousness, not against it. Hill encrypts; the claims require plaintext. But the '239's own rationale is that data in readable form "may be more easily read." A POSITA facing the specific problem the '239 identifies — an adversary arguing "the evidence has been in the control of the offeror… and may have been altered" — has a concrete reason to prefer a hash over plaintext to encryption: an encrypted file cannot be independently verified by a third party without surrendering the key to the data's custodian, which is exactly the vulnerability the '239's Background describes and exactly what Johnson's "keys to unlock the data" and "tamper proof seal" aim at. Hashing the plaintext yields verifiability without custody of a decryption key. So the art supplies a reason to make the very choice (hash, don't encrypt) that the claims recite.
4. The omission of encryption is a negative limitation, not an inventive step. Excluding a known, optional step — Kikinis claim 11 makes encryption optional ("one or both of encryption and data compression"); Hill makes it a design choice — is at most an obvious alternative (KSR: a "mere change in design" / obvious to try).
5. Market and legal incentives. KSR expressly credits "design incentives and other market forces." Both the '239 and the cited art identify evidentiary admissibility, insurance claims, and litigation cost as the drivers. The demand existed and was documented in the art.
6. Implementation was routine. The '239's own specification concedes hashing is known and easily programmed, and enumerates standard algorithms. That concession converts the only missing element into a matter of ordinary engineering.

VII. Where this obviousness case is weakest (candid assessment)

I do not think the challenges are clean, and a petitioner or examiner would face three real problems:

1. No reference discloses storing a validation value in the same file as the data, then re-running the function on that file and comparing. Hill's integrity mechanism is decryption-based; Johnson's is a physical seal plus access keys. Neither teaches the self-authenticating record — data and its digest co-located in a persistent file, recomputable later by an independent party. That specific architecture is the actual point of novelty, and it must be supplied by "common knowledge" rather than by an express disclosure. Patent Owner will argue this is the impermissible use of the claims as a roadmap (In re Kahn).
2. Possible teaching away by Hill (and by Kikinis claim 11). The strongest nonobviousness argument is that the field's integrity solution was obfuscation (encryption), and the claims require its absence. If the art is read as teaching that data must be encrypted to be trustworthy, the "readily readable form" limitation is nonobvious. I find this argument weak but not frivolous, because the references frame encryption as the integrity mechanism rather than merely as confidentiality.
3. Priority / new-matter risk and reference-date risk. If the validation subject matter is new matter added in the CIP chain (the '239's Background phrases the validation system as an unmet need, which suggests it was not in the parents — I did not verify the parents' disclosures on this point), the effective date is 2000-12-11. That does not disturb Hill/Kikinis/Johnson, but it does mean the Garesche reference (filed 1998-06-30) remains only §102(e) art and is of little substantive value here. Conversely, if the claims are entitled to 1998-02-09, Garesche drops out entirely. Either way, the three core references survive.
4. Secondary considerations. The '239's Background states a long-felt need, and Lytx/DriveCam's commercial presence in fleets is real. Patent Owner would point to those under Graham. The counter is that the '239 itself attributes the need to a lack of a device, not a lack of capability, and simultaneously admits the solution technique was known and easily implemented — which weakens the nexus between the asserted need and the claimed advance.
5. A lead I could not verify. The "Cited By" table shows US 2002/0145666 A1 (Scaman, "Incident recording secure database"), priority 1998-06-01, i.e., a third party working on secure/authenticated incident recording on a parallel track. Near-simultaneous independent development is recognized objective evidence of obviousness. It is not a reference of record and I have not reviewed its disclosure, so I flag it only as a lead for a searcher, not as a basis for this opinion.

VIII. Bottom line by claim

Cross-reference check against prior sections: this is consistent with the earlier Patent Summary (five independent claims, all carrying the "readily readable form" limitation; 42 claims; the pre-grant publication's 39 claims lacking that language, suggesting a prosecution amendment) and with the Litigation Summary (no proceeding names the '239). One incidental confirmation of the earlier negative: IPR2014-01010 (TRW Automotive) used US 6,389,340 — the sibling Rayner patent — as Exhibit 1005, reinforcing that the family was litigated over but the '239 was not. No contradiction found.

Confidence and limits. I have read the claims and specification of the '239 in full and the abstracts, claim sets, and substantial description excerpts of US 5,497,419, 5,815,093, 6,163,338, and 6,011,492. I have not retrieved the full text of US 6,405,112, and I have not verified (a) whether validation subject matter appears in the '239's parent applications, (b) the actual prosecution history / reason for the "readily readable form" amendment, or (c) the full claim-by-claim disclosure of the Rayner family patents. Statements resting on those points are flagged above as inferences.