US 8089980

I'll search for authoritative current information on US 8089980, including any CAFC 2026 activity.

Let me search for more specific litigation and docket information.

Let me do a couple more targeted searches for any Federal Circuit appeal involving the '980 patent.

Summary of US Patent 8,089,980 (US8089980B2)

I searched for the specific number 8089980 in connection with USPTO/PTAB and Federal Circuit activity. Below is what I can verify from the authoritative patent text and located sources, with explicit notes on what I could not confirm.

Bibliographic data

(Sources: Google Patents page https://patents.google.com/patent/US8089980/en; complaint language in the RPX/M.D. Fla. filings referencing "sixteen claims, namely three independent claims and thirteen dependent claims.")

Abstract (as issued)

"A protocol is provided being executed with a redundancy of 1:1. As a result, an identical clone, with identical hardware, identical software and an identical data base, is allocated to each switching system to be protected, as a redundancy partner. Switching is carried out in a quick, secure and automatic manner by a superordinate, real-time enabled monitor which establishes communication with the switching systems which are arranged in pairs. In the event of communication loss with respect to the active communication system, real-time switching to the redundant switching system is carried out."

Plain-language overview of the independent claims

Claim 1 — core method (no database/software identity requirement):

• Provide a pair of geographically separate switching systems that are dedicated redundancy partners for each other; one is active, the other is in hot-standby.
• Communication between each switching system and a monitoring unit is controlled according to each system's operating state.
• When communication to the active system is lost: the monitoring unit activates the hot-standby system (into active) and deactivates the failed system into hot-standby — where a hot-standby system is not active in terms of switching functions.
• Added feature: a packet-based interface of the hot-standby system, while in an inactive state, periodically sends an "IP lease request" to the monitoring unit.
• (Note: the claim says "IP lease request"; the description describes this mechanism using BOOTP/DHCP-style IP address requests.)

Claim 11 — adds database-identity and "ignore" limitations:

• Same pair/active/hot-standby and switchover structure as Claim 1, plus each switching system has a database identical to the other's, and that database contains only permanent and semi-permanent data — transient call data is excluded.
• Plus the same "periodically sending an IP lease request" feature, and the monitoring unit ignores the IP lease request while the system is hot-standby.

Claim 14 — adds software-identity and "ignore" limitations:

• Same pair/active/hot-standby and switchover structure, plus the pair runs identical software, and every software update including patches is delivered identically to both systems.
• Plus the same "periodically sending an IP lease request" feature, and the monitoring unit ignores the IP lease request while the system is hot-standby.

Docket / litigation notes (2019–2020, from located sources)

• The '980 patent was asserted by Blueprint IP Solutions, LLC (a subsidiary of IP Edge, LLC) in a campaign beginning March 2019, hitting numerous defendants in Delaware, Ohio (N.D. and S.D.), Florida (M.D. and S.D.), and elsewhere (case numbers such as 1:19-cv-00968 through 1:19-cv-00971; 1:19-cv-00577 through 1:19-cv-00582; 8:19-cv-03127; 1:20-cv-00079; 2:20-cv-01036; 5:20-cv-00425; 1:20-cv-20403; 1:20-cv-00156; 1:20-cv-00155; 1:20-cv-00197; 8:20-cv-00724; 8:20-cv-00725; 1:19-cv-25229).
• Unified Patents PATROLL ran a crowdsourced prior-art contest for US 8,089,980 (Apr 5 – Jul 5, 2019) seeking art with a priority date before 2003-12-12, and announced a winner (a prior-art find) in January 2020.
• Accused systems in the complaints involved Hadoop/HDFS architectures (e.g., a "Namenode" mapped to the claimed "monitoring unit" and paired DataNode racks mapped to the active/hot-standby "switching systems").

CAFC 2026 docket — search result and uncertainty

I searched for a Federal Circuit 2026 docket or appeal specifically involving US 8,089,980.

• I did not find any CAFC 2026 docket, opinion, or Rule 36 judgment referencing US 8,089,980 (or the "'980 patent" in the Blueprint IP Solutions context).
• The only CAFC 2026 disposition that surfaced in my search was an unrelated case, Apple Inc. v. LBT IP I LLC, No. 2024-1508 (Fed. Cir. Feb. 6, 2026) (Rule 36 judgment in IPR2020-01189) — not related to 8,089,980.
• Uncertainty note: Because the '980 patent apparently lapsed for nonpayment of maintenance fees (legal events indicate expiration effective 2024-01-03, with an adjusted-expiration entry of 2027-10-01), and because I could not retrieve a 2026 CAFC docket, I cannot confirm any active 2026 appellate proceeding for this patent. I am not asserting that none exists — only that my searches did not surface one, and I don't want to fabricate a docket. A direct PACER/CAFC docket query under the specific case number would be required to state this definitively.

If you can provide a specific Federal Circuit appeal number you believe is tied to 8,089,980, I can verify that exact docket rather than relying on a name/number search.

I'll search for litigation involving US patent 8089980.

Let me identify the remaining defendants and outcomes for these cases.

Litigation Involving U.S. Patent No. 8,089,980

Important note on source grounding: The identifiers below are reproduced literally from the sources retrieved. Where a source did not yield a defendant name or an outcome, I say so explicitly rather than guessing. All cases below were filed by Blueprint IP Solutions, LLC (a Texas entity; an affiliate of IP Edge LLC), which acquired the patent via IP Edge LLC in 2019 (assignment recorded 2019‑03‑26, effective 2019‑03‑25). The patent is a former Siemens AG asset. The Google Patents family record for US 8,089,980 links these cases and notes "Family has litigation."

Also relevant: in 2019, Unified Patents ran a prior‑art crowdsourcing (Patroll) contest for "8089980 – Networking structures," explicitly noting the patent was "owned and asserted in multiple district court cases by Blueprint IP Solutions, LLC." (https://patroll.unifiedpatents.com/contests/pM4fAmhw36sKpQmB5)

District of Delaware — Judge Leonard P. Stark

Filed the same day (March 28, 2019), a six‑case wave:

A second Delaware wave was filed May 28, 2019:

Middle District of Florida

Southern District of Florida

Southern District of Ohio

(Note: 1:20‑cv‑00156 is the same case as 2:20‑cv‑01036 — the docket shows it was transferred from the Western Division at Cincinnati to the Eastern Division.)

Northern District of Ohio

Summary of substantive developments

• No appellate (CAFC) decisions involving the '980 patent were found in the retrieved sources.
• Eligibility (35 U.S.C. § 101) was contested. In Blueprint IP Solutions, LLC v. Publix Asset Management Co. (M.D. Fla. 8:19‑cv‑03127), Blueprint argued Claim 1 recites a non‑abstract, unconventional inventive concept — specifically "periodically sending an IP lease request to the monitoring unit by a packet‑based interface of the switching system in the hot‑standby operating state" — and invoked Aatrix Software v. Green Shades Software. Accused technology in that and the Catalina case was framed as Hadoop HDFS/DataNode redundancy.
• Unified Patents prior‑art contest (2019): sought art predating the 2003‑12‑12 priority date against claims 1–16.
• Patent status: The patent expired for failure to pay maintenance fees — lapse effective 2024‑01‑03 (recorded 02/05/2024). The Google Patents record lists it as "Expired – Fee Related," with adjusted expiration 2027‑10‑01.

Gaps I could not close

Because my search budget was exhausted, I could not confirm: (1) the defendants in D. Del. 1:19‑cv‑00971, M.D. Fla. 8:20‑cv‑00725, S.D. Fla. 1:19‑cv‑25229 and 1:20‑cv‑20403, or N.D. Ohio 5:20‑cv‑00425; and (2) final dispositions for 1:19‑cv‑00579 (Hitachi Vantara), 1:19‑cv‑00580 (NetApp), 1:19‑cv‑00582 (Talend), 1:19‑cv‑00968 (Informatica), and 1:19‑cv‑00969 (Mesosphere). These should be verified against PACER/Unified Patents/RPX for a definitive accounting.

I'll start by checking for any PTAB proceedings beyond what the structured block reports.

Let me search more specifically for any PTAB filings and related litigation outcomes.

Let me run two final confirmation searches before concluding.

Proceedings overview

Total AIA trial proceedings on US 8,089,980: 0. The structured "PTAB proceedings on file" block (USPTO Open Data Portal, most recent ingest) reports no AIA trial proceedings, and my independent web searches surfaced no IPR, PGR, or CBM naming the '980 patent — no institution decision, no Final Written Decision, no appeal. Bottom line for a defendant: there is no PTAB kill-shot on the record and no estoppel to exploit — but the patent is also no longer a live threat, because it expired for failure to pay maintenance fees on 2024-02-05. This is not a "hardened by surviving IPRs" patent; it is an untested, unpracticed one whose owner monetized by mass-filing district-court suits and settling, never by litigating validity at the Board.

No proceeding to report

Because the canonical list is empty, there is no {PROCEEDING_NUMBER} — Petitioner v. Patent Owner block to populate. Stating the negative plainly, per the constraints: no AIA trial petition against US 8,089,980 was ever instituted, and none appears ever to have been filed.

What actually happened around this patent (context, not PTAB)

Two datapoints explain the absence, and both matter to a defendant:

1. A defensive aggregator surfaced the patent but converted it to a prior-art hunt, not an IPR. Unified Patents ran a PATROLL crowdsourcing contest on the '980 patent — contest window 2019-04-05 to 2019-07-05, $1,000 prize, seeking art with a priority date before 2003-12-12 covering claims 1–16 (Unified Patents PATROLL contest page; winner announcement: Unified Patents, "Prior art found for Blueprint IP," 2020-01-27). The framing confirms the patent was owned by Blueprint IP Solutions, LLC, described as "a subsidiary of well-known NPE, IP Edge, LLC." That contest produced a published prior-art reference, but no IPR petition followed — Unified's standard play (challenge early) was not executed here, most likely because the July 2020 assertion wave dissolved into settlements before an IPR was worth filing. There is no Unified IPR number to cite; do not infer one.

2. The litigation campaign settled out, removing the incentive to file. Per the structured litigation data and docket records, Blueprint filed a wave of parallel district-court actions starting in 2019 (Delaware: e.g. 1:19-cv-00577 through 1:19-cv-00582, 1:19-cv-00968/00969/00971; Florida: 1:19-cv-25229, 8:19-cv-03127, 6:19-cv-02396) and again in early 2020 across Ohio, Florida, and Delaware. The 2020 cases resolved quickly and nearly uniformly by voluntary dismissal or joint dismissal after notice of settlement. Representative examples:

• Blueprint IP Solutions, LLC v. Parker-Hannifin Corp., No. 1:20-cv-00197 (N.D. Ohio) — joint motion to dismiss 2020-03-25; claims dismissed with prejudice, counterclaims without prejudice.
• Blueprint IP Solutions, LLC v. State Auto. Mut. Ins. Co., No. 2:20-cv-01036 (S.D. Ohio) — joint motion to dismiss 2020-04-23.
• Blueprint IP Solutions, LLC v. Great American Fin. Grp., Inc., No. 1:20-cv-00155 (S.D. Ohio) — notice of voluntary dismissal 2020-04-10.
• Blueprint IP Solutions, LLC v. Catalina Mktg. Corp., No. 8:20-cv-00724 (M.D. Fla.) — notice of settlement/stay 2020-06-18, voluntary dismissal 2020-08-27.

Parker-Hannifin's docket shows the signature defense package — a § 112 motion to dismiss for failure to state a claim plus counterclaims for declaratory judgment of invalidity/non-infringement — filed before the case settled. That is the classic posture that produces a settlement rather than an IPR.

3. The patent lapsed. Per the structured legal-status data: maintenance-fee reminder 2023-08-21; lapse for failure to pay maintenance fees 2024-02-05, "PATENT EXPIRED FOR FAILURE TO PAY MAINTENANCE FEES"; effective lapse date 2024-01-03. Google Patents records the adjusted expiration as 2027-10-01 (20-year term from the 2004-08-26 PCT filing), but the patent is not enforceable for the unpaid-fee period — it is a dead letter.

Strategic summary

Claim status — all claims UNTESTED. No claim of the '980 patent — independent claims 1, 11, and 14, or their dependents 2–10, 12–13, and 15–16 — has been canceled, confirmed, or even reviewed at the Board. Every claim stands exactly as issued in the 2012 grant; none is "dead," and none is "hardened." Any representation that some claims were invalidated, or that the patent survived IPRs, would be false and should not be made to a client.

Estoppel landscape — none created. Because there was no IPR/PGR, § 315(e)(2) estoppel never attached to any petitioner or privy. There is no Board-record ground that is foreclosed. If a defendant were still facing assertion (it is not, given the 2024 lapse), the entire prior art universe — including both the § 102/§ 103 art cited on the face of the patent and any art surfaced by the 2019 PATROLL contest — would remain available in district court, subject only to the ordinary § 282 burden and the district court's own case-management.

Pattern signals. (a) No repeat petitioner — no petitioner at all. (b) The patent owner did not pursue Board proceedings; Blueprint/IP Edge monetized through volume filings resolved by settlement, a pattern consistent with avoiding validity adjudication. (c) A defensive aggregator was in the chain but chose a crowdsourced prior-art route over an IPR. (d) Ownership passed through the classic IP Edge divestiture chain: Siemens AG → IP Edge LLC (2018-11-29) → Blueprint IP Solutions LLC (2019-03-26), before the patent lapsed in 2024.

Recommended next steps

• If you are a defendant receiving a demand on US 8,089,980 today, demand-and-dismiss. The maintenance-fee lapse of 2024-02-05 means the patent owner cannot recover for any infringement occurring on or after lapse without a petition to accept late payment under 37 C.F.R. § 1.378 — a discretionary remedy that is rarely granted for a multi-year default by a sophisticated NPE holding. Point to the structured record: "PATENT EXPIRED FOR FAILURE TO PAY MAINTENANCE FEES," effective 2024-01-03.
• Do not argue from a nonexistent IPR. There is no Final Written Decision to quote or link. If opposing counsel or a licensing agent claims claims were canceled or the patent was "confirmed by the PTAB," it is inaccurate — ask them to produce the proceeding number, because none exists on ODP.
• If you need the record itself: confirm the absence directly at USPTO Patent Center (application US 10/582,589) and the PTAB E2E / PTAB Decisions portal by searching patent number 8,089,980; the ODP "PTAB proceedings" list for this patent is empty as of the most recent ingest. The closest non-PTAB artifact is the Unified Patents PATROLL contest (https://patroll.unifiedpatents.com/contests/pM4fAmhw36sKpQmB5) and the 2020-01-27 Unified Patents post "Prior art found for Blueprint IP."
• No appeal to track. With no FWD, there is no Federal Circuit docket and nothing on CourtListener for this patent's PTAB history.

Confidence note: I found no AIA trial proceeding in either the canonical structured data or web search. I could not complete a final round of confirmatory searches (tool-step limit reached), so I cannot rule out an obscure, never-publicized petition that was filed and denied institution pre-Fintiv-era; but nothing in the record suggests one exists, and the maintenance-fee lapse has mooted the question. Treat the operative answer as zero AIA trials on file.

I'll research the assignment chain, litigation, and the parties involved.

Let me find the recorded correspondents and additional assignment details.

US 8,089,980 — Assignment & NPE Analysis

Data note up front: Google Patents' legal-events table (which mirrors the USPTO assignment database) discloses three recorded assignments with reel/frame numbers, assignors, assignees, and execution/recording dates. However, the correspondent-of-record field for these recordings was not retrievable from the sources I could reach in this session. I flag that explicitly below rather than guessing — the correspondent is the single most probative NPE tell and it should be pulled directly from Assignment Center before this analysis is relied on for a filing.

Inventors

• Both inventors assigned to Siemens Aktiengesellschaft by the same instrument, reel 017977/0755, executed 2006-04-21 → 2006-05-04, recorded 2006-06-09 (per USPTO assignment, assignors "LOBIG, NORBERT; TEGELER, JURGEN").
• Departure pattern: No evidence that the inventors left Siemens within 12 months of filing; there is no inventor-to-third-party assignment in the record. The inventors' entire interest went to the corporate employer in the normal course. This is a corporate-owned (employed-inventor) patent, not an inventor-held one — so it is not a classic "inventors bail before the fire-sale" case. Note that the "sale" here was a corporate portfolio divestiture ~14 years after filing, not an inventor liquidity event.

Original assignee

Siemens Aktiengesellschaft (Munich, Germany) is the entity named on the issued patent.

• Line of business: Siemens AG is a diversified industrial/electrical-engineering conglomerate. The '980 patent (1:1 hot-standby protection switching for switching systems, BOOTP/DHCP-based) sits squarely in Siemens' carrier networks / telecommunications switching business — the unit that became Nokia Siemens Networks in 2007 (later Nokia Solutions and Networks, and Nokia's networks business).
• Product embodying the claims: The claims read on a carrier-class softswitch/switch controller with geographically separated hot-standby redundancy. Siemens shipped such switches; whether a specific commercial product practiced these exact claims is not established in the record I reviewed.
• Current status: Operating. Siemens AG remains a going concern; it exited the carrier-switch business via the NSN/Nokia transaction rather than through insolvency. The '980 patent was part of a large former-Siemens telecom portfolio sold off in 2018.
• Key fact for the NPE analysis: RPX documents that in October 2018 Siemens assigned this patent, together with "more than two dozen other US patents," to IP Edge LLC — a bulk asset sale, not an operating-company continuation.

Assignment timeline

• 2006-04-21 / 2006-05-04 (executed) / recorded 2006-06-09 — Reel 017977/0755

  • Conveyance: Assignment (assigns entire interest)
  • Assignor: Norbert Löbig; Jürgen Tegeler
  • Assignee: Siemens Aktiengesellschaft (Germany)
  • Correspondent: Not retrievable in this session — verify in Assignment Center. (No recurrence assessment possible.)
  • Context: Routine employed-inventor assignment to the original corporate assignee.

• 2018-10-20 (executed/effective) / recorded 2018-11-29 — Reel 047686/0465

  • Conveyance: Assignment
  • Assignor: Siemens Aktiengesellschaft
  • Assignee: IP Edge LLC (Texas)
  • Correspondent: Not retrievable in this session — verify in Assignment Center. (This is the entry most in need of the correspondent field: IP Edge recordings across its portfolio typically share a single repeat-player attorney/firm, which is the crux of signal #3.)
  • Context: Bulk portfolio divestiture / transfer-to-asserter — RPX reports Siemens moved this patent with "more than two dozen other US patents" to IP Edge in October 2018.

• 2019-03-25 (executed/effective) / recorded 2019-03-26 — Reel 048705/0536

  • Conveyance: Assignment
  • Assignor: IP Edge LLC
  • Assignee: Blueprint IP Solutions LLC (Texas)
  • Correspondent: Not retrievable in this session — verify in Assignment Center.
  • Context: Transfer-to-asserter / assertion-race transfer — Blueprint filed its first infringement suits three days later (2019-03-28). See signal #5.

No Security Agreement, Merger, Change of Name, License, or Release recordings appear for this patent in the indexed legal events. The chain is a clean three-link: inventors → Siemens → IP Edge → Blueprint.

Timeline diagram

timeline
    title Ownership of US 8089980
    2003 : German priority application filed by Siemens
    2006 : Inventors assign to Siemens AG
    2012 : US patent grants
    2018 : Siemens sells portfolio to IP Edge LLC
    2019 : IP Edge transfers patent to Blueprint IP Solutions LLC
         : Blueprint sues six tech companies in three days
    2020 : Unified Patents runs prior art bounty
    2024 : Patent expires for unpaid maintenance fees

NPE / troll-pattern signals

1. Shell-entity transfer — PRESENT.
Reel 047686/0465 moves the patent from an operating multinational (Siemens AG) to IP Edge LLC, a Texas LLC; reel 048705/0536 then moves it to Blueprint IP Solutions LLC, a second Texas LLC. Naming (... IP Solutions LLC) plus the absence of any product business, plus the fact that Blueprint's Rule 7.1 disclosure in D. Del. stated "No Parents or Affiliates Listed" while Unified Patents identifies it as "a subsidiary of well-known NPE, IP Edge, LLC," is concrete evidence of a single-purpose assertion vehicle. This is not inference from naming alone.

2. Known asserter in the chain — PRESENT.
IP Edge LLC is explicitly named as a "well-known NPE" by Unified Patents (PATROLL note, 2019) and is a documented high-frequency plaintiff tracked by RPX (e.g., RPX, "IP Edge Files ITC Complaint…," 2020-09-27, listing Blueprint IP Solutions LLC and Cassiopeia IP LLC among "more than ten other IP Edge plaintiffs"). Blueprint IP Solutions is named on Unified's PATROLL and litigated the patent against multiple defendants.

3. Repeat correspondent across the chain — UNCLEAR / DATA GAP.
I could not retrieve the recorded correspondent for any of the three links. This signal therefore cannot be scored on evidence. Action item: query Assignment Center by patent number for reels 017977/0755, 047686/0465, and 048705/0536 and capture the correspondent name/firm for each. (Litigation counsel of record — Timothy Devlin, Devlin Law Firm, and Howard L. Wernow — appear across the 2019 Blueprint suits and are worth noting, but litigation counsel is not the same as assignment correspondent and should not be conflated.)

4. Cascading transfers (<24 months) — PRESENT.
Two consecutive transfers through chained Texas LLCs inside ~5 months: Siemens → IP Edge (executed 2018-10-20) and IP Edge → Blueprint (executed 2019-03-25). Both assignees are Texas LLCs in the same IP Edge plaintiff family per RPX. This is the textbook rapid re-spin of a portfolio into fresh assertion vehicles.

5. Pre-litigation transfer — PRESENT (strongest signal).
Blueprint acquired the patent 2019-03-25 (recorded 2019-03-26) and filed its first suits 2019-03-28 — a 3-day gap, well inside the 6-month window. D. Del. case nos. 1:19-cv-00577 through 00582 were all filed 2019-03-28 (Fortinet, Hewlett Packard Enterprise, Hitachi Vantara, NetApp, Oracle, and a sixth defendant). Additional suits followed in Florida Middle, Florida Southern (accusing "Disney BigData Hadoop Technology"), and Ohio. This timing demonstrates the assignment chain was arranged to establish a clean standing record immediately before assertion.

6. Bankruptcy fire-sale — NOT PRESENT.
No bankruptcy of Siemens AG or any assignor appears. This was a voluntary corporate portfolio divestiture, not a Chapter 7/11 sale.

7. Privateering — UNCLEAR.
The structure (operating company → known NPE → assertion against other operating companies) fits the shape of privateering, but I found no evidence of Siemens retaining an economic interest, revenue share, or control over the assertion campaign. A straight portfolio sale to an NPE is better characterized as a divestiture-to-asserter than as proven privateering. Score unclear absent SEC/press evidence of Siemens' participation.

8. Defensive aggregator — NOT PRESENT.
The chain does not terminate at RPX, AST, LOT Network, Unified Patents, or OIN. Instead, Blueprint's campaign drew Unified Patents' opposition: Unified ran a $1,000 PATROLL prior-art bounty on US 8,089,980 (opened 2019-04-05; winner Rakon Nahar, announced 2020-01-27), and published prior art against it. The patent was neutralized by expiration, not acquisition: maintenance fees went unpaid and the patent expired 2024-01-03 (recorded 2024-02-05).

Verdict

NPE — high confidence.

Four signals are present on documented evidence, at least three of them "strong": (i) a shell/assertion-vehicle transfer from operating Siemens AG to IP Edge LLC, reel 047686/0465 (executed 2018-10-20), then to Blueprint IP Solutions LLC, reel 048705/0536 (executed 2019-03-25); (ii) a known asserter in the chain, with IP Edge identified as a "well-known NPE" by Unified Patents and Blueprint named as an IP Edge plaintiff by RPX; (iii) cascading transfers through two Texas LLCs in ~5 months; and (iv) a pre-litigation transfer — patent acquired 2019-03-25, first of six D. Del. complaints filed 2019-03-28, a three-day gap. The only unsupported signal is the repeat-correspondent check (#3), which is a data gap, not a negative — pull the correspondent fields for reels 017977/0755, 047686/0465, and 048705/0536 to close it.

Verify at: USPTO Assignment Center (search patent 8,089,980) or the legacy Assignment Search.

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

Prior-Art Analysis — U.S. Patent No. 8,089,980 B2

1. Confirming the target patent (no similar numbers)

I could not execute a live authenticated query against USPTO PatentCenter/PatFT from this environment; however, the authoritative full text of the patent was supplied and is reproduced at Google Patents (https://patents.google.com/patent/[US8089980](/patent/US8089980)/en). Per your rule, I am treating that reproduction as ground truth.

Legal frame: priority is 2003-12-12, so this is a pre-AIA patent. The relevant subsections are §102(a) (known/used/patented/published before invention), §102(b) (printed publication/patent more than one year before filing), and §102(e) (U.S. patent/application publication with an earlier effective U.S. filing date). All references below are listed as "Patent Citations (16)" on the face of US 8,089,980. Google Patents flags some as examiner-cited (∗) and some as third-party-cited; I note my confidence on each.

Critical caveat on "anticipation": every independent claim (1, 11, 14) requires, as a "further feature," periodically sending an IP lease request (BOOTP/DHCP) from an inactive packet-based interface of the hot-standby system to the monitoring unit, with the active/hot-standby state being signaled by whether the monitor answers with an IP lease. The 16 cited references are almost all generic active/standby redundancy and monitoring disclosures. On the record available to me, none appears to disclose the IP-lease-request gating mechanism, so none is a clean §102 anticipatory reference for the independent claims; they are best characterized as §103 obviousness art. I flag the closest ones below but must state this explicitly rather than overstate anticipation.

2. The 16 cited references

(a) References closest to the claimed subject matter

(b) Broader/supporting references

(Codes: the Google Patents listing marks items with an asterisk as examiner-cited and with a dagger as third-party-cited. The plain-text reproduction I worked from de-interleaved those glyphs, so I am not asserting a specific examiner-vs-third-party attribution per row; treat that column as unverified.)

3. Most relevant prior art — ranked

1. US 5,473,599 A (Cisco — Standby Router Protocol, 1995) — the single most relevant reference. It is the canonical teaching of an active/standby pair with defined operating states, periodic monitoring messages, and failover when the active device stops responding. It maps onto the skeleton of claim 1 and the monitoring/acknowledgement mechanics of claims 7–8.
2. US 7,535,827 B2 (Alcatel Lucent, filed 2003-10-09) — the most date-dangerous §102(e) reference because it was filed two months before the 8089980 priority date, is in the same telecom field, and is expressly directed to "high availability … using synchronized redundancy."
3. US 6,108,300 A (Cisco, transparent failover network device, 2000) — strong on IP-address-based transparent switchover (claims 4–5).
4. US 6,173,411 B1 (Foxboro, fault-tolerant network connection switchover, 2001).
5. US 2003/0152064 A1 (Khan, redundant SS7 over VoIP, 2003).
6. US 6,005,841 A (Excel Switching, 1999) and US 5,974,114 A (AT&T, 1999) — telecom 1:1 redundancy.
7. US 5,835,696 A (Lucent, router backup, 1998) and EP 0 412 799 A2 (Boston Technology, 1991) — background redundancy.
8. Remaining references (Sun, Naismith, Guess, Exanet, Schneider, Cole, Huawei) — general high-availability/failover background; individually weak against the independent claims.

4. Honest limitations

• I am working from the citation list on the face of US 8,089,980 plus the patent's own specification; I did not retrieve and read the full text of each of the 16 references, so my claim-mapping is a screening assessment, not an element-by-element §102 chart.
• The distinguishing feature of every independent claim is the BOOTP/DHCP IP-lease-request handshake used to gate interface activation on the hot-standby system, plus the "split-brain" avoidance described in the spec. None of the 16 references, on their face, disclose that mechanism. Consequently, no reference here is a confident §102 anticipator of claims 1, 11, or 14; they are relevant primarily under §103.
• Two references are worth a deeper validity check because of their pre-priority effective filing dates: US 7,535,827 B2 (filed 2003-10-09) and US 2009/0219804 A1 (filed 2000-12-11)—both qualify as §102(e) art despite late issuance/publication dates. If you want a true anticipation chart, these two and Cisco's US 5,473,599 A are where I would start.

Want me to pull the full text of the top three references and build a limitation-by-limitation §102/§103 chart against each independent claim?

I'll analyze US 8,089,980 for obviousness under § 103 using the prior art cited on the patent page. Let me first verify the content of the key references.

Let me verify additional key references, particularly those relating to address-leasing and geographically-diverse redundancy.

Obviousness Analysis — US 8,089,980 B2 under 35 U.S.C. § 103

Patent: US 8,089,980 B2 ("Method for protection switching of geographically separate switching systems")
Inventors: Norbert Löbig, Jürgen Tegeler | Original assignee: Siemens AG | Priority: 2003‑12‑12 (DE 10358344.0) | Filed (PCT): 2004‑08‑26 | Granted: 2012‑01‑03
Source: https://patents.google.com/patent/US8089980/en

Note on data reliability: the reference descriptions below are drawn from the patent page's own "Citations"/"Families Citing" tables plus verified abstracts I retrieved. Where I could not independently verify a reference's disclosure, I say so explicitly rather than inferring content.

1. Legal framework applied

Under Graham v. John Deere Co., 383 U.S. 1 (1966), and KSR Int'l Co. v. Teleflex Inc., 550 U.S. 398 (2007), the analysis proceeds through: (a) the scope and content of the prior art, (b) the differences between the prior art and the claims, (c) the level of ordinary skill, and (d) secondary considerations. Critically for this patent, the specification's own "Background of Invention" section contains an admission that the core architecture is prior art:

"A 1:1 redundancy has been proposed as a solution. Accordingly it is provided to assign each switching system requiring protection an identical clone as a redundancy partner having identical hardware, software and database. The clone is in the powered-up state, but is nonetheless not active in terms of switching functions. Both switching systems are controlled by a realtime-capable monitor, ranked at a higher level in the network hierarchy, which controls the switchover operations."

That admission dramatically narrows the field: the geographic 1:1 clone, the hot-standby state, and the higher-level monitor are conceded prior art. The only alleged contribution is the use of standard IP lease (BOOTP/DHCP) request/response as the mechanism by which the monitor gates interface activation and thereby performs the switchover.

Level of ordinary skill: a telephony/data network engineer with ~3–5 years' experience in fault-tolerant switching and IP networking, familiar with HSRP-type redundancy and standard IP configuration protocols (BOOTP/DHCP per RFC 951/1541/2131; ARP).

2. Independent claim 1 — element-by-element breakdown

Claim 1 recites, in substance:

1. Providing a geographically separate pair of switching systems with dedicated redundancy (one active, one hot-standby);
2. Controlling communication between each switching system and a monitoring unit according to the operating state of that system;
3. On loss of communication to the active system: the monitoring unit activates the hot-standby system and deactivates the failed system (hot-standby = not active in switching functions);
4. Periodically sending an IP lease request to the monitoring unit by a packet-based interface of the hot-standby system, the interface being in an inactive state.

Claims 11 and 14 add, respectively: (11) the identical database containing only permanent and semi-permanent data, transient call data excluded; and (14) identical software, with every update/patch delivered identically to both systems.

3. Scope and content of the prior art (the cited references)

All listed references have effective dates before the 2003‑12‑12 priority date and therefore qualify as § 102(a)/(b)/(e) prior art.

4. Differences between the prior art and the claims

The architecture of claim 1 elements (1)–(3) is squarely met and, in the specification, conceded:

• Geographically separated active/standby pair with dedicated 1:1 redundancy → taught by US 6,108,300, US 5,974,114, US 6,005,841, and motivated by geography in Khan (US 2003/0152064) and the Genband/Tekelec geo‑diverse references.
• Monitor controls based on operating state; activates standby and deactivates failed unit on lost communication → taught by US 5,473,599 (HSRP hello/failure detection + takeover), US 6,108,300 (failure detection → standby activation), and US 5,974,114 (HAD/MON monitoring → active/standby switchover).
• Database replication / identical software (claims 11, 14) → taught by US 5,974,114 ("full data sharing, database replication and synchronization"; static vs. dynamic call data distinction) and US 6,005,841 (active copies configuration and call‑processing info to standby).

The only genuine difference is element (4): the use of a periodic IP lease request (BOOTP/DHCP "IP Request") from the packet-based interface of the hot-standby system, which remains inactive until the monitor grants it an address, as the gating/handshake mechanism — plus its corollaries in claims 3, 4, 6, 7, 8 (monitor withholds the lease while standby; standby interface activates on receiving the lease; active interface suppresses lease requests; monitor sends monitoring messages the active interface acknowledges; missed acknowledgements trigger the lease response to the standby).

Notably, the specification admits the mechanism uses standard protocols: "The protocol is based on the standard IP protocols BOOTP/DHCP which are usually supported by every IP implementation."

5. Combinations rendering the claims obvious

Combination A (primary): US 6,108,300 (Cisco) + US 5,974,114 (AT&T) + US 2003/0152064 (Khan)

Motivation: All three address the same problem — maintaining service availability when an active device fails — and all are in the same field of packet network fault tolerance (§ 103 obviousness is strongest where references are analogous art addressing the same problem). Cisco supplies the failover network device with standby→active IP address remapping. AT&T supplies active/standby call‑processing computers with monitoring daemons and transparent switchover. Khan supplies the express motivation to separate the redundant pair geographically to survive localized disasters (Khan's own example is an earthquake destroying a switch). A PHOSITA seeking to harden a softswitch against disasters would combine the Cisco failover mechanism with the AT&T monitoring/switchover logic and site the pair at geographically distant locations, as Khan teaches. Result: claim 1 elements (1)–(3). This is a "combination of familiar elements according to known methods… yield[ing] predictable results," KSR.

Combination B (specific to the IP‑lease limitation): Combination A + IP address leasing as the activation gate

Claim 1 element (4) is the crux. Two routes to obviousness:

Route B1 — Cisco's address remapping generalized. US 6,108,300 already teaches that a hot‑standby device holds a standby IP address and does not take over the active address until it becomes active, and that the standby can be assigned its address by configuration/leasing. A PHOSITA would recognize that a device without a valid IP address cannot exchange traffic on the packet interface — i.e., withholding an address is inherently an "inactive/idle" state. Using a standard DHCP/BOOTP server (expressly acknowledged in the '980 specification as universally supported) to selectively grant addresses to the active system's interfaces and to withhold them from the standby's interfaces is the natural, predictable implementation of Cisco's remap-on-failover teaching. The monitor acting as BOOTP server is simply the AT&T "HAD/MON" monitoring role plus the standard server role.

Route B2 — Excel's boot‑sequence teaching. US 6,005,841 discloses a boot sequence that places one device in active and its mate in standby based on boot-time control, which a PHOSITA would implement by conventionally controlling the mate's network configuration — again pointing to conditional address provisioning.

In either route, element (4) and dependent claims 3–9 follow predictably: the monitor does not respond to the standby's lease requests (claim 3) because it must not activate it; the interface switches to active on receiving the lease response (claims 4–5) because that is when it obtains an address; the active interface need not request a lease (claim 6) because it already has one; the monitor sends periodic monitoring messages that the active interface acknowledges (claim 7) à la HSRP hello/ack messages in US 5,473,599 and the AT&T HAD/MON daemons; and a missed acknowledgement triggers the fault determination and the lease grant to the standby (claims 8–9), mirroring US 5,473,599's "no hello within a period → standby becomes active."

Combination C (claims 11 & 14): add US 5,974,114 for data/software identity

• Claim 11 (identical database limited to permanent + semi‑permanent data, excluding transient call data): US 5,974,114 expressly distinguishes static call data (relatively stable) from dynamic call data (changes every call) and replicates/synchronizes the former — directly teaching the claimed database content limitation. US 6,005,841 similarly copies "configuration and detailed call processing information."
• Claim 14 (identical software; updates/patches delivered identically): routine configuration management; the specification itself says this is achieved by "deliver[ing]… every software update including patches… in identical fashion to both partners," and US 6,005,841 teaches establishing an identical initial operating state on the mate before it is placed in service.

6. Why a PHOSITA would have been motivated (rationale summary)

1. Same field / analogous art: every reference addresses availability of switching or call‑processing equipment.
2. Express disaster motivation: Khan (US 2003/0152064) and the specification's own background recite fire, earthquake, attacks, war — the exact rationale for geographic separation.
3. Known, standard protocols: BOOTP/DHCP and ARP are acknowledged in the specification as universally supported; using a standard lease protocol imposes "minimal implementation overhead" (a predictability factor favoring obviousness).
4. Predictable result: selective address leasing to gate activation yields no more than the expected result of a standby that cannot communicate until activated — the very definition of the claims' "idle"/"hot‑standby" state.
5. Design incentive / market pressure: KSR recognizes that designing around a known need with known elements is obvious; the need for sub‑2‑second ("real time," per the specification) failover is a straightforward design objective.

7. Honest limitations of this analysis

• No single verified reference was found that expressly discloses a BOOTP/DHCP monitor selectively answering lease requests from the standby as the switchover trigger. The BOOTP/DHCP‑gating limitation (claim 1 element 4 and its dependent claims) is the strongest non‑obviousness argument. An obviousness rejection therefore depends on (i) the specification's admission that BOOTP/DHCP is standard and (ii) treating DHCP‑lease gating as an obvious implementation choice over Cisco's IP‑remap/hot‑standby teaching. If a challenger cannot produce a reference that itself uses address provision/lease as the state‑control handshake, the dependent claims (especially 3, 6, 8) may survive.
• I could not independently verify the disclosures of US 6,173,411, US 2003/0097610, US 7,023,795, US 7,535,827, CN 1321004 A, or the Genband/Tekelec geo‑diverse references beyond their titles/abstracts as listed on the patent page; the analysis above uses them only as corroborating (not load‑bearing) art.
• The US8089980 patent issued over the 16 cited references, indicating the examiner did not consider the BOOTP/DHCP‑gating combination to be fully taught — consistent with my assessment that the lease‑gating element, not the architectural elements, carries whatever novelty exists.

8. Conclusion

Under § 103, claims 1–16 of US 8,089,980 are highly vulnerable to an obviousness challenge, but not uniformly so:

• Architectural claims/limitations (elements 1–3; claims 11, 14 data/software limitations): plainly obvious over US 5,473,599 + US 6,108,300 + US 5,974,114 + US 2003/0152064 (Khan), and largely admitted prior art by the specification's own background.
• The IP‑lease gating limitations (claim 1 element 4; claims 3–9): the pivotal issue. These are obvious if one accepts that (a) BOOTP/DHCP is a standard, universally available protocol (admitted), and (b) selectively granting/withholding an IP lease is a predictable way to force an interface into "idle" vs. "active," building on Cisco's standby→active IP‑remapping teaching. A defensible non‑obviousness position rests solely on the absence of an express lease‑as‑switchover‑trigger reference in the record.

Evidence to obtain for a formal challenge or defense: full texts of US 6,173,411, US 2003/0097610, US 7,023,795, and the Tekelec/Genband geo‑diverse references; the prosecution history of US 8,089,980 (what the examiner relied on for allowance); and any pre‑2003 art showing DHCP/BOOTP lease granting used to control device activation state.