US 6754699

I'll research US patent 6754699, including checking for any recent CAFC 2026 docket activity.

Let me check specifically for any 2026 CAFC docket activity and recent litigation.

Let me verify the claim structure and check the patent's expiration/litigation status.

Search results for US 6,754,699

Important methodological note: I ran web searches (Google Patents, Justia, Unified Patents, Federal Circuit coverage) rather than querying the USPTO PatentCenter and CAFC docket systems directly. I could not find any CAFC 2026 docket or appeal involving US 6,754,699, and I was not able to retrieve the verbatim claim text within this session. Where I lack authoritative information, I say so below rather than guessing.

Bibliographic summary (from the authoritative Google Patents full text)

Assignment history (per the record): Speedera Networks (2001) → Hewlett-Packard Company security agreement (2002) → assignment and release back (2003) → Comdisco payoff agreement (2006) → HP settlement & release to "Sppeedera Networks, Inc." (2006) → Akamai Technologies, Inc. via Certificate of Ownership & Merger (2006-03-16). (plainsite assignment record)

Continuation family (all claiming priority through this line): US 7,363,361; US 7,194,522; US 7,574,499; US 7,484,002; US 7,743,132; US 7,979,580; US 7,904,541; US 8,341,278; US 8,204,976; US 8,612,564.

Abstract (paraphrased — the fetched page reproduces the substance but not the verbatim abstract block): A content delivery and global traffic management network system in which multiple caching servers host customer content, respond to client requests, and fetch-and-cache from an origin site on a cache miss; a DNS server performs load balancing across servers by selecting the caching/origin server that is closest, available, and least loaded, based on static configuration plus dynamic probe data; persistence and per-zone server assignment are supported; and content freshness is checked against the origin. ⚠️ I do not have the certified abstract wording verified this session.

Plain-language overview of the claims

⚠️ Uncertainty flag: I could not retrieve and verify the exact independent claim language of US 6,754,699 in this session. A confident, claim-by-claim quotation would require pulling the patent's claim set from USPTO PatentCenter/Public PAIR or the issued PDF (linked from Google Patents). What follows is an overview grounded only in the specification's stated subject matter, and should be treated as provisional.

Based on the specification, the independent claims are directed to two complementary aspects:

1. Content delivery aspect — receiving a client request for content (e.g., an embedded object mapped to a network hostname such as customer.speedera.net), and, when a caching ("delivery") server lacks the object, retrieving it from the customer's origin site, storing it in the cache, and serving it to the client — with periodic freshness checking (If-modified-since) against the origin.

2. Global traffic management aspect — resolving a hostname to an IP address of a selected server among those able to serve that hostname, using a DNS server that weighs static hostname→server mappings together with dynamic metrics gathered by probes (service/availability metrics, latency round-trip measurements to the client's local DNS, packet-loss metrics, load), optionally with persistence (returning the same IP for a given client) and per-zone assignment/forwarding among DNS servers.

Typical independent claims in this family recite a method (and a corresponding system/computer-readable-medium claim) combining the DNS-based selection and/or the caching-and-origin-fetch steps. I recommend verifying the exact claim count and wording before relying on this in any legal analysis.

April 2026 CAFC status

• No CAFC 2026 docket involving US 6,754,699 was found. The searches surfaced no appeal or decision naming this patent.
• The prominent 2025–2026 Federal Circuit Akamai case is Akamai Technologies, Inc. v. MediaPointe, Inc., No. 2024-1571 (Fed. Cir. Nov. 25, 2025) — not about the '699 patent. It concerned US 8,559,426 and US 9,426,195 ("System and Method for Distribution of Data Packets Utilizing an Intelligent Distribution Network"), and the court affirmed invalidity for indefiniteness of "best"/"optimal" terms and non-infringement of the surviving claims. (Finnegan, VitalLaw)
• Practically, because US 6,754,699 expired on 2020-08-18 (anticipated expiration), any live 2026 dispute would have to be a damages claim for past infringement or a collateral/ownership issue rather than injunctive relief — but I found no evidence of any such pending matter.

Bottom line: The bibliographic data, assignee chain, and technology are well-grounded in the authoritative text; the verbatim abstract and independent-claim wording are not verified, and no CAFC 2026 activity tied to 6,754,699 exists in the sources I could reach.

I'll search for litigation involving US patent 6754699.

Let me search more specifically on litigation databases.

I found key leads. Let me dig deeper into the Akamai v. Speedera case and check for any post-acquisition assertions.

Litigation Involving U.S. Patent No. 6,754,699

Caveat up front: My search tool could not access PACER, the Unified Patents litigation portal, or RPX Insight case pages directly — I could only see search-engine snippets of those sources. So the following is what I could verify from citable snippets, with the evidentiary limits noted. I did not find any litigation in which 6,754,699 was asserted after Akamai acquired it.

What the patent is

• 6,754,699 B2 — "Content delivery and global traffic management network system"
• Inventors: Eric Sven-Johan Swildens, Richard David Day, Ajit K. Gupta
• Original assignee: Speedera Networks, Inc. (Santa Clara, CA)
• Priority date 2000-07-19; application 09/909,651 filed 2001-07-19; granted 2004-06-22
• Later assigned to Akamai Technologies, Inc. via "Certificate of Ownership & Merger" recorded 2006-03-16 (Google Patents assignment record)

This is the patent that Akamai's own SEC filings describe as Speedera's patent "relating to the combined provision of traffic management and content delivery services."

Known litigation

1. Akamai Technologies, Inc. v. Speedera Networks, Inc. (patent case; '699 asserted by Speedera as a counterclaim)

Source: RPX Insight docket summary (insight.rpxcorp.com/litigation/madce-86351-akamai-technologies-v-speedera-networks).

Akamai's SEC disclosure ties the counterclaim to the '699 subject matter:

"In response, Speedera filed a counterclaim in this case alleging that Akamai has infringed a Speedera patent relating to the combined provision of traffic management and content delivery services. In June 2004, Speedera amended its counterclaim to include a second patent covering a similar service it offers."
— Akamai SEC filing (akamai.gcs-web.com/static-files/6f7d1369-994d-4c72-823a-a614f5ad3087)

Because 6,754,699 issued 2004-06-22, it fits precisely the "second patent" added by Speedera's June 2004 amendment. However, I could not confirm from a primary source (the amended counterclaim or a docket naming the patent number) that 6,754,699 — rather than a sibling in the same Speedera family (e.g., 6,484,143; 7,363,361; 7,194,522) — is the specific patent asserted. I am flagging that as a genuine evidentiary gap rather than asserting it.

2. Earlier Akamai v. Speedera patent suit (D. Mass., 2002)

• Akamai filed suit against Speedera in February 2002 in Massachusetts federal court for patent infringement and false advertising; Speedera counterclaimed with the Speedera patent on combined traffic-management/content-delivery services. (Akamai SEC filing, above.) I did not confirm the case number for this earlier-filed action; it may be the same litigation stream that surfaced as 1:03-cv-10934.

3. Akamai Technologies, Inc. v. Speedera Networks, Inc. (California state court; trade-secret case — not a '699 patent case)

• Filed June 2002, San Francisco Superior Court; alleged theft of Akamai trade secrets from Keynote Systems. Speedera filed a cross-claim (unfair competition, false advertising, trade libel). Preliminary injunction issued Sept. 2002 restraining Speedera. This matter involved no patent and is included only as context for the parties' overall dispute.

4. Resolution (all matters)

• Akamai announced it would acquire Speedera Networks in an all-stock deal valued at ~$130 million; the parties agreed to drop the pending litigation upon closing. (Law.com, "Akamai, Speedera End Legal Fight"; the merger is the transaction recorded as the 2006-03-16 assignment of 6,754,699 to Akamai.)

Post-acquisition

I found no litigation, PTAB/IPR proceeding, or assertion involving 6,754,699 after Akamai's 2006 acquisition. In particular:

• No NPE/patent-assertion campaign naming this patent appeared in any result.
• No IPR/PGR at the PTAB for 6,754,699 appeared in the Unified Patents / Lex Machina-derived listings I retrieved.

Notes on excluded results

Search terms also returned hits for an unrelated "'469 patent" in TWW, Inc. v. Intex Recreation (D.D.C., pneumatic air-bed pumps; citing U.S. Patent numbers like 6,793,469 in a different family). Per your instruction not to auto-correct or conflate identifiers, those are different patents and are excluded from the list above.

Bottom line

The only patent litigation connected to the 6,754,699 subject matter is the Akamai v. Speedera dispute (D. Mass., including 1:03-cv-10934), in which Speedera counterclaimed on its content-delivery/traffic-management patent(s) and which ended in Akamai's 2005–2006 acquisition of Speedera. I could not verify to a primary-source standard that 6,754,699 itself (versus a sibling Speedera patent) was the instrument asserted.

I'll start by verifying whether any AIA trial proceedings exist for this patent, since the structured ODP block reports none.

Search results so far are noisy. Let me target PTAB dockets and litigation directly.

Proceedings overview

Total AIA trial proceedings on US 6,754,699: 0. Breakdown: 0 active, 0 claims invalidated, 0 claims sustained, 0 settled, 0 institution denials — because no IPR, PGR, or CBM petition has ever been instituted or, on the evidence I could locate, ever filed against this patent. The bottom line for a defendant is therefore not a PTAB story: it is that US 6,754,699 expired on 2020-08-18 per the Google Patents bibliographic record ("Anticipated expiration 2020-08-18"; status "Expired - Lifetime"), which extinguishes the § 286 damages look-back for any complaint filed today (see Strategic summary).

Proceedings on file

No proceeding exists — template fields, explicitly

I am not supplying the per-proceeding template because there is no proceeding number to populate and I will not manufacture one. For the record, every requested field is empty for this patent:

• Type (IPR/PGR/CBM): none filed.
• Filed / Status / Judge panel: N/A.
• Petition grounds: N/A. No petitioner has challenged any claim of '699 under § 102, § 103, or § 112 at the Board.
• Institution decision: N/A.
• Final Written Decision: N/A. No claim of '699 has been canceled, confirmed, or held unpatentable by the PTAB.
• Settlement / termination: N/A.
• Appeal: N/A. No FWD, hence nothing appealable under 35 U.S.C. § 319; no CAFC docket.
• Defensive value: see below.

How I checked (and the limits of that check)

• The structured "PTAB proceedings on file" block you supplied — sourced from the USPTO Open Data Portal — returns no AIA trial proceedings for this patent as of the most recent ingest. I treat that as canonical.
• I ran web searches for the patent number paired with IPR, PTAB, final written decision, and the patent-owner/petitioner names. No IPR/PGR/CBM docket, institution decision, or FWD referencing US 6,754,699 surfaced. Hits were bibliographic only (IDS citations of '699 as prior art in later patents, family-member listings in foreign search reports).
• One caution worth flagging so you don't get misled by secondary sources: several PTAB document hits involving the name Eric Swildens concern a completely different subject matter — Swildens' personal ex parte reexamination of Waymo's lidar patent US 9,368,936 (unrelated to '699). Likewise, USPTO PTACTS documents referring to a "'675 Patent" in the search results are different patents (e.g., an antibody-drug-conjugate family), not US 6,754,699. Neither is a proceeding on this patent.
• I found no ex parte reexamination of '699 either, but I could not verify that negatively from the sources available to me — treat reexam status as unconfirmed and check the '699 file wrapper in USPTO Patent Center (https://patentcenter.uspto.gov/) before relying on it.

Flag as required: nothing older or recently filed was surfaced that the ODP missed. If a petition were filed on a date after the ODP ingest, I would have no way to see it here; verify directly at PTAB E2E (https://ptacts.uspto.gov/ptacts/).

Strategic summary

Claim status: nothing canceled, nothing sustained, everything untested — but all of it expired. Because no AIA trial or reexamination certificate touched this patent, the claim set stands exactly as issued on 2004-06-22, and there are no surviving-claim lists, no adverse-judgment claims, and no certificate of cancellation to point to. The operative event for a defendant is not a validity ruling but the term: priority traces to application 09/641,746 filed 2000-08-18, and the record shows the patent expired 2020-08-18. That has two consequences. First, injunctive relief is off the table — there is no ongoing infringement to enjoin. Second, and more important for a demand letter, 35 U.S.C. § 286 caps damages at six years before the complaint; a complaint filed on or about today's date (2026-09-29) reaches back only to 2020-09-29, which is after the 2020-08-18 expiration. On that arithmetic the recoverable-damages window is empty. Caveat, and it matters: confirm the expiration date with Patent Term Adjustment and any terminal disclaimer in Patent Center — Google's "anticipated expiration" figure is bibliographic. Each month of PTA would open a sliver of damages window, so run the date rather than assuming it.

Estoppel landscape: there is none. Because no IPR/PGR/CBM was ever instituted, § 315(e)(2) estoppel was never triggered against anyone, and no petitioner or privy is barred from raising any § 102/§ 103 ground. Practically, that cuts both ways. A defendant currently accused has the entire prior-art toolkit available in district court with no PTAB-induced narrowing of grounds and no IPR estoppel admissions — but that freedom is largely academic for '699 itself, since invalidating an expired patent buys you little once your § 286 exposure is zero. Where the free toolkit does pay off is against the live family members (below), and against any theory that a demand letter's citation of '699 is a stalking horse for those.

Pattern signals: quiet. No repeat petitioner, no serial IPR campaign against this patent, no defensive-aggregator (Unified Patents or similar) activity that I could find, and no PTAB-to-CAFC appeal chain. The absence is itself informative in the way you'd expect: '699 is a 2000-priority, 2020-expired patent whose commercial assertion value decayed before the 2012-2020 IPR boom matured, so there was never much incentive to spend $500K invalidating it. The real asset is the continuation family, all claiming priority back through this chain and several still in force: US 7,194,522; 7,574,499; 7,484,002; 7,743,132; 7,979,580; 7,904,541; 8,341,278; 8,204,976; 8,612,564; 9,026,661; 10,106,694; 10,511,567; and 11,283,715 (all naming Swildens et al., assignee Akamai Technologies, Inc. via the 2006-03-16 Certificate of Ownership & Merger from Speedera). If a live continuation is asserted against you, this patent is your prior art: the '699 specification and its pre-grant publication US 2002/0052942 A1 (published 2002-05-02) are § 102(a)/(b) art against later-claimed subject matter, and the CIP relationship means you should map which '699 disclosure actually supports which later claims. Obviousness-type double patenting across the family is a second, often-underused lever.

Recommended next steps

1. If you received a demand letter citing US 6,754,699, the first response is a term/standing point, not a validity point. Pull the Patent Center file wrapper, confirm the exact expiration date including PTA and any terminal disclaimer, and compute the § 286 window from your anticipated filing date. If the window is empty, say so in writing: no damages, no injunction, and no reason for the patent owner to press the '699 theory.
2. Link to primary sources, not to a non-existent FWD. There is no PTAB Final Written Decision to quote for this patent — do not let an adversary or a form brief imply otherwise. Cite (a) the Google Patents bibliographic record for the expiration/status: https://patents.google.com/patent/US6754699/en , and (b) USPTO Patent Center for the authoritative term and reexamination status: https://patentcenter.uspto.gov/ . For a negative PTAB check, cite PTAB E2E: https://ptacts.uspto.gov/ptacts/ .
3. No active proceedings means no trial-stage milestones to track. If, contrary to this report, a petition is filed after the ODP ingest, the clocks are: POPR due 3 months, institution decision due within 6 months of the petition's filing (35 U.S.C. § 314(b)), and FWD due within 12 months of institution (§ 318(a)), extendable up to 6 months for good cause. Remember Thryv, Inc. v. Click-To-Call Techs., LP, 140 S. Ct. 1367 (2020): a § 315(b) non-institution decision is not appealable. Note also that PGR is unavailable (pre-AIA patent; the 9-month window closed in 2005) and CBM is unavailable (the program sunset on 2020-09-16 and a content-delivery patent likely fails the "covered business method" test regardless), so IPR is the only AIA vehicle left — and a live § 315(b) one-year bar starts the day you are served.
4. Do not treat the '699 demand as the whole threat. Map the demand letter's hostnames/claims onto the live continuations (especially 10,106,694, 10,511,567, and 11,283,715). If the same accused functionality is being pointed at, prepare the invalidity case now in district court — you have no § 315(e)(2) estoppel and no prior IPR estoppel constraints, so grounds can be developed freely. The '699 specification, the 2002-05-02 pre-grant publication, and the parent 09/641,746 / US 6,484,143 disclosure are the natural starting points.
5. State the null result plainly in any internal memo: "No PTAB activity on US 6,754,699 as of 2026-09-29; patent expired 2020-08-18 (verify PTA); § 286 window likely empty." That is the honest posture, and it is a stronger defensive position than an IPR win would have been.

I'll start by pulling what I can from the authoritative text and searching for the underlying assignment records.

Ownership Reconstruction — US 6,754,699 B2

Patent: "Content delivery and global traffic management network system" · App. 09/909,651 · filed 2001-07-19 · issued 2004-06-22 · status Expired – Lifetime

Data-provenance caveat (read before the timeline): I reconstructed this chain from the authoritative Google Patents legal-events feed (which mirrors USPTO assignment data) and from the patent's own front matter, plus SEC/EDGAR and contemporaneous press for the corporate-side facts. I was not able to complete a live pull of the USPTO Assignment Center record in this session, so the reel/frame numbers and the correspondent-of-record names are NOT in hand. I have deliberately left those fields marked as not retrieved rather than inventing them. Metadata confirmed: six recorded post-issuance events between 2001 and 2006.

Inventors

Pattern notes:

• All three inventors assigned to the same employer they worked for — this is a clean employee/founder assignment, not a case of inventors holding personally and later selling. The 2001-09-27 recording names all three individually as assignors to Speedera Networks, Inc.
• No pre-filing or near-filing departure signal. Although Gupta and Day were founders with the strongest incentive to leave post-acquisition, both were still with Speedera at the time of the Akamai deal; Akamai's Paul Sagan publicly stated Gupta would remain through the transition (CNET, 2005-03-16). Departure dates for Day and Swildens are not determinable from retrieved sources, so I cannot confirm or rule out the "all inventors depart within 12 months" fire-sale precursor. Nothing in the record suggests it.
• The Akamai 10-K for FY2004 confirms the corporate antagonism: Speedera counterclaimed in the Massachusetts case alleging Akamai infringed "a Speedera patent relating to the combined provision of traffic management and content delivery services" — i.e., this family — and added a second such patent in June 2004 (Akamai FY2004 10-K).

Original assignee

Speedera Networks, Inc. — Delaware corporation, HQ Santa Clara, California, plus a wholly-owned India subsidiary (Bangalore); founded in the late 1990s.

• Did it ship a product embodying the claims? Yes, unambiguously. Speedera operated a commercial content delivery network with a Global Traffic Management product line (DNS-based routing, latency/service probes, POP-based caching) — this specification reads as a description of that shipping platform, down to named components (SPD, NetProbes, WebCache, SERVPD, LATNPD, SPKT, LOGP). No software or hardware was required at the customer site; it was sold as an outsourced service.
• Primary line of business: distributed application hosting and content delivery / traffic management services. Disclosed customers included DoubleClick, Fox Broadcasting, Macromedia, NASA, McAfee, Univision, AMD and Lowe's (CNET/Law.com, March 2005). Reported ~$8.3M revenue in Q4 2004; ~$25–27M trailing-twelve-month revenue; >$36M venture funding raised.
• Current status: Acquired and dissolved as an independent entity. Akamai announced a definitive merger agreement on 2005-03-16, closed 2005-06-10, and Speedera became a wholly-owned Akamai subsidiary; ~12 million Akamai shares issued, deal valued ≈$130M in stock (Akamai Form 8-K, Ex. 99.1/99.2, filed June 2005; SEC EDGAR). All pending Akamai↔Speedera litigation was stayed at signing and dismissed at closing. Speedera was not in bankruptcy.
• Note on investor collateral (important for reading the record): Hewlett-Packard, Comdisco Ventures, Oracle, Deutsche Bank, Banc of America Securities and others participated in Speedera's 2001 $20M round; Comdisco Ventures separately invested $10M in 2000 (Law.com, 2005-03-16). This is why HP and Comdisco appear in the assignment chain as secured/creditor parties, not as patent owners.

Assignment timeline

All six events below are recorded in the Google Patents legal-events feed for US 6,754,699 B2 (source: patents.google.com/patent/US6754699B2/en). Execution dates, reel/frame numbers, and correspondents were not exposed in the sources retrieved.

• Executed date not exposed / recorded 2001-09-27 — Reel not retrieved

  • Conveyance: Assignment of assignors' interest
  • Assignor: Richard David Day; Ajit K. Gupta; Eric Sven-Johan Swildens (individually)
  • Assignee: Speedera Networks, Inc.
  • Correspondent: not retrieved — cannot be assessed for recurrence.
  • Context: Ordinary founder/employee assignment of the invention to the operating company, contemporaneous with the 2001-07-19 filing.

• Executed date not exposed / recorded 2002-03-26 — Reel not retrieved

  • Conveyance: Amendment to Security Agreement
  • Assignor: Speedera Networks, Inc.
  • Assignee: Hewlett-Packard Company
  • Correspondent: not retrieved.
  • Context: Securitization, not acquisition — HP was an investor in Speedera's 2001 round; this perfects/amends a collateral interest. No ownership transferred.

• Executed date not exposed / recorded 2003-02-05 — Reel not retrieved

  • Conveyance: Assignment and Release
  • Assignor: Speedera Networks, Inc.
  • Assignee: Hewlett-Packard Company
  • Correspondent: not retrieved.
  • Context: Release/clearing of the same HP collateral position — again a security instrument, not a purchase.

• Executed date not exposed / recorded 2006-02-02 — Reel not retrieved

  • Conveyance: Discounted Payoff Agreement
  • Assignor: Comdisco, Inc.
  • Assignee: Speedera Networks, Inc.
  • Correspondent: not retrieved.
  • Context: Creditor wind-down / payoff — Comdisco Ventures was a 2000 investor in Speedera; this records the discounted payoff and return of any collateral interest to Speedera. (Comdisco, Inc.'s own corporate distress in the 2001–2002 period is public; the record here is a payoff, not a sale of the patent.)

• Executed date not exposed / recorded 2006-02-02 — Reel not retrieved

  • Conveyance: Settlement and Release Agreement
  • Assignor: Hewlett-Packard Company
  • Assignee: SPPEEDERA NETWORKS, INC. (the record literally reads "SPPEEDERA" — a typo in the source data; interpreted as Speedera Networks, Inc.)
  • Correspondent: not retrieved.
  • Context: Final settlement/release of the HP collateral interest, recorded the same day as the Comdisco payoff — post-merger title cleanup so the acquirer takes an unencumbered record.

• Executed date not exposed / recorded 2006-03-16 — Reel not retrieved

  • Conveyance: Certificate of Ownership and Merger
  • Assignor: Speedera Networks, Inc.
  • Assignee: Akamai Technologies, Inc.
  • Correspondent: not retrieved.
  • Context: Acquisition closure on the record. The merger itself closed 2005-06-10 (8-K); the certificate was recorded ~9 months later, after the HP/Comdisco releases cleared the collateral. This is the terminal ownership event.

Reel/frame and correspondent: not available from the sources retrieved. To close this gap, search 6754699 at the USPTO Assignment Center or the USPTO Patent Assignment Search and read the "Correspondent" and "Reel/Frame" columns on each of the six rows above. Recurrence of a single correspondent across the 2002-03-26, 2003-02-05, 2006-02-02 (×2) and 2006-03-16 entries would be the only place in this chain where the "repeat recording attorney" signal could even arise.

Family context (supports the chain read): the same Speedera priority family — US 6,484,143, 7,194,522, 7,363,361, 7,484,002, 7,574,499, 7,743,132, 7,904,541, 7,979,580, 8,201,976, 8,341,278, 8,612,564 — all moved with the same 2006-03-16 merger certificate and are today listed to Akamai. No continuation, divisional, or CIP in the family was peeled off into a separate holding entity.

Timeline diagram

timeline
    title Ownership of US 6754699
    2001 : Inventors assign to Speedera Networks
         : Application filed 19 Jul 2001
    2002 : HP security agreement recorded
    2003 : HP assignment and release recorded
    2004 : Patent issues 22 Jun 2004
    2005 : Akamai acquires Speedera 10 Jun
    2006 : Comdisco discounted payoff recorded
         : HP settlement and release recorded
         : Merger certificate to Akamai recorded

NPE / troll-pattern signals

1. Shell-entity transfer — not present. No "IP / Patents / Licensing / Holdings / Ventures" entity appears anywhere in the six recorded events. Every assignee is an operating corporation: Speedera Networks, Inc. (operating CDN), Hewlett-Packard Company (secured creditor), Comdisco, Inc. (creditor), Akamai Technologies, Inc. (operating CDN). The 2006-03-16 Certificate of Ownership and Merger runs from an operating company to an operating company.

2. Known asserter in the chain — not present. No assignee matches Acacia, Marathon Patent Group, Intellectual Ventures, IPNav, Wi-LAN, Mosaid/Conversant, Vringo, Pendrell, Innovatio, MPHJ, Lumen View, Round Rock, Document Generation Corp or any Erich Spangenberg entity. Watch-out: Google Patents lists "HP Inc." among the current assignees. That listing is an artifact of Google's parser reading the secured party field on the 2002-03-26 and 2003-02-05 security instruments; the HP interest was released (2003-02-05 "Assignment and Release" and 2006-02-02 "Settlement and Release Agreement"). HP Inc./Hewlett-Packard is not an owner of this patent. Also note Comdisco, Inc. is a commercial leasing company, not an NPE.

3. Repeat correspondent across the chain — unclear (not assessable). The correspondent of record was not exposed in the sources retrieved, so I can make no finding either way. Structurally this chain has the shape where recurrence would be expected — the two 2006-02-02 releases and the 2006-03-16 merger certificate were all filed in the same post-closing cleanup window and were very likely handled by one firm — but "very likely" is not evidence and I am not recording it as a signal. Pull the correspondents from Assignment Center to resolve.

4. Cascading transfers — not present. The chain spans roughly 4.6 years (2001-09-27 → 2006-03-16) and contains zero transfers between affiliated holding entities. The single same-day pair (2006-02-02) is two releases back into Speedera, not two onward conveyances — the opposite of a cascade. The only ownership change in the entire record is the single Akamai merger step.

5. Pre-litigation transfer — not present. The nearest event to litigation is the 2006-03-16 merger certificate, ~9 months after the 2005-06-10 closing, and it post-dates rather than precedes assertion. No assertion of US 6,754,699 is documented at all. The record actually runs the other way: Speedera, as the then-owner, counterclaimed against Akamai on a sibling patent, US 6,484,143 ("User Interface Device and System for Traffic Management and Content Distribution…"), per the Akamai v. Speedera claim-construction order, D. Mass. No. 02-12226-RWZ, 2003-12-29, and Akamai's 10-K confirms a second Speedera patent was added to that counterclaim in June 2004. That is operating-company assertion, not NPE staging.

6. Bankruptcy fire-sale — not present as to this patent. Speedera was solvent and profitable at the time of the Akamai deal; the transaction was a $130M stock merger, not a §363 sale. Adjacent context worth flagging but not a finding: Comdisco — a Speedera investor — was itself in corporate distress in the early 2000s, and the 2006-02-02 "Discounted Payoff Agreement" recording is consistent with a creditor estate's discounted wind-down. Critically, that instrument runs Comdisco → Speedera, i.e., rights returned to the patent owner rather than sold out of an estate. The patent was never sold in a bankruptcy proceeding.

7. Privateering — not present. Akamai acquired Speedera's family and dismissed the litigation as part of the same transaction (stay on signing 2005-03-16; dismissal at closing), and it retained the portfolio. Akamai asserts CDN patents in its own name against direct competitors — Akamai v. Limelight Networks (the '703 patent, jury verdict $45.5M, D. Mass.), Akamai v. MediaPointe (C.D. Cal., Fed. Cir. appeal 2025). No transfer to a proxy asserter is present or hinted at, and no SEC disclosure or Patent Progress/EFF-style coverage of an Akamai-to-NPE transfer exists in the retrieved record.

8. Defensive aggregator — not present. The chain terminates at Akamai Technologies, Inc., an active litigant and product company. No RPX, AST, LOT Network, Unified Patents or OIN entity appears at any point.

Verdict

Operating-company assertion.

The entire six-event chain (recorded 2001-09-27 → 2006-03-16) consists of a founder-to-operating-company assignment, two investor collateral instruments (HP 2002-03-26 / 2003-02-05), two creditor releases back to the patent owner (Comdisco and HP, both 2006-02-02), and one genuine ownership change — the 2006-03-16 Certificate of Ownership and Merger conveying Speedera Networks, Inc. to Akamai Technologies, Inc., an operating CDN/GTM vendor whose products practice these claims and which litigates in its own name against actual CDN competitors. There is no shell LLC, no known NPE, no chained conveyance, no bankruptcy sale, no defensive-aggregator terminus, and no evidence of pre-assertion transfer; the one documented assertion of this patent family, against Akamai on sibling US 6,484,143, was made by the original operating assignee while it still owned the patents. Two qualifications you should carry forward: (a) the patent's anticipated expiration was 2020-08-18 and its legal status is Expired – Lifetime, so current assertion risk is moot; and (b) I could not retrieve the reel/frame numbers or the correspondents of record, so signal 3 is genuinely untested rather than negative — if you need that closed, run the patent number through the USPTO Assignment Center and compare the correspondent column across the 2002-03-26, 2003-02-05, and 2006-02-02/2006-03-16 rows.

I'll research the prior art citations for US 6,754,699 across available sources.

Let me try to retrieve the actual "References Cited" list for US 6,754,699 from primary sources.

Let me try to pull the actual front-page "References Cited" list from FreePatentsOnline and other full-text mirrors.

Search report: US 6,754,699 — prior-art citations

Scope note / date discrepancy: Your task preamble says "Current Date: April 26, 2026," while the session clock says 2026-09-29. I flag it rather than resolve it; neither changes the analysis below.

1. Patent identified (literal, no auto-correction)

This is the number you asked for — I did not return near-misses such as 6,754,706, 6,694,358, 6,484,143, 6,793, etc., except where they are relevant as family or citation data.

2. ⚠️ Critical verification failure — I could NOT retrieve the item (56) "References Cited" list

I must be explicit: I was unable to retrieve the verbatim front-page "References Cited" (35 U.S.C. § 102 citation) list of US 6,754,699 in this session. Therefore I cannot honestly give you "each patent citation for 6754699" with per-reference claim mapping. Here is exactly what happened, so you can judge the gap:

• The authoritative full text you supplied (Google Patents scrape) truncates before the "Patent Citations" section — the supplied text ends inside the SERVP/log-file-naming disclosure, before the citation table.
• Google Patents renders the examiner/applicant citation list as a separate table from the description; that table was not captured in the fetch.
• My web_search tool returns result snippets, not full page renders. My targeted queries for the '699 citation table returned (a) classification hierarchies, (b) another patent's citation table, and (c) "cited-by" lists — none of which is the '699 item (56) list.
• One search result that superficially looked like it belonged to '699 was headed "Providing uninterrupted media streaming using multiple network sites" with a "Patent Citations (11)" table listing US 6,112,239, US 5,996,015, US 6,363,260, US 2001/0052016, US 2001/0029544, US 2002/0009079, etc., ending with US 6,754,699 B2 as the final row (URL: patents.google.com/patent/US20030005040A1/en#5). Because the table contains 6,754,699, it is the citation list of US 2003/0005040 A1, not of '699. I am flagging this so you do not mistake it for the '699 list — several aggregator snippets blur these tables together.

Consequence: Any list I gave you of "the references cited in 6,754,699" would be reconstruction from the general CDN prior-art landscape, not document-verified. I am labeling every item below accordingly rather than fabricating a § 102 table.

3. What I could verify, and why it matters for § 102

(a) The '699 critical date is not simply "2000-07-19." This is a flagged contradiction with the previously generated section, which stated the prior-art date as 2000-07-19 from the front page. The Google Patents family data shows:

• US 09/641,746, a continuation-in-part parent, priority 1999-11-22, filed 2000-08-18, issued as US 6,484,143 B1 ("User device and system for traffic management and content distribution over a world wide area network").
• US 09/909,651 ('699) filed 2001-07-19, and US 10/873,570 (continuation, → US 7,194,522 B1) filed 2004-06-21.
• Google's listed "Prior art date" is 2000-07-19, but the CIP parent was filed 2000-08-18 — an internal inconsistency in the record.

Why it matters: § 102(a)/102(e) and § 103 critical-date analysis for a CIP depends on which claims are supported by the earlier parent. A reference published between 1999-11-22 and 2001-07-19 may or may not qualify as prior art per claim. Do not assume a single critical date.

(b) Family/priority relatives (not prior art, listed to prevent mis-citation): US 6,484,143 B1; US 7,363,361; US 7,194,522; US 7,574,499; US 7,484,002; US 7,743,132; US 7,979,580; US 7,904,541; US 8,341,278; US 8,204,976; US 8,612,564; plus sibling/appurtenant US 6,694,358; US 6,754,706; US 7,225,254; US 7,523,181; US 7,406,512; US 7,143,170 — all sharing the Swildens et al. priority line and therefore § 102-insulated by common ownership/priority, not citable against '699.

(c) The co-citation landscape (document-verified as cited elsewhere, NOT verified as cited in '699): The same CDN prior-art cluster appears in the "References Cited" lists of later CDN patents that also cite US 6,754,699:

• US 8,452,874 — "(56) References Cited": US 5,774,660 A (6/1998, Brendel et al.); US 6,108,703 A (8/2000, Leighton et al.); US 6,185,598 B1 (2/2001, Farber et al.); US 6,754,699 B2
• US 9,734,472 — same four, plus US 6,529,910 B1 (3/2003, Fleskes); US 6,529,953 B1 (3/2003, Van Renesse); US 6,553,413 B1 (4/2003, Leighton et al.)
• US 8,688,837 — US 5,774,660; US 6,108,703; US 6,185,598; US 6,754,699

This is the strongest documentary signal available to me, but it establishes only that these references belong to the same art cluster — not that the '699 examiner cited them.

4. Candidate prior art — confidence-labeled (PROVISIONAL; verify against the '699 PDF before relying)

⚠️ Items 5–8 publish after 2001-07-19 (the '699 filing date) and therefore cannot be § 102(b) art against '699; if cited at all, they would be examiner/IDS art under § 102(e) as earlier-filed applications, which requires the actual filing dates — which I have not verified. Do not treat any row above as an established citation without pulling the document.

Commonly raised-in-the-art references I could not verify appear in '699's list, and which I therefore omit from the table rather than guess: US 6,006,264 (Colby); US 6,167,427 (Rabinovich); US 6,167,438 (Yates); US 6,185,619 (Jerger); US 6,052,718 (Gifford); US 6,134,588 (Guenthner); US 6,286,043 (Cuomo); US 6,003,030 (Kenner).

5. Provisional § 102 mapping (claim-group level only)

Because neither the '699 claim set nor the (56) list is verified in this session (see the prior section's identical caveat), I can only give a framework, using the specification's own two aspects as claim groups. Anticipation requires every element of a claim in a single reference, arranged as claimed.

6. 2026 activity I did find (flagged; NOT verified as involving 6,754,699)

Two 2025–2026 dockets surfaced that are in the Speedera/Sandpiper family orbit, and you should be aware of them even though neither is confirmed to involve '699:

• IPR2026-00095, Microsoft Corporation v. Sandpiper CDN LLC (PTAB), surfaced via a Docket Alarm exhibit citing, inter alia, US 10,924,573 B2 and US 2005/0033858 A1 (Swildens).
• Sandpiper CDN, LLC v. Google LLC, No. 2:24-cv-03951 (complaint, Dkt. 45) — same exhibit.
• A D. Mass. filing (gov.uscourts.mad.104015.407) briefs inequitable-conduct allegations concerning a Leighton "703" CDN patent, Sandpiper, and the Footprint 1.0 CDN / Farber PCT — i.e., the classic Akamai v. Digital Island prior-art fight, tangential to '699; I could not verify the docket number or parties.

⚠️ I could not confirm that US 6,754,699 itself is asserted or challenged in any of these. Also note '699's record shows "Expired – Lifetime," anticipated expiration 2020-08-18, so any 2026 dispute would be backward-looking damages or collateral. The prior section's finding of no CAFC 2026 docket for 6,754,699 stands.

7. Contradictions with the previously generated section

1. Priority date: The prior section reported "2000-07-19 (as listed on the front page)." The family record shows a CIP parent US 09/641,746 with priority 1999-11-22, filed 2000-08-18 (issued 6,484,143). The 2000-07-19 figure sits between those dates and does not match the parent's filing date. This must be resolved before any § 102(b) analysis — flagging it as an open discrepancy.
2. Assignee list: Consistent (Speedera → Akamai). No contradiction.
3. Claim wording: Prior section flagged the claim text as unverified; that remains true, so the § 102 mapping in §5 above is delivered at claim-group level only.

8. How to close the verification gap (recommended next steps)

To complete this task authoritatively, pull the item (56) list and claim set from primary documents:

1. USPTO PatentCenter → Application 09/909,651 → "Patent Full-Text (PDF)," page 1 (item (56)) and the claims.
2. Google Patents patents.google.com/patent/US6754699B2/en → expand the "Patent Citations" section (distinct from "Cited By" and from the other patent's table noted in §2).
3. Cross-check the IDS/SB-08 in the file wrapper (PatentCenter "Documents & Transactions") to separate examiner-cited from applicant-disclosed art — this matters because examiner citations and IDS citations carry different evidentiary weight.

Bottom line: Patent 6754699 = US 6,754,699 B2 confirmed and correct. I did not obtain the verified item (56) citation list, so I have given you a confidence-labeled candidate set drawn from document-verified co-citation data (Brendel '660, Leighton '703/'413, Farber '598, Fleskes '910, Van Renesse '953, Kenner '239), a provisional claim-group § 102 framework, and an explicit warning that the 11-row citation table sometimes attributed to '699 actually belongs to US 2003/0005040 A1.

I'll research the prior art landscape for this patent. First, let me note what "Prior Art" material was actually supplied on the page, then search for the contemporaneous references.

Good — that surfaced the PTAB/Akamai ecosystem. Now let me verify the key candidate references and check whether the '699 itself was ever challenged.

Obviousness Analysis — U.S. Patent No. 6,754,699 B2 under 35 U.S.C. § 103

0. Threshold caveats — please read first

⚠️ There is no "Prior Art section" on the supplied page to work from. The Google Patents record you provided contains only:

• "Prior art keywords": server; servers; dns; network; content — i.e., an examiner/Google-generated keyword list, not a reference list.
• One prior-art cross-reference: the "external-priority" link US09/641,746 → US 6,484,143 (2000-08-18), a same-family Speedera application.
• No "References Cited" block, no IDS list, and no Non-Patent Citations list appear anywhere in the fetched text.

Accordingly, the combination grounds below are constructed from (i) the '699 specification's own admissions about the state of the art, and (ii) contemporaneous references I verified by web search in this session. Every reference is tagged with its verification status. This is not the patent's prosecution record, and I flag that plainly rather than implying otherwise.

⚠️ Second caveat — no verbatim claim text. I could not retrieve the certified claim set this session. The analysis therefore maps references to representative claim elements drawn from the specification's stated subject matter. Treat the element-level correspondence as provisional; an element-by-element § 103 chart requires the issued PDF.

⚠️ Third caveat — priority-date ambiguity. The front page lists a prior-art date of 2000-07-19 and an external priority claim to US09/641,746 filed 2000-08-18, with the '699 itself filed 2001-07-19. The likely explanation is a provisional at 2000-07-19 plus a non-provisional at 2000-08-18, but the supplied text does not resolve it. This matters, because Leighton (US 6,108,703) issued 2000-08-22 — after 2000-07-19 but before the 2001-07-19 filing — so its § 102 hook is § 102(e) as of its 1999-05-19 filing date, not § 102(b). Flagging this because it is exactly the kind of date argument a patentee would press.

1. Legal framework (pre-AIA)

The application was filed 2001-07-19; the AIA first-inventor-to-file provisions (35 U.S.C. §§ 102/103 as amended) do not apply. Governing law:

• Pre-AIA § 103(a); Graham v. John Deere Co., 383 U.S. 1 (1966) — scope/content of prior art; differences; PHOSITA level; secondary considerations.
• KSR Int'l Co. v. Teleflex Inc., 550 U.S. 398 (2007) — a combination of known elements is obvious where it yields predictable results; "obvious to try" is a valid rationale; the TSM test is not the sole test.
• MPEP §§ 2141–2144.04 — enumerated rationales: (A) known elements combined by known methods → predictable result; (B) simple substitution of one known element for another; (C) known technique used to improve a similar device in the same way; (D) applying a known technique to a known device ready for improvement; (E) "obvious to try" from a finite number of identified, predictable solutions; (F) design incentives/market forces; (G) predictable variation.
• Status note: the '699 is Expired – Lifetime (anticipated expiration 2020-08-18). A 2026 § 103 analysis is therefore retrospective — a validity defense to past-damages exposure or an inter partes challenge — not an injunction fight. My separate search for a PTAB/IPR naming the '699 itself was cut off by a tool limit and is therefore inconclusive; I found no IPR on the '699 in the results that did return, but do not treat that as a clean bill of health.

2. The claimed subject matter decomposed into element sets

From the specification (authoritative text supplied), the disclosure splits cleanly into a content-delivery (CDN) set and a global-traffic-management (GTM) set.

Element Set A — CDN / pull-through caching

Element Set B — GTM / DNS-based selection

Element Set C — service/business method

3. Prior art references verified this session

References I know of but did NOT verify this session ⚠️

Treat these as corroborating context only, not as asserted § 103 grounds:
Cisco DistributedDirector (DNS-based GSLB with proximity/availability and session "sticky" behavior, ~1997–98); Resonate Global Dispatch / Central Dispatch; F5 3DNS / BIG-IP; Alteon; IBM Network Dispatcher; Squid/Harvest proxy caches (1994–96); BIND zone delegation and round-robin (RFC 1034/1035); HTTP If-Modified-Since (RFC 1945, 1996); traceroute/ICMP latency measurement (Jacobson, 1987); IDMaps (1998); Network Weather Service (1996+).

Two recollection corrections (per your ground-truth rule)

1. I had recalled US 6,052,718 as Gifford's "common name server for a plurality of mirrored Web servers." The search results return it as "Replica routing," Sightpath, Inc. I follow the search results.
2. I had recalled US 6,243,761 as Yarom & Natan's resource-binding load-balancing patent. *The results return 6,243,761 as Mogul et al., issued 2001-06-05.* I have dropped the Yarom reference entirely rather than restate it.

The patent's own admissions (usable as § 103 evidence)

The specification itself supplies much of the attack:

• "Load balancers use a variety of techniques…" / "Domain name-server-based round-robin address resolution causes different clients to be directed to different mirrors" (this language tracks Farber '598's own background — same admitted art).
• "the periodic checking is a common feature of caches" and "the cache can look at expiry headers… to ensure freshness."
• LOADP, traceroute-style UDP-high-port probing, ping, and reverse DNS lookup are each described as known named techniques. A reference that names a technique as conventional is an admission of what a PHOSITA knew.

4. Level of ordinary skill (PHOSITA)

A bachelor's degree in CS/EE (or equivalent) plus 2–3 years of experience in internetworking, DNS administration, or HTTP server/proxy operations — or a master's degree plus ~1 year. Such a person:

• knows RFC 1034/1035 and BIND zone semantics, CNAME delegation, NS records, and DNS RR;
• knows proxy-cache operation and the HTTP/1.0 caching model (If-Modified-Since, Expires);
• knows the 1996–2000 commercial GSLB/DNS-redirection and load-balancing appliance market;
• is comfortable with ping/traceroute/SNMP as measurement primitives.

This is a predictable, well-documented art with published standards, which cuts strongly toward obviousness under KSR's "predictable results" and MPEP 2143(A)/(G).

5. The combination grounds

Ground 1 — CDN/caching elements (Set A) + DNS selection (B1–B4)

Primary: Leighton '703. Secondary: Farber '598; Malkin '193.

Leighton discloses, in one reference: distributed edge servers holding embedded-object content for a content provider (A1), serving client browser requests (A2), a DNS layer choosing a well-suited server by location and bandwidth (B1, B2), and low-level DNS tables continually updated based on network conditions and load (B2, B4). Its fingerprint/URL-rewriting addresses stale content (cf. A4).

Leighton's ghosts are primarily push/replication-populated. The '699's distinguishing step is pull-through fill-on-miss from the origin (A3) plus periodic If-Modified-Since revalidation (A4). Both are squarely in Farber '598 (reflectors/repeaters serving requests and rewriting identifiers) and in Malkin '193 (transparent redirection to proxy caches), and are admitted by the '699 specification ("the periodic checking is a common feature of caches").

Motivation (MPEP 2143(A), (C), (G)): Both Leighton and Farber address the same problem — serving distant, bursty Web demand without forcing publishers to build and synchronize mirror sites. Combining DNS-directed edge delivery with a proxy cache that fills on demand from the origin is the combination of two known techniques for a known purpose, producing the predictable benefit each reference already promises (locality + origin shielding), with no change in their respective principles of operation. KSR: "a patent composed of several elements is not proved obvious merely by demonstrating that each element was independently known" — but here the functional linkage is the very benefit both references state.

Ground 2 — GTM/DNS-selection elements (B1–B3, B6 partial)

Farber '598 + Colby '264 + Gifford '718.

Collectively these three disclose every ingredient of the "closest, available, least-loaded" selection:

• Farber — interception + best-repeater selection from a set, redirect, network distance as a criterion, one shared infrastructure serving many providers, identifier rewriting;
• Colby — a Content Server Database and Content/Locality probes feeding a redirector (probe-driven, metric-based selection; content-aware routing);
• Gifford — replica advertisements carrying internetwork performance information and client-address-keyed direction to a replica.

Motivation (MPEP 2143(A), (D)): The '699 specification concedes the prior art performed DNS round-robin mirror selection and load-based balancing, and both Farber and Leighton expressly criticize those techniques for ignoring network distance. Substituting a metric-weighted selection (latency + load + availability) for round-robin, in a system already configured to make a routing decision at a redirecting name server, is a simple substitution of a known element for another to obtain a predictable improvement — the classic Ground-2 posture. The configurable weighting (B2) is routine engineering: the references already weight/rank candidates by their metrics.

Ground 3 — Persistence (B5)

Known design choice + US 6,754,706 (Swildens et al., "Scalable domain name system with persistence and load balancing," 2004-06-22) + Gifford '718 + Civanlar '212.

"Return the same IP to the same client" is (a) the direct consequence of Gifford '718's client-address→replica mapping, (b) the DNS analog of well-known session affinity / "sticky" load balancing (cf. Brendel '660's delayed resource binding), and (c) the subject of a sibling Speedera patent, US 6,754,706, issued the same day as the '699. That the same inventors treated persistence as a separately claimed improvement is itself evidence they regarded it as a discrete, known design axis rather than a unitary invention.

Motivation (MPEA 2143(E), (F)): Avoid client thrashing among servers and preserve cache/session affinity; only a finite, predictable set of implementations exists (hash client address; DNS cookie; TTL/"refresh" timeout — all three are enumerated in the spec). Sharing the table across the zone's authoritative servers is a routine consistency measure once the decision is made to answer DNS locally.

Ground 4 — Per-zone assignment/forwarding (B6) and two-tier remapping (B7)

RFC 1034 § 4.2.1 / RFC 1035 + Leighton '703 + Farber '598.

• Zone-based delegation, authoritative-NS designation, and returning NS records are core, standardized DNS behavior, not invention. Splitting a namespace into zones and having a non-authoritative server forward/refer to the authoritative zone is the base case of RFC 1034.
• Choosing which name server to forward to by lowest latency is the Ground-2 selection teaching applied one tier up — "using a known technique (metric-based selection) to improve a similar device (a set of name servers) in the same way."
• The two-tier / edge sub-domain trick is a direct application of the hostname/fingerprint prepending Leighton already teaches (www.speedera.net → www.edge.speedera.net mirrors Leighton's "prepend virtual server hostname") and Farber's identifier rewriting. Its stated purpose — exceeding the practical cap on authoritative NS records for a single domain and preventing client-resolver "flip-flopping" — is a market/engineering constraint driving a known solution (MPEP 2143(F), (G)).

Ground 5 — Probe suite (B3)

Colby '264 (ICP/IPP/Proximity Assist) + Gifford '718 (replica performance advertisements) + admitted conventional measurement primitives.

HTTP-GET timing, ping, traceroute, ICMP unreachable-port probing, SNMP interface counters, load-average/swap monitoring are each named and described as conventional in the '699 specification itself. Colby and Gifford supply the architectural teaching of distributing measured metrics to the decision point. Broadcasting results to all decision servers rather than storing them at the probe is expressly justified in the spec by DNS answer latency — i.e., a design trade-off, not an inventive step. KSR: finite, predictable design choices.

Ground 6 — Caching + freshness (A1–A4) — substantially admitted

Beyond Ground 1: Malkin '193 plus the spec's own admissions ("common feature of caches"; "look at expiry headers"; "If-modified-since request back to the origin site") place A1–A4 in the art. The only asserted differentiator — no software or hardware installed at the customer site — is a deployment/business-model feature (Ground 7), not a technical one.

Ground 7 — Service/accounting method (C1) ⚠️ weakest ground

Registration → service election → periodic fee → accounting module → invoicing by mail/e-mail/card debit. I did not retrieve a specific documentary prior-art reference for this element, so I do not assert it as a clean two-reference § 103 ground. Properly framed, it is a "routine and conventional" argument (MPEP § 2144.04) — automating a then-ubiquitous application-service-provider subscription/billing workflow with a general-purpose accounting module and e-mail/e-card invoicing, motivated by the market forces of the ASP era. Flagged as inference, not citation.

6. Element → reference cross-reference

Best documentary attack: Leighton '703 + Colby '264 + Malkin '193 + Gifford '718, with '706/standard sticky-DNS for B5 and RFC 1034 for B6.
Best KSR shortcut: Leighton '703 (or Farber '598) as primary, plus the '699 specification's own admissions as the evidentiary basis for official notice on the remaining elements.

7. What the patentee would argue, and the counter

Patentee's best argument — "unification was the invention." No single reference discloses one operator running a DNS-based GTM and a pull-through CDN behind one configuration file, one UI, and one billing stream. The '699 specification itself frames the advance as the elimination of "the need for independent CDN and GTM solutions."

Counter — and this is where KSR bites hardest. That sentence is an admission that both solutions existed independently and were combined. Two known systems, addressing the same problem (delivering content quickly to distant, unpredictable clients) and sharing the same technical substrate (DNS, HTTP, edge servers), are the paradigm combination case. Further, the '699 is not a technical advance over its own earlier family members: US 6,484,143 (filed 2000-08-18, the expressly claimed priority) covers the same combined GTM+CDN disclosure, and US 6,754,706 (same inventors, same issue date) covers the persistence feature — a strong indication that the '699's claims are drafting divisions of one disclosure, not separate inventions. The '699's specification additionally contains multiple express admissions that its individual mechanisms were conventional.

Other likely arguments and their limits:

• "The specific composite weighting of closest + available + least-loaded is the invention." — Colby/Farber/Gifford already teach metric-weighted candidate ranking; the weights reside in a plain configuration file, and MPEP § 2144.04 disfavors patentability for mere configuration of known parameters absent criticality.
• "The threshold/absolute-value limits are critical." — The "send size / send interval," "update = all tests since last update," and "every needed server holds a current config copy" requirements read as implementation detail; no criticality or unexpected result is asserted in the specification.
• Superlative claim terms. Note that "best"/"optimal" phrasing in the same corporate family was held indefinite in Akamai Techs., Inc. v. MediaPointe, Inc., No. 2024-1571 (Fed. Cir. Nov. 25, 2025) (US 8,559,426; US 9,426,195) — a scope problem, not a § 103 one, but relevant to how much of the "closest/least-loaded" language can be read narrowly enough to escape Ground 2.

8. Secondary considerations

I found no evidence of nexus-bearing secondary considerations: no unexpected results, no long-felt-but-unmet need, no industry praise or copying attributable to the claims, and no licenses of the '699 specifically. The 2003–2005 Akamai v. Speedera dispute terminated by acquisition (2005–2006) rather than judgment, so no tribunal ever validated the '699 against the prior art. Where commercial success exists, nexus is weak — it is plausibly attributable to the outsourced-service/billing model and network scale (Ground 7 / Element Set C), not to any claimed technical step. The related Akamai CDN patents were met with IPRs (e.g., the '777 and '112 petitions appearing in this session's results, which used Leighton as a primary reference) — so the family's claims have been actively contested on essentially the art catalogued above.

9. Honest statement of what I could not establish

1. The claim text. Not retrieved. Element correspondence is provisional and must be verified against the issued PDF.
2. "The Prior Art section of this page." Does not exist in the supplied text beyond keyword tags and one priority cross-reference. The grounds above are my own search-derived construction, not the record's citations.
3. US 6,754,706 / '143 exact claim coverage. I verified bibliographic data (same inventors, same issue date / same family) but not the claim scope.
4. Gupta '252. Bibliographic relevance inferred only from a PTAB excerpt describing an IDS; disclosure not verified.
5. Products, standards, and RFCs (DistributedDirector, Resonate, F5, Squid/Harvest, BIND, IDMaps, NWS, traceroute): not verified this session — flagged as corroboration only.
6. No IPR/PGR on the '699 itself was located, but the search step for that question was cut off by a tool limit, so the result is inconclusive, not negative.

Bottom line: On the reference set I was able to verify, the '699's subject matter — DNS-directed selection among distributed content servers on latency/load/availability metrics, pull-through cache-fill from an origin with If-Modified-Since revalidation, per-client persistence, and per-zone DNS authority — is highly vulnerable under § 103. The strongest attack is Leighton '703 + Farber '598 + Colby '264 + Gifford '718 + Malkin '193, with the '699 specification's own admissions supplying the "routine and conventional" bridge for the residual configuration, probe-broadcast, persistence, and zone-delegation elements. That conclusion is contingent on claim scope I could not verify, and the priority-date ambiguity around Leighton's 2000-08-22 issue date is the one technical point a patentee could most profitably litigate.