US RE42725

I'll verify against live sources before summarizing.

Let me check the claims and any 2026 Federal Circuit activity.

Ground-truth check performed

I could not reach USPTO PatentCenter or PACER/CAFC docket systems directly with the tools available to me. What follows is grounded in the authoritative full text of US RE42725 that you supplied, plus web results I retrieved (Google Patents, the patent PDF, FreePatentsOnline, SumoBrain) and one secondary litigation source. Where I could not confirm something from an authoritative source, I say so explicitly.

---

Bibliographic summary — US RE42,725 E (USRE42725E1)

Filing-history context. This is a reissue of an earlier patent whose prosecution derived from a family of applications filed around November 2001 (the "Other References" list cites USPTO Office Actions in applications 09/992,198, 09/992,417, 09/992,420, 09/992,183, 09/992,413, 11/993,031, etc.). ⚠️ Uncertainty: the authoritative text you provided does not include the "Related U.S. Application Data" fields, and none of my retrieved sources stated the original patent number for this reissue plainly enough for me to assert it. I will not guess it.

Priority-date discrepancy to flag. Google Patents shows the prior-art date as 2000-11-20, while a Unified Patents portal record for US-RE42725-E1 lists the priority date as 2000-11-19. Per your instructions I am reporting both literally rather than reconciling them.

---

Abstract

The reissued patent carries two abstracts — the original in brackets, then the new reissue abstract:

• Original (bracketed): Pervasive output capability so an information apparatus can pervasively output digital content to an output device. A data output system includes means for obtaining a document object relating to output content managed from the information apparatus and means for obtaining an output device object with attributes corresponding to the output device. Both objects are provided to a server application operated on a server distinct from the information apparatus and the output device, which generates output data using at least partly those objects; the output data is provided to the output device for rendering.
• Reissue (new): An output system providing output service over a network. The system may obtain a document object, an output device object, and one or more job objects (payment, subscription, authentication, identification, instructions, output options). The objects are provided to a server application over a network for rendering at the output device. The server then sends output data over the network to an output controller connected to one or more output devices; the output controller may convert the output data into a file format for output to the output device. The service may send status information and a confirmation of the output job.

---

Plain-language overview of the independent claims

Note on scope: The claim set runs at least into the 90s (I verified claim text through claim 92). I confirmed four independent claims — 1, 74, 82, and 92 — plus dependent claims (e.g., 33, 76–81, 83–91). I cannot rule out additional independent claims beyond those I saw; the sources I retrieved did not give me a complete, verified claims listing.

Claim 1 — Data output method (method claim). A computer-implemented method for rendering output content at an output device: (a) obtain a document object for the content managed from the information apparatus; (b) obtain an output device object with attributes of the output device; (c) provide both to a server application on a server distinct from both the information apparatus and the output device, which generates output data using at least partly those two objects; (d) provide that output data to the output device for rendering. Two structural limitations close the claim: the output device has an output engine that outputs to a medium per device-dependent data it accepts, and a connection to an output controller; and the output controller itself (i) provides at least part of the output device object to the information apparatus, (ii) receives output data from the information apparatus, (iii) passes it to a selected output device, and (iv) provides a user interface for user-implemented modifications of the controller. The fourth element — a controller-side user interface — is an unusual, narrowing requirement added in reissue.

Claim 74 — Method. Another independent method claim concerning an information apparatus with access to digital content and an output controller configured to receive output data. Its dependents shed light on scope: providing job instructions at the information apparatus (76); controller performing image-processing operations such as interpretation, rasterization, scaling, segmentation, color-space transformation, enhancement, color correction, halftoning, compression/decompression (77); output device object attributes for color/grayscale, laser/inkjet, duplex/single-sided, output quality, price per page, quality of service (78); an identification attribute (79); editing content with a browsing application (80); and receiving estimated processing time/status (81). ⚠️ The full text of claim 74's own body was truncated in the source I retrieved; I am describing it only via its title-level subject matter and its dependents.

Claim 82 — Information apparatus (apparatus claim). An information apparatus for rendering digital content at an output system comprising: an output device distinct from the information apparatus, an output controller that is itself distinct from the output device, the information apparatus, and a server over a network distinct from all three. The server generates output data using at least part of a document object and at least partly based on an output device object, and provides the output data for rendering. The output device has a memory buffer, an output engine, and a connection to the output controller, which includes a user interface for user-implemented modifications of the output controller. The information apparatus is configured to: provide a document object; provide an output device object; provide one or more job objects carrying security/identification information and payment/subscription information; and send all of these to the server. The three-object set (document + device + job, with payment/subscription) is the distinguishing feature relative to claim 1.

Claim 92 — Data output software in a computer-readable storage unit. A software claim covering data output software executable by a processor for rendering digital content at an output device, in an output system that includes an output controller with a user interface for receiving user-implemented modifications of the controller (same phrase appearing in claims 1 and 82). ⚠️ The claim body was truncated in the retrieved source; the "computer readable storage unit" format is notable because it is a non-transitory-medium style software claim.

Recurring claim elements worth noting for mapping: (1) a three-entity split — information apparatus, network server distinct from the output device, and output controller distinct from the output device; (2) the controller as the point that hands the device object to the client, receives output data, and forwards it; (3) object-triplet transmission (document object + output device object + job object with payment/subscription/security); and (4) a controller-side user interface accepting user modifications.

---

Litigation / CAFC check (as requested)

• District court: A secondary source (PatSnap litigation blog) reports Flexiworld Technologies v. Xerox Corp., in which Flexiworld asserted US10481847B2, US10642576B2, USRE042725E, and US10846031B2 — i.e., RE42725 was among the asserted patents — and that the case was dismissed with prejudice with the merits unresolved. Treat the case caption, date, and dismissal detail as unverified secondary reporting; I did not confirm them against a court docket.
• CAFC 2026: I found no 2026 Federal Circuit docket, appeal number, or briefing activity for RE42725. Two searches (including one specifically for Flexiworld CAFC 2026 activity) returned nothing. Given that Google Patents lists the patent as expired as of 2022-12-26, a live 2026 appeal on this patent is unlikely — though an appeal could in principle survive expiry. I cannot access CAFC/PACER dockets directly, so this is a negative search result, not a verified absence.
• Reexamination: Unified Patents' June 24, 2025 ex parte reexam institution concerns US RE48,066 (a different Flexiworld patent, data-mining related, asserted against Indeed) — not RE42725. I found no reexamination certificate or AIA proceeding for RE42725.

---

Confidence and caveats

• High confidence: title, inventors, assignee, reissue application 12/684,869, Jan. 8, 2010 filing, Sept. 20, 2011 issue, expired status, classification, abstract text (both versions), and the substance of claims 1, 82, and 92.
• Medium confidence: the exact priority date (2020-11-20 vs. 2000-11-19 conflict noted above) and the full text of claims 74 and 92.
• Low confidence / unverified: the identity of the original (pre-reissue) patent number, the exact total claim count, whether additional independent claims exist beyond 1/74/82/92, and all litigation specifics beyond what I've attributed to the secondary source.

I'll research litigation involving US patent RE42725. Let me run several targeted searches.

Let me run additional targeted searches on specific litigation.

Bottom line

Based on the searches I was able to run (Google Patents, Justia Dockets, PACER Monitor, RPX Empower, Unified Patents, Action-Intell, and the Stanford NPE Litigation Database), I could identify one litigation campaign in which US RE42,725 E is confirmed to have been asserted: Flexiworld Technologies, Inc. v. Lexmark International, Inc. in the Eastern District of Kentucky. Flexiworld filed several other campaigns (Brother, Canon/Epson, Hisense, Sony, HP, LG, TCL, Vizio, Indeed), but the search results I retrieved do not show RE42725 in those complaints' exhibit lists, so I cannot confirm RE42725 was asserted in them. I flag that as unverified rather than assume.

I was cut off before I could exhaust the tools (I hit the step limit mid-research), so treat this as a good-faith partial list, not a certified litigation history.

---

Confirmed litigation — US RE42,725 E

Note on the parallel docket: the E.D. Ky. docket excerpt shows the lead case as 5:22‑cv‑00097‑KKC‑MAS with 5:22‑cv‑00110‑KKC as a member case, and four related Lexmark suits were filed (Action-Intell refers to "four patent-infringement lawsuits" against Lexmark), so RE42725 may appear in more than one of the four related Lexmark complaints. I could only retrieve the exhibit list for 5:22‑cv‑00110‑KKC.

---

Campaigns I could NOT confirm involve RE42725 (flagged, not asserted as fact)

• Flexiworld v. Brother Industries (U.S.A.), Inc., W.D. Tenn. (e.g., 2:22‑cv‑02236 filed 04/15/2022; 2:22‑cv‑02250 filed 04/21/2022) — four Brother suits, reported as settled then dismissed on March 13 (Action-Intell). The NPE Litigation Database lists U.S. Patent Nos. 10,037,178 and 10,768,178 for the Brother cases. I did not find RE42725 in the Brother exhibit lists.
• Flexiworld v. Hisense (2:22‑cv‑00225 / 2:22‑cv‑00228, E.D. Tex., filed 06/24/2022; 1:22‑cv‑04338, N.D. Ga.) — NPE database lists '178‑family patents, not RE42725.
• Flexiworld v. Sony Corp., 2:23‑cv‑00616 (E.D. Tex., Judge Gilstrap) — First Amended Complaint asserts Nos. 9,798,516; 9,042,811; 9,836,259; 10,768,871; 10,162,596; 11,029,903; 11,096,056. RE42725 is not listed. Stayed for settlement (03/2025), then dismissed with prejudice 05/29/2025.
• Flexiworld v. HP, Inc., 4:24‑cv‑02691 (S.D. Tex., Judge Eskridge, filed 07/19/2024) — patents-in-suit not ascertainable from the 21‑exhibit list retrieved.
• Flexiworld v. Indeed, Inc., 1:24‑cv‑01254 (W.D. Tex., reassigned to Judge Albright) — patents-in-suit not ascertainable from retrieved docket.
• Flexiworld v. LG Electronics, 2:25‑cv‑00960 (E.D. Tex., filed 09/18/2025) — asserts '233, '072, '596, '178 family patents per complaint analysis; RE42725 not listed.
• Flexiworld v. TCL Electronics Holdings Ltd. et al., 2:26‑cv‑00229 (E.D. Tex., Judge Gilstrap, filed 03/20/2026) — twelve patents asserted; the complaint analysis identifies the '871, '798, '056, '259, '811, '233, '903, '000, '031, '402, '802, '521 patents. RE42725 is not among them.
• Flexiworld Tech Inc v. Vizio Inc, 8:26‑cv‑02443 (C.D. Cal., filed 08/27/2026) — patents-in-suit not retrievable.
• Earlier Flexiworld assertions (Canon, Epson) — Action-Intell's background piece references Flexiworld having "previously sued Canon and Epson," but I could not retrieve those complaints and cannot confirm whether RE42725 (granted 2011‑09‑20) was asserted in them.

---

Other RE42725-related matter worth noting

• Litigation flag on the patent itself: the Google Patents page for USRE42725E1 carries a "Family has litigation / First worldwide family litigation filed" indicator linking to Darts‑IP (family 22957058). This corroborates that litigation exists in the patent family, but it is not case-level proof for RE42725 specifically.
• Term: Google Patents lists RE42725 as "Expired – Lifetime," adjusted expiration 2022‑12‑26. Practically, this limits any new infringement suits on the patent.
• I did not find any CAFC appeal, ITC Section 337 action, or PTAB IPR/PGR specifically involving RE42725 in the results retrieved. (One retrieved hit was a USPTO P‑TACTs petition document URL that was serving the E.D. Ky. Lexmark docket text; I could not verify what petition, if any, it corresponds to, so I make no representation about PTAB activity.)

---

Verification caveats (important)

1. My searches returned docket summary pages and secondary reporting, not PACER images of the complaints/orders. The only direct documentary confirmation that RE42725 was asserted is the E.D. Ky. D.I. 1 exhibit list for 5:22‑cv‑00110‑KKC showing "Exhibit 4 – USRE42725" and "Exhibit 8 – Claims Chart for USRE42725."
2. Several docket excerpts mix years (e.g., the Action-Intell note "In March, the U.S. District Court for the Western District of Tennessee denied Lexmark's motion to dismiss four patent-infringement lawsuits" appears to conflate the Brother/Lexmark courts). Confirm dates and outcomes on PACER.
3. Because I could not run every planned query, if you need an exhaustive list, the next steps would be: (a) query PACER/Unified Patents' case list for all Flexiworld cases and pull each complaint's exhibit list for "RE42,725"; (b) check Darts‑IP family 22957058; (c) check whether RE42725 was among the patents in the four related Lexmark complaints (5:22‑cv‑00097 and any 5:22‑cv‑001xx companions) and in the 2022 Brother complaints.

I did not find, and am not asserting, any litigation involving US RE42,725 E other than the Flexiworld v. Lexmark matter above.

I'll start by verifying the canonical position and then searching for any PTAB activity on this patent.

Initial searches mostly surfaced activity against a different Flexiworld patent ('402). Let me dig specifically into RE42725 and its asserted family.

Let me pin down RE42725's lineage and check for any challenge specifically naming it.

Proceedings overview

USPTO Open Data Portal returns zero AIA trial proceedings (IPR/PGR/CBM) naming US RE42725 as of the most recent ingest, and my independent web searches found no PTAB petition, institution decision, or Final Written Decision against this patent either — so the count is 0 proceedings: 0 active, 0 claims invalidated, 0 claims sustained, 0 settled, 0 institution denials, and the bottom-line defensive posture is not "the patent is hardened by surviving IPRs" but rather "RE42725 has never been tested at the PTAB at all," which cuts both ways: there is no inter partes estoppel and no Board-canceled claim to hand a defendant, but there is also no FWD you can point to, and — critically — the patent's own face shows an adjusted expiration of 2022-12-26, which caps any live exposure to back-dated damages under 35 U.S.C. § 286 rather than to ongoing royalties.

(No proceeding blocks returned for US RE42725)

No IPR, PGR, or CBM case number exists for this patent in the structured data provided, and I was unable to surface one by search. I am declining to populate the per-proceeding template (petitioner, grounds, panel, FWD, appeal) because doing so would require inventing a proceeding number — the one thing your instructions prohibit. Two verification caveats, stated plainly:

• I could not confirm the reissue parent from the material available to me. The Google Patents record for USRE42725E1 shows application 12/684,869, filed 2010-01-08, granted 2011-09-20, priority 2000-11-20, assignee Flexiworld Technologies Inc. I did not verify the identity of the original patent surrendered by the reissue, so I am not naming it.
• I could not confirm which Flexiworld patents were asserted in which district court case. The complaint analyses I retrieved (e.g., Flexiworld Techs., Inc. v. Xerox Corp., No. 6:23-cv-06371 (W.D.N.Y.), filed 2023-06-29) asserted US 10,140,073, US 10,481,846, and US 10,761,791 — not RE42725. RE42725 does not appear in any of the pleadings or PTAB papers I reviewed. Treat "RE42725 is being actively asserted in litigation" as unverified.

Family-adjacent PTAB activity (explicitly NOT on RE42725)

This is the useful intelligence, because it tells you who attacks this portfolio and how. Every item below is a proceeding on a different Flexiworld patent.

Two data points worth carrying forward: Flexiworld won the only family FWD I could find (IPR2022-00775 on the '257 patent, claims sustained, contingent motion to amend dismissed), and it successfully knocked out a Roku PGR at the institution stage (PGR2021-00111). This is not a patent owner that folds at the Board.

Strategic summary

Claim status: UNTESTED, not canceled and not sustained. Because RE42725 has never been before the PTAB, there is no claim-level disposition to report. I will not characterize any claim of the reissue as canceled, confirmed, or patentable — no FWD, reexamination certificate, or court judgment in my sources addresses these claims. What is visible on the face of the reissue is that the claims were materially rewritten during reissue: the printed text converts original "means for" / "further comprising means for" limitations into "is further configured to" language (visible in the reissue claim text for claims 44 and its dependents, uspto.report/grant/RE42725). That rewrite is a double-edged § 112 issue — patent owner will argue the means-plus-function presumption is rebutted and the claims are structural; a defendant will argue the reissue amendment narrowed scope and implicates the recapture rule and prosecution-history disclaimer. There is no Board or Federal Circuit ruling on either point.

Estoppel landscape: nothing flows from RE42725. Section 315(e)(2) estoppel is proceeding-specific. With zero proceedings on this patent, no petitioner is estopped as to these claims, and — symmetrically — a defendant facing assertion of RE42725 enjoys the full menu of prior art, including art that Flexiworld has already litigated to a standstill on sibling patents. Note the practical asymmetry in Flexiworld's favor: because the family's IPRs run against later continuations (the '257, '114, '064, '233, '402, '903, '031 patents), Flexiworld's losses (if any) do not bind it on the reissue, and Unified/Roku's expenditures are sunk on other claim sets. A defendant here would be litigating against language — the "output controller," "output device object," "document object," and "pervasive output" framework — that has been in Flexiworld's specification since the 2000-11-20 priority date and only later got early-2000s prior art such as Yamaguchi, Kammer, Moore, Kemp, Keeney, and Vatland thrown at it.

Pattern signals. (1) Repeat petitioners: Roku filed at least five PTAB petitions across the portfolio (PGR2021-00111, PGR2021-00112, IPR2021-00714, IPR2021-00715, IPR2022-01114) after being sued in Flexiworld v. Roku, No. 6:21-cv-00680-ADA (W.D. Tex.), filed 2021-06-28 and settled/dismissed 2022-10-28. Lexmark then filed two more (IPR2023-00845, -00846) after Flexiworld v. Lexmark, No. 5:22-cv-00110 (E.D. Ky.), filed 2022-04-29. (2) Defensive aggregator: yes — Unified Patents is squarely in the chain, both as IPR petitioner (IPR2022-00775) and as ex parte reexam requester (90/014,721). Flexiworld's IPR papers even attacked Unified's standing/membership in the '257 case. (3) Patent owner posture: Flexiworld litigates broadly (Roku, Lexmark, Brother, Hisense, Xerox, and others) but resolves cases quickly — Brother dismissed 2023-03-13, Hisense dismissed 2023-04-07, Roku dismissed 2022-10-28 — which is the behavior of a licensor monetizing settlements, not a patentee seeking appellate claim-construction precedent. I found no Federal Circuit appeal of any Flexiworld-related FWD in my sources; if an appeal of the 2023-11-01 '257 FWD exists, I did not locate it, and I am not representing that it does or does not.

Recommended next steps

1. Do not expect an IPR to save you on RE42725 — expect expiration to. The Google Patents legal-status record shows "Expired – Lifetime," adjusted expiration 2022-12-26. For a defendant being asserted today (2026-09-15), prospective injunctive relief and ongoing royalties should be off the table; the realistic exposure is back damages inside the § 286 six-year window measured against infringement before expiration. That framing, not an invalidity case, is likely your cheapest early motion (partial summary judgment on damages period) and your strongest settlement lever.
2. If you still need an invalidity posture, an IPR is legally available but tactically odd. The Board can institute on an expired patent, but a trial instituted in late 2026 would produce a FWD in 2027–2028, long after the patent lapsed — no estoppel benefit, no prospective freedom-to-operate value, and claim construction shifts to Phillips for expired claims. If you go this route, budget for the § 315(b) one-year bar running from service of the complaint, and note that Flexiworld has a documented habit of settling before institution (IPR2022-01114, dismissed 2022-11-28) — which moots your petition without giving you a merits ruling.
3. Mine the sibling FWDs rather than guessing. The single best-sourced Flexiworld merits document is the IPR2022-00775 Final Written Decision of 2023-11-01, which held no challenged claims of the '257 patent unpatentable and dismissed the contingent motion to amend. Read it to learn (a) which prior-art combinations failed and why, and (b) how the Board construes the "output device object" / "wireless discovery" vocabulary that recurs across this family. Cite it via the Unified Patents case portal and USPTO PTAB E2E; docket materials are also mirrored at Patexia and Docket Alarm.
4. Verify assertion status before doing anything expensive. Neither the ODP block nor any source I retrieved ties RE42725 to a live complaint. If you hold a demand letter or complaint citing RE42725, confirm the asserted claim numbers against the printed reissue text — the reissue renumbered and rewrote the claims relative to the original patent, so a notice letter quoting pre-reissue claim language may be quoting claims that no longer exist. Get the reissue file history (application 12/684,869) first; the § 251 recapture analysis and the reissue-amendment prosecution history are the highest-leverage intrinsic materials here.
5. Sourcing gaps I could not close, flagged honestly: (a) the reissue parent patent number; (b) whether any Federal Circuit appeal arose from Flexiworld family FWDs; (c) whether any CBM review was ever filed against the reissue (CBM eligibility turns on whether the claims are "financial in nature" — note the reissue's G06Q20/32 and G06Q20/3224 classifications covering mobile-payment and location-dependent transactions, which would be the hook, but I found no CBM filing). Treat each as open, and confirm via USPTO PTAB E2E and CourtListener before relying on the negative.

I'll research the assignment/ownership chain for RE42725 across USPTO Assignment Search, Google Patents legal events, and related sources.

Important lead found — a Samsung agreement and Flexiworld corporate details. Let me dig into the specific assignment records.

Ownership & Assignment Chain — US RE42,725 E1 ("Output service over a network")

Sourcing limitation stated up front. I could not open assignmentcenter.uspto.gov or assignment.uspto.gov in this session. Everything below is grounded in (a) assignment instruments and reel/frame citations that appear verbatim inside Flexiworld's own court and PTAB filings, which I did retrieve, and (b) Google Patents' assignee field. The RE42725-specific reel/frame entry is therefore unverified, and I say so rather than guess it. Verify at assignmentcenter.uspto.gov and assignment.uspto.gov/patent/index.html.

---

Inventors

Basis for the employer call: a Revocation and Reappointment of Power of Attorney / Statement under 37 C.F.R. § 3.73(b) in the family record states "Flexiworld Technologies, Inc. states … that it is the assignee of the entire right, title, and interest … by virtue of an assignment from each of the inventor(s)," and is signed by "William Ho Chang, President and Chief Technical Officer." An inventor signing the assignee's § 3.73(b) statement as an officer is direct evidence that Chang was a Flexiworld principal, not an outside contractor. Liu is named as co-inventor and co-assignor on every instrument I located. Source: PTAB petition document 1553925.

Unusual-pattern check — NOT present, and notable for it. The classic fire-sale precursor (all inventors out within 12 months of filing) does not appear here. The opposite: Chang and Liu remained named assignors on Flexiworld instruments executed as late as 10 January 2011 — roughly a decade after the priority filing — and Flexiworld is still asserting the family in 2026. Caveat: I could not confirm formal employment titles for Liu, and I did not find a corporate registration record establishing Flexiworld's incorporation date relative to the 2000-11-20 provisional.

---

Original assignee

Flexiworld Technologies, Inc. — a Washington corporation, mailing address of record 3439 NE Sandy Blvd., Suite 267, Portland, Oregon 97232 (stated in the assignment instrument text). Google Patents lists it as both original and current assignee of RE42725 — i.e., no recorded post-issuance transfer to a third party surfaced.

Did they ship a product? Partial, unverified. Flexiworld's own PTAB exhibit list in PGR2021-00112 includes three commercial-life exhibits — "Article from Portland Business Journal, dated April 5, 2002," "Article from Portland Business Journal, dated April 20, 2003," and "Flexiworld website homepage." That establishes a real early-2000s operating business with press coverage and a public website, but I could not retrieve those exhibits, and I found no verifiable shipping product embodying the RE42725 claims. I also note that Roku's petition attacked the family for lack of written description over the information-apparatus/output-device distinction — an argument that only makes sense if the commercial embodiment was thin.

Primary line of business today: patent licensing and enforcement. The E.D. Tex. docket in Flexiworld v. Roku records an order requiring Flexiworld to produce "all license and assignment agreements related to any Flexiworld patents and/or patent applications" — the discovery footprint of a licensing operation, not a manufacturer. Flexiworld also sent pre-suit notice letters (e.g., 23 July 2021 and 29 October 2021 to Xerox) and settled a string of 2022–2025 cases.

Current status: operating. No bankruptcy — I found no Chapter 7/11 filing, no assignment-in-bankruptcy, and no receivership for Flexiworld Technologies, Inc.

Partial divestiture worth flagging. Per the court's 6 June 2022 decision in Flexiworld Techs. v. Roku Inc., No. 6:20-cv-00819-ADA (W.D. Tex.), Flexiworld assigned four specific items to Samsung: US 7,941,541 (the '541 patent), the pending '958 application, a continuation application, and a second continuation application. Roku attacked Flexiworld's standing by arguing the Samsung agreement swept more broadly; the court agreed with Flexiworld and held the '064 and '066 patents were not assigned. ⚠️ I could not determine the Samsung agreement's execution date, and I could not determine whether RE42725 or its parent (09/992,420) falls inside its scope. Given that a defendant has already litigated this exact title question once, this is the single highest-value ownership item to verify. Sources: CourtListener opinion, W.D. Tex. ECF 198.

---

Assignment timeline

⚠️ The USPTO Assignment Center returned no directly retrievable record to me, so I cannot list a RE42725-specific reel/frame. What follows separates verified family-record data from inferred chain position. This is not a complete recorded-assignment history and should not be cited as one.

A. Verified instrument text (family, not RE42725 itself)

• ASSIGNMENT (Application Already Filed) — assignors William Ho Chang and Christina Ying Liu → assignee FLEXWORLD TECHNOLOGIES, INC., a Washington corporation, 3439 NE Sandy Blvd., Suite 267, Portland, OR 97232. Consideration $1 "and other good and valuable consideration." Covers application 10/053,651 (issued as US 7,609,402). Executed at Portland, Oregon, 10 January 2011. Attorney's docket FLEX 2406. The accompanying power-of-attorney paper carries docket FX1308. Retrieved from the PTAB petition record.
• Reel/Frame 028733/0064 — assignment of the '402 Patent "from inventors Chang and Liu to Flexiworld," cited in Flexiworld's own complaint (via RPX litigation document 15143102). Reel 028733 is consistent with a ~2011 recording, contemporaneous with the January 2011 instrument above.
• Reel/Frame 042385/0202 — assignments of both the '072 Patent and the '178 Patent from Chang and Liu to Flexiworld — a single instrument recorded against two properties (batch recording).
• Reel/Frame 039816/0200 — assignment of the '596 Patent from Chang and Liu to Flexiworld.

B. Chronological chain position (partly inferred)

• 2000-11-20 — Provisional 60/252,682 filed naming Chang and Liu. Conveyance: none recorded at this stage / rights initially vested in inventors.
• 2001-11-18 to 2001-11-19 — Non-provisional applications filed, including 09/992,420 (issued as US 7,318,086). Conveyance: inventor→Flexiworld assignment — execution and recording date not verified; the January 2011 confirmatory instrument pattern suggests Flexiworld re-papered title years later.
• 2008-01-08 — US 7,318,086 issues, assignee Flexiworld Technologies, Inc.
• 2010-01-08 — Reissue application 12/684,869 filed (flexiworld as assignee/consent-giver).
• 2011-01-10 — Confirmatory assignment executed by Chang and Liu in favor of Flexiworld (docket FLEX 2406) for at least one sibling patent. Context: internal title cleanup / prosecution-record hygiene, executed roughly a decade after filing and in the same window as the 2010 reissue filings — not a pre-litigation transfer.
• 2011-09-20 — RE42,725 E1 issues.
• Undated, ~2009–2012 (unverified) — Samsung transaction: '541 patent + '958 application + 2 continuations assigned out of Flexiworld. Context: outright portfolio sale. Scope as to RE42725 unverified.
• 2020-08 onward — no assignment; enforcement begins.
• 2022-12-26 — adjusted expiration.

C. Correspondent of record. I could not retrieve the correspondent field from any reel/frame record, because I could not open the Assignment Center. Two firms recur in Flexiworld's prosecution and enforcement papers, which is adjacent but not the same thing: Kolisch Hartwell, PC (firm of record on the issued patent) and Nelson Bumgardner Conroy P.C. — C. Austin Ginnings, Reg. No. 62,706, 15020 South Ravinia Ave., Suite 29, Orland Park, IL 60462, who filed Flexiworld's papers in PGR2021-00112 (docket: 1548112). Patrick J. McKeever, Reg. No. 66,019, Perkins Coie LLP appears on a joint Flexiworld/Roku filing, but that is Roku's counsel, not Flexiworld's. I make no finding on assignment-recording correspondence — that field is precisely the one I could not read, and it is the field most worth pulling first.

D. Contradictions with the previously generated sections — flagged as required:

1. Reissue parent. The summary section said the pre-reissue patent number "could not be confirmed" and declined to name it. The prior-art section states RE42725 is a reissue of US 7,318,086 (application 09/992,420, filed 2001-11-18). These conflict. The 7,318,086 identification is corroborated by FPO's cited-reference list (7,318,086, "System for mobile and pervasive output," Chang et al., 2008-01-08) and by the family's docket numbering, but I did not independently read the reissue front page's Related U.S. Application Data field. Treat the parent as probable, not confirmed.
2. Xerox and RE42725. The litigation section attributes to a PatSnap secondary source that Flexiworld v. Xerox asserted "US10481847B2, US10642576B2, USRE042725E, and US10846031B2." The PTAB section says the Xerox complaint (6:23-cv-06371, W.D.N.Y., filed 2023-06-29) asserted US 10,140,073, US 10,481,846, and US 10,761,791 — not RE42725. The Xerox complaint text I retrieved this session counts the '181 and '071 patents. The two prior sections cannot both be right, and my own retrieval favors the second. This matters for the NPE verdict below because it is the only claimed pre-2022 Xerox nexus to RE42725.
3. Priority date (2000-11-19 vs 2000-11-20) — unresolved in both prior sections; irrelevant to ownership but noted.
4. Claim numbering (independents 1/74/82/92 vs. an apparent independent system claim 56 and software claim 64) — flagged in the obviousness section; unresolved.

---

Timeline diagram

timeline
    title Ownership of US RE42725
    2000 : Provisional 60252682 filed by Chang and Liu
    2001 : Non provisional applications filed
    2008 : Parent patent 7318086 issues
    2010 : Reissue application 12684869 filed
    2011 : Confirmatory assignment executed Jan 10
         : RE42725 issues Sep 20
    2020 : Flexiworld enforcement campaign begins
    2022 : Samsung standing challenge rejected
         : Patent term expires Dec 26

(Note: the chain shows no transfer event between 2011 and expiry. That absence is the central ownership finding.)

---

NPE / troll-pattern signals

Additional signal not in your template — standing/ownership cloud (worth its own line). Flexiworld's title has already been litigated once: Roku challenged standing based on the Samsung assignment, and Epson obtained a discovery order compelling production of "all license and assignment agreements related to any Flexiworld patents and/or patent applications." That is direct, on-the-record evidence that defendants in this portfolio treat Flexiworld's chain of title as contestable. If you are on the defense side, this is the cheapest non-invalidity attack available and it does not require the patent to be unexpired.

---

Verdict

NPE — moderate confidence.

Flexiworld Technologies, Inc. is itself the current assignee, a documented non-practicing asserter on two independent public NPE directories (Stanford NPE Litigation Database; Korea IP-Navi 2022 NPE Guide, listed alongside Acacia and IP Edge), and it generates revenue through notice letters, licenses, and serial infringement suits rather than a verified product embodying the claims — one strong signal. It does not score on the mechanical NPE tells: no shell-entity transfer, no cascading LLC chain, no pre-litigation re-papering, no bankruptcy sale, no defensive aggregator terminus — the chain is a single inventor→company assignment and it stays there. I decline the higher-confidence label precisely because the archetypal evidence (reel/frame showing a transfer to a licensing-only LLC) is absent, not merely unverified, and I could not query the Assignment Center to confirm there is no late-recorded transfer lurking.

Verification links: USPTO Assignment Center · legacy Assignment Search · search by patent number RE42725, and cross-check the reissue's parent application 12/684,869 (and 09/992,420) — reel/frame entries for a reissue are frequently recorded against the reissue application number, not the patent number, which is a common reason a patent-number query appears to return nothing.

Priorities if you need the definitive chain (in order): (1) pull the Assignment Center record for 12/684,869, not just RE42725; (2) obtain the Samsung agreement and its Exhibit A to test scope against RE42725 — this is the only demonstrated title risk; (3) confirm the reissue's Related U.S. Application Data against the printed front page to settle the 7,318,086 question that the earlier sections left contradictory.

I'll research US patent RE42725 and its cited prior art references.

Let me verify details on the key anticipatory references.

Prior-Art Analysis — US RE42,725 E1 ("Output Service Over a Network")

1. Patent identification (verified, literal)

Sources: https://patents.google.com/patent/[USRE42725](/patent/USRE42725)/en ; https://patents.google.com/patent/USRE42725/en#1 (claims) ; https://www.freepatentsonline.com/RE42725.html ; https://uspto.report/patent/grant/RE42725 ; https://www.sumobrain.com/patents/us/Output-service-over-network/RE42725.html ; https://insight.rpxcorp.com/patent/USRE42725E1 ; reissue front page PDF: https://patentimages.storage.googleapis.com/b5/58/61/ae2930d4a51814/USRE42725.pdf

Everything below is keyed to RE42,725 E1 only. It is frequently confused with other Flexiworld reissues in the same family (RE41,532; RE41,882; RE42,828; RE43,181; RE48,066; RE49,176) — those are different patents and are excluded here.

Two record quirks I am reporting literally, not correcting:

• Some family listings show the priority date as 2000-11-19, while Google Patents shows the prior-art date as 2000-11-20 and the provisional (60/252,682) is listed as filed 2000-11-20. Both appear in the record.
• Claim 1 as reissued contains the original typo history .Iadd./. [.sewer.] .Iadd.server .Iaddend. — i.e., the amendment corrected "sewer" → "server."

---

2. The threshold that drives the whole analysis

For §102 purposes, every cited reference must be measured against the effective date of 2000-11-20 (provisional 60/252,682). I therefore split the face-of-patent citations into two groups:

• Group I — potentially §102(a)/(b)/(e) art: US patents and foreign publications whose filing/priority date precedes 2000-11-20. (Note: a US patent that issued after 2000-11-20 is still §102(e) art if it was filed before that date — this is true for a large share of the list below, e.g. US 6,452,692, US 6,473,800, US 6,648,650.)
• Group II — not §102 prior art for this patent: references whose filing/publication post-dates 2000-11-20, including the applicant's own same-family items that appear on the face of the reissue (US 7,944,577; US 7,318,086; US 6,947,995; US 2008/0318602; US 2009/0002760; US 2009/0070411; and US 7,593,123 Sugahara, whose filing date I could not verify). These were listed for disclosure/prosecution reasons, not because they anticipate.

I could not open the USPTO PatentCenter certified front page in this session; the citation inventory below is taken from four independent mirrors of the front page (FPO "US Patent References," uspto.report "References Cited," SumoBrain "Domestic Patent References," Google Patents). Where I have not verified a reference's filing date, I say so rather than fill it in.

---

3. Most relevant prior art (Group I) — detailed

3.1 US 5,867,633 — Taylor, III et al., "Method and apparatus for processing and printing documents"

• Citation / dates: US 5,867,633 A; issued 1999-02-02 (the issue date is confirmed in a PCT search report citing "US 5,867,633 A (TAYLOR, III et al.) 02 February 1999"), https://ptacts.uspto.gov/ptacts/public-informations/petitions/[1549999](/patent/1549999)/download-documents and https://uspto.report/patent/grant/[5867633](/patent/5867633)
• Disclosure: A client supplies a document to a networked image server; the image server performs the image-processing/formatting operations requested (the record shows an ImageHandle / ConfigureImage interface by which the client "informs the image server of the image processing operations (formatting options) to be performed on the image"), and the processed document is then delivered to a printer/output device.
• Potentially anticipating claims: 1, 2, 4, 5, 7, 8, 30–33, 44, 48, 61–63 — and, most damagingly, the pre-reissue (narrower-amended) claim 1, which did not require the output-controller/UI limitations. Element map: client-held document → document object; server distinct from client and printer performing conversion → server application generating output data; delivery to printer → providing output data to the output device for rendering; image-processing operations at the server → at least partial raster image processing (claims 7–8).
• Corroborating evidence: a PCT search report in the record of a related Flexiworld-family case categorizes US 5,867,633 as "X" (novelty-destroying, alone) against a claim set numbered 1, 2–5, 10–11, 13–19, 23–24, 26–27, 29–39, 42–43 — a claim set that maps almost one-for-one onto RE42,725's claim structure. Caveat: I could not confirm in this session that this particular ISR/written opinion belongs to RE42,725's own family branch, so treat it as strong corroboration, not as the examiner's finding in this reissue.

3.2 US 5,862,321 — Flynn & Lamming (Xerox Corp.; later Cloud Satchel), "System and method for accessing and distributing electronic documents"

• Citation / dates: US 5,862,321 A; application 08/493,376, filed 1995-06-21; priority 1994-06-27; issued 1999-01-19. Confirmed at https://patents.google.com/patent/[US5862321A](/patent/US5862321A) and https://www.sumobrain.com/patents/us/System-method-accessing-distributing-electronic/[6144997](/patent/6144997).html
• Disclosure: A file server holds electronic documents and a document reference/token for each; a portable device carries only the lightweight references over an IR/radio/paging link; a "document handling subsystem" (PC, printer 36, multifunction fax 38, OCR unit 40, IR transceiver 41 on a network 42) receives the reference, retrieves the actual document from the database, and produces the output (paper or electronic). Family member EP 0 691 619 is also cited on RE42,725's face.
• Potentially anticipating claims: 1, 9, 11, 30, 31, 32, 35, 43 (document object carrying a pointer/reference to content stored on another device; portable information apparatus; communication channel to the output device; discovery/"exchange" of office equipment). It is the single best match to the "document object = reference, not the bits" architecture the patent leans on.

3.3 US 6,020,973 — Levine et al. (Xerox), "Centralized print server for interfacing one or more network clients with a plurality of printing devices"

• Citation / dates: US 6,020,973 A; issued 2000-02-01 (title as listed on https://uspto.report/patent/grant/[6020973](/patent/6020973)). Filing date not verified in this session.
• Disclosure: A centralized print server built from an HTTP server layer plus an application layer (the record references Microsoft IIS/ISAs) that mediates between network clients and a plurality of printing devices, converting document requests into printer-appropriate data.
• Potentially anticipating claims: 1, 2, 3, 44, 46, 47, 51–53, 63 — particularly the server distinct from the information apparatus element, the plural service requests from plural information apparatuses element of claim 47, and the output controller converts output data into a form compatible with the printer controller/engine elements of claims 52–53.

3.4 US 5,978,560 — Tan et al. (Xerox), "Load balancing of distributed printing systems using enhanced printer attributes"

• Citation / dates: US 5,978,560 A; issued 1999-11-02 (listed in https://www.sumobrain.com/patents/us/Output-service-over-network/RE42725.html).
• Disclosure: Distributed print system in which enhanced printer attributes are gathered and used to select/load-balance among printers.
• Potentially anticipating claims: 1, 9, 10, 15, 16, 17, 18, 19, 20, 22, 36, 37, 38, 39, 46, 47 — this is the closest art to RE42,725's "output device object with one or more attributes" plus discovery/selection by attribute (price, quality of service, availability, defaults) claims.

3.5 US 6,452,692 — Yacoub, "Method and system for network printing"

• Citation / dates: US 6,452,692 B1; issued 2002-09-17 (listing: uspto.report/FPO). Because it was filed before 2000-11-20 (I could not independently verify the filing date this session), it is §102(e) art notwithstanding its 2002 issue date.
• Potential relevance: claims 1, 3, 32, 44 — network-side rendering/printing of content fetched from elsewhere. Description here is derived from the cited title only; I have not verified its disclosure.

3.6 US 7,478,403 — Allavarpu et al., "Secure access to managed network objects using a configurable platform-independent gateway providing individual object-level access control"

• Citation / dates: US 7,478,403 B1; issued 2009-01-13; priority date recorded as 2000-04-20 (https://portal.unifiedpatents.com). Filed before the critical date → §102(e) art.
• Potentially anticipating claims: 41, 56, 57, 58, 82, 92 (security attribute, access-control list specifying which information apparatus may obtain service, authentication/log-in/password, and the object-level gateway architecture underlying claim 1's "objects").

3.7 US 6,076,109 (Kikinis) and US 6,076,108/Kikinis-family

• Citation / dates: US 6,076,109; issued 2000-06-13.
• Potential relevance: claims 9, 11, 43 — portable/handheld apparatus establishing a (wireless) connection to a peripheral device. Description based on the cited listing; disclosure not independently verified.

3.8 US 5,982,454 — Hobbs, "Method and apparatus for..." (title truncated in the retrieved listing)

• Citation / dates: US 5,982,454; issued 1999-11-16 (uspto.report/Google listing).
• Potential relevance: document delivery/retrieval over a network → claims 31, 32, 33, 74, 75, 92. Title incomplete in my sources; disclosure not verified.

3.9 US 6,009,466 — Hamilton et al. (Sun Microsystems), and US 6,697,848 — Hamilton et al., "Method and apparatus for enabling application programs to communicate with network clients and servers"

• Citation / dates: US 6,009,466 issued 1999-12-28; US 6,697,848 issued 2004-02-24 (issued after the critical date but from a 1995-priority family per the retrieval at https://portal.unifiedpatents.com/patent/[9036181](/patent/9036181) → priority 1995-09-19 ⇒ §102(e) art).
• Potentially anticipating claims: 1, 44, 96 — the "server application operated on a server that is distinct" distributed-computing element, and the cross-platform object/service architecture.

3.10 Older art cited on the face (Group I, pre-2000) most likely to matter for the broadest claims

(All rows above: issue date from the face-of-patent listing; per-reference filing dates not individually verified. Pre-2000 issue dates mean the underlying filings necessarily predate 2000-11-20 and are therefore §102(b) art on their face.)

---

4. Full inventory of cited U.S. patent documents (Group I and II), condensed

Issued before the 2000-11-20 critical date (usable as §102(a)/(b) art on the face):
5228118 (1993-07-13, Sasaki); 5270773 (1993-12-14, Sklut); 5353388 (1994-10-04, Motoyama); 5467434 (1995-11-14, Hower); 5475507 (1995-12-12, Suzuki); 5537517 (1996-07-16, Wakabayashi); 5566278 (1996-10-15, Patel); 5613124 (1997-03-18, Atkinson); 5625757 (1997-04-29, Kageyama); 5748859 (1998-05-05, Takayanagi); 5862321 (1999-01-19, Lamming); 5867633 (1999-02-02, Taylor); 5930466 (1999-07-27, Rademacher); 5931919 (1999-08-03, Thomas); 5940843 (1999-08-17, Zucknovich); 5968176 (1999-10-19, Nessett); 5974401 (1999-10-26, Enomoto); 5978560 (1999-11-02, Tan); 5983200 (1999-11-09, Slotznick); 5987454 (1999-11-16, Hobbs); 6009464 (1999-12-28, Hamilton); 6020973 (2000-02-01, Levine); 6023715 (2000-02-08, Burkes); 6043898 (2000-03-28, Jacobs); 6061142 (2000-05-09, Shima); 6070185 (2000-05-30, Anupam); 6076109 (2000-06-13, Kikinis); 6141659 (2000-10-31, Barker); 6145031 (2000-11-07, Matise).

Issued after the critical date — §102(e) art only if filed before 2000-11-20 (filing dates not verified except where noted):
6173407 (2001-01-09, Yoon); 6189993 (2001-02-20, Mantell); 6225993 (2001-05-01, Lindblad); 6256666 (2001-07-03, Singhal); 6288790 (2001-09-11, Yellepeddy); 6366912 (2002-04-02, Wallent); 6369909 (2002-04-09, Shima); 6418439 (2002-07-09, Papiernaik); 6442375 (2002-08-27, Parmentier); 6452692 (2002-09-17, Yacoub); 6453127 (2002-09-17, Wood); 6473800 (2002-10-29, Jerger); 6477575 (2002-11-05, Koeppel); 6487587 (2002-11-26, Dubey); 6487599 (2002-11-26, Smith); 6493104 (2002-12-10, Cromer); 6515988 (2003-02-04, Eldridge); 6546387 (2003-04-08, Triggs); 6578072 (2003-06-10, Watanabe); 6604135 (2003-08-05, Rogers); 6623527 (2003-09-23, Hamzy); 6643650 (2003-11-04, Slaughter); 6658625 (2003-12-02, Allen); 6694371 (2004-02-17, Sanai); 6697848 (2004-02-24, Hamilton) — confirmed 1995-09-19 priority ⇒ §102(e) art; 6705781 (2004-03-16, Iwazaki); 6738841 (2004-05-18, Wolff); 6741871 (2004-05-25, Silverbrook); 6745229 (2004-06-01, Gobin); 6751732 (2004-06-15, Strobel); 6760745 (2004-07-06, Tan); 6775407 (2004-08-10, Gindele); 6778289 (2004-08-17, Iwata); 6840441 (2005-01-11, Monaghan); 6857716 (2005-02-22, Nagahashi); 7478403 (2009-01-13, Allavarpu) — confirmed 2000-04-20 priority ⇒ §102(e) art.

Group II — not §102 prior art for a 2000-11-20 priority (same applicant/family or later-filed):
6947995 (2005-09-20, Chang); 7028102 (2006-04-11, Larsson — filing date unverified, possibly post-2000); 7318086 (2008-01-08, Chang — the patent being reissued); 7593123 (2009-09-22, Sugahara — filing date unverified); 7944577 (2011-05-17, Chang).

---

5. Cited published applications and foreign documents

U.S. published applications (all are §102(e) art only if filed ≤ 2000-11-20; publication dates listed):
2002/0042263 (2002-04, Ishikawa); 2002/0062398, 2002/0062406, 2002/0077980, 2002/0078101 (2002-05/06, Chang et al. — same family); 2002/0092029 (2002-07, Smith); 2002/0194302 (2002-12, Blumberg); 2003/0120754 (2003-06, Muto); 2003/0160993 (2003-08, Kang); 2004/0057075 (2004-03, Stewart); 2005/0204176 (2005-09, Togawa); 2008/0318602, 2009/0002760, 2009/0070411 (Chang et al. — same family).

Foreign patent documents:

• EP 0 691 619 (published 1996-01 / 1996-10) — this is the EPO family member of US 5,862,321 (Xerox/Flynn & Lamming); see the family listing (DE69535383D1, DE69535383T2, EP0691619A2, EP0691619A3, EP0691619B1, US6144997) at https://patents.google.com/patent/US5862321A. Anticipation exposure is therefore the same as §3.2 above, for claims 1, 9, 11, 30–32, 35, 43.
• EP 0 952 513 (published 1999-10) — Canon-side network printer/communication art; disclosure not verified in this session.

---

6. Non-patent literature cited (NOT prior art)

The "Other References" section of the face of RE42,725 consists exclusively of USPTO prosecution documents — Office Actions and Notices of Allowance in applications 09/992,198; 09/992,417; 09/992,420; 09/992,183; 09/992,413; 11/993,031; 11/933,005; 12/204,689; 12/204,695 — plus the 60/252,682 benefit claim. These are not §102 prior art; they are the prosecution record of the family (useful only for estoppel/claim-construction and for showing what the examiner previously treated as art).

---

7. Bottom line — relative ranking for §102 purposes

1. US 5,867,633 (Taylor, III et al., 1999-02-02) — strongest single-reference §102 candidate. It maps the core of claim 1 (client document → remote server performs image processing → printer), and an ISR in the family record lists it as "X" against claims 1, 2–5, 10–11, 13–19, 23–24, 26–27, 29–39, 42–43.
2. US 5,862,321 / EP 0 691 619 (Flynn & Lamming, 1999-01-19 / EP 1996) — the reference-architecture anticipation: a portable device carrying only a document reference which a networked subsystem resolves and prints.
3. US 6,020,973 (Levine et al., 2000-02-01) — centralized print server mediating many clients and many printers.
4. US 5,978,560 (Tan et al., 1999-11-02) — printer-attribute-driven discovery/selection; attacks the "output device object" and selection claims (10–20, 36–39).
5. US 7,478,403 (Allavarpu, priority 2000-04-20) — §102(e) art aimed squarely at the security/ACL/authentication and object-gateway claims (41, 56–58, 82, 92).
6. US 5,568,278, 5,613,124, 5,937,919, 5,974,401, 5,983,200, 6,141,659 — secondary art for the object model, job/payment, and document-retrieval elements.

Most exposed claims: the pre-reissue claim 1 (and its dependent claims 2–8, 30–33, 44, 48, 61–63). The reissue amendment inserted the entire "wherein the output device includes an output engine … and a connection to an output controller, and wherein the output controller provides at least part of the output device object … provides a user interface for receiving user-implemented modifications of the controller" clause into claim 1 and claim 44. None of the pre-2000 references above is a clean single-reference hit against reissued claim 1's output-controller/UI-modification limitation, so the reissue claims are materially stronger against this art than the original claims were. Conversely, the newly added claims 64–101 (especially the "computer readable storage unit … not being a transitory signal" framing and the duplex/single-sided job-object attribute) are drafted around §101 concerns and, for §102 purposes, must be compared against art directed at print-job attributes (US 5,467,434 Hower; US 5,978,560 Tan) and at job objects generally (US 5,568,278; US 5,937,919).

---

Limitations of this analysis (stated explicitly rather than papered over)

• I could not retrieve the complete certified front page from USPTO PatentCenter in this session; the citation inventory is from four third-party mirrors of the front page that agree with one another on ordering. The authoritative list is page 1 of https://patentimages.storage.googleapis.com/b5/58/61/ae2930d4a51814/USRE42725.pdf.
• Per-reference filing dates are not recorded in the citation lists and I verified them only for US 5,862,321 (1995-06-21 / priority 1994-06-27), US 7,478,403 (priority 2000-04-20) and US 6,697,848 (priority 1995-09-19). Every other "§102(e) eligibility" statement above is a test that must be run against the reference's own filing date — I did not assume it.
• Descriptions for US 6,452,692, US 5,982,454, US 6,076,109, EP 0 952 513 and several table rows are derived from the cited titles only; I did not read their specifications, and I have flagged those rows accordingly. Descriptions for US 5,867,633, US 5,862,321 and US 6,020,973 are grounded in text I actually retrieved.
• Nothing above is a legal conclusion on validity; §102 anticipation additionally requires that every claim element be present in a single reference arranged as claimed, and several references here (e.g., Tan) are better characterized as §103 combinations.

I'll start by locating the actual prior-art references associated with RE42725, since the page copy you supplied includes only the "prior art keywords" field (output, output device, data, information apparatus, job) but not a reference list.

Good — that surfaced the actual reference lists. Let me pull the fuller lists (including foreign references and the pre-2000 entries) and check the key candidates.

Excellent — the reference lists are now visible. Let me pull the pre-2000 entries in full and verify the filing/priority dates of the strongest candidates (since only references predating the Nov. 19–20, 2000 priority date can be §103 art).

Obviousness Analysis — US RE42,725 E1 ("Output service over a network")

35 U.S.C. § 103 (pre-AIA), critical date = Nov. 19–20, 2000

---

0. Note on the "Prior Art section" and on a contradiction with the earlier section

The authoritative page copy you supplied contains no reference table — only the prior-art keyword set: output / output device / data / information apparatus / job. To build this analysis I used the reference lists tied to this exact patent number as retrieved from FreePatentsOnline (US Patent References), SumoBrain (Domestic Patent References / Foreign References), Justia (same list for the sibling family member US 8,169,649), and the Google Patents "cited by / similar" neighborhoods. Every reference I treat as §103 art is labeled with where I got it.

⚠️ Contradiction to flag. The earlier section states the claim set was verified "through claim 92" and identifies independents 1, 74, 82 and 92, with 92 being the software claim. The retrieved uspto.report copy of the granted reissue, however, shows fragments of claims 56, 57, 58, 63 and 64, including "58. The . . . .Iaddend.system of claim 56 in which the security procedure . . . one or more of a subscription indicator, a login, a password" and "64. A computer readable storage unit having data output software . . .". That implies at least one additional independent system claim (56) and a software claim (64) that the earlier mapping did not place. I cannot reconcile the two numbering schemes from the sources I retrieved; I note it because it enlarges the §103 attack surface (more independent claims to invalidate), and because a system claim at 56 would carry the same payment/subscription/security language.

Critical date. Pre-AIA case. Google Patents gives 2000-11-20; Unified Patents records for US-RE42725-E1 give 2000-11-19. Either way, art published before mid-to-late November 2000 is unambiguously prior art; art published later can only be used if it qualifies under §102(e) (earlier effective U.S. filing date) — and then only if not disqualified by §103(c) (common ownership). I flag per-reference which bucket it falls in.

---

1. Legal framework applied

Under Graham v. John Deere and KSR v. Teleflex, a combination is obvious where (A) known elements are combined by known methods to yield predictable results; (B) a known technique is applied to a known device ready for improvement; (C) a finite number of identified, predictable solutions exists ("obvious to try"); or (D) market forces/design incentives supply the motivation. MPEP 2143 requires an articulated reason with rational underpinning — not mere proximity of references.

Two structural facts drive the whole analysis:

1. RE42725's own specification supplies the motivation. It expressly describes the pre-existing problem: users "must first install . . . an output device driver," installation "may take anywhere from several minutes to several hours," and mobile devices have "limited memory and processing power." Under KSR, a patentee's own admission of a known problem is powerful evidence of a known design incentive.
2. No single reference appears to disclose the full claim. This is a combination case, so the motivation articulation is where any litigation would be won or lost.

---

2. Tier 1 — undisputed pre-critical-date art (from RE42725's own cited list)

Tier 2 (cited, but issued after the critical date — usable only as §102(e) art): US 6,738,841 Wolff (printer-server document requests); US 6,741,871 Silverbrook (mobile phone with interactive printer); US 6,751,732 Strobel (secure delivery/printing of documents via a network device); US 6,705,781 Iwazaki (printing service method); US 6,840,441 Monaghan (self-service terminal); US 2004/0057075 Stewart (printing services over a network); US 2003/0160993 Kang. Each would need its underlying U.S. filing date verified before use.

Family-adjacent art surfaced in the same neighborhood (not confirmed on RE42725's own list): US 6,201,611 IBM, "Providing local printing on a thin client" (priority 1997-11-18, per Unified Patents) and its CN 1217503 A counterpart; US 6,140,665 IBM (retrieving documents from multiple document servers); US 6,549,? / US 5,826,244 Xerox (document service over a network via brokered auction, 1998-10-27); US 5,832,191 HP (automatically enabling communication with a network printer); US 5,490,287 Canon and US 6,167,514 Seiko Epson (wireless printing). US 6,201,611 is the single most on-point reference I located and should be verified against the printed reissue's reference table before being relied on.

One art group is a poor weapon: the Flexiworld family bearing 2000-10-31 priority (e.g., US 10,481,847; US 10,637,178; US 9,110,622; US 10,592,202) predates the critical date by ~3 weeks and would otherwise look like §102(e) art. But because it is commonly owned with RE42725, §103(c) disqualifies it from an obviousness attack (it remains available under §102, if at all). I flag this from assignee records only.

---

3. Combination sets

Combo 1 — Claim 1 (method), core elements

Levine (6,020,973) + Lamming (5,862,321) + Hower (5,467,434) or Sasaki (5,228,118) + EP 0952513

Motivation (KSR rationales A, B, D). All references are in networked printing, addressing one problem: a client that lacks a device-specific driver and does not know the target device must still get content rendered correctly. Levine already teaches the server-mediated topology; Hower/Sasaki/EP 0952513 already teach obtaining device attributes before rendering. Substituting a general-purpose rendering server for Levine's print server, and supplying it with the device-attribute object, is "a known technique applied to a known device ready for improvement," producing the predictable result of driver-less output. The patent's own background articulates the design incentive (driver-installation burden; mobile devices with limited memory), which is exactly the KSR "market forces" rationale.

Combo 2 — Claim 1, the "thin client / local printer" variant (strongest single teaching)

US 6,201,611 (IBM, thin-client local printing) + Levine (6,020,973) + Hower (5,467,434) + Sasaki (5,228,118)

US 6,201,611 is, by its title and IBM's 1997 priority, directed to the situation RE42725 claims to solve: a low-capability client that cannot itself render sends content to a host that renders it, and the rendered data is printed on a local printer. Read with Levine's centralized print server, this supplies server-side rendering plus an intermediate controller node — nearly the whole of claim 1's functional chain. Motivation: the client's inability to store drivers is the stated problem in both; combination is a simple substitution of a known rendering host for a known print server. Verify that 6,201,611 is in the printed reference table.

Combo 3 — Claim 82 (apparatus; three objects incl. payment/subscription)

Combo 1 (or 2) + Enomoto (5,974,401) + Zucknovich (5,940,843) + Sklut (5,270,773) [+ Slotznick (5,983,200)]

Claim 82's distinguishing feature is a job object carrying both security/identification and payment/subscription data sent with the document and device objects.

• Enomoto (digital print order and delivery) → ordering/payment flow for print jobs.
• Zucknovich (restriction processing) → subscription/entitlement.
• Sklut (preventing disclosure of sensitive documents) → security/authentication.
• Slotznick (delegated-task agent) → network-side execution of user-delegated jobs.

Motivation (KSR rationales C, E, F). The specification's own use cases — an airport worker walking up to a shared printer; printing at a "convenient" nearby device — are public/shared-device scenarios. Shared devices require user identification and either payment or subscription. Kiosk/copy-shop billing, subscription access control, and document-security handling were each independently known. Aggregating three known data structures (document, device capability, and a job/ordering record) into one request to a rendering server is a predictable grouping of a finite number of identified solutions, satisfying "obvious to try." Payment-per-page/vending logic was also routine (cf. cited US 6,840,441 Monaghan, self-service terminal), subject to verifying its priority date.

Combo 4 — Dependent claims (image processing; attribute set)

• Controller-side image processing (per the dependents' list: interpretation, rasterization, scaling, segmentation, color-space transformation, enhancement, color correction, halftoning, compression/decompression): Sasaki (5,228,118), Motoyama (5,353,388), Takayanagi (5,748,859), Kageyama (5,625,757), Rademacher (5,930,466). Rasterizing in a printer controller (or print server) was the PostScript/PCL business model; the reissue's own specification describes conventional RIP/controller pipelines as prior art, an admission that the operations are old.
• Attributes: color/grayscale, laser/inkjet, duplex/single-sided, output quality, price per page, quality of service: Hower (5,467,434) printer-option availability; Tan (5,978,560) enhanced printer attributes; and, in the family-adjacent set, US 6,621,589 HP (print-job processing using selected printer attributes) — merit verification before reliance.
• Identification attribute (dependent 79) and status/estimated processing time (dependent 81): Sklut/Zucknovich for identification; queuing/spooling status reporting is conventional job-management art (and is described as conventional in the specification itself).

Combo 5 — Software claims (92 / and 64 per the uspto.report fragment)

Same art as Combo 1–4. A "computer readable storage unit having data output software" claim adds only the medium. Absent evidence that the storage unit contributes anything beyond carrying known code, the medium limitation does not rescue the claim where the underlying method is obvious (this is a §103 argument; the §101 written-description/eligibility question is separate and not analyzed here).

Combo 6 — Mobile/wireless-specific flavor (for any claim reciting wireless/close-proximity)

US 5,490,287 Canon + US 6,167,514 Seiko Epson + US 6,034,621 (PC↔PDA sync) + US 5,912,? / 5,917,542 Apple (image capture and transmission) + Silverbrook US 6,741,871 (subject to date verification). Wireless printing and short-range wireless appliance communication predate the critical date; the specification itself treats Bluetooth/IEEE 802.11/IrDA as known prior art, so no claim element resting merely on "wireless" adds patentable weight.

---

4. Base-rate expectation for the reissue claims

• Claim 1 (reissue, narrowed): ~55–70% likely obvious over Combo 1 or 2 except for the output-controller user-interface limitation.
• Claim 74 / its dependents: higher probability of obviousness (Combo 4 rests largely on the patent's own admissions about conventional controllers and RIPs).
• Claim 82 (and any independent system claim, e.g., 56): lower probability (~40–55%) because the specific triple-object with both security/identification and payment/subscription is a narrow, conjunctive requirement that requires a fourth and fifth reference and a clean motivation story.
• Software claims (92 / 64): probability tracks the underlying method claim.

(These are analyst judgments, not verified examiner determinations — I found no reexamination certificate, IPR/FWD, or court invalidity ruling addressing RE42725.)

---

5. Where the patent survives — and the patentee's rebuttals

1. The controller-side user interface ("user-implemented modifications of the output controller"). This phrase appears in claims 1, 82 and 92 per the earlier section. I found no verified pre-critical-date reference in RE42725's own cited list that discloses a print-server/output-controller having a user interface for user-implemented modifications of the controller. The closest candidates are EP 0952513 A1 (automatic configuration of a network printer) and, in the family-adjacent set, kiosk/self-service terminals and HP's automatic network-printer communication art — but "automatic configuration" is arguably the opposite of "user-implemented modifications," which is a potential teaching-away argument for the patentee. This is the strongest non-obviousness foothold, and the reason a §103 attack should lead with Combo 2 and treat the UI element head-on rather than ignoring it.
2. Conjunctive job-object content. Requiring both security/identification and payment/subscription in one job object invites a "no reason to combine / separate references do not teach the conjunctive requirement" response.
3. Secondary considerations. Flexiworld's enforcement activity (per the earlier section's unverified secondary reporting) is evidence of value, but I found no verified evidence of nexus between a commercial product and the reissue claims. Do not assume it exists.
4. §103(c). If the attacker reaches for the 2000-10-31 Flexiworld family, common ownership disqualifies it for §103.

---

6. Confidence

• High: that RE42725's cited-reference corpus (as retrieved) is dominated by networked-printing, thin-client, printer-attribute, print-ordering and document-security art; that the specification self-admits the driver-installation and limited-mobile-device problems; that no single reference discloses the claims; that the earliest undisputed art (Sasaki 1993; Sklut 1993; Hower 1995; Patel 1996; EP 0691619 1996) long predates the critical date.
• Medium: the specific element-by-element mappings, which I derived largely from retrieved titles and dates rather than full reference texts; the §102(e) viability of the Tier-2 references (filing dates unverified); the priority date itself (Nov. 19 vs Nov. 20, 2000).
• Low / unverified: the disclosure content of the Tier-2 and family-adjacent references; whether US 6,201,611 actually appears in RE42725's printed reference table; the full claim set beyond the independents identified earlier (see the claim-numbering contradiction in §0); and all litigation outcomes. I could not reach USPTO PatentCenter, PACER, or CAFC dockets with the available tools, so no document-level verification of the printed reissue's reference table was possible — the reference lists above should be re-checked against the granted reissue text before any of this is relied on.