US 6950013

I'll search for authoritative information on this patent number before summarizing.

Let me run a couple more targeted searches on litigation/appellate history for this specific patent.

Scope note

I searched for U.S. Patent No. 6,950,013 (application 10/158,837), interpreting the identifier "6950013" literally. I found no CAFC docket activity in 2026 (or any year) for this patent, and no 2026 USPTO proceeding. The only contested proceedings I could locate are older and are summarized below. I explicitly excluded results for other numbers that search engines returned alongside this one (e.g., an ex parte reexamination 90/015,984 concerning Patent 8,810,458, and the Wilus/Samsung IPRs 2025-00929/00933/00934/00988/01069); those do not involve 6,950,013 and are not reported here.

---

Bibliographic data

---

Abstract (verbatim)

"A device and method for permanently and securely storing incident information, relating to a vehicle, from remote download to create a secure non-tamperable, permanent database of criminal activity and/or accident evidence for evidentiary purposes. The information may be directly transferred to an information center and/or the authorities through a transmission link, which is preferably a satellite up/link-down/link or saved directly onto the downloading device for transfer to the secure device. The remote downloading device may be activated automatically or upon a trigger signal and comprises an interface, an information capturing storage device, a video monitor display and preferably a transceiver. The interface communicates with an information storage device, downloads the information saved therein and transmits it to the capture storage device, transceiver or both. The received information is reproduced, integrated into an indexed database and transferred to the secure device as part of a secure, indexed database for non-tamperable permanent storage as evidence."

---

Plain-language overview of the independent claims

Claim 1 — System for producing an integrated database (apparatus).
A vehicle incident system with: (a) at least one video camera capturing video of the incident near the vehicle; (b) a recording device that captures those video signals as data; (c) an interface requiring an authorization code to reach that data — the data is inaccessible without the code, which is what preserves it as trustworthy evidence; (d) an information datalink for accessing the recorded data; (e) a transfer device coupled to the datalink that securely receives the data from the remote vehicle recording system; and (f) "means for generating an integrated, indexed database" of that data, coupled to the transfer device.
In short: camera → protected recorder → authorized download path → secure transfer device → indexed database.

Claim 18 — System (same as claim 1, plus permanent storage).
Adds limitation (g): a secure, tamper-proof storage facility in secure communication with the database-generating means, for permanently storing the integrated, indexed database. Practically, claim 1 is the data-collection-and-indexing chain; claim 18 is that chain plus the vault.

Claim 35 — Method for capturing an incident.
Method steps: activate camera(s); generate video of the incident; store the video on a large-capacity recording device as data; provide an authorization code after storing, the code permitting access to the stored video (again, stored video is inaccessible without the code, preserving it as evidence); access the stored data; transfer the data to a transfer device that securely receives it; and generate an integrated, indexed database from the data.

Claim 52 — Device for permanent, secure, tamper-proof storage.
A device comprising: (a) at least one interface for accessing data from a remote vehicle incident recording system; (b) an information datalink coupled to the interface for receiving that data; (c) a transfer device on the datalink that securely receives the data and indexes it for storage; and (d) a secure, tamper-proof storage facility separate from the transfer device but in secure communication with it, for permanently storing an indexed database of integrated data.
(Note: the granted claim text literally recites "a secure, tamer proof storage facility" — a typographical error in the printed patent — and claim 53 literally recites "information storage means far storing data." I am preserving these exactly as printed rather than correcting them.)

Claim 69 — Method for permanently storing data in an indexed database.
Steps: (a) activate a device having an interface for accessing data from a remote vehicle recording system; (b) receive data from that system; (c) transmit the data to a secure location separate from the device using a transceiver coupled to the device; (d) index the data to form a database; and (e) store the database at the secure location on a permanent, secure, tamperproof device, yielding a permanent, non-tamperable indexed database.

Dependent-claim themes across all five families: recording media type (video tape, hard disk, CD-ROM, solid-state — claims 2/19/36/54); overwrite prevention for extended periods (3/20/37/55/82); companion vehicle information — identification, audio, vehicle dynamic, vehicle control data (4–9, 21–26, 38–43, 56–61, 70–75); display means (6/23/40/58); download triggers responding to a predetermined event, transmitted instructions, or an electronic access code (10–13, 27–30, 44–47, 62–65, 83); encrypted download (14/31/48/66); direct satellite up-link/down-link (15/32/49/67/78); transmission triggers (16/33/50/68); and a long enumerated list of database indexes (17/34/51) — VIN, date, owner name, unit serial number, GPS location, street/address/city/state, vehicle make/model/year, insurer, policy number, driver's license/name, date of last access, last user/company, and type of incident or crash.

---

Litigation and administrative history (what actually exists)

• IPR2017-00245, Enforcement Video LLC d/b/a WatchGuard Video v. Evicam International, Inc., patent 6,950,013, petition filed November 11, 2016. Challenged claims: 1, 4, 8–12, 17–18, 27–28, 34–35, 45, 52, 58, 60–61. Grounds included obviousness over Joao (5,917,405) in view of Odle (5,491,511) and Freeman (5,579,239), and obviousness over Mackey (6,141,611). Google Patents records the case as filed and settled; a PTAB notice of refund (Paper 20, mailed June 25, 2018) confirms partial refund of post-institution fees, consistent with settlement.
• E.D. Tex. litigation: cases noted as 6:15-cv-01043 and 4:16-cv-00105 (Sherman Division, Judge Amos L. Mazzant, III). In Evicam Int'l, Inc. v. Enforcement Video, LLC, No. 4:16-cv-00105, the court denied WatchGuard's §101 summary-judgment motion on June 5, 2017, holding the '013 patent is directed to the abstract idea of collecting/organizing/controlling access to vehicle incident information (Alice step one) but that limitations such as download triggers with an access code supply an inventive concept (Alice step two).
• Jury verdict (July 14, 2017): unanimous verdict of no infringement and that the asserted claims were invalid; Agreed Amended Final Judgment entered (Dkt. 201-1, filed Aug. 11, 2017), covering claim 8 of the '013 patent (and claims 3, 8, 13, 19 of the '907 patent). Critically, paragraph 7 of that judgment states each party "waives any appeal from this judgment," and paragraph 6 waives post-verdict motions.
• CAFC 2026: Nothing found. No Federal Circuit docket, opinion, or 2026 appellate activity for 6,950,013 appears in my searches. That is consistent with the appeal waiver in the 2017 final judgment.

---

Points of uncertainty / drafting observations (flagged, not corrected)

1. Claim language differs between the pre-grant publication and the granted patent. The published application of claim 1 recites "generated from a secure vehicle incident capture system," whereas the granted claim 1 (and the PDF/Google Patents text) recites "generated from a remote vehicle incident recording system." The granted text is authoritative here. If you need the prosecution-history reason for the amendment, that would require the file wrapper.
2. Antecedent-basis defects in the granted claims. Claims 62–68 depend from claim 52 but refer to "said transceiver" and "said transmission link," terms that claim 52 does not introduce (claim 52 recites an "interface," a "datalink," a "transfer device," and a "storage facility"). This is a real defect in the printed claim set and is typically challenged in litigation.
3. Typographical errors preserved verbatim: "tamer proof" (claim 52), "far storing" (claim 53), "in response transmitted instructions" (claim 46), and the "device of claim 35" dependency in claim 51 (which should read "method"). These appear exactly in the granted text.
4. PTAB title discrepancy: one third-party IPR summary labels the patent "Device and Method for Permanently and Securely Storing Incident Information." That is not the patent's title; the official title of record is "Incident recording secure database." Treat the third-party label as a paraphrase, not ground truth.
5. Assignee history: the patent issued to individual inventors and was later assigned to Evicam International, Inc. (recorded 2010-06-25). The "current assignee" designation on Google Patents reflects that assignment; I could not independently verify any subsequent chain of title.
6. I did not have live access to the USPTO PatentCenter or CAFC docket systems in this session; findings above rest on the fetched patent text plus secondary sources (Google Patents, PTAB/docket aggregators, court opinions). For a filing-grade verification of 2026 CAFC dockets, the PACER/CAFC docket and USPTO PatentCenter should be checked directly.

I'll search for litigation involving US patent 6950013 specifically.

Let me verify the PTAB proceedings and confirm details.

Litigation Involving U.S. Patent No. 6,950,013

I found one district court case and one PTAB proceeding specifically involving U.S. Patent No. 6,950,013 ("the '013 patent"). Here is what the available records show. (Note: I was unable to complete a final round of verification searches, so I flag the confidence level on each item below.)

---

1. Evicam International, Inc. v. Enforcement Video, LLC d/b/a WatchGuard Video

Procedural and outcome detail:

• Filed 11/24/2015 in the Eastern District of Texas; venue was transferred to the Sherman Division on 2/10/2016 (Order granting the motion to change venue), where it was docketed as 4:16-cv-00105.
• The case survived an Alice/§ 101 patent-eligibility challenge — the court (in a summary-judgment opinion in 4:16-cv-00105) analyzed the '013 patent's Claim 1 as representative and addressed whether the claims were directed to the abstract idea of "collecting, organizing, and controlling access to vehicle incident information."
• Jury trial began July 10, 2017. On July 14, 2017, the jury returned a unanimous verdict finding no infringement of both the '907 and '013 patents and finding asserted claims of the '907 patent invalid. Specifically, per the Final Judgment (Dkt.), the jury found:
  • No infringement of Claims 3, 8, 13, and 19 of the '907 patent;
  • No infringement of Claim 8 of the '013 patent; and
  • Claims 3, 8, 13, and 19 of the '907 patent are invalid.
• Final Judgment entered July 17, 2017; WatchGuard was designated the prevailing party and awarded costs. An Agreed Amended Final Judgment was entered on/about August 11, 2017, terminating the litigation and waiving post-verdict motions and appeals. Evicam granted WatchGuard a covenant not to sue on the '907 and '013 patents in exchange for WatchGuard terminating its IPRs (see below).
• Evicam had sought more than $15 million in damages, reduced to ~$10.4 million at trial; the jury awarded a take-nothing verdict.

Confidence: High. Multiple independent sources (a court Final Judgment PDF, firm press releases, UniCourt docket summary, and Studicata case summary) corroborate the parties, case numbers, verdict, and disposition.

---

2. PTAB — IPR2017-00245 (Inter Partes Review of U.S. Patent No. 6,950,013)

• Type: Inter Partes Review, U.S. Patent Trial and Appeal Board
• Patent challenged: U.S. Patent No. 6,950,013
• Patent Owner: Evicam International, Inc.
• Status: Terminated by settlement (Google Patents lists this as "PTAB case IPR2017-00245 filed (Settlement)")
• The docket materials are indexed under "Inter Partes Review of U.S. Pat. 6950013."

Related PTAB proceeding (for context):

• IPR2017-00051 — Inter Partes Review of U.S. Patent No. 6,211,907. Petitioner: Enforcement Video, LLC d/b/a WatchGuard Video; Patent Owner: Evicam International, Inc. The parties filed a Joint Motion to Terminate on August 18, 2017, after settling both the '907 and '013 disputes; the Board had instituted but had not yet reached a final written decision.

Confidence: Medium-High. The existence, patent number ('013), settlement, and Evicam's role as patent owner are well-supported. I could not positively confirm the identity of the IPR2017-00245 petitioner from the retrieved results — the Google Patents "Petitioner" field appears to be the data-source attribution ("Unified Patents PTAB Data"), not necessarily the named petitioner. Given that WatchGuard filed the companion IPR2017-00051 on the '907 patent and the two matters settled together in August 2017, it is plausible WatchGuard was also the petitioner in IPR2017-00245, but I am not certain of this and would not assert it as fact.

---

Notes on scope / caveats

• I limited results strictly to U.S. Patent No. 6,950,013. I did not include cases asserting only the sibling patents ('907, or the parent 6,211,907 family members) except where they directly bear on the '013 litigation.
• The two Eastern District of Texas case numbers shown on Google Patents (6:15-cv-01043 and 4:16-cv-00105) are the same lawsuit — renumbered after transfer from the Tyler Division to the Sherman Division.
• Google Patents' "Family has litigation" flag for this patent reflects these two Texas filings and the IPR2017-00245 PTAB case.
• I did not find any CAFC appeal on the merits; the amended final judgment waived appeal rights. I also did not identify any separate later/follow-on suits asserting the '013 patent.

If you need the exact docket entry numbers (the Final Judgment was near Dkt. #194–203 in 4:16-cv-00105) or the specific IPR2017-00245 petitioner confirmed, those would require one more targeted pull from PACER and the PTAB docket — let me know and I can specify exactly what to retrieve.

I'll start by checking the canonical structured list against what web sources show, since the previous sections already flagged an IPR that the ODP block may not have indexed.

Now let me confirm the rehearing outcome, the termination date, and check for any additional petitions or appeals.

Let me verify there are no additional petitions (PGR/CBM/second IPR) and no CAFC appeal of this proceeding.

Source-of-record conflict (read first)

The structured "PTAB proceedings on file" block states the USPTO ODP API returns no AIA trial proceedings for US 6,950,013. That is a false negative. Web research definitively establishes one AIA trial on this patent — IPR2017-00245 — with a filed petition, an institution decision, a rehearing denial, and a termination decision, all on the public PTAB record. I am treating the ODP "no proceedings" result as a stale/limited ingest and using the retrieved primary documents instead, as your instructions permit ("flag any you find"). Everything below is sourced to PTAB papers, not to the ODP block.

I also confirmed there is no second IPR, no PGR, no CBM, and no ex parte reexamination on US 6,950,013 in any source I could reach. The ex parte reexam 90/015,984 and the Wilus/Samsung IPRs excluded in the earlier sections do not touch this patent.

---

Proceedings overview

One AIA trial proceeding exists on US 6,950,013 — IPR2017-00245 — and it was terminated by joint motion after partial institution, with zero claims canceled, zero claims sustained, and no Final Written Decision; the patent also expired (adjusted expiration 2019-01-13), so the bottom line for a defendant today is not "hardened patent" but "expired patent, no FWD, no estoppel, and a public institution decision that hands you a working § 103 combination against claims 52/58/60/61 while twice refusing to reach claims 1/18/35."

Breakdown: 0 active / 0 claims invalidated / 0 claims sustained / 1 settled / 1 institution partially denied (as to 11 claims).

---

IPR2017-00245 — Enforcement Video, LLC d/b/a WatchGuard Video v. Evicam International, Inc.

• Type: Inter Partes Review (35 U.S.C. §§ 311–319; pre-AIA § 103(a) grounds)

• Filed: 2016-11-11 (Petition, Paper 1). Confirmed by the National Law Review PTO Litigation Center Report dated 2016-11-14 (Tech Center 2600) and by the Board's own institution decision.

• Status (verbatim as listed by Google Patents): "PTAB case IPR2017-00245 filed (Settlement)." Plain-English gloss: instituted on four claims, then killed by joint motion before any Final Written Decision — a settlement termination under 35 U.S.C. § 317(a), not a merits loss.

• Judge panel: Michael W. Kim, Patrick M. Boucher, and Melissa A. Haapala, Administrative Patent Judges (Panel listed on the 2017-05-18 institution decision and the 2017-07-06 rehearing denial; the termination decision was signed by Boucher and Haapala).

• Petition grounds: Two § 103(a) obviousness grounds against claims 1, 4, 8–12, 17, 18, 27, 28, 34, 35, 45, 52, 58, 60, and 61:

  1. Joao (US 5,917,405) in view of Odle (US 5,491,511) and Freeman (US 5,579,239) — Joao as primary vehicle-security/video/access-code reference; Freeman for the "transfer device" (portable PC with temporary storage and video compression); Odle for the "means for generating an integrated, indexed database" (index file correlating video and digital data).
  2. Mackey (US 6,141,611) alone — on-board accident camera with hard-wired or wireless transfer to a central database server, authorization code, and time/date + vehicle-ID indexing.

  No § 112 grounds were asserted as standalone bases; § 112 ¶ 6 was raised only as claim-construction framing for the "means" limitations. The Petition's table of authorities cites § 102, but the grounds actually presented and decided were § 103(a).

• Institution decision: Partially instituted — entered 2017-05-18 (Paper 9, Trial Instituted Document). The Board instituted on claims 52, 58, 60, and 61 and declined to institute on claims 1, 4, 8–12, 17, 18, 27, 28, 34, 35, and 45. Reasoning, in substance: the Petition failed to show that either Joao or Mackey discloses the "the captured data being inaccessible without the authorization code" limitation of claims 1 and 18, or the parallel "the stored video signal being inaccessible without the use of the authorization code" limitation of claim 35. Claim 52 was designated the illustrative claim.

• Rehearing: Petitioner filed a Request for Rehearing on 2017-06-01 (Paper 11), arguing the Board misapplied the doctrine of claim differentiation (relying on dependent claims 13, 30, and 47) and that claims 1/18/35 must permit access methods other than the authorization code. The Board denied rehearing on 2017-07-06 (Paper 12), holding that failure to credit Petitioner's unpresented claim-differentiation argument was not an abuse of discretion and reiterating that neither Joao nor Mackey maps the inaccessibility limitations. (Notably, the panel observed that neither party had proposed a formal construction of the disputed "inaccessible" phrases.)

• Final Written Decision: None. No FWD ever issued. That is the single most important fact for a defendant — it means no claim of US 6,950,013 has ever been canceled or held unpatentable by the PTAB.

• Settlement / termination: The parties filed a Joint Motion to Terminate (Paper 16) supported by a covenant not to sue (Ex. 1018), filed under seal as business confidential under 37 C.F.R. § 42.74(c). The Board granted the joint motions to terminate on 2017-08-29 (termination decision covering both this case and IPR2017-00051), expressly stating: "Trial was instituted for these proceedings; however, both proceedings are in a preliminary stage. Under the circumstances, we determine that it is appropriate to terminate these proceedings with respect to all parties without rendering a final written decision." Terms of the covenant are confidential. A Notice of Refund (Paper 20, mailed 2018-06-25) confirms the Board returned $1,200 of post-institution fees to Petitioner — the clean fingerprint of a pre-FWD settlement. Counsel of record: Adam Sanderson / William Moon for WatchGuard; Jacob LaCombe / Jamil Alibhai (Munck Wilson Mandala) for Evicam.

• Appeal: None. No Federal Circuit appeal was taken from this proceeding (there was no FWD to appeal), and none is possible now. The parallel district-court case was closed under an Agreed Amended Final Judgment (Dkt. 201-1, 4:16-cv-00105-ALM, filed 2017-08-11) whose paragraph 7 states: "Each party waives any appeal from this judgment."

• Defensive value: Zero estoppel, but a free roadmap. Because no FWD issued, § 315(e)(2) estoppel never attached to WatchGuard or anyone else — no party is barred from re-running any ground. Conversely, the 2017-05-18 institution decision is public and tells you exactly where the Board found a reasonable likelihood of unpatentability (claims 52/58/60/61 over Joao+Odle+Freeman and Mackey) and exactly where it did not (claims 1/18/35, because the "inaccessible without the authorization code" limitation was read as requiring that no other access path exists). Any infringement theory today must reckon with a patent that is expired and was never adjudicated unpatentable.

---

Strategic summary

Claim-by-claim status. Nothing is canceled. Nothing is sustained. The PTAB docket for this patent contains no FWD and therefore no claim-level invalidity holding of any kind. Claims 52, 58, 60, and 61 are the only claims a panel ever agreed to try, and the trial evaporated at settlement. Claims 1, 18, and 35 were twice refused institution — once on 2017-05-18 and again on rehearing on 2017-07-06 — on a claim-construction basis, which is adverse to a would-be challenger, not to the patentee. The remaining claims — 2–3, 5–7, 9, 13–17, 19–26, 29–34, 36–45, 46–51, 53–57, 59, and 69–83 — were never challenged in any AIA trial, and claim 59 is notable as the one dependent of independent claim 52 that the Petitioner simply left alone. Separately, the district court never invalidated a '013 claim: the jury's invalidity finding and the Agreed Amended Final Judgment's "invalid" paragraph ran to claims 3, 8, 13, and 19 of US 6,211,907; for the '013 patent the judgment records only non-infringement of claim 8. (Flagging a discrepancy with the earlier "Patent summary" section, which summarised the verdict as "finding asserted claims invalid" across both patents — the judgment text as excerpted does not extend the invalidity holding to any '013 claim.) So the honest statement is: the '013 patent has never been invalidated anywhere, by anyone — it simply expired.

Estoppel landscape. This is a rare, clean defensive posture. Statutory IPR estoppel under § 315(e)(2) requires a final written decision, and none issued — the Board terminated under § 317(a) at a "preliminary stage." Therefore no ground, raised or reasonably raisable, is estopped as to any party. WatchGuard's protection comes from a contractual covenant not to sue with Evicam, not from estoppel or from a validity judgment; a third party defendant would face no estoppel at all. The practical corollary: the prior art assembled in 2016 — Joao (5,917,405), Odle (5,491,511), Freeman (5,579,239), Mackey (6,141,611) — is fully available, and the district-court campaign added Swanson (5,689,442) and Schofield (WO 94/19212) for the sibling '907 patent. Nothing about IPR2017-00245 forecloses reasserting any of it.

Pattern signals. The same petitioner, WatchGuard, filed two IPRs in the same week: IPR2017-00245 on the '013 patent and IPR2017-00051 on the parent '907 patent (US 6,211,907). Both were terminated together on 2017-08-29 under the same covenant not to sue, after the parties settled the co-pending E.D. Tex. litigation. That is a classic litigation-driven, single-front IPR strategy that settled out — not a defensive-aggregator campaign. There is no Unified Patents (or other aggregator) petition against this patent; the "Unified Patents PTAB Data" string Google Patents shows on the '013 page is a data-source attribution, not a party. The patent owner (Evicam) never appealed to the Federal Circuit — it won the § 101 fight below, won the non-institution fight at the PTAB, took a no-infringement jury verdict plus a covenant, and let the patents lapse. There is no evidence of aggressive PTAB-appeal behavior.

One bibliographic wrinkle worth recording: the institution decision identifies the related patent as "U.S. Patent No. 6,211,901" when describing IPR2017-00051. The correct number is US 6,211,907. This appears to be a typographical error in the Board's opinion; I am not correcting the record, only flagging it so it isn't mismatched against a real '901 patent.

---

Recommended next steps

If you are a defendant receiving a demand on US 6,950,013:

1. Lead with expiration. The patent is listed as Expired – Fee Related, with an adjusted expiration of 2019-01-13 and a stated term adjustment of 226 days. An expired patent cannot be infringed; any demand citing live claims is facially untenable. Note that expiration does not legally foreclose an IPR (the Board can and does institute on expired patents, applying Phillips), but there is no assertion to defend against.
2. Do not let anyone tell you the patent is "hardened." There is no FWD. You can quote the Board directly: "[B]oth proceedings are in a preliminary stage… we determine that it is appropriate to terminate these proceedings with respect to all parties without rendering a final written decision." — Termination Decision, 2017-08-29 (covering IPR2017-00051 and IPR2017-00245).
3. If you nevertheless need an invalidity position, start from the public institution decision, which found a reasonable likelihood that claims 52, 58, 60, and 61 are obvious over Joao + Odle + Freeman and over Mackey. Link: Institution Decision, Paper 9 (2017-05-18) (mirror of PTAB E2E).
4. Watch the claim-construction trap on claims 1/18/35. Two Board panels read "the captured data being inaccessible without the authorization code" as requiring that the data be reachable only through the code. That construction helped the patentee and is why those claims went untried. Any attack on claims 1/18/35 must either find art disclosing true exclusivity of access, or persuade the tribunal to reject that construction. See Decision Denying Request for Rehearing, Paper 12 (2017-07-06).
5. Reuse the district court's agreed constructions — they resolve the patent's printed typos in your favor and fix several means-plus-function structures. In Evicam Int'l, Inc. v. Enforcement Video, LLC, the parties agreed: "tamer [sic] proof" (claim 52) = "tamper proof"; "far [sic]" (claim 53) = "for"; "display means for displaying said data" (claims 6, 23, 58) = structure "visual display monitor 48 and equivalents"; "information storage means" (claim 53) = "video tape drive, hard disk drive, CD ROM drive, solid state repository, flash memory, and equivalents"; "download"/"downloading" = "transferring from one device to another over a wired or wireless network." This dovetails with the typographical defects flagged in the earlier "Points of uncertainty" section and adds the Board's own footnote: "We note that claim 52 recites 'secure, tamer proof.' We treat this as a typographical error."

No active proceedings, so there are no trial-stage milestones to track. There is no institution deadline, no oral hearing, and no statutory 1-year FWD date running on this patent. The statutory § 316(a)(11) clock never started because no trial is pending.

Caveat on this section: I did not have live PTAB E2E or PACER access in this session. All proceeding facts above are drawn from the PTAB papers as mirrored on Docket Alarm and the Board's own opinion text, plus the National Law Review petition-filing report. The ODP block in this prompt returns zero proceedings for this patent, which conflicts with the primary documents; I have flagged rather than reconciled that conflict. For a filing-grade verification, pull IPR2017-00245 directly from PTAB E2E ("Trials@uspto.gov") and confirm the termination date and paper numbers against the docket of record.

I'll research the assignment chain for US 6,950,013 before producing the record.

Let me search for the specific assignment record details.

I'll research the specific prior-art references cited on the face of US 6,950,013, and cross-check against the IPR art identified in the earlier sections.

Let me pull the front-page "References Cited" list from FreePatentsOnline and the USPTO report page.

Let me retrieve the front-page references-cited list and the abstract-detail pages for the candidate references.

Source-integrity note (read first)

The authoritative text I was given for US 6,950,013 — the fetched Google Patents document — does not contain the "Patent Citations" / "References Cited" (front-page citation) table. The fetched text jumps from the specification and claims straight into a forward-citation list ("Cited By (78)"), of which only two entries (US 2003/0200123 A1, Burge; US 2004/0111301 A1, Wahlbin) were visible before truncation. I was also unable to complete the verification searches I attempted against FreePatentsOnline/Justia for the exact front-page list; the tool session hit its step limit.

Consequence: I cannot hand you a verbatim, complete reproduction of the 6,950,013 front page's "U.S. Patent Documents" list. What follows is built from (a) the IPR2017-00245 petition — which I did retrieve, including its exhibit list and grounds — and (b) secondary citation databases (Justia, FPO) that co-list the same references. I flag confidence on each item. Any reference cited on the '013 front page outside the four below is not accounted for here, and would need the actual front page or the file wrapper to enumerate.

---

1. The core prior art of record (IPR2017-00245 exhibits)

The petition's exhibit list (retrieved from the Docket Alarm copy of Paper 1, available via https://www.docketalarm.com/cases/PTAB/IPR2017-00245/.../Petition-1-Petition.pdf) is the single most reliable indexing of the art the challenger treated as material:

¹ Issue dates are drawn from the Justia citation listings that co-list all four references alongside 6,950,013 (e.g. https://patents.justia.com/patent/9756279 and .../10250433), and are consistent across sources. The Mackey title is corroborated by a FreePatentsOnline citation block (https://www.freepatentsonline.com/9230442.html). I could not independently verify the full titles/abstracts of Joao, Odle, or Freeman in this session — treat those descriptions as functional, not verbatim.

Grounds as pleaded (this is important to your § 102 question):

• Ground 1 — claims 1, 4, 8–12, 17–18, 27–28, 34–35, 45, 52, 58, 60–61 obvious over Joao in view of Odle and Freeman.
• Ground 2 — the same claim set obvious over Mackey.

Note what this means: *no reference was asserted as a standalone § 102 anticipation. Both grounds are § 103 obviousness. So the honest answer to "which claims does each reference anticipate under § 102" is: none was asserted as an anticipatory reference; each instead discloses limitations mapping onto the claim set below. I give that mapping, and separately the § 102 category each reference falls into.

---

2. § 102 category for each reference (pre-AIA analysis)

The '013 application was filed May 31, 2002, so pre-AIA §§ 102/103 govern. The controlling question is which priority date the claims actually get — and the '013 is the third link in a CIP chain (09/088,267 → 09/327,828 → 09/758,645 → 10/158,837), so a § 112 written-description analysis could push some claims to the Jan. 10, 2001 date (or later) rather than the Jun. 1, 1998 date. That matters:

Filing dates for Joao and Mackey are the load-bearing fact for the § 102(e) fallback, and I could not verify them in this session. My recollection is that both were filed in the mid/late-1990s (before the '013's effective date under any reading), which would make both available as § 102(e) art — but do not rely on that without pulling the front pages of 5,917,405 and 6,141,611. This is precisely the § 102 date-stacking the petitioner would have had to brief, and it is the weakest link in my reconstruction.

---

3. Reference-by-reference: what each discloses and which claims it maps to

US 5,491,511 — Odle (issued Feb. 13, 1996). A vehicular/event video recording arrangement. Used as a secondary reference in Ground 1, paired with Joao. Maps principally to claim 1(a)–(b) ("at least one video camera for generating video signals of the incident proximate the vehicle"; "a recording device for capturing said video signals as data") and their counterparts — 18(a)–(b), 35(a)–(c), 52 (video data), and the media-type dependents 2/19/36/54 (video tape drive, hard disk, CD-ROM, solid-state). Confidence in this mapping: medium — it follows from Odle's role as the video-capture leg of the combination, not from a verified reading of Odle.

US 5,579,239 — Freeman et al. (issued Nov. 26, 1996). The third leg of Ground 1. In the petition's architecture, Freeman supplies the capture/transfer or record-handling teaching that Odle and Joao lack. Maps to the data-handling limitations: claim 1(d) "information datalink for accessing data captured by said recording device", 1(e) "transfer device… adapted to securely receive data", and the trigger/encryption dependents 10–14/27–31/44–48. Confidence: medium-low on the specific mapping; the exhibit role is certain, the limitation-level allocation is inferred.

US 5,917,405 — Joao (issued Jun. 29, 1999). Primary reference, Ground 1. Joao is a vehicle security/tracking-type patent (wireless reporting of a vehicle condition to a remote station). It is the natural vehicle for the limitations that make the '013 more than a camera-and-recorder: the remote character of the recording system, the information datalink, the "transfer device… adapted to securely receive data from said remote vehicle incident recording system" (claim 1(e)), the download trigger family (claims 10–13 — predetermined event, transmitted instructions, electronic access code), the encrypted-download dependents (14/31/48/66), and the satellite up-link/down-link dependents (15/32/49/67/78). If anything in the record ever rises to § 102 anticipation of claims 1/18/35/52, Joao is the only plausible candidate — but the petitioner did not so assert it, which tells you the disclosure gaps (indexed database; tamper-proof permanent repository) were real.

US 6,141,611 — Mackey et al., "Mobile vehicle accident data system" (issued Oct. 31, 2000). Sole reference for Ground 2. Because it was run alone, it is the closest thing in the record to a single-reference attack, and it is conceptually aimed at the accident-data-recording core: claim 1(a)–(b) (camera + recorder), the companion-data dependents 4–9/21–26/38–43/56–61/70–75 (vehicle identification, audio, vehicle dynamic, vehicle control information), the display dependents (6/23/40/58), and the overwrite-prevention dependents (3/20/37/55/82). Confidence: medium-high on Mackey's subject-matter fit (the title alone supports the accident-data mapping); medium on limitation allocation.

Claims never placed in issue by either ground: independent claim 69 (transmit-to-secure-location + index + store on permanent tamper-proof device) and its dependents 70–83, plus claims 2–3, 5–7, 13–16, 19–26, 29–33, 36–44, 46–51, 53–57, 59, 62–68. If you are assessing validity exposure, claim 69's family is the least-tested portion of the patent — no cited art in this record was mapped against it.

---

4. Related-family art and forward citations — not § 102 prior art, but you should know why

• The applicant's own earlier family members — US 6,211,907 (Scaman et al., issued Apr. 3, 2001), the published US 2001/0005217 A1 (from 09/758,645), and the provisional-rooted 09/088,267 — are all by the same inventive entity (Scaman and Hamilton). Under pre-AIA §§ 102(a)/(e), a reference must be "by another"; same-inventor-entity applications are therefore not § 102 prior art against the '013. Their real exposure is obviousness-type double patenting (and, for the CIP chain, § 112 priority), which is why the petitioner pulled the prosecution histories of 10/147,779 and 10/662,182 as Exhibits 1012 and 1015.
• The "Cited By (78)" list on Google Patents is the reverse direction — later patents citing the '013 — and is not prior art. Do not use it for § 102.

---

5. Caveats you should carry forward

1. The front-page citation list is unverified and likely incomplete. A 2005-era vehicle-recorder patent typically carries 10–40 examiner-cited U.S. references plus possible foreign/other documents. I have accounted for the four references that the litigation record shows were material, not for everything the examiner cited.
2. No § 102 anticipation was pleaded. If your question contemplates an invalidity contention, the correct framing on this record is § 103 over Joao+Odle+Freeman, or § 103 over Mackey — and that IPR settled (consistent with the PTAB refund noted for Paper 20, June 25, 2018), so no PTAB institution decision or final written decision on the merits exists to cite for claim-level findings.
3. This is separate from the district-court outcome already reported. The E.D. Tex. jury found no infringement and (as to the '907 claims) invalidity, and the Agreed Amended Final Judgment waived appeal — so there is no merits appellate ruling to anchor a § 102 analysis either.
4. Two data points above are my reconstruction, not verified quotes: the filing dates of Joao and Mackey (§ 102(e) fallback), and the limitation-level allocations in Section 3. To convert this into a filing-grade § 102 chart, retrieve (i) the '013 front page, (ii) the front pages/file wrappers of 5,917,405 and 6,141,611 for their § 102(e) dates, and (iii) IPR2017-00245 Paper 1's claim charts, which allocate each reference to specific claim elements with pinpoint cites.

I'll research the prior-art references identified in the IPR petition and related vehicle-recording art before building the §103 analysis.

Now let me pull the petition's claim-mapping detail and the key secondary references.

Obviousness Analysis Under 35 U.S.C. § 103 — U.S. Patent No. 6,950,013

Building on the previously generated Bibliographic, Claims, Litigation, and Assignment sections. Patent-level facts (claim text, CIP chain, dates) are taken from the authoritative full text at https://patents.google.com/patent/[US6950013](/patent/US6950013)/en and are not repeated here.

---

0. Two updates and one correction to the earlier sections

0.1 Petitioner identity — now confirmed. The earlier Litigation Summary flagged that the IPR2017-00245 petitioner could not be positively identified. Both the docket index and the AI-summarized petition confirm it:

"IPR2017-00245 … Petitioner(s): Enforcement Video, LLC d/b/a WatchGuard Video; Patent Owner(s): Evicam International, Inc.; Challenged Claims: 1, 4, 8-12, 17-18, 27-28, 34-35, 45, 52, 58, and 60-61."
— https://ai-lab.exparte.com/case/[ptab](/ptab)/IPR2017-00245/doc/summary/1

The docketalarm exhibit likewise carries the caption "IPR2017-00245 Petitioner: Enforcement Video LLC; Patent Owner: Evicam International, Inc."
(https://www.docketalarm.com/cases/PTAB/IPR2017-00245/Inter_Partes_Review_of_U.S._Pat._6950013/08-18-2017-Petitioner/Exhibit-1020-22-AGREED_AMENDED_FINAL_JUDGMENT/)

0.2 CONTRADICTION FLAGGED — what the 2017 jury actually invalidated. The earlier "Patent summary" section states the jury returned a verdict "of no infringement and that the asserted claims were invalid," which reads as covering the '013. The Agreed Amended Final Judgment does not support that reading:

"1. Defendant … does not infringe the following asserted claims: Claims 3, 8, 13, and 19 of U.S. Patent No. 6,211,907; and Claim 8 of U.S. Patent No. 6,950,013.
2. The following asserted claims are invalid: … 6,211,907."

The invalidity paragraph resolves to the '907 patent. For the '013, only non-infringement of claim 8 was adjudicated. There is accordingly no merits §103 holding on the '013 anywhere in the record — the IPR settled before any final written decision. This matters: nothing in the earlier sections should be cited as an adjudicated §103 invalidity of the '013.

0.3 Confidence caveat. The ai-lab.exparte.com pages are AI-generated case summaries. Where I rely on them for the substance of the petition's arguments I mark it as [third-party summary — verify against the paper]. The docketalarm petition table of contents (Ground 1 = Joao in view of Odle and Freeman; Ground 2 = Mackey) is corroborated by the petition PDF docket entry and is treated as reliable for the grounds themselves:
https://www.docketalarm.com/cases/PTAB/IPR2017-00245/Inter_Partes_Review_of_U.S._Pat._6950013/docs/11-11-2016-Petitioner/Petition-1-Petition.pdf

---

1. Governing law and the gate that decides half the analysis

1.1 Law

The '013 carries a 1998 priority date, so pre-AIA §103(a) applies. The framework is Graham v. John Deere, the four Graham factors, and KSR Int'l Co. v. Teleflex, Inc., 550 U.S. 398 (2007) (motivation may be found in design incentives, market forces, "common sense," and the finite number of predictable solutions). A combination of references is proper where each reference is reasonably pertinent to the problem, and the test is what the combined teachings fairly suggest — not what each reference teaches in isolation. In re Keller, 642 F.2d 413 (CCPA 1981).

A hypothetical POSITA here: a B.S. in EE/CS (or equivalent) with ~2–4 years' experience in on-board vehicle electronics, video surveillance/evidence systems, wireless telematics, and relational databases — i.e., someone conversant with event data recorders, compression, encryption, and indexed archives.

1.2 The gating issue: effective filing date, and why it determines whether Mackey exists as prior art

The IPR ran two grounds, and the second was Mackey alone. That is only possible if the challenged claims are not entitled to the June 1, 1998 date. The date matrix:

Dates from the reference front pages: Joao (https://www.docketalarm.com/cases/PTAB/IPR2016-00129/.../Ex_1107___US_5,917,405_Joao.pdf); Odle (https://patents.google.com/patent/KR100905504B1/en); Freeman (https://www.docketalarm.com/cases/PTAB/IPR2017-00245/.../Exhibit-1004-4-US_Patent_No_5,579,239_to_Freeman_et_al.pdf); Mackey (https://patentimages.storage.googleapis.com/40/45/fe/faeeae4748aaee/US6141611.pdf).

Consequence:

• Ground 1 (Joao + Odle + Freeman) is date-proof. All three issued or were filed well before June 1, 1998. This ground survives even on the most patentee-favorable priority ruling.
• Ground 2 (Mackey) lives or dies on the priority ruling. Mackey was filed five months after the '013's earliest priority date. For Mackey to be prior art, the petitioner must have shown that the challenged claims lack §112(a) written-description support in the June 1, 1998 application (09/088,267). The natural target is the new matter added by the two CIPs — the remote transfer device (2001 CIP) and the integrated, indexed database / secure tamper-proof repository (the '013 itself). Claim 1(f) ("means for generating an integrated, indexed database") and claim 18(g) ("secure, tamper proof storage facility") map most directly onto subject matter described only in the later CIPs. If those limitations are not supported by the 1998 disclosure, the effective date for those claims slides to 1/10/2001 or 5/31/2002, and Mackey becomes §102(e) — or, at the 2002 date, §102(b) statutory-bar — art.

Flagged as an assumption: I could not verify the priority/substantive-support analysis from the record available in this session. It is the single most consequential fact in the whole §103 picture and must be confirmed from the file wrapper (priority claim papers, the 09/088,267 specification as filed, and the IPR petition's priority section).

---

2. Ground 1 — Joao (US 5,917,405) in view of Odle (US 5,491,511) and Freeman (US 5,579,239)

2.1 What the references are

Sources: Joao front page (above); Odle title/abstract (https://patentimages.storage.googleapis.com/... and https://uspto.report/patent/grant/[5491511](/patent/5491511)); Freeman front page and abstract ("The playback unit stores and automatically catalogs transmitted data files" — https://www.docketalarm.com/cases/PTAB/IPR2017-00245/.../Exhibit-1004-4-US_Patent_No_5,579,239_to_Freeman_et_al.pdf).

2.2 Mapping to independent claim 1

[Third-party summary of the petition's mapping, verify] "Petitioner asserted that Freeman teaches the claimed 'transfer device' by disclosing a portable personal computer with means for temporary data storage and video compression. Further, Petitioner contended that Odle teaches the claimed 'means for generating an integrated, indexed database' by disclosing a system that stores digital records of transactions in a predefined database format and uses an index file to correlate video and digital data." — https://ai-lab.exparte.com/case/ptab/IPR2017-00245/doc/summary/1

2.3 Motivation to combine (Ground 1)

Applying the KSR rationales:

1. Joao + Freeman — "use of a known technique to improve a similar device in the same way" plus "market forces/design incentive." The petition's stated rationale is that Joao itself aims at smaller size and greater portability, and Freeman's portable computer is more compact than Joao's fixed system components; and Freeman's compression would predictably reduce the video transmission time on Joao's low-bandwidth downlink. [third-party summary] This is a strong KSR rationale (A/C/F) because the substitution is mechanical and the result (smaller, faster, cheaper to transmit) is predictable.
2. Joao + Odle — "organizing disparate records into a searchable index is a commonsense improvement." This is the weakest of the stated rationales. It is exactly the kind of conclusory "commonsense" assertion the Federal Circuit has repeatedly rejected when unsupported by evidence or reasoned explanation. Arendi S.A.R.L. v. Apple Inc., 832 F.3d 1355 (Fed. Cir. 2016); K/S HIMPP v. Hear-Wear Techs., LLC, 751 F.3d 1362 (Fed. Cir. 2014). A well-built petition should supplement "commonsense" with: (i) Odle's own stated purpose (auditing and correlating video with transaction data — the same evidence-integrity problem), and (ii) the ordinary skill of a POSITA in database design. The better-founded motivation is that both Joao and the '013 confront the same problem — making recorded surveillance/incident data retrievable and trustworthy as proof — and Odle solves precisely that problem with an index file and audit trail. That is a "reasonably pertinent art" argument, not a bare "commonsense" argument.
3. No change in principle of operation. Adding Freeman's portable download unit and Odle's indexing layer does not alter how Joao's vehicle security/monitoring system works; it adds a peripheral data path and a downstream archive. The combination is a mere aggregation/improvement, not a new mode of operation.

2.4 Ground 1 as applied to claims 18, 35, 52

• Claim 18 (adds (g) secure, tamper-proof storage facility in secure communication with the generating means). Odle's audit system is, by design, a tamper-resistant audit repository (its governing concept is an audit of the captured multimedia); Joao supplies a central station/processor remote from the vehicle. Mapping (g) onto "Odle's audit store, located at Joao's central facility" is the natural reading. Note the '013 specification's own description of the repository — "The data is cataloged, tagged, encrypted, and compressed … Transfer is accomplished by secure physical transport for direct data download or by highly secure, tamperproof electronic interface through super firewalls" — is itself a generic description of known archiving practice, which weakens any argument that the vault limitation is inventive.
• Claim 35 (method). Same elements in method form. One wrinkle: the granted claim 35 recites "providing an authorization code following storing of said data." Because both Joao's and Mackey's access schemes are code-based, this ordering is not a distinguishing limitation — a POSITA would set the access control at any convenient point, and the specification gives no criticality to the sequence.
• Claim 52 (device; no authorization-code element). Notably broader than claim 1 — it drops the access-code requirement entirely. Its elements are: (a) interface for accessing data from a remote vehicle incident recording system; (b) information datalink; (c) a transfer device that "securely receive[s] data … and index[es] said data for storage"; and (d) a secure, tamper-proof storage facility separate from the transfer device. Under Ground 1, (b)+(c) come from Freeman (portable unit) as modified by Odle (the indexing function), and (d) comes from Odle's audit repository located at a separate facility. [Note the literal typo "tamer proof," preserved as printed.] Because claim 52 contains no access-code limitation and its "securely receive" is purely functional, it is the most vulnerable independent claim.

---

3. Ground 2 — Mackey (US 6,141,611) as a single reference

Mackey is by far the closest art to the '013, and the reason is visible in its abstract:

"one or more video cameras mounted on the vehicle … Camera images … are stored on-board the vehicle, preferably, digitally recorded in a compressed format … data (e.g. one or more operating parameters such as speed, GPS data, engine, and/or brake operating parameters) from the vehicle's on-board embedded computers … An accident detector … generate[s] a trigger signal … the data stored on-board the vehicle is automatically transmitted over a wireless link … to a central data base. Data in the central data base is connected by a digital data network such as the Internet or a secured intranet and the data can be accessed via a computer terminal of an authorized party, such as an insurance adjuster …"
— US 6,141,611 abstract, https://patentimages.storage.googleapis.com/40/45/fe/faeeae4748aaee/US6141611.pdf

3.1 Element mapping for claim 1

[Third-party summary of the petition, verify] "Mackey describes a vehicular incident data system comprising an on-board mobile accident camera that captures and stores video data. This data is transferred, either via a hard-wired bus to a local personal computer or wirelessly to a central database server, which constitutes the claimed remote system and integrated database. Petitioner argued Mackey teaches a 'transfer device' in the form of either a portable personal computer or a remote terminal… Security is achieved through data encryption and the use of a 'proper authorization code'… Mackey's system indexes the data by applying a time/date stamp and a vehicle identification code to each record…"
— https://ai-lab.exparte.com/case/ptab/IPR2017-00245/doc/summary/1

3.2 Claims 18, 35, 52 under Mackey

• Claim 18(g) — secure, tamper-proof storage facility. Mackey's memory lock (step 56) plus encryption (36) is the tamper-proofing; the central database 19/server 20 is the permanent repository in secure communication with the on-board system. Mackey states expressly that the "impact generated remote storage of photographic data will enable the system user to use the data as evidence" — the same evidentiary purpose recited in the '013 specification.
• Claim 35 (method) — near-verbatim. Mackey's FIG. 3 flow is a step-for-step parallel to claim 35: generate video (31) → couple/store (33, 35) → detect event/trigger (37) → transmit (44, 46) → store data in a network-accessible data store (48) with authentication. The only arguable gap is the "large capacity recording device" recitation; Mackey's one-minute rolling buffer is not "large capacity," which is a genuine (if narrow) point for the patentee on claim 35.
• Claim 52 (device with separate secure tamper-proof facility). Interface (bus 23 / transceiver 26), datalink (16/18), transfer device indexing the data (PC 21 / server 20 with time-stamp + vehicle ID), and a storage facility separate from the transfer device (database 19) — all present.

3.3 The single seam in Ground 2

Claim 1(c) requires that the captured data be inaccessible without the authorization code. Mackey's authorization code, on its face, gates access to the central database (terminal 25), not to the on-board memory 28 — the on-board memory is reachable through the hard-wired PC interface. The petitioner's fix was to argue that "to the extent Mackey did not explicitly require an authorization code for the local personal computer, it would have been obvious for a POSITA to do so." [third-party summary] That is a permissible KSR argument (adding a known access-control technique to a known download path, where Mackey already locks the memory and encrypts the data), but it is the one place where Ground 2 requires something beyond Mackey's four corners, and a patentee would attack it as hindsight.

Also note: Mackey arguably anticipates several claims under §102(b) if the effective date is May 31, 2002. The task here is §103, but a challenger should plead §102 in the alternative — a single-reference §102 case is far cleaner than a §103 case resting on a "would have been obvious to add a code" rationale.

---

4. Dependent claims — conventional add-ons

The dependent claims divide into a small number of themes; each theme is either expressly disclosed by one of the four references or is an obvious design choice. A representative chart:

4.1 The index-list claims (17, 34, 51)

These recite indexing by "Vehicle Identification Number, Date of Accident/incident, Owner's Name, Unit Serial Number, GPS location, Street names, Address of Incident, City … State …, Vehicle Manufacturer, Model, Year, Insurer, Policy number, Driver's License Number, Driver Name, Date of Last Access, Name of Last User, Company of last user."

Two points:

1. Most of the list is administrative/descriptive metadata, not a functional relationship. A POSITA categorizing vehicle incident records would select exactly these fields; a database schema keyed on VIN, date, and policy number is routine. Odle's index-file teaching supplies the mechanism.
2. The access-tracking entries are the strongest mapping to Odle. "Date of last access, Name of last user, Company of last user" is precisely the audit-trail function of Odle's audit system — and the '013 specification itself concedes the point: "access to the data will also be recorded and indexed to assure authorized access and retrieval." That is a statement of intended result, not an inventive step.

Note the challenger's strategy gap: claims 51 and 69 were not challenged in IPR2017-00245. Claim 69 (the "permanently storing … indexed database" method) is the claim that most closely tracks Mackey's central-database architecture, and it was left on the table.

---

5. Where the obviousness case is strong, and where it is genuinely contestable

5.1 Strong

• The '013 claims known parts arranged in a known way. Camera (Joao/Mackey), recorder (Joao/Mackey), access code (Joao/Mackey), wireless datalink (Joao/Freeman/Mackey), portable transfer device (Freeman/Mackey), central indexed database (Odle/Mackey), tamper-proof archive (Odle/Mackey). Under KSR, "if a technique has been used to improve one device, and a person of ordinary skill in the art would recognize that it would improve similar devices in the same way, using the technique is obvious."
• Mackey is a near-complete single-reference case, including indexing children by "time/date stamp and vehicle identification code" and the express evidentiary rationale ("will enable the system user to use the data as evidence").
• Dependent claims add nothing but predictable variations.
• No objective indicia of nonobviousness appear anywhere in the record I could retrieve — no unexpected results, no industry praise, no licensing-nexus evidence. (Absence is not itself evidence of obviousness, but it removes the patentee's principal rebuttal.)

5.2 Contestable — priority (Ground 2's existence)

If the patentee establishes June 1, 1998 entitlement for the challenged claims, Mackey ceases to be prior art entirely and Ground 2 collapses. This is the highest-leverage defense and should be resolved first.

5.3 Contestable — claim 1(c) / claim 35(d) access-control-to-evidence

The claims do not merely recite "an access code"; they require that the recorded data itself be inaccessible without the code, thereby securely maintaining the captured data as evidence. Joao's code actuates vehicle systems (a control code); Mackey's code gates the central database terminal, not the on-board memory. A patentee will argue that neither reference — nor their combination — teaches code-gating of the recorded data at the source, which the '013 identifies as the mechanism that keeps the evidence un-impeachable in court. A challenger needs express record support tying the code to data retrieval (Mackey's "memory lock" plus the database authorization code is the best available bridge).

5.4 Contestable — the Odle motivation ("commonsense" indexing)

As noted in §2.3, a bare "organize the data into an indexed database is commonsense" rationale is vulnerable under Arendi and K/S HIMPP, and the Board has recently been strict about unexplained "commonsense" motivations. The better formulation is the reasonably pertinent art / same problem framing.

5.5 Contestable — means-plus-function construction

Claim 1(f) ("means for generating an integrated, indexed database") and claims 4/21/38 ("means for generating vehicle information") use "means for," which carries a strong presumption of §112(f) construction under Williamson v. Citrix, 792 F.3d 1339 (Fed. Cir. 2015) (en banc). If §112(f) applies:

• The limitation is limited to the structure disclosed in the specification for performing that function plus equivalents — here, the off-site/secure-location processor described in the '013 at the passage: "the data is cataloged, tagged, encrypted, and compressed … additional index[ ] information is layered on the files," and "database entries are able of instantaneous access by means of indexing which allows authorities to retrieve information without search of the entire file."
• Odle's indexed database system is a good structural match; but
• A parallel attack exists: the specification may be argued to disclose no algorithm sufficient to correspond to the claimed function, raising a §112(b) indefiniteness/§112(f) insufficiency ground. This is a distinct invalidity theory, not §103, but it is the kind of defect a challenger typically pairs with the §103 case.

5.6 Contestable — analogous art as to Odle

Odle's "multimedia capture and audit system for a video surveillance network" arises in an audit/surveillance context rather than vehicle incident recording. A patentee could dispute field-of-endeavor. The answer is under In re Clay/In re Bigio: Odle is reasonably pertinent because it addresses the identical problem — capturing video plus correlated data in a form that can be searched, authenticated, and audited — which is precisely the problem the '013 states it solves.

5.7 A note on the "verification" limitation

The '013 places substantial weight on verification ("the information can be verified by use of stored information onboard vehicle 11"), and claims 69(e)/18(g) require the archive to be "non-tamperable." A patentee will press the chain-of-custody framing. The counter is contained in the patent's own words: "Tracking of access and software to detect time and date of any change is used to assure integrity of the originally recorded data" — a description of an ordinary audit log, which Odle teaches.

---

6. Additional §103 combinations a challenger should develop

Beyond the two IPR grounds, the following combinations are both better-grounded and better-supported:

1. Mackey + Odle. Mackey supplies camera → on-board compressed storage → trigger → encrypted wireless upload → central database; Odle supplies the index-file architecture and the audit trail (which maps directly onto the '013's "Date of last access / Name of last user / Company of last user" index entries). Motivation: reduce the search cost of the central archive, which Mackey itself requires ("accessible by terminals"). This combination is stronger than Ground 1's Joao + Odle "commonsense" rationale because it does not depend on a bare common-sense assertion.
2. Mackey + Joao. Joao supplies remote-command activation and code-based authorization to the vehicle-side apparatus — plugging the exact gap identified in §5.3 (access control at the source), and supplying the "download trigger … transmitted instructions" and "electronic access code" dependent claims (12/29/46/64/83).
3. Mackey + Freeman. Freeman supplies the portable transfer device with temporary storage and compression, plus "playback unit stores and automatically catalogs transmitted data files" — the offline download/transfer path recited in claims 52–55.
4. Substitute/additional vehicle-camera references. If Joao's vehicle-camera disclosure proves thin, substitute or add Peterson, US 4,789,904 ("Vehicle mounted surveillance and videotaping system") or Michetti, US 4,843,463 ("Traffic accident data recorder") — both cited on the face of Mackey (https://www.everypatent.com/comp/pat6141611.html) and both pre-1998.
5. NPL / state of the art. SAE and IEEE literature on event data recorders, and contemporaneous commercial "black box" vehicle camera systems, are admissible to establish what a POSITA knew and to support the motivation element — particularly for the "prevent overwrite," "encrypted transmission," and "central archive" limitations.
6. Date-sensitive references to avoid (or to hold in reserve): Rayner US 6,389,340/6,405,112/6,449,540; Lambert US 6,421,080 ("pre-event recording"); Plante and other 2000s event-recorder filings. These post-date the 1998 priority date and only become available if the effective date slips to 2001/2002 — in which case they are powerful (e.g., Lambert's pre-event recording directly addresses claims 3/20/37/55).

---

7. Bottom line

1. Ground 1 (Joao + Odle + Freeman) is the date-proof case. It establishes a prima facie §103 case for claims 1, 18, 35, and 52 and, through them, for the challenged dependents (4, 8–12, 17, 27–28, 34, 45, 58, 60–61), all of which add only predictable variations. Its weakness is the "commonsense" motivation for bolting Odle's indexing onto Joao — a rationale that should be re-pled in "reasonably pertinent art / same problem" terms.
2. Ground 2 (Mackey alone) is the strongest case on the merits, but it is conditional. It survives only if the challenged claims are denied the June 1, 1998 priority date, because Mackey was filed December 1, 1998 — five months after the '013's earliest priority date — and did not issue until October 31, 2000. On the 2002 filing date, Mackey is §102(b) art and cannot be sworn behind at all. The same priority determination should be run in the alternative as a §102 attack, which is cleaner than the §103 "it would have been obvious to add an authorization code" bridge needed to close claim 1(c).
3. No adjudicated §103 holding exists for the '013. The 2017 jury verdict invalidated only the '907 claims; the '013 was adjudicated solely on non-infringement (claim 8), and IPR2017-00245 terminated by settlement. There is therefore no estoppel and no PTAB or Federal Circuit merits ruling on obviousness — the §103 analysis must stand on its own.
4. Also pursue §112. Claim 52's dependents 62–68 and claim 53's typographical defects ("tamer proof," "far storing"), plus the §112(f) exposure of the "means for generating an integrated, indexed database" limitation, are separate and largely independent invalidity grounds that a validity challenge should pair with the §103 case.

What to retrieve to firm this up

• IPR2017-00245 Paper 1 (the full petition claim charts, particularly the Joao camera/recording mapping and the priority argument that unlocks Mackey) — https://www.docketalarm.com/cases/PTAB/IPR2017-00245/Inter_Partes_Review_of_U.S._Pat._6950013/docs/11-11-2016-Petitioner/Petition-1-Petition.pdf
• Papers 11–20 of IPR2017-00245, to determine whether the Board instituted (which would give a preliminary, non-binding Board view of the §103 grounds) before the August 2017 settlement. The June 25, 2018 notice of refund of post-institution fees is consistent with early termination, but I could not confirm from the retrieved materials whether institution occurred — treat that as unresolved.
• The file wrapper of 10/158,837, together with the 09/088,267 specification as filed, to run the written-description/priority analysis that decides whether Mackey is prior art.
• Exhibits 1004 and 1009 (Freeman and Joao), to verify the specific column/line citations for the camera, recording, and access-code elements — the three mappings I could not independently verify in this session.