Invalidity dossier
US 9513191
Method for monitoring a subsystem installed in a motor vehicle
Current assignee: Mercedes Benz Group AG
Added 9/24/2026, 3:29:15 PM
Active provider: DeepSeek · deepseek-flash
Patent summary
Title, assignee, inventors, filing/issue dates, abstract, and a plain-language overview of the claims.
I'll search for litigation and current-status information on this specific patent number, then compile the summary.
Let me make one more targeted check for any litigation record.
US Patent 9,513,191 — Summary
Important scoping note up front: I searched for this specific number (9,513,191 / US 9,513,191 B2 / application 14/124,062) and found no CAFC 2026 docket activity, no IPR/PGR, and no district-court case naming this patent. The only Daimler-related litigation my searches surfaced was Orbital Australia Pty Ltd v. Daimler AG, E.D. Va. Civil Action No. 3:14-cv-808, which asserts US 6,923,387, US 5,655,365, and US 5,606,951 — not US 9,513,191. So the litigation/docket portion of your request returns a null result for this patent number, and I'm stating that explicitly rather than substituting a similar number.
Bibliographic Data
| Field | Value |
|---|---|
| Patent number | US 9,513,191 B2 |
| Title | Method for monitoring a subsystem installed in a motor vehicle |
| Inventors | Herbert Schankula; Markus Richter |
| Original assignee | Daimler AG (assignment recorded 2013-12-05, effective 2013-11-11) |
| Current assignee (per Google Patents) | Mercedes Benz Group AG (change of name from Daimler AG; effective 2021-10-01, recorded 2025-07-29) |
| Application no. | US 14/124,062 (PCT/EP2011/006251) |
| Pre-grant publication | US 2014/0277904 A1 (2014-09-18) |
| Priority date | 2011-06-09 (DE 102011103699.0 / DE102011103699 A1) |
| Filing date | 2011-12-10 |
| Issue date | 2016-12-06 |
| Adjusted expiration | 2032-01-18 |
| Status | Active; maintenance fees paid (4th yr 2020, 8th yr 2024) |
| Claims | 24 total, 1 independent (claim 1), 23 dependent |
Foreign family members: EP 2718689 B1, JP 5990263 B2, CN 103597332 B, RU 2573076 C2, WO 2012167810 A1, DE 102011103699 A1.
Abstract (verbatim)
A method for monitoring a subsystem installed in a motor vehicle involves a diagnostic unit checking the subsystem for system errors at least during driving cycles of the motor vehicle, the check being carried out for an occurrence as well as for a correction of a system error. The diagnostic unit carries out a misuse assessment based on a frequency of detection of the occurrence and/or the correction of the system error in order to determine whether the detected occurrence and/or the detected correction of the system error is/are based on misuse. If occurrence of the system error is detected, a restricted operating mode is activated or an activated restricted operating mode is continued in which drivability of the vehicle is restricted after a predefinable number of driving cycles has elapsed or after a predefinable travel distance has passed without the correction of the system error being detected.
Independent Claim 1 — Plain-Language Overview
Claim 1 is a method for monitoring a motor-vehicle subsystem, with three core steps:
Check for errors across driving cycles. A diagnostic unit checks the subsystem during driving cycles of the vehicle, and the check covers both (a) the occurrence of a system error and (b) the correction of a system error.
Misuse assessment by frequency. The diagnostic unit performs a misuse assessment based on the frequency of detection of the occurrence and the correction of the error, to decide whether the detected occurrence/correction is based on misuse. Critically, claim 1 includes an express definition of "misuse": it is the occurrence or correction of the system error resulting from an intervention in the subsystem impermissibly carried out by a user of the motor vehicle. (Note: the published specification's narrative defines misuse as including intentional acts, but the claim language itself is limited to "impermissibly carried out by a user," without an explicit intent requirement.)
Restricted driving mode triggered by an uncorrected error. If an occurrence of a system error is detected, a restricted driving mode is activated (or an already-activated one is continued). In that mode, drivability is restricted once either:
- a predefined number of driving cycles has elapsed without the correction being detected, or
- a predefined travel distance has passed without the correction being detected.
Scope takeaway: The independent claim is deliberately broad on the "how" of the frequency analysis — it recites a frequency-based misuse assessment but does not require the specific characteristic-number formula (k_x = f(k_x-1, F, Σ(M), Σ(B))), the error/mode bits, the remaining-start counter, or the SCR-specific context. Those appear only in dependent claims or the specification. The two claim-1 features most likely to drive validity/infringement arguments are (i) the frequency-based misuse determination and (ii) the restricted drivability consequence tied to elapsed cycles/distance.
Dependent Claims at a Glance
- 2–3: Subsystem is an exhaust aftertreatment system (2), specifically an SCR system checked for consumption-relevant errors causing significantly reduced reducing-agent (urea) consumption (3).
- 4: A memory with per-driving-cycle status locations (error occurrence/correction, restricted-mode switching) across successive cycles, used for the misuse assessment.
- 5: In the restricted mode, a remaining engine-start count or remaining travel distance is decremented from a predefined starting value.
- 6–8: Restricted mode is deactivated only if the misuse assessment shows no misuse; or a detected "correction" is treated as invalid if misuse is found (claims 7–8 track claims 2–3).
- 9–11: The error check requires a "valid" driving cycle, defined via minimum travel duration/distance/speed and/or engine standstill duration (9, and its variants 10–11).
- 12–14: Stored status info from multiple preceding cycles (valid cycle, restricted-mode switching) feeds the misuse assessment (12, and variants 13–14).
- 15–18: A characteristic number redetermined each valid cycle; misuse is found when it reaches/exceeds a limit value (15, and variants 16–18).
- 19–20: The characteristic number is correlated with the number of detected occurrence/correction events.
- 21–24: The characteristic number is stored per driving cycle, and the previous cycle's value is used to compute the current one (i.e., a recursive/accumulating counter).
Notes on Uncertainty / Data Anomalies
- Litigation: No CAFC 2026 docket entries, and no IPR/PGR or district-court filings, were found associating US 9,513,191 with any litigation. Absence of search hits is not affirmative proof that no action exists, but I found nothing.
- Legal-events anomaly: The Google Patents legal-events table for this file lists a 2013-01-30 security-agreement entry naming CREDIT SUISSE AG and ALCATEL LUCENT — which is unrelated to Daimler or this subject matter. I read this as a spurious/mis-linked record in the source data, not as a real chain-of-title event for US 9,513,191. Treat it with caution.
- Assignee naming: "Mercedes Benz Group AG" is presented as the current assignee by change of name from Daimler AG; the record's stated effective date (2021-10-01) differs from its recording date (2025-07-29). The underlying current owner is, per this record, the Mercedes-Benz Group entity.
- Everything above marked as bibliographic/claim data is grounded in the authoritative patent text you supplied; I have not independently verified it against USPTO Patent Center or the CAFC docket system, which I could not reach in this session.
Generated 9/29/2026, 10:52:51 PM
Cases on file (0)
Specific litigation cases in our database that name US patent 9513191. The free-form analysis below may also discuss cases beyond this list.
No cases on file mention this patent. Upload a CSV or add a case manually in Admin → Manage litigation cases.
Litigation summary
Past and pending lawsuits — plaintiffs, defendants, jurisdictions, outcomes, and notable rulings.
I'll search for litigation involving US patent 9513191 across patent litigation sources.
Let me do additional targeted searches on litigation databases to confirm.
Litigation Search — U.S. Patent No. 9,513,191
Bottom line: I found no record of any litigation involving U.S. Patent No. 9,513,191.
What I searched and what came back
I ran targeted queries against sources that index patent litigation (Google Patents, court documents via CourtListener/Justia, PTAB filings, and Unified Patents-related materials). No case was found in which U.S. 9,513,191 was asserted, challenged, or otherwise at issue. The patent does not appear in any complaint, IPR/PGR petition, or litigation dashboard result returned.
Notably, the patent's own Google Patents page contains no "Litigation" entries — only a citation list (prior art cited, citing documents, family members). For a U.S. patent that had been litigated, Google Patents typically surfaces a litigation tab/entries. None appear here.
Important caution — this number is easy to confuse
The searches surfaced several different patents whose numbers or shorthand names resemble "9513191," and these are not the patent at issue. Interpreted literally, none of the following is US 9,513,191:
- U.S. 5,606,951 ("'951 patent") — asserted in Orbital Australia Pty Ltd et al. v. Daimler AG, Mercedes-Benz USA, et al., Civ. No. 3:14-cv-808 (E.D. Va., later transferred to E.D. Mich., 2015). This is a different patent.
- A laundry-detergent "'319 patent" in a D. Del. case (Civ. No. 12-650/12-651) — different patent.
- U.S. 6,465,961 (Cao Group v. GE Lighting) — different patent.
I am flagging these only so they are not mistaken for 9,513,191; none of them involves the patent you asked about.
Patent context (for the file)
- Patent: US 9,513,191 B2 — "Method for monitoring a subsystem installed in a motor vehicle"
- Inventors: Herbert Schankula; Markus Richter
- Original assignee: Daimler AG → Current assignee: Mercedes Benz Group AG (name change, effective 2021-10-01, recorded 2025-07-29)
- Priority: 2011-06-09 (DE 10 2011 103 699.0); Filed: 2011-12-10 (PCT/EP2011/006251); Granted: 2016-12-06
- Family: EP2718689B1, JP5990263B2, CN103597332B, RU2573076C2, WO2012167810A1
- Status: Active; adjusted expiration 2032-01-18
Confidence and limitations
- High confidence that no litigation is recorded in the major publicly indexed patent-litigation databases as of my searches. This is consistent with the profile of the patent: it is a vehicle-control/diagnostic method patent held by an original-equipment manufacturer (Daimler/Mercedes-Benz), a category that is comparatively rarely asserted in affirmative infringement suits.
- Caveat: I was unable to complete a fully exhaustive sweep (I was cut off before finishing additional CourtListener/PACER and Unified Patents portal queries). A proceeding could exist in a venue not captured, or a very recent filing (post my search window) may not yet be indexed. Because the IDs "9513191," "'319," and "'951" are so easily conflated, a definitive clearance should be run directly against the primary sources.
Recommended verification steps
To confirm "no litigation" as a final matter, check these directly (I could not fully retrieve them):
- Unified Patents litigation portal — https://portal.unifiedpatents.com/litigation (search by patent number).
- CourtListener / RECAP — https://www.courtlistener.com (search docket text for "9,513,191").
- USPTO Patent Center / Patent Assignment & Litigation search — https://patentcenter.uspto.gov and the USPTO "Patent Litigation Docket" search.
- PACER (D. Del., E.D. Mich., E.D. Va., C.D. Cal., W.D. Tex. — venues common for auto/supplier patent suits).
- PTAB — search for IPR/PGR/CBM petitions naming 9,513,191 as the challenged patent.
If you'd like, I can attempt a second pass focused specifically on one of those primary sources once search capacity is restored.
Generated 9/29/2026, 10:52:51 PM
Proceedings on file (0)
All PTAB activity →AIA trial proceedings (IPR / PGR / CBM) filed at the USPTO Patent Trial and Appeal Board against this patent. Sourced from the USPTO Open Data Portal and refreshed every six hours; each proceeding number deep-links to the PTAB E2E docket.
No PTAB proceedings on file. This patent has not been challenged via IPR, PGR, or CBM. The absence is itself a signal — well-asserted patents eventually attract IPRs. The LLM analysis below may surface filings the ODP feed hasn’t indexed yet.
PTAB challenges
AIA trial proceedings at the USPTO Patent Trial and Appeal Board — IPR, PGR, and CBM. Petitioners, judge panels, claim-level invalidation outcomes from Final Written Decisions, and Federal Circuit appeals. The single most important defensive datapoint after litigation history.
I'll verify the structured-data default with targeted web searches before concluding.
Let me run final verification searches on possible litigation/assertion context and any non-AIA challenge (EP opposition), plus confirm the "'951 patent" false positive.
PTAB Activity Report — US Patent No. 9,513,191 B2
Patent: Method for monitoring a subsystem installed in a motor vehicle
Patent Owner (current): Mercedes Benz Group AG (formerly Daimler AG)
Inventors: Herbert Schankula; Markus Richter
Priority: 2011-06-09 · Filed: 2011-12-10 · Granted: 2016-12-06 · Adjusted expiration: 2032-01-18
Source of truth: USPTO Open Data Portal structured block ("PTAB proceedings on file"), cross-checked by web search on 2026-09-29. Google Patents record: https://patents.google.com/patent/[US9513191](/patent/US9513191)/en
Proceedings overview
Zero AIA trial proceedings are on file for US 9,513,191. The structured PTAB-proceedings block reports no IPR, PGR, or CBM petitions — no institution decisions, no final written decisions, no settlements, and no Federal Circuit appeals traceable to this patent. My independent web searches likewise surfaced no petition, decision, or appeal bearing this patent number.
The defensive posture this creates is neutral-to-cautious, not triumphant. Unlike a patent hardened by surviving IPRs, this patent has simply never been tested at the Board. That is a double-edged signal for a defendant: (1) there is no § 315(e) estoppel anywhere, so every prior-art ground remains fully available to you; but (2) the claims are untested, and the surface area of the underlying prosecution record (a small set of German-priority references) has never been stress-tested by an adversarial petitioner. This is an operating-company patent (Mercedes-Benz), not an NPE patent — so the "troll with dead claims" framing does not fit, and there is no litigation-driven petition history to mine.
Important disambiguation (false positive flagged). Web results referencing "the '951 patent" in IPRs (e.g., Xilinx and Samsung petitions in Arbor Global Strategies LLC v. Xilinx, Inc. / v. Samsung) concern U.S. Patent No. 7,282,951 — an unrelated semiconductor patent. The coincidental trailing digits do not denote U.S. 9,513,191. Do not cite those proceedings in any brief or demand response as pertaining to this patent.
Proceedings (most-impactful first)
None. There are no proceedings to itemize. Per the task constraint, I will state this plainly rather than manufacture entries: no IPR20XX-#####, PGR20XX-#####, or CBM20XX-##### number can be attributed to this patent from the structured data or from public search.
Contingent / adjacent activity (not AIA trials — noted for completeness only)
- EP 2 718 689 B1 — the European family member, granted 2015-12-09 (family also includes JP5990263B2, CN103597332B, RU2573076C2; German DE102011103699A1 withdrawn). I could not confirm or rule out an EPO opposition within my search budget. An EPO opposition, if any, would not be an AIA trial but could be usefully mined for prior art and claim-construction positions. Treat as unverified.
- No assertion litigation identified. I did not find a US district court action asserting 9,513,191 in my searches. Absence of assertion is consistent with the absence of IPRs — nothing has driven a validity challenge.
Strategic summary
Claim status across the patent. All 24 claims stand UNCHALLENGED / UNTESTED. Nothing is canceled, nothing is confirmed by the Board, and nothing has been narrowed by certificate. Independent claim 1 (the misuse-assessment + restricted-driving-mode method) and its dependents — including the SCR/urea-consumption embodiments of claims 2–3, the memory/status-information claims 4 and 12, the remaining-starts decrement claim 5, the "misuse blocks deactivation" claims 6–8, the valid-driving-cycle claim 9, and the characteristic-number claims 15–24 — remain exactly as granted. For a defendant, the entire claim set is live and must be addressed on the merits; there is no canceled-claim shortcut.
Estoppel landscape. Because no petition was ever filed, § 315(e)(1) and (e)(2) estoppel does not attach to anyone. You (or any co-defendant, or any privy) may raise any § 102/§ 103 ground, before the Board or in district court, unconstrained by prior-petition estoppel. The only estoppel-adjacent friction is § 325(d) — art that the examiner already considered during prosecution of the '191 patent. Practically, the reexamination-/IPR-facing playbook is wide open: the strongest ground set will be art that is not cumulative of the prosecution record, since the specification's own framing (diagnostic unit counts error/correction events across driving cycles, trips a restricted operating mode) is a good target for § 103 combinations. Note the narrow statutory gates that now apply regardless: PGR is unavailable (the 9-month post-grant window closed 2017-09-06), and CBM review is sunset (transitional program expired 2020-09-16). IPR under §§ 311–319 remains the only AIA vehicle.
Pattern signals. No repeated-petitioner pattern, no patent-owner appeal pattern, no defensive aggregator (e.g., Unified Patents) in the chain — the chain is simply Daimler AG → Mercedes Benz Group AG by change of name, with maintenance fees paid at the 4th (2020-06-03) and 8th (2024-05-28) years and the patent active through 2032-01-18. The "absence is itself a signal" reading cuts the other way here: this is a component-level emissions-control patent owned by an operating company, in a family that has been heavily litigated in Europe over SCR/AdBlue strategy (e.g., the UK Pan-NOx judgment and German diesel litigation), yet no one has bothered to IPR it in the US. That is a mild negative signal for the patent's commercial assertion value, not a positive one for its strength.
Recommended next steps
- If you are a defendant being asserted: the absence of any PTAB proceeding is your opening — you would be the first mover with zero estoppel exposure. Commission a full invalidity search now, prioritizing art outside the prosecution record (the IDS-heavy record invites § 325(d) friction if you recycle examiner-considered references). Watch the § 315(b) one-year clock running from service of the complaint; a petition filed after that date is time-barred.
- If you are considering a petition: the natural § 103 attack points are the "frequency-of-detection misuse assessment" and "restricted operating mode after N predefinable driving cycles / travel distance" limitations of claim 1, and the SCR "significant decrease in reducing-agent consumption (≥20%, preferably ≥30%)" limitation of claim 3. Because the claims are method claims tied to a diagnostic-unit algorithm, prior art in the OBD/tamper-detection and reductant-dosing spaces (including the references cited in the record — e.g., DE 195 48 684 A1, US 2007/0018830 A1 Honda tamper detection, and US 2013/0116881 A1 Ford "distinguish degradation from tampering") will be central. Verify each on its own merits; do not assume citation equals anticipation.
- Monitoring: if a proceeding is filed after the ODP ingest cut-off above, expect (i) institution decision at ~6 months from petition, (ii) oral hearing at ~9–10 months, and (iii) FWD within the statutory 1-year-from-institution deadline (§ 316(a)(11)), extendable to 18 months for good cause. Re-run the ODP query — and the PTAB E2E / Patent Trial and Appeal Board decisions pages — before relying on the "no activity" conclusion in any filing.
Confidence and limits. The "no PTAB activity" conclusion rests on two independent sources agreeing: the structured ODP block supplied in this prompt and my web searches. I could not, within the allotted search budget, positively verify EPO opposition status for the family member EP 2 718 689 B1, nor exhaustively sweep every district-court docket for an assertion of this patent. Both are flagged as unverified, not as negative findings. No proceeding number, panel, decision date, or disposition has been invented; where the structured data was silent, I have said so rather than filling the gap.
Generated 9/29/2026, 10:53:02 PM
Assignment history
Inventors, original assignee, and the chain of ownership recorded with the USPTO — including the correspondent attorney who recorded each assignment, since shell-LLC chains often share one repeat-player attorney even when the entity names look unrelated. Surfaces NPE / patent-troll patterns: shell-entity transfers, known asserters in the chain, repeat correspondent fingerprints, pre-litigation assignments, and bankruptcy fire-sales.
I'll research the assignment record and correspondent information for this patent before compiling.
Let me try to pin down the correspondent of record for the specific assignment reels.
Ownership & Assignment Analysis — US 9,513,191 B2
Source note / scope: The def
Generated 9/29/2026, 10:53:12 PM
Prior art
Earlier patents, publications, and products that may anticipate or render the claims unpatentable.
I'll run targeted searches against the patent record and each cited reference. Note one date discrepancy up front: the system clock reads 2026-09-29, while your task header says 2026-04-26 — I'll flag that rather than silently pick one.
Let me pull the primary record and the key citations.
Good — the primary record confirms the citation list. Now let me pull the most §102-relevant references in detail.
I hit the tool-step ceiling before finishing every reference retrieval, so I'll flag precisely which references I pulled full text for versus which I only have citation metadata for. Also noting the date conflict: your task header says April 26, 2026, the session clock says 2026-09-29 — I'll use the record facts, which don't turn on that difference.
Prior-Art Analysis — US 9,513,191 B2
0. Record confirmation (and what I could/couldn't reach)
The patent number resolves cleanly and uniquely:
- US 9,513,191 B2, "Method for monitoring a subsystem installed in a motor vehicle," Daimler AG (now Mercedes-Benz Group AG), appl. 14/124,062, PCT/EP2011/006251, filed 2011-12-10, priority DE 10 2011 103 699.0 (2011-06-09), granted 2016-12-06. (Google Patents, Justia)
- I could not open USPTO PatentCenter directly in this session; the record above is the Google Patents/Justia mirror of the USPTO file. Interpreted literally, 9,513,191 is a single patent — I did not fold in any similar number (this is consistent with the two prior sections, which found no litigation and correctly flagged the
'951/'319number-confusion risk).
This section builds on the earlier summary (24 claims, 1 independent) and litigation section (no litigation found); nothing here contradicts either.
1. The controlling legal date matters — and it is pre-AIA
Effective US filing is the PCT international filing date, 2011-12-10 (35 U.S.C. §363), which is before March 16, 2013, so pre-AIA §102/§103 govern. Priority date is 2011-06-09.
This produces three distinct prior-art windows, and the distinction is decisive here:
| Window | Date | What qualifies |
|---|---|---|
| §102(b) statutory bar | published before 2010-12-10 (1 yr before US filing) | printed publications/patents |
| §102(a) | published before the invention date (≈2011-06-09) | printed publications/patents |
| §102(e) | US patent/pub with a US filing date before 2011-06-09 | US filings & published US applications |
Critical nuance the examiner appears to have exploited (the Hilmer doctrine): Under pre-AIA §102(e), an applicant's foreign priority date cannot be used to antedate a US §102(e) reference — only the applicant's US filing date counts (In re Hilmer, 359 F.2d 859 (CCPA 1966)). So a US application filed between 2011-06-09 and 2011-12-10 is still valid §102(e) art against US 9,513,191, even though it post-dates the German priority. Several cited references (Ford 2011-11-04; 128 Combustion 2011-09-15; Ford 2011-10-27) sit exactly in that window — which is the likely reason a seemingly "later" reference was cited. ⚠️ I did not independently verify each reference's actual US filing date versus the "priority date" Google Patents displays (which is often the earliest, sometimes foreign, priority). That verification is the single most important next step.
2. Master citation table (the 32 "Patent Citations," with §102/claim mapping)
Dates are as listed on the record. "Desc." is drawn from the citation title plus, where I retrieved text, the specification.
2A. References dated before the 2011-06-09 priority — genuine §102 candidates
| # | Citation | Pub / prio date | Desc. | Potential §102 target claims | Anticipates claim 1? |
|---|---|---|---|---|---|
| 1 | DE 195 48 684 A1 (Bosch) | 1997-06-26 / 1995-12-23 | OBD detection & documentation of exhaust-relevant malfunctions; malfunction lamp | Background only | No |
| 2 | US 5,741,958 A (Bosch) — US counterpart of #1 | 1998-04-21 / 1995-12-23 | Detects misfires etc.; stores fault announcements in dependence on a pregiven number of drive cycles; distinguishes an empty-tank-caused fault from a genuine technical defect via fill-level | 4, 9 (partial) | No |
| 3 | US 6,260,411 B1 (Bosch) | 2001-07-17 / 1997-07-11 | Suppresses erroneous OBD announcements caused by fuel deficiency | Background (false-positive suppression) | No |
| 4 | US 2002/0123833 A1 (Sakurai) | 2002-09-05 / 2001-03-01 | Vehicle diagnostic system | Background | No |
| 5 | JP 2005-147118 A / US 7,685,810 B2 (Nissan Diesel) | 2005-06-09 / 2003-10-22 ; 2010-03-30 | Engine control / exhaust emission control apparatus | 2 (exhaust subsystem) | No |
| 6 | JP 2007-522370 A / US 2007/0277502 A1 / US 7,765,797 B2 (DaimlerChrysler/Daimler) | 2007-12-06 / 2003-12-06 ; 2010-08-03 | SCR + urea tank; emergency running mode; restricting drivability (speed/engine-speed limiting) and preventing engine restart when urea not replenished; readable error memory; locked refill to prevent unauthorized opening | 1 (partial — the drivability-restriction half), 2, 3 | No (no misuse/frequency assessment) |
| 7 | US 2006/0265594 A1 / WO 2005/093668 A1 (BMW) | 2006-11-23 / 2004-03-09 | Documentation of vehicle service measures | 6 (authorized-service handling) | No |
| 8 | JP 2006-177317 A / US 7,842,267 B2 (Nissan Diesel) | 2006-07-06 / 2004-12-24 ; 2010-11-30 | Exhaust emission purifying apparatus for engine | 2 | No |
| 9 | US 2007/0018830 A1 (Honda) | 2007-01-25 / 2005-07-20 | Tamper detection: RFID ID chip on component; ECU detects fraudulent replacement/removal (e.g., catalyst-coated radiator) | 1 (misuse-concept only), 6 | No (no frequency assessment, no restricted-drive consequence) |
| 10 | EP 1 760 623 A2 / US 2007/0043951 A1 (Grill / Siemens) | 2007-03-07 / 2005-08-18 | "Safety device for electronic devices" — tamper protection for electronic units | 1 (misuse-concept only) | No |
| 11 | US 2009/0030570 A1 (Renault) | 2009-01-29 / 2005-12-13 | Controlling vehicle operating condition via onboard diagnostic strategy defining different failure types | 1 (operating-mode / failure-type angle), 6 | Possible — needs full text |
| 12 | JP 2009-067091 A (Toyota) | 2009-04-02 / 2007-09-10 | Hybrid drive device | Background | No |
| 13 | DE 10 2009 014 624 A1 (BMW) | 2010-09-30 / 2009-03-24 | Displaying faults in the motor vehicle | Background | No |
| 14 | US 2011/0231053 A1 (Hitachi Automotive) | 2011-09-22 / 2010-03-17 | CAN-communication vehicle control device + diagnostic method | Background | No |
| 15 | US 2012/0226397 A1 (Deere) | 2012-09-06 / 2011-03-01 | Embedded-controller frequency inputs re-used for speed-sensor diagnostics | Background | No |
| 16 | US 2014/0032041 A1 (Daimler AG) | 2014-01-30 / 2011-04-16 | On-board diagnosis unit for a motor vehicle (same assignee) | Potential §102(e) — needs full text; could touch 1, 4, 9 | Possible — needs full text |
| 17 | US 2013/0024066 A1 (Systech International) | 2013-01-24 / 2011-05-27 | Fraud detection in an OBD inspection system | 1 (misuse/fraud concept), 6 | Possible — needs full text |
| 18 | US 2014/0104048 A1 (De Kock) | 2014-04-17 / 2011-05-27 | Anti-theft system for an automotive exhaust component | 1 (misuse), 2 | No (no frequency/mode) |
| 19 | US 2008/0147265 A1 (Automotive Technologies Int'l) and US 2012/0296567 A1 (American Vehicular Sciences) | 2008-06-19 / 1995-06-07 ; 2012-11-22 / 1995-06-07 | Vehicle diagnostic/prognostic message transmission; vehicle component control | Background | No |
2B. References inside the Hilmer window (US-filed after 2011-06-09 but before 2011-12-10) — §102(e) suspects
| # | Citation | Pub / prio date | Desc. | §102(e) relevance | Claim(s) |
|---|---|---|---|---|---|
| 20 | US 8,718,905 B2 (128 Combustion, LLC) | 2014-05-06 / 2011-09-15 | Supplementing engine control via a diagnostics port | Manipulation through diagnostic access | 1, 6 |
| 21 | US 2013/0249682 A1 (Ford) | 2013-09-26 / 2011-10-27 | Vehicle wireless charger safety system | Low relevance | — |
| 22 | US 2013/0116881 A1 (Ford) → granted US 9,068,492 B2 | 2013-05-09 / 2011-11-04 | Distinguishes tampering from degradation: tamper flag; single-drive-cycle detection; preemptive urea-quality-warning-chain inducement mode limiting vehicle speed; asymmetric debouncing | Closest conceptual match to claim 1's misuse-assessment + restricted-drive concept | 1, 5, 6 |
2C. References dated after the US filing (2011-12-10) — not §102/§103 prior art at all
| # | Citation | Pub / prio date | Note |
|---|---|---|---|
| 23 | US 2014/0260216 A1 (Cummins IP) | 2014-09-18 / 2013-03-14 | Diagnosing reductant delivery performance |
| 24 | US 2015/0166357 A1 (Cummins) | 2015-06-18 / 2013-12-12 | Prevention of theft and misuse of ammonia storage systems — thematically on-point but too late |
| 25 | US 2016/0146080 A1 (Jaguar Land Rover) | 2016-05-26 / 2013-07-05 | Monitoring fluid reductant |
⚠️ Flag: these three are the same subject matter as the patent (SCR-reductant misuse/theft) but post-date the 2011-12-10 US filing and the 2011-06-09 priority. They are not available as §102 or §103 art against 9,513,191; they belong in a freedom-to-operate / later-patent analysis, not a validity analysis.
3. Deep-dive on the four references that matter most
3.1 US 5,741,958 A (Bosch) — full text retrieved
- Priority 1995-12-23; granted 1998-04-21.
- Detects exhaust-relevant malfunctions by sensors, evaluates in a circuit unit, stores fault announcements "in dependence upon a pregiven number of drive cycles," and differentiates a fault caused by an empty tank from a genuine technical defect using a stored fill-level value.
- §102 relevance: Anticipates nothing in claim 1. It shares only the generic scaffolding — OBD detection across drive cycles and count-based fault handling — but contains no misuse concept, no frequency-of-occurrence-and-correction assessment, and no restricted driving mode. It is, at best, §103 background for claim 4 (per-cycle fault memory) and claim 9 (preconditions/validity). Its "empty tank vs. real defect" logic is the closest analog in the art to "distinguish a benign cause from an illegitimate one," and is worth citing in any §103 combination.
3.2 US 7,765,797 B2 / US 2007/0277502 A1 (Daimler) — full text retrieved
- Priority 2003-12-06; granted 2010-08-03. Same assignee as the patent.
- SCR exhaust-purification system with urea tank; determines consumption and remaining range; switches to an emergency running mode, and — importantly — if refilling is ignored, "the drivability of the vehicle [can] be restricted, for example by automatic speed limiting and/or engine speed limiting," the restrictions "may also be gradual," and if the tank is emptied, restarting can be prevented; incorrect operation is stored in a readable error memory; and the refill opening is locked against unauthorized opening (software code / special tool / seal).
- §102 relevance: This is the strongest cited reference for the "restricted driving mode" limb of claim 1 and for claims 2–3 (exhaust/SCR subsystem, urea consumption). But it restricts drivability as a function of reductant shortage, not as a function of a frequency-based misuse assessment of error occurrence/correction. It therefore does not anticipate claim 1; it is a strong §103 primary reference against claims 1/2/3 when combined with a tamper/frequency reference (e.g., Honda ʼ830 or Ford ʼ881).
3.3 US 2007/0018830 A1 (Honda) — full text retrieved
- Priority 2005-07-20; published 2007-01-25.
- Vehicle component tamper detection: a hard-to-remove RFID identification chip on a component (e.g., an ozone-catalyst-coated radiator); the ECU detects fraudulent replacement/removal. The background expressly addresses emissions-control components being fraudulently swapped/removed and notes such components are expected to increase with tightening emissions rules.
- §102 relevance: Anticipates only the concept of detecting impermissible intervention in a monitored vehicle subsystem — the "misuse" definition in claim 1. It has no frequency assessment, no driving-cycle accounting, and no restricted-drivability consequence. §103 candidate for the misuse element.
3.4 US 2013/0116881 A1 → US 9,068,492 B2 (Ford) — full text retrieved
- Priority/examiner-cited date 2011-11-04; published 2013-05-09; granted 2015-06-30.
- Provides a first response if degradation is due to tampering and a second if not; sets a tamper flag; detects/assesses tampering within a single drive cycle for certain components; uses asymmetric debouncing (long time constant on the "tamper" state); and — critically — on an SCR stage, "preemptive activation of a UQWC that includes an inducement mode," where the inducement mode "may limit the vehicle speed to a very low speed within four hours of activation." It expressly frames tampering as an operator/service-tech act to silence the urea warning chain.
- §102 relevance — with a caveat: Conceptually this is the closest match to the invention's core idea (tamper/misuse detection + restricting vehicle operation on an SCR system). But it is not §102(a)/(b) art (published 2013, well after both the 2011-06-09 priority and the 2011-12-10 filing). Its only path to prior-art status is pre-AIA §102(e) on the strength of its 2011-11-04 US filing sitting before Daimler's 2011-12-10 US filing — the Hilmer scenario described in §1. If the actual US filing date is confirmed as 2011-11-04, Ford is a §102(e) reference and a powerful §103 primary reference; if it is not, Ford is not prior art at all to this patent.
4. Bottom line on § 102 anticipation
No cited reference, on the text I retrieved, anticipates independent claim 1. Claim 1 requires the conjunction of:
- checks for both occurrence and correction of a system error, across driving cycles;
- a misuse assessment keyed to the frequency of detection of occurrence/correction;
- a defined misuse = user's impermissible intervention; and
- a restricted driving mode triggered on occurrence, restricting drivability after a predefined number of cycles/distance without correction.
The cited art splits into two camps that do not overlap:
- Fault-differentiation / tamper camp (Bosch ʼ958 and ʼ411, Honda ʼ830, Siemens/Grill ʼ951, Systech ʼ066, Ford ʼ881) — has the misuse/tamper-concept but no frequency-of-occurrence-and-correction metric joined to a drivability consequence. (Ford ʼ881 comes closest but adds single-cycle detection, not frequency assessment.)
- Restricted-driving camp (Daimler ʼ797, Nissan Diesel ʼ810/ʼ267) — has the drivability restriction and the SCR context but restricts on reductant shortage, not on a misuse/frequency finding.
Anticipation verdict by claim:
- Claim 1: No single-reference §102 anticipation identified. Best §103 case = Daimler ʼ797 (restricted-drive + SCR) + Ford ʼ881 or Honda ʼ830 (tamper/misuse), properly dated.
- Claims 2–3: Daimler ʼ797 (SCR/urea) and Nissan Diesel ʼ810/ʼ267 are the closest; still not clean §102 because neither checks for "consumption-relevant errors causing significantly decreased reducing-agent consumption" as claim 3 recites — they act on level/shortage, not on abnormally reduced consumption.
- Claim 5: Not anticipated — no cited reference decrements a remaining-engine-start counter.
- Claims 6–8: Honda ʼ830 / Ford ʼ881 touch the "disallow/void a correction when tampering" idea; Daimler ʼ797 stores faults in a readable error memory.
- Claims 9–14 (valid driving cycle; stored per-cycle status): Only generic echoes in Bosch ʼ958 (drive-cycle-dependent fault storage) and US 2006/0265594 (BMW service documentation).
- Claims 15–24 (characteristic number, recursion kₓ = f(kₓ₋₁, F, Σ(M), Σ(B))): Not anticipated by any cited reference — this recursive misuse characteristic number is the most clearly novel/dependent subject matter in the set.
5. Caveats and recommended next steps
- US filing dates are the pivot. Confirm the actual US filing dates (not the displayed priorities) for Ford ʼ881, Ford ʼ682, and 128 Combustion ʼ905; Hilmer makes these §102(e) art only if their US filings precede 2011-12-10.
- Three references I could not retrieve text for and which are the most likely to change the §102 picture: US 2014/0032041 A1 (Daimler, same assignee — on-board diagnosis unit), US 2013/0024066 A1 (Systech, OBD fraud detection), and US 2009/0030570 A1 (Renault, failure-type diagnostic strategy). Renault in particular is a known source of SCR "inducement/derate" strategies and warrants a full read.
- Post-date references (Cummins ʼ216/ʼ357, JLR ʼ080) should be excluded from the validity chart entirely; they are relevant to the patent's forward citation landscape (they cite 9,513,191's family), not to its validity.
- Non-patent citations on the record (German Office Action 2014-12-11; German Search Report 2014-09-18; Japanese Office Actions 2015-02-24 and 2015-12-08; ISR/Written Opinion 2012-05-10) are prosecution-history, not §102 art, and are worth pulling only if you need the examiner's own grounds of allowance.
If you want, I can take the three un-retrieved references in a second pass and give a complete element-by-element §102 chart against claim 1.
Generated 9/29/2026, 10:54:00 PM
Obviousness
Combinations of prior art that suggest the claimed invention would have been obvious under 35 U.S.C. § 103.
I'll analyze obviousness under § 103 using the prior-art references listed on this patent's page. Let me first verify the subject matter of the key cited references so my mappings are grounded.
Obviousness Analysis — U.S. Patent No. 9,513,191 B2 under 35 U.S.C. § 103
Building on the prior summary and litigation sections (not repeated here). Note up front: the summaries above found no litigation and no PTAB proceedings for this patent. That matters analytically — there is no litigation record of secondary-considerations evidence (no nexus, no commercial-success, no copying, no unexpected-results record) to weigh against the prima facie case below.
1. Governing framework and prior-art date qualification
Effective filing date / legal regime. The application is a PCT national stage: priority DE 10 2011 103 699.0 (2011-06-09), PCT/EP2011/006251 filed 2011-12-10, U.S. 14/124,062. Because the effective filing date precedes March 16, 2013, the pre-AIA §§ 102/103 regime governs. Prior art must therefore predate the applicant's invention date (presumptively 2011-06-09), and pre-AIA § 103(c) common-ownership carve-outs apply to certain § 102(e)/(f)/(g) art.
Standard. Graham v. John Deere (scope/content of art; differences; PHOSITA level; secondary considerations), as refined by KSR Int'l v. Teleflex (2007): a combination is obvious where the elements were known, the combination is of familiar elements according to known methods, and it yields predictable results; the motivation may come from the nature of the problem, the prior art's own teachings, or common sense/design incentives, not just explicit "combination" language.
PHOSITA. An engineer with an advanced degree (or ~3–5 years' experience) in automotive powertrain controls / OBD / emissions aftertreatment calibration, familiar with OBD‑II fault-memory conventions (2-trip set / 3-trip clear logic), SCR/urea dosing systems, and "limp-home"/derate/inducement strategies.
Prior-art status of the page's cited references (flagged, not auto-corrected):
| Reference (as listed) | Date | § 103 prior art to 2011-06-09? |
|---|---|---|
| DE19548684A1 / US5741958A (Bosch) | 1995 / 1998 | Yes |
| US20070018830A1 (Honda — tamper detection) | pub. 2007-01-25 | Yes |
| US20090030570A1 (Renault — OBD degraded mode) | pub. 2009-01-29 | Yes |
| US20070043951A1 / EP1760623A2 (Grill/Siemens) | 2007 | Yes |
| DE102009014624A1 (BMW — displaying faults) | 2010-09-30 | Yes |
| US7765797B2 (DaimlerChrysler — reducing-agent tank) | 2010-08-03 | Yes |
| US7842267B2 (Nissan Diesel — exhaust purification) | 2010-11-30 | Yes |
| US20130024066A1 / US8666588B2 (SysTech — OBD fraud) | prov. 2011‑05‑27 | Arguably § 102(e) (provisional predates priority by 13 days) |
| US20140032041A1 (Daimler — on-board diagnosis unit) | prio. 2011‑04‑16, pub. 2014 | Possibly § 102(e); but § 103(c) common-ownership (Daimler) likely disqualifies it for § 103 |
| US20140260216A1 (Cummins), US20150166357A1 (Cummins), US20160146080A1 (JLR), US20130116881A1 (Ford), US8718905B2 | 2011‑09 to 2013 | No — post‑date the priority date; usable only as background/context |
So the usable § 103 combination space is the pre‑2011 set. I treat the post‑2011 citations (Cummins, JLR, Ford, 128 Combustion) as non-prior-art context only.
2. Claim 1 — element decomposition and mapping
Claim 1 has three limitations:
- (A) "checking, by a diagnostic unit, the subsystem for system errors at least during driving cycles … the check is performed for an occurrence of a system error and a correction of the system error."
- (B) "performing … a misuse assessment based on a frequency of detection of the occurrence and the correction," with the claim's own definition: misuse = "the occurrence … or the correction … due to an intervention in the subsystem impermissibly carried out by a user."
- (C) "activating a restricted driving mode or continuing an activated restricted driving mode if occurrence … is detected," where drivability is restricted after a predefined number of driving cycles OR a predefined travel distance without correction.
| Claim-1 element | Primary reference(s) | What the reference discloses (grounded) |
|---|---|---|
| (A) on-board check across drive cycles, both occurrence and clearing | Bosch US5741958A (and the admitted DE19548684A1) | On-board detection/documentation of exhaust-gas-relevant malfunctions; fault-memory handling tied to a pregiven number of drive cycles — e.g., warning set only if fault detected in two sequential drive cycles, cleared only after it is absent in three successive cycles, memory erased after 40 fault-free cycles; distinguishes faults from "an empty tank" vs. "an actual … continuously occurring technical defect." The '191 specification itself concedes this Bosch framework as known. |
| (B) frequency-based misuse assessment (tampering/user intervention) | Honda US20070018830A1; secondarily SysTech US20130024066A1; Grill US20070043951A1 | Honda: anti-tamper detection for a catalyst-coated radiator — ECU monitors behavior and, "if this distinctive temperature rise is not observed while the automobile is warmed up for a plurality of times," concludes the proper component is not attached and sets a malfunction code/MIL. That is a frequency-of-events determination of tampering. SysTech: expressly detects improper tampering (removing catalysts, reprogrammed ECU/chips, defeat devices) "to circumvent … emission regulations." Grill: inhibiting access to sensitive diagnostic data (anti-intrusion). |
| (C) restricted/degraded drivability upon detected fault, sustained across cycles | Renault US20090030570A1 | "application of an adapted operating mode consists in applying a degraded mode strategy of the operation of the vehicle corresponding to the detected presence of the failure," which is maintained if the fault persists on later cycles and abandoned upon return to normal. Renault also stores the per-cycle value at end of each cycle and initializes the next cycle with the stored value. |
Net: every claimed element exists in the pre‑2011 art; the invention sits at the intersection of (i) Bosch-style multi-cycle fault tracking, (ii) Honda/SysTech-style tamper/misuse detection, and (iii) Renault-style degraded-mode carry-over.
3. Combination 1 (primary): Bosch '958 + Honda '830 + Renault '570
Why each is properly combinable. All three are in the same field of endeavor — on-board vehicle diagnostics/emissions monitoring — and address the same underlying problem the '191 patent identifies: ensuring emissions-critical subsystems are not left uncorrected and cannot be defeated. KSR permits combination where references are "from the same field of endeavor" and the combination is "a predictable use of prior-art elements according to their established functions."
Motivation to combine (explicit):
- Bosch supplies the canvas. The '191 patent's own background cites the Bosch approach as known; using an on-board diagnostic unit to check errors across successive driving cycles is admitted prior art. Extending Bosch's cycle-tallying logic (2-set/3-clear/40-erase) to both the occurrence and the clearing of a fault requires no new technology — merely counting the same events in both directions.
- Honda supplies the "misuse" recognition and its frequency basis. Honda's teaching that tampering is inferred from an event occurring (or failing to occur) "for a plurality of times" supplies element (B)'s frequency-of-detection assessment, and its subject matter (a defeat of an emissions-benefit component) is exactly the misuse the '191 patent targets. A PHOSITA would combine Honda's multi-occurrence tamper logic with Bosch's fault memory to distinguish a genuine defect from deliberate user defeat.
- Renault supplies the consequence. Renault teaches applying a degraded-mode operating strategy whenever a fault is present, and carrying the diagnostic state from cycle to cycle. Applying the drivability restriction as the outcome of the misuse finding, and gating the number of permitted cycles/distance on the uncorrected state, is the predictable, known "derate/degraded mode" response that Renault already discloses.
- Problem-driven motivation. As the '191 specification itself admits, urea/reducing agent is a consumable with operating cost, and operators have a financial incentive to defeat dosing; and regulators/warrantors have a countervailing interest in compelling repair. That two-sided pressure supplies a classic KSR "design incentive" motivation to combine a tamper detector (Honda/SysTech) with an OBD fault memory (Bosch) and a degraded-mode enforcer (Renault).
Predicted result: a diagnostic unit that (A) checks the subsystem each drive cycle for occurrence/clearing of a fault, (B) counts how often occurrence and clearing events recur to infer impermissible user intervention, and (C) activates a degraded operating mode when a fault is detected, sustaining it across a preset cycle count/distance until corrected — i.e., the full claim‑1 method. Under KSR, the combination is a "predictable variation" using known elements for their known purposes.
4. Combination 2 (alternative for element B): Honda '830 + Renault '570 + SysTech '066
If a challenge is made to element (B)'s "frequency" character, SysTech US20130024066A1 / US8666588B2 is the more on-point misuse reference: it is directed to detecting whether an OBD/emissions system "has been improperly tampered with or altered" — including owners/service shops removing catalysts or reprogramming the ECU — and it runs multiple tamper test sequences comparing observed responses to expected responses. Even if SysTech (provisional 2011-05-27) is contested as § 102(e) art, it makes the state of the art point that misuse/tamper detection by repeated testing was a known, applied technique in the same field at the relevant time. Grill US20070043951A1 reinforces the anti-intrusion/unauthorized-intervention concept.
5. Dependent claims — mapping to known art
| Claim(s) | Feature | Rendering art |
|---|---|---|
| 2 | Exhaust aftertreatment subsystem | Bosch '958; US7842267B2 (Nissan Diesel exhaust purification); US7765797B2 (DaimlerChrysler reducing-agent tank) |
| 3 | SCR / "consumption-relevant" errors | US7765797B2 and US7842267B2 (reducing-agent storage/metering); the "significantly decreased reducing-agent consumption" is an application of the known SCR/urea architecture |
| 4 | Memory with per-cycle status locations across successive cycles | Bosch '958 (fault memory keyed to drive cycles); Renault '570 (store value at end of each cycle) |
| 5 | Decrement remaining engine starts / remaining distance from a starting value | Renault '570's degraded-mode application; the countdown-to-restriction is the conventional "inducement/derate" counter |
| 6–8 | Deactivation only if no misuse; "correction" invalid if misuse found | Honda '830 (tamper gating); SysTech '066 |
| 9–11 | "Valid" driving cycle defined by minimum duration/distance/speed/standstill | Conventional OBD "drive cycle"/"trip" definitions (Bosch '958 cycle logic) |
| 12–14 | Stored preceding-cycle status used for the assessment | Bosch '958; Renault '570 |
| 15–18 | Characteristic number vs. a limit value | Standard threshold/adaptive fault counters (Renault '570's fault booleans; the counter C bounded CMIN/CMAX → confirm-at-CMAX convention described in the same OBD art) |
| 19–20 | Characteristic number correlated with number of occurrence/correction events | Honda '830's "plurality of times" logic; Renault '570 |
| 21–24 | Characteristic number stored per cycle; previous cycle's value used | Renault '570 expressly: "storing, at the end of each cycle, said particular value … and initializing the diagnostic phase at the start of the next usage cycle with said particular stored value" |
Claims 21–24 are the most notable: their recursive "kₓ = f(kₓ₋₁, …)" structure is squarely anticipated in concept by Renault's stored-per-cycle / carry-forward value. That the '191 specification presents kₓ only as an optional formalization (variable f( ), unspecified) weakens any argument that the specific recursion is inventive.
6. Honest assessment of gaps and counterarguments
The obviousness case is strong but not airtight:
- The "why combine" for (B)+(C) needs care. Bosch distinguishes technical defects from transient conditions (and Honda/SysTech detect tampering), while Renault restricts drivability on a fault — not on a misuse determination. No single reference places "frequency-based misuse finding" as the trigger for the restricted mode. A patentee would argue the claims recite a new decision logic: the restricted mode is activated on fault occurrence but its duration/termination is governed by the misuse assessment (claims 6–8), which no reference squarely shows. In KSR terms this is an argument that the combination changes the "principle of operation" rather than merely substituting known elements — a colorable, though not compelling, rebuttal, because restricting driving as the expected regulatory consequence of an uncorrected emissions defect was itself a known response (degraded/limp-home modes).
- Some cited art is not § 103 prior art. The Cummins, JLR, Ford and 128 Combustion citations post-date the priority date and cannot be used in a § 103 combination (they merely show later, independent interest in the same problem). US20140032041A1 (Daimler) may be § 102(e) art but is likely disqualified for § 103 by pre-AIA § 103(c) given common ownership with the '191 application.
- No secondary considerations of record. The prior sections found no litigation, no IPR, and no commercial-success/copying/unexpected-results evidence tied to this patent. Absent such objective indicia, the Graham factor most capable of rebutting a prima facie case is absent from the record.
- Uncertainty flag. My characterizations of Honda, Renault, SysTech and Bosch are grounded in the retrieval above (verbatim passages from the references). I have not independently verified the full text of US7842267B2, US7765797B2, US20070043951A1, or DE102009014624A1 beyond their titles/citations on the patent page; those dependent-claim mappings are based on title/subject matter and are stated with correspondingly lower confidence.
7. Conclusion
On the face of the pre‑2011 references, claim 1 would likely be held obvious under § 103 over a combination of Bosch US5741958A (on-board, drive-cycle-based fault detection and documentation, with improper-transient vs. genuine-defect discrimination), Honda US20070018830A1 (frequency/"plurality of times"-based detection of component tampering, with MIL/malfunction-code response), and Renault US20090030570A1 (per-cycle storage of diagnostic state and application of a degraded operating mode responsive to, and maintained across, a detected fault). SysTech US20130024066A1 and Grill US20070043951A1 supply corroborating misuse/tamper-detection art. The dependent claims are, in the main, explicit or implicit in the same references — with claims 21–24 (recursive per-cycle characteristic number) being conspicuously close to Renault's stored/carried-forward diagnostic value.
The realistic non-obviousness battleground is not the individual elements but the coupling: using the frequency-based misuse finding to control activation, continuation, and (per claims 6–8) deactivation of the restricted driving mode. Whether that coupling is an "inventive" new principle or a "predictable variation" of Renault's degraded-mode logic is the dispositive question — and, absent any objective evidence of non-obviousness in the record, KSR tilts that question toward obviousness. This is an analytical conclusion, not a legal opinion, and should be confirmed against full-text review of the four references I could not verify directly.
Generated 9/29/2026, 10:54:00 PM
Extensions
Patent term adjustments, term extensions, continuations, divisionals, family members, and expiration dates.
Derivative works
Defensive disclosure: derivative variations of each claim designed to render future incremental improvements obvious or non-novel.
Keep exploring
Other patents in Automotive (A)
- US 3424139I'll search for this specific patent number across the requested sources. Search scope and results I searched for the literal identifier US 3,424,139 (US3424139A / application 605,920). What I found: - USPTO/patent-office data: Confirmed…
- US 10157384I'll search for this specific patent number and any related CAFC activity. Let me dig into the litigation/CAFC history and verify the granted claim set. Let me verify the granted claim set and check for any 2026 CAFC activity. Search scope…
- US 8032277I'll search for authoritative information on US 8,032,277, including any 2026 CAFC activity. US 8,032,277 — Verified Summary Important framing note: I have the full granted text of US 8,032,277 from the authoritative source (Google…
- US 7102494I'll search for authoritative records on this specific patent number. US Patent 7,102,494 B2 — Summary Note on numbering: I have read all identifiers literally, exactly as issued. US 7,102,494 is a real, single patent (not to be confused…
- US 6946953Patent Overview — US6946953B2 Title: Apparatus and method for enhanced data communications and control between a vehicle and a remote data communications terminal Patent number: US6946953B2 | Application: US10/158,581 | Publication…
- US 7449993US 7,449,993 — Verification Summary Search scope note: I checked the USPTO public materials indexed via patent search results (Google Patents bibliographic/family record, USPTO/PTAB petition documents, court docket aggregators) and the…
- US 7015800I'll verify the patent details and check for current litigation/docket activity before summarizing. Let me try to locate the actual claim text and any current litigation status. Let me pull the claim set to accurately describe the…
- US 6744352I'll verify this against live sources before summarizing. Let me check the litigation/appeal angle and confirm the claim set. US 6,744,352 — Summary (with source verification) Verification note: I confirmed this against Google Patents…