US 8332521

I'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 district-court litigation data on the Google Patents record (which cannot be confirmed as CAFC activity). I also could not retrieve the verbatim claim text — the authoritative full text supplied for this patent cuts off mid-sentence in the written description (at the GUI discussion of screen 820), before the claims section. I therefore cannot give you a reliable plain-language reading of each independent claim, and I am not going to reconstruct claim language from the specification and present it as if it were the claims. Treat any claim characterization below as unverified.

Bibliographic data (high confidence)

Title (literal, as listed): "Internet-pad specification, the internet-pad specification may include a touch sensitive screen, a digital camera, a document application, an e-mail application, icons over the touch sensitive screen for user selection, a wireless communication unit for wireless connectivity, a digital content application for playing digital content, and an operating system supporting application programming interface (API)"

Sources: Google Patents US8332521B2; SumoBrain record

Abstract

The fetched record does not include a verbatim abstract field, so I will not present a fabricated one. The closest authoritative framing in the document's own "Definitions" section is:

"Present invention relates to device synchronization and digital output and, in particular, to providing pervasive output for information apparatuses."

That is the document's own summary sentence, not the abstract paragraph. If you need the actual abstract text, it should be pulled from the USPTO PatentCenter/Patent Full-Text record for 12/903,048.

Litigation signal found (district court, not CAFC)

The patent record lists three US district court cases, one of which is 2026-dated:

• Washington Western District Court, case 2:21-cv-01055
• Texas Western District Court, case 6:20-cv-00553
• Texas Eastern District Court, case 2:26-cv-00229 (2026 filing)

Uncertainty flag: I found no Federal Circuit docket for 2026 tied to 8332521. An adverse district-court judgment out of E.D. Tex. is the kind of event that would generate a 2026 CAFC appeal, but I have no authoritative confirmation that an appeal exists, so I am not asserting one.

Independent claims (plain-language overview)

Unable to provide with confidence. The authoritative text I have ends before the claims, and my searches did not surface the claim set. Based only on the specification's described process (explicitly not a claim reading), the claimed subject matter of this family generally concerns:

• an information apparatus (the "internet-pad" of the title) with a touch-sensitive screen, icons for user selection, and an operating system supporting APIs;
• a wireless communication unit for wireless connectivity to an output device;
• discovery of available output devices, service negotiation, and synchronization in which device-dependent components (e.g., a printer driver) are uploaded from the output device's output controller (120) to the information apparatus;
• conversion of digital content into print/output data and wireless transmission to the output device for output.

Do not rely on that paragraph as a claim construction. To give you a literal claim-by-claim (or independent-claim) breakdown, I would need the granted claim text from PatentCenter for application 12/903,048 or the full-text claims on patents.google.com/patent/US8332521/en.

Search hygiene note

Several search hits mixed in unrelated numbers (e.g., US6421748, US6199099, US5619649, US7370090, US9069510, US9037088). I am not attributing any of those to this patent; only 8332521 / 12,903,048 bibliographic data is reported above.

I'll research litigation involving US Patent 8,332,521. Let me run several searches.

Let me dig deeper into the specific cases and the newest filings.

Let me investigate the Roku IPR, the LG case, and outcomes.

Litigation Involving U.S. Patent No. 8,332,521 ("the '521 Patent")

Scope note: Per the strict rule, I treated "8332521" literally and matched only U.S. Patent No. 8,332,521 (Internet-Pad Specification; issued Dec. 11, 2012; assignee Flexiworld Technologies, Inc.; priority date Nov. 1, 2000). I did not fold in results for related but distinct numbers in the same family (e.g., 8,989,064; 9,110,622; 10,133,527). I exhausted my search budget, so a few items below are flagged as uncertain rather than confirmed.

Confirmed district court cases asserting the '521 Patent

These three cases correspond exactly to the three litigation links listed on the patent's own Google Patents page (W.D. Wash. 2:21-cv-01055; W.D. Tex. 6:20-cv-00553; E.D. Tex. 2:26-cv-00229), which corroborates the list above.

Related proceedings — NOT confirmed to involve the '521 Patent

These are part of the same Flexiworld enforcement campaign and are worth tracking, but I could not verify that the '521 Patent itself was asserted/challenged. Do not treat them as '521 litigation without checking the pleadings:

• Roku, Inc. v. Flexiworld Technologies, Inc., PTAB IPR2021-00715. A post-grant (IPR) challenge by Roku. I found an exhibit from this IPR that reproduces the W.D. Tex. Amazon docket sheet, which ties the proceedings together, but I did not verify which Flexiworld patent(s) the IPR challenged — it may have targeted a different family member.
• Flexiworld Technologies, Inc. v. Roku Inc. (W.D. Wash.). This was a standing/ownership dispute over the Samsung assignment agreement. The court held the '064 and '066 patents were not assigned to Samsung. Those are different patent numbers than the '521.
• Flexiworld Technologies, Inc. v. LG Electronics, Inc. / LG Electronics U.S.A., Inc. (E.D. Tex., filed ~Sept. 2025; six patents re wireless connectivity/streaming; accused LG smart TVs, soundbars, remotes, ThinQ app). Whether the '521 is among the six asserted patents is unverified.

Key caveats

1. Patent term status vs. the 2026 suit. The Google Patents record for US 8,332,521 lists its legal status as "Expired – Fee Related," with an adjusted expiration of 2022-03-08. That is in tension with a 2026 complaint asserting the '521, so either the status label refers to a particular expiration/reinstatement event or the 2026 assertion rests on a different family member. I flag this as unresolved.
2. I did not confirm a final merits outcome in either Amazon case. Both terminated (Aug. 2021 for the Texas filing; July 2025 for the Washington filing) without a confirmed judgment, verdict, or settlement figure in the sources I retrieved.
3. Sources used: Google Patents (patents.google.com/patent/US8332521/en), Unified Patents litigation portal case pages, Docket Alarm, CourtListener (claim construction order, Dkt. 161, 2:21-cv-01055-DGE), Dockets.Justia (2:2026cv00229 docket), and law-street-media/ExParte complaint analyses. PACER/CAFC records were not directly queried before my search budget was exhausted.

If you need the definitive outcome of the two Amazon cases or confirmation of whether the '521 was in the Roku IPR / LG suit, those require a direct PACER/PTAB (PTAB E2E) pull or the Unified Patents case pages for the specific case numbers above.

I'll start by verifying the canonical "no PTAB proceedings" signal against live sources and checking for any older or recently-filed AIA trials involving this patent and its owner.

The initial hits are all for other Flexiworld patents (9,836,257; 9,965,233) — not 8332521. Let me search specifically for this patent number and check the litigation defendants.

Let me check the district-court assertions tied to this patent and whether any defendant petitioned on '521 specifically.

Proceedings overview

US 8,332,521 has never been the subject of an AIA trial. The canonical USPTO Open Data Portal block in this prompt reports zero AIA proceedings for this patent, and my independent web searches for the patent number, its owner, and its litigation defendants surfaced no IPR, PGR, or CBM naming the '521 patent — meaning every claim (including asserted claims 7, 12, and 15) is PTAB-untested, the patent is not narrowed by any claim-cancellation, and a defendant gets no free invalidity judgment from the Board; the defensive upside is limited to (a) the patent's expired status, (b) a § 112 indefiniteness fight Amazon has already opened on claim 15, and (c) the family-wide conception-date win Flexiworld obtained in a sibling patent's IPR, which constrains what art any new petitioner can reach.

Coverage caveat (read this before relying on the zero): the ODP block is the canonical source and states "no AIA trial proceedings … as of the most recent ingest." My supporting searches were cut short by a tool-step limit, so I could not run every defendant-specific query I would want (e.g., a dedicated "Amazon IPR Flexiworld '521" sweep). The zero is well-supported but not exhaustively re-verified by me. Re-check PTAB E2E by patent number before you file anything that depends on it.

No AIA proceeding on US 8,332,521

There is nothing to report at the proceeding level. I will not manufacture a docket. The three district-court matters attached to this patent's record — W.D. Tex. 6:20-cv-00553 (Flexiworld v. Amazon), W.D. Wash. 2:21-cv-01055 (Flexiworld v. Amazon, the venue where claim construction actually happened), and E.D. Tex. 2:26-cv-00229 (Flexiworld v. TCL Electronics Holdings Ltd., asserting claims 7 and 12) — generated no PTAB counterpart.

Context — PTAB activity on sibling Flexiworld patents (these are NOT US 8,332,521)

Included because it is the only real PTAB intelligence on this patent family, and the conception-date holding is transferable leverage. Do not cite these FWDs as adjudications of '521.

IPR2022-00775 — Unified Patents, LLC v. Flexiworld Technologies, Inc. (not '521 — U.S. 9,836,257)

• Type: Inter Partes Review
• Filed: 2022-04-08
• Status: Final Written Decision — patent owner prevailed. "Final Written Decision Determining No Challenged Claims Unpatentable; Dismissing Patent Owner's Revised Motion to Amend," Paper 41, 2023-11-01. Institution granted 2022-11-08 on all challenged claims.
• Judge panel: APJs Terrence W. McMillin, Christopher L. Ogden, Brent M. Dougal (Ogden presided at the 2023-08-29 oral hearing).
• Petition grounds: claims 27 and 28 (28 dependent on 27) under pre-AIA § 103(a) — Ground 1: Olgaard (US 7,849,198) in view of Moghadam (US 5,917,542); Ground 2: Acharya (US 2002/0080091) in view of Griffiths (US 7,136,999). The fight collapsed into whether Olgaard (2000-10-24) and Acharya (2000-12-22) were § 102(e) prior art.
• Institution decision: instituted on all challenged claims 2022-11-08; the panel rejected Patent Owner's § 314(a) argument that Unified (a non-practicing defensive aggregator) should be denied — petitioner's lack of product practice is "irrelevant to Congress' statutory scheme for who may be a petitioner."
• Final Written Decision: No challenged claims unpatentable. Flexiworld swore behind both references, proving a conception date of at least 2000-10-22 — ahead of Olgaard. The panel credited inventor testimony plus provisional-draft file metadata as adequate corroboration under the rule of reason (Fleming v. Escort), holding metadata was "the most reliable indicator of the latest date each draft was completed" and rejecting Unified's argument that metadata originating with the inventor cannot corroborate. Flexiworld's contingent motion to amend was dismissed.
• Settlement / termination: none; decided on the merits.
• Appeal: unknown / not found. I did not locate a Federal Circuit docket for the '257 FWD. Do not assume one exists.
• Defensive value: The losing party here was Unified, so the precedent runs against defendants in this family on priority: Flexiworld has already established, through an adjudicated record, a conception date at or before 2000-10-22 with corroborating metadata. Any '521 petition leaning on art dated after 2000-10-22 faces the same sworn-behind attack. Also note Unified's estoppel: as a petitioner in IPR2022-00775, Unified (and privies) is barred under § 315(e)(2) from re-running Olgaard/Moghadam and Acharya/Griffiths on '521 — but that estoppel does not bind any other defendant.

IPR2022-01267 — Roku, Inc. v. Flexiworld Technologies, Inc. (not '521 — U.S. 9,836,257)

• Type: Inter Partes Review
• Filed: 2022-07-29
• Status: unknown to me — docket exists; I did not confirm institution, FWD, or termination. Treat as unresolved.
• Judge panel: reportedly Dougal, Ogden, McMillin.
• Petition grounds / institution / FWD / settlement / appeal: not retrieved. Do not cite.
• Defensive value: Roku was a co-target of Flexiworld's '257/'233 assertions (Flexiworld v. Roku, W.D. Tex. 6:21-cv-00680-ADA). Its filing shows defendants in this family do go to the Board — '521 simply never attracted one, largely because by 2020-2022 it was already near/past expiry.

IPR2022-01114 — Roku, Inc. v. Flexiworld Technologies, Inc. (not '521 — U.S. 9,965,233)

• Type: Inter Partes Review
• Filed: 2022 (Patent Owner's Mandatory Notices dated 2022-07-18)
• Status, panel, grounds, institution, FWD, settlement, appeal: not retrieved. Filed on the '233 patent, a different family member.
• Defensive value: context only.

Lexmark International, Inc. v. Flexiworld Technologies, Inc. (not '521 — U.S. 9,965,233)

• A Lexmark petition challenging the '233 patent exists in the record (Ground 1: claims 1, 2, 4, 5, 7, 9, 11-13, 17-21, 27, 29, 30, 35, 36, 47, 48, 50, 52, 57, 61 over Keeney (US 6,748,471); Ground 2: claims 47, 48, 61 over Keeney + Vatland (US 6,091,507); accuses a "rehash" of wireless printing and image encoding).
• Proceeding number and disposition: NOT CONFIRMED. I saw the petition document but not its assigned IPR number or institution outcome. Do not cite a number.
• Defensive value: shows a major OEM (Lexmark) litigated against this portfolio (E.D. Ky. 5:22-cv-00…) — again without touching '521.

Strategic summary

Claim status on US 8,332,521. Nothing is canceled, nothing is sustained, nothing is tested. Every claim of '521 — including asserted claims 7, 12, and 15 — remains in force for pre-expiration damages. The only meaningful adverse claim-level development in the record is judicial, not administrative: in W.D. Wash. 2:21-cv-01055, Amazon argued claim 15 is indefinite under § 112 for failing to disclose sufficient structure for the eight claimed functions of the "output manager software," and the court issued a claim construction opinion addressing "output manager software" (CourtListener, Flexiworld Technologies Inc v. Amazon.com Inc, W.D. Wash., docket 2:21-cv-01055 — see the construction order at courtlistener.com/recap/gov.uscourts.wawd.302246). I have not confirmed how the court resolved the indefiniteness theory or whether claim 15 survived intact. Do not represent that claim 15 was held indefinite — verify the order. That ambiguity is your single best lead.

Estoppel landscape. There is no § 315(e)(2) estoppel on US 8,332,521 — zero proceedings means zero petitioner estoppel on this patent's grounds. Conversely, a defendant today is not estopped from anything, and the full prior-art universe remains available. Estoppel does attach to Unified Patents (and its privies) from IPR2022-00775, but only as to the '257 patent's Olgaard/Moghadam and Acharya/Griffiths grounds — it does not travel to '521 as a matter of statutory estoppel, though the FWD's factual findings are freely citable against Flexiworld as admissions in any '521 proceeding.

The dominant constraint is the priority date, not the art. Flexiworld has an adjudicated, corroborated conception date of at least 2000-10-22 for the family (IPR2022-00775, Paper 41), and '521 lists a 2000-11-01 priority date. Pre-AIA § 102(e)/§ 103(a) governs. Practically, that kills most of the obvious late-1990s/2000-2001 art pool — including Olgaard (2000-10-24), which Unified spent a full trial trying to make stick and lost. Any '521 petition must lead with art filed/issued before ~2000-10-22, or it will be answered with a sworn-behind declaration and dated provisional-draft metadata.

Timing and remedy realities. Per the patent record, '521 is "Expired – Fee Related," adjusted expiration 2022-03-08, yet Flexiworld asserted it in E.D. Tex. 2:26-cv-00229 (Flexiworld v. TCL Electronics Holdings Ltd.) on claims 7 and 12. That is a past-damages campaign under the six-year § 286 lookback, not an injunction play. Two consequences:

1. PGR is unavailable (patent issued 2012-12-11, far outside the 9-month window) and CBM is gone (transitional program sunset 2020-09-16, and '521's claims are not financial-services claims). IPR is your only AIA vehicle.
2. The economics are upside-down for IPR. On an expired patent the patent owner cannot amend, which helps — but you are spending six figures of PTAB fees to knock out a patent whose only remaining value is a damages tail. Litigation-stage invalidity (§ 101/§ 112) and prior-damages defenses are usually cheaper.

Pattern signals. Flexiworld (NPE; founder William Ho Chang; 77+ US patents) is a serial, multi-defendant enforcer across many family members — Amazon (10 patents incl. '521), Roku, Lexmark, Xerox, TCL. Defensive aggregators are in the fight: Unified Patents filed IPR2022-00775 against the family, and Roku filed two of its own (IPR2022-01114, IPR2022-01267). So far the only family FWD I can confirm went Flexiworld's way. Flexiworld's PTAB counsel of record is Nelson Bumgardner Conroy P.C. (Fort Worth). One unverified data point from a petition exhibit suggests Flexiworld ownership ties to Apex Swiss Holdings SARL and Ninerstar Corporation — I could not confirm this attribution and you should not rely on it.

Recommended next steps

1. Do not build a defense on a PTAB win that does not exist. There is no FWD to link. The absence is the answer, and it is itself diagnostic: this family drew four-plus petitions on its 2009-2018 continuations (Unified, Roku ×2, Lexmark) but zero on '521 — consistent with '521 having expired (2022-03-08) just as the enforcement wave peaked. A 2026 defendant facing TCL-style claims 7/12 assertion is being sued on a dead patent for past damages.

2. Verify and weaponize the W.D. Wash. claim construction. Pull the full order at docket 2:21-cv-01055 (CourtListener recap gov.uscourts.wawd.302246). If the court construed "output manager software" narrowly or sustained any § 112 indefiniteness on claim 15, test whether claims 7 and 12 share that limitation — if so, you may have a collateral-estoppel-flavored non-infringement/invalidity argument that costs nothing at the Board.

3. Check the § 315(b) clock immediately. For E.D. Tex. 2:26-cv-00229, the one-year bar runs from service of the complaint on your client (or a privy/RPI). If you are inside the window and decide to petition, the statutory 1-year trial deadline from institution (§ 316(a)(11)) plus the ~6-month institution deadline means a petition filed now would resolve in roughly 2027 — after the district case may already be tried. Weigh that against a stay motion.

4. If you do petition, lead with pre-2000-10-22 art. Anything later invites the IPR2022-00775 sworn-behind/metadata play, which Flexiworld has already won once. Also consider the Keeney (US 6,748,471) and Vatland (US 6,091,507) combinations Lexmark deployed against the sibling '233 patent — but confirm their filing/priority dates beat 2000-10-22 before investing.

5. Run the two searches I could not finish before relying on this memo: (a) PTAB E2E by patent number for US 8,332,521 and by application 12/903,048; (b) a petitioner-by-name sweep for Amazon, TCL, Roku, and Lexmark against the '521 patent. My conclusion (zero proceedings) rests on the canonical ODP block plus incomplete web confirmation — the ODP "most recent ingest" caveat and my truncated search coverage are the two live risks in this analysis.

I'll research the assignment chain for US 8332521 from multiple angles.

Key litigation finding confirmed. Now let me pin down the assignment records and reel/frame numbers.

Assignment Reconstruction — US 8,332,521 B2 ("Internet-pad specification…")

Research limitation stated up front (important): I could not retrieve the assignment cover-sheet detail for this patent — no reel/frame number, no execution date, and no correspondent of record (the recording attorney/firm). The USPTO Assignment Center (https://assignmentcenter.uspto.gov/) and the legacy Patent Assignment Search (https://assignment.uspto.gov/patent/index.html) were not directly queryable in this research pass. Everything below that is labeled as a reel/frame is quoted from third-party court filings about sibling patents in this family, not from the Assignment Center itself. I am not filling in the missing reel/frame for the '521 assignment, because I do not have it. Where I say "not retrieved," that is a gap, not a negative finding.

Inventors

Patterns to note:

• No inventor-departure pattern. Both inventors remained the named inventors on Flexiworld continuations filed 2012, 2015, 2016, 2017 and 2021 (e.g., US 2011/0165632, appl. 17/171,687; US 10,816,798 family, appl. 16/200,380). There is no evidence either inventor left the assignee within 12 months — the opposite is true: they stayed attached to the portfolio for two decades. This argues against a near-term fire-sale reading of the inventor assignment.
• Timing anomaly worth flagging: the patent's listed priority date is 2000-11-01, but Flexiworld Technologies is reported to have been founded in 2001 in Portland, Oregon. That chronology suggests the earliest priority filing may have been made by Chang and Liu personally before the corporate entity existed, with rights later papered into Flexiworld. I could not confirm this from a recorded document.

Original assignee

Flexiworld Technologies, Inc. — named on the face of the '521 patent. Address of record on the '521 grant is Vancouver, WA; other family records list Portland, OR (e.g., US 7,945,577 lists "Flexiworld Technologies, Inc., Portland, OR"). This is a same-entity address variance, not a transfer.

• Primary line of business (as represented): Flexiworld publicly describes itself as a pioneer/provider of pervasive wireless technology — short-range wireless (Bluetooth, Wi-Fi, IrDA) applications and embedded solutions for the mobile device market, founded by William Ho Chang.
• Did it ship a product embodying the claims? No verifiable evidence found. The company's own site (flexiworld.com) is organized as a "Patents Portfolio" index — a page per patent, with the title, issue date, inventors, and a "Sample Claim." That is a licensing/assertion artifact, not a product catalog. I found no product manual, SKU, retail listing, or shipment record for an "internet-pad" device embodying the '521 claims. Flag as unresolved rather than proven — absence of search evidence is not proof of absence.
• Current status: The entity is still in existence and actively litigating. It is the named plaintiff in Flexiworld Technologies, Inc. v. TCL Electronics Holdings Ltd., E.D. Tex. 2:26-cv-00229 (filed 2026-03-20, Judge Rodney Gilstrap). I found no bankruptcy filing, dissolution, or acquisition of Flexiworld.

Assignment timeline

Bottom line: this patent has essentially a one-link chain of title — inventors → Flexiworld — and I found no recorded post-issuance transfer to any third party.

• Execution date: not retrieved / recorded 2011-04-25 — Reel/Frame not retrieved

  • Conveyance: Assignment (Google Patents legal-events entry: "ASSIGNMENT OF ASSIGNORS INTEREST (SEE DOCUMENT FOR DETAILS)")
  • Assignor: CHANG, WILLIAM HO; LIU, CHRISTINA YING
  • Assignee: FLEXIWORLD TECHNOLOGIES, INC.
  • Correspondent: not retrieved. I am deliberately not naming litigation counsel here as a substitute — plaintiff's counsel (Grochocinski/Ginnings/Glennon) is not the same thing as the assignment correspondent of record, and conflating them would be a fabricated finding.
  • Context: Formation-stage in-house assignment — inventors assigning their own priority-family rights into their own company. Not a fire-sale, not securitization, not a transfer-to-asserter.
  • Recurrence note: In this family, the inventor→Flexiworld pattern is recorded many times over, and the family's recorded reel/frames cited in court filings include 028733/0064 ('402), 039816/0200 ('596), 042385/0202 ('072, '178, '031), 043675/0454 ('856), and 046519/0534 ('871). These are sibling patents, not the '521 patent, and none of them is the '521 reel/frame. I cite them only to show that the family's chain is a repeated inventors→Flexiworld link with no downstream LLC layer.

• No later assignment found. Google Patents lists "Current Assignee: Flexiworld Technologies Inc" with no intervening assignment event between the 2011-04-25 recording and the 2026 assertion. The only other legal-status event of consequence is the 2022-03-08 "Adjusted expiration" / "Expired – Fee Related" entry.

Contradiction to flag (carried over from the prior section): the record says the patent expired 2022-03-08 (fee-related), yet Flexiworld asserted it against TCL on 2026-03-20. These can coexist — a patent owner may still sue for pre-expiration infringement within the § 286 six-year lookback (roughly 2020-03-20 → 2022-03-08 here) — but the docket and the expiration status are in apparent tension and should be reconciled by pulling the maintenance-fee record in Patent Center and the fee-reinstatement history. Treat the expiration status as unverified.

Update to the prior section: the earlier summary could not give a claim reading. Third-party docket analysis of the TCL case indicates claims 7 and 12 of the '521 patent are asserted (characterized as covering a tablet-like internet-pad with touch screen, wireless connectivity, and digital-content applications, plus wireless device discovery at col. 46:48–47:3 of a related patent). This is docket-analysis text, not the grant, so treat it as indicative, not authoritative.

Timeline diagram

timeline
    title Ownership of US 8332521
    2000 : Priority application filed
    2010 : Application 12 903 048 filed
    2011 : Assignment recorded to Flexiworld
    2012 : Patent US 8332521 issues
    2022 : Recorded expiration date
    2026 : Suit filed v TCL in E D Texas

NPE / troll-pattern signals

1. Shell-entity transfer — NOT PRESENT.
There is no recorded transfer out of the original assignee at all. The chain never reaches an "IP Holdings / Licensing / Ventures" LLC. Flexiworld Technologies, Inc. is the original and the current recorded owner and the named plaintiff in 2:26-cv-00229. This is an important negative: the classic purchased-portfolio NPE structure (patent bought into a fresh LLC prosecuted by a repeat attorney) is absent here.

2. Known asserter in the chain — PRESENT (strongest signal).
The assignee is itself a serial patent plaintiff, not a shell downstream of one:

• Google Patents attaches "Family has litigation" to this record with cases 6:20-cv-00553 (W.D. Tex.), 2:21-cv-01055 (W.D. Wash.), and 2:26-cv-00229 (E.D. Tex.).
• Flexiworld is described flatly as a "non-practicing entity (NPE)" and a "patent-licensing company" in Actionable Intelligence (action-intell.com) coverage of Flexiworld v. Lexmark and Flexiworld v. Brother.
• An IPR petition filed against Flexiworld's US 7,609,402 (PTAB, PTACTS) enumerates the Patent Owner's assertion campaign: Epson (C.D. Cal. 8:21-cv-00807, filed 2021-04-29), Brother (W.D. Tenn. 2:22-cv-02237, filed 2022-04-15), Lexmark (E.D. Ky. 5:22-cv-00098, filed 2022-04-15), Hisense (E.D. Tex. 2:22-cv-00227, filed 2022-06-24), and more.
• Additional campaign: Canon (W.D. Tex., filed 2021-02-11), Sony (noticed 2021-10-14), Xerox (W.D.N.Y. 6:23-cv-06370 and 6:23-cv-06372), and Amazon over Echo devices (2020-06).
  This is a broad, multi-year, multi-defendant consumer-electronics/printing enforcement program run by the assignee itself.

3. Repeat correspondent across the chain — UNCLEAR at the recording level; PRESENT at the litigation level.
I have no assignment-correspondent data for this patent, so I cannot make the finding the task specifically asks for (same recording attorney across multiple links). What I can document is repeat plaintiff-side counsel across the campaign: Timothy E. Grochocinski and Charles Austin Ginnings, with Nelson Bumgardner Conroy PC, appear for Flexiworld in the Epson (2021), Brother (2022), and TCL (2026) actions, alongside Peter John Glennon / The Glennon Law Firm, PC in the Xerox matters. That is a repeat-player enforcement firm, but it is not evidence about who recorded the 2011 assignment. Do not read it as such.

4. Cascading transfers — NOT PRESENT. One link, 2011, and nothing after.

5. Pre-litigation transfer — NOT PRESENT. The only assignment is dated ~2010/recorded 2011; the earliest Flexiworld enforcement activity I found is 2020. There is no transfer inside the 6-month window before suit — because there is no transfer at all.

6. Bankruptcy fire-sale — NOT PRESENT. No Chapter 7/11 event found for Flexiworld.

7. Privateering — NOT PRESENT / weak. Flexiworld is a founder-owned entity suing on its own patents; there is no operating-company parent transferring patents to it. The mild variant worth noting: a founder who left a large operating R&D organization (Sharp) formed the entity and later enforced against downstream manufacturers — but there is no evidence Sharp is the beneficial party.

8. Defensive aggregator — NOT PRESENT. The chain does not terminate at RPX, AST, LOT, Unified Patents, or OIN. If anything, Flexiworld is on the receiving end of Unified Patents' litigation tracking and of a third-party IPR petition.

Verdict

NPE — high confidence.

The chain of title terminates at Flexiworld Technologies, Inc. — the original assignee named on the '521 grant and the current recorded assignee (inventor assignment recorded 2011-04-25; no post-issuance transfer found) — and that same entity is the plaintiff asserting the '521 patent against TCL in E.D. Tex. 2:26-cv-00229, filed 2026-03-20. That is one strong, well-documented signal (a proven serial asserter, identified as an NPE by independent litigation press and enumerated as "Patent Owner" in a third-party IPR petition covering at least five prior suits), reinforced by the absence of any product embodying the claims and by a public web presence structured as a patent portfolio with "sample claims." Importantly, this is not the LLC-shell pattern: there is no cascading transfer, no pre-suit assignment, no bankruptcy sale, and I could not obtain the correspondent of record, so the "same lawyer behind unrelated LLC names" tell is untested here — do not treat it as confirmed.

Primary-source links for verification:

• USPTO Assignment Center: https://assignmentcenter.uspto.gov/
• Legacy Patent Assignment Search: https://assignment.uspto.gov/patent/index.html
• Google Patents legal events for this record: https://patents.google.com/patent/US8332521/en
• TCL docket: https://dockets.justia.com/docket/texas/txedce/2:2026cv00229/[244557](/patent/244557)

Next diligence step (the gap that matters): query patent number 8,332,521 and application 12/903,048 in Assignment Center to pull (a) the reel/frame, (b) the execution date, and — the item this task prioritizes — the correspondent of record on the 2011-04-25 recording, then check whether that correspondent recurs on the ~30 sibling Flexiworld continuations. That single data point is what would either upgrade or knock down signal 3.

I'll search for the patent record and its cited prior-art references.

Prior-art analysis for US 8,332,521 — scope and limitations first

Tool limit reached. I exhausted my search budget before I could pull the patent's complete front-page citation list from USPTO PatentCenter or the Google Patents "Citations" panel (the authoritative fetch I was given truncates in the written description at screen 820 and never reaches the claims or the references). I will report only what I actually observed, mark what is missing, and — per your strict rule — not reconstruct claim language or reference lists from memory.

Two constraints that shape everything below:

1. I still do not have the granted claim text for application 12/903,048. A § 102 anticipation mapping is a claim-limitation-by-claim-limitation exercise. Without literal claim language I cannot honestly say "Reference X anticipates claim Y." I can only grade references against the features the specification describes, and label that as structural relevance, not an anticipation finding. This is consistent with the caveat already flagged in the earlier "Patent summary" section — no contradiction, the gap persists.
2. A patent's own "References Cited" are not the same thing as an examiner's § 102 rejection. Front-page references are frequently cited under § 103 (obviousness) or as background art. Nothing I found indicates which of these references, if any, was applied in a § 102 rejection, and I have no office-action record for 12/903,048.

What I could verify: US patent references cited on the face of US 8,332,521

Source: the SumoBrain mirror of the patent's front page, "Domestic Patent References" section — sumobrain.com/patents/us/Internet-pad-specification-internet-may/8332521.html. Titles below are quoted as listed (I have not independently re-verified each against USPTO records).

Gaps I must disclose. The retrieved snippet skipped the block between US 5,748,859 and US 6,167,514, so there are almost certainly additional 1998–2000 US references I did not see. I also could not retrieve the Foreign Patent Documents section or the Other References / Non-Patent Literature section for 8,332,521. Those sections are where the most dangerous art often sits (Bluetooth/Salutation/Jini/Service Location Protocol specifications, for example — the '521 specification itself names Bluetooth, HAVi, Jini, Salutation, SLP and UPnP as discovery protocols, which invites NPL citations).

Contamination warning. Search results also surfaced reference lists belonging to other Flexiworld patents — notably US 8,595,717 and US 8,533,352 (freepatentsonline.com/8595717.html, freepatentsonline.com/8533352.html). Those lists contain Chang-family members (e.g., US 7,949,577; US 7,603,402; US 7,318,086; US 8,285,802) and third-party items (US 7,370,090 Nakaoka; US 7,353,416 Jeansonne; US 2008/0126628 Mullis; US 2009/0198839 Banerjee). I am not attributing any of those to US 8,332,521, consistent with the search-hygiene note already recorded in the earlier summary.

Most relevant prior art — ranked by structural relevance to the described subject matter

Because I cannot do a limitation-by-limitation § 102 comparison, I am ranking by how closely each reference's stated subject matter maps onto the features this specification actually emphasizes. Treat this as a candidate screen for a § 102/§ 103 analysis, not a rejection.

Tier 1 — device-driver acquisition / point-and-print (the apparent core of the invention)

• US 5,228,118 (Sasaki) — selecting one of several printer drivers, from the data processor to the printer, based on the interpreters available on the printer. Directly prefigures the "the printer tells the host what it can accept" architecture.
• US 5,699,495 (Snipp) — "Point-and-print in a distributed environment." Title alone indicates the walk-up-to-a-printer-and-print paradigm the specification's airport/kiosk scenarios describe.
• US 5,412,798 (Garney) — enabling host access to a device driver residing in resource memory of a coupled resource. This is structurally the "driver lives at the device, host maps/uses it" idea.
• US 5,580,177 (Gase et al.) — printer/client network with centrally updated printer drivers. Relevant to the synchronization/upload step, though the topology is network-centric rather than peer-to-peer.
• US 5,613,123 (Tsang et al.) — configuring and executing device drivers based on configuration requirements.
• US 5,220,674 (Morgan et al.) — local area print server requesting and storing required resource data; relevant to resource/data retrieval from a server-side entity (here, the output controller analog).

Tier 2 — wireless connectivity between a portable/computing device and an output device

• US 5,490,287 (Itoh et al.) — wireless communication device and printing system using the same.
• US 5,524,185 (Na) — wireless computer system with shared printer.
• US 6,167,514 (Matsui et al.) — wireless communication method/apparatus/system (note issue date 2000-12-26; § 102(e) analysis turns on its filing date, see below).
• US 5,319,711 (Servi) — wireless device for verifying identification (maps to the specification's authentication steps 604).
• US 6,226,098 (Kulakowski et al.) — printer appliance in a wireless system for broadcasting packets of information.
• US 6,285,889 (Nykanen et al.) — information output system via mobile communication network — i.e., the mobile-terminal-to-output-service concept.

Tier 3 — output-device discovery, option negotiation, and job management

• US 5,485,634 (Weiser et al.) — dynamic selection, allocation and arbitration of control between devices within a region. This is the closest listed reference to the specification's discovery process 502 and service-negotiation process 514.
• US 5,467,434 (Hower et al.) — determining printer option availability and conflict resolution across print job selections (maps to negotiation of capabilities and user preferences).
• US 5,564,109 (Snyder et al.) — remote user interface for prioritizing and selecting among document production peripherals (maps to the GUI printer-selection screens 810–820).
• US 5,287,194 (Lobiondo) — distributed printing; US 5,619,649 (Kovnat et al.) — job-ticket-driven network printing; US 5,566,278 (Patel et al.) — object-oriented printing system.

Tier 4 — output-type and rendering generality

• US 6,263,503 (Margulis) — wireless television system (relevant to the "output device" being a display/audio device rather than a printer).
• US 5,636,211 (Newlin et al.) — universal multimedia access device.
• US 5,519,641 (Beers et al.) — configuring plural multimedia audio cards as a local area network.
• US 5,166,809 (Surbrook), US 5,337,258 (Dennis), US 5,404,433 (Hosogai), US 5,353,388 (Motoyama), US 5,270,773 (Sklut et al.), US 5,596,697 (Foster et al.), US 5,613,124 (Atkinson et al.) — rendering, cost-metric, document-processing, security and object-storage art of lower apparent relevance to the claimed architecture.

Claim mapping under 35 U.S.C. § 102 — what I can and cannot say

I cannot name specific claims. The claim numbers and text for US 8,332,521 were not in my authoritative source, and I will not infer them. Any statement of the form "US 5,699,495 anticipates claim 1" that I produced would be invented.

What I can state with confidence about the statutory analysis:

• Priority date as listed: 2000-11-01, with a filing date of 2010-10-12. If the granted claims are entitled to the 2000-11-01 date (a determination I cannot make — it depends on written-description support and whether any claim recites post-2000 subject matter such as the IEEE 802.11/BT-era framing in the title), pre-AIA § 102 governs and the § 102(b) critical date would be roughly 1999-11-01.
• On that basis, the 1992–1998 references sit in § 102(b) territory — they are printed publications more than one year before the earliest effective filing date. Those are the references most capable of a true § 102(b) anticipation challenge and the ones a validity attack would lead with.
• US 6,167,514 (2000-12-26), US 6,226,098 (2001-05-01), US 6,263,503 (2001-07-17) and US 6,285,889 (2001-09-04) issue after the listed 2000-11-01 priority date. They cannot be § 102(a)/102(b) art against claims entitled to that date. They could only matter as pre-AIA § 102(e) art if their own effective U.S. filing dates precede 2000-11-01 — I did not verify their filing dates, so I am flagging this rather than asserting either outcome. This is exactly the kind of date I would pull from PatentCenter next.

Recommended next steps to close the gaps

1. Claim text — retrieve the granted claims for 12/903,048 from PatentCenter (or the "Claims" tab at patents.google.com/patent/US8332521/en). Only then can a real § 102 element chart be built.
2. Complete citation list — the "References Cited" and "Foreign Patent Documents" sections plus any NPL, from the patent's front page.
3. Prosecution history — the file wrapper would reveal which references were actually applied and under which subsection, distinguishing § 102 from § 103 art.
4. Litigation record — the three district-court matters listed on the record (W.D. Wash. 2:21-cv-01055; W.D. Tex. 6:20-cv-00553; E.D. Tex. 2:26-cv-00229) plus any IPR/PGR filings would show which references the parties actually rely on. I have no verified confirmation of any Federal Circuit activity, and I am not asserting one — consistent with the earlier summary's uncertainty flag. Note also that the analysis date given in this task (April 26, 2026) differs from the system date for this session (September 15, 2026); the 2026 E.D. Tex. case number is reported exactly as the record states it.

Bottom line: the strongest § 102 candidates among the verified citations are the driver-acquisition/point-and-print set — US 5,228,118 (Sasaki), US 5,699,495 (Snipp), US 5,412,798 (Garney), US 5,580,177 (Gase) — reinforced on the wireless side by US 5,490,287 (Itoh) and US 5,524,185 (Na), and on the discovery/negotiation side by US 5,485,634 (Weiser). I cannot tie any of them to a numbered claim of 8,332,521 without the claim text, and I have flagged the list as incomplete.

I'll pull the prior-art references associated with this patent and, importantly, the actual claim text, since the authoritative text I was given cuts off before the claims.

I have partial claim text. Let me retrieve the full claim set and the cited prior-art references.

Let me retrieve the remainder of the claim set and the rest of the cited references.

Obviousness Analysis — US 8,332,521 B2 under 35 U.S.C. § 103

0. Two threshold flags before the analysis

Flag 1 — the "Prior Art" section was not in the material supplied to me. The authoritative text in this thread is the Google Patents full-text fetch, which (a) cuts off mid-sentence in the written description at the GUI discussion of screen 820, and (b) contains no prior-art listing (no "References Cited" / "Cited By" / "Similar Documents" block). So I could not literally "use the results from the Prior Art section of this page." To avoid a fabricated premise, I reconstructed the patent's front-page "References Cited" list from SumoBrain's record of US 8,332,521 and cross-checked it, and I separately flag which references come from that verified list versus general field knowledge (lower confidence). The reference list I obtained is truncated at US 5,748,859 — I do not have the tail of the cited list, and I have none of the "Cited By" (forward) citations.

Flag 2 — the earlier summary's "claims unavailable" conclusion is now partially superseded. I obtained claim text from three independent hosts — Justia, RPX Insight, and uspto.report — which agree with one another on the wording of the observed independent claims. Confidence: medium-high, but not verified against PatentCenter. The quoted language below should be confirmed against application 12/903,048 before being relied on in a filing.

Governing law / date. Application 12/903,048 was filed 2010-10-12, which is before the AIA first-to-file date of 2013-03-16 → pre-AIA § 103(a) applies, judged under Graham v. John Deere and the flexible KSR standard (no rigid TSM requirement; predictable combinations and "obvious to try" within a finite set of identified solutions are obvious). Priority is recorded as 2000-11-01. Watch this: sibling Flexiworld records (e.g., US-20080049253A1, US-7370090) list a 2000-10-31 priority date. That one-day discrepancy is almost certainly a records/formatting artifact, and it does not change any conclusion below, but the true critical date should be pinned down if any reference dates from late October 2000.

1. Structure of the claims (as observed)

Total claim count is not verified; claims 2–6 and 9–10 and 13–14 were not retrievable. Independent claims observed: 1, 7, 12, 15.

2. Reference set

2a. Verified as cited on the face of US 8,332,521 (SumoBrain "Domestic Patent References")

2b. General field knowledge (medium confidence; verify before use)

• Ubiquitous computing: Mark Weiser, The Computer for the 21st Century, Scientific American (Sept. 1991) — the "tabs, pads, boards" framework; the patent's own term "Pad" derives from this literature.
• Touch-screen mobile device w/ e-mail + browser: IBM Simon (1994); Apple Newton MessagePad (1993/1997); Palm III/V/Palm VII (1997–99); Windows CE Handheld PC/Pocket PC with Pocket Internet Explorer and Pocket Inbox (1996–2000); Nokia 9000/9110 Communicator (1996/1998) — e-mail and WWW browser in a wireless mobile device.
• Camera + PDA: Kodak PalmPix for Palm III/V (1999); IDEO eyemodule for Handspring Visor (1999–2000).
• Wireless links: Bluetooth 1.0 (July 1999), IEEE 802.11-1997/1999, HomeRF (1998), IrDA — all four are listed by the patent itself as the applicable wireless technologies (FIGS. 2A–2B discussion).
• Service discovery: Bluetooth SDP (1999), Jini (1999), Salutation, SLP (RFC 2165, 1997), UPnP/SSDP (1999), HAVi — again, all named by the patent itself as known discovery protocols.

The patent's extensive self-admission that these protocols, driver architectures, and output-device types are known is itself powerful § 103 evidence: the specification concedes the building blocks and asserts novelty only in their assembly.

3. Claim-by-claim obviousness mapping

Claim 1 — system

Every element is a known building block, and the combination is a mere aggregation of elements each performing its art-recognized function:

Ground 1-A: US 5,699,495 (Snipp) + US 5,485,634 (Weiser) + US 5,524,185 (Na). Snipp teaches a portable computing device that discovers and prints to networked printers via a point-and-print user interface; Weiser teaches the handheld "pad" form factor and arbitration of control among devices in a region; Na teaches replacing the wired link with a wireless computer/printer link. Result: a wireless handheld pad that discovers and outputs to a printer with a user-selected interface — claim 1's architecture.

Claim 7 — method

• Discovering output devices wirelessly → Snipp; plus the discovery protocols the patent admits are known (SDP, SSDP/UPnP, SLP, Jini).
• Selection via the touch screen → US 5,564,109 (Snyder); Snipp; US 5,287,194.
• Authentication/security over the RF link → US 5,319,711 (Servi, wireless ID verification) + Bluetooth PIN pairing/bonding (1999) + 802.11 WEP (1997) for the "secure connection" limitation.
• Output manager receives the content from the OS via the object model/API → ordinary software engineering; the specification's own FIG. 3A states that OS APIs already existed to let applications communicate with device management applications.
• Encryption/decryption/encoding/decoding/compression → US 5,166,809 (halftoning/RIP art), plus JPEG/LZW/TIFF/PDL practice conceded by the specification.
• Generating output data in a format/language/instruction suitable for the selected device → US 5,228,118 (Sasaki) (driver selected per printer's available interpreters) + US 5,220,674 (resource data served to the client).
• Sending over the secure RF link → US 5,490,287; US 5,524,185.

Ground 7-A: Snipp + Sasaki + Servi + Itoh. Ground 7-B: Snipp + Gase + Bluetooth 1.0 specification.

Claims 12, 15, 16–20 — receiving software components or data from the output device

This is the most directly met limitation in the entire patent. Morgan (US 5,220,674) discloses a print server that supplies the required resource data on request; Garney (US 5,412,798) discloses a device driver residing in the resource's own memory and memory-mapped for access by the host; Gase (US 5,586,177) discloses centrally updated printer drivers pushed to clients plus device status monitoring. That trio maps onto claim 12's "output manager software … for receiving … one or more software components or data from the selected wireless output device," claim 18 ("related to driving or sending of … the selected digital content"), and claim 19 ("identity information … status information, and output parameters").

Ground 12/15-A: Snipp + Morgan + Garney (drivers/resources obtained from the peripheral on demand) + Na or Itoh (the wireless link).

Claim 11 — wireless output controller box → sound/display/TV/projector

US 5,519,641 (Beers) teaches distributing multimedia/audio over a local network to multiple output cards; US 5,220,674 and US 5,287,194 teach a standalone print server "box" (the specification itself concedes the external "output controller box" arrangement at FIGS. 4A and 4G). Buffering, decoding, and delivering output data to a downstream sound/display engine is the conventional print-server function transposed to audio/video — a predictable substitution with no unexpected result.

4. Motivation to combine (the required articulated reasoning)

1. Same field, same problem. Snipp, Morgan, Garney, Gase and Sasaki are all in document output and all address the same recognized problem the '521 specification recites: a transient user at an unfamiliar output device lacks the correct device driver and must not be forced to install one. KSR permits motivation drawn from "the nature of the problem to be solved."
2. Predictable, finite solution set. The patent's own text lists the candidate wireless links (Bluetooth, HomeRF, IEEE 802.11, IrDA) and the candidate discovery protocols (Bluetooth, HAVi, Jini, Salutation, SLP, UPnP). Selecting among a small set of identified, predictable options for the same purpose is "obvious to try."
3. Design incentives / market forces. PDAs of the era had limited memory (the specification says so explicitly), which supplies a concrete reason to store the driver on the output device and pull it over the link rather than pre-install everything — the precise teaching of Garney and Morgan.
4. Straightforward combination of known elements performing known functions. Camera modules for PDAs, e-mail/browser clients, touch screens, and OS APIs were each commercially established by 2000; combining a PDA, a camera module, and an e-mail/browser suite yields no result beyond the sum of the parts (KSR; MPEP 2144.04).
5. Security motivation. Sklut and Servi supply the reason to add authentication and non-disclosure features to the output path — a security concern the '521 specification itself identifies as a drawback of network printing.
6. Implementation-detail limitations. "Object model or API" receipt of content, and choice of compression/encoding, are routine programming choices; per KSR and MPEP 2144.04, employing a known technique (an OS API) to improve a known system is obvious.

Rational underpinning is articulable for each ground, satisfying In re Kahn / MPEP 2143; the references are combinable because they are analogous art in the same field of endeavor (In re Keller — bodily incorporation is not required, only that the combined teachings suggest the claimed subject matter).

5. Where an obviousness case is weaker, and what would strengthen it

Weaknesses.

• I have no office-action record, forward citations, or IPR petition for the '521 patent, so I cannot say what art the examiner actually applied — some of what I mapped above may already be of record with a distinguishing argument attached.
• The tail of the cited-references list (after US 5,748,859) and all foreign references were truncated; a cited reference may be more on-point than anything I used.
• No secondary considerations evidence was located (no licensing-due-to-merits, no nexus-bearing commercial success). The Flexiworld v. Amazon litigation (W.D. Tex., 6:20-cv-00553) and the 2026 E.D. Tex. case (2:26-cv-00229) imply copying/industry-practice assertions, but I found no judgment and no CAFC appeal confirming anything — an inference of nonobviousness from litigation alone is not supportable.

What would strengthen. (a) A single reference or product that discloses the combination of camera + touch screen + e-mail/browser + OS API in one wireless handheld (a § 102-type attack that makes the § 103 combination need only supply the output-manager and wireless-output-device limitations); (b) the actual prosecution history for 12/903,048 and its parent, to identify what the examiner considered cumulative; (c) contemporaneous 1999–2000 product manuals for PalmPix, eyemodule, and Pocket PC printing support, to fix the evidentiary dates.

Bottom line. On the claim text I could retrieve and the reference set I could verify, claims 1, 7, 12, 15 and most dependents appear vulnerable under pre-AIA § 103(a), principally on Snipp + Morgan + Garney/Gase + Na/Itoh, with Sasaki and Servi/Sklut supplying the format-conformance and authentication limitations. The strongest single pillar is that the patent's own specification concedes the wireless protocols, discovery protocols, driver-installation problem, and OS/API architecture — leaving only an assembly of known elements, which KSR holds obvious. This conclusion should be re-run against the PatentCenter claim set and the complete cited-references list before it is relied on.