US 8989820

I'll search for authoritative information on this patent, including any litigation or CAFC activity.

Let me try more targeted searches on USPTO and litigation databases.

Summary — US 8,989,820 B2

Search-scope caveat up front: My searches did not surface any CAFC 2026 docket, PTAB proceeding, or district-court complaint that I could tie to patent number 8,989,820 specifically. I found no evidence of appellate activity for this patent in 2026. I did locate a third-party patent page confirming the grant (uspto.report/patent/grant/8,989,820) and a 2022 patent case styled IPCOMM, LLC v. Motion Metrics Limited et al. (S.D. Cal., No. 3:22-cv-00107), but I cannot confirm that case involves 8,989,820 — it may concern unrelated IPComm portfolio assets. Treat any litigation linkage as unverified.

Bibliographic data (from the authoritative full text)

Note: the same specification text defines the code inconsistently — "QR Code — Quality Response Code" in the glossary versus "QR (Quick Response) code" in the detailed description. I'm reporting this literally as it appears rather than correcting it.

Abstract (as issued)

The invention relates to wireless communication, specifically using a cell-phone to monitor safe driving by suspending transmission or reception of text messages and/or phone calls by the driver of a moving motor vehicle not equipped with hands-free equipment, or complete suspension of communication for a train operator while the train is in motion, unless the transmissions relate to emergency services. Determination of vehicle-operator status and operation terms-and-conditions may be obtained via a vehicle QR code or NFC/Bluetooth/other PAN transceivers combined with a cell-phone-based application.

Independent claims in plain language

Claim 1 — System (QR code + hands-free + velocity).
A "safe driving compliance system" that suspends cellular communication with a driver's smart-phone. It requires: (a) a smart-phone-based compliance application; (b) a QR code assigned to and attached to the vehicle containing the terms and conditions for operating it; (c) the application scans the QR code and confirms the driver's acceptance of those terms via the phone UI; (d) the application also establishes communication with a driver-identification unit inside the vehicle and with the vehicle's hands-free equipment; (e) it monitors vehicle velocity as measured by the smart-phone's channel-estimation function and monitors the hands-free equipment. If the vehicle is in motion and the driver's phone is not communicating through the vehicle hands-free equipment, the application suspends all incoming and outgoing communication between that phone and the cellular network, based on the accepted terms.

Claim 4 — Method of ingesting vehicle information from a QR code.
A method of obtaining vehicle-related information by the compliance application: embed the vehicle information in a QR code; attach the code to the vehicle; scan it into the application. The embedded information must contain: vehicle type (automobile, fleet vehicle, and/or train); the vehicle's hands-free capabilities; the vehicle's NFC capabilities; the vehicle terms-of-use; contact information for recipients of terms-of-use violations; and promotional materials.

Claim 10 — System (parameter set from the QR code drives suspension).
A compliance system comprising an application on a smart-phone holding a set of parameters corresponding to a vehicle and included in a QR code attached to the vehicle. The parameters must include all of: vehicle type (automobile, fleet vehicle, train); hands-free communication equipment capability; NFC capability; vehicle terms-of-use; and an emergency/insurance contact list of recipients for violation or accident reports. Those parameters, combined with vehicle-speed information, are used to suspend all incoming and outgoing communication between the driver's smart-phone and the cellular network when the vehicle is moving and the phone is not communicating through the hands-free equipment.

Claim 11 — Non-transitory memory medium.
A non-transitory computer-accessible medium storing instructions that perform all of: obtaining vehicle information by scanning the vehicle's QR code; establishing communication between an in-vehicle driver-identification unit and the phone's NFC transceiver; establishing communication between the vehicle's hands-free equipment and the phone's Bluetooth transceiver; obtaining vehicle velocity by analyzing the channel-estimation function output; detecting an accident by analyzing instantaneous changes in the accelerometer's acceleration vector; suspending communication (driver-originated/terminated, or passenger-originated/terminated but continued by the driver) while the vehicle is in motion, based on velocity and acceleration vector, when not using hands-free equipment; and sending a violation or accident report by SMS to the recipients identified for violation reports.

Dependent claims (brief)

• Claim 2 (from 1): detect an accident from instantaneous changes in the smart-phone accelerometer's acceleration vectors.
• Claim 3 (from 1): verify vehicle velocity via the smart-phone channel-estimation function.
• Claim 5 (from 4): terms-of-use in the QR code include references to the insurance contract, vehicle operating restrictions, and applicable laws restricting communication while actively operating the vehicle.
• Claim 6 (from 5): on accident detection, send an SMS alert and collect speed at impact, accident location, shock intensity, driver status, and hands-free equipment status, then store in phone memory.
• Claim 7 (from 4): after scanning, establish communication with the NFC device to verify driver status and with the Bluetooth device for hands-free, then report connection status to the cellular network.
• Claim 8 (from 4): use QR/application information to determine driving violations (operating conditions; call/SMS attempts while driving; continuing passenger-originated/terminated communication), send an SMS to QR-code-named recipients, and store violation time and location.
• Claim 9 (from 4): present QR-embedded promotional materials only when the vehicle is not in motion or the recipient is not actively operating the vehicle.

Confidence notes

• Bibliographic data, abstract, and claim content are drawn directly from the authoritative full patent text — high confidence.
• Low/uncertain confidence: existence of any CAFC 2026 appeal or active 2026 litigation involving this patent number. I found none, and I am explicitly flagging that absence rather than asserting the patent has been litigated or appealed. If you need a definitive litigation check, that requires a query to PACER/Docket Navigator or the USPTO Patent Public Search / PTAB APIs, which I could not complete within my tool budget here.

I'll research litigation involving US patent 8989820 across the sources you mentioned. Let me run several searches.

Initial searches didn't surface specific litigation. Let me search the specialized litigation databases you mentioned.

Litigation Search Results for U.S. Patent No. 8,989,820

Summary finding: I located no record of any litigation (district court, ITC, CAFC appeal, or PTAB proceeding) involving U.S. Patent No. 8,989,820.

What I searched

I ran queries specifically targeting the exact number "8989820" / "8,989,820" across general web indexes, the Unified Patents litigation/PTAB portal results, PACER-referenced docket material (CourtListener, Docket Alarm), CAFC opinion repositories, and PTAB filings (IPR / post-issuance proceedings). The instruction to return only results for the specific number was followed — I excluded hits for look-alike numbers (e.g., the Motorola "898" SEP in the Apple v. Motorola saga, Velos '898, Bank of America, NetraDyne, etc.), which are entirely unrelated patents.

What the record shows about this patent

From the authoritative patent data (Google Patents, fetched 2026-09-24):

The prosecution/assignment record contains only:

• An assignment to IPCOMM (reel/frame 029131/0173, effective 2012-06-14).
• Maintenance-fee events, ending in lapse (2023-05-01) for non-payment under 37 CFR 1.362.

Neither an examiner citation, a third-party IPR, nor a docket entry ties this patent to a court case.

Important caveats

• This is not a certified "no-litigation" opinion. I could not directly query the Unified Patents litigation portal case list or PACER's full docket database in a definitive way from these searches, and those are the authoritative sources. If a case was filed and resolved quickly — or filed under a different patent family member (e.g., US 2012/0115413 A1, Ser. No. 13/244,534) — it might not surface in a web search keyed to "8989820."
• Distinguish from related NPE activity. The search surfaced substantial litigation around other driver-distraction patents — e.g., Safe Driving Technologies LLC v. Ford Motor Co., No. 1:21-cv-00064 (D. Del.), and the IPComm patent family should not be conflated with that. However, if you have a specific signal that IPComm (or the '820 patent) was asserted, tell me the party names and I'll target them.
• Assignee name caution: "IPComm," "IPCOMM" (reel frame 029131/0173), and "IP Comm" appear in the record; these refer to the same assignee. Do not interpret these as distinct entities.

Recommendation to confirm definitively

For a conclusive determination, run these direct-source checks:

1. Unified Patents portal – patent page / litigation case list filtered to the exact number.
2. PACER / CourtListener – full-text docket search for "8,989,820" and for "IPComm."
3. USPTO Patent Trial and Appeal Board (PTAB) – search for IPR/PGR/CBM involving 8,989,820.
4. USPTO Assignment / Patent Center – confirm no post-grant reassignments that might indicate litigation-driven transfers.

Bottom line: Based on the searches performed, I found no known litigation involving US 8,989,820. The patent expired for non-payment of maintenance fees in 2023, and no case number, plaintiff, defendant, jurisdiction, filing date, or outcome can be reported for it. If you have a lead (e.g., a plaintiff or venue), I can re-run a narrowly scoped search.

Proceedings overview

Total AIA trial proceedings on file for US 8989820: 0. The USPTO Open Data Portal structured block returns no IPR, PGR, or CBM proceedings, and my independent web searches surfaced no petitions, institution decisions, final written decisions, or PTAB/Federal Circuit appeals naming this patent. There is therefore no "claims invalidated / claims sustained / settled / institution denied" breakdown to report — the breakdown is 0/0/0/0/0 across all categories.

Bottom line for a defendant: this patent was never tested at the PTAB. It is not "hardened by surviving IPRs" — it is simply unlitigated and now financially dead: the record shows the patent expired for failure to pay maintenance fees, with the lapse effective 2023-03-24 (lapse notice posted 2023-05-01, "PATENT EXPIRED FOR FAILURE TO PAY MAINTENANCE FEES ... 37 CFR 1.362"). Google Patents renders the status field as "Expired - Fee Related, expires 2032-07-27," which is the adjusted expiration date had all fees been paid — it is not the date rights actually terminated. The operative event is the non-payment lapse in 2023. That single fact dominates any defensive analysis; the absence of PTAB activity is secondary.

No proceedings to itemize

I am not going to manufacture proceeding headings. There is no IPRxxxxxxxx to report here. Two things worth distinguishing, because they look like PTAB activity in raw search output but are not:

• The "Cited By (21)" / "Families Citing this family" lists on the Google Patents page are later patents that cite 8989820 as prior art (e.g., US 8,880,125 to Cellco Partnership; US 8,914,767 to Symantec; the Allstate 10,604,013 family; the NetraDyne 11,453,365 family). A citation is not a challenge. No IPR petitioner is named anywhere in that data.
• US 2012/0115413 A1 / application 13/244,534 is this patent's own parent (Continuation-in-Part relationship, priority 2010-11-10), not a third-party proceeding.

Searches for "IPComm" or inventor-name-keyed PTAB filings ("Czaja", "Stawski", "Afsar", "Yi" combined with IPR docket patterns) returned nothing. I also found no district court litigation asserting 8989820. I could not query PTAB E2E or CourtListener dockets directly in this session, so if you need a belt-and-suspenders check, run the patent number against PTAB E2E and Docket Navigator / CourtListener's RECAP docket search — but the ODP canonical record and every public source I could reach agree: no AIA trial activity, no appeal.

Strategic summary

Claim status. Every claim — independent claims 1, 4, 10, and 11, and dependent claims 2, 3, 5, 6, 7, 8, and 9 — is UNTESTED. Not one claim has been canceled or held patentable in an AIA trial, because no trial was ever instituted. The full claim set (11 claims) as granted on 2015-03-24 is the same claim set that exists today. Contrast that with the usual "hardened patent" narrative: there is no FWD to quote, no claim-level disposition, and no PTAB paper trail to mine for prosecution-style admissions.

Enforceability. The maintenance-fee lapse is the decisive fact. Under 35 U.S.C. § 41 and 37 CFR 1.362, a patent for which the maintenance fee is not paid in the grace period expires, and the patentee cannot recover damages for infringement occurring after expiration. Note that the 4th-year fee was paid (2018-12-07, with a late-payment surcharge), the reminder for the next fee was mailed 2022-11-14, and the lapse was declared in 2023. Revival avenues exist in principle under 37 CFR 1.378, but for unintentional delay the petition-and-fee window is time-limited, and on these dates it appears long closed. Treat the patent as expired, but confirm the revival-window math with counsel before you stake a motion on it — I have not verified the statute-of-limitations interaction for the pre-lapse six-year lookback (§ 286), which is the only residual exposure theory.

Estoppel landscape. There is no § 315(e)(2) estoppel on anyone. Estoppel attaches only to a petitioner, a real party in interest, or a privy that lost at final written decision — and there is no petitioner and no FWD here. Practically: every prior-art ground remains fully available to any defendant, including grounds that would be IPR-barred by § 311(b) if a petition had ever been filed. The most obvious candidates are the references already on the face of the patent: US 2010/0197351 (Mobile Communication Technologies), US 2010/0216509 and US 2012/0289217 (ZoomSafer, "Safety features for portable electronic device"), US 8,428,973 (USAA, "automatically disabling mobile device usage while driving"), and US 2012/0040665 / US 8,401,589 (AT&T, "Controlled text-based communication on mobile devices"). Those are examiner-cited art, which cuts both ways — but with no IPR estoppel, they can be re-asserted in a § 282 invalidity case or, if the patent were ever revised/revived and asserted, in a new IPR.

Pattern signals. No repeat petitioners, no defensive aggregator (no Unified Patents involvement), no PTAB appeal practice by the patent owner. The patent is held by IPComm (assigned 2012-10-15; inventors Czaja, Stawski, Afsar, Yi) — a small licensing entity with no litigation footprint on this patent that I could find. The patent's own citation network is the more interesting signal: it was cited by Cellco, Symantec, Allstate, and NetraDyne, i.e. the industry built on top of it, while the patentee itself appears to have monetized nothing. That combination — zero assertions, zero PTAB trials, expired for non-payment — is the signature of an unexercised asset, not a troll's war chest.

Recommended next steps

• Lead with expiration, not invalidity. If a demand letter on 8989820 crosses your desk, the immediate response is that the patent lapsed for non-payment of maintenance fees effective 2023-03-24 and cannot support prospective relief or post-lapse damages. Cite the legal-events record on the Google Patents page (https://patents.google.com/patent/US8989820/en) and pull the USPTO PatentCenter maintenance-fee history to confirm the fee and lapse dates against the primary record.
• Check revival before you rely on it. Pull PatentCenter and confirm whether any petition under 37 CFR 1.378 was filed and granted. If none, and the revival window is closed, the expiration defense is essentially dispositive as to forward-looking infringement and injunctive relief. Do not over-assert the window calculation without verifying it.
• Isolate the residual lookback exposure. The only live theory is back-damages under § 286 for pre-lapse conduct. Scope that with the client: any accused product, when it launched relative to 2023-03-24, and whether notice under § 287 was ever given (marking/no marking matters here).
• No PTAB strategy is available or needed. Because no IPR was filed, there is no 1-year § 315(b) bar date from service of a complaint (no complaint found), no institution deadline, and no statutory trial deadline to track. If the patent were somehow revived and asserted, a petitioner would be starting from a blank slate with no estoppel — and would face the ordinary § 315(b) one-year clock running from service.
• Sanity-check the negative. Before finalizing a defense position, run the patent number through PTAB E2E (https://ptab.uspto.gov) and CourtListener/RECAP. My conclusion of "zero proceedings" rests on the ODP feed plus public search, and PTAB filings do sometimes lag indexed databases — but here the expiration postdates any plausible filing window, so the risk that a live proceeding is hiding is low.

I'll research the assignment chain for US 8,989,820, starting with the USPTO Assignment Center record and cross-referencing IPComm's corporate status.

Let me dig into IPComm's corporate identity, the correspondent of record, and any litigation activity.

Let me look for the assignment correspondent of record and IPComm's broader litigation footprint.

Assignment Chain Analysis — US 8,989,820 B2

Tool-budget note: I exhausted my allotted searches mid-investigation. The record below is grounded in the authoritative patent text (Google Patents legal-events block, fetched 2026-09-24) plus the docket/company material I did retrieve. One element the USPTO record normally exposes — the correspondent attorney of record on the assignment — I could not retrieve, and I flag it as a gap rather than guess. See "Limitations" at the end.

---

Inventors

Unusual-pattern check: The "all inventors departing the original assignee within 12 months" fire-sale precursor is not observable — three of four inventors are IPComm insiders who did not leave (they remain on later IPComm filings), and I have no departure data for Yi. The genuinely unusual datum is mixed provenance: an LG-linked standards executive listed alongside the IPComm founder/inventor core. I could not determine how Yi's contribution arose (consulting, prior employment, joint development) — that would require the assignment's supporting documents, which the reel/frame abstract does not contain.

---

Original assignee

IPCOMM (recorded grantee; the litigation plaintiff appears as IPCOMM, LLC), Cardiff by the Sea, CA (806 Ocean Crest, Cardiff, CA 92007).

• Primary line of business: A small communications-technology firm (founded ~2004), variously described as offering VoIP/unified-communications/video-conferencing and network-infrastructure solutions. Caveat: the business description and financials (~23 employees, ~$5.5M revenue) come from an algorithmic aggregator (Kona Equity) and are explicitly self-described as estimates — treat as directional only.
• Did they ship a product embodying these claims? Not demonstrated. I found no evidence of a commercial safe-driving-compliance product. IPComm's disclosed product/patent activity skews to a mixed portfolio (adaptive ski bindings US 8,990,048; skiing analytics US 8,612,181; medication compliance; mobile femto-cell; emergency SMS). The '820 patent reads as a portfolio holding, not a product-mirroring filing.
• Current status: No bankruptcy, dissolution, or acquisition record surfaced. The company appears to persist as a patent-holding/assertion vehicle — it is a plaintiff in S.D. Cal. patent suits (see NPE signals). The '820 patent itself was allowed to lapse for non-payment of maintenance fees (effective 2023-03-24).

---

Assignment timeline

The Assignment Center record for this patent contains exactly one recorded assignment — the original inventor-to-company transfer. There are no post-issuance assignments (no NPE transfer, no security interest, no merger/reorg).

• 2012-06-14 (executed / stated effective date) / recorded 2012-10-15 — Reel 029131/0173
  • Conveyance: Assignment — "ASSIGNMENT OF ASSIGNORS INTEREST"
  • Assignor: Czaja, Stanislaw; Stawski, Ilona; Afsar, Muhammad; Yi, Byung K.
  • Assignee: IPCOMM (IPComm LLC), Cardiff, CA
  • Correspondent: Not retrievable from my sources. Google Patents' legal-events block exposes only the reel/frame and the conveyance text, not the recording correspondent. I did not find the attorney of record. Because the "repeat correspondent" signal depends entirely on this field, it is scored unclear below rather than absent.
  • Context: Initial inventor→company assignment, executed contemporaneously with filing (the effective date equals the 2012-06-14 filing date of application 13/523,693). Not an acquisition, fire-sale, or securitization.

Supporting legal events (Google Patents), all fee-related after the assignment: STCF grant (2015), FEPP maintenance reminder (2018-11-12), MAFP 4th-year fee paid (2018-12-07), FEPP reminder (2022-11-14), LAPS/STCH lapse 2023-05-01 (effective 2023-03-24), FP lapsed (2023-05-23). No subsequent AS/reassignment entry.

Because the chain is a single internal assignment, the ownership of US 8,989,820 never left IPComm from its 2012 execution through the 2023 lapse.

---

Timeline diagram

timeline
    title Ownership of US 8989820
    2010 : Provisional priority filed
    2011 : Parent application filed
    2012 : CIP application filed
         : Assigned to IPCOMM reel 029131 0173
    2015 : Patent issued
    2023 : Lapsed for unpaid maintenance fee

---

NPE / troll-pattern signals

---

Verdict

Insufficient data — for the ownership chain specifically.

The assignment record consists of a single link, Reel 029131/0173 (executed 2012-06-14, recorded 2012-10-15), conveying the four inventors' interests to IPCOMM. There are no post-issuance transfers, no shell-entity hop, no cascading LLCs, and no defensive-aggregator terminus — so none of the eight transfer-based NPE signals is present as a chain phenomenon. The patent simply stayed with its original assignee and then lapsed for non-payment of maintenance fees effective 2023-03-24.

Two honest caveats, stated plainly rather than dressed up as findings:

1. Entity-level (not chain-level) flag: The assignee, IPComm, LLC, is a serial patent plaintiff in S.D. Cal. against parties outside its apparent communications line of business (a mining-technology company; a ski-equipment company). That is asserter-behavior by the patent owner — but it is not an NPE transfer signal under any of the eight defined criteria, and critically, the '820 patent has never been asserted in the cases I found. I am not converting this into an "NPE" chain verdict.
2. Data gap: I could not obtain the assignment's correspondent of record, so Signal 3 is unresolved. If the same attorney/firm filed recordings across the broader IPComm portfolio, that would be worth checking — but I have no basis to assert it.

Because the definition of "Operating-company assertion" requires the current assignee to both ship products embodying the claims and sue actual competitors, and neither is established for the '820 claims, and because "Defensive/non-asserting" requires a defensive-aggregator terminus that does not exist, Insufficient data is the only supportable verdict.

Verify directly at: https://assignmentcenter.uspto.gov/ — search 8989820 (or application 13/523,693); mirrors at https://assignment.uspto.gov/patent/index.html. Pull the full reel 029131/0173 abstract to recover the correspondent, which is the missing field here.

---

Limitations & confidence

• High confidence: only one recorded assignment; reel 029131/0173; execution/recording dates; assignor/assignee names; lapse in 2023. All drawn from the authoritative patent text.
• Medium confidence: inventor addresses/employers and IPComm's business profile (aggregator-sourced, estimated).
• Low/uncertain: Byung K. Yi's employment at filing (inferred from Patent Leaderboard's LG grouping of his patent count — not independently confirmed); the correspondent of record (not obtained); the "IPComm," "IPCOMM," and "IPCOMM, LLC" name variants — the recorded assignee and the litigation plaintiff are very likely the same entity, but I did not verify the LLC-formation chain. Do not treat these variants as confirmed-distinct or confirmed-identical entities without a corporate-records check.

I'll research the prior-art references cited on the face of US 8,989,820. Let me verify each citation and pull details.

Let me gather details on the remaining cited references.

Let me verify the remaining two citations (the Zoomsafer continuation publication and the AT&T application publication).

Prior-Art Analysis — US 8,989,820 B2

Scope note first. My tool could not open a native USPTO Patent Public Search / PatentCenter query window; the results I retrieved came from the authoritative full-text record of US 8,989,820 (Google Patents, fetched 2026‑09‑24, the text supplied to me) plus confirming lookups of each cited reference on Google Patents, FreePatentsOnline, and USPTO.report. I filtered to the exact number 8,989,820 and did not substitute look-alike numbers. Where I could not independently confirm a bibliographic field (e.g., an application serial number), I say so rather than guessing.

Because the '820 patent's effective filing/priority date is 2010‑11‑10 — before the AIA first‑to‑file provisions took effect on 2013‑03‑16 — the pre‑AIA versions of 35 U.S.C. § 102(a), (b), and (e) govern. That matters below, because two of the six references were published after the priority date but were filed before it, so they are § 102(e) art as of their filing dates.

---

1. The two citation lists — a discrepancy to flag

The record lists the cited art twice, inconsistently:

• A "Citations (4)" block: US20100197351A1, US20100216509A1, US20120040665A1, US8428973B1
• A "Patent Citations (6)" block: US20100197351A1, US20100216509A1, US20120289217A1, US8428973B1, US20120040665A1, US8401589B2

The two "extra" entries in the six-item list are family/duplicate members of references already present, not independent art:

• US20120289217A1 is a later Zoomsafer continuation publication of the same 2005‑09‑26 family as US20100216509A1.
• US8401589B2 is the granted patent corresponding to the AT&T application US20120040665A1 (same appl. no. 12/853,788).

So there are effectively four distinct prior-art families cited. I report all six as recorded, literally.

A second, minor point: these references are "cited by" the '820 examiner/third parties, not references the '820 patent itself cites out to. The 10 "Cited By" entries and 25 "Families Citing this family" entries are later documents that cite the '820 patent — they are not prior art to '820 and I exclude them.

---

2. The six references of record

---

3. Per-reference § 102 analysis

Rule applied: a single reference anticipates a claim under § 102 only if it discloses every limitation of that claim, arranged as claimed. For dependent claims (2–3 from 1; 5–9 from 4), the reference must supply the independent claim's limitations plus the added limitation.

Reference 1 — US 2010/0197351 A1 (Mobile Communication Technologies)

• Ground: § 102(a)/§ 102(e) — published 2010‑08‑05, before the 2010‑11‑10 priority.
• Disclosures relevant to '820: a mobile communicator held in a disabled state unless conditions are satisfied; function sets including text messaging and voice; emergency calls always enabled. This maps to the suspension-of-communication concept and the emergency carve-out.
• What it lacks (fatal to anticipation): no QR code, no terms-and-conditions acceptance, no in‑vehicle "driver identification unit," no hands‑free association/override in the claimed sense, no channel-estimation velocity measurement, no accelerometer-based accident detection, no recipient/violation-report machinery.
• Potentially anticipates: nothing in full. Best read as § 102(a)/(e) background/obviousness art against the general disable-unless-condition premise of claim 1 and the emergency-exception aspect.

Reference 2 — US 2010/0216509 A1 (Zoomsafer)

• Ground: § 102(a)/§ 102(e) — published 2010‑08‑26, before the priority date.
• Disclosures relevant to '820: self-contained speed detection (GPS/speed-based), threshold comparison, blocking transmission and reception of voice and text when moving above the threshold, and hands‑free override to re‑enable voice. This is the closest single reference to the suspension-plus-hands-free-override kernel of claim 1.
• What it lacks: no QR code (or any vehicle-attached code carrying terms); no "driver identification unit"; no NFC/Bluetooth association to a vehicle's hands-free equipment as claimed; no channel-estimation velocity; no accelerometer accident detection; no violation reports to QR-named recipients; no promotional materials.
• Potentially anticipates: nothing in full. It is strong § 102(a)/(e)/§ 103 art for the "suspend voice/text while moving, unless hands-free" concept but cannot reach claim 1 because of the QR‑code/terms-and-conditions and driver‑ID‑unit limitations. It cannot reach dependent claim 2 (no accident detection) or claim 3 (no channel estimation).

Reference 3 — US 2012/0289217 A1 (Zoomsafer continuation)

• Ground: published 2012‑11‑15 — after the '820 priority and filing dates. On its face it is not § 102(a)/(b) art. It can only be § 102(e) art as of its actual U.S. filing date; because its substance appears in the earlier 2005 Zoomsafer priority document, it could in principle be accorded the 2005‑09‑26 date for that subject matter (the earlier publication, reference 2, already supplies that date).
• Disclosures: same family substance as reference 2, plus safe‑mode dashboards, priority calling/messaging, third‑party‑app "driving aware" APIs and auto‑reply/voice‑enhancement.
• What it lacks: identical gaps to reference 2 — no QR‑code terms/parameters, no driver‑ID unit, no channel‑estimation velocity, no accident detection by accelerometer.
• Potentially anticipates: nothing in full. At most cumulative § 102(e)/§ 103 art for the hands‑free-override and priority-message sub‑features. Flag: if the examiner relied on this as the anticipatory Zoomsafer reference rather than reference 2, the priority/§ 102(e) date issue is worth watching, since the publication post‑dates the '820 priority.

Reference 4 — US 8,428,973 B1 (USAA)

• Ground: § 102(e)(2) — U.S. patent filed 2009‑05‑29 (before the priority date), granted 2013‑04‑23.
• Disclosures relevant to '820: derives mobile-device speed from accelerometer output, compares to a threshold, and disables functionality above the threshold; insurance-premium linkage.
• What it lacks: no QR code; no terms-and-conditions acceptance; no in‑vehicle driver‑ID unit; no NFC/Bluetooth hands-free association; no channel-estimation velocity; and — importantly — its accelerometer use is for speed, not for detecting an accident/shock (claim 2's non‑periodic impact signature); no violation/accident SMS reports.
• Potentially anticipates: nothing in full. It is the most relevant reference to the accelerometer-sensing limitation folded into claim 11's step set, but claim 11 (and claim 2) require accident detection from instantaneous acceleration-vector change, which reference 4 does not disclose. It cannot anticipate claim 1 (no QR code).

Reference 5 — US 2012/0040665 A1 (AT&T)

• Ground: § 102(e)(1) — published 2012‑02‑16, filed 2010‑08‑10, before the priority date.
• Disclosures relevant to '820: determine the device is in a moving vehicle; determine it is positioned near the driver's seat using multiple in‑vehicle NFC transceivers; then disable text‑based services (device- or network‑side). This touches claim 1's NFC/"driver identification unit" concept, claim 7's NFC NFC-verification step, claim 10's NFC-capability parameter, and claim 11's NFC step.
• What it lacks (decisive): no QR code attached to the vehicle carrying terms-of-use/parameters; no confirmation of driver acceptance of terms; no hands-free Bluetooth association to vehicle equipment as the suspension override; no channel-estimation velocity; no accelerometer accident detection; no promotional-material and violation-reporting to QR‑named recipients. It uses location/time-block/NFC rather than the claimed channel-estimation velocity.
• Potentially anticipates: nothing in full. It is the best § 102(e) art for the NFC driver-proximity limitation and would be central to a § 103 combination, but missing the QR-code/terms-acceptance and channel-estimation limitations prevents anticipation of claims 1, 4, 7, 10, and 11.

Reference 6 — US 8,401,589 B2 (AT&T)

• Ground: § 102(e)(2) — granted patent, filed 2010‑08‑10 (appl. no. 12/853,788), before the priority date.
• Disclosures/lacks: same family and same disclosure as reference 5. It is the granted counterpart of US2012/0040665A1.
• Potentially anticipates: nothing in full, for exactly the reasons stated for reference 5. Treat references 5 and 6 as one art unit; do not double-count them as separate teachings.

---

4. Limitation-by-reference coverage matrix

(✓ = disclosed; ~ = partially/equivalently disclosed; ✗ = absent)

---

5. Conclusion on anticipation

• No cited reference, alone, anticipates any claim of US 8,989,820. Every independent claim (1, 4, 10, 11) requires a QR code assigned/attached to the vehicle and containing terms/parameters, plus (for claim 1) driver acceptance via the UI — a limitation entirely absent from all six references. Because claims 2–3 depend from claim 1 and claims 5–9 depend from claim 4, none of those dependent claims is anticipated either.
• The references are properly characterized as § 102(a)/(e) background art and § 103 combination art, mapping to isolated limitations as shown in the matrix:
  • Zoomsafer (refs 2–3) → speed-threshold suspension + hands‑free override (the claim‑1 kernel).
  • AT&T (refs 5–6) → NFC-based driver-seat proximity detection + feature disabling.
  • USAA (ref 4) → accelerometer-derived speed and functionality disablement.
  • Mobile Communication Technologies (ref 1) → default‑disabled communicator with an emergency-call exception.
• The claimed channel-estimation velocity (claims 1, 3, 11) and the accelerometer shock/accident detection with SMS reporting (claims 2, 6, 11) are not disclosed by any of the six references. Those, together with the QR‑code terms-and-conditions/parameter ingestion, are the features that most plausibly carried the '820 claims to allowance over this art.

---

6. Caveats and things a fuller search should add

1. Native-database confirmation needed. I could not run a direct USPTO Patent Public Search or PACER/PTAB query. For a definitive "art of record" check, pull the '820 file wrapper (Image File Wrapper) to see which of these six were applied in § 102 vs § 103 rejections and with what claim mappings; the "Patent Citations" list alone does not tell you how the examiner used each.
2. Application serial numbers for references 1–4 were not returned by my searches; I therefore give priority/filing dates only for those and am not asserting serial numbers.
3. § 102(e) date sensitivity. References 3 (US2012/0289217A1) and 5/6 (AT&T) published after the '820 priority date. Reference 3 in particular is only prior art if given its 2005‑09‑26 Zoomsafer priority (its own filing post‑dates the '820 priority); references 5/6 rely on their 2010‑08‑10 filing date. If an earlier invention date than 2010‑11‑10 could be sworn to, the § 102(e) status of any of these would need re‑examination.
4. Not prior art: the "Cited By" and "Families Citing this family" lists (e.g., Secure4Drive US2016/0150070; Allstate US10,604,013; Loralee Hajdu US10,841,248; NetraDyne US11,453,365) are later documents citing '820 and must not be treated as '820 prior art.
5. Related-but-uncited material: the '820 patent is a CIP of Ser. No. 13/244,534 (US 2012/0115413 A1), which shares inventors and is not "by another," so it is not § 102 art — but if you are mapping the family, note the '413 publication is the sibling, not a citation.
6. Confidence: Citations, dates, titles, and assignees above are drawn from the authoritative patent text and corroborating patent-office-derived pages — high confidence. The anticipation conclusions are analytical and carry the usual caveat that claim construction (especially of "driver identification unit," "channel estimation function," and "safe driving compliance application") could shift the § 102 boundary. Where a reference post-dates the priority date, I flagged the qualifying-date question rather than assuming § 102(e) applies.

I'll ground the obviousness analysis by pulling details on each cited prior-art reference.

Obviousness Analysis — US 8,989,820 B2 under 35 U.S.C. § 103

Scope note: Per the task, I am working from the "Patent Citations (6)" list on the patent page as the prior-art set. That list contains four distinct references (two appear as application/grant pairs). I retrieved abstracts, summaries, and family data for each; I did not verify paragraph-level text of every reference, so the element mappings below are based on the retrieved disclosures and the examiner's own citations. A formal contention would require pin cites I have not personally confirmed.

---

1. The prior-art set

Prior-art status. All four predate, as U.S. filings/publications, the '820's earliest claimed priority date of 2010‑11‑10 (Prov. 61/412,075). [ZOOM‑1] (2010‑08‑05) and [MCT] (2010‑08‑05) published before that date; [USAA] was filed 2009‑05‑29; [ATT‑1] has a 2010‑08‑10 priority and published 2012‑02‑16. Accordingly they qualify as prior art under pre‑AIA § 102(e) (and § 102(a) for the two 2010 publications) regardless of how the CIP priority question resolves — which matters, because the QR‑code/NFC/train subject matter appears to be new matter added in the 2012‑06‑14 CIP.

A note on the priority date: Claims 1, 4, 10 and 11 all recite QR‑code content that is not in the 2010 provisional. If the claims are entitled only to the 2012‑06‑14 CIP date for that subject matter, even more art becomes available (e.g., US 8,914,767 B2, filed 2012‑03‑12, "using quick response codes to activate software applications" — appearing on this page's "Families Citing" table, not in the cited set). This cuts against the patentee.

---

2. Legal framework and POSITA

Under Graham v. John Deere and KSR Int'l v. Teleflex, the inquiry is the scope/content of the prior art, the differences from the claims, PHOSITA's level of skill, and objective indicia. KSR permits combination of references where there is a known problem, a market demand, or a "finite number of identified, predictable solutions," and permits use of "a known technique to improve similar devices in the same way."

POSITA here: a B.S. in electrical/computer engineering (or equivalent), plus ~2–3 years' experience in wireless mobile terminals/cellular protocol stacks or automotive telematics, including familiarity with smartphone sensors (accelerometers), short-range radios (Bluetooth, NFC), and cellular modem channel estimation.

Primary reference: [ZOOM‑1], because it alone discloses the core claimed function — automatically detecting driving and suspending transmission and reception of text/voice, with a hands-free override and a managed safety policy. [USAA] and [MCT] are strong secondary/primary alternatives for the speed‑threshold‑driven disabling.

---

3. Claim-by-claim analysis

Claim 1 (independent — system)

Conclusion: Claim 1 is the aggregation of known elements, each performing its known function, with no asserted unexpected synergy. Strong § 103 case, subject to the QR element (§4).

Claim 2 (accident detection via instantaneous accelerometer change)

[USAA] expressly derives speed from accelerometer output data. Impact/crash detection from a non‑periodic acceleration spike is a long‑known technique (airbag crash sensors; accelerometer‑based crash detection). Motivation: [USAA]'s insurance context creates an incentive to capture crash data; [ZOOM‑1]'s contact‑notification framework supplies the reporting path. Obvious.

Claim 3 (velocity via channel estimation)

Channel estimation is an existing, standard output of every cellular modem (the '820 specification itself admits "estimates of such distortion are essential to the operation of the BS and each mobile terminal"). Using Doppler shift, proportional to velocity, as a speed source is the "known technique... same way" case of KSR. Motivation: no added hardware; same result as GPS/accelerometer speed. Obvious — though this is the second‑weakest element after the QR code.

Claim 4 (embed vehicle info in QR: type, hands‑free cap., NFC cap., terms‑of‑use, violation contacts, promotions)

• Vehicle type / capability fields: [ATT‑1] discloses in‑vehicle NFC infrastructure and by implication vehicle configuration; [MCT] discloses an in‑vehicle unit the phone must "associate" with.
• Hands‑free and NFC capability data: [ZOOM‑2] (hands‑free equipment), [ATT‑1] (NFC transceivers).
• Terms‑of‑use & violation contacts: [ZOOM‑1]/[ZOOM‑2] administrator‑managed safety policy and contact notification; [USAA] insurance contacts.
• Promotional materials: [ZOOM‑2]'s ZoomPush pushes promotional/celebrity content to the device triggered by driving events; [USAA] insurance‑discount incentives.

Motivation to combine: fleet/rental/insurer management — auto‑configuring the app from a vehicle‑borne code is a labor‑saving, predictable implementation choice (encode known configuration data in a known machine‑readable carrier). Obvious.

Claim 5 (terms include insurance contract refs, operating restrictions, laws)

[USAA] is affirmatively about insurance risk pricing and state cell‑phone laws; [ZOOM‑1] about administrator‑set operating restrictions; the '820's own Background acknowledges the law in most states. Obvious.

Claim 6 (accident → SMS to recipients + capture speed, location, shock intensity, driver & hands‑free status, store)

[ZOOM‑1]/[ZOOM‑2] notify contacts/administrators by SMS/email when safe mode engages; [USAA] gives accelerometer‑derived speed; [ATT‑1]/[ZOOM‑1] give location (GPS); [MCT] gives the emergency‑provider messaging path. Combining these is a predictable, field‑consistent aggregation. Obvious.

Claim 7 (after scan: NFC to verify driver status, Bluetooth for hands‑free, report to network)

This is the cleanest two‑reference combination in the set. [ATT‑1] teaches exactly: NFC transceivers in the vehicle → determine driver's‑seat position → transmit a service activation report to a server on the cellular network which disables features. [ZOOM‑1]/[ZOOM‑2] teach that a hands‑free (Bluetooth) device association overrides the blocking function. The claims' "NFC for driver status + Bluetooth for hands‑free + report to network" is a literal amalgam of these two. Obvious.

Claim 8 (violation determination + SMS to QR‑named recipients + log time/location)

[ZOOM‑1] detects and can notify on blocked/attempted use; [ZOOM‑2] logs driving events for a dashboard/policy; [USAA] collects driving data for insurance purposes. Reporting violations to insurer/fleet contacts follows directly. Obvious.

Claim 9 (present promotions only when not in motion / not the active operator)

[ZOOM‑2]'s ZoomPush already gates content delivery on driving triggers and safe‑mode state, and [ZOOM‑1] suppresses alerts during safe mode. Withholding advertising from an active driver is a predictable, safety‑consistent timing rule. Obvious.

Claim 10 (parameter set — vehicle type, HF cap., NFC cap., terms, emergency/insurance contacts — driving suspension)

Same combination as claims 1 and 4: [ATT‑1] (NFC, moving vehicle, driver‑seat, network suspension) + [USAA] (accelerometer speed, insurance contacts) + [ZOOM‑1] (policy/contacts, hands‑free). Obvious.

Claim 11 (non‑transitory medium performing all steps)

Aggregation of the above; no separate inventive weight. Obvious.

---

4. Where the § 103 case is weakest (candor)

Two elements are not squarely taught by the six cited documents:

1. The QR code carrying terms and conditions + scanned acceptance (claims 1, 4, 5, 8, 10, 11). The cited art uses NFC/BLUETOOTH association (ATT‑1, ZOOM) or ignition‑based vehicle links (USAA) for device‑to‑vehicle registration — not an optical tag. A § 103 case here must rest on: (i) QR/barcode scanning being notoriously well‑known and the spec treating the code as a mere data carrier; (ii) KSR reasoning that substituting one known data‑transfer medium (an optical code) for another (NFC/Bluetooth association) to deliver the same configuration data is an obvious, predictable substitution with no new result; and/or (iii) art outside the cited set (e.g., US 8,914,767 B2, which is on this page's forward‑citation table but is only pre‑CIP‑date art, not pre‑provisional art). This is the strongest non‑obviousness argument the patentee could make.

2. Velocity from the smartphone's channel‑estimation/Doppler output (claim 3, and part of 1/10/11). The cited art derives speed from GPS, accelerometer, or network, not from the modem's Doppler estimate. But the '820 specification itself concedes channel estimation is a standard, always‑present function, so using it as a speed sensor is a classic "known capability, new use" case under KSR.

If a factfinder accepted the patentee's arguments on both points, claim 3 could survive in isolation (it depends from claim 1, so it falls if claim 1 falls). The QR element, however, is present in every independent claim, so all independent claims rise or fall on the QR‑code argument — an aggressive but not implausible non‑obviousness position built on the specificity of the QR data content and the explicit acceptance step.

---

5. Consolidated motivations to combine (§ 103 "articulated reasoning")

1. Same field, same problem. All six references address driver distraction from mobile‑device use in a moving vehicle — the KSR "common problem" factor. [ZOOM‑1] even frames its invention as an improvement over "[s]olutions... which disable or turn off a mobile device when it is detected that the mobile device is traveling at a certain speed" — i.e., over [MCT]/[USAA]‑type art.
2. The references cite each other. [ZOOM‑1]/[ZOOM‑2] expressly discuss US 7,590,405 (the [MCT] family) and hands‑free overrides; the '820 examiner cited all four. Mutual citation is recognized evidence that a POSITA would look to the group.
3. Complementary, non‑overlapping teachings. [ATT‑1] supplies driver‑vs‑passenger discrimination (the very gap [ZOOM‑1] identifies as "a primary problem"); [ZOOM‑1]/[ZOOM‑2] supply the hands‑free override and administrator‑managed policy; [USAA] supplies accelerometer‑based speed and the insurer/fleet incentive; [MCT] supplies emergency‑exception disabling of both TX and RX. Together they cover the claim elements with no gap requiring invention.
4. Market/regulatory demand. State cell‑phone‑while‑driving laws and insurer risk pricing ([USAA]) created strong pressure for a compliance‑monitoring solution — a recognized KSR motivation.
5. Predictability / reasonable expectation of success. Every added element is software logic on a smartphone (or a server) using sensors and radios already present; no unproven technology is required.

---

6. Objective indicia

• No evidence of unexpected results appears in the record; the claims recite aggregations of known functions.
• No litigation or licensing record could be tied to the '820 (consistent with the earlier sections of this analysis). The patent lapsed for non‑payment of maintenance fees effective 2023‑03‑24, which is at least consistent with limited commercial value — although lapse is legally irrelevant to § 103 and should not be treated as an objective indicium.
• The long gap between the 2005–2009 priority dates of the [ZOOM]/[MCT]/[USAA] references and the '820's 2010–2012 filings reinforces that the underlying concepts were mature, well‑explored art — which favors obviousness.

---

7. Bottom line

• Strong § 103 rejection: claims 1, 2, 6, 7, 8, 9, 10, 11 — combinations of [ZOOM‑1] + [ATT‑1] + [USAA] + [MCT], with two‑reference cores ([ZOOM‑1] + [ATT‑1] for claim 7; [USAA] + [ZOOM‑1] for claim 6).
• Moderate: claims 4 and 5 — depend on the QR‑carrier element; strong on the content of the data, weaker on the carrier.
• Weakest: claim 3 (channel‑estimation velocity) and, independently, the QR‑code terms‑and‑conditions element present in every independent claim. If the patentee has any non‑obviousness argument, it lives there.

Caveat: These conclusions rest on the abstracts and summaries retrieved (Google Patents, FPO, patentsencyclopedia, USPTO PTAB filings) plus the examiner's citation record. I have not verified the references at paragraph level, and I explicitly flag that the QR‑code limitation is not clearly disclosed in the six cited references — an honest gap in the record rather than a fabricated teaching.