US 6608554

I'll verify this patent against live sources before summarizing.

Let me check specifically for litigation and any 2026 appellate activity involving this patent family.

US 6,608,554 B2 — Verified Summary

Important scope note up front: I was able to verify the bibliographic and claim data below against the full Google Patents text of US6608554 (fetched 2026-09-30) and against cross-references in uspto.report, FreePatentsOnline, and Justia. I found no CAFC 2026 docket (no "2026-XXXX" Federal Circuit appeal number) involving US 6,608,554. I cannot rule one out — I do not have direct access to the CAFC docket system or PACER, and my searches returned only unrelated 2026 appeals (Headwater/Verizon 26-1884, Contour IP v. GoPro 2026-2012, Spero v. Mercedes-Benz/VW 2025-1064 et al.). Treat "no 2026 CAFC activity" as a search result, not an authoritative docket check.

Also note: I searched for the exact number 6608554. One incidental hit was NL6608554A (a 1966 IBM "record card verifying machine" — an unrelated Dutch publication that shares the numeral string). It is not related to the US patent.

Bibliographic Data

Continuity chain (as stated in the patent's Related Applications section): 10/007,032 is a continuation of 09/569,995 (now US 6,411,203), which is a continuation of 08/907,861 (now US 6,064,299), which is a continuation-in-part of 08/594,255 (now US 6,111,524), which is a continuation-in-part of 08/554,907 (abandoned). The patent notes that the claims were broadened in this continuation from "heavy duty vehicle" to "vehicle" generically.

Abstract (verbatim)

"An apparatus and methods are provided for data communications associated with a heavy duty vehicle. The apparatus preferably includes at least one electronic subsystem associated with the heavy duty vehicle and a plurality of electrical conductors connected to the at least one electronic subsystem and associated with the heavy duty vehicle. A vehicle data communications protocol converter is preferably connected to the plurality of electrical conductors for converting a first data communications protocol associated with data communications along the plurality of electrical conductors to a second data communications protocol such as an infrared or an RF data communications protocol. The apparatus also preferably includes a transceiver connected to the data communications protocol converter for transmitting the second data communications protocol from the heavy duty vehicle and receiving the data communications protocol from a remote data communications terminal."

(Note the abstract still says "heavy duty vehicle" while the claims recite "vehicle.")

Plain-Language Overview of the Three Independent Claims

Claim 1 — Apparatus, vehicle-side + remote terminal (the broadest apparatus claim).
An in-vehicle data communication apparatus with five pieces:

1. at least one vehicle electronic subsystem tied to vehicle operation (e.g., ABS);
2. electrical conductors connected to that subsystem;
3. a connector attached to those conductors and located inside the vehicle;
4. a protocol converter that translates the vehicle's native bus protocol into a second, over-the-air-friendly protocol; and
5. a first transceiver at the connector that sends/receives that converted protocol, plus a remote terminal with a matching second transceiver.
   The two ends talk to each other in the converted protocol. In plain terms: tap the truck's data bus at a connector, convert the vehicle protocol to something wireless, and exchange data wirelessly with a remote computer.

Claim 11 — Apparatus, vehicle-side only (no remote terminal required).
An apparatus with (a) vehicle electrical conductors, (b) a protocol converter, and (c) a transceiver connected to the converter that transmits the second protocol off-vehicle and receives it back from a remote terminal that is "not connected to the vehicle." This claim is notable because it expressly disclaims a physical/wired connection to the remote terminal — i.e., pure through-the-air communication.

Claim 24 — Method.
Two steps: (1) convert a first vehicle data communications protocol carried on vehicle electrical conductors into a second protocol; and (2) transmit that second protocol from the vehicle to a remote terminal not connected to the vehicle. The method claims frame the invention as the act of protocol conversion plus over-the-air transmission.

Notable dependencies worth flagging

• Claim 3 and claim 18/22: the second protocol uses only the physical layer of the first and second transceivers, "and not a data link layer," to simplify coding/conversion. This is a recurring narrow point across the family.
• Claim 5: the connector is a six-pin connector, and the second connector portion defines the transceiver housing.
• Claims 6, 32: first protocol is SAE J1708, J1939, or RS-485.
• Claims 10, 33: remote-side third protocol is RS-232, RS-422, or RS-423.
• Claims 19–20: transceiver mounted in a vehicle light housing, specifically a side-marker light housing (the "covert" installation aspect).
• Claim 17/21/29: RF-transceiver-specific variants.

Claim-drafting anomalies (taken literally, not corrected)

• Claim 13 reads: "An apparatus as defined in 12, further claim comprising a transceiver housing…" — the words "further claim" and the bare numeral "12" (no "claim") appear verbatim.
• Claim 18 recites "the second local-area data communications protocol," a term not introduced in claim 11 or 17 — the antecedent basis is inconsistent on its face.
• Claim 24 recites "from a vehicle," using the indefinite article rather than "the vehicle," which broadens the claim language.

Litigation and Post-Grant Status

Google Patents lists this patent in a family with litigation (Darts-IP family ID 27070730) and records U.S. district court cases in the Eastern District of Texas (6:09-cv-00157, 6:10-cv-00040, 6:10-cv-00327, 6:10-cv-00574, 6:11-cv-00497, 6:12-cv-00057) and the Eastern District of Michigan (2:12-cv-11024). These appear to be the Innovative Global Systems / Vehicle Enhancement Systems enforcement campaign of roughly 2009–2012.

A related family member, US 6,946,953 (a continuation-in-part of the 10/007,032 line), was the subject of IPR2020-00154, Zonar Systems, Inc. v. Innovative Global Systems, LLC — that proceeding also relied on US 6,064,299 and US 7,102,494 as exhibits. Note that IPR was against the '953 patent, not against the '554 patent.

Because 6,608,554 expired (adjusted expiration 2016-05-24), the practical likelihood of 2026 Federal Circuit appellate activity on this specific patent is low — but that is an inference, not a verified docket fact.

Explicit Uncertainty Statement

• CAFC 2026 dockets: Not verified. I could not query the Federal Circuit docket directly, and no search returned a 2026 appeal naming patent 6,608,554 or captioned with Innovative Global Systems / Vehicle Enhancement Systems. Do not rely on this as a definitive "no pending appeals" conclusion.
• Current assignee: Google Patents' own disclaimer states the assignee list "may be inaccurate" and that it performed no legal analysis. The multiple recorded assignments (Vehicle Enhancement Systems → VES-TEK → Vehicle Enhancement Systems (corrective) → Innovative Global Systems) should be confirmed against USPTO Assignment records rather than a patent aggregator.
• Litigation dispositions: I have case numbers only; I did not verify outcomes (settlement, dismissal, judgment) for any of the listed district court cases.
• Term/expiration: The 2016-05-24 "adjusted expiration" is Google's computed figure; I did not independently verify the PTA calculation or any terminal disclaimer effect (a terminal disclaimer is noted on related family members such as US 6,744,352 and US 10,127,556).

I'll research litigation involving US Patent 6608554 across patent litigation databases.

Let me dig into the specific case numbers listed for this patent and identify the parties.

Findings: Litigation involving US Patent 6,608,554

About the patent

• Patent: US 6,608,554 B2 — "Apparatus and method for data communication between vehicle and remote data communication terminal"
• Inventors: Alan Lesesky; Bobby Ray Weant
• Original assignee: Vehicle Enhancement Systems, Inc. (later VES-TEK, Inc., then Innovative Global Systems, LLC)
• Priority date: Nov. 9, 1995 | Filed: Nov. 8, 2001 | Granted: Aug. 19, 2003 | Status: Expired – Lifetime (adjusted expiration May 24, 2016)

Confirmed litigation

1. Innovative Global Systems LLC v. OnStar LLC

• Jurisdiction: U.S. District Court, Eastern District of Texas
• Case No.: 6:10-cv-00574
• Filed: Oct. 26, 2010
• Cause: Patent infringement
• Status/Outcome: Closed
• Source: PACER-derived docket entry (case title, filing date, cause, and "Closed" status confirmed), https://ai-lab-cl-prod.azurewebsites.net/case/dct/txed/6:10-cv-00574/innovative-global-systems-llc-v-onstar-llc

Additional cases the patent databases link to this patent's family (party names not verified in this search)

The Google Patents "Family has litigation" panel — sourced from Unified Patents Litigation Data and Darts-ip (family ID 27070730) — lists the following additional case numbers. I retrieved the case numbers and jurisdictions only; I was unable to independently confirm the plaintiff/defendant names, filing dates, or outcomes for these within this session, so I am flagging them as unverified:

Also listed: "First worldwide family litigation filed" (Darts-ip family 27070730): https://patents.darts-ip.com/?family=27070730

Important caveats

1. Family-based attribution. The Unified Patents / Darts-ip litigation data is keyed to the patent family (ID 27070730), which contains three members: US 6,064,299; US 6,411,203; and US 6,608,554. The "Family has litigation" listing therefore does not establish that each listed case asserted 6,608,554 specifically — the asserted patent could be a different family member. Only 6:10-cv-00574 was independently confirmed as a real infringement suit, and even there the specifically asserted patent number was not confirmed in the record I retrieved.
2. No PTAB/IPR proceedings against 6,608,554 itself surfaced in my searches. (An IPR I encountered, IPR2020-00154, concerned the related Lesesky patent US 6,946,953 — not 6,608,554 — so it is not counted here.)
3. Several similar but distinct patent numbers appeared in search results (e.g., US 6,946,953; US 6,411,203; US 6,064,299). Per your instruction, I have not folded results for those numbers into this answer except to explain the family relationship above.

Recommendation

For a complete, verified case list (parties, filing dates, and dispositions), the specific case numbers above should be pulled directly from PACER/RECAP or the Unified Patents caselist (https://portal.unifiedpatents.com/litigation/caselist), and the docket complaint in each should be checked to confirm that US 6,608,554 (as opposed to a sibling family member) was the patent-in-suit.

Would you like me to attempt direct docket lookups for the six unverified E.D. Tex./E.D. Mich. case numbers?

I'll start by checking the structured PTAB block (which reports no AIA trials) against web sources, since this patent has a notable litigation history.

The first search surfaced a different patent (US 10,469,554). Let me narrow to this patent and its owner.

A Federal Circuit appeal surfaced (Innovative Global Systems v. Motive Technologies, 21-2289, from an IPR). I need to pin down which patent and proceeding numbers.

PTAB / AIA Trial Landscape — US 6,608,554 B2

"Apparatus and method for data communication between vehicle and remote data communication terminal" (Lesesky & Weant; orig. assignee Vehicle Enhancement Systems, Inc.; current assignee of record on Google Patents: Innovative Global Systems LLC)

Proceedings overview

Zero AIA trial proceedings are on file against US 6,608,554. The canonical structured PTAB block supplied in this prompt (USPTO Open Data Portal) returns no IPR, PGR, or CBM naming this patent, and my independent web pass found no petition, institution decision, or Final Written Decision in which US 6,608,554 was the challenged patent — so the status breakdown is simply: active 0 / claims invalidated 0 / claims sustained 0 / settled 0 / institution denied 0, and all 33 claims of the '554 patent are UNTESTED at the PTAB. The bottom-line defensive posture is unusual and, for a defendant, more favorable than a hardened patent: this patent is not merely un-invalidated, it is a 1995-priority patent whose term already expired on 2016-05-24 (Google Patents legal status: "Expired – Lifetime," adjusted expiration 2016-05-24). There is no IPR to cite against it, but there is also no live term to infringe. The IPR risk in this family has been concentrated entirely in later, still-live Lesesky/IGS patents — most notably US 10,157,384, whose claims were all canceled at the Board and the cancellation affirmed by the Federal Circuit.

Critical number-collision warning: searches for "554" and "IPR" frequently surface US 10,469,554 — an unrelated video-streaming patent litigated in IPR2019-00231 and in Fintiv/§ 325(d) briefing involving Comcast/Rovi and fuboTV. That is not this patent. Do not let a "'554 IPR" reference in a demand letter or an opponent's brief be conflated with US 6,608,554.

Proceedings on US 6,608,554

None. There is no proceeding to report at claim-level granularity, and I will not manufacture a docket number to fill this section.

Verification caveats, stated plainly:

• The structured ODP block is the canonical source and reports no AIA trials for this patent. I have no basis to contradict it.
• My web verification was a limited first pass (I was cut off mid-search), so I cannot represent it as an exhaustive E2E/PTAB docket sweep. Confirm in USPTO PTAB E2E (https://ptacts.uspto.gov/ptacts/) by searching the patent number itself, not the family name.
• The Google Patents "Family has litigation" entries for this patent are district-court records (E.D. Tex. cases 6:09-cv-00157, 6:10-cv-00040, 6:10-cv-00327, 6:10-cv-00574, 6:11-cv-00497; E.D. Mich. 2:12-cv-11024), not PTAB trials.
• No defensive aggregator IPR (e.g., Unified Patents) appears in the chain for this patent. Unified Patents shows up only as the database hosting the litigation links, not as a petitioner.

Adjacent proceedings in the same family (NOT US 6,608,554) — context only

These matter because the '554 patent sits at the root of the Lesesky data-communication family, and a defendant evaluating this portfolio will be shown them by opposing counsel. Each is explicitly identified as challenging a different patent. Treat them as portfolio context, not authority against US 6,608,554.

IPR2020-00694 — Keep Truckin, Inc. v. Innovative Global Systems, LLC

• Type: Inter Partes Review
• Patent challenged: US 10,157,384 B2 (not the '554 patent)
• Filed: 2020-03-10
• Status: Final Written Decision issued — all challenged claims held unpatentable
• Judge panel: Administrative Patent Judges Justin T. Arbes, John F. Horvath, and Frederick C. Laney (Laney authored)
• Petition grounds: § 103(a). Claims 1–6, 10, 11, 14–20 over Skeen, Warkentin, and Transportation Regulations; claim 8 adding Murphy; claims 7 and 9 adding Berenz. Supported by the Andrews declaration.
• Institution decision: Instituted 2020-07-23 on all challenged claims and all grounds presented.
• Final Written Decision: 2021-07-21. Verdict, quoting the Board: "we determine that Petitioner has shown, by a preponderance of the evidence, that claims 1–11 and 14–20 are unpatentable." Every instituted claim — 1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 14, 15, 16, 17, 18, 19, and 20 — was canceled. The '384 patent has no surviving asserted claim from this trial. Patent Owner had filed a Response with declarations from Andrew D. Smith, William T. Brown, and Alan C. Lesesky himself (Ex. 2009); oral hearing was held 2021-04-22.
• Settlement / termination: None. Tried to FWD.
• Appeal: Yes — Innovative Global Systems, LLC v. Motive Technologies, Inc. (f/k/a Keep Truckin, Inc.), No. 21-2289 (Fed. Cir.), docketed 2021-09-08, per curiam (Lourie, Bryson, Hughes), judgment entered 2022-06-15: AFFIRMED under Fed. Cir. R. 36 (no precedential opinion). Judgment: https://www.courtlistener.com/opinion/[6477826](/patent/6477826)/innovative-global-systems-llc-v-motive-technologies-inc/
• Defensive value: Not a ground for attacking US 6,608,554, but powerful evidence of the family's institutional fragility — the Board and the Federal Circuit have already taken the name "Innovative Global Systems" off a materially similar Lesesky claim set. If IGS's demand letter is portfolio-wide, this FWD is your leverage.

IPR2020-00692 — Keep Truckin, Inc. v. Innovative Global Systems, LLC

• Type: Inter Partes Review
• Filed: 2020 (concurrently with -00694; described in the -00694 FWD as a "concurrently filed petition")
• Patent challenged: unverified in my searches — the -00694 FWD notes only that it "challenges several claims" of a related patent. I will not guess the number or the claims. Verify in PTAB E2E before relying on it.

IPR2020-00154 — IPR of US 6,946,953

• Type: Inter Partes Review
• Patent challenged: US 6,946,953 B2 ("Apparatus and method for enhanced data communications and control between a vehicle and a remote data communications terminal"; Lesesky & Weant; Vehicle Enhancement Systems) — a descendant in the same continuation chain that produced the '554 patent.
• Filed: on or about 2019-11-19 (per the petition exhibit set dated in the Docket Alarm record)
• Status / petitioner / outcome: not verified — my search was truncated before I could confirm the petitioner, institution decision, or FWD disposition. Do not treat this entry as a findings summary. The salient point is only that the family's mid-generation patent was petitioned while the '554 itself appears never to have been.

Strategic summary

Canceled vs. sustained vs. untested on US 6,608,554. Nothing is canceled; nothing is sustained; all 33 claims (1–33) are untested at the PTAB. That is not a hardening signal — it is mostly a timing signal. The '554 patent's term expired 2016-05-24, before the modern IPR wave reached this family (the family IPRs are 2019–2020 vintage, by which point the '554 was already dead). Petitioners rationally spent their IPR budget on the live descendants — US 10,157,384 (all claims canceled, affirmed) and US 6,946,953 — rather than on an expired patent. So the correct statement is: the patent is unimpeached at the Board because it is expired, not because it proved valid. All 33 claims — including the two independent apparatus claims (1 and 11, 1 being the cab-positioned-connector embodiment and 11 the converter-plus-transceiver embodiment) and the independent method claim 24 — remain legally presumptively valid under § 282 and untested. If a demand letter cites claims 1, 11, or 24, there is no FWD you can quote to kill them.

Estoppel landscape. § 315(e)(2) estoppel is patent-specific and claim-specific, so the IPR2020-00694 judgment estops Keep Truckin/Motive (and privies) only as to US 10,157,384, and only as to grounds raised or reasonably raisable there. No § 315(e)(2) estoppel touches US 6,608,554 at all, and no petitioner has been estopped on it. Practical consequence for a defendant today: every prior-art ground against the '554 claims remains fully available — in district court, in an ex parte reexam, or in your own IPR. You are not inheriting anyone's exhausted grounds, and you are not bound by any prior claim construction. The corollary is that if you file an IPR on the '554 and reach an FWD, you then carry § 315(e)(2) estoppel on that patent for the district-court case.

The bigger picture that outranks the estoppel analysis. This patent expired 2016-05-24. Under 35 U.S.C. § 286, recovery is limited to infringement committed within six years before the filing of the complaint, and there can be no infringing act after a patent's expiration. A complaint filed after 2022-05-24 therefore has no compensable damages window for US 6,608,554 — the six-year lookback reaches back only to 2016-05-24, the very day the term ended. Any assertion of this patent today is, at minimum, a damages dead end and likely a Rule 11 / § 285 exposure if pressed with knowledge of the expiration. Note also that the Google Patents expiration date is an assumption-based legal-status field; confirm the adjusted expiration against the face of the patent's § 154(b) notice and USPTO Patent Center before putting the expiration argument in a brief.

Pattern signals. (1) The same petitioner has hit this family more than once — Keep Truckin/Motive filed at least two IPRs (IPR2020-00692, IPR2020-00694) against IGS patents, and won completely on the one that reached FWD. (2) The patent owner fights and appeals: IGS appealed IPR2020-00694 to the Federal Circuit (No. 21-2289) and lost by Rule 36 affirmance on 2022-06-15 — no precedential law made, but it shows IGS litigates to judgment rather than settling cheaply. (3) The '554-era family was litigated hard in district court as early as 2009–2012 in E.D. Tex. and E.D. Mich., and again in D. Del. in 2019 (IGS v. Keep Truckin, No. 0:19-cv-00641-MN; IGS v. Samsara Networks, No. 0:19-cv-01708-MN, both re the '384 patent). (4) No defensive aggregator (Unified Patents or similar) has petitioned on this patent — every challenge in this family traces to commercial defendants, not to a public-interest filer. So there is no free, ready-made invalidity record you can adopt.

Recommended next steps

1. Identify the patent number in the demand letter before anything else. If it reads US 6,608,554, your lead argument is not invalidity — it is expiration and the § 286 time bar. Pull the § 154(b) term adjustment from the printed patent and USPTO Patent Center, confirm expiration 2016-05-24, and compute the six-year window from the complaint date. If the complaint postdates 2022-05-24, there is no recoverable infringement period.
2. There is no FWD to cite for this patent, and you should say so internally. The best available invalidity-side cite is the IPR2020-00694 Final Written Decision (2021-07-21) canceling claims 1–11 and 14–20 of US 10,157,384, affirmed at Innovative Global Systems, LLC v. Motive Technologies, Inc., No. 21-2289 (Fed. Cir. 2022-06-15) (https://www.courtlistener.com/opinion/6477826/innovative-global-systems-llc-v-motive-technologies-inc/). Use it for § 285 / Rule 11 / proportionality arguments on a portfolio-wide campaign, and quote the disposition exactly: "we determine that Petitioner has shown, by a preponderance of the evidence, that claims 1–11 and 14–20 are unpatentable." Do not represent it as a ruling on the '554 claims.
3. If you need an invalidity vehicle against the '554 itself, the available paths are (a) your own IPR — permissible even on an expired patent, though the practical payoff is limited by the damages analysis above, and it triggers § 315(e)(2) estoppel against you on this patent in the parallel case; (b) ex parte reexamination under § 302, which carries no estoppel and no § 315 time bar and is the cleaner tool for an expired patent; or (c) district-court § 102/§ 103/§ 112 defenses, which are entirely unencumbered by any petitioner's estoppel on this patent.
4. Watch for the still-live family members instead. The active threats in this portfolio are the descendants — US 10,157,384 (all challenged claims canceled, affirmed) and US 6,946,953 (IPR2020-00154; disposition unverified). If a new demand arrives, confirm which of these it asserts; that, not the '554, is where the IPR record actually helps you.
5. Verify the two open items in PTAB E2E before filing. (i) That no IPR/PGR/CBM against US 6,608,554 was filed in the window this search pass could not cover; (ii) the patent, claims, petitioner, and outcome of IPR2020-00692 and IPR2020-00154. Until those are confirmed, treat the "no proceedings" conclusion as the structured ODP position plus a partial web corroboration — well-supported, but not a belt-and-suspenders docket check.

Verification note: this analysis rests on the structured ODP block (canonical: no AIA trials) plus a web pass that was truncated mid-investigation. I have not fabricated any proceeding number, claim number, judge name, or disposition. Where a field is marked "unverified," that is deliberate — do not brief it until confirmed at USPTO PTAB E2E (https://ptacts.uspto.gov/ptacts/) or CourtListener (https://www.courtlistener.com/).

I'll research the assignment record for US 6608554 before drafting. Let me run several searches in parallel.

Let me dig deeper into the specific assignment records and litigation history.

Assignment Record Reconstruction — US 6,608,554 B2

Data-access note (important): I was unable to query USPTO Assignment Center directly in this session — it is a JavaScript application that was not retrievable, and my only tool was web search, which returned no indexed Assignment Center record pages for this patent. The assignment events below are taken from the patent's own Google Patents legal-events record (which mirrors the USPTO assignment dataset) and from the assignment text quoted on that page. Only one reel/frame number could be verified (008964/0397). I have left the other reel/frame fields explicitly marked as unverified rather than guess at them. Correspondent-of-record data for any recording was not retrievable. Verify at: https://assignmentcenter.uspto.gov/ (search patent number 6608554) and https://assignment.uspto.gov/patent/index.html.

Inventors

Residences are taken from the front page of related family member US 6,946,953 B2 (same two inventors, assignee Vehicle Enhancement Systems, Inc., Rock Hill, SC). VES's own corporate history states the company was founded in Rock Hill, SC in 1991 by Alan C. Lesesky, who had prior tenure at Freightliner, White Motor and Bendix; he remains President/CEO of VES and of Innovative Global Systems, LLC (VES website, ves-systems.com/about-us, fetched 2026-09-30).

Unusual patterns: Not present. This is not an inventor-departure fire-sale pattern — the opposite. Both inventors assigned to their employer VES, and the lead inventor is still the principal of both the operating company (VES) and the eventual IP-holding assignee (IGS) three decades later. There is no evidence either inventor left before the 2009 transfer. The relevant anomaly here is concentration of control, not attrition.

Original assignee

Vehicle Enhancement Systems, Inc. ("VES"), Rock Hill, South Carolina — named on the issued face of the patent (original assignee per Google Patents), and confirmed on the face of related family member US 6,946,953 B2 ("Assignee: Vehicle Enhancement Systems, Inc., Rock Hill, SC").

• Primary line of business: heavy-duty truck/trailer electronics R&D and engineering services — braking, lighting, instrumentation, and in-vehicle data communications (SAE J1708/J1939/J560 ecosystem). It is an engineering-services/R&D firm, not a volume OEM; its customers are described as "major OEM fleets, suppliers, government and industry agencies."
• Product embodying the claims: unclear. VES states it "has been contracted to develop, design, and prototype numerous electrical/electronic devices" and does prototype work, but I found no evidence of a commercially shipped product practicing the claimed over-the-air protocol-converting transceiver. I will not assert either way.
• Current status: operating. VES's website is live, states 30+ years in business, and notes a 2013 relocation within Rock Hill with a 9,000 sq. ft. warehouse. No bankruptcy, Chapter 7/11, or dissolution evidence found. Note the corporate history explicitly frames VES and IGS as coexisting entities.

Assignment timeline

Chronological, from the patent's legal-events record. Where the record did not disclose a reel/frame, I say so.

• 1995-11-09 (priority) — priority application Ser. No. 08/554,907 filed (abandoned); this patent claims priority through Ser. Nos. 08/594,255 → 08/907,861 → 09/569,995 → 10/007,032.

  • Conveyance: n/a (prosecution event, listed for chain context)
  • Assignor / Assignee: n/a
  • Correspondent: not disclosed
  • Context: initial filing.

• [execution date not disclosed] / recorded [date not disclosed] — Reel 008964/0397 (reel/frame recovered only indirectly — see below)

  • Conveyance: Assignment
  • Assignor: Lesesky, Alan; Weant, Bobby Ray (named literally in the record as "LESESKY, ALAN, WEANT, BOBBY")
  • Assignee: Vehicle Enhancement Systems, Inc.
  • Correspondent: not retrieved
  • Context: original inventor-to-employer assignment. This reel/frame is known only because the 2004-05-10 corrective filing on Google Patents explicitly references "PREVIOUSLY RECORDED ON REEL 008964 FRAME 0397." I could not independently confirm the execution or recording date, and reel 008964 is substantially later than the 1995 filing date — consistent with a re-recording or a later-recorded confirmatory assignment rather than the original 1995 recordation. Treat the date as unverified.

• 2002-12-02 (recorded) — Reel/frame not retrieved

  • Conveyance: Assignment ("ASSIGNMENT OF ASSIGNORS INTEREST (SEE DOCUMENT FOR DETAILS)")
  • Assignor: Vehicle Enhancement Systems, Inc.
  • Assignee: VES-TEK, INC.
  • Correspondent: not retrieved
  • Context: internal transfer/related-entity reorganization of the patent from the operating company to an affiliate, VES-TEK. I could not verify VES-TEK's corporate nature, purpose, or relationship to VES from any independent source; do not assume it is a licensing shell without further evidence.

• 2004-05-10 (recorded) — Reel/frame not retrieved (corrects Reel 008964/0397)

  • Conveyance: Correction ("CORRECTIVE ASSIGNMENT TO CORRECT ASSIGNOR NAME, PREVIOUSLY RECORDED ON REEL 008964 FRAME 0397")
  • Assignor: Lesesky, Alan; Weant, Bobby Ray
  • Assignee: VEHICLE ENHANCEMENT SYSTEMS, INC.
  • Correspondent: not retrieved
  • Context: administrative correction only — fixes the assignor name on the original inventor assignment; conveys no new interest.

• 2009-04-06 (recorded) — Reel/frame not retrieved

  • Conveyance: Assignment
  • Assignor: VES-TEK, INC.
  • Assignee: VEHICLE ENHANCEMENTS SYSTEMS, INC. (spelling reproduced literally from the record — note the extra "S" in "ENHANCEMENTS." This appears to be either a genuine separate entity or a recordation typo; the two spellings coexist in the chain and I have not auto-corrected it.)
  • Correspondent: not retrieved
  • Context: reverse consolidation — the patent is pulled back from the VES-TEK affiliate to the Vehicle Enhancement(s) Systems entity.

• 2009-04-06 (recorded) — Reel/frame not retrieved — same day as the entry above

  • Conveyance: Assignment
  • Assignor: VEHICLE ENHANCEMENT SYSTEMS, INC.
  • Assignee: INNOVATIVE GLOBAL SYSTEMS, LLC
  • Correspondent: not retrieved
  • Context: transfer to IP-holding/assertion vehicle. Per VES's own corporate history, "In 2008, Mr. Lesesky formed Innovative Global Systems, LLC … to create an IP holding company." The two 2009-04-06 recordings executed the same day (VES-TEK → VES, then VES → IGS) are a classic same-day clean-chain ladder. IGS remains the current assignee and is the named patent owner in the ensuing litigation.

• 2016-05-24 — legal status: expired (adjusted expiration from 20-year term + adjustments / terminal disclaimer effects); "Expired – Lifetime."

Note on timing relative to litigation: the Google Patents page lists E.D. Tex. filings beginning with case 6:09-cv-00157 (2009), then 6:10-cv-00040, 6:10-cv-00327, 6:10-cv-00574, 6:11-cv-00497, plus Michigan E.D. 2:12-cv-11024. The first of these is in the same calendar year as the 2009-04-06 IGS assignment. I could not retrieve the exact complaint filing date for 6:09-cv-00157, so I cannot confirm the "within 6 months" window — see signal 5 below.

Timeline diagram

timeline
    title Ownership of US 6608554
    1995 : Priority application filed by inventors
    2002 : Assigned to VES-TEK Inc
    2003 : Patent issued
    2004 : Corrective filing on inventor assignment
    2009 : Chain pulled back to VES Inc
         : Assigned to Innovative Global Systems LLC
         : First E D Tex suits filed
    2016 : Patent expired

NPE / troll-pattern signals

1. Shell-entity transfer — PRESENT (medium strength). The patent passed from the operating R&D firm (VES) to Innovative Global Systems, LLC on 2009-04-06. This is not inferred from the name alone: the transferor's own website describes IGS as a company "newly formed by Alan Lesesky in 2008 as an IP holding company." Evidence of no products in commerce, a registered-agent address, or single-member Delaware/Texas LLC status was not retrieved, so I cannot confirm the anonymous-shell tells; the finding rests on the entity's self-described purpose plus Unified Patents' classification (signal 2).

2. Known asserter in the chain — PRESENT. Innovative Global Systems, LLC is the patent owner in Unified Patents PTAB case IPR2020-00155, Zonar Systems Inc. v. Innovative Global Systems LLC (filed 2019-11-19; instituted 2020-05-12; settled 2020-08-27), where Unified Patents classifies the patent owner as "NPE (Individual)". IGS also appears as the asserter in the Stanford NPE/asserter database ("Innovative Global Systems LLC v. Teletrac, Inc. et al, 6:10-cv-00040, E.D. Tex.") under the category "Individual-inventor-started." IGS does not appear on the classic large-fund NPE lists in your prompt (Acacia, Marathon, IV, Wi-LAN/Conversant, Vringo, Pendrell, MPHJ, Lumen View, Round Rock, etc.) — this is an inventor-controlled NPE, not a third-party patent aggregator. That distinction matters for characterization but not for the classification: IGS does not practice the patent.

3. Repeat correspondent across the chain — UNKNOWN / NOT VERIFIED. No correspondent-of-record fields were retrievable. The one datapoint I have is prosecution counsel, not a recording correspondent: family member US 6,946,953 B2 names "**Bracewell & Patterson, LLP; Jeffrey S. **[surname truncated in source]" as attorney/agent of record. Per your own caution — many firms do both NPE and operating-company work, and a single appearance is not a finding — I make no finding here. Action item for a follow-up session: pull the correspondent field for each of the four post-issuance recordings; a single recurring recorder across the 2002, 2004 and 2009 links would upgrade this signal.

4. Cascading transfers — PARTIAL / WEAK. There are four recordings across three dates, but the gaps are wide: 2002-12-02 → 2004-05-10 (~17 months) and 2004-05-10 → 2009-04-06 (~5 years). Only the two same-day 2009-04-06 recordings form a tight ladder. The strict test (multiple consecutive assignments through chained LLCs in <24 months) is not met. There is, however, visible churn: VES → VES-TEK (2002) → back to VES (2009) → IGS (2009), which reads as a cleanup-and-extract sequence rather than a continuous licensing chain.

5. Pre-litigation transfer — LIKELY PRESENT, unverified on dates. The transfer to IGS is recorded 2009-04-06; the earliest listed infringement case for this family is E.D. Tex. 6:09-cv-00157, filed in 2009. If that complaint was filed on or after 2009-04-06 (and within six months), the assignment immediately preceded assertion — the paradigm clean-standing/venue-setup pattern. I could not retrieve the exact filing date and therefore mark the "within 6 months" element unverified. Action item: confirm the 6:09-cv-00157 docket date. If confirmed, this is a second strong signal.

6. Bankruptcy fire-sale — NOT PRESENT. No Chapter 7/11 filing, no trustee sale, no §363 auction found for VES, VES-TEK, or IGS. VES's website describes a going concern with a 2013 facility move. Explicitly negative.

7. Privateering — UNCLEAR. On the classic definition (operating company arms an NPE to sue its competitors), VES is not an OEM and I have no SEC filings or EFF/Patent Progress coverage showing VES directing IGS's suits. The complication is that the same individual (Lesesky) is President/CEO of both the transferor and the transferee NPE, so "privateering" understates it — this looks more like self-assertion by an inventor-controlled IP holdco. No finding without the transfer agreement terms.

8. Defensive aggregator — NOT PRESENT. The chain terminates at Innovative Global Systems, LLC, which is an asserting entity, not RPX / AST / LOT / Unified Patents / OIN. No neutralization.

Additional corroborating item: the asserted patents in the Unified Patents IPRs are the same Lesesky family (US 7,102,494; US 6,946,953; US 6,064,299; US 7,280,898) — i.e., IGS built a serial assertion program across the whole portfolio derived from this priority chain, not a one-off suit.

Verdict

NPE — high confidence.

Two strong signals are independently documented. First, the patent was transferred on 2009-04-06 from the operating company Vehicle Enhancement Systems, Inc. to Innovative Global Systems, LLC, an entity that VES's own corporate history describes as an "IP holding company" formed in 2008 by the same founder/CEO — a non-practicing assertion vehicle that is now the current assignee (signal 1). Second, IGS is a recognized asserter: Unified Patents lists it as patent owner classified "NPE (Individual)" in IPR2020-00155 Zonar Systems v. Innovative Global Systems (filed 2019-11-19, settled 2020-08-27), and the Stanford NPE database records Innovative Global Systems LLC v. Teletrac, Inc. et al, 6:10-cv-00040 (E.D. Tex.) under "Individual-inventor-started" (signal 2). The temporal coincidence of the IGS assignment with the first 2009 E.D. Tex. filings further supports a transfer arranged to enable assertion (signal 5, dates unconfirmed). Caveat for accuracy: this is an inventor-controlled NPE — the inventor never left, and the transferor VES still operates — not a third-party patent aggregator; and the reel/frame numbers for the 2002, 2004 and 2009 recordings, plus all correspondent fields, remain unverified and should be pulled directly from Assignment Center.

Verify at: https://assignmentcenter.uspto.gov/ (patent 6608554) · https://assignment.uspto.gov/patent/index.html · Google Patents legal events: https://patents.google.com/patent/US6608554/en · Unified Patents IPR2020-00155: https://portal.unifiedpatents.com/ptab/case/IPR2020-00155

I'll research US patent 6608554 and its prior art citations.

Let me search for the specific "References Cited" on the face of the patent.

US 6,608,554 B2 — Prior-Art Analysis

Important methodological note (please read first)

The instruction was to "look at each patent citation for 6608554." I need to flag a limitation honestly rather than fabricate: the search results I was able to retrieve returned the patent's "Cited By" (forward-citation) list — i.e., 74 later patents/publications that cite US 6,608,554 — not the front-page "References Cited" (prior-art) list that the examiner placed on the face of the '554 patent. Those are two different things, and the forward citations are not prior art against '554 (they post-date it).

Likewise, I located the front-page references of the closely related Lesesky patent US 6,946,953 (Okazaki '719; Drori '667; Jasper '352; Srygley '034; Lesesky '667/'577/'632/'563/'299/'588/'524/'939/'793/'201; Nakanishi '224; Arjomand '202/'609; Ryan '180; Hullinger '485; Mueller '416; McClure '248; design patents D403,659 / D404,170 / D434,006). I could not confirm that this same list appears on the face of '554, so I will not present it as the '554 citation list.

I could not retrieve the exact examiner-cited references of US 6,608,554 from the sources available to me. I am stating this explicitly rather than reconstructing it. The list below is limited to prior art I can actually ground in the authoritative patent text you supplied or in retrieved sources.

1. Verified bibliographic data of the target patent

From the authoritative full text (Google Patents, fetched 2026-09-30):

Continuity chain (as recited in the '554 specification): this application is a continuation of Ser. No. 09/569,995 (now US 6,411,203), which is a continuation of Ser. No. 08/907,861 (now US 6,064,299), which is a CIP of Ser. No. 08/594,255 (now US 6,111,524), which is a CIP of Ser. No. 08/554,907 (abandoned), filed 1995-11-09. This is material to any § 102 analysis: any reference dated after 1995-11-09 is presumptively not prior art unless it qualifies under a § 102(b)/102(e) exception.

2. The only per-claim anticipatory candidates I can legitimately identify

Because I could not retrieve the examiner's citation list, I can only analyze references that the patent text itself identifies as prior art. The '554 specification expressly names these:

A. U.S. Pat. No. 5,488,352 — Jasper — "Communications And Control System For Tractor/Trailer And Associated Method"

• Assignee: common assignee (Vehicle Enhancement Systems) per the specification.
• Disclosure (per '554's own description): data communications between a tractor and trailer; use of SAE J1708 and J1939 for heavy-duty-vehicle data communications; a controller and electronic subsystems on the tractor/trailer.
• Potentially relevant claims: The preamble elements of claim 1 (electronic subsystem, electrical conductors, connector, controller) and claims 8 / 11 / 24 (controller, signal generating means, converting a first vehicle protocol on a plurality of conductors). Jasper is a strong § 103 reference.
• § 102 caveat: Jasper is a tractor↔trailer communications/control patent. The '554 independent claims 1, 11, and 24 each require a through-the-air second protocol (infrared or RF) and a remote data communications terminal with a second transceiver. I have no verified evidence Jasper discloses that, so I would not assert Jasper as a § 102 anticipation of claims 1–33; it is better characterized as § 103 art.

B. SAE Standard J1708 ("Serial Data Communications Between Microcomputer Systems In Heavy Duty Vehicle Applications") and SAE Standard J1939

• Nature: industry standards, identified in the '554 background and relied on for the "first data communications protocol" limitations.
• Potentially relevant claims: claim 6 ("the first data communications protocol comprises … SAE J1708, SAE J1939, and RS-485") and claim 32 (same, in method form). A printed standard predating 1995-11-09 could be § 102(b) art for those narrow protocol-identification limitations only — it cannot anticipate a full independent claim, which also requires the protocol-converting means and transceiver.

3. Why the "74 Citing Documents" are NOT prior art

The Google Patents "Cited By (74)" set (e.g., Zonar US 7,944,345 / 8,400,296 / 8,810,385; Progressive US 8,090,598; Caterpillar US 7,516,244 / 7,983,820; Savi Technology publications; Power Talk US 7,497,529; etc.) all cite '554 and therefore post-date its 1995-11-09 priority / 2003-08-19 grant. They are rebuttal/derivation evidence and license to a technology field, but they are legally incapable of anticipating US 6,608,554.

4. Family members — related, but not prior art

US 6,064,299, US 6,411,203, US 6,111,524, US 6,744,352, US 7,448,993, US 7,817,019, US 8,232,871, US 8,680,976 and application 10/051,772 share the same priority/inventors. As same-family, same-inventor documents they are not prior art against '554 (they are the "Related Parent/Child Applications" listed on the patent). I raise them because they are often mistakenly cited as art.

5. Recommended next step to complete the task properly

To give a defensible, per-reference, per-claim § 102 table you would need the actual front-page "References Cited" of US 6,608,554 (both U.S. Patent Documents and Foreign Patent Documents), which I was unable to retrieve. Those are obtainable from:

• USPTO Patent Public Search / Patent Center (full-text and imaged full document, application 10/007,032), and
• the PDF full text at patentimages (the (56) References Cited block on page 1).

Without that specific list, asserting which references "potentially anticipate which claims" would require me to invent the citations — which I will not do.

Summary table (only grounded entries)

Bottom line: The single reference the '554 specification actually identifies as prior art is U.S. Pat. No. 5,488,352 to Jasper, plus the SAE J1708 / J1939 standards. The full examiner-cited prior-art list for US 6,608,554 was not retrievable in this session, and I have deliberately not fabricated it. If you can supply the patent's page-1 (56) references (or authorize retrieval from the USPTO full-document image), I will build the complete per-reference, per-claim § 102 analysis.

I'll ground this obviousness analysis in the actual prior-art record. Let me pull the references cited on the face of US 6,608,554, since the fetched page text omitted the front-page "References Cited" list.

Let me pull the actual front-page reference list from FreePatentsOnline/Justia, which typically reproduce the examiner-cited U.S. and foreign patent documents.

The front-page "References Cited" list wasn't reproduced in the pages my search returned. Let me try to retrieve the examiner-cited patent documents directly, including from sibling family member US 6,411,203 and the IPR record.

Obviousness Analysis — US 6,608,554 B2 under 35 U.S.C. § 103

0. Scope, evidence base, and an explicit limitation

Before the analysis, one candid constraint, because it materially shapes what follows.

The instruction was to "use the results from the Prior Art section of this page." As fetched, however, the Prior Art panel of the Google Patents page for US 6,608,554 contains only:

• Prior art date: 1995-11-09
• Prior art keywords: data communications · transceiver · vehicle · communications protocol · connector
• the Related/Claiming-Priority application list (the Lesesky parent chain)

The front-page "(56) References Cited" list — the examiner-cited U.S./foreign patent documents — was not reproduced in the page text I retrieved, and my attempts to retrieve it from FreePatentsOnline, Justia, uspto.report, and the patentimages PDFs returned only other patents' reference lists. I therefore cannot report the actual §102/§103 rejections of record or the examiner's cited art for this patent, and I will not invent a citation list. Per the operating rules, I am flagging that gap rather than filling it.

What this analysis therefore is: a KSR-style, claim-element-by-claim-element obviousness assessment built on (a) the prior art identified within the four corners of the '554 document itself, and (b) the standards/protocols the specification and claims expressly name as known. It is a rebuttal/defense-mode analysis, not a critique of a specific rejection of record.

Also flagged — a likely misuse trap: the Google Patents page lists "Cited By (74)" and "Families Citing this family (74)." Every entry there is a post-dating document (e.g., US 6,946,953; US 7,492,529; US 8,626,377; US 10,127,556). Under pre-AIA §102, later documents are not prior art against the '554 patent. They are usable only as evidence of what was conventional in the art (and as proof that the field was crowded) — not as anticipatory or combinable art. I use them only in that limited, secondary way below.

No contradiction found with the previously generated sections. The claim-drafting anomalies (claim 13's "further claim"; claim 18's "local-area" antecedent gap; claim 24's "from a vehicle") are carried forward, not re-argued.

Governing law: Priority 1995-11-09, filed 2001-11-08 → pre-AIA 35 U.S.C. § 103(a), as construed by Graham v. John Deere and, decisively for a 2003-issued patent litigated in 2010–2012, KSR Int'l Co. v. Teleflex Inc., 550 U.S. 398 (2007).

1. The prior art that is actually "of record" in this document

This is a thin but highly probative prior-art base, because most of it is admitted by the applicant in the specification. Under Federal Circuit law, statements in the specification characterizing structures as conventional are admissions usable in a §103 analysis (Constant v. Advanced Micro-Devices; In re Nomiya). The '554 specification does this repeatedly.

Self-collision / §103(c) issue (must be noted): The parents US 6,064,299, US 6,411,203, and US 6,111,524 are by the same inventive entity (Lesesky + Weant) and commonly owned. They are therefore not "prior art by another" under pre-AIA §102(a)/(e), and any residual §102(f)/(g)/(e) art is disqualified by pre-AIA §103(c) (common ownership). They cannot be combined against these claims. Likewise the children ('352, '800, '493, '019, '976) post-date. This narrows the attack surface considerably and is a legitimate defensive point.

2. Claim-construction points that drive the §103 result

Three constructions materially change obviousness:

1. "vehicle data communications protocol converting means" is means-plus-function (pre-AIA §112 ¶6). Its scope is limited to the disclosed structure and equivalents: the spec discloses a first converter 37 = RS-485 transceiver and a second converter 39 = microprocessor + IrDA IC (or RF IC). Prior art must therefore disclose (or render obvious) that structure (or an equivalent) functioning to translate the bus protocol to the over-the-air protocol.

2. Independent claim 1 does not require wireless. Read literally, claim 1's "second data communications protocol" is unqualified — it never says infrared, RF, or "not connected." Claims 11 and 24 do (the remote terminal is "not connected to the vehicle"). So claim 1 is broader and more vulnerable than claims 11/24.

3. "only using the physical layer … and not a data link layer" (claims 3, 18, 22, 30) is the single most distinguishing limitation in the patent — and, as shown below, it is also the most factually fragile.

3. Independent claim 1 — element mapping and combinations

Combination 1 (primary): Jasper '352 + an admitted wireless datalink (IrDA or RF) + a conventional converter

Rationale / motivation (KSR):

• The problem was known and the solution was pre-identified. Jasper already communicates vehicle data over the bus; the only unmet need was getting it off the vehicle without a tether. The specification itself frames the invention as providing "through-the-air … data communications … which does not require equipment to be coupled to the heavy duty vehicle."
• Finite, predictable options. At the 1995 priority date, a POSITA seeking an over-the-air link had essentially two choices — IR or RF — and the claims themselves treat that pair as the universe ("one of either an infrared … or an RF data communication protocol"). KSR: where there is "a finite number of identified, predictable solutions," following the lead is obvious.
• Design incentives / market forces. Fleet operators and D.O.T.-related inspection needed to read ABS/brake/trailer data quickly, ideally without opening a locked cab or mating a dirty connector. That is a classic KSR "design incentive … and the market forces."
• Predictable substitution of a known component for a known component. Replacing/adding a wired diagnostic link with a standard IrDA modem is a substitution of one known element for another yielding no more than expected results.

Combination 2 (for the converter): Jasper '352 + SAE J1708 + a general-purpose protocol converter

• J1708 supplies the first protocol; the spec admits the converter's building blocks (RS-485 transceiver, microprocessor, IrDA/Rohm IC). Combining a documented bus protocol with a documented modem/controller to bridge them is mechanical; the specification concedes as much by calling the components "understood by those skilled in the art."

Combination 3 (for the RF variants, claims 17–23, 29–31): + CEBus

• The spec expressly names CEBus as a known RF protocol using "predetermined RF data communications protocol." Choosing CEBus or a "simple modulation scheme" to implement the second protocol is a design choice among known options.

Preliminary conclusion on claim 1: On this record, claim 1 is highly vulnerable. Its wireless-agnostic scope means even a wired second protocol + a second transceiver could read on it, and every recited element is either disclosed by Jasper '352 or admitted conventional in the specification.

4. Independent claim 11 (vehicle-side only; remote terminal "not connected")

Claim 11 adds the express "not connected to the vehicle" limitation — i.e., genuine through-the-air communication — and drops the connector-position requirement of claim 1.

• The added limitation is disclosed/motivated by the same art as Combination 1: the specification's own stated object is to avoid coupling equipment to the vehicle.
• Counter-argument available to the patentee: claim 11 requires the transceiver itself to both transmit from and receive from the remote terminal, with the converter in a vehicle-mounted apparatus. If the asserted art merely shows a handheld reader that downloads but does not support bidirectional exchange, the "receive … from a remote data communications terminal" limitation is not met. (Note claim 1 and 11 both require receive, unlike claim 24's method, which is transmit-only.)

Conclusion: claim 11 is vulnerable but slightly narrower/more defensible than claim 1 because of the express bidirectional, non-connected limitation.

5. Independent claim 24 (method: convert, then transmit to a non-connected remote terminal)

• This claim is transmit-only and recites "from a vehicle" (indefinite article) — the broadest possible framing. A method of "read the bus, translate the protocol, beam it out" is the natural, expected result of applying a standard wireless modem to Jasper's bus. Under KSR, "[t]he combination of familiar elements according to known methods is likely to be obvious … if it does no more than yield predictable results."

Conclusion: claim 24 is highly vulnerable.

6. Dependent claims

7. Overall motivation-to-combine statement (why a POSITA would have combined)

Synthesizing KSR:

1. The prior art elements were "known" and the combination was "predictable." Jasper '352 + a standard IrDA/RF modem + a standard protocol converter performs no function beyond what each was known to perform.
2. The improvement was express and pre-identified by the applicant's own specification. The spec frames the goal as replacing a coupled link with a through-the-air link.
3. A finite, predictable solution set (IR or RF) existed at the priority date — the claims themselves enumerate it exhaustively.
4. Strong market/design motivation: fleet diagnostics, D.O.T. inspections, locked cabs, dirty/corroded connectors (the spec's own recital of "dirt, dust, grime, corrosive atmospheres").
5. "Obvious to try." With only two physical layers to test, KSR squarely applies.
6. Post-dating "Cited By" evidence corroborates, rather than proves, obviousness: 74 later documents independently adopted the "wireless telematics gateway off a vehicle bus" architecture — useful only as contextual evidence that the architecture was conventional, not as prior art.

8. Where the patentee has the strongest §103 defense

1. Claims 3 / 18 / 22 / 30 ("physical layer only, not a data link layer"). Because standard IrDA implementations include a data link layer, this limitation is comparatively specific and could defeat a §103 combination built on off-the-shelf IrDA (the art must supply the motivation to strip the DLL). Still, the specification's own "simplification" rationale cuts against the patentee.
2. Claims 19–20 (side-marker light housing). Requires a specific motivation (concealment) and a lamp-housing-integration reference; a clean combination is harder to assemble.
3. §103(c) / common-ownership shield against the parent Lesesky patents (US 6,064,299 / 6,411,203 / 6,111,524) and identity-of-inventorship shield on all family members.
4. Means-plus-function narrowness of the "converting means" limits the art that can read on element (d).

9. Claim-by-claim risk summary

Bottom line: On the record available on this page, every independent claim is prima facie obvious under pre-AIA §103/KSR given Jasper '352 plus the applicant's own admissions that the converter components (RS-485 transceiver, microprocessor, HP/Rohm IrDA ICs, RF/CEBus modems), the six-pin Deutsch connector, and laptop computers were all conventional. The only realistically survivable limitations are the "physical layer only, not a data link layer" claims (3, 18, 22, 30) and the side-marker-light-housing claims (19–20) — and even those are vulnerable given the specification's own characterizations.

Verification & uncertainty statement (per operating rules)

• Not verified: the examiner's actual "References Cited" list and any §102/§103 rejections of record for US 6,608,554. I could not retrieve them, and I have not fabricated a citation list.
• Not verified: whether any specific one of the E.D. Tex./E.D. Mich. suits asserted the '554 patent specifically (the litigation data is family-keyed; see prior section).
• Cross-references to priors retained, not repeated: the abstract/claims "heavy duty vehicle" vs. "vehicle" mismatch; the claim 13 "further claim"/bare-"12" defect; the claim 18 "local-area" antecedent gap; the claim 24 "a vehicle" indefiniteness. No contradiction found between this analysis and the previously generated sections.
• Self-collision limitation applied: the Lesesky parent/child applications are not used as combinable prior art (same inventive entity / common ownership, pre-AIA §103(c)); the 74 "Cited By" documents are used only as conventionality context, not as prior art.