Invalidity dossier
US 7944577
Output controller for mobile and pervasive digital content output
Current assignee: Roku, Inc.
Added 8/28/2026, 6:46:45 PM
Active provider: DeepSeek · deepseek-v4-flash
Auto-generating section 1 of 2: Extensions…
Each section takes ~30-60s with web-search grounding. Keep this tab open — sections will fill in below as they complete.
Patent summary
Title, assignee, inventors, filing/issue dates, abstract, and a plain-language overview of the claims.
I'll research US patent 7944577, searching the USPTO database and checking for any CAFC 2026 docket activity, while being careful to interpret the patent number literally.
I found the abstract and some litigation documents. Now let me retrieve the actual claim language and check for any CAFC 2026 docket activity more specifically.
I have the abstract and bibliographic data. The claims section wasn't included in the full text I have, so let me retrieve the actual claim language for US7944577 and also double-check for any CAFC 2026 docket entries.
I've reached the limit of my search steps, but I have enough to give you a well-grounded summary. Here it is, with explicit flags on anything I could not verify authoritatively.
US Patent 7,944,577 B2 — Summary
Title: Output controller for mobile and pervasive digital content output
Patent/Application Nos.: US 7,944,577 B2; Appl. No. 11/933,005 (pre-grant publication US 2008/0278746 A1)
Inventors: William Ho Chang (Vancouver, WA, US); Christina Ying Liu (Vancouver, WA, US)
Assignee (original): Flexiworld Technologies, Inc. (Portland, OR, US). Per the Google Patents assignment record, the patent was reassigned to FLEXIWORLD TECHNOLOGIES, INC. on 2021-07-30 (same entity name, formal assignment record).
Filing date: October 31, 2007
Earliest priority date: November 20, 2000 (continuation family dating to 2000)
Issue (grant) date: May 17, 2011
Legal status: Expired – Fee Related; adjusted expiration noted as 2023-01-29.
Abstract (verbatim from USPTO/FreePatentsOnline/Golden sources):
"Pervasive output capability is provided so that an information apparatus can pervasively output digital content to an output device regardless of the processing power, display screen size and memory space of the information apparatus. This allows small mobile devices with limited display, processing power, and memory to be able to output a digital document (e.g., PDF, HTML, PowerPoint etc) in its full original richness, without resorting to downsizing, truncating, reducing, clipping or otherwise altering the original document. A data output service method for rendering at an output device output content managed from an information apparatus may include obtaining by wireless communication from the information apparatus at least part of a document object relating to the output content, obtaining at least part of an output device object with one or more attributes relating to the output device, and providing the document object and the output device object to a server application operated on a server that is distinct from the information apparatus and the output device, and generating with the server application output data relating to the output device. The output data may then be provided to the output device for rendering the output content as the data output service."
What the patent covers (plain language): A system/method that lets a small mobile device (phone, PDA, pager, camera, etc.) output content — print, display, or play — on a nearby output device (printer, TV, projector, speakers) without the mobile device having to install a device-specific driver. The mobile device obtains a "document object" (content or a pointer to content) and an "output device object" (capability/attribute data about the target device), hands both to a remote server application, and the server does the heavy conversion into device-ready "output data." The output data is then sent back to the mobile device and wirelessly to the output device, which renders it — even when the mobile device itself cannot display the full document.
Independent claims — with a significant caveat
The full claims text was not included in the patent text you provided (it ends at the GUI figures), and I could not retrieve the complete "What is claimed" section verbatim from an authoritative source within my search budget. I therefore cannot state with certainty how many independent claims the granted patent has or quote them exactly.
What I did find: a USPTO PTAB petition document (ptacts.uspto.gov, petition file 1549999) quotes what it calls the "'577 Patent" (i.e., US 7,944,577) claim 1, broken into preamble elements and method steps. Based on that document, granted claim 1 appears to be a method claim performed by an output controller, requiring roughly:
- An output controller having a wireless communication unit, a processor, application software (including processing content with at least a digital imaging operation), and a memory/storage component for storing data and for queuing/spooling;
- Establishing a wireless communication channel with an information apparatus, including authenticating the apparatus or its user;
- Obtaining at least part of an output device object (attributes about the output device) and wirelessly providing it to the information apparatus;
- Receiving, wirelessly, output data from the information apparatus that includes the digital content for rendering plus device-dependent data related to the output device; and
- Queuing or spooling the received output data for rendering.
The same document cites a dependent claim 12 reciting "the output controller is included in the output device."
⚠️ Uncertainty: This claim reconstruction comes from a PTAB petition document quoting the patent, not from the granted patent's claims page directly. Treat the exact wording and the total number of independent claims (the abstract suggests at least one method claim; the family's later continuations reference multiple independent claims) as unverified. If you need the exact claims, the authoritative source is the USPTO Patent Center/Google Patents claims section for US7944577, which I could not fully retrieve here.
Litigation / PTAB / CAFC status
- IPR2022-01269 — filed at the PTAB (petition by Unified Patents, per the Google Patents litigation metadata), status shown as Settlement.
- District court: Texas Western District Court, case 6:21-cv-00767 (per Unified Patents litigation data).
- CAFC 2026 dockets: I searched specifically for a 2026 CAFC (Federal Circuit) docket involving patent 7944577 or Flexiworld and found no CAFC 2026 docket entry. This is a negative result from web searches, not a definitive docket-database confirmation; I cannot rule out an appeal under a different docket reference. (Note: one search result referencing a "'794 patent" deposition about synchronized data segments "S1/S2" is a different patent, not this one — I excluded it as not being US 7,944,577.)
Bottom line: The core facts (title, inventors, assignee, dates, abstract) are confirmed across multiple sources. The independent-claim breakdown is based on a PTAB petition document quoting claim 1 and should be verified against the granted claims text if precision matters.
Generated 8/29/2026, 12:49:35 AM
Cases on file (2)
Group view →Specific litigation cases in our database that name US patent 7944577. The free-form analysis below may also discuss cases beyond this list.
- Roku, Inc. v. Flexiworld Technologies, Inc.filed Jul 29, 2022IPR2022-01269USPTO Patent Trial and Appeal Board (PTAB), inter partes reviewterminated Oct 31, 2022terminated (settled prior to institution)
Defendants: Flexiworld Technologies, Inc.
- Flexiworld Technologies, Inc. v. Roku, Inc.filed Jul 27, 20216:21-cv-00767-ADAU.S. District Court for the Western District of Texas, Waco DivisionSettled
Defendants: Roku, Inc.
Litigation summary
Past and pending lawsuits — plaintiffs, defendants, jurisdictions, outcomes, and notable rulings.
Litigation Involving U.S. Patent No. 7,944,577 ("the '577 patent")
Based on searches of the Stanford NPE Litigation Database, RPX, PACER Monitor, the PTAB (ptacts.uspto.gov), and the Unified Patents portal, I have identified two district-court cases and one PTAB proceeding tied to the '577 patent. Details and confidence flags are below.
1. Flexiworld Technologies, Inc. v. Roku, Inc.
- Plaintiff: Flexiworld Technologies, Inc.
- Defendant: Roku, Inc.
- Jurisdiction: U.S. District Court for the Western District of Texas, Waco Division
- Case No.: 6:21-cv-00767-ADA
- Filing date: July 27, 2021
- Patents asserted: The '577 patent (claims 1 and 23, per a complaint analysis of the docket), together with family patents 9,836,257, 9,389,822, and a fourth patent ("'031"). Accused products included Roku streaming devices, the Roku Mobile App, Roku TV OS, and Roku TV products (TCL, Hisense, Philips).
- Status/outcome: Settled in 2022. The case was stayed pending Roku's standing and transfer motions and its PTAB petitions; the parties resolved the litigation as part of the settlement that terminated IPR2022-01269 (see below). Patexia's summary of the family litigation confirms the case "was resolved through a settlement in 2022."
- Sources: ptacts.uspto.gov petition exhibits (status report and complaint excerpts, Exs. 1018–1020); Patexia case listing (7/27/2021, W.D. Tex.); ai-lab.exparte.com complaint analysis for 6:21-cv-00767.
2. Roku, Inc. v. Flexiworld Technologies, Inc. — IPR2022-01269 (PTAB)
- Petitioner: Roku, Inc. (counsel: Perkins Coie)
- Patent Owner: Flexiworld Technologies, Inc.
- Tribunal: USPTO Patent Trial and Appeal Board (PTAB), inter partes review
- Proceeding No.: IPR2022-01269
- Filing date: July 29, 2022
- Patent/claims challenged: U.S. Patent No. 7,944,577, claims 1–14 and 23–25
- Status/outcome: Terminated — settled prior to institution. Joint motion to terminate filed October 27, 2022; Board's settlement termination decision issued October 31, 2022 (37 C.F.R. § 42.74); refund of the petition fee approved November 2022.
- Correction to prior analysis: The Google Patents litigation metadata labels this case under the "Unified Patents PTAB Data" license, which apparently led an earlier summary to infer the petitioner was Unified Patents. The actual petition (ptacts.uspto.gov, petition file 1549999) identifies Roku, Inc. as petitioner and Flexiworld as patent owner. Roku also filed contemporaneous IPRs against family members 9,389,822 and 9,836,257, and another family member (9,965,233) was challenged in IPR2022-01114.
- Sources: ipverse.greyb.com IPR case details; ptacts.uspto.gov IPR2022-01269 petition; PTAB termination decision dated Oct. 31, 2022.
3. Flexiworld Technologies, Inc. v. Sony Corporation
- Plaintiff: Flexiworld Technologies, Inc. (counsel: Nelson Bumgardner Conroy PC)
- Defendant: Sony Corporation
- Jurisdiction: U.S. District Court for the Eastern District of Texas, Marshall Division (Judge Rodney Gilstrap)
- Case No.: 2:23-cv-00616 (2:23-CV-00616-JRG)
- Filing date: December 19, 2023 (RPX Empower); Sony served January 17, 2024; First Amended Complaint filed June 6, 2024.
- Status/outcome: Dismissed with prejudice. The parties filed a Joint Stipulation of Dismissal (Dkt. 42) under Fed. R. Civ. P. 41(a)(1)(A)(ii) dismissing "all pending claims and counterclaims" with prejudice; each party to bear its own costs. The Court acknowledged and accepted the stipulation and ordered the case closed. No merits ruling was issued.
- ⚠️ Flag — '577 patent involvement unverified at the amended-complaint stage: The Stanford NPE Litigation Database lists 7944577 among the patents in this case (case 2:23-cv-00616, E.D. Tex.). However, detailed patent lists for this case from PatSnap (7 asserted patents) and GoldenCompass (15 patents) do not include 7,944,577. The discrepancy is likely because the original complaint (Dec. 2023) asserted a broader set of patents, including the '577, and the First Amended Complaint (June 6, 2024) narrowed the case to seven patents (US 9,836,259, 11,096,056, 9,798,516, 9,042,811, 10,768,871, 11,029,903, and 10,162,596). I could not retrieve the original complaint's patent exhibit list within my search budget, so the assertion of '577 in the Sony case is plausible but not definitively confirmed; treat it as "reported by Stanford NPE DB, not confirmed by the amended-complaint patent lists."
- Sources: npe.law.stanford.edu/patent/7944577; litigation.rpxcorp.com (filed 12/19/2023); pacermonitor.com/public/case/51750256; PatSnap litigation summary (dismissal order verbatim, Dkt. 42); goldencompass.patentpia.com patent list.
Other potential matters — not confirmed for '577
- No CAFC (Federal Circuit) appeal involving the '577 patent was found — including no 2026 docket activity. Both district-court matters ended without appealable merits rulings (settlement; stipulated dismissal with prejudice), which is consistent with the absence of appellate activity.
- No ITC investigation involving the '577 patent was found.
- The Google Patents "family has litigation" tag (Darts-ip family 22957058) reflects litigation across the broader Flexiworld family (e.g., the IPRs against 9,389,822, 9,836,257, 9,965,233 and related district-court cases) and should not be read as additional '577-specific cases.
Patent status note relevant to remedies
The '577 patent is Expired – Fee Related, with adjusted expiration noted as January 29, 2023. Because the Roku case settled and the Sony case was dismissed with prejudice, no live damages window is at issue in pending litigation, but any hypothetical future assertion would be limited to pre-expiration damages.
Bottom line: Known litigation specific to US 7,944,577 is (1) Flexiworld v. Roku, 6:21-cv-00767-ADA (W.D. Tex., filed 7/27/2021, settled 2022); (2) the related PTAB IPR2022-01269 (Roku v. Flexiworld, filed 7/29/2022, terminated-settled 10/31/2022); and (3) Flexiworld v. Sony, 2:23-cv-00616 (E.D. Tex., filed 12/19/2023, dismissed with prejudice — with the caveat that the '577's presence in that case is per the Stanford NPE DB and not confirmed by amended-complaint patent lists). No CAFC 2026 or other appellate activity was found.
Generated 8/29/2026, 4:47:46 AM
Proceedings on file (0)
All PTAB activity →AIA trial proceedings (IPR / PGR / CBM) filed at the USPTO Patent Trial and Appeal Board against this patent. Sourced from the USPTO Open Data Portal and refreshed every six hours; each proceeding number deep-links to the PTAB E2E docket.
Current assignee: Roku, Inc.
No PTAB proceedings on file. This patent has not been challenged via IPR, PGR, or CBM. The absence is itself a signal — well-asserted patents eventually attract IPRs. The LLM analysis below may surface filings the ODP feed hasn’t indexed yet.
PTAB challenges
AIA trial proceedings at the USPTO Patent Trial and Appeal Board — IPR, PGR, and CBM. Petitioners, judge panels, claim-level invalidation outcomes from Final Written Decisions, and Federal Circuit appeals. The single most important defensive datapoint after litigation history.
Proceedings overview
There is one AIA trial proceeding on US 7,944,577 that I can verify: IPR2022-01269 (Roku v. Flexiworld), which terminated by settlement before institution — so the count is: 1 settled / 0 active / 0 claims invalidated / 0 claims sustained on the merits / 0 institution denials. Bottom line for a defendant: no claim of the '577 patent has ever been canceled or even examined on the merits by the PTAB — the patent is PTAB-untested — but the sole IPR settled pre-institution, the patent expired in 2023 (fee-related, adjusted expiration 2023-01-29), and every ground Roku assembled remains legally available to a new, timely challenger.
⚠️ Source discrepancy, flagged: The canonical "PTAB proceedings on file" block in this prompt (USPTO ODP API ingest) reports no AIA trial proceedings. Live web search, however, confirms IPR2022-01269 from multiple independent sources — the USPTO PTACTS petition copy (ptacts.uspto.gov file 1549999), the Board's Termination Decision (DocketAlarm), and GreyB's PTAB case tracker. Per the operating rules (prefer live search results; flag conflicts), I treat IPR2022-01269 as real and flag that the ODP block is stale or incomplete.
IPR2022-01269 — Roku, Inc. v. Flexiworld Technologies, Inc.
- Type: Inter Partes Review
- Filed: 2022-07-29
- Status: Terminated-Settled (Board termination decision dated 2022-10-31; "we have not yet determined whether to institute trial"). Plain English: the case was settled and dismissed before the Board ever ruled on institution.
- Judge panel: Terrence W. McMillin, Christopher L. Ogden, and Brent M. Dougal, Administrative Patent Judges; the termination decision was authored by APJ Dougal. (DocketAlarm lists the same panel: Dougal, Ogden, McMillin.)
- Petition grounds: Roku petitioned for IPR of claims 1–14 and 23–25 of US 7,944,577, requesting cancellation under pre-AIA 35 U.S.C. § 103. Grounds identified in the petition:
- Ground 1a: Saulpaugh (US 6,850,979) + Ghori (US 6,243,772) → claims 1–14 and 23.
- Ground 1b: Saulpaugh + Ghori + Engeldrum (US 5,638,117) → claims 14 and 24–25.
- Ground 2a / 2b: Gu (US 6,892,230) + Shamoon (US 7,233,948), with Engeldrum added for the color-correction limitation of claim 24 (per the petition's summary; the exact claim scope of Grounds 2a/2b is not fully visible in the snippet I retrieved — treat the 1a/1b mapping as verified, 2a/2b as partially verified).
- Supporting evidence: declaration of Dr. Eli Saber (Ex. 1003), claim listing (Ex. 1004), file history (Ex. 1002), plus Flexiworld's own 2000 provisional applications (Exs. 1006–1010) and a later Chang patent (Ex. 1015) on the priority-date question. Roku applied a November 18, 2001 POSITA date while noting the patent claims priority to the 2000-11-20 provisional — expressly reserving the right to contest priority.
- Institution decision: None. The proceeding was terminated before the Board decided whether to institute (the termination decision states: "We have not yet determined whether to institute trial in these proceedings"). No § 314(a) analysis, no NHK-Fintiv analysis on the record.
- Final Written Decision: None issued. No claim of the '577 patent has been held unpatentable (or patentable) by the Board.
- Settlement / termination: On 2022-10-27, with Board authorization, the parties filed a Joint Motion to Terminate (Paper 7), a Settlement and Patent License Agreement (Ex. 2001), and a Joint Request to Keep Separate (Paper 8). The parties represented that they had "settled their entire dispute concerning the [subject] patent[s]" and that the Board had not decided the merits. The Board granted termination on 2022-10-31 under 37 C.F.R. § 42.74 and ordered the settlement agreement treated as business confidential and kept separate from the patent file (terms confidential — the title indicates a license was part of the deal, but the terms are not public). Roku's $22,500 post-institution fee was refunded (Notice of Refund, 2022-11-25). Petitioner's counsel: Perkins Coie (McKeever, Bombach, Day, Schunter; pro hac vice for Matthew C. Bernstein). Patent owner's counsel: Nelson Bumgardner Conroy P.C. (Bumgardner, Delafield, Ginnings).
- Appeal: None. There is no FWD to appeal, and I found no CAFC docket for this patent (including no 2026 CAFC entry).
- Defensive value: The IPR produced zero claim cancellations — Flexiworld walked away with all claims intact. But it also produced zero estoppel (see below), and Roku is now licensed and out of the picture. For a current defendant, this proceeding is evidence that Flexiworld will settle on a portfolio license rather than litigate to a merits decision — and that the strongest PTAB artillery (Saulpaugh/Ghori/Engeldrum/Gu/Shamoon) is still unfired and available.
Strategic summary
Claim status — CANCELED vs. SUSTAINED vs. UNTESTED. No claim of US 7,944,577 has been canceled, and no claim has been sustained on the merits — the Board never instituted trial. Claims 1–14 and 23–25 were challenged in the Roku petition but are untested (the petition died pre-institution). Claims outside that set (e.g., 15–22, if present) were never challenged at all. The only "adverse event" to the patent is not PTAB-related: the patent is expired — fee-related, adjusted expiration 2023-01-29 per USPTO records. That caps any recovery to pre-expiration conduct and forecloses injunctive relief; it also means the "troll" is asserting a dead patent for past damages only. (Verify the exact maintenance-fee/expiration status in USPTO Patent Center before relying on it.)
Estoppel landscape. Because IPR2022-01269 was terminated before institution, neither § 315(e)(1) (institution-stage estoppel) nor § 315(e)(2) (post-FWD estoppel) attached to anyone. All of Roku's prior-art grounds remain available — Saulpaugh, Ghori, Engeldrum, Gu, Shamoon, Slaughter (US 6,643,650), and Lamming (US 5,862,321), in any combination. The only practical constraint on reusing them is § 315(b)'s one-year bar, which runs from service of a complaint on each specific defendant — so a defendant served recently can file a fresh IPR on the same art. Roku itself is time-barred (served in the W.D. Tex. case by mid-2021) and is licensed, so it is not coming back.
Pattern signals. (1) Roku filed three coordinated IPRs on the same day — IPR2022-01267 (9,836,257), IPR2022-01268 (9,389,822), and IPR2022-01269 (7,944,577) — and settled all three in a single joint termination on 2022-10-31 with one Settlement and Patent License Agreement: a classic portfolio-wide settlement. (2) The earlier summary in this thread attributed the IPR to "Unified Patents" based on Google Patents metadata — that is a misreading: Unified Patents is merely the source of the PTAB data feed; the petition and Board decision identify Roku, Inc. as petitioner. (3) Unified Patents has separately attacked a sibling Flexiworld patent — IPR2022-00775 on 9,836,257 — and lost on the merits: the FWD (Paper 41, 2023-11-01) held claims 27–28 not unpatentable, crediting Flexiworld's corroborated October 22, 2000 conception via provisional-application metadata to swear behind the references. That is the single most important signal for this family: Flexiworld fights priority dates hard and has won. Any new petitioner on 7,944,577 should expect a § 102(e) swear-behind battle over the 2000-11-20 provisional priority date and must come prepared with conception/reduction-to-practice counter-evidence. (4) Downstream litigation has also fizzled: Flexiworld v. Roku, 6:21-cv-00767 (W.D. Tex.) was stayed during the IPR and resolved by the settlement; Flexiworld v. Sony, 2:23-cv-00616 (E.D. Tex.) was dismissed with prejudice by joint stipulation in 2024 with no merits ruling (per the PACER-derived order quoted by PatSnap; note that PatSnap's patent list for that case does not include 7,944,577, though Stanford's NPE database associates it — flagging the inconsistency).
Recommended next steps
- Confirm the expiration defense first. Pull the maintenance-fee/status screen in USPTO Patent Center for 7,944,577. If "Expired — Fee Related" as the metadata indicates, assert it immediately: no post-2023-01-29 damages, no injunction, and a strong early-dismissal hook.
- Do not assume IPR estoppel protects you — it doesn't. The Roku settlement produced no estoppel for anyone. If you were served within the last year, the Saulpaugh/Ghori/Engeldrum/Gu/Shamoon combination from the Roku petition (ptacts.uspto.gov file 1549999; also on DocketAlarm) is a ready-made § 103 roadmap — but budget for the priority-date fight Flexiworld already won once in IPR2022-00775 (FWD, Paper 41, 2023-11-01). Attack the 2000-11-20 provisional priority claim head-on; Flexiworld's conception evidence will be the battleground.
- No active PTAB proceedings pending — there are no institution deadlines, oral-hearing dates, or FWD dates to track on this patent. The absence of an active IPR, combined with the patent's expiration, makes a merits-based PTAB defense optional rather than mandatory; for a recently served defendant, however, a fresh petition is still the cheapest path to killing or narrowing the remaining damages window.
- Watch the broader Flexiworld portfolio. The same settlement pattern (IPR2022-01267/01268) and the Sony dismissal show Flexiworld resolving cases on licenses and stipulations rather than merits wins — a defendant facing a demand letter may find that a credible, timely IPR petition (even on the already-assembled art) is the leverage that produces a nuisance-value exit.
Key sources: Termination Decision (2022-10-31), IPR2022-01269 (DocketAlarm); Petition for IPR of US 7,944,577 (PTACTS file 1549999); case tracker (GreyB/IPverse, IPR2022-01269); IPR2022-00775 FWD discussion (PTAB Litigation Blog / JD Supra, 2023-11-01).
Generated 8/29/2026, 4:48:42 AM
Ownership chain (1)
Asserters network →Structured records extracted from the assignment-history narrative below. Each entity links to its full ownership-network profile.
? · recorded 2021-07-30 · Assignment of Assignors' Interest
William Ho Chang; Christina Ying LiuFlexiworld Technologies, Inc.
litigation-standing perfection
Assignment history
Inventors, original assignee, and the chain of ownership recorded with the USPTO — including the correspondent attorney who recorded each assignment, since shell-LLC chains often share one repeat-player attorney even when the entity names look unrelated. Surfaces NPE / patent-troll patterns: shell-entity transfers, known asserters in the chain, repeat correspondent fingerprints, pre-litigation assignments, and bankruptcy fire-sales.
I'll research the assignment chain for US 7944577 through USPTO assignment records and cross-referencing sources.
The IPR detail is valuable — it was Roku (not Unified Patents as petitioner), and it settled pre-institution. Now let me find the actual USPTO assignment reel/frame records.
I found several Flexiworld assignment reel/frames from Epson's answers. Now I need the specific reel/frame for the '577 patent itself.
I've hit my search budget. Below is my reconstruction with every fact tagged by source and confidence level. I could not query the USPTO Assignment Center directly (no interactive access), so the reel/frame for the '577-specific recording is unverified; everything else is flagged accordingly.
Inventors
| Inventor | Address on patent | Role / employer at filing |
|---|---|---|
| William Ho Chang | Vancouver, WA, US | Co-inventor and co-founder/principal of Flexiworld Technologies, Inc. — the original assignee. Chang is the named inventor on essentially the entire Flexiworld wireless-output family (US 7,609,402; 8,184,324; 9,298,407; 9,836,259; 10,140,071; 10,140,072; 10,126,991; etc., all assigned to "Flexiworld Tech Inc" per Unified Patents portal records). |
| Christina Ying Liu | Vancouver, WA, US | Co-inventor and co-founder/principal of Flexiworld Technologies, Inc. Also named on the same family of Flexiworld patents. |
Unusual pattern worth flagging: Both inventors are the principals of the original assignee, and their assignment to Flexiworld was not recorded until 2021-07-30 — roughly 10 years after the patent issued (2011-05-17) and exactly as the 2021–2022 assertion campaign began (see below). That is a late standing-perfection pattern, not a fire-sale or departure pattern. (Source: Google Patents legal-events feed on the patent page; sibling-patent assignments admitted in Flexiworld v. Epson answers — see timeline.)
Original assignee
- Flexiworld Technologies, Inc. (Portland, OR, US) — named assignee on the issued patent (FreePatentsOnline/Google Patents bibliographic data).
- Products: No evidence in any source I retrieved that Flexiworld ever shipped a commercial product embodying these claims. Its known output is a large patent portfolio with 2000–2001 priority covering wireless/mobile printing, pervasive output, and digital-content output.
- Line of business: Patent development, licensing, and assertion. Since mid-2021 it has been litigating the family against major consumer-electronics companies (Epson — per Epson's admitted answers to Flexiworld's complaint; Roku — IPR2022-01269; plus W.D. Tex. case 6:21-cv-00767).
- Current status: Operating (not acquired, dissolved, or in bankruptcy) as a patent-assertion/licensing entity. It still owns the '577 patent; there is no recorded transfer away from Flexiworld.
Assignment timeline
Critical framing: The only recorded assignment event surfaced for US 7,944,577 is the inventors → Flexiworld assignment recorded 2021-07-30 (Google Patents legal events: "Assigned to FLEXIWORLD TECHNOLOGIES, INC. — ASSIGNMENT OF ASSIGNORS INTEREST (SEE DOCUMENT FOR DETAILS). Assignors: CHANG, WILLIAM HO, LIU, CHRISTINA YING"). This is the original assignment recorded late — not a post-issuance change of ownership. I found no assignment from Flexiworld to any third party for this patent. If the Assignment Center confirms nothing else, that means the original assignee still owns the patent.
- 2007-10-31 — Application 11/933,005 filed (continuation of a family dating to 2000-11-20). No assignment event recorded at filing in the Google Patents feed.
- 2011-05-17 — US 7,944,577 B2 granted to Flexiworld Technologies, Inc.
- ~2021-07-30 (recorded) — Reel/Frame not independently verified for the '577 ⚠️
- Conveyance: Assignment of Assignors' Interest (original inventors' assignment, recorded late)
- Assignor: William Ho Chang; Christina Ying Liu
- Assignee: Flexiworld Technologies, Inc.
- Correspondent: not retrievable within my search budget — do not fabricate. ⚠️
- Context: litigation-standing perfection — the recording coincides with the start of the 2021 assertion campaign (W.D. Tex. 6:21-cv-00767; Epson suit; then Roku IPR in 2022).
- Corroborating pattern: in Flexiworld v. Epson, Epson admitted batch-recorded Chang/Liu → Flexiworld assignments for sibling patents at 2021-era reels: 046519/0534 ('871), 042385/0202 ('031, '072, '178), 043675/0454 ('856), 039816/0200 ('596) — and a 2011-era recording at 028733/0064 ('402). The '577's own reel/frame was not among the numbers I could retrieve. (Source: action-intell.com copy of Epson's answers to Flexiworld's lawsuit.)
Plain finding: one-link chain — Chang & Liu → Flexiworld Technologies, Inc. Flexiworld remains the owner and is the party asserting the patent (Roku IPR2022-01269 respondent = Flexiworld; W.D. Tex. 6:21-cv-00767). No shell-LLC transfer, no cascade, no aggregator appears in the chain.
Timeline diagram
timeline
title Ownership of US 7944577
2000 : Earliest priority date
2007 : Filed as continuation
2011 : Granted to Flexiworld
2021 : Inventor assignment recorded
: W D Tex infringement suit filed
2022 : Roku IPR filed
: IPR settled pre-institution
NPE / troll-pattern signals
Shell-entity transfer — not present. The patent never moved to an "IP / Licensing / Holdings" LLC. The current owner is the original assignee, a corporation (Flexiworld Technologies, Inc.). No registered-agent address or single-purpose LLC in the chain.
Known asserter in the chain — present (strong). Flexiworld Technologies, Inc. — the current assignee — is itself a serial patent plaintiff. Concrete evidence: (a) Flexiworld v. Epson — Epson's answers admit the suit and the assignment recordation (action-intell.com, Aug 2021); (b) IPR2022-01269, Roku, Inc. v. Flexiworld Technologies, Inc., filed 2021-07-29-style docket activity on 2022-07-29, settled pre-institution 2022-10-31 (ipverse.greyb.com PTAB case detail; patent 7944577, respondent appl. 11/933,005); (c) W.D. Tex. 6:21-cv-00767 (2021, per Unified Patents litigation data); (d) RPX Insight tracks Flexiworld's litigation (insight.rpxcorp.com litigation_documents/15143102), and the Unified Patents portal tracks the Flexiworld portfolio at scale. This satisfies "entity surfaced by Unified Patents or RPX as a high-frequency plaintiff." ⚠️ I could not confirm a formal line-item on a published NPE directory, so the "list" part is inferred from the tracking + docket evidence, not a directory screenshot.
Repeat correspondent across the chain — unclear. The chain has only one link, so there is no recurrence to test. The correspondent of record for the 2021-07-30 recording could not be retrieved in my search budget. ⚠️
Cascading transfers — not present. No chained LLC assignments, no <24-month multi-hop sequence. The chain is inventors → Flexiworld only.
Pre-litigation transfer — present, in modified form. The 2021-07-30 recording of the inventors' assignment lands squarely at the opening of the 2021–2022 assertion campaign (W.D. Tex. 2021 suit; Epson answers Aug 2021; Roku IPR 2022). This is late standing-perfection — recording an assignment that should have been recorded at filing (2007) — done to establish a clean ownership record before suing. Sibling patents show the same batch pattern (reels 042385/0202, 043675/0454, 046519/0534). It is not a change of ownership, so I rate it moderate, not the classic "transfer to a new plaintiff" tell.
Bankruptcy fire-sale — not present. No Chapter 7/11, no court-supervised patent sale involving Flexiworld.
Privateering — not present. No evidence an operating company transferred patents to Flexiworld to assert against competitors. Flexiworld is the original assignee from the inventors.
Defensive aggregator (anti-NPE) — not present. The chain does not terminate at RPX, AST, LOT, Unified Patents, or OIN. Flexiworld retains and asserts the patent.
Verdict
NPE — high confidence.
The two driving facts: (1) the current assignee, Flexiworld Technologies, Inc., is itself a high-frequency patent plaintiff (Epson suit, Roku IPR2022-01269, W.D. Tex. 6:21-cv-00767) with no evidence of any product business — the classic non-practicing-entity posture — and (2) the inventors' assignment was recorded only on 2021-07-30, a decade post-issuance, precisely as the assertion campaign launched (litigation-standing perfection; sibling patents batch-recorded at reels 042385/0202, 043675/0454, 046519/0534). I'm using "high confidence" rather than "moderate" because the asserter signal is strong and the litigation-timed recording corroborates it; the classic shell-LLC and cascading-transfer tells are absent only because the chain is a single link — Flexiworld is the NPE rather than a downstream buyer. Caveat: the '577's exact reel/frame and the recording correspondent remain unverified; confirm at the USPTO Assignment Center before relying on the specific 2021-07-30 entry.
Verification links: https://assignmentcenter.uspto.gov/ (search Patent No. 7944577) · https://ipverse.greyb.com/ptab-web/cases/case-details/IPR2022-01269 · https://portal.unifiedpatents.com/litigation/Texas%20Western%20District%20Court/case/6%3A21-cv-00767
Generated 8/29/2026, 4:48:39 AM
Prior art
Earlier patents, publications, and products that may anticipate or render the claims unpatentable.
I'll research the prior-art citations on the face of US 7,944,577. Let me start with targeted searches.
Good start. Let me pull the full "References Cited" section from multiple sources.
Let me retrieve more of the cited-references list and cross-check the IPR-based art.
Method, scope, and a sourcing caveat
I searched for US 7,944,577 specifically (no other number) and pulled its own "References Cited" / "Domestic Patent References" lists from patent-mirror and aggregator sites (SumoBrain, FreePatentsOnline, Google Patents citations block, Justia, Unified Patents portal).
Two things you need up front:
The full patent text in my prompt (Google Patents fetch) contains only the abstract, description, and figure list — it does not contain the "References Cited" front page or the "What is claimed" section. So all citations below come from mirror-source retrieval, not from the authoritative front page.
I hit my search-step ceiling mid-task. As a result I retrieved the cited-references list in two disjoint slices and could not obtain a single complete, ordered list:
- Slice 1 (ascending, issue dates 1993 → 2000-02-01) — SumoBrain "Domestic Patent References."
- Slice 2 (descending, issue dates 2009-09-22 → 2002-12-11) — FreePatentsOnline "US Patent References."
- Gap: references issuing between roughly 2000-02 and 2002-12 were not retrieved; foreign references and "Other References" (NPL) were not retrieved at all. ⚠️
I validated Slice 2 as backward citations (not forward citations) on a simple date test: every entry there (e.g., 7,593,123 issued 2009-09-22; 7,478,403 issued 2009-01-13) predates the '577's 2011-05-17 grant, so none of them can be patents that cite the '577. They must be references the '577 cites.
Also note the front page's "Prior art keywords" (per the Google Patents record): output; controller; output device; information apparatus; data — which is consistent with what the examiner was searching.
Table A — Examiner-cited U.S. patent references, verified (issue dates 1993 – 2000-02-01)
Source: SumoBrain, https://www.sumobrain.com/patents/us/Output-controller-mobile-pervasive-digital/7944577.html ("Domestic Patent References"). Dates shown are the issue dates given by the source; filing dates were not exposed in the retrieved slice. ⚠️
| Patent | Issue date | Inventor | Title / subject (as retrieved) | Provisional § 102 / relevance read |
|---|---|---|---|---|
| 5,228,118 A | 1993-07-13 | Sasaki | Printing system where one of several printer drivers is selected based on interpreters available on the printer | Device-capability-driven driver/format selection. Touches the "device-dependent output data" idea. Weak. |
| 5,270,773 A | 1993-12-14 | Sklut et al. | Image producing device with security to prevent disclosure of sensitive documents | Security/confidential-document handling. Weak (relates to confidential-output features, not claim 1). |
| 5,353,388 A | 1994-10-04 | Motoyama | System and method for document processing | Generic document processing/print pipeline. Background. |
| 5,467,434 A | 1995-11-14 | Hower, Jr. et al. | Determining printer option availability and representing conflict resolution among print-job selections | Directly relevant to "output device object with attributes" and job-option negotiation. Possible § 102/§ 103 relevance to the output-device-object and job-object aspects. |
| 5,475,507 A | 1995-12-12 | Suzuki et al. | Color image processing, automatic contour detection | Color/image processing — relevant to the color space conversion / imaging operation elements (implicated by IPR claim 24 "color correction"). Weak alone. |
| 5,537,517 A | 1996-07-16 | Wakabayashi et al. | Information processing device using an accessory control device | Peripheral control architecture. Background. |
| 5,566,278 A | 1996-10-15 | Patel et al. | Object oriented printing system | Notable: object-oriented representation of print jobs/pages — the closest thing in this slice to a "job object"/"document object" representation. Possible § 102 candidate for object-representation limitations; not for wireless/mobile. |
| 5,613,124 A | 1997-03-18 | Atkinson et al. | Generating/storing multiple representations of a source object in object storage | Multiple representations of one document object (cf. "full" vs. "reduced" document object). Background-but-thematic. |
| 5,625,757 A | 1997-04-29 | Kageyama et al. | Printing system | Background. |
| 5,748,859 A | 1998-05-05 | Takayangi et al. | Transmitting/processing print data for a printer | Print-data transmission. Background. |
| 5,862,321 A | 1999-01-19 | Lamming et al. | System and method for accessing and distributing electronic documents | ⭐ The single most important examiner-cited reference. This is the walk-up/mobile-document-access art (Xerox PARC "document server" lineage). It is the only reference in either retrieved slice that arguably addresses mobile user + network-stored document + nearby output device. In the earlier PTAB section of this analysis, Lamming was listed as available prior art in this family; flagging a mild inconsistency: my retrieval shows Lamming is a reference cited on the face of the '577, and I did not confirm it as a ground within Roku's IPR2022-01269 petition. Treat "Lamming as IPR ground" as unverified. |
| 5,867,633 A | 1999-02-02 | Taylor, III et al. | Method and apparatus for processing and printing documents | Background. |
| 5,930,466 A | 1999-07-27 | Rademacher | Data compression of bitmaps using rows/columns divided into vertical slices | Relevant only to the compression steps recited in the spec/claims ("compression/decompression" of output data). Weak. |
| 5,931,919 A | 1999-08-03 | Thomas et al. | State-based object transition control and attribute-based locking | State-machine/job-state control and attribute locking — relevant to job/object state management and queuing, not to wireless. Possible § 102/§ 103 support for job-object/state limitations. |
| 5,940,843 A | 1999-08-17 | Zucknovich et al. | Information delivery system with restriction processing | Restriction/entitlement processing — background for the authentication/payment optional features. |
| 5,968,176 A | 1999-10-19 | Nessett et al. | Multilayer firewall system | Security/access control. Background for authentication. |
| 5,974,401 A | 1999-10-26 | Enomoto et al. | Digital print order and delivery method and system | Remote print ordering/delivery — network print-service art. Moderate relevance to "data output service." |
| 5,978,560 A | 1999-11-02 | Tan et al. | Load balancing of distributed printing systems using enhanced printer attributes | ⭐ Second-most relevant examiner citation: explicitly about distributing print work based on machine-readable printer attributes — i.e., an "output device object with one or more attributes." Strong § 103 combination candidate with Lamming; possible § 102 candidate for the attribute-negotiation limitations. |
| 5,983,200 A | 1999-11-09 | Slotznick | Intelligent agent for executing delegated tasks | Agent/delegation. Background. |
| 5,987,454 A | 1999-11-16 | Hobbs | Selectively augmenting retrieved text, numbers, maps, charts, still pictures, moving pictures and audio from a network resource | Content retrieval/augmentation — thematic only. |
| 6,009,464 A | 1999-12-28 | Hamilton et al. | Enabling application programs to communicate with network clients and servers | RPC/network-transparency art. Background. |
| 6,020,973 A | 2000-02-01 | Levine et al. | Centralized print server for interfacing one or more network clients with a plurality of printers | ⭐ Directly pre-dates the priority date and reads on the "server distinct from the information apparatus and the output device" architecture. The best § 102(a)/(b) candidate in the retrieved set for the server-mediated output architecture — but it is LAN-centric, with no mobile/wireless pervasive-output teaching. |
Table B — Examiner-cited U.S. patent references, verified (issue dates 2002-12-11 → 2009-09-22)
Source: FreePatentsOnline, https://www.freepatentsonline.com/7944577.html ("US Patent References"). The list is presented newest-first; I retrieved 28 rows before truncation. ⚠️ Filing dates were not exposed.
Critical analytical point before the table: every reference in Table B issued after the '577's 2000-11-20 priority date. Pre-AIA § 102(a)/(b) treatment as patents/printed publications is therefore unavailable. They can only be prior art under pre-AIA § 102(e) (and then § 103) if their U.S. filing dates precede 2000-11-20. The fact that the examiner cited 2002–2009 art at all is itself evidence that prosecution did not treat the claims as fully entitled to the 2000-11-20 date — which is precisely the battleground Roku targeted in IPR2022-01269. That is a substantive finding worth carrying forward.
| Patent / Pub. | Issue or pub. date | Inventor | Title (as retrieved) | Provisional § 102(e) read |
|---|---|---|---|---|
| 7,593,123 | 2009-09-22 | Sugahara | Printing system for grouping printing apparatuses | Weak/background. |
| 7,478,403 | 2009-01-13 | Allavarpu et al. | Secure access to managed network objects via a configurable platform-independent gateway with object-level access control | Background for object-level access control/authentication. |
| 7,028,102 | 2006-04-11 | Larsson et al. | Method and system for presenting information | Background. |
| 6,857,716 | 2005-02-22 | Nagahashi | Print-controlling method and print-controlling device for printer | Printer-controller art — relevant to the output controller / raster-imaging elements of claim 1 only if earlier-filed. |
| 6,840,441 | 2005-01-11 | Monaghan et al. | Self-service terminal | Payment/self-service kiosk — thematic for the payment features. |
| 6,778,289 | 2004-08-17 | Iwata | Image processing device | Imaging background. |
| 6,775,407 | 2004-08-10 | Gindele et al. | Producing a final modified digital image using a source image and a difference image | Image-processing background. |
| 6,760,745 | 2004-07-06 | Tan et al. | Web server replicated mini-filter | Network-server background. |
| 6,751,732 | 2004-06-15 | Strobel et al. | Secure delivery and printing of documents via a network device | Relevant to secure delivery → authentication limitations. |
| 6,745,229 | 2004-06-01 | Gobin et al. | Web-based integrated customer interface for invoice reporting | Background. |
| 6,741,871 | 2004-05-25 | Silverbrook et al. | Mobile phone with interactive printer | Notable: a mobile phone + printer system. But this is Silverbrook/Netpage-style interactive (coded-substrate) printing, which requires coded pages and a page server — architecturally different from the claimed device-independent output-data scheme. Flagged: I did not retrieve its claims, so treat the comparison as title-based. |
| 6,738,841 | 2004-05-18 | Wolff | Method and apparatus for processing document requests at a printer server | Relevant to server-side document processing for a printer; § 102(e) candidate for the server-conversion limbs. |
| 2004/0057075 A1 | 2004-03-25 | Stewart et al. | System, method and recordable medium for printing services over a network | Pre-grant publication — § 102(e) candidate only with pre-2000-11-20 US filing. |
| 6,705,781 | 2004-03-16 | Iwazaki | Printing service method for printing system and the printing system | Print-service art. |
| 6,697,848 | 2004-02-24 | Hamilton et al. | Enabling application programs to communicate with network clients and servers | Background (successor to 6,009,464). |
| 6,694,371 | 2004-02-17 | Sanai | Communication interface device and method | Interface/adaptor art — thematic for communication units. |
| 6,658,625 | 2003-12-02 | Allen | Apparatus and method for generic data conversion | Relevant to generic/device-independent format conversion before output. |
| 6,643,650 | 2003-11-04 | Slaughter et al. | Mechanism and apparatus for using messages to look up documents stored in spaces in a distributed computing environment | ⭐ Jini-style service discovery + message-based object lookup. This is the reference the earlier PTAB section listed among available art; my retrieval shows it is a reference cited on the face of the '577 (Slice 2). It maps well to the discovery process / output-device-object retrieval features. § 102(e)/§ 103 candidate only if earlier-filed. |
| 6,623,527 | 2003-09-23 | Hamzy | Method for providing a document with a button for a network service | Background for UI-triggered network services. |
| 2003/0160993 A1 | 2003-08-28 | Kang | Method for printing to a networked printer | Pre-grant pub — § 102(e) candidate only. |
| 6,604,135 | 2003-08-05 | Rogers et al. | WWW client-server dynamic interactive system and method | Background. |
| 2003/0120754 A1 | 2003-06-26 | Muto et al. | Device searching apparatus | ⭐ Relevant to the discovery/search-for-available-output-device process (Fig. 5 steps 501–508). |
| 6,578,072 | 2003-06-10 | Watanabe et al. | Network photograph service system | Thematic (photo print services). |
| 6,546,387 | 2003-04-08 | Triggs | Computer network information management using intelligent software agents | Agent-based retrieval background. |
| 6,515,988 | 2003-02-04 | Eldridge et al. | Token-based document transactions | Document-job/accounting background. |
| 2002/0194302 A1 | 2002-12-19 | Blumberg | Method and system for client-less viewing of scalable documents | ⭐ Relevant to the "output the full document even though the client can't render it" rationale (server-side/client-less rendering). |
| 6,493,104 | 2002-12-11 | (not retrieved) | Data processing system/method permitting a computer to automatically detect the presence of and establish a communications link with a printer | ⭐ Relevant to automatic device discovery and link establishment (Fig. 5). |
Table C — Art asserted in IPR2022-01269 (NOT examiner-cited in the slices I retrieved)
These are materially more important than the examiner citations, and they should be kept in a separate bucket. Per the earlier PTAB section (sourced to the PTACTS petition copy of IPR2022-01269), Roku asserted § 103 — not § 102 — over these:
| Reference | Ground mapping (per petition, as previously reported) |
|---|---|
| Saulpaugh, US 6,850,979 (issued 2005-02-01) | Primary reference, Grounds 1a/1b (with Ghori; +Engeldrum for claims 14, 24–25) |
| Ghori, US 6,243,772 (issued 2001-06-05) | Secondary, Grounds 1a/1b; user-level security / transparent local-vs-remote object access. Would fall in my un-retrieved 2000–2002 gap if it was also examiner-cited — unverified whether it appears on the '577 face |
| Engeldrum, US 5,638,117 (issued 1997-06-10) | Added for color-correction limitations (claims 14, 24–25) |
| Gu, US 6,892,230 (issued 2005-05-10) | Grounds 2a/2b; secondary/pairing reference with Shamoon. ⚠️ I did not verify Gu's title or subject matter in this session — do not rely on a description of it from me |
| Shamoon, US 7,233,948 (issued 2007-06-19) | Grounds 2a/2b. ⚠️ Same caveat — title/subject matter not verified in this session |
⚠️ Note: Saulpaugh (2005), Gu (2005), and Shamoon (2007) all postdate 2000-11-20 and are therefore § 103 references whose availability depends entirely on (a) being § 102(e) art by earlier US filing date, or (b) the '577 being denied its 2000-11-20 priority. That is why the earlier PTAB section's point about Flexiworld's October 22, 2000 conception win in IPR2022-00775 is the controlling fact for any renewed challenge.
§ 102 anticipation analysis — and why I am deliberately limiting it
I cannot give you a reliable claim-by-claim § 102 mapping, and I want to be explicit about why rather than manufacture one. Section 102 anticipation requires every element of a given claim to be disclosed in a single reference, arranged as in the claim. That analysis requires: (1) the granted claim text of the '577, and (2) the full text and claims of each reference. In this session I have neither. As the earlier summary in this analysis already flagged, the granted claims were not in the patent text provided, and the best available reconstruction came from a PTAB petition quoting claim 1 (an "output controller"-side method reciting a wireless communication unit, a processor, application software performing at least a digital imaging operation, memory for storage and for queuing/spooling, authenticating the information apparatus or user, providing an output device object wirelessly, wirelessly receiving output data including device-dependent data, and queuing/spooling that output data; with dependent claim 12 reciting that the output controller is included in the output device). That reconstruction is itself flagged as unverified.
With that caveat stated, here is my best-effort, explicitly provisional read of the § 102 candidates — i.e., references that could conceivably anticipate on their own, as opposed to the many that are only § 103 fodder:
Tier 1 — genuine single-reference § 102 candidates (verified citations):
- US 5,862,321 (Lamming et al.), issued 1999-01-19 — available under § 102(a)/(b) (issued before 2000-11-20). Best candidate for the core "access and distribute electronic documents to a nearby output device from a mobile information apparatus" concept. Provisionally maps to: the information-apparatus/output-device interaction and document-object handling. Does not appear to supply the "remote server application distinct from both the apparatus and the device that generates device-ready output data" limb. So: plausible § 102 as to an apparatus/system claim, weak as to the server-conversion method claim.
- US 6,020,973 (Levine et al.), issued 2000-02-01 — § 102(a) art (issued two months after the earliest priority date but before the 2007 filing, so it is at minimum § 102(b) art as to the '577 claims; and if the claims do not get the 2000-11-20 date, it is squarely § 102(a)/(b)). Best § 102 candidate for the "centralized print server between clients and printers" architecture — i.e., the server-mediated output limb. It does not teach the mobile/wireless/limited-resource motivation.
- US 5,978,560 (Tan et al.), issued 1999-11-02 — § 102(a)/(b) art. Best candidate for the "output device object with one or more attributes relating to the output device" limitation (enhanced printer attributes driving distributed print management), possibly in combination with the job-object limitations.
Tier 2 — § 102(e)-only candidates (post-2000 issuance; availability hinges on earlier US filing):
4. US 6,643,650 (Slaughter et al.) — service discovery + message-based object lookup; candidate for the discovery/output-device-object-retrieval limitations.
5. US 6,738,841 (Wolff) — document requests processed at a printer server; candidate for the server-side processing limb.
6. US 2003/0120754 A1 (Muto et al.) — device searching apparatus; candidate for the discovery step.
7. US 2002/0194302 A1 (Blumberg) — client-less viewing of scalable documents; candidate for the "output the original document the client cannot render" rationale.
8. US 6,741,871 (Silverbrook et al.) — mobile phone + printer; candidate only for the "mobile apparatus outputs to a printer" preamble, and weakened by its coded-substrate/Netpage architecture.
Everything else in Tables A and B is best characterized as background art or § 103 support, not a standalone anticipation: the 1993–1998 entries (Sasaki, Sklut, Motoyama, Hower, Suzuki, Wakabayashi, Patel, Atkinson, Kageyama, Takayangi, Taylor, Rademacher, Nessett, etc.) are single-limb references to print data, job options, object storage, compression, or firewalls. That they were cited by the examiner, and yet the claims issued, tells you the examiner treated them as background against a wireless pervasive-output-from-a-limited mobile device invention.
⚠️ Two things I could not confirm and will not guess at: (a) whether Ghori US 6,243,772 or any other 2000–2002 reference appears on the '577's face (falls in my retrieval gap); (b) whether Saulpaugh/Gu/Shamoon/Engeldrum appear anywhere in the '577's cited-references list — I did not see them in the two slices I retrieved, which suggests they were IPR-discovered art, not examiner-cited art, but that inference is not confirmed.
What I could not verify (explicit)
- The complete and ordered "References Cited" list on the '577 front page — retrieved in two truncated, non-overlapping slices with a 2000–2002 gap. ⚠️
- Foreign patent references and "Other References" (non-patent literature) — not retrieved at all. ⚠️
- Filing dates / priority dates of each reference — not exposed by the mirror sources; I gave issue/publication dates only. A proper pre-AIA § 102(e) analysis needs those filing dates. ⚠️
- The granted claim text of US 7,944,577 — still not retrieved (this was flagged in the earlier summary and remains unresolved). Any claim-number mapping above is therefore provisional. ⚠️
- Titles/subject matter for Gu US 6,892,230 and Shamoon US 7,233,948 — I did not verify these in this session. ⚠️
- Mild inconsistency flagged: the earlier PTAB/strategic sections describe Lamming '321 and Slaughter '650 as part of Roku's prior-art arsenal. My retrieval shows both are references cited on the face of the '577; I did not confirm them as grounds inside Roku's IPR2022-01269 petition. The § 103 ground mapping I could verify was Saulpaugh+Ghori(+Engeldrum) and Gu+Shamoon.
Practical takeaways
- The examiner-cited art is weak on the patent's actual point of novelty. The face citations are a tour of pre-2000 print-path plumbing (print servers, printer attributes, object-oriented printing, compression, firewalls). Only Lamming '321, Levine '6,020,973, and Tan '5,978,560 come close to the "mobile apparatus → network → device-attribute-aware output" architecture — and none of them teaches the combination of limited-resource mobile client + remote server-side device-dependent conversion.
- The citation dates themselves are evidence about priority. The presence of 2002–2009 art on the face implies the examiner did not accord the claims full 2000-11-20 priority benefit during prosecution. Expect any future challenger (and the record from Roku's petition) to attack priority head-on — and note from the earlier section that Flexiworld has already won a corroborated October 22, 2000 conception fight in IPR2022-00775 on a sibling patent.
- Anticipation is the wrong tool here. Nobody has ever obtained an anticipation holding against this patent; Roku went § 103 (two multi-reference grounds) and settled pre-institution. If you need § 102, the realistic candidates are Lamming '321 and Levine '6,020,973, and both leave the server-side device-dependent-conversion limb on the table.
- Timing check: the '577 is recorded as Expired – Fee Related, adjusted expiration 2023-01-29 (per the earlier sections). A § 102 analysis today is defensive/historical — relevant to pre-2023 conduct, not to prospective relief.
Key sources: https://www.sumobrain.com/patents/us/Output-controller-mobile-pervasive-digital/7944577.html (Domestic Patent References, 1993–2000 slice) · https://www.freepatentsonline.com/7944577.html (US Patent References, 2002–2009 slice) · Google Patents https://patents.google.com/patent/US7944577/en (bibliographic data, prior-art keywords, litigation metadata) · PTACTS IPR2022-01269 petition copy (grounds and reference list, as reported in the earlier PTAB section).
Generated 9/15/2026, 4:47:58 AM
Obviousness
Combinations of prior art that suggest the claimed invention would have been obvious under 35 U.S.C. § 103.
I'll ground the prior-art references and claim structure before running the § 103 analysis. Let me pull the key references and the granted claims.
Let me pull the granted claims and the remaining references.
Obviousness Analysis — U.S. Patent No. 7,944,577 B2 under 35 U.S.C. § 103
Prepared: April 26, 2026 · Patent: US 7,944,577 B2 ("the '577 patent"), Output controller for mobile and pervasive digital content output · Appl. No. 11/933,005 · Filed 2007-10-31 · Granted 2011-05-17 · Assignee Flexiworld Technologies, Inc. · Status Expired – Fee Related (adjusted expiration 2023-01-29)
0. How this memo builds on the prior sections, and what I could not re-verify
I am not repeating the summary, litigation, PTAB, or assignment sections. I build directly on three findings from those sections and add the § 103 layer:
- The only substantive prior-art work ever assembled against this patent is Roku's petition in IPR2022-01269 (filed 2022-07-29; terminated-settled pre-institution 2022-10-31). That petition is the de facto prior-art record, and its exhibit list is now the primary source for the reference set: EX1005 US 6,850,979 (Saulpaugh), EX1011 US 6,243,772 (Ghori), EX1012 US 5,638,117 (Engeldrum), EX1013 US 6,892,230 (Gu), EX1014 US 7,233,948 (Shamoon), EX1015 US 9,965,233 (Chang), EX1016 US 5,862,321 (Lamming), EX1017 US 6,643,650 (Slaughter), plus the Saber declaration (EX1003) and claim listing (EX1004) — confirmed at
https://ipverse.greyb.com/ptab-web/cases/case-details/IPR2022-01269. - No PTAB or court has ever reached the merits, so nothing below has been adjudicated. This is a fresh analysis of an untested record.
- ⚠️ Two constraints on this memo, carried forward and now material to § 103:
- The granted claim text was not in the source text I was given, and I could not retrieve the "What is claimed" section verbatim within this session's budget. My claim-1 reconstruction is second-hand — from a PTAB petition quoting the patent (ptacts.uspto.gov file 1549999). Element-by-element mapping below is therefore provisional. Treat every "claim 1 requires X" statement as a working hypothesis to be re-checked against EX1001/EX1004.
- I could not re-verify the filing dates of Gu (US 6,892,230), Shamoon (US 7,233,948), Slaughter (US 6,643,650), Engeldrum (US 5,638,117), or Lamming (US 5,862,321) in this session. Those dates are outcome-determinative (see § 1).
1. Framing the § 103 question correctly
Three framing issues drive the whole analysis. Ignoring them produces a § 103 opinion that is legally fragile even if technically persuasive.
1.1 The effective filing date is contested, and it is the first battleground
The '577 patent claims benefit back to a priority date of 2000-11-20, with the family descending from 2000-era provisional applications. Roku submitted five provisionals as exhibits (EX1006–EX1010: US Prov. 60/209,525; 60/209,140; 60/209,430; 60/208,011; 60/202,975) — that is a signal that Roku was attacking both the date and the written-description support of the priority claim, not merely the claims themselves.
Practical consequences for § 103:
- A reference is only § 102/§ 103 prior art if it predates the effective date. Roku applied a November 18, 2001 POSITA/prior-art cut-off while expressly reserving the right to contest priority — i.e., Roku ran a two-track theory: (i) prior art predating 2000-11-20 (Saulpaugh, Ghori), and (ii) prior art that only qualifies if the priority claim is broken.
- ⚠️ If any of Gu, Shamoon, Slaughter, or Engeldrum has a filing date after the effective date, it drops out of the § 103 combination entirely unless priority is knocked out. Gu (US 6,892,230, "Dynamic self-configuration for ad hoc peer networking") and Shamoon (US 7,233,948) are the references I would scrutinize first, because their Ground 2 role makes the Gu + Shamoon combination wholly dependent on date resolution. Verify these filing dates against the front pages of EX1013 and EX1014 before relying on Ground 2.
- The Patent Owner has a proven priority-defense playbook. In the sibling proceeding IPR2022-00775 (Unified Patents v. Flexiworld, on US 9,836,257), the Board's Final Written Decision (Paper 41, 2023-11-01) held claims 27–28 not unpatentable, crediting Flexiworld's corroborated October 22, 2000 conception via provisional-application metadata to swear behind the references. Any § 103 theory that depends on a 2001+ reference should assume a Rule 131 / priority challenge will be mounted and be prepared with conception/reduction-to-practice counter-evidence — or avoid the fight by relying only on pre-October-2000 art.
1.2 The specification's own admissions shrink the invention to a combination question
This is the single most useful § 103 lever in this file, and it comes from the '577 patent itself:
- The specification admits that an "output controller" is a known, conventional device: "One example of such an implementation is a print server connected to an output device 106" and "[output controller] may sometimes be referred to as print server or output server."
- It admits that printer controllers, RIP, color correction, halftoning, compression, decoding, and queuing/spooling are conventional (FIGS. 10A/10B: "a conventional printing system includes three basic components: a raster image processor, a memory buffer, and a marking engine"; RIP "may be located within an output device itself … [or] in a software application or device driver").
- Its own discovery-process section lists the known discovery/interoperability protocols: "Bluetooth, HAVi, Jini, Salutation, Service Location Protocol, and Universal Plug-and-play among others" — an express admission that service advertisement, device discovery, and capability negotiation over wireless links were known.
- It admits wireless printing hardware existed: Bluetooth, IEEE 802.11, HomeRF/SWAP, IrDA, USB, FireWire, Ethernet.
So the § 103 question is not "was an output controller with a processor and memory new?" — the patent concedes it was not. The question is whether combining a wireless print-server-style output controller with (a) authentication of the sending information apparatus, (b) an exchange of device-capability/attribute data ("output device object") with that apparatus, (c) receipt of device-dependent output data from that apparatus, and (d) queuing/spooling before rendering was an unobvious combination in 2000. That is a combination-of-known-elements case, which is precisely where KSR bites hardest.
1.3 The claim-reconstruction hypothesis I am testing
Per the PTAB petition quoting the '577, granted claim 1 appears to be a method performed by an output controller comprising: a wireless communication unit; a processor; application software including processing content with at least a digital imaging operation; a memory/storage component for storing data and for queuing/spooling; the steps of establishing a wireless channel with an information apparatus including authenticating the apparatus or its user; obtaining at least part of an output device object and wirelessly providing it to the information apparatus; wirelessly receiving output data from the information apparatus, the output data including the digital content for rendering and device-dependent data related to the output device; and queuing or spooling the received output data for rendering. Dependent claim 12 reportedly recites that "the output controller is included in the output device."
Claims 1–14 and 23–25 were challenged; claims 15–22 were never challenged at all. ⚠️ I cannot describe their scope.
2. Level of ordinary skill in the art (POSITA)
Proposed: a bachelor's degree in computer science, electrical engineering, or equivalent, plus 2–3 years of experience in networked printing / peripheral device drivers / distributed computing, or a master's degree plus ~1 year. This is essentially the level Roku applied (a practitioner as of 2001-11-18 per the petition).
The POSITA's knowledge base in late 2000 is the key to every motivation-to-combine argument below. That practitioner knew:
- Print servers and spoolers were commodity products (the '577 specification says so).
- Wireless LAN and personal-area networking (Bluetooth 1.0, IEEE 802.11, IrDA, HomeRF) were commercialized and standardized.
- Device discovery and capability advertisement were standardized: SLP (RFC 2608, June 1999), Jini (Sun, 1999), UPnP (1999), Salutation, HAVi — all named in the '577 specification.
- Network print-job submission with job and printer attributes was standardized: the Internet Printing Protocol — RFC 2566 (April 1999) "IPP/1.0: Model and Semantics," followed by RFC 2910/RFC 2911 (2000) — which defines printer objects with attribute sets, job objects with attributes, device-capability query, and spooling/queuing semantics.
- Device-independent rendering by a remote server was the core premise of web/print-server architectures: submit content + target-device description to a server; the server renders device-ready data.
⚠️ RFC 2566/2608 and the Jini/UPnP specifications were not in Roku's ground list. They are, in my view, the most valuable additions available to a new challenger, because they are printed publications with hard, verifiable 1999 publication dates and they go directly to the "output device object" and "queuing/spooling" limitations. See § 7.
3. Element-by-element mapping of claim 1 (working hypothesis)
Legend: ● = teaches the element · ◐ = teaches an analogous/partial element · – = silent / needs a secondary reference. Confidence tags in the Notes column reflect my verification level, not the reference's actual content.
| # | Claim 1 limitation (per petition reconstruction) | Saulpaugh US 6,850,979 | Ghori US 6,243,772 | Gu US 6,892,230 | Shamoon US 7,233,948 | Slaughter US 6,643,650 | Engeldrum US 5,638,117 | Lamming US 5,862,321 | Notes / confidence |
|---|---|---|---|---|---|---|---|---|---|
| (a) | Output controller having a wireless communication unit | – | ● | ◐ | – | – | – | ◐ | Ghori: appliance unit with second digital wireless transceiver + control unit; confirmed from granted claim 1 text (FPO) |
| (b) | Processor + application software incl. processing content with ≥1 digital imaging operation | ◐ | ◐ (compression/decompression engine in control unit) | ◐ | – | ◐ | ● (color correction/transform) | – | RIP/color/halftone admitted conventional in '577 FIGS. 10A/10B; Engeldrum supplies color-correction. ⚠️ Engeldrum title unverified this session |
| (c) | Memory/storage for storing data and for queuing/spooling | ◐ | ● (memory buffer; decompression) | – | ◐ (persistent store) | – | – | – | Queuing = admitted conventional print-server/spooler art + IPP (RFC 2566). ⚠️ Shamoon's exact disclosure unverified |
| (d) | Establishing a wireless channel with an information apparatus, including authenticating the apparatus/user | ● (authentication service generates credential; credential embedded in outgoing messages; integrity verification; negotiates security level) | ● (wireless link establishment) | ◐ (ad hoc peer networking, auto-config) | ◐ | – | – | ◐ | Saulpaugh's authentication disclosure is confirmed from its abstract |
| (e) | Obtaining ≥ part of an output device object and wirelessly providing it to the information apparatus | ● (service advertisement / message schema defining permitted messages & capabilities) | ◐ (appliance capabilities/compression support) | ● (device description / capability discovery for peer devices) | – | ● (service interface/data transform description) | – | – | This maps the coined "output device object" onto the known service-advertisement / device-description concept. Gu/UPnP + Saulpaugh/Jini are the natural pairing |
| (f) | Wirelessly receiving output data from the information apparatus, including the digital content for rendering + device-dependent data related to the output device | ◐ (type-safe messages per negotiated schema) | ● (output presentation signals from PC; applicant device receives presentation data) | – | – | ● (server-side transform of data to a target representation) | ● (device-dependent color transform) | ◐ | Ghori is the strongest single reference for "device sends content wirelessly to an appliance output unit"; Slaughter supplies server-side transform-to-target |
| (g) | Queuing or spooling the received output data for rendering | ◐ (gate/message scheduling) | ◐ (buffer before display) | – | – | – | – | – | Weakest limitation on the petition's art alone — best supported by conventional print-spooler art and IPP |
Dependent-claim clusters:
- Claim 12 — "output controller is included in the output device" → squarely conventional (FIGS. 3A/3B of the '577 itself; Ghori's control unit is inside the appliance unit).
- Claim 14 / 24–25 — color-correction / color-management limitations → Engeldrum.
- Claims 23–25 — output-device-object / authentication-related dependent limitations → Saulpaugh.
4. Combination 1 — Saulpaugh + Ghori (Ground 1a: claims 1–14 and 23)
4.1 What each reference contributes
US 6,850,979 (Saulpaugh et al., Sun Microsystems; priority 2000-05-09; granted 2005-02-01) — "Message gates in a distributed computing environment." Confirmed content (abstract,
https://wiki.golden.com/wiki/US_Patent_6850979_...): a message gate is a secure message endpoint for a client or service in a distributed environment; gates "perform the sending and receiving of messages between clients and services using a protocol specified in a service advertisement"; creation of a message gate may involve an authentication service that generates an authentication credential and "may negotiate the desired level of security and the set of messages that may be passed between client and service"; gates verify messages against a message schema to ensure the messages are allowed; gates embed the authentication credential in outgoing messages and verify integrity. Messages may be XML.
Why it matters: Saulpaugh independently supplies the distributed-computing architecture elements of claim 1 — wireless/networked client-service channel, authentication of the counterparty, exchange of a service advertisement/message schema that constrains what the service will accept (the functional equivalent of an "output device object"), and device-independent messaging.US 6,243,772 (Ghori et al.; granted 2001-06-05) — "Method and system for coupling a personal computer with an appliance unit via a wireless communication link to provide an output display presentation." Confirmed content (granted claim 1,
https://FreePatentsOnline.com/6243772.html): establishing a wireless communication link between an appliance unit and a personal computer via first/second transceivers through a control unit "including a decompression engine configured to decompress signals received across the wireless communication link and a compression engine," and "providing an output display presentation on a display screen of the appliance unit based on first signals transmitted from the personal computer via the wireless communication link." Dependent claims add spread-spectrum links, audio output, and graphics/audio/audio-visual data composed before transmission.
Why it matters: Ghori supplies the output-side hardware elements — a wireless-capable appliance/output unit with a control unit, buffering/compression, and an output device that renders content received wirelessly from a computing device.
4.2 Why a POSITA would have combined them (the motivation)
Under KSR Int'l Co. v. Teleflex Inc., 550 U.S. 398 (2007), and In re Keller, 642 F.2d 413, 425 (CCPA 1981), the test is what the combined teachings would have suggested to a POSITA — the references need not suggest the combination in the same way or for the same purpose. Five independent rationales work here, any one of which suffices:
- Known technique, predictable result (KSR, 550 U.S. at 416–17). Print servers were admitted-commodity. Saulpaugh's authenticated service-advertisement messaging and Ghori's wireless appliance output unit are both known techniques in the same technical field (networked/wireless peripheral output). Combining an authenticated distributed-messaging client-service layer with a wireless output appliance yields nothing more than the predictable sum of the parts.
- Same field, common problem. Both references address delivering content/data over a network or wireless link from a computing device to a device that renders it. Saulpaugh addresses the secure transport/negotiation half; Ghori addresses the wireless rendering device half. A POSITA solving "how do I let a portable computer print through a printer without a bespoke driver" would naturally reach for both.
- Market and industry demand. The '577 specification itself documents the 2000-era demand: mobile workers wanting to print e-mail, flight schedules, articles, and photos at nearby printers, and the pain of per-model driver installation. That demand was well known across the industry (which is why Bluetooth printing, HomeRF, IPP, and web-to-print were all being commercialized in 1999–2000). KSR recognizes "design incentives and other market forces" as a valid motivation.
- Design incentive to reduce driver proliferation. The whole point of the problem being solved is that N printer models × M mobile platforms = N×M drivers. Routing device-independent content through a controller that advertises its own capabilities (Saulpaugh's service advertisement; the "output device object") and does the device-specific processing at the output side (the admitted conventional output/printer controller, FIGS. 10A/10B) is the self-evident architectural fix. The '577 specification admits this architecture was known — it just claims a particular feature set for the controller.
- Simplicity / reduction of parts. Placing the wireless unit, authentication, capability advertisement, and spooling in one controller at the output device is a straightforward substitution of a print server with a wireless print server — an enumerated KSR rationale (substitution of a known element to obtain a predictable advantage).
4.3 Differences to address candidly
The combination's soft spots, which a KSR analysis must confront rather than paper over:
- "Output device object" as a named, exchanged object. No petition reference uses the term. Answer: § 103 does not require the reference to use the claim's words (In re Bond, 910 F.2d 831, 832 (Fed. Cir. 1990)). Saulpaugh's service advertisement/message schema and Gu's device description perform the identical function of conveying a device's identity/capabilities to the counterparty.
- Queuing/spooling inside the controller (limitation (g)). This is the weakest element on the petition's art. Answer: queuing/spooling was the defining conventional function of a print server — the '577 specification concedes as much — and IPP (RFC 2566) standardizes job attributes and spooling. Combining a wireless print server with a spooler is substitution of a known element.
- The combination is not "compelled" by either reference. Answer: unnecessary. KSR and In re Keller confirm that explicit teaching, suggestion, or motivation in the references is not required where the combination is of known elements for their known purposes with predictable results.
5. Combination 2 — Saulpaugh + Ghori + Engeldrum (Ground 1b: claims 14 and 24–25)
Engeldrum (US 5,638,117) is cited in Roku's grounds for the color-correction/color-management limitations (per the ground mapping at Ground 1b, adding Engeldrum "for the color-correction limitation of claim 24"; ⚠️ I could not re-verify the reference's title or specific disclosure in this session — verify the front page of EX1012 before using it).
Motivation: device-dependent color reproduction is the canonical reason output data must be adapted to a specific output device. A POSITA combining Ghori's wireless output appliance with a color-managed rendering path would necessarily reach for known color-correction/color-transform techniques to make the transmitted content render correctly on the target device. Adding a known color-correction reference to a known wireless-output combination is a paradigm KSR case: "a court must ask whether the improvement is more than the predictable use of prior art elements according to their established functions." 550 U.S. at 417.
⚠️ Date flag: Engeldrum is a pre-1997 reference (US 5,638,117 issued 1997), so it comfortably predates even an October 2000 conception date. It is date-safe. Gu and Shamoon are not (see § 6).
6. Combination 3 — Gu + Shamoon (+ Engeldrum) (Ground 2a / 2b)
Per the petition's summary, Ground 2a/2b maps Gu (US 6,892,230) + Shamoon (US 7,233,948), with Engeldrum added for claim 24's color limitation. ⚠️ I flagged in the PTAB section that the precise claim scope of Grounds 2a/2b is less verified than 1a/1b, and that flag carries over here.
- Gu (US 6,892,230) — "Dynamic self-configuration for ad hoc peer networking" (Microsoft). This is the device-discovery / capability-description reference: ad hoc peer networking with automatic self-configuration, device/service description, and bridging to non-conforming devices. Functionally, Gu's device description and capability exchange are the "output device object" analog, and Gu supplies the automatic configuration motivation (zero-configuration on the user's part) that the '577 patent touts.
- Shamoon (US 7,233,948) — I could verify only the existence and petition role; the reference's title as I recall it relates to persistent stores. It appears to be cited for the memory/storage + persistence aspects of the controller. ⚠️ I could not verify its title, disclosure, or filing date in this session. Do not rely on Ground 2 until EX1014's front page is checked.
- Motivation: Gu and Shamoon are both drawn from the same late-1990s/2000 distributed-systems literature as Saulpaugh. A POSITA building a wireless output controller would adopt auto-configuring peer discovery (Gu) to eliminate user setup, and a persistent store (Shamoon) to hold queued/spooled jobs and device state. Both are known techniques applied to their known purposes.
⚠️ Material date risk: Ground 2 lives or dies on whether Gu and Shamoon predate the effective filing date. If either post-dates 2000-11-20, the combination collapses unless priority is first invalidated. Given the sibling Board's willingness to credit October 22, 2000 conception (IPR2022-00775 FWD), Ground 1a/1b (Saulpaugh + Ghori, both date-safe) is strategically the stronger attack; Ground 2 is the backup.
7. Combinations I would add to the Roku ground set (the highest-value gap)
Roku's petition left three obvious, date-safe, printed-publication categories on the table. Each closes a limitation the petition's art supports only thinly — especially queuing/spooling (g) and the exchanged "output device object" (e).
| Reference / category | Date (verify) | Why it is valuable | Closes |
|---|---|---|---|
| IPP: RFC 2566 (Apr. 1999) "IPP/1.0: Model and Semantics"; RFC 2910 / RFC 2911 (2000) | 1999–2000 printed publications | Defines printer objects with attribute sets, job submission with job attributes, device-capability query, and spooling/queuing semantics over a network | (e) output device object; (g) queuing/spooling; (f) device-dependent job data — a strong, primary reference, not just a gap-filler |
| SLP — RFC 2608 (June 1999); Jini (Sun, 1999); UPnP Device Architecture (1999/2000) | All 1999–2000 | Standardized service discovery with advertised service/device attributes over a network — the literal antecedent of "output device object" exchange. The '577 specification names SLP, Jini, UPnP, HAVi and Salutation as known. | (d) channel establishment; (e) device object exchange, via an admitted-prior-art admission in the patent itself |
| Conventional print-server / spooler art (LPR/LPD; commercial print servers; the '577's own FIGS. 10A/10B printer controller + memory buffer) | pre-2000 | The '577 specification admits "print server" as the output controller's conventional example and admits RIP/memory buffer/marking engine as a "conventional printing system" | (b) digital imaging operation; (c) storage; (g) queuing/spooling; (a)/(e) controller with wireless adapter |
| Slaughter US 6,643,650 (Sun) — petition EX1017; "Mechanism and apparatus to access and transform data" ⚠️ title unverified | ~2000 | Server-side data transformation to a target representation — the "server application generates output data" concept in the abstract, and a bridge to a distributed transform service | (f) device-dependent output data |
| Lamming US 5,862,321 (Xerox) — petition EX1016 ⚠️ title unverified | 1999 issue | Portable-device/document-orchestration art from the ubiquitous-computing literature; useful for the document object / pointer-to-content side and for § 103 "whole-disclosure" context | document-object side; context for the problem |
The single most persuasive framing available: use IPP + SLP (or UPnP) + a conventional wireless print server as the primary combination for the controller-side limitations, and use Saulpaugh + Ghori for the wireless/authentication layer. Both halves are printed publications with verifiable 1999 publication dates — which means you can win without ever reaching the contested priority date, the very fight Flexiworld won in IPR2022-00775.
8. Motivation to combine — consolidated argument
Under Graham v. John Deere Co., 383 U.S. 1 (1966), and KSR, the following rationales are available and should be pleaded cumulatively. Any single one supports the conclusion; together they make the teaching-away defense difficult.
R1 — Predictable combination of known elements (KSR at 416–17). Every element of claim 1 was individually known: wireless links (Ghori, Bluetooth/IEEE 802.11/IrDA); authentication (Saulpaugh); capability advertisement/device description (Gu; SLP/Jini/UPnP, admitted in the '577 specification); device-dependent rendering and color correction (Engeldrum; admitted RIP/halftone in FIGS. 10A/10B); queuing/spooling (admitted print-server art; IPP RFC 2566). The combination performs no new function; it aggregates known functions.
R2 — Known technique applied to a known problem. The problem — how to let a resource-constrained portable device output to an arbitrary nearby output device without installing device-specific drivers — was the industry's stated problem, documented by the '577 specification's own background.
R3 — Market forces / design incentive (KSR at 417, 421). Commercial demand for mobile wireless printing and the driver-proliferation cost curve made the architecture self-evident. Bluetooth printing, HomeRF, IPP, and web-to-print were all being commercialized contemporaneously.
R4 — Substitution of a known element with a predictable advantage (MPEP 2144.04). Substituting a wireless print server for a wired one, and placing the controller inside the output device (claim 12), are the textbook substitutions. The '577 specification expressly contemplates exactly these (FIGS. 3A/3B/3C: internal card, combined controller, external box "one example of such an implementation is a print server").
R5 — Teach-away-free environment. None of the references criticizes, disables, or discredits the others' approaches; Saulpaugh's authenticated service layer, Gu's auto-configuration, and Ghori's wireless appliance are complementary, not mutually exclusive. In re Gurley, 27 F.3d 551, 553 (Fed. Cir. 1994) requires actual criticism or discrediting for a teach-away — mere silence is not teaching away (In re Kahn).
R6 — Express admission in the patent itself. The specification's admissions of print servers, conventional printer controllers, and the enumerated discovery protocols (Bluetooth/HAVi/Jini/Salutation/SLP/UPnP) operate as admitted prior art and eliminate any argument that the claimed controller architecture was novel at the architectural level.
9. Anticipated Patent Owner rebuttals — and the responses
| PO argument | Response |
|---|---|
| Priority / swear-behind (their strongest play, per IPR2022-00775). "The provisional disclosed the invention; conception was Oct 22, 2000; the reference is not prior art." | Concede nothing and plan for it. (i) Prefer art that predates October 2000 — Saulpaugh (May 2000 priority), Ghori (1996-era), Engeldrum (1997), Lamming (1999 issue), plus IPP RFC 2566 (Apr 1999) and SLP RFC 2608 (Jun 1999) — so there is nothing to swear behind. (ii) Attack written-description support in the provisionals for each specific claim limitation, not the date generally: the corroborated conception evidence in IPR2022-00775 went to different claims of a different patent. Demand a limitation-by-limitation § 112 ¶ 1 support showing. (iii) Roku's five provisional exhibits show this was already planned. |
| The references are non-analogous art (distributed-computing middleware vs. printers). | Saulpaugh, Gu, Slaughter and Ghori are all in networked data-output / peripheral delivery — the same field of endeavor, and alternatively reasonably pertinent to the driver-elimination problem (In re Bigio, 381 F.3d 1320 (Fed. Cir. 2004)). IPP and SLP are literally printer/print-service standards. |
| "Output device object" is a coined term with no counterpart. | § 103 does not require the reference to use the claim's words; the function controls (In re Bond). Saulpaugh's service advertisement/message schema and Gu's device description perform it identically. Expect the PO to argue narrow construction — in which case the term may also be indefinite under § 112 ¶ 2, an independent invalidity posture. |
| Secondary considerations (long-felt need, industry praise, licensing success). | Interrogate nexus hard. The '577 patent has no product embodiment (per the assignment analysis, no evidence Flexiworld ever shipped a product); the licenses are litigation settlements, which have weak nexus and little weight (Iron Grip v. USA). Also note the decade-long delay between grant (2011) and assertion (2021) — weak evidence of long-felt unmet need. |
| "The Board already credited Flexiworld's conception." | That was IPR2022-00775 on US 9,836,257, a different patent and different claims. It produces no estoppel on the '577 (the '577's own IPR terminated pre-institution), and it is not a merits ruling on any claim of the '577. |
10. Strength assessment — where the § 103 case is strong, moderate, and weak
| Claim 1 limitation | Strength on the petition-plus-additions record | Why |
|---|---|---|
| (a) wireless communication unit in an output controller | Strong | Ghori express; Bluetooth/802.11/IrDA wireless print servers were commercial |
| (b) processor + application software, digital imaging operation | Strong | Admitted conventional (FIGS. 10A/10B); Engeldrum |
| (c) memory/storage | Strong | Ghori memory buffer; admitted print-server art |
| (d) establishing wireless channel with authentication | Strong | Saulpaugh's authentication service/credential is confirmed in its abstract |
| (e) obtaining/providing "output device object" to the information apparatus | Moderate–Strong | Functionally met (Saulpaugh service advertisement; Gu device description; SLP/UPnP), but the reverse-direction exchange with the sending information apparatus is the place PO will fight |
| (f) receiving output data with content + device-dependent data | Moderate | Ghori + Engeldrum + Slaughter; the "device-dependent data traveling with the job" nuance is IPP's home turf — add RFC 2566 |
| (g) queuing/spooling | Moderate | Weakest on the petition's art; strongly fixed by adding IPP/conventional spooler art |
| Claim 12 (controller in the output device) | Strong | Conventional; FIGS. 3A/3B |
| Claims 14, 24–25 (color) | Moderate | Depends on Engeldrum's disclosure ⚠️ unverified |
| Claims 15–22 | Unknown | Never challenged; text not available to me |
Overall: a well-pleaded § 103 case on claims 1–14 and 23 using Saulpaugh + Ghori (Grounds 1a/1b) is more likely than not to persuade a PTAB panel on the technical merits — but the two decisive variables are (1) whether the granted claim text matches the petition's reconstruction, and (2) whether PO re-runs its winning priority/conception play. Ground 2 (Gu + Shamoon) is materially weaker because of unresolved date exposure and my inability to verify Shamoon.
11. Bottom line
- The obviousness theory is sound and the record is already half-built. Roku's IPR2022-01269 assembled a complete § 103 roadmap — Saulpaugh + Ghori (Grounds 1a/1b, claims 1–14, 23) and Gu + Shamoon + Engeldrum (Grounds 2a/2b) — and then walked away pre-institution, generating zero estoppel and zero claim cancellations. Every ground remains legally available to a timely new challenger. KSR rationales R1–R6 above support the combination independently of any express teaching suggestion.
- The strongest available theory is NOT Roku's. It is a combination built on pre-October-2000 printed publications — IPP (RFC 2566, April 1999) + SLP (RFC 2608, June 1999) or UPnP/Jini + Saulpaugh + Ghori — because that avoids the priority/conception fight Flexiworld has already won once (IPR2022-00775 FWD, Paper 41, 2023-11-01, crediting corroborated October 22, 2000 conception). Add conventional print-spooler art for the queuing limitation.
- The claim-1 reconstruction and Engeldrum/Shamoon/Gu disclosures are unverified in this session. Before any of this is filed or relied upon, confirm: (i) the granted claims text (EX1001/EX1004); (ii) the front-page filing dates of EX1013 (Gu) and EX1014 (Shamoon); (iii) EX1012's (Engeldrum) actual disclosure; (iv) the five provisionals' (EX1006–1010) filing dates and their limitation-by-limitation § 112 support.
- Practical value is now defensive, not offensive. Because the patent is Expired – Fee Related (adjusted expiration 2023-01-29), the § 103 analysis is worth running to (a) defeat pre-expiration damages in any residual or renewed assertion, (b) support an IPR if a defendant was served within the last year, and (c) frame a § 285 exceptional-case or Rule 11 posture. It cannot support injunctive relief for the patent owner, and it does not revive a live royalty base.
This is a technical invalidity analysis, not a legal opinion. A filing-grade § 103 position requires the granted claims, the file history (EX1002), and the Saber declaration (EX1003), none of which I could fully retrieve in this session.
Generated 9/15/2026, 4:48:14 AM
Extensions
Patent term adjustments, term extensions, continuations, divisionals, family members, and expiration dates.
Derivative works
Defensive disclosure: derivative variations of each claim designed to render future incremental improvements obvious or non-novel.
Keep exploring
More patents asserted by Flexiworld Technologies, Inc.
- US 10162596Summary — U.S. Patent No. 10,162,596 (US10162596B2) Bibliographic data (verified against USPTO-derived sources: uspto.report and Google Patents) | Field | Value | |---|---| | Patent number | 10,162,596 (B2) | | Title | Portable electronic…
- US 9836259Based on the authoritative patent text you supplied plus live searches of USPTO records (uspto.report, Google Patents, Justia, Unified Patents, Flexiworld's own portfolio page), here is the requested summary. US Patent 9,836,259…
- US 11096056
- US 9798516
- US 9042811Summary of U.S. Patent No. 9,042,811 (US9042811B2) Bibliographic Data | Field | Value | |---|---| | Title | Specification of Smart Wireless Television for Rendering Digital Content | | Assignee (at grant) | Flexiworld Technologies, Inc…
- US 10768871The initial searches returned no results. Let me try broader queries. I have the core patent details. Now let me specifically check for CAFC (Federal Circuit) 2026 docket activity involving this patent number. US Patent 10,768,871…
- US 11029903I'll search for US patent 11029903 in the USPTO database and check for any CAFC 2026 docket activity involving this patent number. The initial searches returned no results. Let me try alternative queries. I have solid USPTO/Google Patents…
- US 9965233I'll search for the specific patent number and any CAFC 2026 docket activity. Let me get more detail on the claims and check for any CAFC activity specific to this patent. Based on my searches (Google Patents, USPTO/PTAB records via…
Other patents in Software Technology & Computing Systems (T)
- US 8073911I'll search for litigation and docket information on this specific patent, then compile the summary. Let me check for CAFC 2026 activity and the district court litigation. US Patent 8,073,911 — Summary Note on scope of this report: All…
- US 9110622I'll search for the authoritative details on this specific patent, including any 2026 CAFC activity. Let me check for any 2026 CAFC docket activity involving this patent. Summary of US Patent 9,110,622 B2 Identification & bibliographic…
- US 8332521I'll search for authoritative information on this patent number. US 8332521 — Concise Summary Search coverage / caveats up front: My searches did not return a CAFC (Federal Circuit) 2026 docket entry for patent 8332521. What I did find is…
- US 9069510I'll verify against live sources before summarizing. US Patent 9,069,510 B2 — Analyst Summary Verification status: Core bibliographic data below is grounded in the authoritative full text fetched from Google Patents…
- US RE42725I'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…
- US 10346114I'll search for authoritative information on this patent, including any CAFC 2026 docket activity. Let me search for the litigation/docket details and the actual claim text. US Patent 10,346,114 B2 — Analyst Summary Sourcing note: I worked…
- US 7240100I'll run several targeted searches for this specific patent number and for any 2026 CAFC activity. Let me check for reexamination history, litigation, and any 2026 Federal Circuit activity. Search summary — scope and what I actually found…
- US 8850571I'll search for this specific patent number and its current litigation status. Let me run additional targeted searches. Let me search specifically for the claims of this patent. Search Report: US 8,850,571 B2 Scope note on the searches. I…
This patent in court (2)
2 tracked lawsuits name US 7944577.