Invalidity dossier
US 10740066
Output devices that establish wireless connection with an information apparatus subsequent to having been wirelessly discovered by the information apparatus
Current assignee: Flexiworld Technologies, Inc.
Added 8/29/2026, 4:47:04 AM
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 verify the specific patent against live sources before summarizing.
Now let me check for any CAFC 2026 activity involving this specific patent.
Verification note
I searched for the specific number 10740066 / US 10,740,066 B2 and did not substitute any similar numbers. The authoritative source I relied on is the patent's own full text (Google Patents mirror of USPTO full-text: https://patents.google.com/patent/[US10740066B2](/patent/US10740066B2)/en), cross-checked against uspto.report (https://uspto.report/patent/grant/[10,740,066](/patent/10740066)) and the Unified Patents portal (https://portal.unifiedpatents.com/patents/patent/10740066). I do not have direct API access to USPTO PatentCenter or to CAFC dockets; see the limitations section at the end.
US 10,740,066 B2 — Bibliographic summary
| Field | Value |
|---|---|
| Patent number | US 10,740,066 B2 |
| Title | "Output devices that establish wireless connection with an information apparatus subsequent to having been wirelessly discovered by the information apparatus" |
| Application no. | 16/396,460 |
| Pre-grant publication | US 2019/0250883 A1 (published Aug. 15, 2019) |
| Filing date | April 26, 2019 |
| Issue/grant date | August 11, 2020 |
| Inventors | William Ho Chang (Vancouver, WA); Christina Ying Liu (Fremont, CA) |
| Assignee | Flexiworld Technologies, Inc. (Vancouver, WA) — original and current |
| Primary examiner | Melvin H. Pollack |
| Attorney/agent firm | Chernoff Vilhauer LLP |
| Earliest priority claimed | Nov. 1, 2000 (provisional 60/245,101); also provisional 60/262,764 filed Jan. 19, 2001 |
| Family ID | 22925285 |
| Claims | 20 total; independent claims 1, 7, and 14 |
Priority chain (verbatim from the patent's Cross-Reference section): a continuation of Ser. No. 16/229,896 (filed Dec. 21, 2018) → Ser. No. 15/201,194 (filed Jul. 1, 2016, issued as US 10,162,596) → Ser. No. 13/710,295 (filed Dec. 10, 2012, issued as US 9,383,956) → Ser. No. 12/903,048 (filed Oct. 12, 2010, issued as US 8,332,521) → Ser. No. 10/016,223 (filed Nov. 1, 2001, issued as US 7,941,541), claiming benefit of provisional 60/245,101. It is also a continuation-in-part of Ser. No. 16/200,380 (filed Nov. 26, 2018) → Ser. No. 15/332,432 (filed Oct. 24, 2016, issued as US 10,140,071) → Ser. No. 10/053,765 (filed Jan. 18, 2002, issued as US 9,836,257), claiming benefit of provisional 60/262,764.
Abstract (verbatim):
"Output devices (or output controllers connectable to an output device) that is wirelessly discoverable by an information apparatus are herein disclosed and enabled. An output device may be an audio output device, a printer, a television, a projector, or a display device. The output device may include one or more chips or chipsets that are compatible with Bluetooth or IEEE 802.11 standards. The output device is operable to: wirelessly announce its availability for the information apparatus to wirelessly discover the output device when the information apparatus is within a limited physical distance to the output device; wirelessly transmit one or more device attributes related to the output device from the output device to the information apparatus that has wirelessly discovered the output device; and wirelessly receive, from the information apparatus, output data that is in accordance, at least in part, with the one or more device attributes."
Plain-language overview of the independent claims
Note the unusual claim drafting: the claims are written from the output side (output controller / output device), not the phone side. The title notwithstanding, the claimed subject matter is the printer/display/speaker controller receiving content, not the information apparatus.
Claim 1 — a "wireless output controller" (apparatus claim).
A wireless output controller (separate from the phones/tablets it serves) with memory storing device‑dependent attributes about itself, plus radio‑frequency wireless communication hardware. It must be configured to, in order:
- Announce/advertise its availability over the air so an information apparatus within a limited physical distance can wirelessly discover it for short-range communication;
- Transmit its device-dependent attributes over an RF link to that apparatus, triggered by having been discovered;
- Receive information or a service request back from the apparatus after step 2;
- Run an authentication/security procedure in response to that request — involving detecting identification info, address info, security info, a password, a PIN, or biometric information about the user or the apparatus;
- Only after successful authentication, wirelessly receive output data from the apparatus (that receipt being predicated on having sent the attributes in step 2); and
- Provide output-management functions — storing, buffering, queuing, or spooling at least part of that output data in its own memory/storage — for outputting/rendering it.
The final "wherein" clause requires the output service be provided based on both (a) having been wirelessly discovered and (b) having implemented the authentication/security procedure. In short: advertise → be discovered → send device attributes → get a request → authenticate → receive job data → spool/buffer and render.
Claim 7 — a "wireless output device" (apparatus claim).
A wireless output device (again a separate device from the information apparatus) with embedded processor(s), memory/storage holding its device attributes, software/firmware, wireless hardware circuitry, and an output controller. Executing the firmware causes it to:
- Announce/advertise availability for wireless discovery based on the apparatus being within a limited physical distance for short-range wireless communication;
- Wirelessly transmit its stored device attributes over an RF channel to the discovering apparatus;
- Wirelessly receive output data (digital content) over that RF channel, subsequent to step 2; and
- Process at least part of that output data (decoding, conversion, scaling, or interpreting) into a form/format/instruction/language acceptable for output by the associated output device.
The RF channel must be either (a) direct short-range wireless or (b) wireless LAN communication. Unlike claim 1, claim 7 has no authentication requirement; the novelty emphasis is discovery-then-attribute-transmission-then-receive, with the device itself doing the decode/convert/scale/interpret work.
Claim 14 — a "wireless output controller" (method implemented by software/firmware).
A wireless output controller serving client devices that are distinct from it, comprising processor(s), memory/storage, software or firmware, and wireless chips/chipsets. Execution of the firmware implements a method:
- Broadcast/advertise availability so a client device can wirelessly discover it, based at least in part on short-range wireless communication;
- Establish a wireless communication link with the discovering client device;
- Transmit device information about the controller over that established link;
- Receive output data from the client device, subsequent to step 3, the output data including digital content for rendering/outputting at one or more output devices connected to the controller;
- Process/decode/interpret at least part of the received output data; and
- Deliver the processed output data to the connected output device(s) for rendering.
Again the closing "wherein" requires the service be provided subsequent to both discovery and transmission of device information.
Representative dependent claims of note: claim 4 (IEEE 802.11 or Bluetooth chips/chipsets), claim 5 (direct short-range link or WLAN), claim 6 and 11 (downloading/installing application software from a server, managed by embedded OS), claim 8 (device type ↔ content type mapping: TV/display/projector↔video, printer↔image/document, audio device↔audio), claim 3/13/17 (external controller wired to a television), and claim 12/18 (device attributes include capability, duplex, color, language, or format information).
Litigation status (as surfaced by the searches)
Family has litigation appears on the Google Patents record, with a family-level Darts-IP link (family 22925285). Concrete U.S. matters that the searches surfaced referencing this patent:
- Flexiworld Technologies, Inc. v. Roku Inc., No. 6:20-cv-00819 (W.D. Tex., Waco Div., Judge Alan D. Albright), filed Sept. 8, 2020. The complaint attached "Exhibit 3 – US Patent 10740066" and "Exhibit 6 – Roku '066 Claim Chart," alongside US 8,989,064 and US 10,346,114. (https://unicourt.com/case/pc-db5-flexiworld-technologies-inc-v-roku-inc-[668953](/patent/668953))
- Case 8:21-cv-00807 (C.D. Cal.), listed on the Google Patents litigation table (https://portal.unifiedpatents.com/litigation/California%20Central%20District%20Court/case/8%3A21-cv-00807). The Google record does not identify the defendant.
- Flexiworld Technologies, Inc. v. Sony Corporation, No. 2:23-cv-00616 (E.D. Tex.), listed in the Stanford NPE Litigation Database as involving patent 10740066 (https://npe.law.stanford.edu/patent/10740066).
- PTAB IPR2021-00713 — the Google Patents family record lists this as "filed (Final Written Decision)" with a Unified Patents PTAB link (https://portal.unifiedpatents.com/ptab/case/IPR2021-00713). Caveat: the Google entry is attached at the family level, so I cannot confirm from these results alone that US 10,740,066 itself was the challenged patent rather than another family member.
CAFC 2026 docket check — no results
My searches for Federal Circuit activity involving this patent (e.g., "Flexiworld Technologies Federal Circuit 2026 appeal 10740066") returned no results. I found no CAFC 2026 docket entry, appeal number, or opinion for US 10,740,066. I am not asserting that none exists — only that I could not find authoritative evidence of one, and I do not have direct docket-database access.
Legal status and term — a genuine data conflict to flag
Sources disagree on important dates, and I am not auto-correcting any of them:
- Google Patents lists "2021-11-01 Anticipated expiration" and status "Expired – Fee Related." A 2021 expiration is internally consistent with a 20-year term running from the Nov. 1, 2001 filing of parent application 10/016,223.
- Unified Patents lists "Expiration Date: 2021-10-31" and "Lifetime Renewal Fees: $0," i.e., essentially the same conclusion, one day earlier (consistent with their 2000-10-31 priority entry).
- patents-review.com lists "Adjusted expiration: 2039-04-26" — a naive 20-years-from-this-application's-filing-date calculation, which would be incorrect for a continuation.
- Unified Patents also lists Application Date 2019-04-25 and Grant Date 2020-08-10, whereas Google Patents and uspto.report both say filed April 26, 2019 and granted August 11, 2020. These are one-day discrepancies I cannot resolve from the available sources.
- Unified Patents lists Priority Date 2000-10-31; Google Patents and the patent's own front matter say 2000-11-01.
For any term calculation, I would defer to USPTO PatentCenter/PAIR and the official maintenance-fee record rather than any of these aggregators.
Where I lack authoritative information
- I did not query USPTO PatentCenter or PAIR directly; Google Patents' full-text rendering is my primary source.
- I could not independently verify which patent in Flexiworld family 22925285 was the subject of IPR2021-00713, or its outcome.
- I could not retrieve the defendant in C.D. Cal. case 8:21-cv-00807.
- I cannot state definitively whether any CAFC 2026 appeal exists; only that my searches returned nothing.
- I have not re-verified the current assignment record against USPTO's assignment database; "Flexiworld Technologies, Inc." as current assignee is as reported by the aggregators, which note their own data may be inaccurate.
Generated 9/14/2026, 12:46:47 PM
Cases on file (2)
Group view →Specific litigation cases in our database that name US patent 10740066. The free-form analysis below may also discuss cases beyond this list.
- Flexiworld Technologies, Inc. v. Roku Inc.filed Sep 8, 20206:20-cv-00819U.S. District Court, W.D. Tex. (Waco Division), Judge Alan D. Albrightstanding motion denied; disposition unverified
Defendants: Roku Inc.
- IPR2021-00713U.S. Patent Trial and Appeal BoardFinal Written Decision; outcome unverified
Defendants: Flexiworld Technologies, Inc.
Litigation summary
Past and pending lawsuits — plaintiffs, defendants, jurisdictions, outcomes, and notable rulings.
I'll research litigation involving US 10740066. Let me search multiple sources.
Let me dig deeper on specific cases and the PTAB proceeding.
Litigation involving US Patent 10,740,066 ("the '066 patent")
Identifying note on the number: The patent you asked about is US 10,740,066 (US10740066B2), "Output devices that establish wireless connection with an information apparatus subsequent to having been wirelessly discovered by the information apparatus," inventors William Ho Chang and Christina Ying Liu, original/current assignee Flexiworld Technologies, Inc. (application 16/396,460, filed 2019‑04‑26, granted 2020‑08‑11). In the litigation documents this patent is referred to as the '066 patent. Do not confuse it with Flexiworld's other "'066" patent, RE48,066 (an internet-based transactional/data-mining patent asserted against Indeed) — that is a different patent, and I excluded it.
1. Flexiworld Technologies, Inc. v. Roku Inc.
| Field | Detail |
|---|---|
| Plaintiff | Flexiworld Technologies, Inc. |
| Defendant | Roku Inc. (counterclaimant) |
| Jurisdiction | U.S. District Court, W.D. Tex. (Waco Division), Judge Alan D. Albright |
| Case No. | 6:20-cv-00819 (a/k/a W‑20‑CV‑00819‑ADA) |
| Filing date | September 8, 2020 |
| Patents asserted | 8,989,064 ('064), 10,346,114 ('114), 10,740,066 ('066) |
| Key ruling | Order Denying Roku, Inc.'s Motion for Partial Dismissal Due to Lack of Standing ('064 and '066 Patents), ECF No. 198, signed June 6, 2022, following a March 4, 2022 hearing. Roku argued the '066 and '064 patents had passed to Samsung under a Nov. 2012 Patent Purchase and License Agreement (assignment of U.S. 7,941,541 and application 13/103,958). The court construed the agreement under Washington law, applied ejusdem generis and Intellectual Ventures I LLC v. Erie Indem. Co., held the specific list of assigned patents controlled over general "rights related thereto" language, and held Flexiworld is the sole owner of the '066 and '064 patents and has standing. |
| Status | Motion denied; I was not able to verify the ultimate disposition of the case (settlement, dismissal, or judgment). Sources: CourtListener order, Justia docket doc. 198, UniCourt docket |
2. Flexiworld Technologies, Inc. v. Epson America, Inc.
| Field | Detail |
|---|---|
| Plaintiff | Flexiworld Technologies, Inc. |
| Defendant | Epson America, Inc. |
| Jurisdiction | U.S. District Court, C.D. Cal., Judge Andre Birotte Jr. (Magistrate Judge Douglas F. McCormick); originally assigned to Judge Christina A. Snyder, reassigned 5/18/2021 |
| Case No. | 8:21-cv-00807 (8:21-cv-0807 AB (DFMx)) |
| Filing date | April 29, 2021 |
| Patents asserted | Fourteen patents including 10,740,066 ("the '066 Patent") — per Epson's Answer (Aug. 23, 2021), the patents-in-suit also included 7,609,402; 8,630,000; 9,036,181; 10,037,178; 10,140,071; 10,140,073; 10,481,846; 10,481,847; 10,642,576; 10,761,791; 10,768,871; 10,846,031; 10,873,856. |
| Outcome/status | Closed — "REPORT ON THE DETERMINATION OF AN ACTION Regarding a Patent or Trademark (Closing)… Order Dismissing Civil Action," entered February 2, 2022. Dismissal terms are not shown in the available docket excerpts. |
| Sources | Unified Patents docket, Justia docket, Epson Answer PDF |
3. Flexiworld Technologies, Inc. v. Sony Corporation
| Field | Detail |
|---|---|
| Plaintiff | Flexiworld Technologies, Inc. |
| Defendant | Sony Corporation |
| Jurisdiction | U.S. District Court, E.D. Tex., Judge Rodney Gilstrap |
| Case No. | 2:23-cv-00616 |
| Filing date | December 19, 2023 (complaint); Sony served January 17, 2024 |
| Outcome/status | Dismissed with prejudice — Joint Stipulation of Dismissal filed May 27, 2025; case stayed for settlement March 7, 2025, stay extended, and "ORDER DISMISSING CASE" entered May 29, 2025. No merits ruling. |
| ⚠️ Verification caveat | The Stanford NPE Litigation Database lists 10740066 as a patent asserted in this case (npe.law.stanford.edu/patent/10740066), and the Google Patents "litigation" banner for US10740066 points to this case via the Darts-IP family. However, third-party patent lists for the operational patents in 2:23-cv-00616 (from PatSnap and GoldenCompass) enumerate 10037178, 10140073, 10387087, 10489096, 10642576, 10768871, 10846031, 10866773, 11029903, 11096056, 7609402, 9042811, 9836257, 9836259, 9965233 — not 10,740,066. The First Amended Complaint (June 6, 2024) similarly lists eight patents (9798516, 9042811, 9836259, 10768871, 10162596, 11029903, 11096056, 10387087). It is possible 10740066 appeared in the original complaint (which had 62 exhibit attachments) and was dropped from the amended pleading. Treat the inclusion of 10740066 in the Sony case as reported-but-unconfirmed. |
| Sources | Unified Patents docket / PACER Monitor, RPX Empower, PatSnap litigation note |
PTAB proceeding: IPR2021-00713
| Field | Detail |
|---|---|
| Caption | Roku, Inc. v. Flexiworld Technologies, Inc. |
| Patent | U.S. Patent No. 10,740,066 B2 |
| Case No. | IPR2021-00713 (companion IPR2021-00714 on 8,989,064) |
| Petitioner | Roku, Inc. (Perkins Coie LLP — Patrick McKeever, Evan Day) |
| Patent Owner | Flexiworld Technologies, Inc. (Nelson Bumgardner Conroy PC — Timothy E. Grochocinski, Austin Ginnings) |
| Panel | APJs Terrence W. McMillin, Christopher L. Ogden, Brent M. Dougal |
| Claims challenged | 7, 8, 10, 11, 14, 15, 17, 19 |
| Grounds | (1) Yamaguchi + Gu (claims 7, 8, 10); (1A) + Garfunkel (claim 11); (2) Ikonen + Gu (7, 8, 10); (2A) + Garfunkel (11); (3) Ikonen + Kammer (14, 15, 17); (3A) + Peng (19) |
| Oral hearing | July 19, 2022 (video) |
| Status | Google Patents' litigation banner records the case as having reached a Final Written Decision. I could not confirm the outcome of that Final Written Decision from the sources retrieved, and I will not guess at it. The record shows the Institution Decision rejected Ground 3 (Ikonen's "inquiry response" was not a "broadcast or advertisement of availability") and found Yamaguchi was not prior art on Ground 1, but instituted on Ground 2 — and Flexiworld argued the Board "incorrectly found Petitioner has reasonable likelihood of prevailing on Ground 2." A collateral priority dispute is also on the record: Flexiworld shifted from a January 19, 2001 priority date to the November 1, 2000 provisional (60/246,101) after the petition was filed (Ex. 1025, Reply Declaration of Samrat Bhattacharjee, Ph.D.). |
| Sources | IPR2021-00713 hearing transcript, Patent Owner demonstratives, Reply declaration Ex. 1025 |
What I could NOT confirm
- No confirmed appellate (CAFC) activity on 10740066. I found no Federal Circuit appeal docketed from IPR2021-00713 or from the Roku/Epson district court cases.
- The Final Written Decision outcome in IPR2021-00713 (claims cancelled / upheld / mixed) is unverified.
- The disposition of Flexiworld v. Roku, 6:20-cv-00819 after the June 2022 standing order is unverified (the docket research I could access stops at the standing ruling).
- Whether 10740066 was actually asserted against Sony — conflicting sources (see caveat above).
- I found no other district court case asserting 10,740,066. Flexiworld's other suits (Amazon; Hisense, 2:22-cv-00225/00228 E.D. Tex. and 1:22-cv-04338 N.D. Ga.; Brother, 2:22-cv-02250 W.D. Tenn.; Indeed, 1:24-cv-01254 W.D. Tex.) are separate campaigns on different Flexiworld patents; the Indeed case concerns RE48,066, not 10,740,066.
Related patent-prosecution/status facts worth noting
- Per Google Patents, US10740066B2 is Expired – Fee Related, with an anticipated expiration of 2021‑11‑01 (20 years from the 2000‑11‑01 priority).
- A request for ex parte reexamination was filed (effective 2021‑04‑08) against a related Flexiworld patent (US 10,346,114), and Roku filed IPR2021-00715 against US 10,346,114 — context that the Flexiworld "printing/output" family was attacked by Roku on multiple fronts in April 2021, contemporaneously with IPR2021-00713.
- The Epson action also implicated the Samsung Patent Purchase and License Agreement chain of title, the same issue litigated in the Roku standing motion and in the Amazon case (which, per Judge Albright's order, was transferred to the W.D. Wash. and stayed pending a motion to dismiss).
Generated 9/14/2026, 12:46:58 PM
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: Flexiworld Technologies, 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.
I'll research the PTAB record for US 10740066. The prompt's structured block says ODP shows no AIA proceedings, but the patent's own Google Patents page flagged an IPR — let me verify.
Found the core proceeding (IPR2021-00713, Roku v. Flexiworld). Now I need the Final Written Decision outcome and any appeal.
Let me get the claim-level outcome for the '066 IPR specifically, plus any appeal.
PTAB / AIA trial analysis — US 10,740,066 (Flexiworld Technologies, Inc.)
⚠️ Threshold flag — the "no PTAB activity" premise is wrong. The structured block supplied in this prompt states that the USPTO ODP API returns no AIA trial proceedings for this patent. Web research directly contradicts that. There is at least one AIA trial on the '066 patent: IPR2021-00713, Roku, Inc. v. Flexiworld Technologies, Inc., and the '066 patent's own Google Patents page links it as "PTAB case IPR2021-00713 filed (Final Written Decision)." Multiple third-party dockets, PTAB papers, and hearing transcripts confirm the case number, the parties, and that the patent at issue is U.S. 10,740,066. Treat the ODP "no proceedings" result as an ingest gap, not an absence of proceedings. Do not rely on it for a freedom-to-operate or estoppel analysis.
Proceedings overview
Count: 1 AIA trial proceeding on the '066 patent itself (IPR2021-00713, Roku v. Flexiworld), status = Final Written Decision issued; the claim-level disposition of that FWD is not verifiable from the sources I could reach, so I cannot tell you whether claims 7/8/10/11 were canceled or sustained — that single missing fact is the whole ballgame and must be pulled from PTAB E2E before anyone relies on this patent either way. What is documented is that the Board instituted only Ground 2/2A (Ikonen-based), covering only claims 7, 8, 10, 11, and denied institution on Grounds 1/1A (Yamaguchi not shown to be prior art) and Grounds 3/3A (claims 14, 15, 17, 19 — Ikonen's "inquiry response" not a broadcast/advertisement of availability). Bottom line for a defendant: claims 14, 15, 17 and 19 were never tested at trial and were never at risk of cancellation in this IPR — they are the patent's least-litigated, arguably most exposed flank. Claims 7, 8, 10, 11 went to a final decision whose outcome you must verify. Separately, the '066 record reports legal status "Expired - Fee Related" with an anticipated expiration of 2021-11-01 — if that is accurate, assertion value is limited to past (pre-expiration) damages under 35 U.S.C. § 286, and no injunctive theory survives.
IPR2021-00713 — Roku, Inc. v. Flexiworld Technologies, Inc.
Type: Inter Partes Review (35 U.S.C. §§ 311–319)
Patent: U.S. Patent No. 10,740,066 B2 ("the '066 patent")
Filed: 2021-04-09 (reported filing date; the companion IPR2021-00714 on U.S. 8,989,064 filed 2021-04-09 per Patexia, and Roku's '714/'715 filings on the same family are recorded with effective date 2021-04-09. The exact '713 petition date was not independently confirmed — verify in E2E.)
Status: Final Written Decision issued (per the '066 patent's Google Patents litigation link: "PTAB case IPR2021-00713 filed (Final Written Decision)"). Claim-level disposition not verified — see gap note below.
Judge panel: at the 2022-07-19 oral hearing: Administrative Patent Judges Terrence W. McMillin, Christopher L. Ogden, and Brent M. Dougal (per the Record of Oral Hearing, IPR2021-00713/-00714). (Companion '714 FWD panel was Brent M. Dougal (writing), Bryan F. Moore, Christopher L. Ogden per Patexia; I did not verify the '713 FWD panel roster.)
Parties / counsel: Petitioner Roku, Inc. — Perkins Coie LLP (Patrick McKeever, Evan Day); expert Dr. Samrat Bhattacharjee. Patent Owner Flexiworld Technologies, Inc. — Nelson Bumgardner Conroy PC (Timothy E. Grochocinski, Austin Ginnings); expert Dr. Todor Cooklev.
Petition grounds — challenged claims 7, 8, 10, 11, 14, 15, 17, and 19 (per Ex. 1025, Bhattacharjee Reply Decl. ¶ 1; confirmed by both parties' demonstratives):
Ground Claims Reference(s) 1 7*, 8, 10 Yamaguchi, Gu 1A 11 Yamaguchi, Gu, Garfunkel 2 7*, 8, 10 Ikonen, Gu 2A 11 Ikonen, Gu, Garfunkel 3 14*, 15, 17 Ikonen, Kammer 3A 19 Ikonen, Kammer, Peng (* = independent claim as identified in Patent Owner's demonstratives, Ex. 2042.) Statutory basis: § 103 obviousness (with a predicate § 102/§ 112 priority fight — see below).
Institution decision: Paper 21; partially instituted — Grounds 2 and 2A instituted; Grounds 1/1A and 3/3A denied. As characterized by Patent Owner (Ex. 2042): the Board "Correctly found Ground 3 insufficient because Ikonen's 'inquiry response' is not a 'broadcast or advertisement of availability'" and "Correctly found Ground 1 insufficient because Yamaguchi is not prior art." (ID dated October 2021 — companion '714 ID is dated 2021-10-22; exact '713 ID date not verified.)
- The Ground 1 denial turned on a priority dispute: Roku's petition assumed a 2001-01-19 effective date (Provisional 60/262,764), which Yamaguchi pre-dates. After the petition was filed, Flexiworld shifted position to claim benefit of Provisional 60/245,101, filed 2000-11-01, which knocks Yamaguchi out. Roku argued in reply that claim 7 is not entitled to the '101 provisional because it fails to describe a first "output device" that processes output data for a second "output device" (Ex. 1025 ¶¶ 5–6). The Board sided with Flexiworld at the institution stage on this point.
Final Written Decision: Issued (date not verified; the companion '714 FWD issued 2022-10-21 on the shared statutory 1-year trial clock, and the two cases were heard together on 2022-07-19). Because institution was limited to Grounds 2/2A, the FWD could, as a matter of scope, have adjudicated only claims 7, 8, 10, and 11. Claims 14, 15, 17, and 19 were not part of the trial and were not addressed on the merits. I will not state which of claims 7/8/10/11 were canceled or held patentable — that specific disposition is not in the sources I retrieved, and fabricating it would be worse than admitting the gap.
Settlement / termination: No settlement or termination identified; the case proceeded through institution, Patent Owner Response (Paper 24), Sur-Reply (Paper 34), a reply declaration (Ex. 1025), expert depositions (Cooklev, 2022-03-30), and oral hearing. No adverse judgment or abandonment noted.
Appeal: Not verified. I could not confirm whether the '713 FWD was appealed to the Federal Circuit (and could not check the '714 FWD either). Do not assume either way.
Cross-reference — same petitioner, same family, file 2021-04-09: Roku also filed IPR2021-00714 on U.S. 8,989,064 (sibling patent; FWD 2022-10-21, panel Dougal/Moore/Ogden, with Patexia reporting claims invalidated "1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 12, 14…" — list truncated in the source), and IPR2021-00715, recorded on the U.S. 10,346,114 patent's Google Patents legal events with opponent "ROKU, INC.", effective 2021-04-09. These are different patents, not proceedings on the '066 patent, but they are the clearest available signal of how Roku's campaign against this family played out claim-by-claim.
Defensive value: Two usable points regardless of the missing FWD outcome. First, claims 14, 15, 17, 19 of the '066 patent have never been through an instituted AIA trial — the Board twice declined the only presented grounds against claim 14 (the "advertising"/availability broadcast limitation) and claim 19, and no other petitioner appears to have tried. That is both an opportunity (untested claims invite a fresh IPR, subject to § 315(b)) and a warning (the Board's institution-stage reading of "broadcasting or advertising … availability" on the '066 specification at 21:7-17 is friendly to the patent owner on that term). Second, the Yamaguchi art was knocked out as non-prior-art because the Board accepted a 2000-11-01 effective date. Any defendant planning to use Yamaguchi against the '066 patent must expect to re-litigate — and win — the priority/§ 112 written-description fight first.
Strategic summary
Which claims are canceled / sustained / untested. This is the part you must not guess at. What is structurally certain is the scope of the only adjudication on this patent: the Board instituted on Ikonen + Gu / Ikonen + Gu + Garfunkel against claims 7, 8, 10, and 11 and rendered a Final Written Decision (the '066 patent's Google Patents record links the case as having reached FWD). Claims 14, 15, 17 and 19 were denied institution and therefore are neither canceled nor adjudicated — they are untested at the PTAB. The claim-by-claim outcome for 7/8/10/11 is the single fact I could not verify; my honest position is that stating it would be fabrication. Practically: if your demand letter or complaint asserts claim 14 or claim 19, no IPR has yet touched it, and you are the first mover on those claims. If it asserts claim 7, check the FWD first — every ground Roku presented against claim 7 other than Ikonen + Gu was refused at institution.
Estoppel landscape. Estoppel under § 315(e)(2) runs against Roku and its privies only, and only as of the FWD. For Roku that bar is broad in both directions: it reaches Grounds 2/2A (instituted and finally decided) and Grounds 1/1A and 3/3A (raised in the petition and reasonably could have been raised). It does not estop you. Two consequences: (a) the printed publications Roku developed — Ikonen, Gu, Garfunkel, Kammer, Peng, Yamaguchi — are now fully public and citable in district court by any later defendant, and (b) you are not bound by the Board's institution-stage rejection of the Yamaguchi grounds, including its acceptance of the 2000-11-01 priority date — but that rejection is a strong preview of how the Board would treat Yamaguchi again, so budget for a written-description challenge to the '066 claims' entitlement to Provisional 60/245,101 before you lean on Yamaguchi. Note also that the '066 patent is a continuation-in-part joining the 10/016,223 chain (filed 2001-11-01) and the 10/053,765 chain (filed 2002-01-18, claiming Provisional 60/262,764 of 2001-01-19); the priority splice between those chains is the highest-value invalidity lever in the file.
Pattern signals. Roku is a serial petitioner against this family — IPR2021-00713 ('066), IPR2021-00714 ('064), and IPR2021-00715 (recorded on '114), all effective 2021-04-09, all litigated by Perkins Coie, with the '713/'714 cases argued together on 2022-07-19. Flexiworld's PTAB practice is defensive and expert-heavy (Grochocinski/Ginnings; Dr. Cooklev), and it successfully changed its priority story mid-IPR to defeat Yamaguchi. A defensive aggregator is in the chain but on a different patent: Unified Patents filed an ex parte reexamination on U.S. 10,346,114 (control no. 90/014,721), which the USPTO granted on 2021-05-11 finding substantial new questions of patentability — that reexam, not an IPR, is how Unified attacked this family, and it is on the '114, not the '066. Finally, the '066 patent's own Google Patents record carries "Expired - Fee Related" with anticipated expiration 2021-11-01, and a family member (the '114) is recorded as lapsed for failure to pay maintenance fees effective 2023-07-09. If the '066 patent is in fact expired, the patent's assertion value collapses to pre-expiration past damages.
Recommended next steps
- Pull the '713 Final Written Decision today — this is the one open item. Use PTAB E2E (https://e2e.uspto.gov/) for the IPR2021-00713 file wrapper (Papers 21 and the FWD), the PTAB decisions search at https://www.uspto.gov/patab (PTAB Decisions / the PTAB API at https://developer.uspto.gov/api-catalog), the case folder at https://www.docketalarm.com/cases/PTAB/IPR2021-00713/Roku_Inc._v._Flexiworld_Technologies_Inc/, and the aggregator link on the patent page at https://portal.unifiedpatents.com/ptab/case/IPR2021-00713. Read the Disposition paragraph of the FWD literally and quote claim numbers verbatim; if the FWD canceled claims 7/8/10/11, say so in those exact terms; if it sustained them, your IPR path is much harder.
- If claims were canceled: cite and quote the FWD disposition directly against any demand letter or complaint count built on those claims — a canceled claim cannot support infringement, and post-issuance cancellation is an incontestable defensive fact. If only some were canceled, map them precisely; do not generalize.
- If claims 7/8/10/11 survived: do not refile the same Ikonen + Gu theory — you would be re-arguing art the Board has already passed on, and the § 325(d) discretion and estoppel-by-analogy risks are real. Your better levers are (i) a written-description / priority attack on the '101 Provisional to move the effective date to 2001-01-19 and revive Yamaguchi, (ii) new art against claims 14, 15, 17, 19, which are untested, and (iii) the "broadcasting or advertising availability" limitation, which is the term the Board read narrowly at institution the first time.
- Verify the '066 patent's legal status in PatentCenter. The Google Patents record shows "Expired - Fee Related" and anticipated expiration 2021-11-01. Confirm the expiration/lapse date and whether any maintenance fee was reinstated. An expired patent still supports past damages to the § 286 six-year lookback, but it kills injunctive and ongoing-royalty theories — that reframes settlement value immediately.
- Confirm the appeal posture. I could not verify whether the '713 (or '714) FWD was appealed to the Federal Circuit. Check the CAFC docket and CourtListener (https://www.courtlistener.com/?q=Flexiworld) before treating any FWD as final and non-appealable; a pending appeal changes the estoppel analysis and the settlement calculus.
- Do not rely on the "no PTAB activity" premise. The absence of an ODP record here is a data gap; the actual PTAB record on this patent includes a full trial with a Final Written Decision.
Verification log — items I could NOT confirm (do not fill these in by inference)
- The claim-level disposition of the IPR2021-00713 FWD (which of claims 7, 8, 10, 11 were canceled vs. sustained). Unknown to me.
- The exact FWD date for IPR2021-00713 (inferred October 2022 from the shared trial clock and companion '714 FWD of 2022-10-21). Not verified.
- The exact petition filing date and institution decision date for IPR2021-00713 (2021-04-09 and October 2021 respectively, inferred from the companion '714 docket). Not verified.
- The FWD panel composition for '713 (the hearing panel of McMillin/Ogden/Dougal is confirmed; the FWD roster is not).
- Whether IPR2021-00715 is in fact directed to U.S. 10,346,114 — it is recorded that way on the '114 patent's Google Patents legal-events table, but I did not confirm it against the PTAB docket.
- Federal Circuit appeal(s) — docket numbers, issues, and disposition. Not checked (research truncated).
- The full claim list invalidated in the companion '714 FWD on the '064 patent (the source string was truncated mid-list).
- Which patents Flexiworld actually asserted in W.D. Tex. 6:20-cv-00819 and C.D. Cal. 8:21-cv-00807, and whether the '066 patent was among them.
Primary sources cited above: IPR2021-00713/-00714 Record of Oral Hearing (2022-07-19) and Petitioner/Patent Owner demonstratives (Exs. 1037, 2042), Bhattacharjee Reply Declaration (Ex. 1025), Cooklev deposition transcript (2022-03-30), Patexia case summary for IPR2021-00714, Unified Patents' 2021-07-07 note on ex parte reexam 90/014,721 ('114 patent), and the Google Patents legal-events/status records for U.S. 10,740,066, 10,346,114, and 8,989,064.
Generated 9/14/2026, 12:47:32 PM
Ownership chain (2)
Asserters network →Structured records extracted from the assignment-history narrative below. Each entity links to its full ownership-network profile.
2002-07-18 · reel 042385/0202 · Assignment
CHANG, WILLIAM HO; LIU, CHRISTINA YINGFLEXIWORLD TECHNOLOGIES, INC., WASHINGTON
? · reel 028733/0064 · Assignment
CHANG, WILLIAM HO; LIU, CHRISTINA YINGFlexiworld Technologies, Inc.
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 verify the assignment chain against live sources before writing.
Key finding surfaced: an assignment to Flexiworld with reel/frame 042385/0202. Let me pin down whether that record covers this patent and check the corporate/NPE posture.
Reel 042385/0202 confirmed as the inventors→Flexiworld assignment. Now I need to determine whether this patent itself carries a recorded assignment, plus the asserter profile.
Inventors
Two named inventors, both consistent across the entire Flexiworld family:
| Inventor | Address of record (per patent front matter) | Employer at time of filing |
|---|---|---|
| William Ho Chang | Vancouver, WA | Flexiworld Technologies, Inc. — Chang is the founder/principal of Flexiworld; he is the assignor on the family-wide inventor assignment (Reel 042385/0202) |
| Christina Ying Liu | Fremont, CA | Flexiworld Technologies, Inc. — co-assignor on the same record |
Pattern note — no departure signal. The typical red flag I look for here (all inventors exiting the assignee within 12 months of filing, ahead of a portfolio sale) is absent. Both inventors remain the named inventors on essentially the entire 59-patent Flexiworld portfolio (see the long list of Chang William Ho / Liu Christina Ying family members surfaced by Google Patents and Unified Patents), and both are signatories to the family-wide assignment. This is a founder-inventor portfolio, not an employee-invention portfolio that was abandoned. That said, the effective date of their assignment (2002-07-18) was recorded roughly 15 years after execution — see the timeline below.
Original assignee
Flexiworld Technologies, Inc. (Vancouver, Washington). Named as original assignee and current assignee on the Google Patents record (https://patents.google.com/patent/[US10740066B2](/patent/US10740066B2)/en) and on the Unified Patents portal as "Flexiworld Tech Inc" (https://portal.unifiedpatents.com/patents/patent/[10740066](/patent/10740066)).
- Primary line of business: patent holding and licensing/enforcement. Flexiworld is a founder-controlled portfolio entity whose 59 granted U.S. patents (2015–2023, per USPTO PatentsView data via https://plainpatent.com/company/flexiworld-technologies-inc/) are all in the same G06F/G06Q/H04W wireless-output space claiming priority to 2000–2002 applications.
- Product embodying the claims: I found no evidence of any commercial product. I did not locate a current product line, and Flexiworld's litigation posture (notice letters and suits, not marketplace competition) is inconsistent with an operating company asserting against competitors. I flag this as a negative finding from absence of evidence, not as proof — I did not verify a 2001–2003 product history.
- Current status: not dissolved. The entity is still actively asserting: it appears as plaintiff in E.D. Tex. case 2:25-cv-00960 (complaint asserting the '811, '072 and '178 patents, citing Reel/Frame 042385/0202 for each — https://ai-lab-cl-prod.azurewebsites.net/case/dct/txed/2:25-cv-00960/doc/analysis/1), and in Flexiworld v. Hisense (RPX docket document 15143102). Stanford's NPE Litigation Database classifies Flexiworld as
3 Failed startup— i.e., as a patent asserter, in the failed-startup category (https://npe.law.stanford.edu/patent/10740066).
Assignment timeline
Data-access caveat, stated up front: the USPTO Assignment Center / assignment.uspto.gov UI is not directly reachable from my available search tooling, so I could not pull the Abstract of Title for patent number 10,740,066 itself. What follows is reconstructed from (a) Google Patents' AS | Assignment legal-event block on the Flexiworld family, and (b) Flexiworld's own infringement complaints, which plead their assignment records by reel/frame. Items I could not verify against the primary record are marked accordingly. Do not treat the reel numbers below as confirmed-against-10,740,066 without pulling the Abstract of Title.
2002-07-18 (executed) / recorded ~2017 (exact recording date not retrieved) — Reel 042385/0202
- Conveyance: ASSIGNMENT OF ASSIGNORS' INTEREST
- Assignor: CHANG, WILLIAM HO; LIU, CHRISTINA YING (individually)
- Assignee: FLEXIWORLD TECHNOLOGIES, INC., WASHINGTON
- Correspondent: not retrieved — see the gap note below
- Context: founding-entity assignment; the two inventors conveyed their rights to their own company. Recorded as a single omnibus instrument covering a large number of family properties, ~15 years after execution.
Verification gap: This reel is the assignment record Flexiworld pleads for multiple family members (e.g., the '811, '072 and '178 patents in 2:25-cv-00960). I could not confirm that Reel 042385/0202 specifically lists patent 10,740,066. Note the sequencing problem: the instrument was executed in 2002 and recorded around 2017, whereas application 16/396,460 (this patent) was not filed until 2019-04-26 — so unless a later record or a confirmatory assignment was filed, this omnibus record may not reach this application. Resolving this requires the Abstract of Title.
Earlier Flexiworld reel — Reel 028733/0064 (a second Flexiworld inventor-assignment record, pleaded for the '402 patent = US 7,609,402 in the Hisense complaint)
- Conveyance: ASSIGNMENT OF ASSIGNORS' INTEREST
- Assignor: CHANG, WILLIAM HO; LIU, CHRISTINA YING
- Assignee: FLEXIWORLD TECHNOLOGIES, INC.
- Correspondent: not retrieved
- Context: the same two inventors assigning to the same assignee on a different reel — evidence that Flexiworld has more than one omnibus inventor-assignment record and that the family's title documentation is not on a single instrument. Whether 10,740,066 is covered by 042385/0202, 028733/0064, both, or neither is unresolved.
No other assignments found. I found no record of: any transfer out of Flexiworld; any assignment to a licensing LLC, aggregator, or acquirer; any security agreement, merger, or name change; and no defensive-aggregator acquisition. As far as the evidence shows, Flexiworld has owned this patent continuously since the inventors assigned their rights.
Unresolved discrepancy in the priority chain — flagging a parent, not this patent. In the previously generated section, the priority chain runs through Ser. No. 13/710,295, issued as US 9,383,956. Google Patents lists two assignees for US 9,383,956: "Flexiworld Tech Inc" and "Mattel, Inc." (https://patents.google.com/patent/[US10346114B2](/patent/US10346114B2) — family table; also https://patents.google.com/patent/[US10133527B2](/patent/US10133527B2)). If that reflects a recorded assignment and not a data artifact, it would mean a genuine transfer affecting a parent in this patent's chain. I could not verify it. This is a lead for the Assignment Center, not a finding, and I am not asserting Mattel has any interest in US 10,740,066.
Correspondent-of-record gaps (explicitly not filled): the task asks for the filing attorney/agent on each recording, because that is the best shell-entity tell. I could not retrieve the correspondent for Reel 042385/0202 or Reel 028733/0064, and I will not invent one. Relevant nearby data point, carefully distinguished: the prosecution attorney/agent of record on the face of US 10,740,066 is Chernoff Vilhauer LLP (Portland, OR), per the patent front matter. That is the prosecuting firm for the Flexiworld family, not the assignment correspondent — the two roles are distinct and I have no evidence tying Chernoff Vilhauer to the recordings.
Timeline diagram
timeline
title Ownership of US 10740066
2000 : Provisional filed by Chang and Liu
2001 : Parent application 10016223 filed
2002 : Inventors assign rights to Flexiworld
2017 : Inventor assignment recorded
: Reel 042385 frame 0202
2019 : Continuation 16396460 filed
2020 : Patent US 10740066 issues
: First suit filed against Roku
2021 : Patent term expires
2023 : Suit filed against Sony
2025 : Further Flexiworld suits filed
NPE / troll-pattern signals
Shell-entity transfer — not present. The only conveyance in the chain runs inventors → Flexiworld Technologies, Inc., the same entity that is the original and current assignee. There is no "IP / Holdings / Licensing / Ventures" successor, no single-purpose LLC, and no transfer at all out of the founder-controlled company. This is an original-owner asserter, not a shell structure.
Known asserter in the chain — present. Flexiworld Technologies, Inc. is itself the asserter throughout. It is indexed as a patent asserter in the Stanford NPE Litigation Database, category "3 Failed startup", at https://npe.law.stanford.edu/patent/10740066, and it appears in RPX's litigation-document database (https://insight.rpxcorp.com/litigation_documents/15143102) and on the Unified Patents portal. Note this is not a match against the named lists in my mandate (Acacia, Marathon, IV, Wi-LAN, etc.) — Flexiworld is an independent failed-startup asserter, and I am not attributing it to any of those families. Assertion activity tied to this patent: Flexiworld v. Roku, No. 6:20-cv-00819 (W.D. Tex., filed 2020-09-08, complaint attached "Exhibit 6 – Roku '066 Claim Chart"); Flexiworld v. Sony Corp., No. 2:23-cv-00616 (E.D. Tex.); and C.D. Cal. 8:21-cv-00807.
Repeat correspondent across the chain — unclear. There is only one meaningful link in the chain (plus the parallel 028733/0064 record), so there is no recurrence to analyze, and in any event I could not retrieve the correspondents at all from the sources available to me. No finding either way. I do want to be precise about what a "repeat correspondent" finding would require here: with a founder-assignee that never transferred the patent, the informative correspondent would be on the 028733/0064 vs. 042385/0202 pair — same filer or different filers.
Cascading transfers — not present. No chained transfers. One assignment, executed 2002, and nothing since. Nothing resembles the LLC-to-LLC chain of 2+ assignments in under 24 months.
Pre-litigation transfer — not present. The sole assignment is effective 2002-07-18; the first suit naming this patent (Roku) was filed 2020-09-08. That is ~18 years before the first assertion — the opposite of a venue/standing-motivated late transfer. (The 2017 recording is pre-litigation by 3 years and appears to be a bookkeeping cleanup rather than an assertion-driven transfer, though I cannot confirm the recorded date.)
Bankruptcy fire-sale — not present. No Chapter 7/11 record, no trustee sale, no portfolio auction found. Flexiworld remained the grantee of record throughout.
Privateering — not present. Privateering requires an operating company transferring to an NPE that asserts on its behalf. Flexiworld transferred to no one; it asserts for itself. There is no operating-company transferor in the chain.
Defensive aggregator (anti-NPE) — not present. The chain does not terminate at RPX, AST, LOT, Unified Patents, or OIN. To the contrary: Unified Patents is the challenger, not the transferee — the Google Patents family record lists PTAB IPR2021-00713 with petitioner "Unified Patents" (https://portal.unifiedpatents.com/ptab/case/IPR2021-00713). (Caveat carried over from the prior section: that IPR is attached at the family level, so I still cannot confirm whether US 10,740,066 itself — rather than another family member — was the challenged patent, or its final outcome.) This patent has not been neutralized by acquisition.
A structural fact worth stating plainly, because it cuts against the usual troll narrative: there is no assignment-chain evidence of NPE behavior here at all. The classic NPE signature — a shell-entity transfer — is what makes chain analysis useful, and it is absent. Flexiworld's NPE character comes from its conduct (a 59-patent founder portfolio, notice letters, serial suits against TV/printer/consumer-electronics makers, a "failed startup" classification by Stanford, no product in commerce), not from its paper title.
Verdict
NPE — moderate confidence.
Justification: only one strong signal is present — Flexiworld Technologies, Inc. is a publicly indexed patent asserter (Stanford NPE Litigation Database, category "3 Failed startup", https://npe.law.stanford.edu/patent/10740066) that has asserted this patent across multiple suits against Roku, Sony and others, and there is no evidence it ships any product embodying the claims. Every structural transfer signal is absent: the only recorded conveyance is the 2002-07-18 inventors→Flexiworld assignment (Reel 042385/0202; sibling record Reel 028733/0064), there are no shell-entity transfers, no cascading LLCs, no pre-litigation transfer, no bankruptcy sale, and no defensive-aggregator termination — so this is an original-owner failed-startup asserter rather than a privateering or shell-LLC chain. Had I been able to confirm a recorded assignment specific to 10,740,066 and a recurring assignment correspondent, this would likely escalate to high confidence; as it stands the supporting signals are one strong plus several absent, which lands at moderate.
Verify at: https://assignmentcenter.uspto.gov/ (search by patent number 10740066; also pull the Abstract of Title and the cover sheets for Reels 042385/0202 and 028733/0064 to capture the correspondents I could not retrieve). Cross-check the US 9,383,956 "Mattel, Inc." assignee discrepancy while you are in there — it is the one open question that could change this picture.
Two contradictions with the previously generated sections that I am flagging rather than silently resolving: (i) the prior section recorded that Google and Unified disagree by one day on filing (2019-04-26 vs. 2019-04-25), grant (2020-08-11 vs. 2020-08-10) and priority (2000-11-01 vs. 2000-10-31) — that discrepancy is still unresolved and it matters for the expiration line in the diagram above; and (ii) the prior section found no CAFC 2026 activity, which is consistent with what I see here, but note the patents expired in 2021 per Google/Unified, so post-2021 suits (Sony 2023, 2025 filings) can only be reaching back damages inside the §286 window.
Generated 9/14/2026, 12:47:33 PM
Prior art
Earlier patents, publications, and products that may anticipate or render the claims unpatentable.
I'll verify the patent and gather its citation record from live sources before analyzing prior art.
Let me pull the actual citation record and the IPR prior-art grounds.
Let me retrieve the cited-references table and the IPR references precisely.
Verification and scope
I searched for the literal string 10740066 / 10,740,066 and did not substitute any similar number. The patent is confirmed:
- US 10,740,066 B2, "Output devices that establish wireless connection with an information apparatus subsequent to having been wirelessly discovered by the information apparatus," Appl. No. 16/396,460, filed Apr. 26, 2019, granted Aug. 11, 2020, inventors William Ho Chang / Christina Ying Liu, assignee Flexiworld Technologies, Inc., primary examiner Melvin H. Pollack. (https://patents.google.com/patent/[US10740066B2](/patent/US10740066B2)/en; https://uspto.report/patent/grant/[10,740,066](/patent/10740066))
Resolution of a conflict flagged in my earlier section. Previously I wrote that I could not confirm whether US 10,740,066 itself (rather than another family member) was the subject of IPR2021-00713. That caveat is now resolved: PTAB filings state on their face "PTAB Case No. IPR2021-00713 / U.S. Patent No. 10,740,066," and the Patent Owner's own demonstratives read "IPR No. 2021-00713 (U.S. Patent 10,740,066)." The '066 patent is the challenged patent. (https://portal.unifiedpatents.com/ptab/case/IPR2021-00713; Docket Alarm exhibits cited below.)
1. Important structural finding about the '066 citation record
Before any per-reference analysis, a finding that changes how the citation list must be read:
The "References Cited" list on the face of US 10,740,066 is not a set of examiner-assailed references directed at the '066 claims. It is a cumulative family citation dump — roughly 700+ U.S. patents spanning Dec. 1971 (3,629,493 Morgenfruh) through May 2020 (10,642,576 Chang et al.), plus dozens of U.S. pre-grant publications (2001/0011302 through 2020/0097225), 15 foreign documents, and ~90 "Other References," virtually all marked "cited by applicant."(https://uspto.report/patent/grant/10,740,066)
Two tells confirm this:
- The list includes Flexiworld's own earlier patents and the inventor's own applications — e.g., 7,941,541 (Chang et al.), 7,944,577 (Chang et al.), 8,332,521 (Chang et al.), 9,383,956 (Chang et al.), and dozens of
2002/0097xxxChang publications. A reference naming the same inventors is not prior art "by another" under pre-AIA §102(a)/(e); it is relevant only to priority, §102(g), or obviousness-type double patenting. - The list includes the parent application's USPTO office actions by number (10/016,630; 10/000,732; 10/003,594; 13/710,299; 14/828,349/369/359; 16/229,896, etc.) and PCT search reports for PCT/US01/46247 and PCT/US01/48057 — i.e., the prosecution history of the family.
Consequence: filing dates, priority dates, and abstracts for individual entries are not stated in the citation list itself (only issue/publication month-year and inventor surname). I can give you verbatim citation data for the entire list, but I cannot supply verified filing dates and technical descriptions for all ~1,000 entries without pulling each document individually — and I will not invent them. Below I therefore do what actually serves the purpose of the request: rank the references that are genuinely probative against claims 1, 7, and 14, and give verified detail for those.
2. Tier 1 — the art actually asserted against the '066 claims (most relevant prior art)
The most probative prior art for US 10,740,066 is not on the patent's face at all. It was assembled by Roku, Inc. in IPR2021-00713, which sought cancellation of claims 7, 8, 10, 11, 14, 15, 17, and 19. The grounds table, verbatim from the Patent Owner's demonstratives:
| Ground | Claims | Reference(s) | Statutory theory as pleaded |
|---|---|---|---|
| 1 | 7*, 8, 10 | Yamaguchi, Gu | §103 combination (Yamaguchi primary) |
| 1A | 11 | Yamaguchi, Gu, Garfunkel | §103 |
| 2 | 7*, 8, 10 | Ikonen, Gu | §103 combination (Ikonen primary) |
| 2A | 11 | Ikonen, Gu, Garfunkel | §103 |
| 3 | 14*, 15, 17 | Ikonen, Kammer | §103 |
| 3A | 19 | Ikonen, Kammer, Peng | §103 |
(* = independent claim.) Source: https://www.docketalarm.com/cases/PTAB/IPR2021-00713/Roku_Inc._v._Flexiworld_Technologies_Inc/docs/07-14-2022-Patent_Owner/Exhibit-2042-Patent_Owners_Demonstratives.pdf
Institution and outcome, as recorded:
- The Board instituted on Ground 2/2A only.
- The Board refused Ground 1/1A — "Correctly found Ground 1 insufficient because Yamaguchi is not prior art."
- The Board refused Ground 3/3A — "Correctly found Ground 3 insufficient because Ikonen's 'inquiry response' is not a 'broadcast or advertisement of availability.'"
- A Final Written Decision issued (confirmed by Flexiworld/Roku's Oct. 27, 2022 joint motion in IPR2022-01267, which states "The Board has issued Final Written Decisions in IPR2021-00713 and IPR2021-00714").
- I could not retrieve the operative result of the FWD (which claims, if any, were cancelled). I am not asserting an outcome.
The Yamaguchi priority fight (the single most consequential §102 fact for this patent). Roku's expert declaration states that Flexiworld originally pleaded only the Jan. 19, 2001 filing date of provisional 60/262,764 — under which Yamaguchi undisputedly pre-dated the invention — and that after the Petition was filed, Flexiworld changed position to claim benefit of provisional 60/246,101 dated Nov. 1, 2000, which pushed Yamaguchi out of the §102 window. (Ex. 1025, Reply Declaration of Samrat Bhattacharjee, ¶ 5.) That is exactly the kind of priority-date contingency that governs every §102 mapping below.
What this means for §102 specifically
An important precision point, since you asked which claims each reference anticipates under §102: every asserted ground in IPR2021-00713 was a §103 combination, not a §102 anticipation. Petitioner itself therefore treated each reference as disclosing less than the full claim. My honest §102 overlay is:
| Reference (as identified in the PTAB record) | Asserted against | Closest to single-reference §102 on | Notes |
|---|---|---|---|
| Ikonen (primary) | claims 7, 8, 10 (w/ Gu); claims 14, 15, 17 (w/ Kammer) | claims 14, 15, 17 | Strongest single-reference candidate; it was the ground that survived institution. Its defeat at Ground 3 turned on claim 14's "broadcasting or advertising availability" limitation — the Board held Ikonen's "inquiry response" is not an advertisement of availability. |
| Yamaguchi (primary) | claims 7, 8, 10 | claim 7 | Never reached the merits in the FWD because the priority date moved and it ceased to be prior art. |
| Gu | secondary in Grounds 1, 1A, 2, 2A | none alone | Used to supply elements missing from Yamaguchi/Ikonen. |
| Garfunkel | secondary, claim 11 only | none alone | Tied to claim 11's download/install-from-server limitation. |
| Kammer | secondary in Grounds 3, 3A (claims 14, 15, 17) | none alone | Likely US 7,356,347 (Kammer, Apr. 2008) — this surname appears in the '066 face citation list at that number/date — but I have not verified that the IPR exhibit and the face-cited patent are the same document, and a 2008 issue date only qualifies as prior art if its underlying filing/priority date clears the critical date. |
| Peng | secondary, claim 19 only | none alone | Possible (unverified) match to the face-cited US 2017/0318115 A1 (Peng et al., Nov. 2017). If that is the reference, it could only be §102(a)(2)/§102(e) art — which means claims 14–19 would have to be denied the 2000/2001 priority date (plausible, since '066 is a CIP). Flagging as an inference, not a verified citation. |
I did not retrieve the Petition (Paper 2) or Exhibits 1002–1037, so I cannot give you the full bibliographic citations (patent/publication number, filing date, assignee) for Yamaguchi, Gu, Garfunkel, Ikonen, Kammer, or Peng. I am not going to fabricate those numbers.
3. Tier 2 — the most relevant references actually listed on the '066 face
These are verbatim entries from the '066 "References Cited" list, with titles I was able to ground from independent sources. Dates are the issue/publication dates as printed in the citation list (not filing dates).
| Citation (verbatim from '066 list) | Date (as listed) | Description | §102 exposure |
|---|---|---|---|
| US 6,138,178 — Watanabe | Oct. 2000 | "Controlled device storing multiple drivers that judges and downloads a particular driver corresponding to a controller's operating system having an identical or greater version number" (assignee Fujifilm; priority 1997-01-28). | §102(b) as to claims 6 and 11 ('066's download/install-application-software limitations) and to claim 1's "device dependent attributes" transmission — a device storing driver information and serving it to a requesting controller. |
| US 6,285,889 — Nykanen | Sep. 2001 | "Information output system, method for outputting information and terminal devices for outputting information via mobile communication network" (priority 1996-08-07). | §102(a)/(e) depending on the critical date — directed at the core "mobile apparatus outputs to a remote output service" concept of claims 1, 7, 14. |
| US 7,379,958 — Karhu | May 2008 | "Automatic and dynamic service information delivery from service providers to data terminals in an access point network" (https://patents.google.com/patent/[US7379958B2](/patent/US7379958B2)). | §102(e) — squarely addresses service information delivery/discovery in a wireless access-point network, i.e., the "announce or advertise availability / transmit device attributes" steps of claims 1(1)-(2), 7(1)-(2), 14(1)-(3). Date-gated. |
| US 7,379,090 — Nakaoka et al. | May 2008 | "Print portal system on network" (https://portal.unifiedpatents.com/patents/patent/US-[7370090](/patent/7370090)-B2). | §102(e) — network-mediated print job delivery; relevant to claims 14(4)-(6) (receive output data, process, deliver to connected output device). Date-gated. |
| US 6,889,385 — Rakib et al. | May 2005 | "Home network for receiving video-on-demand and other requested programs and services" (https://portal.unifiedpatents.com/patents/patent/US-[6889385](/patent/6889385)-B1). | §102(e) — relevant to the television/display branch of claim 8 and claim 1's externally-connected-controller branch (claim 3/13/17). Date-gated. |
Why these five and not the other ~695: the remainder of the list is overwhelmingly pre-2001 imaging/printing/driver art (raster image processing, page description languages, marking engines, color tables) generated by the parent '541 prosecution. It bears on the specification's disclosure of output-side processing, not on the discovery → attribute-transmission → receive-output-data sequence that actually defines claims 1, 7, and 14.
Self-references to discount. 7,941,541; 7,944,577; 8,332,521; 9,383,956; 9,845,193; 10,642,576; and the Chang-authored 2002/00xxxxx publications are the same inventive entity. They are not §102(a)/(e) "by another" art. They matter for priority, §102(g), and double patenting only — do not count them as prior art against the '066.
Foreign Patent Documents (verbatim, as listed):
CN 1217503 (May 1999) · CN 1488106 (Apr 2004) · CN 100334577 (Aug 2007) · CN 1541370 (May 2010) · CN 101833430 (Sep 2010) · CN 101834892 (Sep 2010) · CN 101825996 (May 2012) · EP 738949 (Feb 2002) · EP 952513 (Feb 2004) · EP 691619 (Feb 2007) · GB 2332764 (Nov 2002) · JP 11316658 (Nov 1999) · WO 0195096 (Dec 2001) · WO 0195097 (Dec 2001) · WO 02084928 (Oct 2002)
I have not verified the content or priority dates of any of these. JP 11316658 (Nov. 1999) and GB 2332764 are the ones I would pull first for a §102(b) attack on claims 7/14, purely because of their dates relative to a Nov. 1, 1999 critical date — but that is a lead, not a finding.
4. Tier 3 — "Other References" (all marked cited by applicant; verbatim titles)
These are the highest-value printed-publication art on the face, and I can cite them verbatim because they appear in the record:
| Reference | Date | Relevance to '066 claims | §102 |
|---|---|---|---|
| Bisdikian et al., "WiSAP: a wireless personal access network for handheld computing devices," IEEE Personal Communications, vol. 5, no. 6, pp. 18-25 | Dec. 1998 | Short-range wireless service to handhelds — claims 1(1), 7(1), 14(1) | §102(b) (before Nov. 1, 1999) |
| Miller, "Mapping Salutation Architecture APIs to Bluetooth Service Discovery Layer," v1.0 | Jul. 1, 1999 | Service discovery over Bluetooth — the "announce/advertise availability so a client can wirelessly discover" element | §102(b) |
| Albrecht et al., "IP Services over Bluetooth: Leading the Way to a New Mobility," IEEE 24th Conf. on Local Computer Networks | Oct. 18-20, 1999 | IP service delivery over Bluetooth — claims 7, 14 | §102(b) |
| Bettstetter et al., "A Comparison of Service Discovery Protocols and Implementation of the Service Location Protocol," 6th Eunice Open European Summer School | Sep. 13-15, 2000 | Comparative service-discovery protocols — claim 14(1) | §102(a) only (after the Nov. 1, 1999 critical date; requires an invention date later than Sept. 2000) |
| Schuyler et al., "Solutions to Sharing Local Printers: LAN Systems Inc., LANSpool," PC Week, vol. 6, no. 39, p. 75 | Oct. 1989 | Shared network printing — background, weak against claims 1/7/14 | §102(b) |
| House et al., "An on-line communication print service for the demanding client," SIGDOC '93, pp. 135-139 | Oct. 1993 | Remote print service | §102(b) |
| Screenshots from Microsoft NT, Figs. 5-7; Screenshots from Microsoft Word 2000, Figs. 1-4 | 1998 / 1999 | Print UI — anticipation of claims 1/7/14 is essentially nil | §102(b) |
| Haynie, "The Zorro III Bus Specification," Rev. 1.0 | Mar. 20, 1991 | Expansion-bus hardware — background only | §102(b) |
Provisional Applications via public pair: 60/224,701, 60/227,878, 601243,654, 60/208,967, 60/220,047, 60/239,320 |
— | Third-party filings; §102(e) candidates if any mature into a patent. Note: "601243,654" is rendered literally in the source; I am not auto-correcting it to 60/243,654. | §102(e), unverified |
5. The §102 framework that governs (and why it decides everything here)
This is the crux, and it is exactly what IPR2021-00713 turned on:
- If a '066 claim is entitled to Nov. 1, 2000 (provisional 60/245,101) or Jan. 19, 2001 (provisional 60/262,764), pre-AIA 35 U.S.C. §102 applies. The pre-AIA §102(b) critical date becomes Nov. 1, 1999 (one year before the earliest supported filing) — which is why nearly everything in Tier 3 is §102(b) art, and why Yamaguchi (post-dating Nov. 1, 2000 but pre-dating Jan. 19, 2001) collapses as prior art the moment Flexiworld perfects the earlier date.
- If a claim is not entitled to that benefit — a live possibility, because '066 is a continuation-in-part (via Ser. No. 16/200,380 → 15/332,432 → 10/053,765), and because claims 14-20 are drafted around subject matter (broadcasting/advertising availability by the controller itself, client device delivers output data for rendering at one or more output devices connected to the controller) that the '101 provisional may not describe — then the critical date shifts to the CIP's Nov. 26, 2018 filing (or Apr. 26, 2019), and AIA §102(a)(1)/(a)(2) governs. That is the only world in which the 2017 Peng reference and 2018-era art become available.
Roku's expert made precisely this argument: "claim 7 of the '066 Patent and its dependent claims are not entitled to claim the benefit of the '101 Provisional," because the provisional "fails to describe systems with a first 'output device' that processes output data for a second 'output device'" (Ex. 1025, ¶¶ 5-6). Under AIA §102, that argument, if accepted, converts the entire Tier 2/Tier 3 date analysis.
6. What I could not verify — explicitly
- Full bibliographic citations for Yamaguchi, Gu, Garfunkel, Ikonen, Kammer, and Peng. I have the surnames and the claim mapping from the PTAB grounds table and demonstratives, but not the patent/publication numbers, filing dates, or assignees. Fabricating these would be worse than omitting them.
- The operative disposition of the IPR2021-00713 Final Written Decision (which claims, if any, were held unpatentable).
- Filing/priority dates for the individual face-cited references. The citation list supplies issue dates only. My §102 assignments for Tier 2 items labeled "§102(e) — date-gated" are conditional on priority dates I have not pulled.
- The identity of the IPR "Kammer" and "Peng" exhibits relative to face-cited US 7,356,347 and US 2017/0318115 A1 — plausible matches, unverified.
- The content of the 15 foreign documents. Presented verbatim as listed, uncharacterized.
- I did not query USPTO PatentCenter/PAIR directly. Google Patents and uspto.report are my rendering sources; the litigation/docket material comes from Docket Alarm, CourtListener, Justia, and the Stanford NPE database.
Practical next step to complete the per-reference analysis you asked for: pull the IPR2021-00713 Petition (Paper 2) and Exhibits 1001-1037 from the PTAB record, plus the '101 provisional (60/245,101) and the '764 provisional (60/262,764). Those three documents resolve the priority date, and the priority date resolves which of ~1,000 listed references is even eligible as §102 art. Everything else is downstream of that.
Generated 9/14/2026, 12:48:02 PM
Obviousness
Combinations of prior art that suggest the claimed invention would have been obvious under 35 U.S.C. § 103.
I'll ground this analysis in the actual prior-art record from the IPR and related proceedings before constructing the §103 combinations.
Let me pin down the reference identities and the eventual PTAB outcome, since those anchor any §103 analysis.
Obviousness Analysis under 35 U.S.C. § 103
U.S. Patent No. 10,740,066 B2 ("the '066 patent")
0. Scope note — what prior art I am actually working from
Important disclosure: the prompt directs me to "use the results from the Prior Art section of this page," but no separately labeled Prior Art section was transmitted in either the source patent text or the previously generated sections. Rather than manufacture one, I reconstructed the prior-art record from the authoritative materials available to me:
- The grounds of invalidity as actually pleaded and instituted in Roku, Inc. v. Flexiworld Technologies, Inc., IPR2021-00713 (the IPR on this exact patent) — Patent Owner's Demonstratives, Ex. 2042 and Petitioner's Demonstratives, Ex. 1037.
- The Bhattacharjee reply declaration (Ex. 1025), which discusses the references element-by-element — link.
- The Lexmark IPR record on sibling Flexiworld patent 7,609,402, which independently identifies two of the same references by patent number — Flexiworld Preliminary Response.
- The '066 specification's own Background and Detail, which under the admitted-prior-art doctrine is usable as prior art.
I was unable to verify the bibliographic identity of every reference (see §9). Where I could not, I say so rather than guess. Claim text is taken from the previously generated plain-language claim summary in this analysis, which I treat as authoritative for cross-reference.
1. The threshold question that controls everything: the critical date
Under § 103 the first task is fixing the effective filing date, because it determines the entire prior-art set.
| Candidate date | Basis | Consequence |
|---|---|---|
| Nov. 1, 2000 | Provisional 60/245,101, in the § 120 chain through Ser. No. 10/016,223 | Narrowest prior-art window; this is the date Flexiworld shifted to mid-litigation |
| Jan. 19, 2001 | Provisional 60/262,764, the date Flexiworld originally pleaded | Broader prior-art window |
This is not academic. Per Ex. 1025 ¶ 5, Roku's expert states that "at the time that I provided my original declaration, there was no dispute that Yamaguchi was prior art" because Flexiworld had pleaded only the Jan. 19, 2001 date; Flexiworld then changed position after the Petition was filed to claim the Nov. 1, 2000 provisional. The Board's Institution Decision then "correctly found Ground 1 insufficient because Yamaguchi is not prior art."
The necessary inference is that Yamaguchi's effective date falls somewhere after Nov. 1, 2000 but (per Roku's position) before Jan. 19, 2001 — a roughly 11-week window. I could not retrieve US 7,355,732's actual filing/priority date to confirm the window's boundaries, and I flag that as an unresolved gap.
Analytical consequence: the single highest-leverage § 103 issue for this patent is not any reference's technical content — it is whether claim 7 (and its dependents) is entitled to the '101 provisional's Nov. 1, 2000 benefit at all. Roku argued it is not, on a § 112 written-description theory: the '101 provisional allegedly "fails to describe systems with a first 'output device' that processes output data for a second 'output device'" (Ex. 1025 ¶¶ 5–6). If that argument prevails, the effective date moves to Jan. 19, 2001, Yamaguchi is restored as prior art, and Grounds 1/1A become live. The same priority-shifting maneuver was run by Unified against the sibling '257 patent, where the Board instituted on all challenged claims (Unified Patents, Nov. 8, 2022).
Note the oddity I will not auto-correct: Ex. 1025 refers to the provisional as "U.S. Provisional Application No. 60/246,101," while the patent's cross-reference section (per the earlier bibliographic section of this analysis) identifies the Nov. 1, 2000 provisional as 60/245,101. These may be a transcription error in one source, or two different provisionals. I cannot resolve it and do not correct either number.
2. Level of ordinary skill in the art (POSITA)
Neither party appears to have disputed the POSITA definition in the '713 record. Based on the field and the '066 specification, a defensible construction is:
A person with a bachelor's degree in electrical engineering, computer science, or equivalent, and at least two years of experience in one or more of: (a) wireless data communications protocol stacks (IEEE 802.11, Bluetooth, IrDA); (b) peripheral device driver architecture and page-description/output languages; or (c) print/network output device management.
Both experts in the record fit this profile: Dr. Samrat Bhattacharjee for Roku and Dr. Todor Cooklev for Flexiworld. Dr. Cooklev's field (wireless standards) is a reasonable proxy in the other direction — the field is wireless-protocol-centric, not printing-centric, which matters because the references are predominantly wireless-networking references.
3. The prior art references
| Ref. | Identity | Status of my verification | What it discloses (as used in the record) |
|---|---|---|---|
| Yamaguchi | U.S. Patent No. 7,355,732 B2 | Number corroborated in the Lexmark/'402 exhibit list ("EX1006 — U.S. Patent No. 7,355,732 B2 ('Yamaguchi')"); effective date not verified | Coin-operated paid printing system. An interface box is wire-connected to a printer. User inserts coins in a coin rack → system displays a random number on an LED → only then an RF connection is established with the user's wireless device → user inputs the random number to authorize access → document wirelessly transmitted → printed. Discloses: RF receipt of document data; a device-side authentication step using a user-entered identifier; payment processing; a controller physically separate from the print engine. |
| Gu | UPnP-architecture reference (Gu) |
Number NOT verified | Described in Ex. 1025 as teaching: Description URL "[t]he URL returned from a Controlled Device or Bridge in response to any UPnP SSDP query"; devices provide description URLs in response to SSDP searches; "[t]he result of an SSDP search is always a URL that points to the Description Document"; "Both the Announce and Discovery packets also contain a link or a URL to an XML file" (Gu 51:32–36); the description document contains modelName, modelNumber, serialNumber, UDN, friendlyName (Gu 27:26–28:33, Fig. 15); the description document "provides the information necessary to identify, describe, connect and control" a controlled device (Gu 21:28–31). |
| Kammer | U.S. Patent No. 6,950,645 B1 — "Power-conserving intuitive device discovery technique in a Bluetooth environment" | Number corroborated in Flexiworld's own Lexmark Preliminary Response ("U.S. Patent No. 6,950,645 ('Kammer')") | Bluetooth device discovery; receipt of a device's "user-friendly name" to enable a user to select a device for connection. |
| Ikonen | Wireless output/discovery reference (Ikonen) |
Number NOT verified | A client-inquiry → device-response model. Critically, the Board held at institution that Ikonen's "inquiry response" is not a "broadcast or advertisement of availability." In the companion IPR2021-00714, Ikonen was combined additionally with Beck. |
| Garfunkel | Software download/installation reference | Number NOT verified; my inference of its subject matter is from its placement against claim 11 (the software-download/install limitation) in Grounds 1A/2A | Assigned in the Petition to the element concerning obtaining/installing application software at the client. |
| Peng | Reference used only in Ground 3A against claim 19 | Number NOT verified | Element within the Ikonen+Kammer chain. |
| Bluetooth Specification, Vol. 2 (Generic Access Profile) | Standard | Corroborated as a Roku exhibit (Appendix to Ex. 1025) | Inquiry / inquiry-scan discovery and the friendly-name device attribute. |
The formulations actually pleaded (Ex. 2042):
| Ground | Claims | Reference combination |
|---|---|---|
| 1 | 7, 8, 10 | Yamaguchi + Gu |
| 1A | 11 | Yamaguchi + Gu + Garfunkel |
| 2 | 7, 8, 10 | Ikonen + Gu |
| 2A | 11 | Ikonen + Gu + Garfunkel |
| 3 | 14, 15, 17 | Ikonen + Kammer |
| 3A | 19 | Ikonen + Kammer + Peng |
4. The strongest § 103 material is inside the patent: its own admissions
Before reaching the reference combinations, note that the '066 specification concedes the core paradigm. From the specification's Discovery Process discussion (§ 5, step 502):
*"In one scenario, information apparatus 100 broadcasts a service request… Service devices, such as output device 140 equipped with output controller 120, 'listen to' such signals, 'read' the request, 'see' whether they can provide requested service, and respond… Alternatively or in combination, all service devices can periodically or continuously announce or advertise the services they provide. Information apparatus 100 'listens to' such announcements and identifies the service it needs."* (col. 21:7–17, quoted at Ex. 2042)
That sentence is, on its face, claim 1 element (1) and claim 14 element (1) ("broadcasting or advertising… availability… to enable a client device… to wirelessly discover the wireless output controller"). Flexiworld itself relied on that passage as evidence that "advertising" has a settled meaning — which cuts both ways: an admitted, prior-art practice cannot supply novelty.
The same specification also:
- names "Bluetooth, HAVi, Jini, Salutation, Service Location Protocol, and Universal Plug-and-play" as "applicable protocols" for the discovery process (i.e., the § 103 motivation to combine an announce/discover protocol with an output device is supplied by the patent itself);
- names "IrDA, home RF, Bluetooth, IEEE 802.11, HiperLan2" as the wireless options;
- admits that output controllers "may store… device or printer driver, software components, device dependent data or parameters, user interfaces" for upload — the very "device attributes" and download functionality at issue;
- admits "Management tools such as queuing and spooling of print jobs, quality of service, etc. may be provided by the output controller" — i.e., claim 1 element (6) (storing/buffering/queuing/spooling at the output controller) is admitted art;
- admits "Security procedures may be implemented by software, hardware or a combination… in various steps and stages of communication" — i.e., claim 1 element (4) (authentication) is admitted art.
Under In re Nomiya / Riverwood Int'l v. R.A. Jones line of authority, these admissions are prior art for § 103 purposes without further evidentiary authentication. A well-constructed obviousness case should lead with them.
5. Claim-by-claim mapping and the combinations
5.1 Independent claim 1 — "wireless output controller" (apparatus)
Ordered elements and where each is met:
| # | Claim 1 limitation | Primary teaching | Corroboration |
|---|---|---|---|
| 1 | Announce/advertise availability over the air so an apparatus within limited physical distance can discover it for short-range communication | Gu (SSDP Announce packets) or Kammer (Bluetooth inquiry/discovery) — and the '066 spec's own admitted "announce or advertise the services they provide" | Bluetooth Generic Access Profile |
| 2 | Wirelessly transmit device-dependent attributes, triggered by having been discovered | Gu (description document: modelName, modelNumber, serialNumber, UDN, friendlyName) | Kammer's "user-friendly name" |
| 3 | Receive information or a service request back from the apparatus after (2) | Yamaguchi (receipt of document/print request over RF); Ikonen (inquiry/response) | Gu (control point interaction) |
| 4 | Run an authentication/security procedure — detecting identification, address, security info, password, PIN, or biometric | Yamaguchi (random number displayed on LED and entered by the user as the authorization key; colloquially a device-issued PIN); additionally the '066 spec's admission that security procedures are conventional | Bhattacharjee Ex. 1025 ¶ 52: "Yamaguchi discloses a security procedure whereby a user has to enter a valid ID number to be authorized and allowed to use the interface box." |
| 5 | Only after successful authentication, wirelessly receive output data predicated on having sent attributes in (2) | Yamaguchi (document data received only after the random number is accepted) + Gu (the description/document exchange preceding service) | — |
| 6 | Provide output-management functions — storing, buffering, queuing, or spooling — at the controller | Admitted art in the '066 spec ("queuing and spooling of print jobs… may be provided by the output controller"); also conventional print-server practice recited in the Background | — |
| 7 | Closing wherein: service provided based on both discovery and the authentication procedure | Combination itself | — |
Assessment: claim 1 is the hardest of the three independents, chiefly because of the ordering: attributes out → request in → authenticate → job data in. Yamaguchi inverts the economic logic (coins first, then connection), so the ordering is not squarely met by Yamaguchi alone, and Gu does not authenticate. But the gap is one of sequencing, not of substance — the "authenticate-then-deliver" ordering is the oldest pattern in the paid-output art, and Yamaguchi itself performs authentication before releasing the document. Combination: Yamaguchi + Gu (+ Kammer), with the specification's admissions supplying elements 4 and 6.
5.2 Independent claim 7 — "wireless output device" (apparatus; no authentication)
| # | Claim 7 limitation | Teaching |
|---|---|---|
| 1 | Announce/advertise availability for discovery based on limited physical distance for short-range wireless | Gu / Kammer / Bluetooth GAP; admitted in spec |
| 2 | Wirelessly transmit stored device attributes over an RF channel to the discovering apparatus | Gu (description document) / Kammer (friendly name) |
| 3 | Wirelessly receive output data (digital content) over that RF channel, subsequent to (2) | Yamaguchi (wireless receipt of electronic document data) |
| 4 | Process at least part of the output data (decode, convert, scale, interpret) into a form/format/instruction/language acceptable for output by the device | The output device's own output controller; Kammer/Gu supply the surrounding architecture — this is the element Roku flagged as spanning two output devices (Ex. 1025 ¶ 6), which the prior art meets only if the POSITA reads the "output controller" and the "output device" as distinct structures, as the '066 specification's own FIG. 4A/4D cascaded-box embodiments do |
Assessment: claim 7 is the most exposed independent claim. It is effectively discovery + attribute transmission + wireless download + rendering-side processing — the standard architecture of UPnP-over-802.11 and Bluetooth-capable peripherals as of mid-2000. Any of (Gu + Kammer), (Gu + Yamaguchi), or (Ikonen + Gu) reads on it, subject to the priority issue in §1. Note also that claim 7 carries no authentication limitation, which removes the one element Flexiworld has been able to defend successfully elsewhere.
5.3 Independent claim 14 — "wireless output controller" (method in firmware)
| # | Claim 14 limitation | Teaching |
|---|---|---|
| 1 | Broadcast/advertise availability so a client can wirelessly discover it, based at least in part on short-range wireless communication | Gu (SSDP Announce) or Kammer (Bluetooth); admitted in spec. This is the element the Board found Ikonen alone does not disclose. |
| 2 | Establish a wireless communication link with the discovering client | Yamaguchi (RF link established after coin insertion); Kammer |
| 3 | Transmit device information about the controller over the established link | Gu (description document) |
| 4 | Receive output data from the client, subsequent to (3), for rendering at output device(s) connected to the controller | Yamaguchi (interface box connected to printer 106) |
| 5 | Process/decode/interpret the received output data | Controller's processor |
| 6 | Deliver processed data to the connected output device(s) for rendering | Yamaguchi |
| 7 | Wherein closure: service subsequent to discovery and transmission of device information | Combination itself |
Assessment: claim 14's vulnerability is concentrated in element (1). Ikonen + Kammer was the pleaded combination, and the Board's institution decision held it insufficient — because Ikonen's response to a client inquiry is not an advertisement. Flexiworld's own demonstrative frames this as a win on the "advertising" term. But note the asymmetry: Ikonen + Gu (Ground 2) was instituted, because Gu supplies exactly the device-initiated Announce that Ikonen lacks. Claim 14 is therefore strongest when the advertiser is not Ikonen but Gu, Kammer/Bluetooth GAP, or the specification's own admitted practice.
5.4 Dependent claims
| Claim | Additional limitation | § 103 assessment |
|---|---|---|
| 3, 13, 17 | External controller wired to a television | Yamaguchi's interface box is wired to the printer — direct read; and the '066 spec's FIG. 4A/4D describe the same cascade |
| 4 | IEEE 802.11 or Bluetooth chips/chipsets | Admitted in spec; Kammer (Bluetooth) and generic 802.11 NIC art |
| 5 | Direct short-range link or WLAN | Bluetooth GAP / 802.11 ad-hoc; Kammer |
| 6, 11 | Downloading/installing application software from a server, managed by embedded OS | This is the element mapped to Garfunkel in Grounds 1A/2A, and it is also admitted in the '066 spec (output controllers store drivers/components and upload them; output controllers "may contain an embedded operating system") |
| 8 | Device-type ↔ content-type mapping (TV/display/projector↔video; printer↔image/document; audio↔audio) | Roku's expert materials in the companion '064 IPR expressly cite claim element 1[g]'s "video content, audio content, or document content" — mapping content type to output device type is a routine design choice with no unexpected result; supported by Gu's device-type description fields and Yamaguchi's document data. Also, the '066 spec's own list of output devices. |
| 12, 18 | Device attributes include capability, duplex, color, language, or format information | Gu (modelName, modelNumber, and UPnP device/service description fields); printer capability attributes are the standard content of PDL-device description |
| 15, 17, 19 | (as pleaded: 15/17 with Ikonen+Kammer; 19 with +Peng) | Grounds 3/3A |
General note on the dependent claims: where a dependent claim adds only a device-type, protocol-type, or attribute-field limitation, the § 103 case is materially stronger than for the independents, because each is a selection from a small, enumerated, predictable set that the specification itself recites (Bluetooth/802.11/IrDA; printer/TV/projector/audio; duplex/color/language). KSR squarely covers "a combination of familiar elements according to known methods… when it does no more than yield predictable results."
6. Motivation to combine
6.1 Why a POSITA would combine Gu's discovery/description framework with a wireless output device
The strongest rationales, in descending strength:
The patent's own admission supplies the motivation. The '066 specification names Universal Plug-and-play as an "applicable protocol" for its discovery process and explicitly describes the device-side "announce or advertise" model. A POSITA reading the field in 2000 had UPnP (published model/architecture June 2000), Jini, SLP (RFC 2608, June 1999), HAVi, and Bluetooth GAP all offering device announcement. Combining an announce/discover layer with a wireless output device was not merely obvious — it was the stated design goal of the field.
Improving a similar device in the same way (KSR). Gu's SSDP Announce + description document and Kammer's Bluetooth discovery solve the shared problem of both Yamaguchi and Ikonen: a roaming user who does not know what devices are nearby. Substituting a discoverable, self-describing device for a coin-rack-selectable device is the use of a known technique to improve a similar device in the same way.
Predictable, compatible, and market-driven. The art is uniform: all of Gu, Kammer, Ikonen, and the '066 spec address wireless device discovery for service provision on a LAN/PAN. Combining them yields no unexpected result — it yields exactly the interoperability each was designed for.
Design incentive / cost. Roku's expert established that adding UPnP to 802.11 was a rational choice precisely because 802.11 adoption outpaced Bluetooth ("when Windows XP launched in October 2001, it supported 802.11, but not Bluetooth"; Bluetooth cards cost roughly "twice what you'd pay for wireless Ethernet"). This is a design-incentive rationale under KSR.
6.2 The counterarguments (Flexiworld's position) and why they are contestable
| Flexiworld argument | Source | Rebuttal |
|---|---|---|
| Yamaguchi's user has already selected the device by inserting coins — there is no need for a discovery/description phase, so the combination is "nonsensical" | Flexiworld Preliminary Response ('402 IPR) | The motivation is not that Yamaguchi's own user needs discovery; it is that a device-agnostic roaming user needs it. The claims are directed to the device side and are not limited to coin-operated systems. Motivating a modification by a different class of user in the same field is permissible. |
| Gu retrieves the description document in the "description" step, not the "discovery" step — so Gu does not teach providing device attributes as part of discovery | POR, as summarized in Ex. 1025 ¶ 45 | Ex. 1025 ¶¶ 45–46 is a direct answer: Gu at 11:30–35, 13:34–43, 16:63–65, 19:4–8, and 51:32–36 tie the discovery result to the description URL, and Gu's 48:37–42 frames "description" as an extension of "discovery." A POSITA would read the two as a continuous sequence. |
| UPnP has security issues — a disincentive to combine Gu | Petitioner's Demonstratives (Ex. 1037) list this as a PO response under Ground 2 | A generic security concern does not teach away; the '066 spec itself concedes security procedures are conventional and implementable "in various steps." Moreover, the combination is what is challenged, and the authentication element (where claimed) is separately supplied by Yamaguchi or by admitted art. |
| Bluetooth adoption lagged 802.11 | Roku's own Ex. 1028 § 43 | This cuts for obviousness on the 802.11 branch of claims 4/5, and the claims recite "IEEE 802.11 or Bluetooth" — so a POSITA's preference for 802.11 still satisfies the claim. |
| Ikonen's response is not an "advertisement" | Institution Decision; Ex. 2042 | Correct as to Ikonen alone — but the pleaded Ground relied on Ikonen + Kammer, and the Board found that combination insufficient on this element too; whereas Ikonen + Gu was instituted because Gu supplies Announce. The lesson for any renewed challenge is to source the "advertise" limitation from Gu, Kammer/GAP, or the specification's admission — not from Ikonen. |
6.3 The priority argument as a motivation-independent path
Separately from any technical argument, if the '101 provisional lacks § 112 support for (i) a first output device that processes data for a second output device and (ii) an output controller that announces its own availability (the two issues Roku framed for the oral hearing), then:
- claim 7 and its dependents revert to Jan. 19, 2001;
- Yamaguchi becomes prior art;
- and Grounds 1 + 1A (Yamaguchi + Gu [+ Garfunkel]) become available, not merely Ground 2.
That is a purely legal claim-construction/priority move, and it is the highest-value lever in this file.
7. Objective indicia / secondary considerations
Flexiworld has asserted, in the sibling '402 IPR, that it "is a pioneer" with "over 80 United States patents," having been "[v]oted the best early stage company in the Pacific Northwest in 2002" and having its business plan ranked top-2 among the "Ten Best" in 2002 and 2003. Assessment:
- Company-level awards lack nexus to the challenged claims. They are evidence about Flexiworld as an enterprise, not about the '066 claims. Under the framework applied in Ancora Techs. v. Roku, 2025 WL ___ (Fed. Cir. June 16, 2025), the Federal Circuit relaxed the license-evidence nexus standard — holding that "licenses to the challenged patent do not require a nexus to the specific claims at issue" and that the licensed patent need not be the sole motivation for the license — but retained a nexus requirement for industry praise. Flexiworld's press/award evidence is industry commentary about the company, so the Ancora relaxation does not reach it.
- Licenses/settlements. If Flexiworld points to the Epson dismissal (C.D. Cal. 8:21-cv-00807, closed Feb. 2, 2022) or the Sony dismissal (E.D. Tex. 2:23-cv-00616, dismissed with prejudice May 29, 2025), the Ancora holding would counsel giving such licenses significant weight if they (a) specifically identify the '066 patent and (b) involve royalties substantially exceeding litigation costs. Based on what I retrieved, the dismissal terms are not public, so I cannot assess this. Caution: Ancora concerned a different patent (US 6,411,941, owned by Ancora Technologies and asserted against Roku/Nintendo/VIZIO) — I cite it for the legal standard only, not as authority about the '066 patent.
- No evidence found of copying, unexpected results, or a recognized long-felt but unmet need tied to the claims.
8. Bottom line
Where the § 103 case is strong:
- Dependent claims 3–6, 8, 11–13, 17, 18 — each adds a device-type, protocol-type, or attribute-field limitation drawn from a short, enumerated, predictable list (Bluetooth/802.11; printer/display/TV/projector/audio; duplex/color/language). KSR disposes of these almost summarily.
- Claim 7 — no authentication; the discovery → attribute-transmission → wireless-download → render-side-processing sequence is precisely the UPnP-over-802.11 / Bluetooth-GAP architecture available in mid-2000. Gu + Kammer, or Gu + Yamaguchi, or Ikonen + Gu (the instituted ground) all read on it, subject to the priority question.
- Claims reciting the "advertise availability" step (1, 14) — supported by Gu's SSDP Announce, Kammer's Bluetooth discovery, the Bluetooth GAP specification, and — decisively — the '066 specification's own admission that "all service devices can periodically or continuously announce or advertise the services they provide."
Where the § 103 case is weak / genuinely contested:
- Claim 1's ordered sequence — attributes out → request in → authenticate → job data in — is not cleanly met by any single pleaded reference. Yamaguchi authenticates, but with a coin-first economic logic that inverts the claimed order. This is a real, if bridgeable, gap.
- The "advertising" limitation against Ikonen. The Board held Ikonen's inquiry response ≠ an advertisement. That holding is a live constraint; any renewed challenge must not source that element from Ikonen.
- Claim 7's two-output-device reading. If claim 7 is construed to require a first output device processing data for a second output device, the pleaded art's coverage of that element (element 7[j]) is contested, and it is simultaneously the linchpin of the priority attack — the same construction that broadens the claim also severs it from the '101 provisional. This is an unavoidable strategic tension for the patent owner.
What this analysis cannot conclude: I did not verify the Final Written Decision in IPR2021-00713, so I cannot state whether any claim of the '066 patent was ultimately held unpatentable, and my Institution-stage conclusions above are drawn from the parties' demonstratives characterizing that decision, not from the decision itself. Any determination that the claims are invalid on these grounds would overstate the record.
9. New data conflicts to flag (in addition to those flagged in the earlier sections)
Legal-status label changed between fetches. The earlier section of this analysis reported Google Patents showing "Expired – Fee Related" with a 2021-11-01 anticipated expiration. The live fetch now returns "Expired - Lifetime" for the same record. I do not resolve this and do not auto-correct either label.
An unexplained maintenance-fee lapse event. The Google Patents legal-events table for US10740066B2 shows "Lapsed due to failure to pay maintenance fee — Effective date: 20221120" (code
FP, under 37 CFR 1.362). This is internally anomalous: the patent granted 2020-08-11, so the first maintenance fee (3.5 years) would not come due until ~2024-02-11 — and if the term instead expired 2021-11-01 (20 years from the Nov. 1, 2001 parent), no maintenance fee would ever come due at all. A 2022-11-20 lapse fits neither theory. I record the event literally and flag it as unreconciled; it may be aggregated family data rather than an event specific to this patent.Unverified reference identities. I confirmed by patent number only Yamaguchi (US 7,355,732) and Kammer (US 6,950,645). I could not verify the patent numbers, dates, or assignees of Gu, Ikonen, Garfunkel, or Peng, and I inferred Garfunkel's and Peng's subject matter solely from their claim assignments in the pleaded grounds. Treat those four as placeholder-verified only.
Provisional number conflict — 60/246,101 (Ex. 1025) vs. 60/245,101 (patent cross-reference). Both recorded as-is; neither corrected.
10. Sources
- US10740066B2 — Google Patents (full text)
- Patent Owner's Demonstratives, Ex. 2042, IPR2021-00713/-00714
- Petitioner Roku's Demonstratives, Ex. 1037
- Reply Declaration of Samrat Bhattacharjee, Ex. 1025
- Bhattacharjee Reply Declaration (companion '064 IPR), Ex. 1028
- IPR2021-00713/-00714 Oral Hearing Transcript, July 19, 2022
- Flexiworld Preliminary Response, Lexmark IPR on US 7,609,402 (identifies Yamaguchi = US 7,355,732 and Kammer = US 6,950,645)
- Lexmark petition exhibit list, Ex. 1006 = Yamaguchi
- Unified Patents record for US 10,740,066
- Unified Patents — Flexiworld '257 patent IPR instituted on all challenged claims (Nov. 8, 2022)
- Ancora Technologies, Inc. v. Roku, Inc. (Fed. Cir. June 16, 2025) — secondary-considerations nexus standard
Generated 9/14/2026, 12:48:30 PM
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 Wireless Technologies
- US 8989064I'll search for the patent details and any related litigation. Let me get the claim text and check for any 2026 CAFC activity. Let me look for the full claim set of the patent. US Patent 8,989,064 — Summary Source note: The authoritative…
- US 7797367I'll search for the specific patent number as requested. Let me search for the specific claims and any litigation involving this exact patent number. Let me check specifically for any Federal Circuit (CAFC) activity on this exact patent…
- US RE44904I'll search for authoritative information on this patent number and any 2026 litigation activity. Let me dig into litigation and any 2026 appellate activity. Let me check for PTAB proceedings and any 2026 appellate activity. US RE44,904 E…
- US 9219982I'll search for authoritative information on this specific patent number, including litigation/docket activity. Let me check specifically for any Federal Circuit (CAFC) 2026 appeal activity involving this patent. US Patent 9,219,982 —…
- US 6370135I'll verify the patent's bibliographic data and check for any 2026 litigation, then summarize. The CAFC search returned nothing. Let me run a couple of targeted follow-ups on litigation/docket history. US Patent 6,370,135 — Analyst Summary…
- US 6424635I'll verify the current status of US 6,424,635 through targeted searches, then summarize. US 6,424,635 — Verification note first I searched for this exact number (6424635 / 6,424,635) and found no USPTO litigation record, no CAFC 2026…
- US 6304561I'll search for information about US Patent 6,304,561, including any USPTO records and CAFC docket activity. Let me do a couple more targeted searches to check for any CAFC or district-court litigation involving this specific patent…
- US 6466559Based on the authoritative patent text (Google Patents, fetched 2026-09-09) and corroborating search results (Justia/patents.justia.com confirming grant data), here is the summary. Searches of CAFC 2026 dockets and litigation databases…
This patent in court (2)
2 tracked lawsuits name US 10740066.