US 5974234

I'll search for the specific patent number and any associated litigation, then summarize.

Search results for US 5,974,234 — litigation/docket check

No CAFC 2026 appeal, no district-court case, and no PTAB/IPR proceeding involving U.S. Patent No. 5,974,234 was found in my searches. I want to be explicit about this rather than infer a "clean" litigation history: I could not query PACER, Docket Navigator, or the CAFC docket directly, so all I can say with confidence is that nothing surfaced.

Two cautions about near-matches I did see, neither of which relates to this patent:

• The string "5974234" appears in Tribunal Regional Federal da 3ª Região, Apelação Cível nº 5974234-27.2019.4.03.9999 — this is a Brazilian social-security (INSS) appeal, not a US patent case. The digits coincide; do not treat it as a hit.
• The PTAB petition and IPR materials returned (Keeney/spooling-server, VideoLabs, VirtaMove, Summa etc.) involve entirely different patents.

The patent's status, per the USPTO/Google Patents record, is "Expired – Lifetime" with an anticipated expiration of 2017-04-15 (20 years from filing, with maintenance fees paid). Its terminal date has passed, which is a practical reason no 2026 appellate activity exists.

Concise summary of US 5,974,234

Abstract (as issued)

A printing system in which one or more clients communicate with a plurality of printers by way of a print server whose architecture is characterized by a plurality of layers. One layer receives a client request designating an operation to be performed with respect to one of the printers. The system includes (i) an application layer that develops a command expression based on the request, (ii) a communications interface with a first connectivity module and a second connectivity module respectively communicating with a first and second printer, and (iii) a routing interface communicating with both the application layer and the communications interface, for directing the command expression to a selected one of the connectivity modules. The selected module then uses the command expression to perform at least part of the designated operation on its printer.

Plain-language overview of the independent claims

Claim 1 (the core server claim). A centralized print server sitting between clients and multiple printers. It has three cooperating pieces: a single application layer that turns a client's request into a "command expression"; a communications interface containing at least two separate connectivity modules, each dedicated to talking to a different printer; and a routing interface (sitting between the two) that selectively directs the command expression out of the single application layer to the correct connectivity module. The chosen module then carries out at least part of the requested operation on its printer. The commercial point: one application layer can drive many dissimilar devices because device-specific knowledge is pushed down into the per-device connectivity modules.

Claim 12 (the HTTP/Internet-context independent claim). A centralized server for an Internet/Intranet printing system, comprising an HTTP server layer that receives a client request seeking a set of information about one of the document-processing devices, in combination with a single application layer communicating with that HTTP layer and with the downstream routing/communications structure (the claim text in the record I retrieved is cut off mid-claim, so I cannot restate its full scope reliably). Claim 13 depends from claim 12; I do not have its full text.

Plain-language overview of the dependent claims (2–11)

• 2 — The routing interface is an application programming interface (API) that interprets the command expression to decide which connectivity module receives it.
• 3 — The command expression asks a module to retrieve selected state information about jobs in that printer's queue.
• 4 — The command expression asks a module to retrieve selected machine settings of the printer.
• 5 — The command expression can instruct a module to add or delete a printer from the system.
• 6 — One of the layers is an HTTP server that responds to HTTP requests from clients.
• 7 — At least one, but not all, of the printers has its own embedded HTTP server — i.e., the proxy works for devices with and without embedded web servers (the express distinction over HP's proprietary-card approach discussed in the Background).
• 8 — Adds a database, communicating with both the single application layer and the routing interface, storing information about each printer.
• 9 — When the communications interface obtains fresh information from a printer, the corresponding database portion is updated when a preselected condition is met.
• 10 — That condition is age-based: the stored portion is refreshed when its age exceeds a preselected threshold age (the "date stamped" cache concept).
• 11 — Alternatively, the database portion is updated periodically.

Confidence / uncertainty notes

• Bibliographic data, abstract, and claim 1 are drawn from the full patent text supplied, which I treat as authoritative.
• Independent-claim completeness caveat: the record I retrieved truncates claim 12 mid-sentence and omits claim 13 entirely. I have therefore described claim 12 only in part and flagged claim 13 as unverified rather than guessing its scope.
• Litigation caveat: absence of a CAFC 2026 docket hit is based on web search only, not on a direct PACER/CAFC docket query. Given the patent expired 2017-04-15, any 2026 appeal would be unusual, but I cannot rule one out definitively.
• Assignee caveat: Google Patents lists current assignee as Google LLC (a chain of recorded reassignments from Xerox, plus two secured-party releases in 2011/2022). USPTO/Google expressly state assignments are not legally verified; I have reported them as recorded, not as adjudicated ownership.

I'll search litigation databases for this specific patent number.

The initial searches didn't surface anything specific. Let me query litigation databases more directly.

Let me try a few more targeted litigation-database searches.

Summary

I found no litigation involving U.S. Patent No. 5,974,234.

Despite targeted searches of litigation-focused sources (Unified Patents, CourtListener/RECAP, Justia dockets, Docket Alarm, PACERMonitor, PTAB/USPTO PTACTS, and CAFC opinions), no case — district court, ITC, PTAB, or appellate — could be tied to this specific patent number.

What I searched

• Queries for "5,974,234", "5974234", and the patent title ("Centralized print server for interfacing one or more network clients with a plurality of printing devices") combined with terms like litigation, infringement, complaint, plaintiff/defendant, and Xerox.
• Litigation aggregators and repositories: portal.unifiedpatents.com (caselist), CourtListener, Justia dockets, Docket Alarm, PACERMonitor, and CAFC opinion/order pages.
• USPTO PTACTS for any IPR/PGR/CBM involving the patent.

Results — no matches

Every hit returned was not this patent, and per your instruction I am expressly flagging them rather than treating them as relevant:

Additional context (no litigation implications)

• Prosecution/ownership history (from the patent record): original assignee Xerox Corp.; assigned to Google Inc. (2012) and later Google LLC (2017); legal status now Expired – Lifetime, with anticipated expiration on 2017-04-15 (20 years from the 1997-04-15 filing date).
• No reexamination, IPR, PGR, CBM, or other post-grant proceeding involving this patent appeared in the PTAB records I reviewed.

Caveats

1. Absence of evidence is not conclusive proof of absence. Docket aggregators index incompletely, and older district-court filings (especially pre-2000) are often not fully digitized. A definitive negative would require a PACER/Unified Patents Docket Navigator run scoped precisely to 5,974,234.
2. If you want an exhaustive check, I'd recommend a paid Docket Navigator or LexisNexis PatentAdvisor search keyed to the patent number, plus an assignment/license review (given the Xerox → Google transfer in 2012, the patent may have only ever been used defensively by its owners).
3. I did not auto-correct any identifiers; JP 5974234 and the Brazilian case number are reported here only to explain why they are not the patent you asked about.

Bottom line: On the evidence available, U.S. Patent No. 5,974,234 has no known litigation history.

PTAB AIA Trial Landscape — U.S. Patent No. 5,974,234

Patent: "Centralized print server for interfacing one or more network clients with a plurality of printing devices"
App. No.: 08/842,546 · Filed: 1997-04-15 · Issued: 1999-10-26
Inventors: Levine; Gombert; Mayer · Original assignee: Xerox Corp.
Current assignee of record: Google LLC (Xerox → Google Inc. on 2012-02-16; Google Inc. → Google LLC on 2017-10-05)
Statutory term end: 2017-04-15 (Google Patents legal status: Expired – Lifetime; "Anticipated expiration" docketed 2017-04-15)

Proceedings overview

Zero AIA trial proceedings on file. The USPTO Open Data Portal returned no IPR, PGR, or CBM proceedings for US 5,974,234, and nothing in web search contradicts that — a targeted search for IPR/PGR/CBM petitions naming the '234 patent returns no PTAB docket, no institution decision, no Final Written Decision, and no Federal Circuit appeal. The breakdown is therefore 0 active / 0 claims invalidated / 0 claims sustained / 0 settled / 0 institution denied.

The defensive bottom line is unusual and stronger than "hardened by IPR": because the patent expired on 2017-04-15 and the claims were never tested at the Board, there is nothing left to challenge and nothing left to assert. Claim 1 through claim 13 stand unadjudicated but unenforceable — they cannot support an infringement demand, and no IPR can be filed against them for defensive estoppel purposes (a petition against an expired patent is permissible in theory but serves almost no litigation purpose). If someone is citing this patent number in a demand letter today, the letter is defective on its face: the asserted right expired more than nine years ago.

How this conclusion was reached (and its limits)

• Structured source (canonical): the ODP-derived "PTAB proceedings on file" block supplied with this matter reports no AIA trial proceedings as of the most recent ingest. No proceeding numbers were supplied, so none are reported here. I have not generated any proceeding number.
• Independent web check: searches for US5974234 IPR PTAB, "5,974,234" PTAB AIA trial, and "5974234" IPR2020/IPR2019/CBM surfaced only (a) the patent's own Google Patents/Schrift page, (b) an unrelated Japanese patent JP 5974234 B2 (an Autoliv/Nissin solenoid-valve patent — a different document that coincidentally shares the number), (c) an unrelated Brazilian civil appeal No. 5974234-27.2019 (INSS social-security benefits), and (d) an unrelated U.S. trademark registration No. 5,974,234 (NINETYEIGHT6). None of these are PTAB proceedings on this patent.
• Claim-level outcomes, panels, institution reasoning, settlements, and CAFC dispositions: not applicable and not knowable here — with no proceeding on file there is no FWD, no APJ panel, and no appeal. I am explicitly declining to fill these fields with inferred content.

Proceedings

None. No AIA trial proceeding has been instituted, denied, or terminated with respect to U.S. Patent No. 5,974,234. There is no FWD to link at USPTO PTAB E2E and no CAFC opinion at CourtListener.

Strategic summary

Claim status. Claims 1–13 of the '234 patent are UNTESTED — not canceled, not confirmed. No claim has been narrowed, disclaimed, or held unpatentable by the Board, and there is no certificate under 35 U.S.C. § 318(b) affecting any claim. The absence of PTAB activity here is not the "well-asserted patents eventually attract IPRs" signal, because the patent was never a significant assertion vehicle: it issued to Xerox in 1999, was swept into the Xerox→Google transaction in 2012 (a five-year-later-to-expiry defensive acquisition, typical of a defensive portfolio buy rather than an enforcement program), and reached end of term on 2017-04-15 without a single public IPR, PGR, CBM, or reported district-court assertion. Contrast that with, e.g., the parallel IPR2025-xxxxx activity around Intellectual Ventures print/imaging patents, where assertion drove multi-petition IPR campaigns.

Estoppel landscape. Because no petitioner ever filed, § 315(e)(2) estoppel attaches to no one. There is no petitioner, no real party in interest, and no privy barred from raising prior-art grounds in a district court. Practically this is moot: the claims are expired, so there is no live infringement action in which invalidity could be raised, and no defendant needs a prior-art ground. Separately, PGR was never available for this patent (it issued 1999-10-26, long before the 2012-09-16 PGR effective date), and the CBM transitional program has sunset for new petitions (2020-09-16); even while open, a print-server/HTTP-proxy patent of this type would likely have been excluded as a "technological invention."

Pattern signals. No repeat petitioner, no judicial-estoppel chain, no defensive aggregator (Unified Patents or similar) in the record. The only post-issuance activity in the assignment history is security-interest housekeeping — Bank One (2002-06-28), JPMorgan Chase (2003-10-31), and releases by both secured parties (2011-09-23, and again 2022-09-07 for the JPMorgan successor-in-interest) — which is financing paperwork, not enforcement or validity activity.

Recommended next steps

1. If you received a demand or notice letter citing US 5,974,234: treat it as a red flag about the sender's diligence, not as an exposure. Verify the patent's legal status on the USPTO Patent Center / Global Dossier; the record shows term expiry on 2017-04-15 and "Expired – Lifetime." An expired patent cannot be infringed — no injunction, no ongoing royalty, and damages limited at most to the pre-expiry window (which cannot include present-day accused products unless they predate April 2017).
2. Do not budget for an IPR. There is no AIA trial to file, join, or defend, and no claim-level Board findings to leverage. Any invalidity work should be directed at whatever live patents the asserting party actually owns.
3. If the letter cites other patents in the same Xerox/Google print-server family — e.g., the cross-referenced applications noted on the face of the '234 patent (Ser. No. 09/003,734, Network Printing System, Levine; Ser. No. 08/842,584, Network Printing System, Levine et al., both filed the same day) — run the PTAB check on those numbers individually. Their AIA-trial posture may differ entirely from the '234 patent's, and contiguity in a patent family says nothing about PTAB exposure.
4. Re-verify before relying on this memo. ODP ingest lags, and a late-filed petition or a sua sponte Board action would change the picture; a fresh check of the PTAB E2E search page for patent number 5974234 is the right confirmation step. As of 2026-09-24 I found none, and I have flagged that as a finding rather than an assumption.

I'll reconstruct the chain from the authoritative patent text first, then attempt to verify reel/frame and correspondent data via live sources.

Let me try to surface reel/frame numbers and the recording correspondent.

Assignment Record Reconstruction — US 5,974,234

Data-availability note (read first). The authoritative patent text provided for this matter (Google Patents / USPTO legal-events feed) exposes dates, conveyance types, assignors and assignees — but not reel/frame numbers and not the correspondent of record. I was unable to retrieve the underlying USPTO Assignment Center images for this patent in my reachable sources. Every reel/frame field below is therefore marked "not retrieved" rather than guessed. If you are working from the live Assignment Center UI, the six XRX-related entries and the two Google entries are all that should appear; the timeline and parties below should reconcile one-for-one.

Inventors

Pattern check: All three inventors executed an assignment of assignors' interest to Xerox Corporation at filing (recorded 1997‑04‑15). There is no evidence of inventors departing the original assignee within 12 months. Note, however, that this is the absence of evidence, not affirmative evidence of retention — I have no post‑1997 employment or personnel data on Levine, Gombert or Mayer. The three are credited on several other Xerox networked‑printing/server filings of the same era (e.g. the cross‑referenced Levine applications), which is consistent with a career engineering group rather than a departing-team signal.

Original assignee

Xerox Corporation (Stamford, CT / Rochester, NY; New York corporation).

• Product embodiment — yes, on the face of the spec. The disclosure expressly situates the proxy print server on the Xerox Document Centre System 35 digital copier / networked multifunction platform and references Xerox's DocuSP 1.0 print server for the AAA (Accounting/Authorization/Authentication) function. The patented architecture (HTTP server layer → application layer → routing API → communications/middleware layer → device) is the network‑connectivity stack for those Xerox products, so Xerox did ship products embodying the claims.
• Primary line of business: document management / printing and copying hardware and software.
• Current status: operating. Xerox remains a public operating company (Xerox Holdings Corporation; XRX). Xerox's document‑outsourcing BPO business was spun off as Conduent in 2017 (Separation and Distribution Agreement dated Dec. 30, 2016); the printing business continues under the Xerox name. Xerox did not file Chapter 7/11 in this period — its 2000‑2002 difficulties were SEC accounting restatements, not a bankruptcy proceeding.

Assignment timeline

Recorded / executed dates below are taken from the authoritative legal-events text. Google Patents "Assigned to" events are generally recording dates; the corroborating public reporting places the Xerox→Google batch transaction in February 2012.

1997‑04‑15 (executed at/near filing) / recorded 1997‑04‑15 — Reel/Frame not retrieved

• Conveyance: Assignment of Assignors' Interest
• Assignor: Barry G. Gombert; Jonathan D. Levine; James L. Mayer (individually)
• Assignee: Xerox Corporation
• Correspondent: not retrieved. (For background only — not attributed to this record: Xerox's IP correspondence of record in other filings of this era is handled in‑house by Margaret W. Walker, Norwalk CT, and externally by Latham & Watkins LLP c/o Angela M. Amaru, New York. I could not confirm either on this patent's assignment record.)
• Context: initial prosecution‑era assignment — inventors convey to the employer.

2002‑06‑28 / recorded 2002‑06‑28 — Reel/Frame not retrieved

• Conveyance: Security Interest
• Assignor: Xerox Corporation
• Assignee: Bank One, NA, as Administrative Agent
• Correspondent: not retrieved.
• Context: securitization — collateral grant under Xerox's bank credit facility; not a transfer of ownership.

2003‑10‑31 / recorded 2003‑10‑31 — Reel/Frame not retrieved

• Conveyance: Security Agreement
• Assignor: Xerox Corporation
• Assignee: JPMorgan Chase Bank, as Collateral Agent
• Correspondent: not retrieved.
• Context: securitization — successor/parallel collateral grant in the same refinancing cycle.

2011‑09‑23 / recorded 2011‑09‑23 — Reel/Frame not retrieved

• Conveyance: Release by Secured Party
• Assignor: JPMorgan Chase Bank, N.A. → Assignee named in record: Xerox Corporation
• Correspondent: not retrieved.
• Context: security‑interest release / housekeeping.

2011‑09‑23 / recorded 2011‑09‑23 — Reel/Frame not retrieved

• Conveyance: Release by Secured Party
• Assignor: Bank One, NA → Assignee named in record: Xerox Corporation
• Correspondent: not retrieved.
• Context: security‑interest release / housekeeping. (Both 2011 releases executed the same day, clearing the 2002 and 2003 liens.)

2012‑02‑16 / recorded 2012‑02‑16 — Reel/Frame not retrieved

• Conveyance: Assignment of Interest
• Assignor: Xerox Corporation
• Assignee: Google Inc.
• Correspondent: not retrieved.
• Context: portfolio acquisition. Public reporting (SEO by the Sea, Feb. 2012; SynergyTek transaction analysis) identifies this patent as one of a batch of Xerox patents acquired by Google in early 2012, alongside US 6,020,973 (the sibling "Centralized Print Service" case), US 5,933,801, US 6,494,950 and others.

2017‑10‑05 / recorded 2017‑10‑05 — Reel/Frame not retrieved

• Conveyance: Change of Name
• Assignor: Google Inc. → Assignee: Google LLC
• Correspondent: not retrieved.
• Context: change of name only (Google Inc. reorganized into Google LLC under Alphabet Inc.). No change in beneficial ownership.

2022‑09‑07 / recorded 2022‑09‑07 — Reel/Frame not retrieved

• Conveyance: Release by Secured Party
• Assignor: JPMorgan Chase Bank, N.A. (as successor‑in‑interest administrative and collateral agent to JPMorgan Chase Bank) → Assignee named in record: Xerox Corporation
• Correspondent: not retrieved.
• Context: late housekeeping release — a clean‑up of the 2003 security interest recorded ~10 years after Xerox sold the patent to Google. It reflects the assignor's lien record, not ownership of the patent.

Also noted: anticipated expiration 2017‑04‑15 (statutory term end; the patent is expired — legal status "Expired – Lifetime").

Timeline diagram

timeline
    title Ownership of US 5974234
    1997 : Filed by Xerox Corp
         : Inventors assign to Xerox
    1999 : Patent issued
    2002 : Security interest to Bank One
    2003 : Security agreement to JPMorgan Chase
    2011 : Both security interests released
    2012 : Assigned to Google Inc
    2017 : Patent expires
         : Name change to Google LLC
    2022 : JPMorgan release recorded to Xerox

NPE / troll-pattern signals

1. Shell-entity transfer — not present. The only operating→operating transfer is 2012‑02‑16, Xerox Corporation → Google Inc. (reel/frame not retrieved). Google Inc. is a large operating technology company; the 2017 entry is a Change of Name to Google LLC, not a transfer to a licensing vehicle. No "IP/Patents/Holdings/Ventures" entity appears anywhere in the chain.

2. Known asserter in the chain — not present. No assignee matches a public NPE list. Chain assignees are: Gombert/Levine/Mayer → Xerox → (Bank One, JPMorgan — lienholders only) → Google Inc. → Google LLC. No Acacia, Marathon, IV, IPNav, Wi‑LAN, Conversant/Mosaid, Vringo, Pendrell, Innovatio, Round Rock, Erich Spangenberg entity, or other high‑frequency plaintiff appears. No RPX/Unified Patents asserter‑directory hit surfaced for this patent.

3. Repeat correspondent across the chain — unclear / not retrievable. The correspondent of record is not exposed in the authoritative legal‑events text, and I could not pull the Assignment Center images. I therefore cannot confirm or refute a repeat recording attorney. Do not treat the Xerox in‑house / Latham & Watkins correspondents mentioned above as a finding — those names come from unrelated Xerox trademark assignment records, and attributing them to this chain would be fabrication. Action item for the live check: capture the correspondent on each of the six XRX/Google entries; the two 2011 releases plus the 2022 release (three releases from two banks) are the entries most likely to show a single recurring filings agent.

4. Cascading transfers — not present. There is no run of chained LLCs. The only ownership transfers are 1997 (inventors→Xerox), 2012 (Xerox→Google) and 2017 (name change). The 2002/2003/2011/2022 entries are security interests and their releases, which change lien status, not ownership, and must not be counted as chain hops.

5. Pre-litigation transfer — not present / unclear. The 2012 Xerox→Google sale is the only candidate, and the timing does not fit the pattern: the patent went to Google, an operating company, not to an asserter, and I have no evidence Google has asserted this patent. Separately — and not a basis for this signal — Xerox (the seller) had asserted a different set of its own search/query patents against Google and YouTube/Yahoo in litigation around 2009–2010. That is an operating company asserting its own portfolio; the 2012 portfolio sale is best read as part of a broader commercial resolution/relationship rather than an asserter being armed. I flag the possible linkage as unverified.

6. Bankruptcy fire-sale — not present. Xerox Corporation did not enter Chapter 7 or 11. The 2011 and 2022 "release" records are ordinary credit‑facility lien releases, not sale orders from a bankruptcy estate.

7. Privateering — not present. Google acquired the patent for its own portfolio; there is no back‑license or assertion‑on‑behalf‑of‑Xerox arrangement in the record, and no SEC disclosure or press coverage surfaced describing such a structure.

8. Defensive aggregator — not present. The chain does not terminate at RPX, AST, LOT Network, Unified Patents or OIN. It terminates at Google LLC (an operating company). Google is a LOT Network founder, but the patent was acquired directly and is not held by a defensive aggregator. Note the practical effect: the patent expired 2017‑04‑15, so it is now neutralized regardless of holder.

Verdict

Operating-company assertion.

Justification: the ownership chain terminates at Google LLC, an operating technology company, via the 2012‑02‑16 assignment from Xerox Corporation to Google Inc. and the 2017‑10‑05 change of name, with the original 1997‑04‑15 inventor assignment to Xerox as the only other true ownership transfer. Every intermediate record (Bank One 2002‑06‑28, JPMorgan Chase 2003‑10‑31, the two 2011‑09‑23 releases, and the 2022‑09‑07 release) is a security interest or its discharge and does not move title; no NPE, shell LLC, or defensive aggregator appears anywhere in the chain. Caveat: I found no evidence that Google has asserted this particular patent, and the patent expired 2017‑04‑15 — so the accurate reading is "held (and now lapsed) by an operating company," not "actively asserted."

Verification link: https://assignmentcenter.uspto.gov/ (search patent number 5974234) — mirror: https://assignment.uspto.gov/patent/index.html

Two fields to capture when you run the live pull, since I could not: (a) the reel/frame for each of the eight recorded entries (all marked "not retrieved" above), and (b) the correspondent of record, particularly on the three secured‑party releases (2011‑09‑23 ×2 and 2022‑09‑07), which are the entries most likely to reveal a recurring filings agent.

I'll research the patent's cited references and prior art. Let me run several searches.

Let me search for the patent's front-page "References Cited" and citation tables.

Let me try to locate the patent's front-page "References Cited" listing directly.

Prior-Art Analysis — U.S. Patent No. 5,974,234

Patent: U.S. 5,974,234 — Centralized print server for interfacing one or more network clients with a plurality of printing devices
Inventors: Jonathan D. Levine; Barry G. Gombert; James L. Mayer
Assignee (original): Xerox Corp. | App. No.: 08/842,546 | Filed: 1997-04-15 | Granted: 1999-10-26
Claims: 13 | Status: Expired – Lifetime (anticipated expiration 2017-04-15)
Governing law: Because the application was filed 1997-04-15, the pre-AIA version of 35 U.S.C. § 102/103 applies (the AIA first-inventor-to-file provisions govern applications filed on or after 2013-03-16).

⚠️ Critical methodology caveat — read this first

I could not retrieve the examiner's front-page "[56] References Cited" table for U.S. 5,974,234. The authoritative full text supplied for this analysis (fetched from the Google Patents page) is truncated before the front-page citation block. Multiple targeted searches of the USPTO/Google Patents/FreePatentsOnline records did not surface the [56] field or the examiner's cited-reference list.

What that means for this report:

So the table below is not the examiner's citation list. It is the set of patent references that applicant/patent itself cites as background — which in this patent is effectively the entire cited-art record visible to me. If a definitive § 102 study is needed, the front-page [56] block must be pulled from the USPTO PatentCenter/PAIR file wrapper or the granted-patent PDF. I am flagging this rather than presenting the specification citations as if they were the examiner's citations.

Also note: the specification cites several references without reciting an issue date (Salgado, Bonk, Mensing, Kovnat, Sanchez). I have not auto-filled those dates; where I state a date below, it is either quoted from the patent text or is my own external knowledge, which I mark as such.

1. References cited in the specification (patent documents)

These are the references the patent text itself sets out. Dates in the "Date" column are exactly as printed in the patent.

2. The only genuinely close references, and why none appears anticipatory

The claims of '234 are not directed to printing per se. Claim 1 requires the combination of:

• (a) a single application layer developing a "command expression" from a client request;
• (b) a communications interface with first and second connectivity modules to first and second printers respectively; and
• (c) a routing interface selecting which connectivity module receives the command expression.

None of the references in §1 discloses element (c) (the routing/API abstraction), and none discloses the "single application layer → routing interface → per-device connectivity module" division of labor that the specification identifies as the invention (FIGS. 6A/6B, and the "Numerous features" section).

Closest-reference mapping (preliminary):

Bottom line for §1: on the available record, no specification-cited reference, taken alone, discloses all elements of any one of claims 1–13. They are properly characterized as § 103 technological-background art, not § 102 anticipatory art. Note also that a reference that "discloses that…" in a Background section is a characterization by the applicant, and I have not independently verified the reference texts; where the two could diverge, the reference's own specification controls.

3. Family member — must not be mistaken for prior art

The search record shows EP 0 874 306 A3 (Xerox Corp.) as the European counterpart of this application, and the EPO register lists US 5,974,234 A within the EP 0874306 family (alongside BR 9801021 A and JP 10-301732 A). EP 0 874 306 is the same invention/disclosure, not separate prior art. It appeared in the EP 0 965 908 A3 search report as a "P, A" citation against that application — i.e., '234/EP 0874306 is prior art to others, not the reverse.

4. Forward citations — not prior art (flagged to prevent error)

Search results repeatedly surfaced entries where US 5,974,234 A appears as a cited document in later patents/applications — e.g.:

• US 2003/0081245 A1 (Hewlett-Packard Development Co.; priority 2001-10-30) — cites US 5,974,234 A
• EP 1259887 A4 ("Managing Print Jobs") — lists [X] US 5974234 A as an examination citation against its own claims
• US 6,931,447; US 6,771,381; US 2004/0008369 A1; US 10,768,871 B2 — all list US 5,974,234 A in their "Cited By"/prior-art tables

These postdate the '234 filing/priority date (1997-04-15) and therefore cannot be § 102 prior art against '234. They are relevant only as evidence of the field's development and as potential § 103 "secondary" context, not as anticipatory references. To be explicit per the operating rules: I am reporting these because they appeared in the search results and because § 102 analysis is often confused by forward citations — they are not eligible references against this patent.

5. What remains to be done for a definitive answer

To complete a rigorous § 102 study you would need, none of which I could obtain:

1. The front-page [56] "References Cited" list from the granted patent (USPTO PatentCenter / PAIR file wrapper / the granted-PDF front page) — this is the examiner's citation record and is the primary source the task asks for.
2. The file-wrapper "References Cited by Examiner" list, which frequently differs from the specification's background citations.
3. Full texts of U.S. 5,220,674 and U.S. 5,179,637 to test claims 1, 3 and 4 properly against them.

I state plainly that I do not have high confidence that the list above is co-extensive with the examiner's citation list, and I have not fabricated an examiner list to fill the gap.

One-paragraph summary

The references I can verify for U.S. 5,974,234 are those cited in its own specification: fifteen U.S. patents on multifunctional digital copying, print queues, electronic precollation memory, and networked printing — of which U.S. 5,220,674 (Morgan et al., local-area print server, issued Jun. 15, 1993) is the most pertinent to claim 1 — plus two incorporated PDL patents (Bonk; Mensing), the Salgado VCM patent, the Kovnat scan-to-file application, a copending Grzenda application, two same-day Levine companion applications, and the 1990 PostScript Language Reference Manual. None of these appears to disclose all elements of any of claims 1–13, and none discloses the claim-1 routing interface, the claim-6 HTTP server layer, or the claims 8–11 database/caching features; they are best treated as § 103 background art rather than § 102 anticipations. The examiner's [56] citation table is not in the material I was able to retrieve, and that limitation — not an absence of art — is the reason the present analysis should be treated as provisional.

I'll ground this analysis in the actual prior-art record for this patent rather than working from memory. Let me pull the cited references and their characterizations.

Let me pull the front-page "References Cited" list and a couple of the most relevant cited references.

Obviousness Analysis — U.S. Patent No. 5,974,234 under 35 U.S.C. § 103

Governing frame note. This patent was filed 1997‑04‑15, so it is pre‑AIA: the operative test is § 103(a) as it read then — whether "the subject matter as a whole would have been obvious at the time the invention was made to a person having ordinary skill in the art." That temporal anchor (April 1997) matters: post‑filing art cannot be used. Concretely, items like US 5,832,191 (HP, filed 1997‑04‑30) and US 6,453,127 / US 2001/0055492 (priority 1997‑09‑26) that surface in the citation neighborhood are not prior art here and I exclude them.

1. What I treated as "the Prior Art section"

Because the record supplied truncates the front-matter citation list, I anchored on the two things that are in the record:

1. The patent's own Background (authoritative; applicant's admissions are usable prior art). It expressly characterizes: (a) HTML/HTTP as an interface for control and status of print/document machines, including CGI and dynamic page generation; (b) HP's arrangement of clients ↔ a server ↔ document processing devices requiring a proprietary HP card; and (c) a "Middleware" approach in which "an application layer communicates with a connectivity layer," with Middleware comprising "a plurality of modules, each of which modules facilitates the transfer of operation requests between the clients and one or more target devices."
2. The Google Patents "prior art keywords" for this page — server, printers, communicating, information, application layer — which confirm the field is network print server architecture.

I verified content for US 5,220,674 (Morgan et al., Jun. 15, 1993) from the issued PDF (patentimages.storage.googleapis.com/d7/7a/22/808af4c2e27efa/US5220674.pdf; patents.google.com/patent/US5220674A). For US 5,179,637 (Nardozzi), US 5,113,494 (Menendez), US 5,164,842 (Gauronski), US 4,947,345 (Paradise), US 5,551,686 (Sanchez), and US 5,579,447 (Salgado) I have only the characterizations in the Background and secondary snippets; see Caveats.

2. Person of ordinary skill in the art (April 1997)

A bachelor's degree in CS/EE (or equivalent) plus ~2–4 years' experience in network software, client/server or network printing, or a master's with less experience. The POSITA would be familiar with: TCP/IP; HTTP/HTML and CGI; SNMP and the RFC 1759 printer MIB; LPR and other print protocols; print queues and job control; layered protocol stacks (OSI) and layered software architecture; C++/OOP and device-class abstraction; and API/driver design. This is not a specialized skill set — it is exactly the profile the patent's own specification assumes (it discusses all of these as background).

3. Claim-construction points that drive the analysis

Net: claim 1 is, functionally, "application layer → API/dispatcher → per‑device communication modules → plural printers." That is a software-architecture claim, and architecture claims are precisely where KSR's "predictable results from known elements" reasoning bites hardest.

4. The references relied on

R1 — US 5,220,674 (Morgan et al., DEC, 1993) — primary reference. Discloses a local area print server 10 between plural printing clients 18a, 18b … and plural printers 16a, 16b. Structure: a network facility (client side), a driver (printer side), a server job controller selecting/queuing requests, a program control that "insures that the information forwarded to the printers is in a syntax understandable by them" (i.e., per‑device translation), a resource manager, a status collector, and a system manager. Its LAPS protocol includes CONNECT, DATA, CONTROL ("set and change the parameters by which the printing system operates"), END‑OF‑JOB, RESOURCE‑STATUS, STATUS, and RESOURCE‑FAULT. It supports status queries ("whether a particular printing request has been accepted … and later serviced"; pages printed), add/delete printing clients, cancelling printing requests, and promoting a high‑priority request above earlier ones. The status collector keeps state and forwards status messages to configured destinations.

R2 — Admitted web/HTTP prior art (Background). HTML/HTTP for machine control/status; CGI invocation with user‑supplied parameters; static + dynamically computed pages; browser compatibility (Netscape 2.01+ / Microsoft "nashville").

R3 — Admitted "Middleware" prior art (Background). Application layer ↔ connectivity layer via a plurality of per‑target modules; the patent's stated improvement is only to shift selection of device values from the application layer down to the connectivity layer (FIG. 6B vs FIG. 6A).

R4 — Admitted HP proxy arrangement (Background). Clients ↔ server ↔ devices, but devices require a proprietary card — establishing the "works with devices that have and don't have embedded HTTP servers" design goal as an admitted, pre‑existing problem.

R5 — US 5,179,637 (Nardozzi, 1993). Print jobs from a source distributed among a set of print engines via a scheduler that interprets job control information and passes files to an image processor — cumulative evidence of multi‑printer job routing.

R6 — US 5,164,842 / US 4,947,345. Print‑queue management/proofing in an electronic printing system and a print queue for a multifunctional printing system — cumulative evidence that queue state/settings management was routine.

(R5/R6 used only as "state of the art" corroboration; the core case rests on R1–R4.)

5. The obviousness case

Ground I — Claims 1–5, 8–11 and 12: R1 + R2 + R3 (+ R4 as need)

Claim 1 mapping:

Claim 6 (HTTP layer): supplied essentially 1:1 by R2 — HTML/HTTP for control and status, CGI for parameterized output.

Claims 3–5 (queue‑job state; machine settings; add/delete device): R1 expressly discloses status queries about a print request, the CONTROL message to set/change operating parameters, and the ability to add/delete printing clients (the analogous add/delete operation). Claim 4's "machine settings" is met by CONTROL/site‑settable parameters.

Claims 8–11 (database + age/periodic refresh): see Ground III.

Motivation to combine (KSR/TSM): The applicant's own Background supplies the motivation in express terms — the desire for a platform‑neutral control/status interface (lower development cost, no per‑OS client software, multi‑lingual, server‑side upgrades), and the express desirability of a proxy "capable of performing a host of Internet operations among document processing devices some of which include embedded HTTP servers and others of which do not." That is a statement of the problem and of the desired solution — the strongest form of design‑need evidence. R1 supplies the multi‑printer server skeleton and the command repertoire; R2 supplies the neutral browser/HTTP front end; R3 supplies the two‑tier application/connectivity split with per‑target modules. The combination does no more than substitute a known web front end for a known proprietary UI and re‑arrange a known application/connectivity split — predictable results.

Ground II — Claim 1's "single application layer" limitation is not a saving distinction

The Background admits the prior Middleware architecture already had an application layer communicating with a connectivity layer through a plurality of per‑target modules. The patent's asserted advance (FIG. 6B) is that the application layer need only issue a function call with an argument, with value selection delegated to the connectivity layer. Reciting that same division structurally ("single application layer" + "routing interface" + "connectivity modules") is the classic case of claiming an architecture whose only new thing is where code responsibility is placed — a design choice, not a technical advance. Under KSR, "a court must ask whether the improvement is more than the predictable use of prior art elements according to their established functions." Here it is not, absent evidence that the placement produced an unexpected result (none is disclosed; the spec's only asserted benefits are reduced application‑layer code and easy accommodation of heterogeneous devices — both inherent in the known layering).

Ground III — Claims 8–11 (database with age‑stamped / periodic refresh) are obvious optimizations

Age‑based freshness and periodic refresh of a cached copy of remote state is the routine cache‑coherency technique of the era (HTTP proxy caching; SNMP polling). R1's status collector already "maintain[s] a wide range of state information regarding virtually every subsystem with which the server communicates" and reports to interested components. Adding a database cache in front of that collector, refreshed when data exceeds a threshold age or on a timer, is (i) a known technique to improve a similar device in the same way (KSR), and (ii) at most an obvious design choice between the two expressly claimed alternatives (age‑triggered vs. periodic) — which are themselves the two conventional polling/caching modes. No unexpected result is disclosed; the spec's stated benefit (avoiding a round trip when the data is "sufficiently current") is the definition of a cache.

Ground IV — Claim 7 ("at least one, but not all, printers has its own HTTP server")

This is a capability/backward‑compatibility claim. The motivation is admitted and explicit in the Background: HP's comparable product required a proprietary card in every device, and it "would be desirable" to serve devices with and without embedded HTTP servers. Once the POSITA builds a proxy whose purpose is to normalize heterogeneous devices (Ground I), supporting a mixed population — some with embedded web servers, some without — is the predictable result of that purpose, and KSR's "design incentive / market pressure / obvious‑to‑try" rationales apply directly. Nothing in the claim requires any particular technical means for the mixed case.

Ground V — Claim 12 (and claim 13)

Claim 12 is the HTTP/Internet‑context independent claim; per the earlier summary section, the record truncates claim 12 mid‑sentence and omits claim 13, so the following is qualified. On the text available, claim 12 recites (i) an HTTP server layer receiving a client request for information about a document processing device and (ii) a single application layer. Those two elements are supplied by R2 and R3 respectively, on the same reasoning as Grounds I–II. To the extent claim 12 adds the downstream routing/communications structure, that is claim 1's structure (Ground I). I cannot fully assess claim 13 without its text.

6. KSR rationales, consolidated

7. Counter‑arguments a patent owner would raise, and how they fare

1. "The claims require a single application layer; the prior art is per‑device." Weak — the Background admits a central application layer over per‑target Middleware modules, and "single" is undefined in the spec.
2. "A POSITA would not have modularized the software this way." Weak — device drivers, adapter/proxy patterns, and layered stacks were standard; the Background itself describes the two‑tier split.
3. "The 1997 date — no one had combined web UIs with print servers." Partially answerable: the Background admits HTML/HTTP machine control/status and an HP client‑server‑device arrangement, so the combination was already known in the field; the patent concedes the only gap was card‑free/mixed‑device support.
4. "Non‑obvious because it avoids a proprietary card." This cuts for obviousness: the problem was identified in the art, and the solution (proxy normalization) is the ordinary response.
5. § 112 / functional‑claiming objections. Not § 103, but relevant: several limitations are recited functionally ("for developing," "for directing," "for storing"), which tends to broaden them toward the prior art.

8. Secondary considerations

Per the earlier sections: the patent expired 2017‑04‑15 and no litigation, IPR or other post‑grant proceeding is known. There is therefore no evidence of record of commercial success, long‑felt need satisfied, failure of others, copying, or licensing tied by nexus to the claims. Absent such evidence, secondary considerations do not rebut the prima facie case. (If a nexus argument were made via a commercial product, note the ownership chain Xerox → Google and that the patent appears to have been held/used defensively — reported as recorded, not adjudicated.)

9. Bottom line

On the record available, claims 1–12 (and 13, to the extent ascertainable) would have been obvious under § 103 over Morgan (US 5,220,674) in view of the web/HTTP‑CGI and layered‑Middleware art admitted in the patent's own Background, with the caching claims (8–11) obvious over routine cache‑freshness practice and claim 7 obvious as a design‑choice/backward‑compatibility limitation. The strongest single piece of evidence is the applicant's own Background, which states the problem (neutral, card‑free, mixed‑device Internet access) and describes the two‑tier application/connectivity architecture the claims then recite structurally — precisely the situation KSR targets.

10. Caveats and confidence

• Record gap (material): I could not retrieve the full front‑page "References Cited" list for US 5,974,234; the background and "prior art keywords" were my anchors. My § 103 case therefore leans on R1 (verified full text) + the patent's own admissions (authoritative), not on a reconstructed citation list. I did not invent reference numbers to fill that gap.
• Unverified reference bodies: For US 5,179,637, US 5,113,494, US 5,164,842, US 4,947,345, US 5,551,686 and US 5,579,447 I relied on the Background's characterizations and secondary snippets; I do not assert specific column/line disclosures for them.
• Claim 12 / 13: analysis is qualified because claim 12 is truncated and claim 13 is absent from the supplied record (consistent with the earlier summary section).
• Interpretation of task instruction: I read "the Prior Art section of this page" as the patent's Background prior‑art recitation plus the Google Patents prior‑art keyword set, since no separate machine‑generated "Prior Art" section was present in the supplied material. If a distinct prior‑art list exists on the live page, this analysis should be re‑run against it; the conclusions above are those that follow from the evidence I could actually verify.
• No auto‑correction: identifiers are reported exactly as they appear (e.g., the Brazilian case No. 5974234‑27.2019.4.03.9999 and JP 5974234 are unrelated coincidences, as flagged earlier).