US 10469614

I'll search for this specific patent number and related docket information.

Let me search for the specific claims and litigation/Court of Appeals docket information.

Let me get the actual claim text for this specific patent.

US 10,469,614 B2 — Analyst Summary

A note on scope up front: The authoritative full text you supplied covers the front matter and the long background/specification of this patent but is truncated before the claims. I was able to retrieve the bibliographic data directly and the claim-1 subject matter indirectly through the PTAB/IPR record and related litigation briefing, but I could not retrieve the verbatim issued claim text of the '614 patent. Where I describe claim scope below, I flag it as derived from the IPR petition summary rather than from the claim language itself.

1. Bibliographic data (high confidence — matches the authoritative text)

⚠️ Identifier discrepancy (not auto-corrected): one third-party database page (ai-lab.exparte.com, IPR2020-01506 case page) lists the '614 title as "System and method for exchanging information over a computer network." Every primary/authoritative source (the Google Patents family record you supplied, Espacenet, and the EPO Board of Appeal decision) uses "System and method for improving Internet communication by using intermediate nodes." I treat the former as a database error, but I am reporting it literally since I cannot verify its origin.

2. Abstract

I do not have the '614 patent's own verbatim abstract. The abstract that repeatedly attaches to this family describes: "A method for fetching a content from a web server to a client device … using tunnel devices serving as intermediate devices. The client device accesses an acceleration server to receive a list of available tunnel devices. The requested content is partitioned into slices, and the client device sends a request for the slices to the available tunnel devices…" (see US 10,986,208 B2, a later continuation in the same family: https://patentimages.storage.googleapis.com/45/fa/d5/c7b503954ae14b/US10986208.pdf).

Uncertainty flag: Because the '614 patent is a separate-filing continuation in the same specification family, its issued abstract is likely substantively similar, but the "slicing"/"acceleration server" language may belong to a different continuation's claim set. Treat that abstract text as approximate for '614.

3. Independent claims — plain-language overview

What is well grounded: Per the PTAB petition in IPR2020-01506 (Code200, UAB; Teso LT, UAB; Metacluster LT, UAB; Oxysales, UAB v. Luminati Networks Ltd., filed Sept. 4, 2020), the challenged claims were 1–2, 4–13, 15–20, 22–23, 25–26, and 28–29 — so the patent has at least 29 claims, and claim 1 is an independent claim. The petition's description of the invention, and the EPO Board of Appeal's parallel summary of a family member's claim 1, both point to the same core.

Claim 1 (independent — method), as characterized in the IPR record:
A method in which a client device acts as an intermediary/proxy rather than an end-user. The client device determines its own resource availability (e.g., CPU, memory, bandwidth utilization) against a criterion/threshold, and thereby exists in either a first state (available) or a second state (unavailable). When in the first state, the client device:

• receives a request from a first server,
• performs the task of fetching content from a separate, third-party web server over the Internet, and
• returns the fetched content to the first server.

(Source: https://ai-lab.exparte.com/case/ptab/IPR2020-01506/doc/1011 — the petition mapped "client device" onto Mithyantha's appliance 200′ and "first server" onto appliance 200, and alternatively mapped them onto MorphMix tunnel nodes.)

Dependent claims (per the same record) add limitations such as TCP/IP-based communication, status/monitor signaling, and HTTP-based content retrieval.

Other independent claims: Given the claim-numbering gaps in the challenge (3, 14, 21, 24, 27 unchallenged), it is plausible the patent contains additional independent claims (e.g., a system/apparatus claim or a server-side method claim), but I could not verify the number or text of any independent claim other than claim 1. I am not going to guess at their wording.

Terminology note (relevant to claim scope): Courts and the PTAB construed the '614 terms "client device" as "a device that is operating in the role of a client by requesting services, functionalities, or resources from other devices" and "first server" as "a server that is not the client device." Bright Data argued for a hardware-based construction (consumer computer vs. commercial server) and lost that argument, a dispute that ultimately drove the Federal Circuit appeals discussed below.

4. USPTO / PTAB / court docket status

PTAB (USPTO):

• IPR2020-01506 — challenged the '614 patent. Google Patents' family record lists it as "filed (Not Instituted – Procedural)." So the challenge to this specific patent did not proceed to a final written decision on the merits.
• Note: The other IPRs in Bright Data's broader campaign (IPR2021-01492/01493, IPR2022-00103, -00135, -00138, -00353, -00861, -00862, -00915, -00916) concerned related patents, not the '614.

District court (E.D. Tex.): The '614 patent was one of the patents-in-suit in Bright Data Ltd. f/k/a Luminati Networks Ltd. v. Teso LT, UAB, et al., No. 2:19-cv-00395 (E.D. Tex.) — where a jury verdict found the asserted patents valid and infringed — and appears in related E.D. Tex. filings 2:19-cv-00397 and 2:19-cv-00414 catalogued on the patent's Google Patents page. (Sources: https://portal.unifiedpatents.com/litigation/Texas%20Eastern%20District%20Court/case/2%3A19-cv-00395; PTAB petition excerpt at ptacts.uspto.gov petition 1550342.)

CAFC 2026 dockets: I did not locate a 2026 Federal Circuit docket captioned to the '614 patent specifically. The 2025–2026 Federal Circuit activity in this corporate family is:

• Bright Data Ltd. v. Code200, UAB, et al., Nos. 2023-2144, -2145, -2146, -2147, -2414, -2415, -2442, -2443 (Fed. Cir.) — consolidated appeals from IPRs on related patents; opinion Aug. 1, 2025 (affirming role-based constructions of "client device" / "second server"); panel rehearing and rehearing en banc denied Oct. 1, 2025.
• Bright Data Ltd. v. Code200, UAB — petition for certiorari filed at the Supreme Court (No. 25-779, docketed Dec. 30, 2025), raising prosecution-disclaimer / claim-construction issues.
• A 2026 E.D. Tex. trial setting exists in Bright Data Ltd. v. Oxylabs, UAB, No. 2:23-cv-00171-JRG-RSP (jury selection 7/17/2026), but I cannot confirm the '614 patent is asserted there.

I cannot state with authority that any 2026 CAFC docket is tied to patent 10,469,614. If you need that verified, the reliable route is the CAFC's PACER docket search restricted to "Bright Data Ltd." as appellant with the '614 patent number cross-checked against the notice of appeal.

5. Summary of uncertainty

I'll research this thoroughly. Let me start with the litigation database sources and specific case numbers mentioned in the patent record.

Let me dig deeper into each specific case and search for additional litigation including any later cases.

Litigation Involving U.S. Patent No. 10,469,614 ("the '614 patent")

Patent identification (as literally recorded): US 10,469,614 B2 — "System and method for improving Internet communication by using intermediate nodes." Inventors: Derry Shribman; Ofer Vilenski. Application 16/214,433, filed 2018-12-10, granted 2019-11-05. Original assignee Luminati Networks Ltd.; current assignee Bright Data Ltd. (name change recorded 2021-03-31). Priority date listed as 2013-08-28. Anticipated expiration listed as 2034-08-26.

The '614 patent was asserted in three co-pending U.S. district court actions in the Eastern District of Texas (two of which were consolidated), plus one PTAB inter partes review petition. Notably, the Google Patents record for this patent itself lists exactly these: cases 2:19-cv-00395, 2:19-cv-00397, and 2:19-cv-00414, and PTAB case IPR2020-01506 ("Not Instituted – Procedural").

1. Bright Data Ltd. (f/k/a Luminati Networks Ltd.) v. Teso LT, UAB; Oxysales, UAB; Metacluster LT, UAB

Key events / outcome:

• Defendants' Rule 12(b)(6) motion asserting the patents were abstract under 35 U.S.C. § 101 was denied (Dkt. 85), with the court noting claim construction would aid the analysis.
• Claim Construction Opinion and Order entered 12/07/2020 (Dkt. 191). The court construed, e.g., "client device" (in the '614 patent) and "first server" as "server that is not the client device."
• Teso re-raised § 101 eligibility; the court's order of 02/16/2021 (Dkt. 303) analyzed the asserted independent claims of the '319, '510, and '614 patents and found the claims were not directed to an abstract idea (rejecting the Alice challenge).
• Jury verdict returned 11/05/2021 (Dkt. 516) in favor of Bright Data, including findings of infringement by Oxylabs and an award of lost profits. (Verdict form posed Questions 1–4 on infringement, invalidity, willfulness, and lost profits.)
• Case proceeded to judgment post-trial; the related Tefincom action was later stayed pending "any appeal and entry of a final and non-appealable judgment" in this 395 case (see Case 3).

Note on status: The docket and PTAB filings I located confirm the trial verdict and judgment activity, but I did not find a confirmed record of the final appellate disposition (any Federal Circuit appeal outcome) in the sources retrieved. I am therefore flagging the appellate/post-judgment final outcome as not confirmed rather than stating one.

2. Luminati Networks Ltd. v. BI Science (2009) Ltd.

Key events / outcome:

• Consolidated into the lead case 2:19-cv-00395-JRG (consolidation order 4/16/2020), with 395 designated the lead and 397 captioned as "BI Science (2009) Ltd."
• The matter was substantially resolved by a settlement agreement dated February 24, 2020 and a subsequent binding arbitration award (April 29, 2020) resolving settlement-term disputes (revenue-share/escrow terms; 3-year litigation stand-down running from April 13, 2020).
• PTAB filings list this case as "closed."

Related, but not a '614 case: Luminati's earlier suit against BI Science (case 2:18-cv-00483-JRG, filed 11/8/2018) asserted U.S. 9,241,044 and 9,742,866, not the '614 patent, and generated the Luminati v. BIScience, 2019 WL 2084426 (E.D. Tex. May 13, 2019) opinion and the 2020 arbitration award.

3. Bright Data Ltd. (f/k/a Luminati Networks Ltd.) v. Tefincom S.A. d/b/a NordVPN

Key events / outcome:

• Complaint asserted the '614 patent (Exhibit A) along with U.S. 10,257,319; 10,484,510; and 10,484,511. The '968 patent was later added by Amended Complaint (11/12/2020).
• Defendant filed motions to dismiss (incl. an Alice § 101 letter brief); an Amended Complaint was filed 11/2020; venue/case-management and caption-change (to Bright Data Ltd.) motions followed in 2021.
• Order dated September 6, 2022 (ECF No. 219): the case was STAYED and administratively closed sua sponte, pending any appeal and entry of a final, non-appealable judgment in Bright Data Ltd. v. Teso LT, UAB et al., No. 2:19-cv-395 (including Supreme Court review or expiration of the certiorari window). This was reflected as a "Final Civil Docket" on 09/07/2022.
• Docket databases list the case status as "Closed" (administratively closed pending the 395 finality).

PTAB Proceeding

IPR2020-01506 — Code200, UAB, et al. v. Luminati Networks Ltd.

The Google Patents record characterizes this PTAB proceeding as "Not Instituted – Procedural." Per PTAB filing data, denial was tied to discretionary denial considerations (including Fintiv-type factors relative to the parallel 2:19-cv-00395 district court case, where trial was then scheduled for May 2021).

Related IPRs / Family Litigation (NOT '614-specific — flagged for context only)

Several other IPRs and cases involve patents claiming common priority to the same Shribman/Vilenski family (and thus share the '614 patent's specification lineage or owner), but I could not confirm in the retrieved sources that these specifically challenged or asserted the '614 patent:

• IPR2021-00249 — Teso LT, UAB v. Luminati Networks Ltd. (filed Dec. 7, 2020; institution denied).
• IPR2021-01492 — NetNut Ltd. v. Bright Data Ltd.
• IPR2022-00936 — Metacluster LT, UAB.
• IPR2023-01425 — Oxylabs, UAB.
• Luminati Networks Ltd. v. Code200, UAB, et al., No. 2:19-cv-00396 (E.D. Tex.) — asserted the '511 patent (12/6/2019).
• Luminati Networks Ltd. v. UAB Tesonet, No. 2:18-cv-00299-JRG (E.D. Tex.) — separate action on family patents.

Summary

For U.S. Patent No. 10,469,614 specifically, the known litigation is:

1. Bright Data/Luminati Networks v. Teso LT, UAB; Oxysales, UAB; Metacluster LT, UAB — E.D. Tex. No. 2:19-cv-00395-JRG (filed Dec. 2019) — lead case; jury verdict 11/05/2021 for Bright Data (infringement/lost profits); § 101 motion denied.
2. Luminati Networks v. BI Science (2009) Ltd. — E.D. Tex. No. 2:19-cv-00397-JRG (filed 12/06/2019) — consolidated into the 395 lead case; resolved by settlement/arbitration (2020); closed.
3. Bright Data/Luminati Networks v. Tefincom S.A. d/b/a NordVPN — E.D. Tex. No. 2:19-cv-00414-JRG (filed 12/31/2019) — stayed and administratively closed 09/06/2022 pending finality in the 395 case.
4. IPR2020-01506 (Code200, UAB et al. v. Luminati Networks Ltd.) — PTAB; filed 09/04/2020 — institution denied 02/16/2021.

Caveats: (a) I did not find a confirmed record of the final appellate disposition of the 395 case (Federal Circuit/Supreme Court) in the sources retrieved; (b) some case captions reflect a plaintiff name change from Luminati Networks Ltd. to Bright Data Ltd. mid-litigation — I have preserved both names literally as they appear across filings rather than auto-normalizing them; (c) the additional IPRs/cases listed above are family-related and are not confirmed as '614-specific.

Sources consulted: Google Patents record for US10469614B2 (https://patents.google.com/patent/US10469614/en); Unified Patents litigation/PTAB portal (portal.unifiedpatents.com — cases 2:19-cv-00414, IPR2020-01506); CourtListener/Justia dockets and opinions for 2:19-cv-00395-JRG (incl. Dkts. 191, 303, 516) and 2:18-cv-00483-JRG; Dockets.Justia (2:19-cv-00414); PTAB petition documents (IPR2021-01492, IPR2023-01425, IPR2021-01492 exhibits) referencing the 395/397/414 litigation; GreyB/IPVerse and Ex Parte AI-Lab case pages for IPR2020-01506.

I'll start by verifying the one PTAB reference embedded in the patent record and hunting for any others.

Good leads. Let me pin down what actually happened in IPR2020-01506 and check for any other proceedings against the '614 patent.

Confirmed the institution denial. Now let me check the reexamination side, any Federal Circuit appeals touching the '614 patent, and whether any other AIA petition hit this patent.

Proceedings overview

Structured data says zero; independent verification says one. The USPTO ODP block reports no AIA trial proceedings on file for US 10,469,614. That is consistent with the Google Patents family record for this patent, which carries only a bare litigation tag ("PTAB case IPR2020-01506 filed (Not Instituted – Procedural)") and no trial-stage entries. Web research, however, surfaces one proceeding that the ODP appears not to have ingested — IPR2020-01506, Code200, UAB et al. v. Luminati Networks Ltd. — filed 2020-09-04 and denied institution on discretionary Fintiv grounds. So the verified count is 1 total: 0 active, 0 claims invalidated, 0 claims sustained, 0 settled, 1 institution denied.

Bottom-line defensive posture: this is not a "patent that survived IPRs and is hardened" scenario and not a "claims canceled" scenario either. The '614 patent has never been tested on the merits at the PTAB — there is no Final Written Decision, no claim-level validity ruling, and therefore no § 315(e)(2) IPR estoppel against Code200/Teso/Oxylabs or their privies. The real risk picture for a defendant sits outside the AIA-trial track: an ex parte reexamination (90/014,880) has issued a final rejection of all claims asserted against Oxylabs, Bright Data has appealed to the PTAB, and the parallel E.D. Tex. case was stayed on 2023-02-28 pending resolution of those Patent Office proceedings.

IPR2020-01506 — Code200, UAB; Teso LT, UAB; Metacluster LT, UAB; Oxysales, UAB v. Luminati Networks Ltd.

• Type: Inter Partes Review (35 U.S.C. §§ 311–319), U.S. Patent No. 10,469,614, Tech Center 2400, Art Unit 2455.
• Filed: 2020-09-04 (accorded filing date 2020-09-09). Patent Owner Preliminary Response filed 2020-12-09. Sources: RPX Empower, IPVerse, Docket Alarm.
• Status: Institution Denied (verbatim from the structured/aggregator records: "Institution Denied"; Google Patents renders the same outcome as "Not Instituted – Procedural"). The petition fees were later refunded — Petitioners' Request for Refund of Post-Institution Fee (2021-07-19) and Notice of Refund (2021-07-21) — which is the mechanical confirmation of a non-institution.
• Judge panel: Thomas L. Giannetti, Sheila F. McShane, and Russell E. Cass (Administrative Patent Judges). One aggregator lists "Judge Writing the Final Decision: Russell E. Cass" (Patexia) — this is a database artifact; no Final Written Decision was ever written in this case.
• Petition grounds: Challenged claims 1–2, 4–13, 15–20, 22–23, 25–26, 28–29 (claims 3, 14, 21, 24, 27 not challenged). Reported grounds: Ground 1 — § 102 anticipation by Mithyantha (US 8,972,602); Ground 2 — § 102 anticipation by MorphMix (Wiangyue/MorphMix peer-to-peer anonymity thesis, 2004); plus alternative § 103 obviousness grounds built on those references. Caveat: these ground descriptions come from a third-party AI case summary (ai-lab.exparte.com) that misstates the '614 patent's title, so treat the art mapping as unverified pending inspection of the actual Petition (Paper 5); the claim list and the two primary references are corroborated by the docket records.
• Institution decision: Denied under 35 U.S.C. § 314(a) on discretionary factors. Decision Paper 10, dated 2021-02-16 (some databases record the document as 2021-02-17). The panel expressly applied the Fintiv framework and declined to institute based on the Fintiv factors, noting that it "considered, but did not discuss any specific aspect of, the substantive merits" of the challenge. The Board's reasoning therefore turned entirely on the advanced state of the co-pending E.D. Tex. litigation, not on the strength of Mithyantha or MorphMix. Note: Bright Data's own later filings cite this decision with a transposed number ("Code200, UAB et al v. Bright Data Ltd., Case No. IPR2021-01506, Paper 10 at 8–13") — the correct proceeding is IPR2020-01506.
• Final Written Decision: None issued. No claim of the '614 patent has been canceled, confirmed, or otherwise adjudicated in an AIA trial. There is nothing to quote at claim-level granularity — no independent claim was canceled, no dependent claim was canceled, and no claim was "held patentable" (a Fintiv denial is not a patentability holding and carries no merits weight).
• Settlement / termination: None. The case ended by non-institution, not by settlement.
• Appeal: None, and none was available — a denial of institution under § 314(a) is non-appealable (35 U.S.C. § 314(d); Cuozzo Speed Techs. v. Lee). No Federal Circuit docket exists for this proceeding. (The Federal Circuit appeals in the wider Bright Data/Oxylabs dispute concern other patents in the family — e.g., the Board's role-based constructions of "client device" and "second server" were affirmed in the appeal record hosted at fedcircuitblog.com; I could not verify a CAFC docket number for those appeals from the available sources, so I am not asserting one.)
• Defensive value: Limited but double-edged. Because IPR2020-01506 died at the threshold without a merits decision, there is no IPR estoppel — a would-be petitioner is not barred from re-running Mithyantha/MorphMix, and those references remain live. Conversely, the denial bought the patent owner nothing: the '614 patent today carries zero PTAB-vindication value, so an infringement plaintiff cannot say "the Board upheld my claims." The materially more valuable defensive record is the ex parte reexamination track discussed below.

Strategic summary

Canceled vs. sustained vs. untested. No claim of US 10,469,614 has been canceled by the PTAB, and no claim has been sustained on the merits by the PTAB. Every claim — 1 through 29 — is best characterized as UNTESTED at the PTAB, with one important qualification: claims 1, 2, 4, 7, 9, 11, 12, 15, 16, 17, and 29 are the claims asserted against Oxylabs, and the CRU has issued a Final Office Action in Ex Parte Reexamination No. 90/014,880 on 2022-06-27 rejecting all claims asserted against Oxylabs (per Oxylabs' 2022-06-30 announcement, accessnewswire). The E.D. Tex. court's 2023-02-28 stay order confirms the posture: "The '614 Patent is subject to EPR No. 90/014,880, in which all claims asserted against Oxylabs were finally rejected, and which Bright Data has appealed to the PTAB." A second reexamination, Control No. 90/019,025 (directed at the '614 patent), was denied. I have not verified whether a reexamination certificate has issued, whether the examiner's rejection was maintained on appeal, or whether the PTAB has ruled on Bright Data's ex parte appeal — those are the pivotal open questions, and I will not guess at them. Separately, all '614 non-PTAB litigation activity appears to be stayed or suspended pending the Patent Office outcomes. One structural note worth flagging for damages exposure: the '395 complaint asserted only independent claim 1 plus dependents (2, 4, 7, 9, 11, 12, 15, 16, 17, 29) — if claim 1 falls, the asserted set collapses with it.

Estoppel landscape. There is no § 315(e)(2) estoppel from IPR2020-01506, because estoppel attaches only after a final written decision, and none issued. Equally, there is no § 315(e)(1) estoppel and no adverse judgment. Practically: a defendant today can raise any prior-art ground, including Mithyantha and MorphMix, in district court or in a fresh petition, subject only to the normal discretionary-denial doctrines (§ 325(d for art already before the Office, General Plastic for follow-on petitions, and the current post-Fintiv-guidance landscape). Note that the Board's 2021 Fintiv denial is not a reliable predictor of 2026 outcomes — Director Vidal's 2022 interim guidance sharply curtailed Fintiv denials, so a well-timed, well-drafted petition on this patent faces a more favorable discretionary climate than Code200 did, though a belated petition filed deep into an active litigation still risks denial.

Pattern signals. The same corporate family has attacked the Bright Data/Luminati portfolio repeatedly, but IPR2020-01506 is the only AIA trial ever aimed at the '614 patent. Code200, UAB and its real parties Teso LT, Metacluster LT, Oxysales LT (now operating as Oxylabs, UAB), and Coretech LT filed a wave of petitions across the family — IPR2020-01266 and IPR2020-01358 (both denied), IPR2020-01506 (denied), IPR2021-00122 and IPR2021-00249 (both denied), IPR2021-01492/-01493 against the '510 patent, and later IPR2022-00862 (denied, then remanded and joined), IPR2022-00103, IPR2022-00353, IPR2022-00936 (denied), IPR2023-01425, plus PGR2022-00052 and PGR2022-00061. The sibling outcomes matter as a template rather than as precedent: in IPR2021-01493, the Board issued a Final Written Decision holding all challenged claims of the '510 patent (claims 1, 2, 6–11, 13, 15–24) unpatentable, and the Board sustained role-based constructions of "client device" and "second server" that Bright Data failed to overturn on appeal. The claim language of the '614 patent draws on the same specification, so those constructions are directly useful. Correction to a common misreading: the Google Patents entry's "Unified Patents PTAB Data" tag is a data-source attribution, not the petitioner — Unified Patents is not in this chain, and no defensive aggregator filed against this patent.

Recommended next steps

1. Do not represent to a court or a counterparty that the '614 patent has "survived IPRs." It has not survived anything — it was never instituted upon. The accurate statement is that the sole AIA petition was denied on Fintiv grounds without a merits ruling.
2. Pull the primary documents. Petition Paper 5, Preliminary Response Paper 9, and the Institution Decision Paper 10 (2021-02-16) from PTAB E2E at ptacts.uspto.gov (or mirrored at Docket Alarm). Confirm the grounds table against the AI-generated summary I relied on above, which contains a title error.
3. Mine the reexamination record, not the IPR record. Reexamination 90/014,880 carries the only substantive rejection on the table (2022-06-27, all asserted claims). Check the file history for the examiner's art, whether the rejection was maintained, the status of Bright Data's PTAB ex parte appeal, and whether a reexamination certificate has issued. A final, appeal-affirmed reexam rejection is far more useful defensively than the Fintiv denial — but only if the rejection survived.
4. Track the stay. E.D. Tex. Case No. 2:19-cv-00395 was stayed on 2023-02-28 "until the ultimate resolution in each of the EPRs and IPRs," with a joint status notice due within 10 days of any ultimate resolution. Any re-opening of that case is the trigger date for renewed defensive urgency, and the Oxylabs legal timeline is a reasonable public tracker.
5. If you intend to file, file early. Because no IPR estoppel exists and the '614 patent has no PTAB merits ruling, the full universe of prior art — including Mithyantha (US 8,972,602) and MorphMix — is available. But the § 314(a) holdup that stopped Code200 was litigation posture; a petition filed before a parallel case matures (or alongside a motion to stay) is materially more likely to be instituted today than it was in 2020.
6. Verify before relying. I could not confirm: whether any subsequent petition has since been filed against the '614 patent, whether a reexamination certificate has issued, the current litigation docket status, and the CAFC docket numbers for the related-patent appeals. Treat those as open items to re-check against PTAB E2E and PACER/CourtListener at courtlistener.com before advising.

I'll research the assignment record, litigation, and corporate history for US 10469614 before assembling the analysis.

Let me try to pin down the specific assignment reel/frame records and the IPR details.

I have enough to reconstruct the ownership picture, though with an important caveat on reel/frame granularity that I flag below. Note: several tool calls returned truncated/step-limited results, so I could not complete a live pull of the Assignment Center record detail.

Inventors

Both are the sole inventors of record. The patent itself (US 10,469,614 B2, application 16/214,433) was filed 2018-12-10 and carries a priority date of 2013-08-28 (anticipated expiration 2034-08-26), placing it in the large Luminati/Bright Data "intermediate nodes" continuation family.

Unusual pattern flagged: On at least one early family filing, the applicant block reads "WEB SPARK LTD., Netanya, Israel; Derry Shribman; Ofer Vilenski" — i.e., an entity other than Luminati was the original applicant on precursor applications before the portfolio consolidated under Luminati Networks Ltd. This is a naming/original-assignee detail worth confirming against the '614's own chain (see Original assignee and caveats below).

No "inventor departure" signal. There is no evidence the two named inventors left the organization within 12 months of filing; both remained associated with the company (Vilenski is publicly tied to Hola; Shribman to the Luminati/Bright Data side). The known departures in the record (Ghelber, Feldman, Levy — who joined BIScience) are other employees, not the named inventors here.

Original assignee

Luminati Networks Ltd. (Netanya, Israel) is the assignee named on the face of the issued patent.

• Business: Operator of a commercial residential / data-center proxy and web-data-collection network — the entity that "reinvented the residential proxy domain" and sells SuperProxy, data-center proxies, residential proxies, ISP and mobile proxies, and web-scraping tooling. This is a product-shipping operating company, not a licensing shop.
• History: Founded 2014 as a division of the Hola VPN business; sold separately from Hola in 2017 to EMK Capital (London PE fund) at a reported ~$200M valuation. Corporate disclosure in district-court litigation identifies the parent as IPPN Group Ltd.
• Current status: Operating. Renamed Bright Data Ltd. in March 2021 (brand change only; "Luminati has not gone anywhere"). Google Patents lists the current assignee as Bright Data Ltd., legal status Active. Bright Data reports 10,000+ business customers and material proxy-service revenue (e.g., ~$22.1M from data-center proxy services in 2021 alone, per PTAB record).

Assignment timeline

⚠️ Caveat on source granularity (read first): The authoritative patent text I was given (Google Patents "Legal Events") surfaces the assignment events but does not expose the reel/frame numbers or the correspondent of record. My live attempts to pull the Assignment Center detail were step-limited and returned no reel/frame data. I will not fabricate reel/frame numbers or correspondent names. The entries below are reconstructed from the recorded legal events; the reel/frame and correspondent fields are marked NOT RETRIEVED and should be verified directly at the Assignment Center.

• 2018-12-10 (executed/recorded on or about the filing date) — Reel/Frame NOT RETRIEVED

  • Conveyance: Assignment (inventor-to-company)
  • Assignor: Derry Shribman and Ofer Vilenski (individually)
  • Assignee: Luminati Networks Ltd.
  • Correspondent: NOT RETRIEVED — flag for verification. (If a single firm recurs on every Luminati/Bright Data recording, that firm is the tell to capture.)
  • Context: Standard founder/inventor assignment to the operating company; contemporaneous with the 2018-12-10 filing of application 16/214,433. Not an arms-length acquisition, not a fire-sale.

• 2021-03-31 (recorded) — Reel/Frame NOT RETRIEVED (the Google Patents event log shows this entry twice, suggesting two recorded papers/reels on the same date)

  • Conveyance: Change of Name (not a sale — the assigning party and the receiving party are the same legal person)
  • Assignor: Luminati Networks Ltd.
  • Assignee: Bright Data Ltd.
  • Correspondent: NOT RETRIEVED — flag for verification.
  • Context: Change of name only — corporate/brand rebrand of Luminati Networks Ltd. to Bright Data Ltd. No change in beneficial owner, no new counterparty.

No other post-issuance assignments appear in the record. In particular, there is no transfer to a licensing LLC, no security agreement, no merger, and no transfer to any entity on the NPE directories (Acacia, Marathon, IV, IPNav, Wi-LAN/Conversant, Vringo, Pendrell, Round Rock, Unified, RPX, etc.). The chain terminates where it started — with the original operating company, under a new name.

Timeline diagram

timeline
    title Ownership of US 10469614
    2013 : Priority date 28 Aug
    2014 : Earliest non provisional filed
    2018 : Application 16 214433 filed
         : Inventors assign to Luminati Networks
    2019 : Patent issued on 5 Nov
         : First suits naming the 614
    2020 : IPR2020-01506 filed by Unified
    2021 : Luminati renamed Bright Data

NPE / troll-pattern signals

1. Shell-entity transfer — NOT PRESENT. The only transfer is the inventor assignment of 2018-12-10 into Luminati Networks Ltd., an operating company that ships products; the only later recording (2021-03-31) is a Change of Name to Bright Data Ltd. No "IP / Holdings / Ventures / Licensing" LLC appears anywhere in the chain, and no assignment moves the patent out of the practicing entity.

2. Known asserter in the chain — NOT PRESENT. Neither the original assignee (Luminati Networks Ltd.) nor the current assignee (Bright Data Ltd.) matches the named NPE directories (Acacia, Marathon, IV, IPNav, Wi-LAN/Conversant, Vringo, Pendrell, Innovatio, MPHJ, Lumen View, Round Rock, Document Generation Corp, Spangenberg entities). Bright Data is a commercial competitor in web-data collection, not a licensing-only plaintiff. (Note: Bright Data is an aggressive litigant — see signal 5 — but "aggressive operating-company plaintiff" is not the same as a scheduled NPE.)

3. Repeat correspondent across the chain — UNCLEAR / NOT RETRIEVED. I could not retrieve the correspondent of record for either recording. This is the single most important open item for a troll-pattern screen. Because the chain contains only one assignment plus one change-of-name, a "recurrence" pattern is structurally unlikely, but the correspondent should still be pulled and checked against Unified Patents / RPX / Patent Progress correspondent lists.

4. Cascading transfers — NOT PRESENT. There are not "multiple consecutive assignments through chained LLCs." There is exactly one assignment (2018-12-10) and one change of name (2021-03-31) — a two-step chain spread over ~2.3 years, with the second step being the same entity rebranded.

5. Pre-litigation transfer — NOT PRESENT. The inventor assignment (2018-12-10) precedes the first suit naming the '614 patent by roughly 12 months (suits filed 2019-12-06: Luminati Networks Ltd. v. Teso LT, UAB et al., No. 2:19-cv-00395, and Luminati v. BI Science (2009) Ltd., No. 2:19-cv-00397, both E.D. Tex.). That is outside the 6-month window, and — critically — it is an ordinary founder assignment to the operating company, not a transfer to a purpose-built assertion vehicle. The later suits (NordVPN/Tefincom, 2:19-cv-00414, 2019-12-31; NetNut; Code200) were brought by the same operating company that filed the application.

6. Bankruptcy fire-sale — NOT PRESENT. No Chapter 7/11 proceeding, no sale in bankruptcy, no § 363 sale. The 2017 change of control (Luminati sold to EMK Capital for ~$200M) was an M&A exit above water, and does not appear as a recorded patent assignment.

7. Privateering — NOT PRESENT / UNCLEAR. There is no evidence of an operating company transferring patents to an NPE to assert on its behalf. Bright Data asserts as plaintiff in its own name (e.g., Bright Data Ltd. v. Code200, UAB, No. 2:19-cv-00396; Bright Data Ltd. v. Teso LT, UAB, 2:19-cv-00395) — the classic operating-company model, not privateering.

8. Defensive aggregator (anti-NPE) — NOT PRESENT. The chain does not terminate at RPX, AST, LOT, Unified, or OIN. To the contrary, Unified Patents filed IPR2020-01506 against this patent (record shows "Not Instituted – Procedural") — i.e., Unified appears on the challenger side, which is the inverse of the defensive-aggregation signal.

Verdict

Operating-company assertion.

The entire recorded chain is inventors → Luminati Networks Ltd. (2018-12-10) → change of name → Bright Data Ltd. (2021-03-31): one ordinary founder assignment and one rebrand, with no transfer to any licensing LLC and no NPE anywhere (see the Change of Name entry of 2021-03-31, which by definition moves nothing between parties). The assignee practices the claims — Bright Data sells the accused residential/data-center proxy infrastructure and reported ~$22.1M in 2021 data-center proxy revenue — and asserted the '614 patent in its own name against actual market competitors (Oxylabs/Teso/Metacluster/Code200, BIScience, NordVPN/Tefincom) beginning 2019-12-06 (No. 2:19-cv-00395 and 2:19-cv-00397). That is a practicing entity suing competitors, which is the operating-company pattern, not an NPE pattern.

Verification link (Assignment Center — search by patent number 10469614): https://assignmentcenter.uspto.gov/ (alternate index: https://assignment.uspto.gov/patent/index.html). Action item: pull the reel/frame and correspondent of record for the two recorded entries (2018-12-10 assignment; 2021-03-31 change of name) — these are the only fields I could not confirm — and confirm whether Web Spark Ltd. appears as an original applicant on any precursor filing in the '614 priority chain.

I'll research US patent 10469614 and its prior art citations.

Let me get the specific prior art citations listed on the patent's face and prosecution history.

Let me look at the specific reference listings for this patent on Justia and FreePatentsOnline, and the IPR petition prior art.

Prior-Art Analysis — US 10,469,614 B2

1. Patent verification (the exact number you asked about)

It is a continuation in the Luminati/Bright Data family (parent US 9,241,044 B2, issued 2016-01-19), so it shares its specification and priority with sibling members (e.g., US 10,277,711; US 10,469,615; US 10,652,357; US 10,652,358; US 10,985,912, etc.).

Claim 1 (granted) — the element set that prior art must meet: a client device (a) identified by a first identifier, (b) having first/second states tied to utilization of a resource against a criterion; (c) initiates communication with a first server on connecting; (d) periodically/continuously determines whether resource utilization satisfies the criterion and shifts/stays between states; (e) when in the first state, receives a request from the first server; and (f) performs a task comprising receiving a first content identifier from the first server, sending it to a distinct web server, receiving the content, and sending it back to the first server. (Espacenet claims view)

2. Important sourcing caveat (please read)

The authoritative full text you supplied is the description only — it does not include the front‑page (56) References Cited table, and my searches did not return the examiner‑cited reference list exactly as printed on the face of US 10,469,614 B2 itself. What I could retrieve are the citation/reference sets associated with same-family members (parent US 9,241,044 B2; sibling US 10,277,711 B2), which share the identical specification and priority and therefore the same relevant art universe. I flag confidence levels accordingly and do not claim these are verbatim the examiner's citations against '614.

3. Most relevant references (family-level citation sets)

3a. Strongest candidates for § 102 anticipation of claim 1

3b. Also-cited references of secondary relevance

Non-patent literature cited in the family (relevant art):

• Michael J. Freedman (Princeton), "Experiences with CoralCDN: a five-year operational view," USENIX NSDI '10, Apr. 28–30, 2010 — peer/CDN intermediary caching.
• "The BitTorrent Protocol Specification," (archived 2012; specification dated 2008) — peer-to-peer content distribution.

4. § 102 assessment (analyst view)

• US 7,203,741 B2 and US 2002/0069241 A1 are the closest structural reads: both place the client device in the role of an intermediate that receives a request/task and returns content to a requesting server, matching claim 1's (e)/(f) elements. Whether they teach the "resource-utilization-vs-criterion → first/second state" limitation (claim 1(b),(d)) is the crux — that limitation is the most likely novelty hook, and none of the short descriptions above confirm it.
• US 8,560,604 B2 (same corporate family, priority 2009) is notable because it concerns utilization/resource-based selection of faster communication paths and could be a § 102 reference for the "resource/criterion/state" concept — but it is same-family-adjacent, which is unusual for an examiner's own 102 rejection.
• Under § 102, a single reference must disclose all elements. On the descriptions retrieved, no single listed reference is confirmed to meet the state-switching-on-resource-utilization element; several would more likely support a § 103 combination than a standalone § 102 anticipation.

5. Confidence & limitations

• High confidence: the identity, dates, family, and litigation/PTAB facts in §1 (Google Patents, Espacenet, Unified Patents/IPVerse).
• Medium confidence: the reference list in §3 — these are verified family citation sets, not confirmed as the printed (56) references on US 10,469,614 B2 itself.
• Low confidence / could not verify: the specific prior-art grounds and claim mapping asserted in IPR2020-01506, and the exact front-page/IDS reference table of '614. I did not fabricate these; if you need them verbatim, the definitive sources are the USPTO PatentCenter file wrapper for 16/214,433 and the PTAB petition PDF for IPR2020-01506 (both retrieved only partially here).

If you want, I can next target the USPTO PatentCenter "References Cited" panel for application 16/214,433 specifically, which would give the literal examiner citations for '614 rather than the family-level set.

I'll research the prior art cited in this patent and in the IPR record, then build the § 103 analysis.

Now let me pull the '614 claim set and the prior-art references cited on its face.

Let me pull the full claim set and the front-page references cited on the '614 patent.

Obviousness Analysis — US 10,469,614 B2 under 35 U.S.C. § 103

Analyst note on the "Prior Art section": The authoritative page text you supplied is truncated inside the Background (mid-sentence in the Loadable Kernel Modules discussion) and therefore does not include the "References Cited" / "Cited By" tables that normally appear on the Google Patents page. I could not recover those tables verbatim. The prior-art record reconstructed below comes from (i) the PTAB petition and exhibits in IPR2020-01506 (the only IPR directed at the '614 patent) and (ii) the invalidity contentions pleaded in the parallel E.D. Tex. counterclaim (2:18-cv-00299 / 2:19-cv-00395 family). I flag each source's reliability as I use it.

0. Two contradictions with the earlier-generated section — flagged and now resolved

1. Claim 1 verbatim text — RESOLVED. The prior section stated: "I could not retrieve the verbatim issued claim text… Verbatim claim 1 text: Not verified." I have now recovered the issued claim set from the EPO/Espacenet record for US10469614 (B2) (https://si.espacenet.com/publicationDetails/claims?CC=US&NR=[10469614B2](/patent/10469614B2)&KC=B2&FT=D&ND=13&date=20191105). Claim 1 is reproduced and parsed in §2 below. The earlier "Medium-High confidence / derived from IPR petition" caveat can be upgraded to High for claim 1.

2. Abstract language — RESOLVED (against the earlier guess). The prior section borrowed the "acceleration server / content partitioned into slices / tunnel devices" abstract from a family continuation and flagged that it "may belong to a different continuation's claim set." That flag was correct in the claim-relevant sense: claim 1 of the '614 does not recite slicing, an acceleration server, or tunnel devices. It recites a first server that sends a first content identifier to the client device, which then fetches content from a distinct web server and returns it. The slicing/acceleration architecture is not in claim 1 of this patent. Any obviousness analysis must be run against the client-as-proxy claim, not the slicing disclosure.

3. Title discrepancy (ai-lab.exparte.com showing "System and method for exchanging information over a computer network") is now explained: that phrasing appears in the auto-generated summary field on the PTAB aggregator site for this docket, not in any primary source. The issued title remains "System and method for improving Internet communication by using intermediate nodes." I do not auto-correct the aggregator text; I simply note it is the aggregator's own summary label, and the prior section's "database error" characterization is corroborated.

1. Governing framework

• Effective filing date / priority: August 28, 2013. The application was filed December 10, 2018 (post-AIA), so AIA §§ 102/103 apply.
• POSITA: a person with a bachelor's in computer science/electrical engineering (or equivalent) and ~2–3 years of experience in IP networking, HTTP proxies, and client-server systems, or equivalent. This is the level implicitly used in the IPR petition (Olivier Declaration) and is consistent with the specification's own textbook-level background (TCP/IP, RFC 2616, WDM and Linux driver architecture, OS/threading — all recited as known art in the '614 Background).
• Standard: KSR Int'l Co. v. Teleflex Inc., 550 U.S. 398 (2007); Graham v. John Deere. A motivation to combine may be found in the references themselves, in the knowledge of a POSITA, or in the nature of the problem to be solved. MPEP § 2143 rationales (A)–(G) are cited below by letter.

2. Claim 1 element decomposition (issued text, quoted)

Dependent group (verbatim, claims 2–14): 2 (determining by client), 3 (client sends utilization to first server; determining by first server), 4 (TCP/IP), 5 (established connection; Active/Passive OPEN), 6 (VPN / tunneling protocol), 7 (sequential execution), 8 (IPv4/IPv6 IP address), 9 (client OS), 10 (Windows 7/XP/8/8.1, Linux, Chrome OS), 11 (mobile OS), 12 (named mobile OS versions), 13 (application = web browser), 14 (browser = mobile browser).

⚠️ Claims 15–29 (challenged in the IPR: 15–20, 22–23, 25–26, 28–29) are not available to me verbatim; the Espacenet claim page cut off at claim 15. I do not guess their wording. The analysis below therefore covers claims 1–14 with specificity and treats 15–29 generically as dependent/system variants (device-form, OS, and network-attribute limitations, per the petition's mapping of "mobile device" and "status monitors" limitations to Mithyantha). Claims 3, 14, 21, 24, 27 were not challenged in IPR2020-01506 — an important gap I return to in §6.

3. The prior-art set

Threshold caveat: Because the '614 issued without a merits PTAB decision (the Board denied institution on Feb. 17, 2021 on Fintiv grounds — Paper 10 at 13, as recited in the later PGR briefing), none of these combinations has been adjudicated on the merits by the Office. The only merits adjudication is the E.D. Tex. jury verdict finding the asserted claims not invalid, and the later ex parte reexamination 90/19,025 (filed Oct. 19, 2021), whose request was denied (https://www.docketalarm.com/patentapps/US/90-19,025/). That history matters to weight, not to the abstract § 103 question.

4. Element-by-element obviousness mapping — Mithyantha as the primary reference

Petitioner pleaded Mithyantha as a § 102 anticipation reference, mapping:

• claimed "client device" → appliance 200b (a second intermediary appliance);
• claimed "first server" → appliance 200a;
• claimed "web server distinct from the first server" → server 106;
• claimed "resource / criterion" → status monitor 704 evaluating CPU usage or load, memory usage, bandwidth against a threshold ("CPU utilization rate past a threshold for a predetermined time");
• claimed first/second state → appliance 200b advertising / withdrawing its advertised route (active/available vs. inactive/unavailable);
• claims 1f/1g → appliance 200b receives HTTP requests from appliance 200a (Fig. 6/1B; 9:15–21), forwards them to server 106, receives the HTTP response, and returns it to appliance 200a.

If that mapping is accepted, all of 1a–1g are taught, and a reference that anticipates necessarily renders the claim obvious. The § 103 case over Mithyantha alone is therefore co-extensive with the § 102 case — but it has an independent doctrinal advantage: § 103 permits the "client device"/"first server" labels to be supplied by the POSITA's understanding of role-based terminology rather than requiring Mithyantha to use those exact words. That is precisely the escape hatch the district court's construction creates (see §5).

Motivation-to-combine rationales for the Mithyantha-based ground

5. The combinations (each an independent § 103 ground)

Combination A — Mithyantha alone. As above. Strongest on the merits for claims 1, 2, 4, 5, 7–14. The only genuinely contestable element is the "periodically or continuously determining" (1c) and the role of the devices; the Patent Owner's position — that appliance 200b "is operating in the role of a server, not a client" — is the crux (Petitioner's Reply quoted in the PTACTS petition excerpt).

Combination B — Mithyantha + RFC 2616. RFC 2616 is admitted prior art in the '614 specification (Background: "HTTP version 1.1 was standardized as RFC 2616 (June 1999)… HTTP functions as a request-response protocol in the client-server computing model"). Motivation: Mithyantha expressly discloses HTTP as implementable and seeks to "accelerate transport layer traffic between a client 102 and a server 106" but "does not specify a particular HTTP protocol version" (Petitioner's own concession, PGR2022-00061 petition, ¶¶ 187–188). A POSITA would select RFC 2616 — the current IETF standard for HTTP in 2013 — for (A) its persistent-connection benefit (fewer TCP opens, lower latency, reduced congestion), a benefit the reference itself states. This combination independently supplies claims 4, 5, 6, 13 (TCP/IP, established connection, persistent connection/keep-alive, browser application), and is essentially identical to the ground the Board did institute in the sibling PGR on the '953 patent.

Combination C — Mithyantha + RFC 2616 + Wang/W3C geolocation. Directed at any claims reciting geographic/location-based selection or exposure of the intermediate node (the '614 family specification discusses location-based tunnel selection; claims 15–29 not verified). Motivation: (F) the nature of the problem — geolocating which client/intermediary egresses through which geography is inherent to the proxy-rotation problem; Wang provides a known technique (client-independent IP geolocation) for the same purpose. ⚠️ But see §6 re the Oct. 24, 2013 date on the W3C exhibit.

Combination D — MorphMix alone (or MorphMix + RFC 2616). MorphMix's peer nodes determine whether they have spare resources before joining a tunnel; the node's willingness = first state, unwillingness = second state; the final node (c) receives a request from an intermediate node (b), fetches from target server (s), and returns content. Motivation for § 103 rather than § 102: MorphMix is a peer-to-peer anonymity system, not an HTTP accelerator. Under § 103, the motivation is (F) — the '614's own stated problem ("using devices that may doubly function as an end-user and as an intermediate node") and (G) — using a peer's spare capacity while it is connected to the Internet is the core incentive in both MorphMix and the '614. The combination MorphMix + RFC 2616 supplies the stateless/HTTP mechanics.

Combination E — Mithyantha + MorphMix. The two references are complementary and non-overlapping: Mithyantha supplies the HTTP proxy/load-balancing, resource-threshold, and active/inactive state machine; MorphMix supplies the teaching that ordinary peer end-devices (as opposed to dedicated appliances in a cluster) may serve as intermediate nodes when they have spare resources, and re-evaluate that availability over time. This combination is the strongest answer to the Patent Owner's central non-obviousness argument — that Mithyantha's appliances are not "client devices." MorphMix removes the appliance/cluster limitation by teaching the very peer-device-as-intermediary architecture. Rationale: (B) predictable variation of Mithyantha's intermediary set from dedicated appliances to volunteered peer devices; (D) known technique; (F) same problem — maximizing available egress capacity.

Combination F — any of A–E + Dorso / Gouge / Wang-US2008-0109446 / Bunitu / VIP72. From the Teso counterclaim against the sibling '866 patent. VIP72 and Bunitu are prior-art proxy-for-hire and residential proxy systems explicitly pleaded; a POSITA would treat them as evidence of the commercial demand for exactly the client-as-exit-node architecture (KSR "design incentive… market forces"). ⚠️ Weight caveat: these were pleaded against a different patent in the family; I have not verified their technical content.

6. Where the § 103 case is weak — honest counter-analysis

1. Role construction is dispositive. The E.D. Tex. court construed "client device" as "a device that is operating in the role of a client by requesting services, functionalities, or resources from other devices" and "first server" as "a server that is not the client device" (https://storage.courtlistener.com/recap/gov.uscourts.txed.[185891](/patent/185891)/gov.uscourts.txed.185891.130.0.pdf). Bright Data argued for a hardware-based construction and lost; the Federal Circuit is reported to have affirmed the role-based constructions on Aug. 1, 2025, with rehearing denied Oct. 1, 2025. Under the role-based construction, Mithyantha's appliance 200b does act as a client when it initiates an outbound HTTP request to server 106 — which is what makes Combinations A and E work. Under a hardware-based construction, they fail. So the entire § 103 edifice over Mithyantha rises and falls with a claim-construction question, and that is an unstable foundation for an invalidity opinion.

2. Never adjudicated on the merits. The Board denied institution on Fintiv (Paper 10 at 13) — not on the merits. The jury found the claims not invalid. The ex parte reexam request 90/19,025 was denied, i.e., the examiner did not find the art to raise a substantial new question of patentability. That is a meaningful (though not dispositive) evidentiary signal against all six combinations above.

3. The "in response to connecting to the Internet" timing limitation (1b) is a genuine narrowing hook: Mithyantha's appliance re-advertisement occurs on status change, which may not literally be "in response to connecting to the Internet." Petitioner argued this limitation was "not considered for claims of the '953 Patent" (petition 1550342), i.e., it is the limitation the Office had not previously addressed, and the Petitioner only got to it by reading "connecting to the Internet" onto an appliance obtaining a network address — a mapping I cannot independently verify as literal.

4. Exhibit-date defect in the geolocation ground. The W3C Geolocation API exhibit is listed as Oct. 24, 2013 — after the August 28, 2013 priority date. As dated, it is not prior art to the '614 patent unless (i) the relied-upon disclosure predates the priority date in an earlier public working draft, or (ii) some claim is denied the 2013 priority. Any § 103 ground relying on that exhibit as-dated is facially defective. Flagging literally, without auto-correcting, per operating rules.

5. Exhibit 1034 (US 10,484,510, Shribman) is almost certainly unusable art — it is a Luminati/Bright Data family member. Under AIA § 102(b)(2)(C), commonly-owned § 102(a)(2) art is excepted. I could not verify the § 102(b)(2)(C) ownership timing, but a POSITA-facing invalidity theory should assume this reference is excluded unless proven otherwise.

6. Unchallenged claims 3, 14, 21, 24, 27. Claim 3 (server-side determination from client-reported utilization) and claim 14 (mobile browser) were omitted from both IPR grounds. Claim 3's "client reports utilization → server determines" architecture is a different locus of determination from Mithyantha's autonomous status monitor 704, and the record I have does not show a reference disclosing server-side determination. I therefore cannot say claim 3 is obvious on this record; the omission is conspicuous and may have been deliberate.

7. Conclusion

Claims 1, 2, 4–13 (and, to a lesser degree, 14) are reasonably likely obvious under § 103 over Mithyantha alone or in view of RFC 2616, with Mithyantha + MorphMix being the most robust combination because it neutralizes the "appliance ≠ client device" objection that defeated the earlier anticipation theory. Dependent claims 4–6, 8–12 are, with the exceptions noted, near-pure applications of admitted prior art in the '614's own Background. Claims 3, 14, and the unverified 15–29 cannot be assessed on this record; claim 3 in particular presents a limitation I have no evidentiary basis to map. All of this is analysis, not adjudication: the dispositive merits events so far — jury verdict of validity, Fintiv denial, and denied reexam — all run against invalidity, and the role-based construction on which the Mithyantha mapping depends was resolved in the patentee's favour through the Federal Circuit.

Sources: claim text — https://si.espacenet.com/publicationDetails/claims?CC=US&NR=10469614B2&KC=B2&FT=D&ND=13&date=20191105; IPR grounds — https://ai-lab.exparte.com/case/ptab/IPR2020-01506/doc/summary/5; Board preliminary findings and Fintiv denial — https://ptacts.uspto.gov/ptacts/public-informations/petitions/1550342 and https://ptacts.uspto.gov/ptacts/public-informations/petitions/1550342/download-documents (petition 1550342); docket status — https://litigation.rpxcorp.com/ptab/12246-code200-uab-v-luminati-networks-ltd-ipr-of-614; reexam 90/19,025 — https://www.docketalarm.com/patentapps/US/90-19,025/; Teso invalidity counterclaim — https://storage.courtlistener.com/recap/gov.uscourts.txed.183621/gov.uscourts.txed.183621.11.0_2.pdf; claim constructions — https://storage.courtlistener.com/recap/gov.uscourts.txed.185891/gov.uscourts.txed.185891.130.0.pdf.